I have a battery drain problem but without AOD. In fact I’ve hardly been using AOD at all, having read that it contributed to battery drain. I’m now running some tests to see whether the drain is increased when using AOD. If not, then my conclusion would be that (my) drain problem is coming from elsewhere.
Just to give an idea, at night in Aeroplane mode with no connectivity at all, the charge level decreases by about 2% / h. In “normal” usage, using 5G data, phone calls, the occasional hotspot, it’s 3% / h.
But this is off topic. I’ll either start a new one, or more probably contribute here:
Unfortunely no. I think its genuinely just a hardware problem, and to be painfully honest, ive just learned to ignore it. I know, I should fuss up about this, but quite frankly I don’t see it as enough of an issue to get customer support to send a replacement display. Glad you found a solution though.
I can reproduce this too with the image below. On my Pixel 3 the image is total black. On my FP5 the image is gray. The notification bar remains with a gray tint (due to Google Photos) and there is backlight bleeding at the edges of the screen and in general remains gray.
With AoD it is also not off, the display still uses the backlight?! This explains the battery drain as well.
I think it’s a software issue, at least I hope so. I’ll report it to FP support.
Yes, making a black image with an RGB value of 0,0,0, DC Dimming turned off and screen display settings/colour correction set to default perimeters, I still get a bleed of light, like the pixels can’t seem to turn themselves off fully. What’s funny is now ive been using this phone for around 1 and a bit months, I can start to see my status bar icons begin to burn in on what is supposed to be a fully black screen.
I dont know, maybe I’ll reach out to Customer support later down the line and try for a replacement screen, I dont use the AOD so it isn’t draining battery and its only majorly noticeable at night so for me its nothing major, just an annoyance that, for my personal use, doesnt require a screen replacement.
I see it now too, with the brightness at 100% with a black image in Google Photos. With DC Dimming off the blacklight bleeding happens with low brightness already, but when turned on it is deep dark black. So there is some difference, just not with high brightness
I did the same test with my Pixel 3 as well, but on that phone the display is pure black with 100% brightness. I use on both phones Google Photos to display the image.
However, when I reboot my phone into the recovery mode (turn off the phone, and then long press the volume up button and power button at the same time untill you see the recovery menu), then I do see a pure black screen with high brightness. So I think the display is just fine. But there is something odd about it in the software. I also messed with the color profiles in the display settings, but that doesn’t seem to have an effect.
So TL;DR, I think it’s a software issue since the display can show deep black with 100% brightness. You can also see it partially when you pull down the notification bar twice. But of course it’s not total dark, but you should see that it can have this deep dark contrast.
In the My Fairphone app you can also do a display test, but it doesn’t go full black, the notification bar is still visible. But no backlight bleeding in the black areas.
I hope that they just accidentally messed up the black level, that they communicate to the screen, similarly to how TVs sometimes work on limited range signals. If that is the case, they can do a simple firmware update to fix this issue.
Holy smokes it may actually be a software fault, I also tried android recovery mode and the black background was proper OLED black, no light bleeding whatsoever. I also noticed when booting the phone, the default android boot screen ALSO is properly OLED black, but as soon as fairphone splash screen plays with the 4 spinning dots, the black begins to have the light bleeding through.
This is, in my books, great news! As it may now just need a small patch to fix, and not a brand new display. I will contact customer support about this, I encourage others to do so if they are also having this issue.
Pretty much. If you have this issue - and especially if it’s important to you - then please open a ticket with them. It’ll help them to see what people care about and which problems exist in the “real world” in the first place. They might also update priorities if they get more reports.
It’s categorized as “medium impact” which is the highest priority at the moment. So please let the support do their work and don’t bother them with unnecessary complaints.
That’s a community maintained list of issues. FP support uses their incoming tickets to prioritize issues. So yes, the way to flag issues and get them fixed is to open tickets (not just by one person, but by everyone).
