Google has quietly replaced the public, instant download system for Pixel phone driver and kernel source code with a manual request process that forces developers to fill out a Google Form and wait weeks for access, according to GrapheneOS on X.
The change affects anyone building custom software for Pixel devices — from privacy-focused operating systems like GrapheneOS itself to popular custom ROMs like LineageOS. Where developers previously grabbed kernel code directly from public repositories, they now submit a form and wait for someone at Google to send them a Google Drive link. GrapheneOS reports the turnaround takes weeks, not hours.
Google Pixel Source Code: What Changed and Why It Matters
The new bottleneck is not just about speed. GrapheneOS says Google is also squashing the update history into a single, hard-to-read file rather than preserving the step-by-step commit records that let developers trace individual bug fixes and security patches. That makes it significantly harder to audit what changed between versions — a critical capability for security-focused projects.
This is not an isolated move. It builds on a broader pattern that began in March 2025, when Google relocated Android development to a closed internal environment. When Android 16 shipped in June 2025, it omitted device tree files for Pixel phones, driver binaries, and the complete kernel source commit history from AOSP. Google VP Seang Chau framed the shift as a philosophical one: “AOSP needs a reference target that is flexible, configurable, and affordable — independent of any particular hardware, including those from Google.”
Google has since pivoted AOSP’s reference implementation to “Cuttlefish,” a virtual device paired with generic system images — useful for app developers, but useless for anyone building software that needs to talk to actual Pixel hardware. LineageOS developer Nolen Johnson has noted that developers must now reverse-engineer Android changes using older device trees, adding weeks of work to every update cycle.
The Practical Impact for Pixel Owners
For the average Pixel user running stock Android, nothing changes immediately. But the custom ROM ecosystem is what keeps older Pixel phones alive past their official support window, provides privacy-hardened alternatives to stock Android, and serves as the proving ground for security research that benefits all Android users. Slowing that ecosystem down has real downstream costs.
GrapheneOS is already hedging. The project has announced that upcoming GrapheneOS-powered Motorola phones are being built specifically to sidestep Google’s tightening grip on Pixel source code — a notable vote of no-confidence from the project that has long treated Pixels as the gold standard for secure Android hardware.
Google has not publicly commented on the change.
Sources: GrapheneOS on X (primary), Android Authority, gHacks
