• lightnsfw@reddthat.com
    link
    fedilink
    arrow-up
    10
    ·
    2 days ago

    Pretty sure only pixels are, but Motorola was working on one. It’s fucking stupid that the only phone they support is manufactured by the company that is causing most of the problem. Their phone sucks too.

      • pmk@piefed.ca
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 days ago

        Next flagship Motorola will have official GrapheneOS support. It will be very expensive. After that, hopefully more mid-level Motorola phones will be supported too.

        • BrownSugarBits@lemmy.world
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          2 days ago

          OR - they could dumb down grapheneOS so that it can run on a lot of other phones ?? ? maybe? yes? I get the desire to be able to encrypt the entire drive - that IS important, but I think its more important to get the functionality of graphene provides to more people. A non-google based phone is pointless on only google based hardware.

          • TootTootComingThru@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            The point of GOS isn’t to “encrypt the entire drive” though, the whole point is a secure, private and stable platform that actually works. Their team chose Pixel phones because the hardware makes it possible to make it more secure, as in it has specific things in it that many other phones don’t have.

            Adding more supported phones would be great, but it would mean having to support that many more configurations and likely sacrificing the main features and stability as it is not a huge team and afaik they’re all volunteers.

            The whole point is security and privacy, adding whatever phone you have in your pocket for support is a) not realistically possible for them or b) would compromise the entire project due to either how many resources they have or due to the actual hardware of that particular phone.

            It’s not stupid, it’s a pretty clever group of people working on GOS. It’s not perfect but that’s what it is right now, I get that Google is an evil company but you can always buy second hand and at the end of the day there’s like maybe one less evil phone company among the many so it’s a problem with just about every phone you’re gonna buy.

          • pmk@piefed.ca
            link
            fedilink
            English
            arrow-up
            4
            ·
            2 days ago

            I would love to see GrapheneOS on Fairphone, but, you know, asking them to weaken security is a bit like asking Stallman to support proprietary software. Some people don’t compromise on their core mission. Hopefully more phones will start having secure hardware in the future. I think a lot of people value security, sustainability, and degoogling. Right now there’s no hardware where you can get all three.

            • sudoer777@lemmy.ml
              link
              fedilink
              English
              arrow-up
              4
              ·
              2 days ago

              I’m more excited for the Linux support efforts on Fairphone tbh, not a fan of Android

              • pmk@piefed.ca
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 day ago

                For degoogling it would be amazing, and postmarket/nura has been doing a lot of progress lately. As long as google is the steward of aosp and firmware is closed, all aosp based projects are kind of relying on google. For security pure linux has a long way to catch up though. And battery life. And ability to be used as a daily main device.

                • sudoer777@lemmy.ml
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  edit-2
                  1 day ago

                  For security on Linux, a lot of it is trading off how much control you have over the OS. Like with GrapheneOS you’re basically limited to the settings that it exposes, while with Linux you can do anything you want with root access. Which is better depends on the situation, but normally I’d rather have the latter. For sandboxing apps we have Flatpak although right now it’s pretty janky compared to how Android does it so it could definitely be improved, and a user-facing permissions API would be nice. SecureBlue also applies some other security hardening present on GrapheneOS.

                  For app support for me at least Linux already has most of what I want, although it lacks proprietary app support and some FOSS apps are Android-only, not sure how well Waydroid works.

                  EDIT: Now that I think about it, I think the lack of user-facing permissions toggles might be the source for most of Flatpak’s current problems. Because right now apps have to define broad permissions for themselves so that users don’t get confused when they don’t work as expected. For instance, for programs that expect to have direct write access, on Android you can pop up a file picker that grants it permanent write access to the directory you choose, but Flatpak doesn’t have this AFAIK so a lot of them will just automatically grant write access to the entire user directory.

        • sudoer777@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          The flagship Motorola also sucks, missing a bunch of features that even my $150 Samsung J3 had