I am currently running Graphene OS and I am very happy with it, but I am not so happy with my Pixel phone. I am wanting to switch hardware that Graphene does not support.

Would I be losing many privacy & security advantages by switching to Lineage?

5 points
*

This is an old post but here are my two cents.

LineageOS supports much more devices. It’s what I personally use. It’s security very much outclassed by that of GrapheneOS. However, to be honest I don’t care all that much. I’m not a journalist or targeted person. And I, personally, like to root and “pimp out” my device with kernel mods and the like. While all this CAN be done on GrapheneOS, it sort of defeats the purpose of having GrapheneOS. It’s supposed to be a secure, locked-down fortress.

In short, if you want a super secure, de-Googled device, then GrapheneOS. But if you want a Googled device you can do a bit more with, and really make yours in every way, then LineageOS.

permalink
report
reply
2 points
*

Hi people, so weird but if anyone’s reading this, I thought there was only one comment on this post, the one by @nomadjoanne, turns out there were actually way more from two months ago, but they’re invisible from my instance (sh.itjust.works)

How could I see this one (from a lemmy.world user) but not others by users of the same instance? Anyone know of a possible explanation? Ty

permalink
report
parent
reply
2 points

I agree with all this and will add that, even though what GrapheneOS team is doing is very admirable, the very fact that LOS (and automatically Lineage4microg) runs on hundreds of devices, makes the latter way more useful to a LOT of people (meaning a lot less throwaway tech too), plus not tieing you down to a single hw vendor!

Heck, even an old enough Pixel phone that programmatically loses Graphene’s support, is still almost garanteed support from LOS for many years

In my mind LOS is 95% of the way there, microg 97%, GOS 99%? As far as android goes, they’re all great

permalink
report
parent
reply
3 points

This is why I kind of hate ARM. Amd, why on the laptop end, i have no inrention of awitching to ARM anytime soon. The inability of these SOCs to use a generic kernel is just infuriating.

permalink
report
parent
reply
2 points

lineageos is NOT a Googled device.

permalink
report
parent
reply
2 points

Both can be completely de-Googled. Privacy is equal. Graphene has a slight edge in security with hardened memory allocation.

I prefer Lineage OS so I’m not tied to a device platform. That’s just my opinion, though.

permalink
report
reply
2 points

sorry I don’t have an answer to your question, but can I ask you why are you not happy with your pixel? I’m about to buy a new smartphone and I’m considering a pixel

thanks in advance!

permalink
report
reply
1 point

There is a couple reasons, I am not a huge fan of the shape, meaning I would rather have a smaller screen, but thicker phone to allow for a bigger battery. Pixel 4 screen size was perfect in my opinion. There is also something about the square corners I don’t really like, can’t really put my finger on it, but again the Pixel 4 was great. I only upgraded because the battery was wearing out. Also with the 6a, not a great camera. Not any better than the 4. I would recommend trying Pixel 7 or waiting for the 8.

permalink
report
parent
reply
2 points

thanks!

permalink
report
parent
reply
1 point
*

I don’t know about the details, but afaik LineageOS is focused on providing (outdated) devices with up-to-date software, with privacy and security playing a minor role, while GrapheneOS is focused on privacy and security, with no longterm (3 years +) support/updates.

The article is a bit older, but imo sums up the differences between the two OSs good enough: https://pyrephone.com/de-googled-phone-comparison-e-os-vs-lineage-vs-calyx-vs-graphene/

permalink
report
reply
-2 points

Yes. In many ways

permalink
report
reply

Lineage OS

!lineage_os@lemmy.world

Create post

The community for the Lineage OS.

Rules

Do not ask for an ETA

Don’t ask for the estimate time of arrival of builds for a device. Builds will come when ready. Don’t ask about future plans, updates, developments, or news. We don’t have crystal balls, schedules, or grand strategies that dictate when or if things will happen.

Do not ask whether your device will be supported

Whether a device will supported depends on whether a maintainer or a contributor has the device and intends to bring it up. Don’t ask if builds for another device will work on your unsupported device. Don’t ask where builds for a previously supported device are. Don’t state that you’re waiting for builds for an unsupported device. Don’t ask if a supported device will be supported on a newer version. Don’t ask for support on un-supported devices.

Do not beg for VoLTE

Not all devices with LTE are VoLTE-capable.

Do not post bug reports

We have a separate bug tracker. Please see the instructions on the wiki regarding how to report bugs correctly.

Don’t ask for help with non-Lineage ROMs

This community is for LineageOS. If you have a problem with a non-LineageOS ROM, ask elsewhere. This also extends to asking for ROM suggestions.

Do not ask for features to be added

We are not accepting feature requests in this subreddit, on GitLab, or anywhere else at this time. If you have implemented a new feature we accept patches through Gerrit at http://review.lineageos.org

Don’t ask about unsupported mods

  • Magisk modifies the boot image
  • MicroG requires signature spoofing
  • Substratum modifies frameworks
  • SuperSU is not a supported root access manager
  • Xposed breaks the Android APIs

We can’t help with these things because we don’t control them and we can’t support devices with them installed because they modify the OS at a deep level and they may open security holes.

Don’t link to or discuss unofficial builds or sites

Please don’t post links to unofficial builds or unofficial news sources. If it’s not lineageos.org – it’s not official.

Community stats

  • 1

    Monthly active users

  • 13

    Posts

  • 32

    Comments

Community moderators