GrapheneOS has accused Google of pressuring Android phone manufacturers not to work with the alternative operating system, alleging that Google Mobile Services licensing contracts have been used as leverage. The claims arrive as GrapheneOS prepares its first official expansion beyond Pixel devices through Motorola’s Signature 27.

In its public statements, the security- and privacy-focused project said Google has repeatedly asked manufacturers whether they were collaborating with GrapheneOS, followed by alleged contractual threats. GrapheneOS argues the issue extends beyond its own installation process to bootloader unlocking, which is required to install an alternative operating system.

The project has called for action by the US Department of Justice and alleged that some of Google’s conduct could violate US criminal antitrust law. Those are allegations from GrapheneOS, not findings by a court or regulator. No public documents have been presented to substantiate the purported recent threats, and Google has not issued a public response specifically addressing the claims.

Google engineers aren’t the problem. The business people are the problem.

GrapheneOS

GrapheneOS said Google employees have contributed to compatibility with features including passkeys and FIDO2 authentication in the Vanadium browser. Its dispute is instead aimed at what it describes as Google’s commercial efforts to prevent the project from reaching more manufacturers.

Motorola support is still pending

Motorola announced the Signature 27 on November 5 with planned GrapheneOS compatibility, following a partnership disclosed at MWC 2026. It is set to become the first Motorola handset officially prepared for the OS, but the integration remains under development and Motorola has not said when users will be able to install it.

GrapheneOS has officially supported Pixel phones until now, citing the hardware security capabilities and update mechanisms required by the project. The Signature 27 is also marketed with advanced Gemini integration, creating an unusual pairing with an operating system that does not include Google services by default. GrapheneOS allows those services to be installed separately in a sandboxed environment without their usual system privileges.

Google Mobile Services and Play Integrity sit at the center of the broader compatibility dispute. GMS is licensed separately from the Android Open Source Project, while Play Integrity lets apps assess aspects of a device and its software environment. Banking and payment apps can decline to run on alternative operating systems when they do not receive the expected verification result; GrapheneOS argues that this disadvantages independent platforms, including ones designed with strong security protections.

The accusations emerge against an established EU antitrust backdrop. On July 2, 2026, the Court of Justice of the European Union upheld a €4.125 billion fine against Google over Android-related anticompetitive practices. The C-738/22 P ruling covered contractual restrictions that hindered the development and distribution of alternative Android versions, but it does not establish that GrapheneOS’s new allegations are true.

GrapheneOS also fears that future Pixel phones could lose bootloader-unlocking support, though Google has made no announcement pointing to such a change. Tensions have already grown after GrapheneOS raised compatibility concerns about the Pixel 11 series and its lack of Memory Tagging Extension support. Whether Motorola’s pending Signature 27 release becomes a broader route for GrapheneOS beyond Pixels now depends on the rollout timetable—and on whether Google responds to the project’s allegations.

VIAcybernews.com
SOURCEgrapheneos.social
Previous articleGoogle Gemini’s Computer Use Can Operate Mac Apps in an Isolated Window
Next articleNvidia Closes Down 14% as Market Value Falls to About $3 Trillion