Google is pushing OEMs against GrapheneOS and bootloader unlocking

Google is accused of pressuring Android manufacturers to avoid supporting GrapheneOS and to restrict bootloader unlocking, while increasingly tying key features and services to locked‑down, Google‑controlled firmware. Commenters see this as part of a broader trend: Android becoming less open through mechanisms like Play Integrity and hardware attestation, which can lock alternative ROMs and rooted devices out of banking, AI, and other critical apps. The thread contrasts GrapheneOS with options like /e/OS, LineageOS, Fairphone, and Linux phones, and raises antitrust, security, and user‑freedom concerns, while noting emerging alternatives such as upcoming Motorola devices officially supporting GrapheneOS.

Overall reaction to Google’s behavior

  • Many commenters are unsurprised and see this as part of a broader trend of Google locking down Android (Play Integrity, attestation, GMS-based CAPTCHA, exclusive Pixel features).
  • Several say this makes them more likely to try GrapheneOS, framing Google’s actions as evidence that it is viewed as a threat, and noting a possible “Streisand effect.”
  • Others argue Google’s moves are simply business strategy in a mobile OS duopoly, not specifically about GrapheneOS.

Bootloader unlocking and device control

  • Concern that Pixels now rely on Google servers to approve bootloader unlocking and that carrier/financing constraints can silently block unlocks.
  • Some argue this has long been true in practice; others insist it has recently tightened.
  • Broader worry that OEM-controlled keys and TEEs will eventually require vendor approval for any firmware, undermining user ownership.
  • Technical discussion notes that modern devices use TrustZone/TEEs and secure elements; kernel exploits typically can’t fully bypass these.

GrapheneOS, hardware requirements, and alternatives

  • Many praise GrapheneOS for strong security/privacy, especially sandboxed Google Play (no privileged Google services).
  • Project representatives emphasize strict hardware requirements (secure element, MTE, full driver/firmware updates for ~7 years) and refuse to relax them or support GSIs, arguing that would undercut their purpose.
  • Some users criticize this as making GrapheneOS a “luxury niche” and ask for a “Graphene Lite”; others counter that people wanting broader hardware support should use LineageOS or similar.
  • Discussion of the new Motorola partnership and the flagship Signature 27; hope expressed for cheaper supported models later.

/e/OS, Fairphone, microG and security debates

  • Multiple detailed critiques claim /e/OS and Fairphone lag badly on security patches, use outdated kernels/drivers, and weaken standard Android protections.
  • microG is criticized for needing privileged access, running obfuscated Google blobs (DroidGuard), leaking data via incomplete permission checks, and offering worse app compatibility.
  • Some defend Fairphone and Chinese vendors as “lesser evils” compared to Google; others argue that poor security negates privacy gains.

Regulation, antitrust, and evidence

  • Several urge users to write to state attorneys general, EU competition authorities, and DMA teams, positioning Play Integrity and attestation as gatekeeper abuses.
  • Others are skeptical regulators care about privacy but note fines and political incentives might help.
  • A few criticize the lack of public evidence about Google pressuring OEMs, seeing the messaging as alarmist or marketing; defenders reply that OEMs can’t safely go on record, so specifics can’t be shared.