GoKawiilCalvin Wankhede / Android Authority
TL;DR Google reportedly replaced automatic code updates for Pixel hardware with a manual Google Forms request system.
Developers report waiting weeks for Google Drive links instead of receiving instant code downloads.
The upcoming GrapheneOS-powered Motorola phones are built specifically to avoid this exact problem.
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.
What used to take a couple of hours is now taking weeks.
What actually changed? 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.
GrapheneOS on X
... continue reading