25
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Aug 2025
25 points (100.0% liked)
Android
1167 readers
2 users here now
General discussions about the entire Android ecosystem.
Related Communities:
Rules:
spoiler
0. Use common sense.
- No piracy. Period. Don't care about your beliefs.
- No gray-area or illegal exploitation such as bypassing Google FRP, permanently locked bootloader, rooting un-rootable devices, bypassing lockscreen, etc.
- No sharing APKs or related executable software. See rule 4 for more details.
- If APKs are shared, they must be done from well-known sources such as GitHub, Google Play, and F-Droid. No direct downloads or sketchy file sharing websites. This does not mean advertise your software here. Do so in the !androidapps@lemmy.ml community.
- No Android v. iPhone discussions. We also do not tolerate slander or bashing of both devices and their respective ecosystems.
- No shilling. We will call you out on it and take action. You can calmly and respectfully make suggestions, even to other devices or ecosystems like iPhone. Nothing more than that.
- No discussion/promotion of controversial or scam custom OS's or companies such as CalyxOS (Calyx Institute), PureOS (Purism), etc.
- No discussion/promotion of controversial or scam devices such as Librem (Purism), Freedom Phone, etc.
- No discussions of devices or software that deviate or mismarket themselves from Android such as PinePhone, Librem, Ubuntu Touch, etc. These are not Android devices and are not in any way related to Android.
- No custom OS promotions. Discussions about known OS's are okay such as GrapheneOS, ProtonAOSP, etc. Though these discussions would be better in !aosp@lemmy.ml.
- No politics.
These rules are subject to change at any point in time with or without user notice.
founded 4 years ago
MODERATORS
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
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