Comment on Help with Lineage/microG update? [OP6]
boredsquirrel@slrpnk.net 4 months ago
- No idea but why not do that?
- Updates are done OTA but may only contain diffs using the base OS. So they may be broken if you dont flash both slots. Absolutely flash both slots.
- You should wipe that phone clean, then it doesnt matter and just flash 21 directly.
Also, note that outdated phones will mostly still run an outdated and insecure kernel, and have not updatable, vulnerable firmware.
Idk Android is likely somewhat secure, but I wouldnt want to daily drive something different from a (used) Google Pixel with GrapheneOS anymore. I get updates like 4 times a month!
halm@leminal.space 4 months ago
Thanks for the advice, will definitely follow your first point. As for the rest I think I’ll wait for a response from somebody with experience with the actual ROM and/or device.
Not between major versions on LOS.
Not the ROM or device I was asking about but thanks again 🤷 I’m trying to squeeze as much life out of the phone I already have, not splurge money I don’t have on another. That said, I’m coming to terms with the fact that my next phone, one day, will likely be a Pixel.
boredsquirrel@slrpnk.net 4 months ago
Doesnt matter. Android does updates by downloading the diff between the current version and the next. This goes into the other slot. If in the other slot you have some extremely outdated version this will likely break so absolutely flash both.
LineageOS has some advantages like way better stock AOSP apps. GrapheneOS still has the horrendous versions Google published before abandoning them, from various different Android versions.
halm@leminal.space 4 months ago
I see, that makes sense now. I’ve been snooping around the LineageOS website in the last couple of hours, and in their v21 announcement they write:
— so maybe dual slot installation is part of the package now?
boredsquirrel@slrpnk.net 4 months ago
I dont think that release message has anything to do with that
I dont know how Android does updates. The current system slot is read-only. It may be that the first system update reads from that slot and writes it to the other partition, then downloads the diffs, apply them here, then reboot.
But it may be that the signing keys have changed etc. In general, Android 10 to 14 is a huge step and this can likely cause breakages. Just please flash both slots.
From that point of the OS updatr on I have no idea what is GrapheneOS and what is AOSP.
On GrapheneOS you do a reboot, on an early boot screen your apps are updated too, I think they are in part precompiled and this is then done for the new base OS.
Then after the reboot, there are still optimizations going on in the background, if you press a button all these apps are killed to be reloaded with the new dependencies.