Возможно, стоит пояснить разницу между синхронизацией из thread/process-safe и синхронизацией с помощью Lock🤔
Наша задача — заставить разные процессы и потоки обращаться к базе данных (или любым другим ресурсам) последовательно. Чтобы не случилось так называемого race condition, то есть состояние гонки. Это когда разные потоки или процессы пытаются одновременно что-то сделать с одним и тем же ресурсом.
В этом случае нам нужна какая-то логика ограничения. Пока один процесс не завершил своё действие, другие не могут получить доступ к ресурсу.
Так вот, thread-safe и process-safe означает что отдельно взятые операции записи в БД гарантированно будут последовательны. Запросы из разных процессов или потоков выстроятся в очередь и не будут мешать друг другу. Лучше всего когда этот блок реализован на уровне БД в виде атомарных операций или ещё как-то.
Но зачем нам тогда еще дополнительный Lock?
Этот способ синхронизации используется когда процесс никак не укладывается в одно действие и должен сделать множество операций прежде чем дать доступ следующему. В этом случае процесс ставит некий глобальный Lock на ресурс и никто другой, даже получив законное право на доступ, не может ничего сделать. Все ждут пока этот Lock не будет снят.
Это решается на уровне приложения и правильность реализации полностью в вашей ответственности. Например, если забыли разблокировать или сделали перекрёстный Lock (Deadlock как на картинке), то всё зависнет в бесконечном ожидании.
#basic
Hello everyone ! Long time without an announcement from your favorite frenchie (@Onelots)
As you know, we try to be as transparent as possible with you.
That's why today we decided to tell you how much money goes in and goes out the project.
As you probably know, about 1 year ago (May 2025) we moved from the "classic" rom scheme (every maintainer builds and send his zips on source forge) to a new one, using a dedicated server to build for all the devices, and cloudflare's content delivery network to provide you the builds as fast as possible all around the world.
This system had many advantages, such as :
- Fast releases (the server is huge)
- Consistent releases (since the sources are always the same as for the other devices on the server)
- Way more security : No one has the signing keys anymore, only the server.
But all this has a cost, and we felt like the community deserved to know what costs how much.
This "1 year period" is the one I used to do this table : From May 2025 to April 2026.
🔊 Please note : We are not begging for money! It's quite the opposite, actually. This message is there to thank you for your support. As you will see in the image below, the people who supported us really helped us to keep the ROM alive.
I'm obviously open to the discussion if anyone has a question about the table I sent. Just ping me and I'll be happy to reply !
#KeepEvolving#EvolutionX
#EvolutionX#UNOFFICIAL#A15#diting
EvolutionX 10.7 | UNOFFICIAL | Android 15
Updated: 29/6/2025
▪️Download: Gdrive | Mirror
▪️Screenshots
▪️Support
Changelogs:
• Sync last source
• Voip volume control problem fixed
• All new infinityx features have been added
• Optimized things for better performance
• Xiaomi camera Support
• Added Sony dolby
• KSU Support
WARNING
It is necessary to clean flash
Credits:Here
By@Jezzay97 | Donate
Follow@xiaomi_12tpro_updates
Join@xiaomi12tpro_chat
#EvolutionX#UNOFFICIAL#A15#diting
EvolutionX 10.7 | UNOFFICIAL | Android 15
Updated: 4/6/2025
▪️Download: Gdrive | Mirror
▪️Screenshots
Changelogs:
• June 2025 security patches have been merged into our Android 15 QPR2 branch. The latest version is now 10.7. As a reminder, all related Play integrity spoofing in the ROM have been removed already. All reports regarding certification failing will be ignored
• Switched to Yuki kernel oss
• kernel is now compiled with yuki clang 21 optimized by klozz
• Has the visual bug of negative battery percentage been fixed?
• The entire tree has been overrun. performance has been optimized and improved, such as micro lag.
• New thermal system
• Override doze mode support
• Remove wifilearner HIDL entry from manifest
• and other internal changes
• Add support for spatial audio
• Xiaomi camera Support
• Dolby audio by default
• KSU Support
CLEAN FLASH MANDATORY
Credits:Here
By@Jezzay97 | Donate
Follow@xiaomi_12tpro_updates
Join@xiaomi12tpro_chat
#EvolutionX#UNOFFICIAL#A15#diting
EvolutionX 10.6 | UNOFFICIAL | Android 15
Updated: 31/5/2025
▪️Download: Gdrive | Mirror
▪️Screenshots
▪️Support
Changelogs:
• Sync last source from evox
• sepolicy: Allow fingerprint hal to read system dmabuf device
• switch to common AIDL IR service
• HBM removed and display saturation
• And other minor changes
• Rebase Xiaomi Parts
• Xiaomi camera Support
• KSU Support
Credits:
@TeamMEX_XDA
@ArianK16a
@Omar99A
By@Jezzay97 | Donate
Follow@xiaomi_12tpro_updates
Join@xiaomi12tpro_chat
#EvolutionX#UNOFFICIAL#A15#diting
EvolutionX 10.3.1 | UNOFFICIAL | Android 15
Updated: 20/3/2025
▪️Download: here
▪️Screenshots
▪️KSU
Changelogs:
• Added FEAS support
• Fingerprint fixes, not sure if this fixes fingerprint issues for some users.
• March security patch updated
• Sync last source
• Integrity passed
Notes:
• QPR2 is not yet ready by the evolution working group. So we still have to wait.
Credits:
Thanks to @Mohammadnt96 and @TeamMEX_XDA
By@Jezzay97 | Donate
Follow@xiaomi_12tpro_updates
Join@xiaomi12tpro_chat
#EvolutionX#UNOFFICIAL#A15#diting
EvolutionX 10.3 | UNOFFICIAL | Android 15
Updated: 6/3/2025
▪️Download: here
▪️Screenshots
Changelogs:
• March patches are now available in Google source. However, it seems this is A15 QPR2 with all the changes made. We will be waiting for LineageOS this time before merging anything as it's sure to break a lot of the current code we have.
Credits:
Thanks to @Mohammadnt96 and @TeamMEX_XDA
By@Jezzay97 | Donate
Follow@xiaomi_12tpro_updates
Join@xiaomi12tpro_chat