Google is making it harder to build custom ROMs for Pixel phones

Affiliate links on Android Authority may earn us a commission. Learn more.

Unlike some of the best Android phones on the market, Google Pixels have traditionally given developers a clean, transparent canvas to inspect software, test early builds, and run alternative operating systems like GrapheneOS. However, a quiet shift in how Google handles Pixel source code is reportedly threatening that open reputation, and it could soon impact anyone using custom software on their phone.

According to GrapheneOS on X , Google has apparently replaced public, instant code downloads for Pixel phone drivers with a manual request form. Instead of publishing code directly to open developer platforms where anyone can grab it, Google now requires developers to fill out a Google Form and wait for someone to send them a Google Drive link.

Custom software relies on two distinct components: custom ROMs (alternative operating systems like GrapheneOS) and the low-level kernel (the code that bridges your phone’s hardware to its software).

Google is legally required under open-source licenses like GPLv2 to share the low-level kernel code. Previously, it posted kernel code as automatic updates to a public developer platform. Now, GrapheneOS says Google requires developers to manually request Pixel kernel code through a Google Form and wait weeks for a Google Drive link, all while squashing the update history into a single, hard-to-read file.

Because custom ROMs cannot function reliably without a working kernel, this change creates a major double bottleneck. Kernel developers lose visibility without a step-by-step update history to trace bug fixes. Meanwhile, custom ROM projects face multi-week delays waiting for kernel files, grinding their security patches and new Android ports to a halt.

An operating system like GrapheneOS cannot release new Android updates or security patches for Pixels until it receives the kernel source code and tests the kernel. Waiting weeks for a Drive link brings their entire pipeline to a crawl.

If you use your Pixel out of the box with standard Android, you won’t notice a difference today. Your regular software updates and security patches will still arrive directly from Google as usual. However, if you buy Pixels specifically to run custom, privacy-centric operating systems like GrapheneOS, this change hits home: