• sabreW4K3@lazysoci.al
    link
    fedilink
    English
    arrow-up
    54
    arrow-down
    1
    ·
    3 months ago

    I get that stockholders love Sundar Pichai, but under his leadership all I’ve seen him do is kill the Android community and now he’s about to kill the ecosystem too. He’s so shortsighted in his approach that it hurts.

  • Tetsuo@jlai.lu
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    1
    ·
    3 months ago

    Probably the beginning of the end for that open source project.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      1
      ·
      3 months ago

      Beginning of the end?

      They killed off AOSP apps and replaced then with proprietary ones. Almost the latest Android features are proprietary and Google tied.

    • sunzu2@thebrainbin.org
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      3 months ago

      Well it is end of the google doing us any favours

      Not sure if it is actually the end though… We at least got to put up some fight lol

  • Ulrich@feddit.org
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    3 months ago

    Since the title makes absolutely no sense:

    To balance AOSP’s open nature with its product development strategy, Google maintains two primary Android branches: the public AOSP branch and its internal development branch. The AOSP branch is accessible to anyone, while Google’s internal branch is restricted to companies with a Google Mobile Services (GMS) licensing agreement. While some OS components, such as Android’s Bluetooth stack, are developed publicly in the AOSP branch, most components, including the core Android OS framework, are developed privately within Google’s internal branch. Google confirmed to Android Authority that it will soon shift all Android OS development to its internal branch, a change intended to streamline its development process.

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    18
    ·
    edit-2
    3 months ago

    Donate to Lineage OS I guess

    Seriously though I think it would be nice to see more manufacturers take projects like Lineage OS seriously. Lineage OS has the organization and base to create a better ecosystem.

    • Trickster@lemm.ee
      link
      fedilink
      English
      arrow-up
      24
      ·
      3 months 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
        ·
        3 months 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
        ·
        3 months 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
      ·
      3 months 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
        ·
        3 months 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 :)