This week, many users learned that Google began rolling out Android 16. With this release, speculation arose that the Android Open Source Project (AOSP) might be discontinued. However, Google has confirmed that AOSP is not going away. Despite this reassurance, the changes related to the launch could pose challenges for custom ROM developers.

The main issue stems from Google not releasing the Pixel hardware repositories and device trees alongside the Android 16 launch. These components are critical for custom ROM developers, as they provide essential tools such as device trees and driver binaries necessary for creating updates. The lack of access to these resources has fueled concerns over the future of AOSP and its viability for custom development. Custom Android ROM developers rely heavily on Pixel hardware repositories to successfully manage their projects.

Without these resources, creating and maintaining custom ROMs could become significantly more complicated. Additionally, this situation impacts security researchers who work on vulnerabilities within the Android ecosystem. Android’s VP and GM, Seang Chau, addressed the concerns surrounding AOSP, affirming that “AOSP is NOT going away.” He also mentioned that Google remains committed to updates within the project.

However, when questioned about the availability of Pixel device trees and hardware repositories, no definitive response was provided, leaving uncertainty for the developers. Chau emphasized that AOSP requires a flexible and configurable reference target, independent of any specific hardware. While developers have built alternatives like Cuttlefish and GSI targets for ongoing testing, the absence of Pixel resources remains a pressing concern. If Google does not make these repositories available, the development of custom ROMs could dwindle, which the community hopes to avoid.