I know the generall guidance for private phones was Pixel with graphene OS. I was financially planing on buying a 10th gen pixel when they come out later this year to only put gos on it. However with the recent news, I am wondering if this is still the recommended best practice from this community.

I am worried that if the gos team needs to spend tonnes of ressources on maintaining basic drivers and stuff then they won’t have any time to work on the privacy and security features they are best known for.

What is your oppinion?

Also does anyone have a way to dpam feedback to google? I couldn’t finf a generall feedback form, but if they know that people aren’t buying their hardware because of this decision, they might back down. (I really fell in love with gos researching it lately so I would hate to have to switch to something like /e/ os or calyx or something)

  • sic_semper_tyrannis@lemmy.today
    link
    fedilink
    English
    arrow-up
    16
    ·
    edit-2
    5 days ago

    See if the Graphene team supports the 10 when it comes out. If it does then get that and if they don’t then get the Pixel 9 at a discounted cost and put on GOS. Then wait and see what happens with the situation.

    Calyx is okay but MicroG doesn’t work nearly as well as GOS sandboxed GPlay. eOS tends to be multiple Android versions outdated. I’d go with GOS, Calyx, Lineage, then eOS.

    • utopiah@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      5 days ago

      multiple Android versions outdated.

      What’s the pragmatic consequence of that? Are the security risk actually that great because Android architecture isn’t that secure or rather isn’t there a smaller and smaller amount of hard to execute exploit anyway that yes being up to date is always more secure yet only marginally so?

      I’m asking because I worry that always playing faster catch up with Google leave them in charge.