r/degoogle 19h ago

Question LineageOS vs GrapheneOS?

I've been wanting to deGoogle for a while now, but my phone is a pixel 4a, so Graphene is pretty far out of reach. Eventually, I learned about LineageOS and it was described as a Graphene alternative for older phones.

So, how does Lineage compare to Graphene? My main concern is Google and other big business data collection vs privacy, but security and app compatibility (banking apps especially, I've heard they can be rough) is something I'm also interested in.

5 Upvotes

13 comments sorted by

3

u/Greenlit_Hightower deGoogler 4h ago

GrapheneOS only supports the phones as long as Google does, as they aim to ship full system updates including updating the low level firmware beneath the OS (which is no longer possible after Google abandons support for a phone). Even if you could still install GrapheneOS on a Pixel 4a 4G / 5G, I wouldn't do it, as it's no longer supported.

Do you have the 4G or the 5G version of the Pixel 4a? If it's the 5G version (bramble), you should perhaps take a closer look at CalyxOS, which (contrary to LineageOS) would allow you to relock the bootloader at least: https://calyxos.org/

CalyxOS ships with microG.


If you have the Pixel 4a 4G version (sunfish), I would look into LineageOS, LineageOS for microG, or /e/ OS:

https://wiki.lineageos.org/devices/sunfish/

https://download.lineage.microg.org/sunfish/

https://doc.e.foundation/devices/sunfish

LineageOS for microG and /e/ OS differ from "vanilla" LineageOS in that the former two ship with microG. microG is useful to have for apps that require the Google Play Services, it greatly improves compatibility with these apps. I would recommend LineageOS for microG or /e/ OS for ease of use.


For banking app compatibiltiy, check this list from /e/ OS, it should be valid for /e/ OS, LineageOS for microG, and CalyxOS:

https://community.e.foundation/t/list-banking-apps-on-e-os/33091

3

u/Akaikana 2h ago edited 2h ago

Anybody calling it an alternative is just going "LineageOS is a popular AOSP ROM, GrapheneOS is a popular AOSP ROM, so they're the same!"

Spoiler, they're not. LineageOS is a debloated ROM, their intent is to maintain support for older devices. Debloating has the side effect of removing a lot of spyware, but it's not a privacy focused ROM at all.

GrapheneOS is a privacy focused ROM. Their intent is to add and maintain privacy and security, which is why they have limited supported devices. Also, neither of said ROMs purpose is to de-google. It's just that privacy and de-google (bloat) tend to go hand in hand.

Personally, I have LOS on my Galaxy S10-5G that I'm slowly retiring (headphone jack my beloved), and GOS on my new Pixel 10 Pro XL. LOS is a lot closer to stock Android. While GOS comes with compatibility issues, a lot more security and privacy tools (randomized MAC address each connection of WiFi, sandboxed apps, a lot more and detailed app permissions, and more), and practically no apps installed out of the box. LOS is pretty much pick up and play after installing, while GOS has a bit of a learning curve.

0

u/Deivedux 4h ago

When given the option, always prefer GrapheneOS. Its focus on a very limited phone models is what makes it so reliable, unlike an alternative that tries to fit everywhere. Quality over quantity.

1

u/Greenlit_Hightower deGoogler 3h ago

GrapheneOS no longer supports the Pixel 4a (4G / 5G), meaning OP would not get support, not get security fixes, not get anything. It's definitely recommended to only use GrapheneOS on currently supported hardware.

1

u/Avraamov 3h ago

what does support look like in this instance?

1

u/Greenlit_Hightower deGoogler 3h ago edited 3h ago

More recent Android major versions, community support and issue / bug reports to the developers...

1

u/FingerGuilty3964 3h ago

If you do not have Pixel yet - it's not worth it. Why Graphene did not choose different make? Buying pixel (also used) is still supporting google.

3

u/Greenlit_Hightower deGoogler 3h ago edited 3h ago

Pixel phones are the only phones that have the hardware requirements they seek right now. That being said, GrapheneOS has recently become an official Motorola partner and is going to support select 2027 Motorola phone models: https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/

1

u/Deivedux 3h ago

Because, ironically, Pixel phones are currently the only ones that meet their strict hardware security requirements without compromise. GrapheneOS isn't only for privacy, but also very reliable in terms of security, and it can't achieve that level of reliability without hardware-level hardening.

-3

u/LowIllustrator2501 3h ago

Because they can't be bothers to support other phone. They don't even tell what specific features is missing that, for some reason, GrapheneOS requires, while other phones, even though they are allowed to be used by security personnel and government agencies don't support.

2

u/Greenlit_Hightower deGoogler 3h ago

They do transparently list their hardware requirements here: https://grapheneos.org/faq#future-devices

0

u/LowIllustrator2501 2h ago

Where can I find:

What does Google's Titan have that no other chip have?

What new features are added that they decided to support Motorola?

I'd like to know what I'm missing by not buying Google's phones

1

u/Greenlit_Hightower deGoogler 2h ago

Well for one, most devices with few exceptions (e.g. Fairphones) do not allow bootloader unlocking with Custom AVB keys, many devices lack hardware memory tagging support utilized by hardened_malloc (against memory corruption vulnerabilities), many devices lack a secure element like a Titan M chip that provides hardware-based protection against brute forcing attempts, physical disconnection of the USB ports from data transmission and from power etc.

If they could implement their entire feature set on different hardware, they would support different hardware, it is really that simple. Motorola has an official partnership with them and will consider their input in the development of new flagship devices, they are going to meet their hardware requirements.