GrapheneOS is preparing to move beyond its long-standing Pixel-only footing with planned support for the Motorola Signature 27. But the security-focused Android project now alleges that Google is trying to prevent that expansion by pressuring phone manufacturers through Google Mobile Services licensing arrangements.
In posts from its official account, GrapheneOS said Google has repeatedly asked manufacturers whether they were working with the project, then allegedly threatened contractual restrictions. The project also argues that the dispute concerns more than installing its operating system: it could affect whether owners can unlock a device bootloader, a necessary step for installing an alternative OS.
Why the Motorola expansion matters
The Signature 27, released November 5, is the first Motorola phone announced as officially prepared for GrapheneOS following a partnership disclosed at MWC 2026. The software integration is still in development, and Motorola has not said when GrapheneOS installation will become available. U.S. availability and pricing for the phone were not confirmed in the supplied information.
Until now, GrapheneOS has officially supported Pixel phones, which the project says met its hardware-security and update-mechanism requirements. The Motorola effort would give users of another major Android hardware brand a supported route to an operating system designed around security and privacy rather than Google’s default software stack.
That distinction is particularly notable because the Signature 27 is marketed with advanced Gemini integration. GrapheneOS can still run Google services, but installs them separately in a sandboxed environment without their usual system-level privileges.
- Google Mobile Services is licensed separately from the Android Open Source Project and provides Google’s proprietary app and service layer.
- Play Integrity lets apps evaluate aspects of a device and its software environment; banking and payment apps may decline to run on alternative operating systems when they do not receive the expected verification result.
- GrapheneOS says these mechanisms can put independent operating systems at a disadvantage, including systems that provide substantial security protections.
Claims remain unproven
GrapheneOS has called for U.S. Department of Justice intervention and characterized the alleged conduct as potentially violating U.S. criminal antitrust law. Those are allegations from the project, not findings by a court or regulator. GrapheneOS has not publicly produced documents substantiating the alleged recent threats, and there is no announced investigation based on its complaints.
Google engineers aren’t the problem. The people in the business side are the problem.
GrapheneOS
The project says Google employees have directly helped improve compatibility with capabilities including passkey and FIDO2 authentication in the Vanadium browser, while its complaint is directed at Google’s business organization. Google had not issued a specific public response to the new allegations at the time of the reporting dossier.
The dispute has some relevant legal history, though it does not establish GrapheneOS’s current claims. On July 2, 2026, the Court of Justice of the European Union upheld a €4.125 billion antitrust fine against Google over Android-related conduct, including contractual restrictions that hindered the development and distribution of alternative Android versions.
GrapheneOS also fears Google could block bootloader unlocking on future Pixel phones, although Google has made no announcement indicating that it will do so. For users considering an alternative Android build, the practical issue is whether they can retain control over the software on their hardware while keeping access to essential apps. Motorola’s pending support could broaden that choice, but its rollout timing—and the outcome of GrapheneOS’s allegations—remain unknown.
Post Footer automatically generated by Add Post Footer Plugin for wordpress.













