34
Pixel 11 doesn't yet meet the GrapheneOS security standards and may be skipped (discuss.grapheneos.org)
submitted 1 month ago by to c/graphene_os@lemmy.sdf.org
4 comments fedilink hide all child comments

all 4 comments

sorted by: hot top controversial new old
[–] 27 points 1 month ago

Old post. Latest update from GOS 2 days ago:

  • permalink
  • fedilink
  • source
    •
    [–] 8 points 1 month ago (2 children)

    Apparently it's likely that the SoC does support MTE, but that Google had disabled it in firmware at launch because of some issues and is going to re-enable it for QPR2. Who knows whether that is actually the case though

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 4 points 1 month ago (1 child)

    Is this because of the delays surrounding Android 17 in general you think?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 1 month ago

    It could be. It could also just be that the engineers had to rush to meet a deadline. Last year during the initial Pixel 10 release the pixels were using a bunch of out-of-tree patches until QPR1 (which also didn't have its source code released until December) because the initial launch was timed right with Android 16. That meant that Pixel 10s couldn't boot anything other than the stock Pixel ROM because no one else had those patches. GrapheneOS couldn't support them until that release in December happened. This could end up being something similar.

  • permalink
  • fedilink
  • source
  • parent
    • 2 comments in c/hackernews@lemmy.bestiver.se view that post
    [–] 12 points 1 month ago (1 child)

    Honestly I'm far more excited about Motorola getting Graphene so I can finally dump pixel.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •