GrapheneOS Accuses Google of Pressuring Phone Makers to Drop It
On 19 and 20 November 2026, GrapheneOS said Google has been repeatedly contacting Android phone makers to ask whether they work with the project and to threaten them over Google Mobile Services licensing. It also expects Google to start locking Pixel bootloaders. These are GrapheneOS's own claims: no evidence was published, and the coverage so far carries no Google response.
On this page
What GrapheneOS says Google is doing
GrapheneOS, the open source Android fork built around privacy and security, used its official Mastodon account on 19 November to accuse Google of working against it. The opening post said Google is "trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking", and that it is making a growing number of features and updates exclusive to Pixels.
A follow-up a few hours later was more specific. The project said Google "has been repeatedly reaching out to OEMs to question whether they're working with us" and threatening them on the basis of Google Mobile Services (GMS) licensing terms, the agreement phone makers sign to ship the Play Store and Google's apps. GrapheneOS also said it expects Google to begin locking the bootloaders on Pixel phones, which would end the ability to install another operating system on them.
The project was careful to separate the company's staff from its strategy. It said many Google engineers support its work and have added explicit support for its Vanadium browser to passkey handling in Play services, and that the problem is the business side.
What is claim and what is confirmed
Everything above is an allegation from one party. GrapheneOS did not publish emails, contracts or the names of the phone makers it says were contacted, and Notebookcheck's report on the thread carries no response from Google. The Pixel bootloader prediction is an expectation, not an announcement: Google has said nothing of the kind publicly.
Some context is on the record. The project has only ever run on Pixels, Motorola announced a long-term partnership with it in March, and the Motorola Signature 27 has been confirmed as the first non-Pixel phone it will support. So the accusations arrive just as GrapheneOS is about to stop depending on Google's own hardware. GrapheneOS says Motorola still cannot sell phones with GrapheneOS preinstalled at scale because of GMS licensing.
This is also not a new grievance. In September the project complained that Google was holding back platform security patches and new developer interfaces from the wider Android ecosystem and was slow to answer a source code request.
The Play Integrity problem behind the complaint
The practical pain point is the Play Integrity API, the check that apps use to ask Google whether a device and its operating system are approved. GrapheneOS argues that the check's main purpose is to enforce GMS licensing by rejecting any hardware or operating system that has not licensed it, and that it locks its users out of apps that rely on it, banking apps included. It says it has built workarounds for simple cases but expects the checks to keep expanding.
The project says it raised this with the European Commission several times and nothing changed, and that the EU's fines have not altered Google's behavior. The EU's top court upheld a 4.1 billion euro Android fine against Google in July, in a case about restrictions on phone makers. GrapheneOS now wants the US Justice Department to look, and tagged the department in its posts.
Why this matters if you run AI on your own phone
Private, on-device AI rests on a simple assumption: you control the device. A phone with an unlockable bootloader lets you choose an operating system that does not report to anyone, and then run local models on top of it. If unlocking became rare, or if more everyday apps refused to run on anything except a Google-approved system, that choice would get narrower, whatever the reason behind it.
Nothing has changed for users today. Pixels still unlock, GrapheneOS still ships, and the Motorola work continues. Treat this as one side of a dispute until Google answers or a regulator asks questions. If you depend on a privacy-first phone, the thing to watch is whether the banking and identity apps you need start demanding Play Integrity.