Hi, I am currently running Fairphone’s official Android 13 on my FP3 as a daily driver. Especially since A13, the phone became annoyingly slow, even without heavy usage like gaming.
Since the FP6 seems to have some bugs that are yet to be resolved and other brands don’t offer that level of repairability and fair production, I want give LOS4microg 22.2 (+Magisk) a try.
Is the phone usable as a daily driver like that, maybe even more than with A13?
A more specific question: my power button is dead, so I turn it on by removing the charging cable while the display shows “Fairphone powered by Android”. When the phone is on, I use WaveUp to turn my screen on (if the fingerprint sensor doesn’t respond), I use screen attention to turn it off and the power off/restart/lockdown options in the pulldown menu. Since these workarounds keeps my phone usable, do they still work in LOS/LOS4microg?
Welcome to the Community forum.
If you haven’t considered it yet, you might want to look for a (used) “Rear Module” in this forum’s marketplace: Market - Fairphone Community Forum
Thanks @urs_lesse, I haven’t considered replacing the rear module - I’m gonna look into that.
Anyone willing to share their experiences with LOS 22.2 as a daily driver on the FP3? Going through this page, it seems to be working flawlessly, apart from some bugs that are fixed quickly by @TeamB58. Are you happy with the performance of the FP3 or is LOS22 too much for such an old phone to use it as a daily driver?
It’s going ok on my front. Updates are still stable and the phone is usable to the best of its capacity
I am very satisfied with LOS on the FP3 and grateful for it, I have no stability problems, thousands of hours without rebooting are no problem.
I can’t say much about performance, I’m a light user and it’s enough for me.
I habe been using LOS for years now and it just works.
Sometimes bugs come, but they also quickly go.
Two things are annoying:
The WLAN doesnt work well with my FritzBox. That seems to be an issue of the FP3 itself and not of LOS.
The battery does not last for more than a day. It changed at some point an never got better. I am not sure what the issue ist, but I simply charge overnight now.
So overall, I am very happy and can recommend it. Especially, since the updates are arriving quite quickly and one usually gets the most recent Android Version, although that might stop due to the outdated kernel.
Well, I’m using it as my daily driver but the performance to me is far away from making me “happy”. Since years I never thought about a new phone but since a few months I do think about it cause the phone got slow.
Since I am running LineageOS 22.1-20250917 on my FP3 I dare to ask here:
After returning from the UK to Germany, mobile data doesn’t work with most apps. The APNs are correct, and rebooting didn’t help, though everything works fine with Wi-Fi. It worked before with older versions of LineageOS 22.1.
Does anyone have any ideas about what to do? Currently, I suspect there is an issue with SSL certificates.
(Please let me know if I should ask this elsewhere.)
Hi, i run also 20250917, but i don’t have any problems with mobile data.
So some apps do work? Thats strange.. did you get any error on apps which don’t work?
Did you do anything special in UK? Like installing certificates, changing apns.. and so on?
I just did a fresh install today of LineageOS + MicroG and I was having the same issue. For me it was solved by including the port (8080 for my provider) in the APN. Not sure if this did anything, but it worked for me. Also had to select which APN to use.
Also, thanks @TeamB58 for your efforts for yet another amazing release 
Thanks, @YokaiRick for your answer. Good to know that my LineageOS works in general. Yes, it is super strange that some apps work with mobile data, while others don’t. Unfortunately, all non-working apps just say that they don’t have internet access. Of course I have not actively installed or changed any certificates. APNs have been changed in Paris automatically, and I had to reset them in the UK to my usual settings, which worked before.
Interesting, @Timmeh that you had a similar issue. Since I use MicroG too, it might be related to that…. I tried to set my APNs port to 8080, without any positive effect. In the past, I have never configured “port” for any APN. What list of ports do you set? Thank you so much for your help.
Hello,
I’m having some Android crashes on some conditions when jack 3.5 is connected, e.g. audio is playing then call is coming, but not always. It keeps crashing until I unplug jack cable.
Did anyone else experience this issue ?
Might want to check what your provider specifies for APN settings. AFAIK it is set automatically so not sure my fidgeting did anything to be honest.
Also, did you turn on mobile internet? I know it is obvious, but when I first booted it was default to off.
LineageOS with MicroG was pushed earlier today, but it’s the first time I see a change in the file naming. It now contains “NO-PI-PATCH” (see here). What does it mean? And is it safe to install?
An internet search finds this reference …
Apparently this way users have a higher chance to have certain banking Apps working. The way I read it there’s a patch that gets a set of banking Apps to work, while it breaks other banking Apps. So alternating builds are being made with and without the patch so you as a user can pick whichever build lets your banking App work, or you don’t have to care if you and your Apps are not affected.
“(without the patch) - Triodos should run, Nationwide should not”
“(with the patch) - Nationwide should run, Triodos should not”
Play Integrity awareness might not be limited to banking Apps, but these are the examples used.
Just to give clarity on that, Google has now switched to a quarterly security release since June 2025. You can check the bulletins here.
The October Security Bulletin has been empty. Iff a CVE is critical or high then only it gets released in a month or else all CVEs would be fixed quarterwise moving forward.
The Security Patch Levels shall be updated even though that month does not have any fixes. So, this should not impact your banking apps and others that depend on SPL.
Let me know if you have any queries.
Edit: I am not sure if this would be relevant to the microg query since I am not aware what “NO PI PATCH” means.
Thanks.
I guess that Android 16 wont come for the FP3 due to the Kernel?
We are working hard to get Android 16 but no promises. For reference, I have completed the eBPF till 4.14
There’s still a long way to go but it’s not a dead end. It might take more time but we will try.
Wow, that is an unexpected answer. Very cool that you are trying this! Thank you.
This is a bit of a shot in the dark, please redirect me elsewhere if I posted in the wrong topic.
I had LineageOS 17.1 on my FP3+, with root via Magisk. I wanted to upgrade to LOS21, and uninstalled Magisk and unrooted (I don’t remember the process, it was a while ago). After following the upgrade procedure from the LOS wiki, LOS 21 would not boot and after a few failed attempts, the active slot switched back to LOS 17.1 and I had my phone back. For a long time I didn’t have time so I kept that.
Now I’m trying the same with LOS 22.1, and I have a similar issue, but now I can post the error I get: when booting the newly installed LOS 22.1, after booting unsuccessfully 3 times, the device goes into Lineage Recovery and I get presented with a screen saying “Can’t load Android system. Your data may be corrupt. […]” and that the reason is init_user0_failed.
I’ve tried to fetch logs in various ways (adb logcat, fetching the recovery log from Lineage Recovery), but I can’t find any more information than that. Also, I couldn’t find information about that particular error message anywhere.
Anyone have any idea what could be causing something like this? Anything I can try?