• apfelwoiSchoppen@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    We need hardware requirements so that not just pixel phones can get grapheneOS. Giving into Google hardware to escape Google software is a step I don’t want to take. I’ll take calyxOS or disvestOS until then.

    • FutileRecipe@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      We need hardware requirements so that not just pixel phones can get grapheneOS.

      GOS has strict hardware requirements to increase security that currently only Pixels meet. They won’t, and shouldn’t, compromise their standards which would give you a weaker OS. Want GOS on other vendors? Convince those vendors to up their hardware game.

    • EngineerGaming@feddit.nl
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      My main issue with Pixels is their price, even the Pixel A. They are completely unaffordable new, and only hit below $300 when they barely have any support yet (or are used). I don’t mind using an EOL phome because with short support like on phones it is unavoidable, but that would be after alreafdy overpaying.

      • iiGxC@slrpnk.net
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        I would only buy a used one anyways. Even when they’re pretty new you can get good deals on swappa, even for new in box ones

      • orclev@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        Honestly the short 5 year from original release till EOL thing really fucking annoys me, but it’s literally every phone on the market. I’ve looked, it’s impossible to find a phone that doesn’t force you to replace it every few years unless you go to a plain dumb phone that only supports voice calls and maybe basic SMS with no apps. That’s just a nonstarter in this day and age.

        Even alternative Android firmware like GrapheneOS and /e/OS are dependent on the stock firmware releases by the phone manufacturer so when the manufacturer goes EOL and stops releasing updates your alternative installs also are effectively EOL.

        The only solution to this problem I’ve seen that seems like it has a chance is Linux Phone OS, but it still has several problems that make it unusable for most people (biggest one probably being that it provides absolutely terrible battery life).

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      7 months ago

      Requirements exist. It’s just that device manufacturers don’t seem to care.

      I think it’s more reasonable to look at Linux phones than GrapheneOS supporting anything beyond Pixels. I was hoping to get a Linux phone this time around, but they just don’t support the basic features well enough. Hopefully my next phone will be a Linux phone, but we’ll see.

      Giving into Google hardware to escape Google software is a step I don’t want to take

      Yeah, it’s annoying. However, it’s important to note that Google is generally really good about security, so it’s not a surprise that their phones have a lot of cool security features.

      I also didn’t want to give Google money, so I bought a used Pixel and saved a ton of money. I got a Pixel 8 in like-new condition for <$400 on eBay after a big discount from an eBay sale, and I can expect 6+ years of updates (not just security updates, but OS updates). I’m really enjoying GrapheneOS so far. I guess I tangentially helped them, but at least my dollars_ didn’t go to Google.

      That said, CalyxOS and DivestOS are also fine projects, and I seriously considered using them instead.