After the fix to the fingerprint issues with cloned apps, we have now also removed a commit that was causing massive memory leaks with our Pixel Launcher.
This has already been removed from our latest source code (A16) and updates will be released to solve the issue with the memory leaks.
THANKS TO @ChrisCatto FOR FINDING AND RESOLVING THE MEMORY LEAKS.
This has already been removed from our latest source code (A16) and updates will be released to solve the issue with the memory leaks.
THANKS TO @ChrisCatto FOR FINDING AND RESOLVING THE MEMORY LEAKS.
GitHub
Fix the issue of avoiding app crashes in HWUI (Hardware UI) · Evolution-X/frameworks_base@ba62c13
During monkey testing, there is a probability that the Paint shader is released twice, leading to a crash. However, this issue cannot be reproduced through manual operations at present.
Through cod...
Through cod...
❤36🔥9🥰4⚡2👍1🤯1
Huge announcement today!
We have fully fixed the Fingerprint issues with work profiles/private space/cloned apps. Several changes were added/removed related to biometrics and as we hoped, the issue no longer occurs. FP unlocks right away even when private space has been set up.
This was the commit causing trouble since Android 15: https://github.com/Evolution-X/frameworks_base/commit/0ce66d25b8bf6cf9e68a88c140850c3c18fae900 and it has since been reverted for both A16 and A15.
This important change will be included in all upcoming updates. We thank you for being patient regarding this major issue.
We have fully fixed the Fingerprint issues with work profiles/private space/cloned apps. Several changes were added/removed related to biometrics and as we hoped, the issue no longer occurs. FP unlocks right away even when private space has been set up.
This was the commit causing trouble since Android 15: https://github.com/Evolution-X/frameworks_base/commit/0ce66d25b8bf6cf9e68a88c140850c3c18fae900 and it has since been reverted for both A16 and A15.
This important change will be included in all upcoming updates. We thank you for being patient regarding this major issue.
❤105👍23🔥15❤🔥6🥰4🤯2
FYI the latest keybox the ROM uses has been revoked so most if not all will now see failing integrity. For the upcoming builds, built-in keybox overlay has been removed. Find your own non-revoked keybox for now.
Latest releases of Evo without keybox will pass device integrity by default and no modules needed
Try using modules together like Play Integrity fix NEXT, TrickyStore and TSupport Advance to get the latest passing keybox and strong integrity again.
Latest releases of Evo without keybox will pass device integrity by default and no modules needed
Try using modules together like Play Integrity fix NEXT, TrickyStore and TSupport Advance to get the latest passing keybox and strong integrity again.
👍22❤13🤯5😱4👏1
Yes, we know about QPR1 source code release.
Yes, we will still wait for Lineage to rebase their code on it before we adapt ours.
No, we still do not allow ETAs regarding Evo based on A16 QPR1.
https://github.com/Evolution-X/manifest/commit/551f738e53bda3d969e6a0d2022d29ab4c9d47de
Yes, we will still wait for Lineage to rebase their code on it before we adapt ours.
No, we still do not allow ETAs regarding Evo based on A16 QPR1.
https://github.com/Evolution-X/manifest/commit/551f738e53bda3d969e6a0d2022d29ab4c9d47de
GitHub
Manifest for Android 16.0.0 Release 3 (BP3A.250905.014) · Evolution-X/manifest@551f738
Change-Id: I2ae05dda46125f9deac5c4868ba67188188ae564
❤43🔥19
Evolution X (Official)
Yes, we know about QPR1 source code release. Yes, we will still wait for Lineage to rebase their code on it before we adapt ours. No, we still do not allow ETAs regarding Evo based on A16 QPR1. https://github.com/Evolution-X/manifest/commit/551f738e53bda…
OH BOY! CAN'T WAIT TO SEE WHAT FEATURES QPR1 BREAKS
🔥43😁22❤5🙏2
Evolution X (Official)
Yes, we know about QPR1 source code release. Yes, we will still wait for Lineage to rebase their code on it before we adapt ours. No, we still do not allow ETAs regarding Evo based on A16 QPR1. https://github.com/Evolution-X/manifest/commit/551f738e53bda…
Who wants to see a barebones Evo QPR1 build?
❤75🔥16😱7👍5🙏3
November 2025 security patches have been merged into our Android 15 (now 10.11) branch. We'll do the same for our Android 14 branch soon.
While you're here, we're already starting work on our Android 16 QPR1 testing, by doing a barebones but still slightly LineageOS-based version of Evo X. What this means is there won't be any features but you will see some semblances of LineageOS during this phase. This branch of Evo X is not recommended for builders as of the moment.
This is more or less just to see what QPR1 has to offer by default. Stay tuned and #KeepEvolving
While you're here, we're already starting work on our Android 16 QPR1 testing, by doing a barebones but still slightly LineageOS-based version of Evo X. What this means is there won't be any features but you will see some semblances of LineageOS during this phase. This branch of Evo X is not recommended for builders as of the moment.
This is more or less just to see what QPR1 has to offer by default. Stay tuned and #KeepEvolving
❤53🔥18👍5😁2