←back to thread

GrapheneOS is the only Android OS providing full security patches

(grapheneos.social)
751 points akyuu | 2 comments | 06 Dec 25 13:58 UTC | HN request time: 0.001s | source
Show context
nanomonkey ◴[06 Dec 25 16:46 UTC] No.46174682[source]▶
As a LineageOS user, I'd be interested in the disparity between GrapheneOS and LineageOS.
replies(7): >>46174688 #>>46174849 #>>46174856 #>>46174958 #>>46175224 #>>46176936 #>>46182713 #
worldsavior ◴[06 Dec 25 16:46 UTC] No.46174688[source]▶
https://eylenburg.github.io/android_comparison.htm
replies(3): >>46174737 #>>46175049 #>>46175520 #
the_biot ◴[06 Dec 25 17:34 UTC] No.46175049[source]▶
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?

replies(2): >>46175186 #>>46177024 #
fmajid ◴[06 Dec 25 17:52 UTC] No.46175186[source]▶
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).
replies(2): >>46175709 #>>46176101 #
1. vbezhenar ◴[06 Dec 25 19:00 UTC] No.46175709[source]▶
Do you claim that there's a place where I can find datasheets for peripheral devices for Google Pixel? Like GPU, etc.
replies(1): >>46175779 #
2. fmajid ◴[06 Dec 25 19:07 UTC] No.46175779[source]▶
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.