• Biskii@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      I’m planning on getting a Pixel 7 Pro soon and I’m going to immediately put GrapheneOS on it. Are there any extra precautions I need to take?

      • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.comOP
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 month ago

        Not really, just make sure that you’re getting a carrier-unlocked device, since carrier locks often also come with permanent bootloader locks. As long as you can unlock the bootloader (i.e. the OEM unlocking setting in the developer settings is NOT greyed out), everything will be fine.

      • eleitl@lemm.ee
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 month ago

        Got my Pixel 7 a a few days ago for 335 EUR, runs GrapheneOS well.

        • Biskii@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 month ago

          I can’t wait! I’ve been on a cheap prepaid phone for YEARS and it barely functions at all at this point. I’m very excited about using a custom OS again. I think my last one was cyanogen mod on a Galaxy S3 if I am remembering correctly

  • JackGreenEarth@lemm.ee
    link
    fedilink
    English
    arrow-up
    14
    ·
    1 month ago

    That ranking makes sense, GOS is the best. It’s just a shame they don’t support non Pixel phones, of the rankings doesn’t include other custom ROMs

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 month ago

      I understand the decision. It’s kind of unreasonable to expect a developer to maintain a release without access to reasonably-maintained source to work on.

      • BearOfaTime@lemm.ee
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        1 month ago

        Yep.

        But in the Real World, what’s the pragmatic difference between Graphene and a well-managed Lineage or DivestOS device, since security and privacy are both managed via layers?

        I’m genuinely not being snarky. I tried running Graphene and had issues, and their support was atrociously condescending and critical, so now I’m running DivestOS instead. I’ve run Lineage on other devices without Google.

        • henfredemars@infosec.pub
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 month ago

          I think there’s definitely security concerns which is their highest priority. If the kernel isn’t maintained, security issues aren’t getting patched. You might be able to cobble something together, but there’s going to be holes.

          I think they’re paranoid and that’s not a judgment. Rightly so if security is your first priority.

          • Kernal64@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 month ago

            According to the Graphene OS website, the main issue isn’t even that. It’s that you can’t relock the boot loader on almost any device other than a Pixel. That leaves a huge security hole on the phone, and it’s one that almost all rooted users of other phones have open, whether they realize it or not.