2
Graphene OS vs Lineage OS
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jun 2023
2 points (100.0% liked)
Lineage OS
413 readers
1 users here now
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.
founded 1 year ago
MODERATORS
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.
lineageos is NOT a Googled device.
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
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.
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