TL;DR
Google will limit public Android source drops to Q2 and Q4 starting in 2026 to match a new trunk-stable development model. The change aims to simplify branch management and improve platform stability but will slow how quickly custom ROM projects can integrate interim platform updates.
What happened
Historically Google released the Android source to AOSP at the same time as public Android launches. That pattern shifted with Android 16, when the QPR1 source did not appear until mid-November and Google moved directly to QPR2. Google has now told Android Authority that, beginning in 2026, it will only publish AOSP source twice a year: once in Q2 and once in Q4. The company says this schedule aligns with its trunk-stable approach and should reduce branch complexity while delivering a more stable platform for the ecosystem. Google recommends developers use the android-latest-release manifest branch, which will point to the most recent AOSP drop, rather than aosp-main. Major Q2 releases and smaller Q4 developer-facing updates will continue alongside Quarterly Platform Releases; security fixes will still be pushed monthly to the dedicated security branch. Regular Pixel users are expected to keep receiving QPRs on schedule, but custom ROM development faces slower integration of interim platform changes.
Why it matters
- Fewer AOSP drops means custom ROM teams receive official source code less frequently, which can delay builds and feature backports.
- Reducing branch churn is intended to improve platform stability for device makers and app developers.
- Monthly security branch updates will continue, so security patches remain available even with the new schedule.
- The shift formalizes a development cadence that prioritizes major mid-year releases and smaller year-end developer updates.
Key facts
- Google will publish Android source to AOSP only in Q2 and Q4 starting in 2026.
- Android 16 deviated from the prior pattern when its QPR1 source release arrived late and Google skipped a separate Q1 AOSP drop.
- Google cites alignment with a trunk-stable development model and a goal of improving platform stability.
- Developers are advised to use the android-latest-release manifest branch, which will reference the most recent AOSP release.
- Quarterly Platform Releases (QPRs) will continue as usual for device users.
- Security-related changes will still be pushed monthly to a dedicated security branch.
- Custom ROM projects such as LineageOS will need to base interim builds on later QPRs (example: Android 17 QPR4) due to fewer AOSP drops.
- The change follows an earlier move by Google to stop making real-time commits to public AOSP branches.
What to watch next
- How major custom ROM projects adjust release schedules and whether their update cadence slows: not confirmed in the source.
- Whether Google patches its AOSP publishing cadence in response to developer feedback: not confirmed in the source.
- Ongoing monthly security branch pushes and how they are used to backport fixes into custom builds.
Quick glossary
- AOSP: Android Open Source Project — the public repository of Android source code used by developers, device makers and custom ROM projects.
- QPR (Quarterly Platform Release): A scheduled Android update delivered quarterly that can include security fixes, platform improvements and minor feature changes.
- Trunk-stable development model: A source control approach where development focuses on a mainline (trunk) with stability-focused releases, intended to reduce the need for many long-lived branches.
- Manifest branch (android-latest-release): A repository pointer that indicates which source tree corresponds to the most recent release pushed to AOSP; recommended by Google for building and contributing.
Reader FAQ
When does the new AOSP publishing schedule start?
Google stated the twice-yearly AOSP drops will be effective in 2026.
Will Pixel users stop receiving regular updates?
No — the report says regular Pixel users will continue to receive Quarterly Platform Releases on schedule.
Will security updates continue monthly?
Yes — Google will keep pushing security-related changes monthly to a dedicated security branch.
How will custom ROM projects be affected?
They will have fewer separate AOSP drops to base builds on, which can slow integration of interim platform changes; LineageOS was cited as an example needing to use later QPR builds.
Google’s new Android source code release schedule is bad news for custom ROMs By Rajesh Pandey Published 13 minutes ago Rajesh started following the latest happenings in the world of…
Sources
Related posts
- Transform your phone into a true productivity workhorse with a USB-C hub
- Google Drive revives Material 3 Expressive visual style in Android app
- Brave refactors Rust-based adblock engine to cut browser memory use