zlacker

https://eylenburg.github.io/android_comparison.htm

>>worlds+(OP)
This is a great resource! Thanks

>>worlds+(OP)
That comparison shows "Deblobbed? Yes" for GrapheneOS. That implies they've replaced (most of) the blobs for wifi, bluetooth, 5g chips etc.

Is that actually true? It's such a big deal, and I see little to no work being done on this front.

Anyone have any idea what GrapheneOS actually deblobbed?

>>the_bi+P5
They can because they essentially support Google chipsets, which are not blobby like MediaTek or Qualcomm because Google for all its faults is still relatively open (except their recent change in release schedules is why the Pixel 10 series still only has experimental GrapheneOS support).

>>worlds+(OP)
Nice! Thanks for the link. I noticed they didn't mention MOCOR OS (for the new Nokia 3210), but then I remembered that that's not an Android version. I'll see if they can add it somewhere else.

Unrelated, but this led me to find gnuclad, which may be somewhat externally maintained and is used to create the cladogragms.

>>fmajid+28
Do you claim that there's a place where I can find datasheets for peripheral devices for Google Pixel? Like GPU, etc.

>>vbezhe+tg
No, but they used to publish the source code for the drivers as part of AOSP. Now they no longer publish the device trees. Check out GrapheneOS' other Mastodon posts for the gory details.

>>fmajid+28
Here’s an example of the radio firmware and vendor blobs required for a pixel 9 pro XL build: https://github.com/TheMuppets/proprietary_vendor_google_komo...

Nobody, including Graphene, is getting away with building their own modem firmware. The reduced blobs are on userspace and some HAL components.

>>the_bi+P5
It's nowhere near that. Pretty sure even modules are signed by Google.