GrapheneOS openly accuses Google of pressuring OEMs to shun it ahead of its Motorola debut

GrapheneOS has accused Google of trying to stop Android phone makers from working with it. In a series of posts on its Mastodon account, the team behind the privacy-focused Android fork said Google is trying to convince OEM partners not to support GrapheneOS, or even bootloader unlocking.
According to GrapheneOS, Google has been "repeatedly reaching out to OEMs" to ask whether they are working with the project. The team claims Google then threatens those companies based on Google Mobile Services licensing terms, which it says multiple courts have found illegal. It also accuses Google of making a growing number of features and updates exclusive to Pixels; GrapheneOS expects Google to start locking the bootloaders on those phones.
The timing gives us a fair amount of context, in fact. GrapheneOS has only ever run on Pixels, but Motorola announced a long-term partnership with the project at MWC 2026 in March. The company has since confirmed the Signature 27 (read our review here) as its first phone with official GrapheneOS support.
GrapheneOS also took shots at the Play Integrity API. It says the API’s main purpose is to enforce GMS licensing by blocking hardware or operating systems that don’t license it. That can lock GrapheneOS users out of apps that rely on it (including many banking apps). The team added that EU countries are adopting Play Integrity in their own apps; talks with the European Commission led nowhere.
Back in July, the EU’s top court upheld Google’s €4.1 billion Android fine. That case covered restrictions on phone makers. GrapheneOS argues such fines haven’t changed Google’s behavior. Hence, it is now seeiking an audience with the US Justice Department.
Not everyone at Google is the problem, according to the team. It said Google’s engineers have helped the project, even adding support for its Vanadium browser to Play services passkeys. Its major complaint is with Google’s business side instead.







