
On 19 November 2026, the team behind GrapheneOS, the hardened, open-source Android build, publicly accused Google of working against it. "Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels," the project wrote on Mastodon, adding that Google is also "trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking."
According to Notebookcheck's account of the posts, GrapheneOS says Google has been "repeatedly reaching out to OEMs" to ask whether they work with the project, and is using the terms of its Google Mobile Services (GMS) licence against them — terms GrapheneOS says multiple courts have found illegal. These are the project's accusations; Google has not responded to them, both Notebookcheck and The Tech Outlook report.
The timing matters. GrapheneOS has only ever run on Pixel phones. Motorola announced a long-term partnership with the project at MWC in March 2026, and its Signature 27, launched globally at the start of November, is the first phone from another maker with official GrapheneOS support.
GrapheneOS also predicts that Google will start locking Pixel bootloaders, keep pushing its Play Integrity API and try to make Android forks non-viable. It says Play Integrity mainly exists to enforce GMS licensing, and it can lock GrapheneOS users out of apps that rely on it, including many banking apps. The project says Google's engineers are not the problem — "People there have repeatedly helped us and even explicitly added support for GrapheneOS to Google Software," it wrote — but its business side is. After the EU's top court upheld Google's €4.1 billion Android fine in July, GrapheneOS says it is now seeking an audience with the US Justice Department.
The thread drew more than 350 points on Hacker News within hours. Nothing has changed for Pixel owners yet: the bootloader lock is GrapheneOS's prediction, not an announced Google plan.


