Thanks for update……
can i flash this update (dirty flash)…..via Lineage Recovery sideload…. over the previous Build?
Or new istall….dtbo…boot…vendor boot…..?
You can just sideload the lineage zip from lineage recovery, no need to flash any of the other partitions manually. However, make sure to install gooogle apps add-ons again before booting the new update (otherwise it will loose some permissions). This is necessary because backuptool is not working on the older build yet, but it will not be necessary anymore for upcoming builds (if your google apps package supports backuptool, like MindTheGapps), both using OTA updates or sideloading the zip.
It works very well! Thx, no issues encountered here, been using for 24h, eSIM in Sweden
Thank you so much Arian for the effort you put into this! Quick question:
If I install the unofficial LineageOS on the FP6 now, and later the official version comes out,
will I get it through the updater, or will I need to do a new clean install?
You will not be able to update via the settings. The current builds use my custom update channel and even if i’d link the official build there, it would be rejected because it’s signed with a different key. But you should be able to sideload the update from recovery without having to factory reset / clear your data. Of course, I can’t say that for sure yet since there’s no official build to verify it with, but, from my experience on other recent devices, this worked without issues.
Got it, thanks a lot for the quick clarification!
Is there anything I could do if SMS are still not working? 
I’d suggest to update to the latest build and if it does not work there, please connect your phone to a computer and send the output of this:
adb root
adb shell qtigetprop persist.vendor.radio.poweron_opt
adb unroot
the output is: 1
(writing random gibberish to reach 20 characters")
Please update to the newer builds then, they changed this property to 0 which fixes SMS.
We were on the latest build Now that I changed it manually according to the github issue, it works.
Any chance you manually used qtisetprop before then?
Each property has a def_val and a value key, we changed the def_val key, but if you ever used qtisetprop to set it to 0 before, value will be set to that value and takes priority over the def_val property. Can you please run these commands and share the results? In case the def_val is actually 1 for you, and you are sure you didn’t manually mess with the db, please describe which build you originally flashed and how you updated to which build exactly as detailed as you remember.
$ adb root
$ adb shell
FP6 / # sqlite3 data/vendor/radio/qcrilNr.db 'SELECT def_val FROM qcril_properties_table WHERE property IS "persist.vendor.radio.poweron_opt";'
0
FP6 / # sqlite3 data/vendor/radio/qcrilNr.db 'SELECT value FROM qcril_properties_table WHERE property IS "persist.vendor.radio.poweron_opt";'
FP6 / # exit
$ adb unroot
I just installed the latest image (0914)and when I want to set the screenlock pin I get the message ‘Screenlock was already changed. Try again with the new screen lock.’ After which the settings program crashes.
I installed recovery, the image, latest NikGapps core and Magisk 29 before staring configuration. All via sideload, as recovery doesn’t offer the option to install from the sdcard.
I can switch screenlock between none and swipe afterwards, but all other options give the same error. Fingerprint tells me ‘setup needed’, but I don’t want to use fingerprint. (and when I try it gives the same error)
Any tips? Maybe start fresh and flash Lineage and only NikGapps and add Magisk after initial config?
This sounds like you’re running into factory reset protection (as in you did not log out of your Google account before installing the ROM). You can fix this either by logging into your Google account again, or, if you don’t want to use Google services, clearing your factory reset protection partition using fastboot: fastboot erase frp
Thanks, logging into my google account fixed this…
I have to admit, Lineage is already very stable, I have less issues with the sd card then in the FP Android… In the FP version I had to reboot the device every time I wanted to write something to SD. (It felt like it was set to read only mode after the 1st time the screen locked)
Did someone manage to install microg ?
I’ve tried MinMicroG-Minimal from recovery but I’m getting “Not enough free space in your /mnt/system”
Also tried via magisk but it got stucked in a boot loop
Did you reboot the Recovery after flashing the ROM? It should have prompted you to reboot to the new recovery if you want to flash more packages. This error is what happens if you don’t do that.
Yes I did reboot to recovery after installing the rom. Also confirmed that the slot changed after rebooting.
It’s recommended to follow the official instructions to install microg: Installation · microg/GmsCore Wiki · GitHub
Thanks that worked
I thought you need to install the microg app as system app so I never tried this. But thats not necessary.