I have just done a OTA update to Lineage 14.1 microG 20180328. It worked, but it stopped at the TWRP recovery screen (version 3.2.1), and I had to tell it, to install the update and where to find the update file (at internal shared storage/data/lineageOS-updates/. I have had this as well with the clean LOS 14.1 without microG. No problem for me, but for an unexperienced user it might be a problem. At a Samsung phone I don’t have to interfere to do such a LOS update.
Shouldn’t there be a way to let the OTA update run automatically without any manual interference at the FP2 as well? There should be something wrong with the settings of my FP2?
My FP2 is encrypted and it has a SD card configured as external storage. @chrmhoffmann, @Roboe, @snevas, @z3ntu: Do you know something about such OTA update settings?
OK, so that seems to be the relevant difference.
Maybe the issue is caused by the sequence of decrypting partitions / requesting password )or something like this) after rebooting and before starting automatic installation?
In this case the behaviour should be the same on other devices running LOS & TWRP recovery…
Just for completeness, I’m on on the March 28th version, my phone is encrypted and I did not have any issues installing the update. But I don’t have the MicroG things. And I don’t have the zip file on an external SD card. I just start the update from within the updater screen and the phone reboots itself into TWRP and installs the update after entering the access code.
Your setting isn’t different from mine! I find the update zip files on the internal storage, the phone is encrypted and I did have this trouble with both, plain LOS and LOS microG. Thus it seems not to be caused by encryption.
But what else could it be? To root the (meanwhile sold and on its way to Sweden) FP2, I flashed ‘addonsu-14.1-arm-signed.zip’ via TWRP. Your phones are rooted in the same way? - The new owner may come back to me with this trouble!?