So similar means, on the FP3 the screen dimms while you use it, and while the slider stays at 100% and it stays like this and you cant do anything about it, if you touch the screen or move the slider manually doen and up again or not? Sure it dimms before it locks, still under normal circumstances it will light up again, by shortly touching the screen. If its the same on the FP3 with beta A13, I would rather say they incorporated the same bug into the FP3 OS. I never had this neither with the FP3 Iode Android 12 last summer before I switched to the FP4.
1 Like
If they are not able to fix this problem, they should provide a downgrade to android 11.
I cannot stand this issue much longer
1 Like
did you open a ticket? I did so 2-3 days ago as it seem to be reproducible in sunlight. Instead of downgrading, did you think about installing a Custom ROM, I think I havent seen any report that this bug is also showing in any Custom ROM so far? They will not manage two Android Versions at the same time, so downgrading would mean you stick to security patch level what makes your phone insecure over time.
1 Like
I opened a Ticket and they said they would forward it to the respective department.
I would rather use an insecure andorid Version without this problem than a secure one with this problem. Actually it is the most annoying problem I ever had with a mobile phone ever since it makes the phone nearly unusable in a bright environment.
And I am really not motivated at all to read stuff about custum roms. I just want a phone that works but android 12 update really fucked up
4 Likes
I believe that they do:
- Visit
https://support.fairphone.com/hc/en-us/articles/4405858261777?s=09
- Download
https://fairphone-android-builds.ams3.digitaloceanspaces.com/FP4%2FFP4-FP4K-factory.zip
- Install it.
Just be very careful I guess this latest A11 version is the version that was only provided to some specific carriers and countries and installing this just might bring a lot more trouble. And whatever you do, def do not relock the bootloader else you will end up in completely useless bricked phone that needs to be send in.
Normally they def do not provide the option to manually downgrade for good reasons I guess
3 Likes
Because of the downgrade, or just generally, nobody should relock it? I was just about to relock my phone to recover access to Google Pay, since I believe that a locked bootloader is the last hurdle to overcome to pass SafetyNet validation.
Just have a look here… In short: yes in general, be careful, main factor seem to be the security patch date…
2 Likes
I saw that there is now a button for “extended darkness”. It’s just stupid that the display doesn’t behave the way it did before this new function, but that it’s STILL darker than it already is. Fairphone turns more and more into extremely half-hearted implementation of features.
Yeah, I’ve realized that I was wrong. It always occurs in brightness. I erroneously concluded that it was due to heat because the place I tested it was dark and thus cool.
You probably just don’t have the screen above 70% in the first place if you’re in the dark. 
I do think it’s responding to heat. The issue usually kicks in a few minutes after opening a heavy game, or soon after hitting “update all” on google play, and it’s also much more unstable while charging. I’d reckon the function is designed to reduce burn-in on OLED screens, although of course it doesn’t make sense here as the FP4 doesn’t have an OLED screen.
1 Like
I don’t see how wobbly luminosity would prevent that, I agree less luminosity would slow the process a wee little bit, but is it enough to be worth the hassle? Especially if it’s potentially annoying (“it doesn’t matter you’re not able to read your screen, the important thing is it will live longer…”)?
Also in this case there would 1. be a proper setting somewhere, 2. the phone would just go down a few notches and stay there, and 3. it would not report full brightness when it has knowingly scaled it back.
IMHO all points to a bug somewhere between Android’s brightness management and the backlight firmware.
2 Likes
I would not agree to that, as it for me happens just by typing a response here in the forum or an email (so really nothing heavy or creating really heat) and it def was and still is at 100% when it happens and it always happens (or it just noticeably happens) when you are out in the sun.
2 Likes
Maybe it would make more sense if I said “warmth” rather than “heat”. In any case it’s very easy to demonstrate that it’s not dependent on the brightness sensor.
How do you demonstrate? I could link it to this sensor, doing the sensor test in sunlight fails…
Maybe its caused differently or your issue us different!?
Either in a dark room or taping over the sensor. I reproduced it just now in a dark room by setting brightness to 100%, plugging in the charger, and playing Stumble Guys for about 5 minutes. That was starting from cold, but if I had been using the phone before that it would probably have been sooner.
4 Likes
Interesting observation 
Most of the times my screen suddenly got dimmed was with Duolingo, which can be a very resource hungry app sometimes. Not on the charger, but happened in very different lighting conditions.
Could this be a function that is supposed to reduce power draw going rogue 
I remember some people having issues with Google Maps showing a “overheating” message a while back, maybe it’s meant to prevent the system from overheating by limiting some components.
1 Like
Well, my FP4 does get warm (not hot) often, at least more often than my previous Samsung, but it never complained about overheating (definitely not while using Google Maps!), and some of this warmth is most likely due to being in my (warm) pockets and having that metal chassis which readily conducts heat.
I’d vote “likely”.
If this is true, summer is coming and we should notice even more/stronger brightness fluctuations.
So really different things can make this happen, again even with a Custom ROM. not sure if it helps or make more complicated to figure it out. So everyone on FPOS could help by contacting support…
2 Likes