Google's recent decision to replace automatic code updates for Pixel phones with a manual Google Forms request system has sparked concern among developers and enthusiasts of custom ROMs. This shift, which has reportedly caused delays of weeks instead of the usual couple of hours, is a significant departure from Google's past practices. The company has traditionally provided a clean, transparent canvas for developers to inspect software, test early builds, and run alternative operating systems like GrapheneOS. However, the new system creates a double bottleneck, hindering both kernel and custom ROM development. This change not only affects the speed of security updates for custom software but also reduces transparency, making it harder for independent security researchers to audit Google's code. The impact is particularly pronounced for Pixel owners using custom, privacy-centric operating systems like GrapheneOS, which rely on early code drops to test and port new Android updates. The situation is further complicated by Google's shift in the AOSP reference target from Pixel to a virtual device called "cuttlefish," and the subsequent reduction in the availability of device trees and driver binaries. This has led to a situation where the Pixel is no longer better than any other Android phone, and developers are left with limited reasons to choose it over other options. The GrapheneOS team has highlighted that their upcoming partnership with Motorola, which will host its own code and sidestep Google's approval process, is a direct result of these challenges. This development raises questions about the future of custom ROMs and the role of Google in fostering an open and transparent ecosystem. As the situation unfolds, it will be crucial to see how Google responds to the concerns of developers and enthusiasts, and whether it can find a way to balance its interests with the needs of the community.
