Android has long been celebrated for its open-source nature, primarily due to the Android Open Source Project (AOSP). This initiative has empowered developers to create their own versions of the Android operating system or custom ROMs tailored for various devices.
Shift Towards a Closed Ecosystem
However, a noticeable shift is occurring, as some developers express concerns that Android is becoming increasingly closed off. This change follows Google's decision to alter how it releases the source code for Android, particularly regarding Pixel devices. These modifications have raised alarms among custom ROM developers, including notable projects like GrapheneOS, LineageOS, and /e/OS.
The Role of AOSP
Historically, AOSP has served as the backbone for alternative Android development. Through this open-source project, developers have had the ability to access Android's source code, allowing them to either create custom operating systems or modify existing versions according to their needs. AOSP is not only a resource for independent projects but also forms the foundation for many Android smartphone manufacturers.
- Samsung utilizes AOSP for One UI
- Xiaomi has developed HyperOS
- Oppo’s operating system is based on ColorOS
- Vivo employs Funtouch OS
- Realme uses realme UI
- Nothing has created Nothing OS
Impact of Google's Recent Changes
One of the most significant changes that has caught the attention of developers is Google’s recent decision to exclude device trees and driver files (binary blobs) from the AOSP Android 16 release. Previously, these files facilitated a smoother development process for building Android systems for Pixel devices. Now, developers must compile these components independently, complicating and extending the development cycle.
Google's Assurance and Future Outlook
Despite the changes, Google has reassured the community that AOSP will continue to exist. The company states that it is not discontinuing AOSP but rather modifying the distribution of certain device components. This alteration is expected to have the most significant impact on custom ROM projects reliant on AOSP code, such as GrapheneOS, LineageOS, CalyxOS, and other privacy-focused Android distributions.
The GrapheneOS team has acknowledged their commitment to adapting their operating system to Android 16. However, they anticipate that the porting process will take longer now that they must independently establish device support that was previously provided through AOSP.
Source: https://tekno.kompas.com/read/2026/07/07/16030077/google-makin-menutup-android-pengembang-custom-rom-mulai-khawatir
