• Sonalder@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    Could you provide sources please? I think it’s “just” that the new commits aren’t public until the release is.

      • Sonalder@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        this change doesn’t mean that Android is becoming closed-source

        What will change is the frequency of public source code releases for specific Android components. Some components like the build system, update engine, Bluetooth stack, Virtualization framework, and SELinux configuration are currently AOSP-first, meaning they’re developed fully in public. Most Android components like the core OS framework are primarily developed internally, although some features, such as the unlocked-only storage area API, are still developed within AOSP.

        source code for changes will only be released when Google publishes a new branch containing those changes

        • Dyskolos@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          But what good is aosp (or graphene) still being open for, if google closes their devices (drivers i assume) off? Currently the pixels are king because of that.

          Should’ve saved the news I was referring too, now I’m not sure what exactly it was about. Hopefully just my cynical ass overreacting.

          • Sonalder@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            2 months ago

            No, the Pixels are king because they let you unlock the booloader and lock it back.

            GrapheneOS team said themselves that having pixel device trees in AOSP never was a requierment