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

What it is

GrapheneOS's statement on the Pixel 11 series, published around a planned device port that was abandoned mid-development after a week of porting work, due to the absence of ARM Memory Tagging Extension (MTE) support.

How it works

GrapheneOS's security model depends on MTE being enforced OS-wide — kernel, every base OS process, and (via hardened_malloc) most user-installed apps by default, with a per-app opt-out for incompatible apps. This differs structurally from the competing approaches the summary names: Apple's Memory Integrity Enforcement only covers the kernel and "a large portion" of userspace, and neither iOS MIE nor Android 16 Advanced Protection Mode apply MTE to third-party apps unless the developer explicitly opts in — and neither OS encourages that opt-in (Apple's own docs warn developers it risks performance/stability issues). GrapheneOS instead forces the allocator-level enforcement regardless of app developer action.

flowchart TD
    MTE[Hardware MTE present] -->|Pixel 8/9/10| Full[OS-wide enforcement + per-app opt-in]
    MTE -->|Pixel 11: absent| Skip[Port abandoned]
    Full --> Apps[User apps covered by default]
    AppleMIE[Apple MIE / AAPM] -->|opt-in required, discouraged by docs| AppsOptional[User apps usually uncovered]

Preconditions / Affected

Anyone currently planning to buy or already running a Pixel 11 for GrapheneOS; Pixel 8, 9, and 10 are unaffected and retain full MTE support. The gap applies specifically to After-First-Unlock (AFU) runtime exploit protection — Titan M3 on Pixel 11 still improves Before-First-Unlock (BFU) data-extraction resistance for users without a strong passphrase, but that's a separate, narrower protection than MTE.

What to do

GrapheneOS explicitly recommends against buying Pixel 11 devices and says Pixel 10 is preferable (cheaper, similar hardware, has MTE). It states it hasn't decided whether to fully skip Pixel 11 support, and is shifting focus toward a Motorola partnership using Snapdragon 8 Elite Gen 5 hardware (claimed 40% higher single-thread, 80% higher multi-thread CPU, 100%+ higher GPU performance than Pixel 11, and MTE support). It also flags hope that the Pixel 11a (expected to use 10th-gen rather than 11th-gen internals, mirroring how the 10a used 9th-gen parts) could still ship with MTE.

Caveats

GrapheneOS states the MTE omission is "near certainly" a hardware-level limitation, not just a software/firmware gap, but does not confirm this with certainty. The Motorola pivot is prospective — no shipped device or timeline is given. The post also separately notes Pixel was dropped as an AOSP reference device in Android 16, making future Pixel support harder generally, independent of the MTE issue.