Yesterday I tried to install it. As I had a few unrelated problems, i rolled back, but a few observations:
I couldn’t connect to my wifi, it would not take my password. Wanted to investigate later, but as i had no time left, no logs. Will try later again, if it doesn’t ring a bell
My sd card is formatted texfat. This was shown as unusable and i would have to reformat. Any way for a support of this fs type?
As i depend on some apps i wanted to install the patched play store from shadow53. It did not show, regardless of how i tried. Any hints?
Hi!
I installed the LOS without microG on my phone and tested. Everything worked quite fine - even Magisk. Amazing work you did!
Then I thought yesterday, I should lock the bootmanager to use the phone witout that boot warning. But with that I managed to wipe my phone - even Magisk. Somehow I mixed up the 2 partitions it seams.
But I have a question: Will the probblem with a complete wipe be always there when I update LOS before OTA is working? Or are there any hints to avoid that?
But I have a question: Will the probblem with a complete wipe be always there when I update LOS before OTA is working? Or are there any hints to avoid that?
Thank you for your answer, dk!
I’d like to go on testing LOS (because it is the best Android out there).
Is there any backup tool (on FDroid) that might help me restoring the installed apps or their configuration?
Great idea! I never thoght of the backup-functions of TWRP. I only used it to flash.
Well … the only problem I found out was, that I am unable to launch TWRP from fastboot with locked bootloader.
Maybe it works with the installed version …
I flashed LOS on my FP3, and it’s working pretty good so far.
But trust gave me a warning that this build was made with public keys. I’m not sure what this means, but a quick websearch hasn’t been able to tell me why this should worry me.
Hi,
that warning means that we (meaning Max or myself) haven’t bothered to sign the ROM in any way, but are using default behavior. Signing the system software is done by the “official” distributions as a certification and guarantee to users that they are getting the original stuff, and not some manipulated and possibly malicious build by evil hackers. It is the same idea as with the little lock symbol you see up there at the browser address line at the top that is claiming that you are really looking at an official Fairphone website.
This warning will go away when the FP3 phone ROM is officially recognized and supported by LineageOS, because at that point the ROM will be built on their servers and signed using private keys known only to the developers there.
Hello again!
I use the rom (without microG) now every day and there is only one little issue: Wenn playing music with the installed player and screen off everything is fine. But when pushing the on/off button to interact there is a quiet creaking for about half a second. This is only after a few minutes without interaction - maybe some kind of energy saving issue.
But everything else I use regularly works really fine.
Great work!
Hi all,
I have submitted a request to go official with the ROM to the LineageOS devs.
I am confident that we have 99% of all issues resolved. I have been using the LineageOS ROM every day now for weeks and am quite satisfied with stability, features, and performance. Thanks to all the brave souls here who were willing to test with us, and let’s see how the response is.
Great to hear that! I keep my fingers crossed for you.
By the way, I testet a little bit with my sound issue: Som installed music player from f-droid had the problem in slitely other way: No creaking but one little break (just long enough to realize it).
But on the other hand my podcast player (AntennaPod) has absolutly no problem.
Thanks for your efforts! I got my FP3 two a week ago and now successfully installed your LineageOS ROM. Perhaps it might help others, below is roughly what I did. Although there are better guides here and there, this puts it all in one place. So perhaps useful for others here. Use at your own risk.
Installation guide for LineageOS on the FP3 from a stock ROM. Prerequisites: a computer with adb and fastboot installed.
As per https://support.fairphone.com/hc/en-us/articles/360041655711-Unlock-the-bootloader-of-your-Fairphone-3:
2a. Enable OEM unlocking
2b. Reboot into bootloader: “adb reboot-bootloader” (or power + volume down when devices is off)
2d. Run “fastboot oem unlock <your unlock code>” after the device is in the menu
2e. Follow the instructions on the device - all data will be wiped so make sure you have your data safe
Download the .img version of TWRP (3.4.0 or newer) from https://eu.dl.twrp.me/FP3/
Download the latest LineageOS ROM for FP3 from https://github.com/WeAreFairphone/android_device_fairphone_FP3/releases (choose between with and without MicroG)
As per this thread:
5a. Reboot into bootloader: “adb reboot-bootloader” (or power + volume down when devices is off)
5b. Reboot into TWRP (not installing it, just booting into): “fastboot boot twrp-3.4.0-0-FP3.img”
5c. Inside TWRP: Swipe to allow modifications first
5d. Enable sideloading: Advanced -> ADB Sideload -> Swipe
5e. Then from your computer, run: “adb sideload lineage-16.0-20200625-UNOFFICIAL-FP3-with-microG.zip” (or other .zip)
5f. Select back (don’t reboot yet) and select Wipe -> Format Data -> yes
5g. Now “Reboot System” and LineageOS should show up
After boot into LineageOS, in case of MicroG and GCM:
6a. Do the MicroG self-check and make sure everything is ticked
6b. Enable ‘Google device registration’ and ‘Google Cloud Messaging’ in MicroG settings
6c. Dial the phone ‘number’: *#*#2432546#*#* (for GCM - make sure it says it is connected)
6d. Only then install apps (through F-Droid or Aurora Store)
