Available now! Telegram Research 2025 β the year's key insights 
Evolution X (Official)
Open in Telegram
Based on AOSP, with your favorite customizations. #KeepEvolving π Apply for maintainership! On-Topic: @EvolutionX Off-Topic: @EvolutionXOT Updates: @EvolutionXUpdates Website: https://evolution-x.org Sources: https://github.com/Evolution-X
Show moreπ Analytical overview of Telegram channel Evolution X (Official)
Channel Evolution X (Official) (@evolutionxofficial) in the English language segment is an active participant. Currently, the community unites 22 420 subscribers, ranking 6 041 in the Technologies & Applications category and 19 382 in the India region.
π Audience metrics and dynamics
Since its creation on Π½Π΅Π²ΡΠ΄ΠΎΠΌΠΎ, the project has demonstrated rapid growth, gathering an audience of 22 420 subscribers.
According to the latest data from 19 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 56 over the last 30 days and by 4 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 20.56%. Within the first 24 hours after publication, content typically collects 9.43% reactions from the total number of subscribers.
- Post reach: On average, each post receives 4 609 views. Within the first day, a publication typically gains 2 115 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 38.
- Thematic interests: Content is focused on key topics such as branch, build, custom, lineageo, icon.
π Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
βBased on AOSP, with your favorite customizations.
#KeepEvolving
π Apply for maintainership!
On-Topic: @EvolutionX
Off-Topic: @EvolutionXOT
Updates: @EvolutionXUpdates
Website: https://evolution-x.org
Sources: https://github.com/Evolution-Xβ
Thanks to the high frequency of updates (latest data received on 20 June, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
22 420
Subscribers
+424 hours
+227 days
+5630 days
Posts Archive
22 420
We have generated private keys for use with all upcoming official releases.
Unofficial maintainers can continue to follow the LineageOS signing guide.
22 420
It's confirmed :)
Signed builds pass DEVICE integrity and we can dirty flash from unsigned to signed builds using a migration script.
22 420
Some devs via XDA have confirmed that signing builds have made their play integrity pass. Just need to verify it with some builders for now. In any case, we'll be requiring our maintainers to sign their builds from now on if this indeed is the way to pass play integrity from here.
22 420
Looks like 9to5Google made a video about Evolution X!
https://youtu.be/-XUuiGTtNmY?si=DgKZdiKu_3DvFLRq
22 420
In any case, if you guys want to test a temporary fix, try installing https://github.com/chiteroman/PlayIntegrityFix/releases/download/v15.9.9/PlayIntegrityFix_v15.9.9.zip
And let me know if it fixes issues such as RCS
22 420
Just gonna announce it right now while investigation is ongoing. Since play integrity can't be fixed just yet, 9.0 releases will not pass play integrity certification. What's possibly going to happen?
- Bank apps may not open or show rooted error
- Some apps will not show in Play store even when searching
- Google Pay/Google Wallet may show error setting up
- RCS messaging may not work
- For some really random instance, some users will not receive/initiate calls
We're really caught in a loop right now since several checks are being made. Devs have found Google checks for kernel strings that make it fail, others have tried changing userdebug to user via build.prop to make it pass. For now, we can only speculate about other checks, but it seems some LineageOS builds and AOSPA builds have passed once again by flashing chiteroman's latest module.
We will keep everyone updated.
22 420
chiteroman's module didn't help pass device integrity in the latest Evo 9.0 that was released nor did the updated pif.apk. We've made a few changes to be tested tonight and hopefully this mitigates the issue for the time being.
In any case, a pif apk update may no longer work for all current evo builds.
22 420
And Google killed the Moto Clark spoof. Seems we need to find another. PIF.apk update again once we find one.
22 420
Hi all, @aidanwarner here.
I've been brought on to help with all things PR related.
As Joey stated previously, we want to do everything we can to remain fully neutral moving forwards. If anyone has a specific issue with anything we have publicly stated moving forwards, you're welcome to message me privately and we can figure it out.
Regardless of the specific ROM were running or building, we're all a part of the Android Community.
I look forward to seeing you all around. Feel free to tag me in anything you need help with and I'll do what I can.
22 420
Good day to all. This is to call for a truce. To anyone who has had issues/beef with us in the past and would like to settle it amicably, we're open to hear you out in the group.
We will listen to what you have to say, and what adjustments/agreements can be done to further improve our relations with other members of the Android custom ROM community.
We'd like to totally move on from past issues and start anew with everyone. Consider this our apologies for past conflicts and a way to mend rifts that have occurred previously.
22 420
https://www.reddit.com/r/Android/s/4r01vKjBsF
The Elixir issue has reached Reddit
And has also reached a Google employee
https://twitter.com/SwiftOnSecurity/status/1791839908400656775
22 420
https://twitter.com/TheNotesOfJosh/status/1791627871519174697
Since this is gaining traction, might as well inform all our users.
Sorry for another unrelated announcement, but please know our team promises not to include any codes such as the one posted. We will also promise to not lock features behind subscriptions either.
This is just unethical behavior and is similar to DLCs or pay walls by mega corporations. It's no different than OEMs that have closed source codes and that's not what we're about.
Please avoid ROMs of the same nature.
22 420
Updated PIF.apk now available. Just install as a normal app. Credits to Play Integrity Fix NEXT team
22 420
We've merged May 2024 security patches into XYZ!
Initial release will be version 9.0 for all official devices and rollout starts today.
All official devices will be required to build version 9.x onwards only and Evo AOSP will be deprecated for official devices (unless allowed due to booting issues).
22 420
While Android is open source and we completely understand other ROMs adding the same features as we do, we highly discourage an almost 1:1 copy.
Our Evolution XYZ base is just a few weeks old and totally curated by Anierin and myself, but we already have a copycat in the form of FortuneOS. The dev is apparently HorizonDroid's ex co-developer.
Kindly check the recent commits in Evo XYZ, especially in frameworks_base, packages_apps_Settings, lineage-sdk, and packages_apps_Customization (compared to packages_apps_Evolver).
It's really just unfair how some "devs" do all the work and curate all the necessary things only for someone to just copy exactly how they did it and almost do nothing and yet release with their own "branding".
It's a complete rip-off of our latest work and we highly recommend to fully condemn it in public if you see any traces of it (whether in telegram or elsewhere).
22 420
May 2024 security patches (android-14.0.0_r35 tag) have been merged into our source.
Version 8.6 is called Isaw and is the latest Evo AOSP release.
Evo XYZ will have to wait until after LineageOS merges into their source.
Don't forget to support and help out!
