Graphene is still based on AOSP, they could probably have a workaround for that but the main issue I can see is small projects being leftover by their devs because the majority of there users runs a Google controlled Android and thus they will be forced to verify… Some will do it other probably won’t.
It that not moribund anyway? Isn’t the last android version going very closed source now and hence condemning all others based on it to die?
If not now, then soon.
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
I think well see more ppl doing custom roms and whatever android version of jailbreaking is maybe? Dissapointing tho, this will be my last android tablet.
What then, iOS?
Some Linux phone. The only thing I will probably regret is the camera on those.
What exactly is this product, though? Does it already exist?
Yes. Some do. Not tried yet, simply because the cam is always not very competitive. But my next one will be one.
https://linuxstans.com/linux-phone/
Wow, thanks! I only know the Fairphone…
I hope they all are kinda decent. But as long as my pixel works I don’t see a reason to buy a new one.
If Google strips our phones of NewPipe, etc., then yeah, that’s gonna be a problem, haha.
Yup…problems are probably coming either way. I hate enshittification 😐
Maybe graphene?
Graphene is still based on AOSP, they could probably have a workaround for that but the main issue I can see is small projects being leftover by their devs because the majority of there users runs a Google controlled Android and thus they will be forced to verify… Some will do it other probably won’t.
I am concerned…
It that not moribund anyway? Isn’t the last android version going very closed source now and hence condemning all others based on it to die? If not now, then soon.
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
I think well see more ppl doing custom roms and whatever android version of jailbreaking is maybe? Dissapointing tho, this will be my last android tablet.