Search results for

All search results
Best daily deals

Affiliate links on Android Authority may earn us a commission. Learn more.

GrapheneOS claims Google is now waging war against it, could lock Pixel bootloader

GrapheneOS leadership claims Google is trying to wipe it out and is even threatening OEMs.
•

Nov 20, 2026 — 2:25 AM ET

•
•
grapheneos boot animation
Calvin Wankhede / Android Authority
Add Android Authority on Google:
TL;DR
  • The GrapheneOS team has claimed that Google was trying to harm the project and wipe it out.
  • Google was allegedly contacting Android OEMs to ask whether they were working with GrapheneOS, and was purportedly threatening these brands.
  • The team also suggested that Google could start locking the bootloader on Pixels and taking other actions to make Android forks unviable.

GrapheneOS is the leading Android fork if you want a secure and private smartphone experience. Pixels were the only officially supported platform, but the team is also working with Motorola to launch a Motorola Signature 27 phone with GrapheneOS. However, the developers of this software have now made some interesting claims against Google.

The GrapheneOS team claimed on X that Google was contacting Android OEMs to ask whether them whether they were working with the GrapheneOS project. Furthermore, the team asserts that Google was threatening these brands by citing Google Mobile Services licensing terms.

GrapheneOS Google threatening OEMs claim
X.com/GrapheneOS

The group also suggested that Google might eventually institute a variety of measures to thwart GrapheneOS and other Android forks:

We expect Google will begin bootloader locking Pixels, continue heavily pushing the illegal Play Integrity API and trying to make forks of AOSP non-viable. Many of their actions are clear violation of US criminal law. US antitrust law even includes prison time for individuals.

GrapheneOS leadership even said they wanted to talk to US attorney-general Todd Blanche and others in a bid to stop “Google’s escalating anti-competitive behavior.” In saying so, the team also praised Google’s engineers for directly working with the project.

“There are a lot of engineers at Google who support what we’re building and have directly worked with us,” it explained. “People there have repeatedly helped us and even explicitly added support for GrapheneOS to Google software including supporting Vanadium for Play services FIDO2 and passkeys.”

Unfortunately, the team says Google’s business division was the problem rather than its engineers:

Google’s business side is actively trying to wipe out alternatives. Google Mobile Services licensing has many illegal terms aimed at preventing competition. That isn’t enough for them. They’re very directly trying to harm GrapheneOS in multiple ways and outright wipe it out.

Either way, you won’t need to buy a Pixel phone if you’d like to use GrapheneOS. The project formed a partnership with Motorola last year, and the Signature 27 will be available as a GrapheneOS variant. Nevertheless, it would be very concerning if Google were pressuring OEMs to stop working with GrapheneOS. This apparent pressure would also come years after Google lost court battles over its agreements with OEMs. These previous agreements included terms restricting manufacturers when it came to shipping devices with Android forks.

We’ve contacted Google and Motorola for comment regarding these GrapheneOS claims. We’ll update our article as soon as the companies issue a response to us.

Conversation

Read what readers said or add your take.