If you followed my recent posts, you know I have been interesting by Android custom ROMs lately.
Not only as a user, effectively modifying my main daily phone to run Android 16 (it was released six years ago and abandoned on Android 12), but also as an Android apprentice developer learning how to build and modify the system to keep targeted devices up-to-date with the latest AOSP release.
Scratching that itch, I built and publicly released multiple versions of Android for the Google Pixel 4a, 4a 5G and Pixel 5, using Evolution X (here is a summary of my latest releases).
Long story short, after supporting those devices on my spare time just for fun and learning from the community along the way for the past few months, I recently joined the project as an official maintainer.
What it means to be official maintainer
So, what does it change ?
Not much to tell the truth, but the differences are impactful.
- As a maintainer for the project, I am expected to keep the source code of my devices up-to-date (as long as technically possible) and suitable to be built on its CI/CD infrastructure,
- As a benefit of building on Evolution X servers, my releases will now be officially signed and can be pushed to devices as Over-The-Air updates, bypassing the need for a computer to do a manual update each time.
A huge leap in both developer and user experience obviously.
The path moving forward
So, what now ?
More of the same, basically.
My intent is to keep releasing updates as regularly as possible, and use the newly gained communication channels with other maintainers to stay informed of changes ahead of time and help fixing bugs.
Here goes hoping I'll still find some spare time to continue supporting my devices, keeping the process fun and improving by learning from the community.
Search for "Pixel 4a", "Pixel 4a 5G" or "Pixel 5" among Evolution X supported devices list to get my official releases.
Comments