The vendor security patch level shown in lineage4microg complies with BoardConfig.mk and reflects the status of the extracted blobs by extract-files.sh e.g. proprietary libs. However, the firmware partitions e.g. for the modem aren’t included there as you can estimate from the OTA image file sizes (LOS4MG 694MB < LOS 699MB although ca. 70MB MG et al is included in LOS4MG). For a detailed check you may extract and compare the images included in the OTA’s payload.bin (cf. Extracting proprietary blobs from LineageOS zip files | LineageOS Wiki), and see that the firmware partitions unfortunately are missing the the LOS4MG. To stay up to date with the firmware partitions, I’m afraid you have to continue on basis of the original LOS or you need to setup your own LOS4MG build and include the FW images yourself …
Since a couple of weeks, I can’t receive any SMS for one of my carriers (I have 2 SIM cards). I have tried with the SIM card in another phone, and it works. The carrier claims the SMS have not been delivered because the phone is offline, which it isn’t. It’s been online all time.
So I suspect something happened with one of the latest updates, possibly the 20220221 update (I received my last SMS 2022-02-22 and I guess that’s when I updated the phone).
Anyone else?
Edit: Looking through the changelog, the only thing I find is this: https://review.lineageos.org/c/LineageOS/android_device_fairphone_FP3/+/322885/
The last update did change qti-telephony-common.jar to match stock. That may be related to SMS services. Can you send SMS?
Yes, I can send SMS. After fiddling with the phone and moving SIM cards around, it actually seems to work again. Which is good, of course, but a bit unsettling not knowing why it didn’t work.
Hello, I finally made the jump to 18.1 from 17.1 without a hitch, and I wanted to say a huge thank you to the maintainers. Long live lineageos!
My FP3+ top-module front-camera is not working anymore. The FP3+ Module works in a FP3 with stock rom.
On my FP3+ with latest LOS 18.1 build only the 8 MP old FP3 top-module works?
Anyone else is facing problems?
More information in this thread:
Thanks in advance!
Turns out I have the same issue on FP3 with upgraded cameras. I added details to the thread mentioned above.
While it might take time for official LineageOS 19.1 to arrive, take a look at my new work here
PS: It is only for Google/Pixel fans.
Thanks.
I just want to quickly say thank you for continued maintenance of the release and the regular and fast implementation of the security fixes. Thank you very much to all involved!
This is the second time my phone stops receiving SMS after an upgrade. Furthermore, the performance problems I complained about earlier is back. As far as I understand, this is partly due to zRAM not being enabled in LineageOS, whereas it is in stock FP3 Android. Seriously considering reverting back to stock unless someone can come up with a brilliant solution. I’m out of ideas. (I really don’t want to, because there are some aspects of LineageOS I really don’t want to miss, but I have to be able to trust my phone.)
I definitely support that. I’m rooted, but I’m considering unrooting as this is an endless race between Google/banking and workarounds. But enabling zram (and automatically switching airplane mode) are still making me keeping root.
I also considered stock…
you seem to say that the low performance of fp3+ is related to the fact that zram is not activated, is that right?
I am on /e/os (based on lineageos)
Yes, with time running there’s more pressure on the memory management. Sure, not needed apps get cleared from memory, but you can see the effects better and better with uptime
Hello, since the latest update, 18th April, the camera now seems to freeze in apps such as opencamera and WhatsApp. It works fine in the stock camera app. Is anyone else experiencing this?
Might have something to do with the new blobs. Right now I can’t catch a complete logcat, but it looks like there’s something going on here: WARNING: CPU: 3 PID: 21445 at …/…/…/…/…/…/kernel/fairphone/sdm632/kernel/power/qos.c:682 pm_qos_update_request.part.5+0x1c/0x28
Will try tomorrow to get a complete log and open an issue, if nobody beats me to it 
Edit: just created the issue with a logcat on gitlab
Also, some Apps can’t access their data on the external disk, notable osmand+ and the epaper app from a german newspaper
I can’t get any “permission denied” or the likes from the log
Edit: I guess I found out what happened: the permission is “access to MEDIA files”, but the card material or the epaper files aren’t flagged as media (in fact, they are stored in the Android/ - app specific folder on the card
Hi there, I’ve been meaning to report this for a while. On my phone, the auto dark mode and auto night light mode are turned on. If I understand correctly, they’re supposed to both turn on at dusk and turn off at dawn.
Well, regularly (or maybe all the time, I’m not sure), I have to forcefully turn them off in the morning by clicking on “turn off until sunset” for both options (and sometimes (all the time?) they don’t turn on at dusk).
Am I the only one ?
LOS 18.1 micro-g latest update (was happening in previous updates, too)
Yes I am experiencing this - unable to take photos using the main (back) camera when using Open Camera and ProShot. Videos are OK though.
In the stock camera app, back camera works OK, but unfortunately selfies are still green 
FP3 with updated (FP3+) camera modules / LOS 18.1 Apr 18 build
You are correct. I cannot use Osmand+ and its maps anymore. This is new with the New build.
With the normal FP3 and the stock camera modules I cannot save photographs in opencamera either.
Edit: Podcast addict cannot download new episodes either. Old episodes refuse to play (connection error).