mmustermann has a build he is releasing each month, won’t be compatable with the official release.
We are just waiting for some changes to be merged on lineageos’s side, then we should have an official release. ETA is between tomorrow and the end of the world.
I might be wrong but from the instructions I read here it appears it should not be that much of a big deal to update from unofficial to official… In any case, I’ll have to try it when official gets real.
I’ve never tried that. It sounds easy.
Because of the warning concerning migration builds, I would use the script as described a section later: Signing Builds | LineageOS Wiki
The switch to official builds should not be a big deal. It is just a matter of swapping my keys with the official ones. Worked before for me when switching from the test keys to my own. The switch to official should be similar.
I have to admit that I never tried it. But the first entry in the FAQ is
Installing LineageOS zips in Recovery results in “Error 7”
You are attempting to migrate from an unofficial build to official LineageOS. A full data wipe is needed if you are coming from something other than an official build of LineageOS.
But I don’t see anything different to @mmustermann’s switching to his own keys, just be warned if there are any errors.
My script is just the official one with the test keys replaced by my own. Download it, extract it, rename it to migration.sh, backup your data and follow the instructions in the “Using a script” section: Signing Builds | LineageOS Wiki
Does the bootloader need to stay unlocked for the key switching script to work and for OTA updates to work once on official or is it fine to lock it again after either of those points?