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.
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.
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
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…
deleted by creator
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.
(deleted content)
Could you provide sources please? I think it’s “just” that the new commits aren’t public until the release is.
deleted by creator
(deleted content)
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