![](data:image/svg+xml;charset=utf-8,<svg height="364px" width="573px" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
Google will shift all Android operating system development to its internal branch, aiming to “streamline its development” process.
This move, confirmed by Google to Android Authority, means the public Android Open Source Project (AOSP) branch will no longer be a primary development area after over 16 years.
How Android Development Works Now
AOSP, licensed under Apache 2.0, lets anyone use, modify, or distribute Android freely. Google drives most AOSP development but also runs a private internal branch for partners with Google Mobile Services (GMS) licenses.
This dual setup creates gaps—features and APIs in the internal branch, like those in the Android 16 beta, often outpace the public AOSP version. Even with trunk-based development, these differences linger.
Why Google Is Making the Change
Google noted that juggling two branches sparks frequent merge conflicts. For instance, a patch adding screen magnifier settings clashed due to differing accessibility lists, while the unlocked-only storage area API required manual syncing of internal build flags. Google said this shift aims to cut such inefficiencies and unify its workflow.
Google’s Open-Source Promise
Google emphasized its commitment to keeping Android open-source. “We will continue to publish the source code for new Android releases,” the company stated, including the Linux kernel fork under GPLv2, which mandates public availability.
What’s Changing for Source Code
The frequency of public releases for some Android components will shift. Features like the build system, update engine, Bluetooth stack, Virtualization framework, and SELinux configuration—currently built openly in AOSP—may see less frequent updates. Core OS framework work, mostly internal, will dominate, though some features will still emerge from AOSP.
What Google Expects
Google believes this move will streamline Android development, letting “developers and OEMs use a single version of Android without tracking unfinished future work just to keep up.” The focus is on efficiency and consistency.
Official Details Still Ahead
Google hasn’t shared full specifics yet. Android Authority reports an official statement is expected later this week, with Android 16’s source code due later in 2025.
