• Venator@lemmy.nz
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      Sounds like they’re intentionally setting the barriers to entry too high for anyone other than Google…

        • Venator@lemmy.nz
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          24 hours ago

          Mainly just that one mean it will never be available on any other hardware…

          All the others seem like nice to haves rather than requirements to me(the first one is half required , half nice to have “…including full hardware security functionality”), but I guess I might change my mind when I get around to building a Linux phone when I have time to do that when I’m dead… 😅

          • ChickenAndRice@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            22 hours ago

            Building a linux phone: do you mean from scratch, or just installing one of the Linux phone OS’s that already exist?

            I’ve been following Ubuntu Touch for several years now and, while they have made a lot of progress, its main hurdles have the same thing in common: mobile hardware is incredibly locked down. For example, Ubuntu Touch uses proprietary Android drivers for many low level functions. Even then, there’s some features that aren’t stable across all devices, like VOLTE.

            It sucks, I really want to use Ubuntu Touch (or any of the Linux alternatives) but I can’t make phone calls or text in the US without VOLTE support. There are a few phones that support VOLTE, but the feature is either in beta, the phone is expensive, or the phone is not sold in the US.

            Anyways bringing that back to Graphene: In my case, I’m using this as a stopgap until Linux phones take off (assuming they ever do). For now I guess the best thing is to just be skeptic, keep things minimal, and bloat-free.