GrapheneOS not supporting Pixel 11s? (grapheneos.social)

submitted 18 hours ago by soratoyuki@piefed.zip to c/privacy@programming.dev

10 comments fedilink hide all child comments

cross-posted from: https://piefed.zip/c/privacy@lemmy.ml/p/1776518/grapheneos-not-supporting-pixel-11s

If GrapheneOS stops supporting future Pixels, and Motorola is only targeting the flagship market for their compatible phones, we're looking at truly dark days ahead.

you are viewing a single comment's thread
view the rest of the comments

[-] ZoteTheMighty@lemmy.zip 2 points 6 hours ago

Can someone translate these acronyms into human words?

[-] girsaysdoom@sh.itjust.works 5 points 5 hours ago* (last edited 5 hours ago)

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.

BFU - Before First Unlock

AFU - After First Unlock

MTE - Hardware memory tagging

Modern mobile device OS' are more resilient to attacks if they had been rebooted but haven't been logged onto yet (before first unlock). GrapheneOS leverages MTE in a way that secures the device even after the first unlock (but with the device on the lock screen). This means that while the new Pixel 11 phones improve the phone's security when it hasn't been in recent use it reduces security while it is in use.

TLDR: new phone has weaker security on lock screen

[-] GreenKnight23@lemmy.world 1 points 5 hours ago

sorry mate, I don't get it either.

this post was submitted on 29 Aug 2026

30 points (100.0% liked)

Privacy

5076 readers

154 users here now

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 3 years ago

MODERATORS

Ategon@programming.dev

danielintempesta@programming.dev