• Trickster@lemm.ee
      link
      fedilink
      English
      arrow-up
      24
      ·
      22 days ago

      From GrapheneOS:

      We already had to wait until the stable tags to get the vast majority of the source code, so not much will change overall. It’s a major step in the wrong direction but without a large direct impact on us. It only reinforces that we need to obtain partner access via an OEM we can work with to help improve their platform security while also being able to port our changes earlier.

      • limerod@reddthat.comM
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        22 days ago

        I was thinking more about the additional development time and how far behind open source devs would be vs OEMs. Having all development be closed leaves a sour taste either way.

      • Markaos@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        22 days ago

        How so? I doubt many ROMs are based on code that isn’t part of an Android release. Surely GrapheneOS devs can just use the Android 16 branch once it’s released to make an Android 16 version of GrapheneOS.

    • catloaf@lemm.ee
      link
      fedilink
      English
      arrow-up
      6
      ·
      22 days ago

      I don’t think it’ll change. Google will still be releasing source snapshots for each release.

      • deafboy@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        22 days ago

        Well, this is exactly the kind of question one asks if one wants to get lectured about multiple ways they’re wrong by the graphene developers.

        In other words, no. It isn’t :)