- GrapheneOS says Google queried OEMs about partnerships and leveraged GMS licensing terms
- The Play Integrity API is framed as the practical gate blocking banking and other apps on third-party systems
- Motorola Signature 27 was slated as the first officially GrapheneOS-supported device, now uncertain
AI CURATED HOT STORY · 11/21/2026
GrapheneOS Accuses Google of Pressuring OEMs with GMS Licensing
GrapheneOS has publicly accused Google of abusing its market power by using GMS licensing as leverage to pressure phone manufacturers not to collaborate with the open-source security-focused Android distribution. The project named Motorola's Signature 27 as a casualty, claiming Google actively asked OEMs about partnerships and threatened licensing terms. GrapheneOS also warned that Google might lock Pixel bootloaders, cutting off third-party system installation paths.
The dispute extends to the Play Integrity API, which GrapheneOS says acts as a de facto gatekeeper preventing third-party systems from running banking and other critical apps. These allegations currently come solely from GrapheneOS, and Google has not issued a formal response, leaving the facts unverified.
If true, such actions would severely undermine the viability of third-party Android systems and stifle open-source innovation. GrapheneOS plans to seek intervention from the U.S. Department of Justice, potentially triggering antitrust scrutiny and impacting fair competition in the mobile OS market.
Hourly heat curve
15 fully observed hoursThe line compares only sources observed throughout; gap hours are interpolated to keep the trend continuous.
Coverage timeline
Total 2 reports · Latest first- IT之家 · IT业界T2·62 pts
- Hacker News AIT2·58 pts
- GrapheneOS says Google is pressuring Android OEMs to isolate the project
- The team warns Pixel bootloaders could be locked, cutting off third-party ROM flashing
- The claims are one-sided for now, with no Google response and facts unverified