Porting LineageOS to FP2

Yeah seems to be that! Gonna try the airplane workaround next time.

1 Like

Can add your results as comment to the bug report

1 Like

You can turn any forum topic into a RSS feed by adding “.rss” to the URL. For example:



Finally got a meaningful almost not corrupted last_kmsg after a random reboot.
Guess what? It’s the modem driver purposefully panicking the kernel to reboot the SoC after a modem failure.

SMSM: Modem SMSM state changed to SMSM_RESET.
Fatal error on the modem.
modem subsystem failure reason: lte_ml1_sm_conn_meas_vmc.c:3285:Assert IS_BIT_SET(meas_cfg_req->meas_obj_valid.
subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
[<c010ee28>] (unwind_backtrace+0x0/0x138) from [<c0bd54b8>] (panic+0xb0/0x23c)
[<c0bd54b8>] (panic+0xb0/0x23c) from [<c017ce90>] (subsystem_restart_dev+0x1b0/0x1fc)
[<c017ce90>] (subsystem_restart_dev+0x1b0/0x1fc) from [<c0bd5184>] (restart_modem+0xa8/0xd4)
[<c0bd5184>] (restart_modem+0xa8/0xd4) from [<c01438c4>] (modem_err_fatal_intr_handler+0x34/0x48)
[<c01438c4>] (modem_err_fatal_intr_handler+0x34/0x48) from [<c021ae98>] (handle_irq_event_percpu+0x94/0x2b8)
[<c021ae98>] (handle_irq_event_percpu+0x94/0x2b8) from [<c021b0f8>] (handle_irq_event+0x3c/0x5c)
[<c021b0f8>] (handle_irq_event+0x3c/0x5c) from [<c021dd48>] (handle_level_irq+0xf4/0x130)
[<c021dd48>] (handle_level_irq+0xf4/0x130) from [<c021a4ac>] (generic_handle_irq+0x20/0x30)
[<c021a4ac>] (generic_handle_irq+0x20/0x30) from [<c0138b4c>] (smp2p_gpio_in_notify+0x254/0x2dc)
[<c0138b4c>] (smp2p_gpio_in_notify+0x254/0x2dc) from [<c0be8000>] (notifier_call_chain+0x40/0x68)
[<c0be8000>] (notifier_call_chain+0x40/0x68) from [<c01d8cc4>] (raw_notifier_call_chain+0x14/0x1c)
[<c01d8cc4>] (raw_notifier_call_chain+0x14/0x1c) from [<c0137c2c>] (smp2p_interrupt_handler+0x330/0x47c)
[<c0137c2c>] (smp2p_interrupt_handler+0x330/0x47c) from [<c021ae98>] (handle_irq_event_percpu+0x94/0x2b8)
[<c021ae98>] (handle_irq_event_percpu+0x94/0x2b8) from [<c021b0f8>] (handle_irq_event+0x3c/0x5c)
[<c021b0f8>] (handle_irq_event+0x3c/0x5c) from [<c021de64>] (handle_fasteoi_irq+0xe0/0x14c)
[<c021de64>] (handle_fasteoi_irq+0xe0/0x14c) from [<c021a4ac>] (generic_handle_irq+0x20/0x30)
[<c021a4ac>] (generic_handle_irq+0x20/0x30) from [<c0108eb8>] (handle_IRQ+0xa4/0xe4)
[<c0108eb8>] (handle_IRQ+0xa4/0xe4) from [<c01028c0>] (gic_handle_irq+0x98/0x124)
unwind: Unknown symbol address c01028c0
unwind: Index not found c01028c0
wcnss crash shutdown 0
Rebooting in 5 seconds..
Going down for restart now
Calling SCM to disable SPMI PMIC arbiter

1896 Corrected bytes, 11 unrecoverable blocks

Can you open a bug here:

Here: https://bugtracker.fairphone.com/project/fairphone-lineageos-on-fairphone/issue/13

I have updated the modem.zip file to the latest modem firmware of Fairphone OS 17.09.3. This zip file also includes the official Fairphone splash image. In case you have installed a custom splash image, you might want to reflash it.

I wanted to add some verification code to the updater-script, but it doesn’t run yet. I’ll try to fix it until the next release.

:file_folder: Download: modem-17.09.3.zip
:bookmark_tabs: SHA256: 14a27ed94dc450ed1fe0e9cd2543f4b350dec096f97369a33c5e2c3693dd45bd

After you have flashed the zip file, you should see the version 4437.1-FP2-0-07 under Settings -> About Phone -> Baseband Version. It was 4436.1-FP2-0-05 in the previous version.

Since those are binary blobs, I have no idea what has changed since the previous release. But comparing the image files, I can see that the following files were changed:


The following files were not changed since previous release:


Alternatively, you can flash the latest modem firmware using fastboot. You can get the firmware images from the official Fairphone OS downloads page (scroll down to binary images). Don’t flash system.img, boot.img and recovery.img obviously.


Regarding the SIM2 SMS bug which was closed in the bugtracker

I know that this bug is fixed in LineageOS BUT as stated in differend post in the Lineage OTA thread

and also in the bugreport from @freibadschwimmer

this bug still persist in our Lineage ROM till now.

After some peeking around in logfiles and with regards to the different SIM bugs in the bugtracker and here at the forum, it looks like that we have a problem with the communication between
OS <-> RIL <-> MODEM
As RIL and MODEM are binary objects from Fraiphone/HW Vendors and also used in the FPOS/FPOOS builds without the problems we have in Lineage, perhaps there is some ill communication between OS <-> RIL.

What build (=build date) and what modem are you running?

Can you fill in the modem and your findings in issue 14? I’ve re-opened issue 6.

Thanks for your tests and your work!

Build-Date = Mon Sep 11 07:54:22 UTC 2017
Baseband = 4437.1-FP2-0-07

I have downgraded to my (self-built from source on the given dates, with only a slight modification to frameworks/base to add a signature-spoofing permission, required for proper operation of microG) 20170918 build from my 20170930 one because it was unusable: some processes would randomly fail to start, and this would only get worse with the uptime. I’m afraid I don’t have much debug info on this, but I suspect this is because of the recent kernel changes.

Please use the kernel with the revision e8ab366049f92612f4926ea422a1ce313625e305 and not cm-14.1 for now.

1 Like

Fairphone hasn’t changed any files for the modem firmware in FPOS 17.10.1 compared to FPOS 17.09.3. So there won’t be a flashable ZIP file this month.


What is the current status? Is there already an official request (link) to become a LingeageOS device?

I am very satisfied with the current (14.1-20171004-UNOFFICIAL-FP2) release. Thanks very much to @snevas and @chrmhoffmann and all other contributors.

Simply top!



I need to write a wiki page and some stuff. Maybe I find a few hours this weekend to progress this. I have a cleaned up device tree now and cve status is also looking quite good.

I recently tried to upgrade kernel as well, but we see some issues with device getting unresponsive.



I can help with the wiki, if you want. I know how Jekyll works, so I can free you from some dirty work.


5 posts were merged into an existing topic: Using LineageOS on the FP2

3 posts were split to a new topic: Missing GravityBox on Lineage OS

If ever there needs more porting to be done we can reopen this topic.