Fuck Google with a stiff wire brush.

    • JBrickelt963@jlai.lu
      link
      fedilink
      arrow-up
      2
      ·
      6 hours ago

      Above all, the organisation behind it must be or become sufficiently robust, like GNU/Linux, in order to take up the torch, but that requires a lot of financial backing.

      It’s not impossible, but in my opinion it won’t happen right away and is likely to take time to implement. Once that’s done, the only issue left will be installation (for users, that is).

      • Corridor8031@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        4 hours ago

        I am not really sure, but i think i have read that google and android has to split up because of cartel laws at some point,

        and i hope this might make things better (considering that like a lot of different companys do rely on android after all), but it is a fragile hope

    • LedgeDrop@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      19 hours ago

      … except for the binary os blobs, that’ll need to be reverse engineered to run it on… well… any real hardware /s

        • LedgeDrop@lemmy.zip
          link
          fedilink
          arrow-up
          2
          ·
          8 hours ago

          As far as I understood from Graphene, when Google released the source code for Android 16, they also stripped all the reference code for Pixel devices.

          Historically, Google would ship the code for Pixel and a software emulator as “reference designs”. Now, it’s only shipped with the emulator.

          The Graphene Team needed to reconstruct the pixel code from the Android 15 release. Fortunately, the divergence between Android 15 and 16 was minimal, but I’m certain the division will widen as time goes by.

          • Corridor8031@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            4 hours ago

            yeah i think i understood it like that too, but they sounded confident that this was a one time issue and that it wont really be a problem now for future releases

            but sry i am not really sure what you mean/ the connection is to the topic/ the os/ driver and firmware blobs?