Google Halts Android Open Source Project (AOSP) and Shifts Development to Private Branches

Google has announced a major shift: beginning at the end of March 2025, Android development will be moved entirely to an internal private branch, ending real‑time public commits to the Android Open Source Project (AOSP). The continuous‑integration and code‑review platforms for AOSP are expected to be shut down, cutting off external developers from tracking progress.

While full source releases will still be published for each new Android version, incremental updates during development will no longer be made public. External developers may have to wait several months for the latest code, and the open‑source scope will be reduced to components bound by strong licenses such as the GPL (e.g., Linux kernel drivers), with many other parts becoming closed.

For major smartphone manufacturers that have signed GMS agreements, the short‑term impact is limited because they can still obtain the latest code and support through internal Google branches. However, in the long run the control of the ecosystem may become more centralized under Google, increasing dependence on its frameworks.

Individual developers and third‑party ecosystems will face significant challenges: they will lose the ability to submit code in real time and must work with delayed code versions, making adaptation to new features much harder. Third‑party ROM projects that rely on AOSP may be unable to include basic components such as dialers or messaging apps, forcing them to develop replacements from scratch.

The Android community is likely to feel a long‑term dampening effect on contributions, as the perception of Android as an open platform erodes. Some view this as a transition toward a more closed ecosystem, akin to fencing off an open garden.

From a technical and legal perspective, the GPL still requires kernel‑level components to remain open, while the Apache 2.0 license permits Google to modify and distribute AOSP code without further open‑sourcing. Historically, Android has been gradually closing source since version 4.4 in 2013, stripping core services into proprietary modules.

Industry analysts note that domestic operating systems such as Huawei’s HarmonyOS and Xiaomi’s SurgeOS, which are based on AOSP, may accelerate efforts to reduce reliance on Google’s ecosystem. This shift could reshape the global OS landscape, with Google potentially tightening hardware‑vendor constraints to boost GMS pre‑installation and advertising revenue, while manufacturers balance compliance with autonomy.

In summary, Google’s move is not a complete shutdown of Android’s source code but a privatization of its development workflow, reinforcing ecosystem control. The immediate effect on major OEMs is modest, yet the long‑term consequences could remodel the mobile operating‑system market and spur the growth of alternative open‑source solutions.

References

[1] 界面新闻: https://finance.eastmoney.com/a/202503273357974895.html

[2] 新浪财经: https://finance.sina.com.cn/tech/roll/2025-03-27/doc-ineraiqt8198171.shtml