As a LineageOS user, I'd be interested in the disparity between GrapheneOS and LineageOS.

They have different goals:

GrapheneOS wants to make a FOSS Android with the security model that makes it hard for any bad party to break into the phone.

LineageOS wants to make a FOSS Android that respects user's privacy first and foremost - it implements security as best as it can but the level of security protections differs on different supported devices.

Good news is that if you have a boot passphrase, it's security is somewhat close to GrapheneOS - differing in that third parties with local access to the device can still brute-force their access whereas with GrapheneOS they can't - unless they have access to hardware level attacks.

	▲	akimbostrawman 2 hours ago \| parent [-]
		that is simply wrong. GrapheneOS is both in terms of security and privacy the best but currently only supports pixel phones. LineageOS is trying to support as many devices as possible still with lot of google connections and missing security updates. >Good news is that if you have a boot passphrase, it's security is somewhat close to GrapheneOS its not anywhere close https://grapheneos.org/features

▲

worldsavior 5 hours ago | parent | prev | next [-]

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

▲

the_biot 4 hours ago | parent | next [-]

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?

▲

fmajid 3 hours ago | parent [-]

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).

▲

joecool1029 2 hours ago | parent | next [-]

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.

▲

vbezhenar 2 hours ago | parent | prev [-]

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

	▲	fmajid 2 hours ago \| parent [-]
		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.

▲

rolandog 3 hours ago | parent | prev | next [-]

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.

▲

uneekname 4 hours ago | parent | prev [-]

This is a great resource! Thanks

▲

xxmarkuski 4 hours ago | parent | prev | next [-]

Graphene OS provides advanced security capabilities and a thorough defense-in-depth approach including a hardened supply chain. GOS aims to provide mechanisms to protect against 0day attacks. For example Celebrite can not open up GOS. GOS relys on hardware support provided by Pixels. Graphene OS works on getting their developments upstream.

For a list of security features see here [0].

[0] https://grapheneos.org/features

▲

mcsniff 4 hours ago | parent | prev | next [-]

If you care about security above all else and you have a Pixel, GrapheneOS should really be your only consideration.

LineageOS has a place for those who care less about security and more about features, "freedom", compatibility, community etc...

I was a LOS user and maintained my own forks for devices, but switching to GrapheneOS was a good decision and I don't really miss anything.

▲

subscribed 3 hours ago | parent [-]

It might be important to mention, that Lineage OS is available on a number of the devices abandoned by their original vendors, so sometimes it may be a much better solution to get a Lineage OS onto their former "flagship" which stopped getting updates 18 months after the release.

So if the bootloader can be relocked and not passing Play Integrity scam is not a problem, Lineage may be a better option. Better than nothing, that is.

	▲	Terr_ 2 hours ago \| parent [-]
		Just yesterday I took an old Motorola smartphone from 8 years ago (Android 9) and put LineageOS on it. Poof, it's transformed from unusually-glitchy e-waste to a tool someone can actually benefit from. > So if the bootloader can be relocked Their website says they recommend against that and will not support it, because of a high chance the device will get bricked. :(

▲

ForHackernews 3 hours ago | parent | prev [-]

GrapheneOS is a locked-down, security-hardened system that's good if you need absolutely maximal security (e.g. journalists, activists, folks targeted by state actors). LineageOS is a more of an open system for tinkerers who want to play outside Google's walled garden.

You can have root to control your own device on Lineage, but not Graphene.

▲

arcanemachiner 3 hours ago | parent [-]

I believe you can root GrapheneOS. It just breaks the security model, so it's not recommended to do so.

	▲	ForHackernews 3 hours ago \| parent [-]
		Ah, you're right: https://github.com/schnatterer/rooted-graphene I stand corrected. Still, as you say, less point in it since it breaks their security model.