Android: Google halves release cycle for AOSP source code

Starting this year, Google will only release new Android source code twice a year in the Android Open-Source Project (AOSP). This cycle aligns with the trunk-stable model introduced in mid-last year. Even with the update to Android 16 QPR1, which was released in September, Google took an unusually long time to publish the source code in AOSP – it appeared a full two months later. For custom ROM developers, this change is likely to be another hurdle in delivering timely updates.

New AOSP code only twice a year

Until now, since the inception of AOSP in 2007, Google has released the source code almost simultaneously with the release of an Android update. The AOSP code, provided under the rather permissive Apache 2.0 license, allows independent developers to compile their Android versions. Custom ROM developers such as GrapheneOS, LineageOS, or CalyxOS also rely on the AOSP code.

Starting this year, custom ROM developers will have to adapt: Google informs developers accordingly on the Android website with a banner: “Starting in 2026, we will release code in Q2 and Q4 to AOSP to support our trunk-stable development model and ensure platform stability for the ecosystem.”

This means Google is halving the number of source code releases. Previously, the company released the code with each quarterly Android version. With the reduced release cycle of twice a year, Google will in the future only provide the source code for the major Android update in the second quarter – likely Android 17 – and a smaller one in the fourth quarter, both of which will bring changes to the SDK for developers.

Google: Focus on stability

In a statement to Mishaal Rahman of Android Authority, a Google spokesperson explained that the new strategy “simplifies development, removes the complexity of managing multiple code branches, and allows them to deliver more stable and secure code to Android platform developers.”

The spokesperson further clarified that Google's commitment to AOSP remains unchanged – this was already assured by Google's Vice President and General Manager of the Android platform, Seang Chau, on X in mid-2025. The new release plan helps the company “create a more robust and secure foundation for the Android ecosystem.”

The Google spokesperson added that the process for releasing security patches will not change, and the company will continue to release security patches every month in a dedicated branch solely for security purposes for relevant operating system versions. However, it should be noted that Google switched to a so-called “Risk-Based Update System” (RBUS) a few months ago, where monthly security patches are smaller than before – only high-risk vulnerabilities are patched promptly. Other, less security-relevant vulnerabilities are now only patched quarterly.

Google has been working on a new update strategy for Android for a long time. Most recently, the company stated in December that “instead of just a single annual operating system update, more frequent releases will be provided.” This means that new Android features will appear in the future when they are ready. According to Google, the goal of the new strategy is to “drive innovation in apps and devices faster” and to offer users and developers “more stability and perfection.”

(afl)