Thanks a lot @Max_S and @dk1978 for making LOS possible for FP3. Looks awesome to see the official support on the LOS homepage. I am really excited to try the official version. Props to all other maintainers and testers too!
But still I am also looking forward to see progress in adapting LOS for the new FP3+ modules. Please link future related topics here when closing the thread @Alex.A. Thanks again.
Thanks. So if I understand the process correctly, new builds are triggered regularly (once a week?) and if the build fails, the next attempt will be next time the set of builds is triggered again?
Funny thing that the microG-version has completed fine: https://download.lineage.microg.org/FP3/
I’ll try this probably this evening. If anyone is faster than me with trying, I’m eager to hear if that build works!
oh wow, that’s nice!
Could you check whether SeedVault is available in this build?
Although i doubt it since this new backup&restore solution is primary available for LOS 17.1…
EDIT:
I think normally they’re triggered once a week, yes. But they could also be triggered manually, too, if something fails.
I will try this soon. I wonder however, how things behave with Magisk installed. Will I need to remove it before attempting a dirty install?
Edit: I backed up in TWRP, just tried … and it worked with all my data unscathed. According to the instructions here (dirty install): https://lineage.microg.org/ I first installed the migration ZIP and then sideloaded their microG LOS version. Used TWRP for that to, as the sideload failed in the stock recovery. The flash did remove Magisk however, so I had to reinstall. I do wonder though - will this happen after every OTA update? Is there a way to prevent it?
Anyways - I’m glad it worked out. Kudos to all involved in the development!
Yes, microG is the latest version (.2.13.203915 at the time of writing), the menu “Exposure Notifications” is visible, and seems to work with Corona-Warn-App.