Custom ROM enthusiasts, rejoice! After months of waiting, Google has finally released the Android 16 QPR1 source code to AOSP, breathing new life into the custom development scene. But here's where it gets controversial: Google's initial silence on a timeline and their decision to withhold Pixel device trees and driver binaries had many fearing the worst for the future of custom ROMs. Now, with the code finally available, the community can dive into the latest features, including the highly anticipated Material 3 Expressive design.
In September, Google rolled out the first Quarterly Platform Release (QPR) of Android 16, but the absence of the updated codebase on AOSP (Android Open Source Project) left developers in limbo. This, coupled with the missing device trees and driver binaries for Pixel phones, seemed to signal a potential setback for custom ROM development. While Google eventually confirmed the release of the Android 16 QPR1 source code, they remained tight-lipped about when it would actually happen. Fast forward two months, and the code is finally live on AOSP (https://android.googlesource.com/platform/build/+/refs/heads/android16-qpr1-release), thanks to a Reddit user (https://www.reddit.com/r/Android/comments/1oukr2c/android16qpr1hasbeenreleasedto_aosp/) who spotted the update.
Interestingly, Google dropped the Android 16 QPR1 source code on the same day they released the November Pixel Feature Drop (https://www.androidpolice.com/november-google-pixel-feature-drop/) for compatible devices. This raises the question: Will Google repeat the delay for Android 16 QPR2, scheduled for December? Only time will tell.
For everyday Android users, this update might not seem like a big deal. But for developers, it’s a game-changer. The source code not only allows custom ROM creators to integrate the latest features into their builds but also enables older devices running AOSP-based ROMs to experience Material 3 Expressive and Live Activities. Additionally, it gives curious developers a peek under the hood, offering insights into Google’s future OS plans.
Take LineageOS, for example. They recently released v23 of their ROM (https://www.androidpolice.com/lineageos-23-keeps-custom-rom-spirit-alive-android-16/) based on the initial Android 16 build, which lacked the OS’s most exciting features. With the QPR1 source code now available, they can update their build to include all the enhancements. Expect other popular custom ROMs to follow suit in the coming weeks, rebaselining their projects on Android 16 QPR1.
However, it’s important to note that Google’s decision to withhold Pixel device trees and driver binaries (https://www.androidpolice.com/googles-latest-aosp-move-spells-doom-for-pixel-custom-roms/) still poses challenges for custom ROM development on Pixel devices, even with the latest OS code on AOSP.
And this is the part most people miss: While Google’s move to release the source code is a win for the custom ROM community, it also highlights the ongoing tension between open-source ideals and corporate control. Should Google be more transparent about their release timelines? And what does the future hold for custom ROMs on Pixel devices? Let us know your thoughts in the comments—we’d love to hear your take on this evolving landscape.
