• Google has deliberately excluded Pixel device trees from Android 16, making the development of custom ROMs significantly more challenging.
• Developers are now faced with obstacles such as reverse engineering and the risk of hardware components malfunctioning on custom ROMs.
• The company's transition to using "Cuttlefish" as a main reference target might adversely affect long-term support for devices.

Custom ROMs aren't something I often consider these days when acquiring a new phone—you can find some of my views on the matter here. However, if you own a Pixel phone and were planning to keep it functional beyond its end-of-life, we have some unfavorable news for you.

Android 16 has been officially released into the Android Open Source Project (AOSP), allowing developers to explore the final Android version and adapt it for non-Pixel devices. Yet, the device trees and driver binaries for Pixel devices are missing. Seang Chau, Google's VP and GM of Android, verified that this exclusion is intentional. He noted that "AOSP requires a reference target that is adaptable, configurable, and economical – not tied to any specific hardware, including those provided by Google." He addressed rumors suggesting AOSP's discontinuation due to this change being viewed by some as an initial move towards ending it, emphasizing that the absence of Pixel device trees is deliberate.

The effective closure of Google Pixel device trees is problematic for any Pixel receiving Android 16, or at least for users interested in installing a custom ROM. Although creating a custom ROM for these Pixel devices remains feasible, the process is notably more difficult now. Developers attempting to port custom ROMs onto Pixel devices must engage in reverse engineering and "blind guessing." They will have to rely on outdated device trees and documentation, hoping they can determine how to make their software compatible with the phones' hardware.

Related ##### 5 Hidden Costs of Buying a Google Pixel

The Pixel 9a potentially provides the best value for a brand new phone. It's still a Pixel, nevertheless.

Posts 36 This introduces additional layers of complexity for custom ROM developers, transforming what was typically a straightforward task into one that could span weeks or even months. There's also a genuine concern that certain hardware components or features might remain permanently impaired on custom ROMs. Features depending on highly customized drivers, like advanced camera capabilities, may prove especially challenging to fully implement.

The company has announced its intention to shift toward utilizing a virtual device known as "Cuttlefish" as its primary reference target for AOSP development. This strategy aims to render AOSP development more independent of specific hardware configurations. Nonetheless, for individuals desiring prolonged device usability, this could spell troubling news. Fortunately, most new Pixel phones offer a minimum of seven years of updates, so although custom ROM support is currently underwhelming, your phone should continue functioning for a substantial period.

The above is the detailed content of Custom ROM Support Just Got a Lot Worse on Google Pixel Phones. For more information, please follow other related articles on the PHP Chinese website!