I neither would say heat is an issue, I had it outside in sunlight and so far sunlight does not really cause heat like in the summer…
I’m just wondering whether this “sudden dimming” isn’t preparatory to the screen turning off. Since we all have different screen-on timeouts, different people are going to see different effects. You might (provisionally) try extending the following value:
Settings > Display > Screen timeout
to see whether that prevents the screen from dimming ?
Could well be. I’m testing a beta A13 on an FP3 and have something almost identical with my30 sec timeout
No it is not as discussed already above
you use the FP3 and not the FP4 so how would you notice when we talk about a FP4 bug🤔
I thought so too, but then I did notice that my screen’s brightness is very slightly varying all the time (constantly?), even when and while I’m actively touching the screen. Most of the time it’s rather imperceptible, but sometimes, rarely for me, it becomes very noticeable.
Timeout might account for some occurrences, but there definitely is a different problem too.
For me it seems to be reproducible in the sun. Currently writing in a dimmed screen, brightness at 100% and difficult to see something… For me that def did not happen last year.
I was saying that it may not be a bug as OldRoutard speculated that it may be an Android intent, which as I have moved from 11 to 13 I see a similar issue. So I was saying OldRoutard maybe on to something which is Android 12/13 related and not Fairphone 3 or 4 issue.
It must be the way I comment as I’ve noted a few times you have interpreted differently than I meant. Even in the UK my place of birth people wonder what I’m talking about
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.
If they are not able to fix this problem, they should provide a downgrade to android 11.
I cannot stand this issue much longer
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.
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
I believe that they do:
- 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
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…
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.
That’s just a feature of #android12.
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.