At first glance I almost could not believe my eyes: After more than 15 months, this major issue has finally been solved. Personally I had lost hope, but - hey! - this is amazing.
I can definitely confirm that for me, this fix has significantly improved the battery consumption of the display. Thatâs in particular because I use the app LED Blinker due to the undesired loss of AoD. Now I can actually live with charging only to 80% and still have enough battery life left in the evening, which did not work for me before the latest update.
So as you have successfully solved the display issue - please bring AoD back so that we can use the native Android feature instead of all kinds of workarounds.
And in case you didnât notice it before: The green tint when holding the phone at an angle has also disappeared. And I would like to refer to a video on youtube, where a fairphone employee wanted to destroy this error, which a âtesterâ published in a fairphone test, with the words âI donât know how âyouâ normally hold a cell phoneâŚâ and ended with uncomprehending smile. Comedy Gold like Appleâs â You hold it wrong-Meme!
After barely getting through the day with my FP2 in the past I was happy to find that the FP5 went longer with one charge but it still wasnât amazing compared to other smartphones. With this change you seem to have made a huge step forward in that aspect, im writing this on my phone that was charged to 100% the day before yesterday (finished charging at 11:30 AM) and it currently still has 31% left. So thatâs more than two days with my usage. Thanks, keep that spirit up, fix more issues and make the FP5 an even better phone
Fairphoneâs firmware with this fix will also appear in the next update of LineageOS 22 for FP5 (probably on 11 Feb, since current update was yesterday on Feb 4)
@michele.g
We are seeing one update after another without Always On Display returning to the FP5. I really donât see the point of keeping it cancelled. Fairphone successfully solved the display issue, so why not just bring AoD back? Itâs still everyoneâs own choice to turn it on or off.
For me this is really, really annoying as this feature was crucial for my decision to buy the FP5. I would not have accepted a phone without AoD and without a notification LED. I need one or another to reasonably use my phone. Itâs rude from the manufacturer to just take a feature away that was part of the deal at the time of purchase. I would actually prefer to return the phone to the manufacturer and claim my money back if AoD does not return.
So please take care of this issue and make this important feature available again. Thanks.
You need to write to fairphone. This is a user forum; asking us users to change the software is as helpful as asking your neighbor to change the software.
You are both right, @yvmuell and @AxelFFF . And the missing feature annoys me so much that I indeed have filed a ticket with Fairphone support on this.
First it took FP one and a half years to identify and repair an obvious display error which made it impossible to actually profit from the key advantages of an OLED display. And now have been keeping us from taking a free choice of whether to turn AOD on or off for already more than nine months. I paid for this feature, it was crucially decisive for my purchase. Thatâs why I feel cheated on, this is just not a correct behaviour from a manufacturer towards its customers.
And another update (FP5.UT2P.B.122.20250422) that has not brought AOD back.
My support ticket (no. 1267716) raised on 23rd April, 2025, which is more than 3 weeks ago, has not been answered yet. No reaction at all so far, not even an apology or a message that they are working on something, I am just being ignored. This is what I call really bad customer support, itâs non-existing.
@michele.g Can you please take a look and make sure that this issue is taken seriously? Thanks.
I am guessing a bit here but I think getting AOD back and usable is simply not possible. Lots of people seem to have linked this OLED issue with the AOD issue, but no - its very different. With AOD enabled the CPU doesnât sleep and the battery will last like 6 hours - unusable.
I honestly think Fairphone messed up and the hardware they have used simply does not support AOD.
I also would never have brought a phone with no notification LED (preferable) and no AOD and the second a phone with a serviceable battery and either LED/AOD enters the market I will buy it. Until then, have to just accept things as they are and remember to manually wake phone sometimes.
Why do you think so, that this is the case, and that this is the problem? Do we have concrete information on this?
Apparently other phones can do it ok, and if the AOD has an animation or its content continuously changes, then the CPU must be not sleeping there either.
What phones usually do is sleep most of the cores of the CPU, especially the more performant ones, but always keep one awake, e.g. to be able to keep a network connection open to receive push notifications, and to schedule background tasks of apps.
I am not an expert and this is my opinion and nothing more
I am running Iode, which has the fixes for âOLED black pixelâ and AOD still absolutely smashes battery and the CPU is prevented from ever sleeping. This can be seen in the standard battery usage menus.
I honestly donât think modern phone SoCs are as simple as âkeep one core awake for background stuffâ. I think they have to actually be able to support driving the screen whilst actually being asleep. The weird embedded systems SoC chosen for the FP5 probably doesnât support this because its never meant for phones. Again, my opinion, but Fairphone know its annoying a lot of people and they canât fix it.
Please dont open up this discussion here again. The FP6 is around the corner and Iâm very confident we will see AoD. For the FP5 I would be interested how its working on the Shift 8 which uses the same SOC, will check their forumâŚ
@michele.g
