Google says AOSP not being ‘discontinued’ even if Pixel change impacting custom ROMs

Google withheld the release of the Pixel device trees and hardware repositories, which are crucial for makers of custom ROMs, when Android 16 was released earlier this week. Some began to speculate that “AOSP is being discontinued” as a result of this. Despite Google’s denials, the Pixel modification appears to be deliberate.

Google made the source code for Android 16 available to the Android Open Source Project on Tuesday. In a significant departure from previous releases, the Pixel device trees and other code that were utilized to modify the AOSP release to fit particular (made by) Google hardware were not made available.

Custom Android ROMs will struggle to produce their OS updates without the Pixel hardware repos, which contain the device trees, driver binaries, and other components. Security (vulnerability) researchers may also be affected by this.

As a result, some community members conjectured that AOSP was being phased out. Seang Chau, the vice president and general manager of Android, said on Wednesday night that “AOSP is NOT going away” in general. Google has stated that it will continue to be “dedicated to AOSP updates,” speaking directly to developers.

The Android team’s statement does appear to indicate that Pixel device trees will no longer be available. A “reference target” that is “independent of any particular hardware, even those from Google” is what AOSP hopes to provide in the future.

You May Like

Google Tensor G6 powers Pixel 11 with faster AI and 4K Portrait Video

Google Pixel HiLight brings call and Gemini alerts to Pro models

Made by Google 2026: Pixel 11, Pixel Watch 5, and Pixel Tag Fully Detailed

AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Google. For years, developers have been building Cuttlefish (available on GitHub as the reference device for the project) and GSI targets from source. We continue to make those available for testing and development purposes.

Once more, Google is “dedicated to AOSP,” but the future will be more difficult for people who run custom ROMs.

Stay connected with the latest from Droid Tools—follow us on X @droid_tools, like our page on Facebook, check out our updates on Instagram, and follow us on Google News for real-time news, device tips, and mobile tech insights.