GrapheneOS Accuses Google of Sabotaging OEM Partners Over Bootloader Unlocking
GrapheneOS says Google is making features Pixel-exclusive while pressuring OEMs to drop support for the privacy OS and bootloader unlocking. Motorola Signature 27 will be the first non-Pixel device to run GrapheneOS.

By Ryan Chua, Cloud & Enterprise Tech
, updated 3 min read
GrapheneOS, the privacy-focused open-source mobile operating system, has accused Google of sabotaging its OEM partners by making an increasing number of Android features and updates exclusive to Pixel devices while simultaneously pressuring those same partners not to support GrapheneOS or allow bootloader unlocking.
In a post on X yesterday, the GrapheneOS team wrote: "Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking. They're also trying to harm GrapheneOS directly."
The project added that Google is "actively interrogating, influencing and outright threatening OEMs to try to stop us having more options than Pixels."
Motorola partnership expands GrapheneOS beyond Pixels
The allegations come as GrapheneOS announced a partnership with Motorola. The Motorola Signature 27, announced on 6 November, will be the first Motorola device with official GrapheneOS support. GrapheneOS said more Motorola devices will follow.
Until now, GrapheneOS has only officially supported Google Pixel devices. The Motorola partnership represents the first expansion to a non-Pixel OEM, which may explain the alleged pressure from Google.
What this means for users
Bootloader unlocking is essential for installing alternative operating systems like GrapheneOS. If Google successfully pressures OEMs to disable bootloader unlocking, it would effectively prevent users from installing privacy-focused alternatives on those devices.
GrapheneOS develops substantial privacy and security improvements over stock Android, including hardened sandboxing, exploit mitigations, and a permission model that includes network and sensors permissions. The OS does not include Google Play services, though they can be installed as sandboxed apps via a compatibility layer.
Google has not publicly responded to the allegations.
Why it matters
If true, the allegations suggest Google is using its control over Android to lock in users to Pixel hardware and Google services, while actively working to prevent the emergence of privacy-focused alternatives on competing hardware. This raises competition concerns similar to those regulators have examined in other markets.
For users, the Motorola partnership means GrapheneOS will soon be available on hardware beyond Pixels, offering more choice for privacy-conscious buyers, provided OEMs resist pressure to lock down bootloaders.
Sources
- 1GrapheneOS on Xx.com