There’s no GrapheneOS for Pixel 11 phones because Google cut a key security feature
The open‑source security‑focused ROM team announced on Mastodon that after a week of work they produced only a partial build for the Pixel 11 series. Their roadblock is the absence of hardware‑level support for ARM’s Memory Tagging Extensions, a capability that the Pixel 8, 9 and 10 phones shipped with and that GrapheneOS relies on for system‑wide memory‑safety protection. Without MTE, the ROM cannot enforce its default security model, forcing the developers to consider abandoning the Pixel 11 entirely and redirecting effort toward upcoming Motorola devices. The team also warned potential buyers that the Pixel 11’s other upgrades—post‑quantum verified boot, a switch to AOSP IMS, and the Titan M3 security chip—do not compensate for the missing MTE.
This setback reflects a broader tension between Google’s hardware roadmap and the custom‑ROM ecosystem. While Google has promoted the Pixel line as a reference platform for Android security, the decision to drop an optional but critical feature suggests a cost‑driven trade‑off that harms third‑party projects. Competing manufacturers, notably Motorola, may now gain a foothold among privacy‑conscious users if GrapheneOS can deliver a comparable experience on their hardware. Meanwhile, the Pixel 11a rumor hints that Google could re‑introduce MTE on a variant that shares more components with the Pixel 10, indicating a possible partial remedy but also underscoring the inconsistency across its own product line.
Looking ahead, the lack of MTE on the Pixel 11 could push security‑focused consumers toward older Pixels or alternative brands, shrinking the market for GrapheneOS on Google devices. Developers will watch for any official clarification from Google about MTE support and for the release of the Motorola devices that GrapheneOS plans to target. If Google later reinstates MTE on a Pixel 11a or future models, the ROM team may revisit the port, but until then the Pixel 11’s appeal to the privacy community remains severely limited.
Key Takeaways
GrapheneOS cannot complete a full ROM for Pixel 11 phones because the devices do not include ARM’s Memory Tagging Extensions.
Google appears to have removed MTE from the Pixel 11 line as a cost‑saving measure, despite its role in protecting against memory‑safety bugs that account for over 60 % of high‑severity exploits.
The GrapheneOS team is likely to abandon the Pixel 11 series and concentrate on upcoming Motorola hardware where MTE support is assured.
Consumers seeking the highest security on a custom ROM should consider Pixel 8‑10 models or wait for a potential Pixel 11a that might retain MTE.
About the Source
This analysis is based on reporting by Android Authority. Here is a short excerpt for context:
The GrapheneOS team suggests Google may have dropped this key security feature to 'save money'Read the original at Android Authority