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

Not like among the best Android phones available on the market, Google Pixels have historically given builders a clear, clear canvas to examine software program, check early builds, and run various working programs like GrapheneOS. Nonetheless, a quiet shift in how Google handles Pixel supply code is reportedly threatening that open popularity, and it may quickly impression anybody utilizing customized software program on their telephone.

In accordance with GrapheneOS on X, Google has apparently changed public, immediate code downloads for Pixel telephone drivers with a guide request kind. As an alternative of publishing code on to open developer platforms the place anybody can seize it, Google now requires builders to fill out a Google Type and wait for somebody to ship them a Google Drive hyperlink.

What used to take a few hours is now taking weeks.

What truly modified?

Customized software program depends on two distinct elements: customized ROMs (various working programs like GrapheneOS) and the low-level kernel (the code that bridges your telephone’s {hardware} to its software program).

Google is legally required underneath open-source licenses like GPLv2 to share the low-level kernel code. Beforehand, it posted kernel code as computerized updates to a public developer platform. Now, GrapheneOS says Google requires builders to manually request Pixel kernel code via a Google Type and wait weeks for a Google Drive hyperlink, all whereas squashing the replace historical past right into a single, hard-to-read file.

As a result of customized ROMs can’t operate reliably with out a working kernel, this transformation creates a significant double bottleneck. Kernel builders lose visibility with out a step-by-step replace historical past to hint bug fixes. In the meantime, customized ROM initiatives face multi-week delays ready for kernel information, grinding their safety patches and new Android ports to a halt.

An working system like GrapheneOS can’t launch new Android updates or safety patches for Pixels till it receives the kernel supply code and exams the kernel. Ready weeks for a Drive hyperlink brings their whole pipeline to a crawl.

How does this have an effect on you as a Pixel proprietor?

In case you use your Pixel out of the field with normal Android, you gained’t discover a distinction at present. Your common software program updates and safety patches will nonetheless arrive instantly from Google as typical. Nonetheless, in case you purchase Pixels particularly to run customized, privacy-centric working programs like GrapheneOS, this transformation hits house:

• Slower safety updates for customized software program: Various working programs depend on early code drops to check and port new Android updates forward of time. Multi-week delays imply your customized ROM may lag far behind normal Pixel updates.
• Much less transparency: With out a clear view of code historical past, impartial safety researchers have a tougher time auditing what Google is altering underneath the hood.
• Pixels have gotten much less developer-friendly, whereas competing manufacturers are stepping up: GrapheneOS famous that its upcoming {hardware} partnership with Motorola gained’t undergo from these delays as a result of they deal instantly with the {hardware} maker.

The GrapheneOS staff clarified that this doesn’t contact Android as an entire, and it gained’t contact Motorola’s upcoming GrapheneOS telephones both. It’s aimed squarely at Pixel. In reality, the staff claims Motorola’s long-term partnership with GrapheneOS, which ends GrapheneOS’ years-long Pixel exclusivity, exists largely as a result of Google made constructing various Android variations for Pixel so tough. Motorola will host its personal code going ahead, sidestepping Google’s approval course of fully.

Just some years in the past, Google used to go above and past, releasing not solely the GPL-mandated kernel supply code but additionally the total kernel commit historical past. In reality, Google used to go two steps past by additionally releasing system timber and driver binaries, which it was underneath no obligation to launch in any respect.

The corporate’s cause for doing so was that the Pixel was handled as a reference platform for AOSP, so builders wanted a straightforward method to construct for it. With the discharge of Android 16, Google shifted the AOSP reference target from Pixel to a digital system referred to as “cuttlefish” and subsequently stopped supplying Pixel system timber and driver binaries. And now, as GrapheneOS highlights, Google can be making it very tough to entry the kernel supply code for Pixels.

In that sense, the Pixel is not higher than another Android telephone. The one developer-focused cause to purchase a Pixel now could be that they continue to be simple to unlock the bootloader on, and their manufacturing unit photos are simply obtainable.

We’ve reached out to Google to ask why this guide course of was launched and whether or not they plan to hurry up turnaround instances for builders. We are going to replace this story as quickly as we hear again.