Official LineageOS 17.1 for Fairphone 3/Fairphone 3+

Glad the APN details helped, the issue was resolved for me as-well. See original post.

3 Likes

Thank you @Gert123 and all others involved! As the battery calculates a remaining battery time of approx 5h I also suspect battery issues…

EDIT: Futhermore, the APN settings are fine…

(LineageOS 17.1-20210215, without MicroG, Fairphone 3)

Live Display not working.

Does anyone have the same problem / know any solution to this? When I adjust basically any settings related to the screen colors of my FP3, it doesn’t take any effect!

So none of these are working for me:

  • Live Display adjustments in System Settings
  • night colors
  • greyscale mode (put display into black and white for reading etc.)

Any tipps or help would be much apreciated. Thank you

1 Like

These are known bugs at the moment. Unfortunately, our maintainer is a bit “time challenged”, but i guess/hope this will change again one day :wink:

1 Like

Fairphone 3+, Lineage 17.1 - 20210127 - microG

Hi, i just wanna report some issue:

  • Contact synchronisation is not working with Twint. It is only working when I save a new contact though twint.
  • Sometimes during phone call, phone freeze and need to be hard restart. (Batterie away) Sorry not have more details
  • Qoqa.ch app is not able to notify, also with all permission
  • The 48MP Camera is still working on 12MP

Thanks for your work, I’m really happy with Lineage!

I know thats sad to hear, but it isn’t really a 48MP camera. The camera has a so-called quad-bayer sensor that combines 4 pixes into one whicht results in a 12MP output.
Take a look here:

Have you had those issues with normal phone calls or with messaging apps like Signal/WhatsApp?
Similar issues with messaging apps were mentioned here before and @lklaus opened an issue at GitLab

4 Likes

Thanx for the answer!!
I didn’t know about the camera, but it seems logical!
About the restart issue, i had that 3 times the ladt week and only by normal phone call.

Hello all,
I am waiting for @dk1978 to come online.

In the mean time, here’s a treat to all users from my side.

11 Likes

Moderators/Admins, am I allowed to share this unofficial build via a new post?

1 Like

You are free (and very welcome!) to post a link to the unofficial image with a disclaimer that it is an unofficial image, and users are free to decide to click on it or not :wink:

5 Likes

Done:

Thanks

6 Likes

The FP3 image runs very stable. Many thanks to @dk1978 .

The following problems I currently still have in the Bluetooth area:

  • Volume in the car (with bluetooth) partly too loud / too quiet
  • Starting a call in the car (from contacts) not possible. Nothing happens. Pairing is ok.

Are there others with the same problem?
I am currently on 17.1-20210222-NIGHTLY-FP3.

Thanks for feedback.

Am i doing something wrong? I tried to follow the steps on LineageOS wiki for installing, and when i did “temporarily” flash recovery, it immediately rebooted, i have had no time to hold volume up and power to access recovery mode. Now when i do manage to get into recovery, its a dead android with “no command”. Should i repeat the steps and make sure i get into recovery on first try else the original system will wipe it ?

As I yesterday had an important phone call which terminated three times with a spontaneous reboot:
What exactly are the required partitions to flash after extracting them from the stock ROM?
And who to flash? Can we assume that the normal way would be like fastboot flash modem modem.img? I mean: is the partition always called like the image?

Best regards

In one of the threads there was a script which did the flashing. I’m not sure where it was, but later i probably can amend this post with it, if nobody else was faster…

Edit: yes, looks like all the partitions are named similar:

fastboot flash product product.img -S 522239K || exit 1
fastboot flash keymaster keymaster.img -S 522239K || exit 1
fastboot flash cmnlib64 cmnlib64.img -S 522239K || exit 1
fastboot flash cmnlib cmnlib.img -S 522239K || exit 1
fastboot flash lksecapp lksecapp.img -S 522239K || exit 1
fastboot flash mdtp mdtp.img -S 522239K || exit 1
fastboot flash vendor vendor.img -S 522239K || exit 1
fastboot flash system system.img -S 522239K || exit 1
fastboot flash boot boot.img -S 522239K || exit 1
fastboot flash vbmeta vbmeta.img -S 522239K || exit 1
fastboot flash dtbo dtbo.img -S 522239K || exit 1
fastboot flash dsp dsp.img -S 522239K || exit 1
fastboot flash devcfg devcfg.img -S 522239K || exit 1
fastboot flash tz tz.img -S 522239K || exit 1
fastboot flash rpm rpm.img -S 522239K || exit 1
fastboot flash sbl1 sbl1.img -S 522239K || exit 1
fastboot flash modem modem.img -S 522239K || exit 1
fastboot flash aboot aboot.img -S 522239K || exit 1
2 Likes

Thank you very much. And if I understood @dk1978 correctly, the modem and the dsp are the partitions which should/could be updated, right?
Edit: and of course one must get hands on the stock ROM…

Hi! I have installed an unofficial lineageos 16 (gsi build) some months ago (before FP3 got an official image). So my bootloader is already unlocked, I have twrp installed on the recovery partition (at least the active one) and also magisk and microg (flashed separately). I want to install the microg build of lineago OS, preferably without loosing data :slight_smile:

So far, I understand the upgrade process should be:

  • (backup data partition)
  • adb reboot recovery to reboot into twrp, and sideload in this order:
    • migration zip of microg build
    • new microg lineage os rom
    • magisk
    • twrp in boot partition?
  • reboot, check that everything is working
  • redo step 2 to flash everything in inactive slot.

Is this gonna work? Can I flash directly on LO 17, or do I need to first migrate to microg LO 16

Reading this thread, it feels like I’ll loose my data by upgrading to 17. Is it really the case? Can I restore from the backup I made with twrp after the fact?

Do I have the correct flash order? I might not flash twrp at all btw (I find it handy to have it installed, but I might do it later)

Thanks for your answers.

Hi everyone :slight_smile:
I have a question regarding the following commit: FP3: Import blobs from FP3-REL-Q-3.A.0077-20201221.124002 · LineageOS/android_device_fairphone_FP3@bd8ac5c · GitHub

The commit message sais new blobs are imported, but I only see changed strings. Can someone tell me how the importing of blobs work?
Also I am wondering what blobs get updated with LOS and what blobs dont. Also: How can I update the blobs that dont get updated with LOS? This seems important because of the known call freezes etc that fairphone seems to have fixed now.

Thanks for any details :slight_smile:

Please PM me for the details on how blobs work with LineageOS.

Hey all,

I am waiting for all initial issues to be resolved before I get a FP3+. I read the official blog post about various issues including the random reboots during calls, and there are various upates where it’s mentioned that a lot of the issues are fixed (the December update specifically mentions the random reboots).

Are these fixes incorporated into LineageOS 17? If not, how does it work, are they eventually going to be incorporated? Where can I follow developments on this?

Thanks in advance!

1 Like