This one is merged now @snevas would you please trigger a new build.
Building 
please test the testbuild.zip after it has finished. See
progress here:
https://fp2.joutubes.nl/jenkins/job/FP2-LineageOS14.1/41/console
1 Like
Thanks for the testbuild but sadly it didnāt work for me. SIM2 SMS bug is still present on my phone.
@_Chris @oli.sax would you give a try on the testbuild?
You can see the SVN changes to the device tree and the build information here. If you look at the build start date you can trace it back to a release.
Hello,
I am trying to follow these steps (from a FP2 open OS 17.04)
Flashing OTA fix went (finally) ok
But when I come to flash the lineage-migration-signed.zip and the lineage-14.1-20170609-UNOFFICIAL-FP2.zip, my phone always answers āzip signature verification failedā (doesnāt change a thing if I do it queuing the 2 files or step by step).
Does someone have an idea what I could try?
Thanks!
Vero
20170609 isnāt a OTA build. Download the latest here:
https://fp2.joutubes.nl/builds/full/
20170803 is the latest build. This one will flash after the migration zip.
Also disable the verification step checkbox before you flash.
Hello,
I thought you didnt need the migration zip, as the instructions in the 1st post donāt mention flashing it if coming from FPOS. I didnāt use it when I came from Open Android 5.1 and I can get OTA updates with Lineage.
Iād say that if you follow the instructions in the 1st post under āif coming from any other buildā then it should be a ok
Hello,
As I have a Mac, I had trouble getting fastboot to work, so instead I was able to use the TWRP App, which I downloaded from the play store to the phone, to flash the TWRP OTA Fix to recovery. This skipped the fastboot trouble. I can still successfully install Lineage OTA updates through the updater. What do you think about me adding a line or two with installation instructions in the beginning of this thread for those who canāt get fastboot going? It might help Lineage to reach a wider audience
1 Like
Itās a wiki post, so you can edit it yourself. But try to keep the instructions as simple as possible
1 Like
Thanks! But I am still tryingā¦
I updated open OS to the very last one 17.07.
(actually I had a look at lineage because it was impossible to get the file from here 2 days ago, but it worked todayā¦ )
Everything was still okay (apps, contacts, sms,ā¦ )
I flashed modem-17.07.6 (myabe it was not useful now I had the latest open OS?)
Then lineage-migration-signed (the latest one 08-03)
What should I choose now in the team wine recovery project page?
reboot?
Edit : Actually, I finally manage to get Lineage OTA updates through the updater so I made a step (or at least I hope soā¦). But after the reboot, I have this same screen and I donāt kow what to do
If coming from open OS, follow this part from the 1st post (no migration zip needed):
Be aware that youāll need to factory reset and youāll lose all data that you donāt backup.
Ok, thanks, I will start from scratch 
Edit: sounds like it doesnāt workā¦ I am āstuckā in open OS 17.07 whatever I tryā¦ 
Maybe is it because I get an āerror 7ā message (while flashing lineage-14.1-20170803ā¦zip)?
I keep trying
Edit2: I did exactly what is written here
And I still get this get this error7 message :-/
Edit3: No, it worked finallyā¦ in 2 steps
- factory reset
- flashing lineage 14.1-20170614-UNOFFICIAL-FP2.zip
@sky I just installed the testbuild.zip of 05/08/2017 and I also confirm that the SIM2 for SMS setup doesānt survive a reboot 
Pushed a update with the new security patches. Nothing else changed. Timestamp is 20170808.
Be aware of the following bugs:
3 Likes
As I still canāt OTA successfully (āDie ĆberprĆ¼fung ist fehlgeschlagen, beschƤdigter oder ā¦ā), I got me a logcat:
08-08 20:13:10.945 10081 18291 D DownloadManager: [269] Finished with status SUCCESS
08-08 20:13:14.691 7880 7890 I art : Background sticky concurrent mark sweep GC freed 139423(6MB) AllocSpace objects, 5(168KB) LOS objects, 28% free, 19MB/26MB, paused 1.564ms total 203.863ms
08-08 20:13:24.540 10081 10093 V DownloadManager: Deleting /data/data/com.android.providers.downloads/cache/lineage-14.1-20170808-UNOFFICIAL-FP2.zip via provider delete
08-08 20:13:30.775 18216 20682 E DownloadComplete: Verification failed
08-08 20:13:30.775 18216 20682 E DownloadComplete: java.security.SignatureException: signature digest verification failed
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.RecoverySystem.verifyPackage(RecoverySystem.java:315)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at com.cyanogenmod.updater.service.DownloadCompleteIntentService.onHandleIntent(DownloadCompleteIntentService.java:99)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.Handler.dispatchMessage(Handler.java:102)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.Looper.loop(Looper.java:154)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.HandlerThread.run(HandlerThread.java:61)
(How do I format this best?)
Is it possible that the LineageOS/android_frameworks_opt_telephony tree isnāt used in our LAOS builds?
Itās included. If you search within the buildservers console log youāll see:
00:01:19.506 Fetching project LineageOS/android_frameworks_opt_telephony
But Iāve heard there have been some other changes yesterday that could fix it. Could you test this one after is finishes?
Iāve seen that, but no more hints to the content of that tree and also no hints to SubscriptionController.java in my logcat after booting the phone.
Iāll try the new build as soon as possible.
No, the new testbuild didnāt fix it.