What the 2026 GrapheneOS Pixel 11 warning is: MTE cut explained
GrapheneOS says Pixel 11 lacks MTE, so its port stalled. It points buyers at Pixel 8–10. Below: the checkable thread, the upgrades that remain, and what Google has not confirmed.
On 29 August 2026 GrapheneOS wrote on Mastodon that a week of work produced only a partial Pixel 11 port, and that it cannot finish because ARM hardware memory tagging is missing in software, firmware, and almost certainly hardware.
The searchable story is the GrapheneOS Pixel 11 warning: the hardened Android build that has followed Pixels since the Pixel 8 era says the new phones dropped MTE. Android Authority and AndroidPure reported the thread the same weekend. Google had not published a confirmation in those reports as of 30 August.
What the official thread said — and what it did not lock
The official account wrote that it appears Google cut an important security feature to save money. That sentence is the project’s inference. Android Authority wrote that it asked whether Pixel 11 supports MTE and would update if the company answered. No public reply is in those reports as of 30 August.
How the week stacked
-
1
Google launched Pixel 11, 11 Pro, and 11 Pro XL
The company blog on 12 August 2026 introduced the trio with Tensor G6. Retail date in that post was 20 August. That launch note is not the story GrapheneOS is telling.
-
2
A week of port work hit a wall
On 29 August the project said it had a partial port and could not complete it: no ARM hardware memory tagging in software, firmware, and near certainly hardware.
-
3
People who want GrapheneOS were told to skip the 11
The same thread: Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE. The project may skip the 11 series and put effort on Motorola hardware it has already committed to.
MTE tags memory and traps out-of-bounds access
ARM Memory Tagging Extension marks allocations and faults code that reads or writes outside them. Google said in 2022 that memory-safety bugs were more than 60% of the high-severity issues it tracked — a figure Android Authority repeats in this coverage.
GrapheneOS uses MTE across the base OS; stock Pixel barely does
The project uses MTE in the kernel and every standard base-OS process, with a per-app toggle. Stock Android never turned it on by default. Android 16 Advanced Protection Mode enables it for a few processes. Losing the hardware removes the layer GrapheneOS built around.
Pixel 11 still gained other security pieces
The same Mastodon thread credits post-quantum verified boot (ML-DSA), a move from Samsung Shannon IMS to AOSP IMS, and Titan M3 for better Before First Unlock protection. The project says none of that replaces MTE after unlock (AFU).
| Claim | Checkable source | How to read it |
|---|---|---|
| No MTE in software, firmware, likely hardware | GrapheneOS Mastodon, 29 Aug 2026 | Project observation from a stalled port |
| Do not buy Pixel 11 for GrapheneOS | Same thread | Advice for GrapheneOS users, not every shopper |
| Google has not confirmed the cut | Android Authority, as of 30 Aug | No public company reply in that report |
Picking a hardened handset is not the same job as a 15-minute huddle. If you only need voice and a board in a browser tab, the wbroom homepage opens a room without an account. Privacy notes live in privacy, no account; phones as clients are in mobile browser. Limits sit on the features page. When a heavy suite is the wrong tool, see when not to use heavy meeting apps.
GrapheneOS, 29 August 2026: we strongly recommend against buying Pixel 11 devices. Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE. Pixel 11’s Titan M3 should improve BFU security for users without a strong passphrase, but losing MTE craters AFU security.
# GrapheneOS on Pixel 11 (Mastodon, 2026-08-29)
Port: partial after ~1 week; cannot complete
Missing: ARM hardware memory tagging (MTE)
Layer: software, firmware, "near certainly" hardware
Recommend: Pixel 8 / 9 / 10 (Pixel 10 cheaper + MTE)
Also on 11: ML-DSA verified boot, AOSP IMS, Titan M3
Open: Google has not confirmed MTE status in coverage through 2026-08-30Boundaries
- GrapheneOS advice is not a stock-camera review
- The thread is about whether the project can ship its hardened OS at the security level it requires. It is not a battery or camera score.
- Carrier unlock is not bootloader unlock
- AndroidPure, citing the project: Verizon-branded Pixels cannot install another OS because the bootloader stays locked. T-Mobile is described as eventually allowing it. Network-unlocked is not the same flag.
- Motive is inferred
- The “save money” line and the roughly 3.125% extra cache estimate are the project’s reasoning. No Google statement on motive appears in the 30 August reports.
Questions worth checking
Should nobody buy a Pixel 11?
No. The project is explicit: this is advice for people who intend to run GrapheneOS. Shoppers who stay on stock Android and never flash another OS sit outside that warning.
Has Google admitted there is no MTE?
Through the Android Authority piece dated around 30 August, the reports show no public company reply. The gap is GrapheneOS’s finding from its own port.
What if the order already shipped?
The project pointed at the typical Google Store 15-day return window from delivery. For a used budget they mentioned a Pixel 8a that still has most of its seven-year support. Store terms and your region still govern the return.