Google removes Pixel device trees from AOSP, making custom ROMs harder

Google omitted Pixel device trees and driver binaries from the Android 16 AOSP release, meaning developers must now reverse‑engineer hardware configs to build custom ROMs for Pixel phones【1】. This change raises the workload for projects like LineageOS and GrapheneOS and could curb the Pixel’s appeal to Android tinkers.

Shift to a virtual reference device

Google announced that the Pixel will no longer serve as the reference target for AOSP. Instead, the company will use “Cuttlefish,” a virtual Android device that runs on PCs, to provide a hardware‑agnostic reference platform【1】. The move is presented as a way to keep AOSP “flexible, configurable, and affordable” without tying it to any specific hardware【1】. While Cuttlefish simplifies testing across diverse hardware, it cannot fully replicate the quirks of real devices, making it a less precise benchmark for developers who need exact hardware details.

New bottlenecks for custom ROM developers

Custom ROMs rely on device trees—a set of configuration files that describe a phone’s hardware layout. Until now, Google supplied these trees for Pixel devices, allowing developers to pull the configurations, add customizations, and build images with minimal effort【1】. With the omission, developers must now extract the necessary information from older Pixel trees (Android 15) and guess changes month‑by‑month, a process described as “painful” by LineageOS contributor Nolen Johnson【1】.

Compounding the issue, Google has also begun squashing the kernel source commit history to a single commit, removing the incremental change log that developers previously used to track bug fixes and security patches across devices【1】. This hampers both kernel developers and ROM projects, as the kernel is a critical bridge between hardware and software.

A separate report notes that Google has replaced instant driver code downloads with a manual Google Forms request system, causing weeks‑long delays for developers seeking Pixel kernel files【3】. GrapheneOS highlighted that what once took hours now takes weeks, further slowing the custom ROM pipeline.

Broader implications for the Pixel ecosystem

Pixels have long been favored by the modding community because of their easy bootloader unlock and readily available factory images. The new restrictions place Pixels on par with other Android devices, where developers typically must build device trees from scratch and contend with limited driver access. While the hardware remains unlockable, the increased effort required to produce stable custom ROMs may deter some enthusiasts, potentially reducing the Pixel’s differentiation among power users.

What to watch

• Release of Android 16 QPR1 Beta 1 – further details on the rollout of the Cuttlefish reference target and any additional omissions.
• Response from custom ROM projects – whether LineageOS, GrapheneOS, or others adjust their development timelines or seek alternative reference devices.
• Potential expansion of anti‑rollback protection – Google may broaden rollback safeguards, which could further limit the ability to flash older builds for testing or recovery【2】.

The removal of Pixel device trees signals a strategic shift toward a more closed development model for Google’s flagship hardware, raising questions about the future of community‑driven Android innovation on the platform.