# GrapheneOS accuses Google of pressuring OEMs to restrict Android forks

> **Key takeaway:** GrapheneOS claims Google is using licensing threats and feature exclusivity to prevent hardware partners from supporting independent Android builds and bootloader unlocking.

**Published:** 2026-11-20T10:41:26+00:00 
**Source:** It&#x27;s FOSS Community News 
**Category:** distro-news 
**Canonical URL:** https://fosswire.org/news/grapheneos-accuses-google-of-pressuring-oems-to-restrict-and.html 

## Summary
The GrapheneOS project has issued a formal accusation against Google, alleging that the company is actively sabotaging independent Android distributions. According to the project, Google is pressuring Original Equipment Manufacturers (OEMs) to avoid supporting GrapheneOS and is discouraging the practice of bootloader unlocking through licensing threats.

This alleged behavior is part of a broader trend where Google is making significant Android updates and features exclusive to Pixel hardware. GrapheneOS argues that these tactics, combined with the aggressive promotion of the Play Integrity API, are designed to limit the viability of Android forks and ensure users remain within the Google-certified ecosystem.

## Technical and Regulatory Allegations
- **Feature Exclusivity:** The project cites that major Android updates, such as Android 17 QPR2, are being released exclusively to Pixel devices, leaving other hardware partners behind.
- **Bootloader Restrictions:** GrapheneOS claims Google is steering partners away from supporting unlocked bootloaders, which are a technical requirement for installing non-standard operating systems.
- **Play Integrity API:** The project identifies the Play Integrity API as a primary tool for enforcing Google certification, noting that it allows apps to detect and reject non-certified environments like GrapheneOS.
- **Hardware Attestation vs. Certification:** Rather than attempting to spoof Google certification, GrapheneOS advocates for the use of hardware attestation to verify device integrity without relying on Google's proprietary certification status.

## Why it matters
These developments pose a significant threat to the diversity of the Android ecosystem and the survival of privacy-focused forks. If bootloader unlocking is restricted and Play Integrity becomes a mandatory barrier for essential services like banking, the ability for users to run hardened, independent operating systems on mainstream hardware will be severely diminished.