I waited for lineage to be released for the Fp3 before I bought it and end of the security patch support would end my use of the phone. So I wish you (and me) good luck at convincing the others!
Same! The journey of my FP3 will end, when I wonāt get any more security updates via Micro G anymore (or one of the important apps stops working).
as @TeamB58 mentionned, we should still have 2 years remaining for security updates!
for a device released in 2019, getting security updates until 2027 is nice!
on my own, iāll probably keep my fp3 until it dies.
recently fixed my headphones issue by replacing top module.
3 Likes
Well, thatās too bad. ;-(
Still, thank you for all your hard work all these years.
Iāll also stick to my Fairphone 3 until the end of security updates, and see then what to do.
It may be very out of date hardware (especially the camera), but for someone like me who do not play games and is not fond of being constantly connected, it does its job perfectly.
1 Like
Thank you very much, @TeamB58 for your hard and faithful work all over these years! As an enthousiastic LineageForMicroG user I was always thankful for your updates and would of course also be happy for future updates.
1 Like
Hello,
Iām quiet, but Iāve been using LineageOS on Fairphone 3 for several years. Whether the adventure ends with version 22 or not, I thank you for your long-standing support.
Axel.
1 Like
Since yesterday I canāt download the update from 5. December in the lineage updater app (microg). It says (in German):
Download failure. Check your internet-connection.
I checked the properties of the updater-app to see if it somehow lost its permission to use the wifi but it didnāt. Restart to system didnāt help.
Problems on the server side? Any ideas?
Edit
https://status.lineageos.org/?locale=de
Says server ok!
Downloadserver needs maintenance
2 Likes
Many thanks for the hint! Doesnāt sound like a quick solution. So I wait for the server to get funtional again.
Is a manual update possible/recommended?
New info on the security issue December 2025 security issues Ā· Issue #835 Ā· lineageos4microg/docker-lineage-cicd Ā· GitHub
2 Likes
Builds are comming back!
Having a frustrating issue with my installation at the moment. I have the build from early December installed and it worked very well for a while. Today I cannot boot anymore: the LOS loading icon freezes and the screen goes black. I did not do a LOS update, still running the one that worked earlier. I can reboot by holding the power button very long but I get the same issue again. I can still boot into recovery and fastboot if I hold the volume button.
Does this issue sound similar to anyone? Is there a known way to debug what is causing the booting to crash?
Thanks very much for the link! There it says:
Installing the new builds
Do not try to install the new build using the Updater app
We recommend installing these new builds by folowing these steps:
-
Take a backup, using SeedVault and / or Android Backup Project (if you have access to a Linux machine, real or virtual). This should not be necessary, but itās a useful step ājust in caseā.
-
Download the new build zip file from the Download server or by by getting the download URL from the ā3 dots ā Copy URLā option next to the newly advertised build in the Updater app.
-
Boot your device into recovery, and flash the new ROM zip file using
adb sideloadon your computer. Detailed instructions for these steps are available from the LineageOS installation instructions for your device (which can be found by following the links from their āDevicesā wiki page). The recovery will report āSignature verification failed: Install anyway?ā Choose āYesā as it is understood the new build uses a different signing key than the old builds.
Unfortunately the procedure described in Devices | LineageOS Wiki needs a Mac/Linux machine which I donāt have. No procedure for a windows pc any more.
Since I am not used to sideloading any more I need a step-by-step tutorial for a PC. Could anybody help because I fear to make a fatal mistake? 
I guess that all lineage users will need such a tutorial too?
will that work?
yes it should
Ce texte sera masquƩ
1 Like
Thanks @piero-e , it did! I successfully updated by dirty-flashing according to the tutorial. Felt like an adventure 
to navigate through the recovery with happy end. 
Edit: unfortunately the tutorial didnāt say that itās neccessary to tap āapply updateā (or similar) in the recovery to get the phone into sideload-mode. After I tried that (bravely) the sideload worked.
2 Likes
Small update on this. Tried factory resetting and reflashing, but any form of booting (recovery, fastboot, OS) started to get very difficult until at some point it was not able to boot at all. Thereās either something faulty in the power system or my storage has failed. It would be a gamble to start buying spare parts to potentially repair it, so Iāve decided to give up on my 5 year old FP3 (upgrading to FP6).
Itās been a long journey. My FP3 was on Lineage since the first day I used it, I believe one of the (first unofficial, later official) builds of @dk1978. Later transitioning in the follow-up of @TeamB58 . Iāve never had issues, updates were smooth, stable and quick. My gratitude is enormous for the hard work of you wonderful people. Thank you!
3 Likes
I assume that after manually updating my fp3 by sideloading the december build the next lineageos updates should work again through the updater app. Is that correct?Because the security keys match again?
Hey @TeamB58. I was wondering, if you can give me a hint on how to proceed with this issue: Settings for "Minimal time between two notifications" is gone (#8959) Ā· Issues Ā· LineageOS / issues / android Ā· GitLab
This was a very useful feature to limit annoying notifications, if someone sends multiple messages in a short time span.
How can this be reintegrated in LOS? Is it only missing for the FP3 or generally?
1 Like
Itās just that nobody had time to port it due to code refactoring and amount of effort involved.
Someone has to port it from lineage-21(if it was there).
1 Like