The development landscape Android has always been characterized by a certain predictability: whenever Google released a new public version of its operating system, the corresponding source code was almost simultaneously made available on the Android Open Source Project (AOSP).
This practice, which for years enabled a thriving ecosystem of parallel development, is about to undergo a transformation. If with Android 16 the first signs of change had already emerged, with the delay in publishing the QPR1 code until mid-November, Mountain View has now confirmed that this approach will no longer be the exception, but the rule.
AOSP, new semiannual cadence from 2026
Google has officially announced a change of direction regarding the management of the source code of the green robot. Starting in 2026, the tech giant will limit the release of new source code on AOSP to only two time windows per year: the second quarter (Q2) and the fourth quarter (Q4).
This decision was communicated directly to partners and confirmed to the press, marking a turning point in the distribution philosophy that has accompanied Android since its early days.
The company’s goal is to align AOSP publication with the new development model defined as “trunk-stable”.
According to official statements released by Google, this change is essential to ensure greater stability of the platform for the entire ecosystem.
In a technical note, the company explained that to build and contribute to AOSP it will be recommended to use the latest Android release rather than the generic main branch, noting that the “aosp-latest-release” branch will always refer to the latest actual release uploaded to the open-source platform.
Simplification and stability: the reasons for the change
The logic behind this move lies in Google’s desire to reduce intrinsic complexity in managing multiple code branches. The new calendar fits perfectly with the recent restructuring of Android’s release cycle itself.
As already happened with Android 16 in 2025, the company plans to launch the major version of the operating system in the second quarter of the year. While the Quarterly Platform Releases (QPR) will continue to be developed and distributed internally and on Pixel devices, the public source code will see a minor update, developer-focused, only in the fourth quarter.
This strategy, in Google’s view, should ensure that Android developers always have access to a platform version that is, first and foremost, secure and stable, avoiding fragmentation that results from maintaining development branches in real time.
It is no coincidence that this decision comes almost a year after the choice to stop real-time code commits on public AOSP branches, a move already justified by the need to improve internal efficiency.
Impact on users and the world of “modding”
It is reasonable to wonder what the practical repercussions of this new policy will be. For the average user, especially Pixel smartphone owners, the news is reassuring: nothing will change at all. Devices will continue to receive quarterly updates (Quarterly Platform Release) via OTA (Over The Air), enjoying the latest features as soon as they are ready.
The story changes drastically when looking at the other side of the coin, namely the Custom ROM community. Historic and vital projects like LineageOS, which base their existence on the free and timely availability of source code, will face non-negligible obstacles.
Since Google will no longer publish separate AOSP releases in the first and third quarters, independent developers will not be able to rapidly incorporate platform changes introduced in the mid-year QPRs.
This means that the development of custom ROMs will have to base on older versions or wait for the two annual releases, inevitably slowing the arrival of new features on devices not officially supported or more dated.
Although Google has confirmed that it will continue to upload security patch changes to the dedicated branch on a monthly cadence, thus ensuring device protection, functional innovation in the open-source world will suffer a noticeable slowdown, limiting the responsiveness of a community that has always represented the heart of Android’s freedom.
