Google will publish Android Open Source Project code only twice annually starting in 2026, cutting releases from quarterly to biannual. The company confirmed the change through updates to official AOSP documentation this week.
AOSP source code will now drop in Q2 and Q4 each year, down from four releases that previously matched Android's quarterly platform updates. Google told Android Authority the move aligns with its "trunk-stable development model" to ensure platform stability.
The change affects how developers access Android's core codebase. Google recommends shifting from the frequently changing aosp-main branch to android-latest-release, which always points to the most recent stable version pushed to AOSP.
Custom ROM communities face the most immediate impact. Projects like LineageOS and GrapheneOS rely on timely AOSP access to port security patches and features to older devices. With only two releases annually, these groups may face longer waits for critical code.
Device manufacturers receive different treatment. Samsung, as a top-tier Android partner, gets early, private access to Android platform code directly from Google, according to SammyGuru. Their development pipelines remain unaffected by the public release schedule.
The reduction follows months of delayed AOSP releases in late 2025. Android 16's quarterly updates faced holdups, with September 2025 code not reaching AOSP for weeks after internal rollout at Google, WebProNews reported.
Security updates continue monthly through Android's security bulletins. However, AOSP integration of these patches may not sync as seamlessly with the biannual code drops, potentially creating vulnerability windows between releases.
Smaller OEMs and emerging market manufacturers could struggle most. These companies depend on AOSP for cost-effective software bases without heavy reliance on Google's proprietary services, according to industry analysts.
The move represents Google's latest step in tightening control over Android's development. Over recent years, the company has moved more components into closed-source Google Play Services and scaled back security patch releases to AOSP.
Open-source advocates express concern about reduced transparency. In an OSNews article, Thom Holwerda wrote that 'OASP is already on life support, and with this latest move Google is firmly gripping the plug,' suggesting the change brings Google closer to focusing entirely on proprietary 'Pixel Android' development.
Google maintains AOSP remains active despite the reduced release frequency. The company previously denied rumors about discontinuing the project entirely, stating "AOSP is not going away" in response to speculation last year.
The true test arrives with 2026's Q2 release. If it delivers comprehensive code with robust documentation, developers may adapt to the new rhythm. Persistent delays could trigger broader backlash across the Android ecosystem.
Android powers over three billion devices globally. Google's biannual schedule reflects a calculated trade-off between open-source accessibility and platform stability as the operating system matures into its second decade.
