Android has long been celebrated for its open nature, largely thanks to the Android Open Source Project (AOSP). This initiative allows developers to create their own versions of the operating system or customize ROMs for a variety of devices. However, recent changes by Google have raised alarms among custom ROM developers, leading to fears that the platform is becoming increasingly closed off.
Shifting Dynamics in Android Development
Recent adjustments in how Google releases Android source code, particularly for Pixel devices, have sparked concern among developers of custom ROMs like GrapheneOS, LineageOS, and /e/OS. These projects rely heavily on AOSP as their foundation, which is crucial for building alternative Android systems.
The Declining Role of AOSP
AOSP serves as an open-source framework that enables developers to access Android's source code and create tailored operating systems. However, the role of AOSP in facilitating alternative Android development appears to be diminishing. This shift is particularly troubling for projects that depend on AOSP for their functionality and updates.
- GrapheneOS: Focuses on security and privacy enhancements.
- LineageOS: Aims to bring the latest Android updates to older devices.
- /e/OS: Provides an Android experience without Google services.
Aside from individual developers, AOSP is also the basis for various smartphone manufacturers’ operating systems, with companies like Samsung, Xiaomi, and Oppo tailoring AOSP to create their unique user interfaces.
Impact of Google's Changes
One significant alteration is Google’s decision to exclude device trees and driver files, known as binary blobs, from the AOSP Android 16 release. These files were previously instrumental in easing the development process for Pixel-compatible operating systems. The removal means that developers must now independently assemble these components, complicating and lengthening the development timeline.
Google's Position on AOSP
Despite these changes, Google has clarified that AOSP is not being discontinued. The company is simply modifying the manner in which certain device components are distributed, aiming to ensure the AOSP project continues. However, this new distribution method is expected to have the most profound effects on custom ROM projects that heavily rely on AOSP, such as GrapheneOS, LineageOS, and CalyxOS.
The team behind GrapheneOS has acknowledged their commitment to updating their operating system to Android 16. However, they anticipate that the porting process will be considerably more time-consuming due to the need to build device support independently, which was previously provided through AOSP.
Source: https://tekno.kompas.com/read/2026/07/07/16030077/google-makin-menutup-android-pengembang-custom-rom-mulai-khawatir
