• eleitl@lemmy.zip
    link
    fedilink
    English
    arrow-up
    15
    ·
    5 hours ago

    But of course they would that. And it shouldn’t take too long until Google makes Android completely proprietary.

  • kepix@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    6 hours ago

    ive seen the same news on reddit and lemmy. reddit was like “omg gimme that feature, even i dont use it, it is my right”. lemmy is like “are you insane? just get a better platform, your dependency from google is going to kill you”

  • undu@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    4
    ·
    9 hours ago

    Shaming Google will only work for so long. Grapheme is is doomed to fail as long as it has a complete dependence on Google’s whims.

    Have they announced the pivot to a non-android platform? Being security-mind it is frankly bizarre they have long ignored the Google dependency as a huge risk for the project.

    • notSys@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 hour ago

      AOSP is the most secure base. GrapheneOS focus is to be the most secure OS. Not to be the best open source mobile OS or even to be FLOSS.

      Notice how they’re complaining only about things that could improve security, not general usablity fixes.

    • im_fine_sandy@nord.pub
      link
      fedilink
      English
      arrow-up
      26
      ·
      6 hours ago

      they have long ignored the Google dependency

      What a silly thing to say.

      I’m absolutely certain that no contributors, and extraordinarily few users, are ignoring the risks implied by the google dependency.

      A pixel with Graphene is the best option for a daily driver for as long as it’s viable. I expect that’s everyone’s understanding of the project.

      I don’t really see how this project can “pivot to a non-android platform”, as I imagine none of their codebase can be transferred.

      Sooner or later the project will become non-viable and we will all switch to whatever the best option is at that time.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        Sooner or later the project will become non-viable and we will all switch to whatever the best option is at that time.

        Or everybody who isn’t Google will have to collaborate on a hard fork of AOSP.

        Or some governments will have to finally break out of their oligarchic regulatory capture and step in with antitrust law.

    • asdfasdfasdf@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      5 hours ago

      I will never understand this argument. Why in gods name would it be better for them to switch to a completely different OS like Linux and essentially have to destroy the entire ecosystem and start from scratch vs just hard forking current AOSP and maintaining it themselves?

      • Swedneck@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        4 hours ago

        i mean, i think there would be a lot of merit in maintaining a minimal linux platform that’s basically just an android VM, that way it’s basically infinitely easier to port to new devices and sandboxing becomes quite ironclad.

    • Augmented1207@feddit.org
      link
      fedilink
      English
      arrow-up
      24
      ·
      9 hours ago

      Idk if i am missing someting, but what Plattform other than Android is suitable? Linux is just not there yet and people want a phone they can use easily, which graphene is and Linux is just not there yet i think

      • undu@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        19
        ·
        9 hours ago

        That’s exactly my point, there’s none and GrapheneOS are not working to create a suitable one yet.

        The time to start working on plan B is yesterday

        • MalReynolds@slrpnk.net
          link
          fedilink
          English
          arrow-up
          8
          ·
          6 hours ago

          Likely plan B is fork AOSP and crossport security fixes, such features as Google deigns to put in AOSP and so forth. They can do that at any time they choose, may as well wring as much work out of the big G as possible, later is better. Remember their focus is security, it just happens to benefit privacy as well.

          Here’s hoping they can hang on long enough that there’s a viable hardened Linux phone to take the role.

      • mmmm@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        8
        ·
        8 hours ago

        But somehow Android, which is based on Linux, somehow checks those points for them…

        The hipocrisy is too big to ignore and it’s true, with that mindset of just wanting and waiting for someone else to do the hard work for them to just add patches here and there… they’re doomed to fail.

        • yetAnotherUser@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 hour ago

          I don’t think you understand how different Android and Linux distributions truly are.

          Linux alone refers to the kernel. There are custom AOSP kernels based on the Linux LTS versions with a few extra patches but that is basically all that connects Linux to Android.

          But absolutely everything in userland is wholly diifferent in Android than with any Linux distribution out there.

          And you can’t just replicate what Android did on top of the Linux kernel without Google amounts of resources. Which GrapheneOS does not have in the slightest.

  • Jiral@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    8 hours ago

    Graphene’s problem is that its very high firmware and other requirements mean they have to stand on the shoulders of giants. Their problem is that the giant is Google.

    They would probably need huge resources to do that on their own, which is why they have to rely on the maintenance effort of some large company.

    • NokkR6@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      They announced a partnership with Motorola and said it will makes things better for them.

      • Jiral@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        4 hours ago

        Supposedly. Yet Motorola doesn’t have the reputation to be frantical about their firmware and security updating. Also, they are not at the source either, Google is. That also adds delay. We will see how the partnership with Motorola will work out in practice.

    • paraphrand@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      8 hours ago

      It’s interesting to hear it has high hardware requirements. I didn’t know that. That sounds similar to the problem that also causes planned obsolescence in phones generally.

      • Jiral@lemmy.world
        link
        fedilink
        English
        arrow-up
        19
        ·
        8 hours ago

        High requirements not as in performance but hardware security feature. But that is the easy part as far as I understand. The difficult part is the requirement of super fast and constant security patching.

  • PiraHxCx@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    1
    ·
    11 hours ago

    i bet that thing of google cutting security stuff for pixel11 was because the government complained about graphene making it unhackable

  • Pirate2377@lemmy.zip
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    3
    ·
    8 hours ago

    I feel vindicated for pivoting to Ubuntu Touch. It’s far from secure and is admittedly inferior to Android right now, but at least it has no dependence on Google. I kind of saw this coming the second they annouced closing down Android and making security fixes no longer open source