I’m so confused by this submission. It’s not a guide but a collection of notes from someone (in china) customizing a oneplus build. There’s some useful info there but only if you’re already at a point where you’re comfortable running your own compiled full vanilla builds.
There are a lot of phones missing from there though.
I don't use lineage OS myself, but I thought the same as I read the first few sections of this article. This "guide", if anything will just confuse the less tech savvy users rather than help.
wiki.lineageos.org has specific install instructions for every phone/device they support, I have no idea why you would choose to follow anything else.
just as an example, for the Nintendo switch v2(devices built after the homebrew method was patched) can be found at:
There's an install guide for almost every android capable device for the last decade on the wiki!
[deleted]
I personally had big problems doing an OTA update within LineageOS that required a factory reset afterwards. So yeah, don't do the OTA updates. Do full backups and full manual updates instead.
Title doesn't really fit, but useful info on AOSP internals nonetheless.
Any guidance on whether I should use graphene or lineage if I want a simple easy to use replacement for google captured android?
If you need to ask, probably graphene. IMHO the only downside to graphene is that they consider the user to be an attack vector and therefore eg. actively object to allowing root access, while lineage is less bothered by it. If you don't care about that, use graphene. If you do, probably go with lineage.
the only downside to graphene is that they consider the user to be an attack vector
In other words, just like Google.
Didn't lineage remove built in root years ago? That means you still need a third party root solution like magisk. Factoring that in there's not much practical difference between lineage and graphene.
I believe LOS still does userdebug builds, so you get root over adb by default. It is pretty much impossible to create a usable local backup on official no-root Graphene builds with the recommended re-locked bootloader.
I switched to Graphene with my new phone. It includes SeedVault which is unable to backup most of my apps and ADB backup works with even fewer (deprecated by Google). So only things I could sort of backup were apps that had their own config/data export options. The stupid, "we know best" restrictions from being able to copy between user profiles also made backup and restoring a PITA (upstream android stupidity, not Graphene specific) It was a few days later before I was back to where I was before having to restore stock OS to get a warranty repair (GrapheneOS does not include repair mode or some such thing that the Google service place required). If I was still on a rooted phone, it would have taken a few minutes to restore everything.
With one minor caveat[0] yes I believe neither actively includes it, but GOS devs actively denounce being able to give apps root access and at the very least I've never heard LOS devs say anything similar. While a quick web search will turn up discussions/repos/articles about installing magisk on GOS anyways, they give me the impression that it's more likely to break; in particular, GOS (understandably) wants to re-lock the bootloader and that's not going to play nice with things that (necessarily) modify the OS. So like... I think you can root GOS, but heuristically I would be much more nervous about it breaking.
That said, for a user who says "I want a simple easy to use replacement for google captured android", I don't think rooting is likely a concern, so taking the more polished GOS is probably desirable.
[0] I don't have a non-magisk LOS phone to check, but I think stock LOS includes an option in developer settings to allow root for adb. This is mostly not what people mean when they talk about root access, but it's a form of root access.
Personally I am not sure what "replacement for google captured android" means. That said, if you aren't using a pixel, you aren't using graphene. If you do have a pixel, then graphene is the way to go.
I find it easier to install, and the fact that you can run google play services in a sandbox, is a great safety blanket.
I’m so confused by this submission. It’s not a guide but a collection of notes from someone (in china) customizing a oneplus build. There’s some useful info there but only if you’re already at a point where you’re comfortable running your own compiled full vanilla builds.
Go to https://wiki.lineageos.org if you want to install and/or compile for a phone.
>Go to https://wiki.lineageos.org if you want to install and/or compile for a phone.
There are a lot of phones missing from there though.
I don't use lineage OS myself, but I thought the same as I read the first few sections of this article. This "guide", if anything will just confuse the less tech savvy users rather than help.
wiki.lineageos.org has specific install instructions for every phone/device they support, I have no idea why you would choose to follow anything else.
just as an example, for the Nintendo switch v2(devices built after the homebrew method was patched) can be found at:
https://wiki.lineageos.org/devices/nx_tab/install/variant2/
There's an install guide for almost every android capable device for the last decade on the wiki!
I personally had big problems doing an OTA update within LineageOS that required a factory reset afterwards. So yeah, don't do the OTA updates. Do full backups and full manual updates instead.
Title doesn't really fit, but useful info on AOSP internals nonetheless.
Any guidance on whether I should use graphene or lineage if I want a simple easy to use replacement for google captured android?
If you need to ask, probably graphene. IMHO the only downside to graphene is that they consider the user to be an attack vector and therefore eg. actively object to allowing root access, while lineage is less bothered by it. If you don't care about that, use graphene. If you do, probably go with lineage.
the only downside to graphene is that they consider the user to be an attack vector
In other words, just like Google.
Didn't lineage remove built in root years ago? That means you still need a third party root solution like magisk. Factoring that in there's not much practical difference between lineage and graphene.
I believe LOS still does userdebug builds, so you get root over adb by default. It is pretty much impossible to create a usable local backup on official no-root Graphene builds with the recommended re-locked bootloader.
I switched to Graphene with my new phone. It includes SeedVault which is unable to backup most of my apps and ADB backup works with even fewer (deprecated by Google). So only things I could sort of backup were apps that had their own config/data export options. The stupid, "we know best" restrictions from being able to copy between user profiles also made backup and restoring a PITA (upstream android stupidity, not Graphene specific) It was a few days later before I was back to where I was before having to restore stock OS to get a warranty repair (GrapheneOS does not include repair mode or some such thing that the Google service place required). If I was still on a rooted phone, it would have taken a few minutes to restore everything.
With one minor caveat[0] yes I believe neither actively includes it, but GOS devs actively denounce being able to give apps root access and at the very least I've never heard LOS devs say anything similar. While a quick web search will turn up discussions/repos/articles about installing magisk on GOS anyways, they give me the impression that it's more likely to break; in particular, GOS (understandably) wants to re-lock the bootloader and that's not going to play nice with things that (necessarily) modify the OS. So like... I think you can root GOS, but heuristically I would be much more nervous about it breaking.
That said, for a user who says "I want a simple easy to use replacement for google captured android", I don't think rooting is likely a concern, so taking the more polished GOS is probably desirable.
[0] I don't have a non-magisk LOS phone to check, but I think stock LOS includes an option in developer settings to allow root for adb. This is mostly not what people mean when they talk about root access, but it's a form of root access.
Personally I am not sure what "replacement for google captured android" means. That said, if you aren't using a pixel, you aren't using graphene. If you do have a pixel, then graphene is the way to go.
I find it easier to install, and the fact that you can run google play services in a sandbox, is a great safety blanket.