Pixel 11 doesn't yet meet the GrapheneOS security standards and may be skipped

Original Article ↗ Hacker News Discussion ↗

Google’s latest Pixel 11 phones currently lack full support for Memory Tagging Extension (MTE), a hardware security feature GrapheneOS considers mandatory, so the project may skip supporting this generation unless Google enables it in a future Android update. Commenters debate whether relying so heavily on Google hardware is sustainable, especially as Google cuts costs, misses security updates, and allegedly restricts non-Samsung OEMs from shipping devices with GrapheneOS preinstalled, raising antitrust concerns. Many users say they will stick with older Pixels or wait for upcoming Motorola devices designed to meet GrapheneOS’s security requirements rather than upgrade to the Pixel 11.

Status of Pixel 11 and MTE

  • Original post (Aug) said Pixel 11 doesn’t meet GrapheneOS security standards because Memory Tagging Extension (MTE) is disabled in firmware and OS.
  • Later Android 17 QPR2 betas added partial firmware support, confirming some hardware MTE capability, but it’s incomplete, test-only, and can be toggled via fastboot even on locked devices.
  • Pixel 11 has also missed Android 17 QPR1 and some September 2026 security updates, leaving it behind older Pixels on patches.
  • GrapheneOS states they will not support Pixel 11 unless full, production MTE support ships and the update situation is resolved.

GrapheneOS stance and communications

  • Some commenters see the announcement as emotional, speculative about Google “cutting security to save money,” and unprofessional.
  • Others defend the project’s transparency and argue that criticism of Google and discussion of layoffs, cost cutting, and missed patches are evidence-based.
  • There is debate over whether speculating about Google’s motives is helpful or just noise.

Motorola partnership and Google’s OEM limits

  • Big side topic: Google reportedly restricts non‑Samsung OEMs from directly selling devices with GrapheneOS, only allowing it within quotas.
  • Commenters compare this to past Microsoft and Intel anti‑competitive behavior and to previous EU antitrust cases against Google.
  • Guessed workaround: OEM sells stock Android devices, a third party reflashes GrapheneOS.
  • Some expect regulators (especially in the EU) to intervene; others are pessimistic about enforcement.

Broader ecosystem and alternatives

  • Many users say they’ll skip Pixel 11 and keep or backtrack to earlier Pixels (7/8/9a/10/10a), citing small generational gains and long support windows.
  • Pixel hardware reliability is a recurring sore point (motherboard failures, pink lines, other defects); several say they are done with Pixels.
  • The upcoming Motorola devices that meet GrapheneOS’ hardware requirements generate optimism, though some worry they’ll be expensive flagships and more identifiable.

Security and MTE value

  • Discussion on whether MTE is truly crucial: some argue newer Android code is moving to memory‑safe languages and heavy pre‑release sanitizers, so MTE’s marginal benefit may be modest.
  • Others say dropping any defense‑in‑depth measure is a regression, especially while competitors like Apple and Samsung push similar features.