zlacker

>>tripdo+(OP)
GrapheneOS made an unforced error by exaggerating the situation. ("Boy who cried wolf"). When you're generic and obviously false in your criticism, it makes it easy for the company to counter it. "Google is killing AOSP" catches eye, but it is sooo easy for the company to counter.

What is going on is frustration. GrapheneOS has been relying on Google's good faith effort on providing binary blobs to Pixel in addition to AOSP to make their OS. Google was under no obligation to give that, and they stopped doing it for whatever reason.

To make things worse, GrapheneOS mentions legal/anti-trust blah blah blah, which means no engineer will touch / comment / help in the matter, and it gets routed to legal blackhole.

>>bitpus+v4
How is he exaggerating the situation? What is false about the criticism? Are you referring to a previous time where they cried wolf? I read through the Twitter thread and GrapheneOS seemed pretty even keeled and above board about it to me (even if that is uncharacteristic)

>>oharap+r6
Graphene's claim of "AOSP is dead" is easily verifiable.

> This also marks the availability of the source code at the Android Open Source Project (AOSP). You can examine the source code for a deeper understanding of how Android works, and our focus on compatibility means that you can leverage your app development skills in Android Studio with Jetpack Compose to create applications that thrive across the entire ecosystem.

https://android-developers.googleblog.com/2025/06/android-16...

This was posted 2 days back.

>>bitpus+q8
But you don't have any ability to run AOSP on any devices? Free as in literally unrunnable?

AOSP feels incomplete without there being some flagship way to use it.