Not from my understanding of the situation, Android Open Source Project (AOSP) is still Free, Open Source and living.
What’s changing is that now with Android 16 and following, Google removed the Pixel device trees from the AOSP. But still according to them, they never considered AOSP providing device trees as a hardware requirement.
Also according to GrapheneOS team Pixel 10 has much more significant hardware changes than the Pixel 6a through Pixel 9a.
Hmm then it was something else. Google closed part of the source or their drivers off, so aosp is stuck wherever it’s now?
There was something major that made me stop updating 🤔
fully happen inprivate. Currently, Google shares some of the work it does on the public AOSP Gerrit, but moving forward, this work will all be done inprivate.
The latter part is probably the reason for my fear. I read that aosp soon will be moribund. I mean, it would surely be time for the usual enshittification
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
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.
Not from my understanding of the situation, Android Open Source Project (AOSP) is still Free, Open Source and living.
What’s changing is that now with Android 16 and following, Google removed the Pixel device trees from the AOSP. But still according to them, they never considered AOSP providing device trees as a hardware requirement.
Also according to GrapheneOS team Pixel 10 has much more significant hardware changes than the Pixel 6a through Pixel 9a.
Hmm then it was something else. Google closed part of the source or their drivers off, so aosp is stuck wherever it’s now? There was something major that made me stop updating 🤔
Could you provide sources please? I think it’s “just” that the new commits aren’t public until the release is.
From a quick search,unverified:
https://www.androidauthority.com/google-android-development-aosp-3538503/
fully happen in private. Currently, Google shares some of the work it does on the public AOSP Gerrit, but moving forward, this work will all be done in private.The latter part is probably the reason for my fear. I read that aosp soon will be moribund. I mean, it would surely be time for the usual enshittification
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.
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