Another anomaly is that when the LUX reading is zero in adequate lighting if I turn off the Adaptive brightness the LUX reading disappears and there’s not even a zero reading. It does start up again once more light is sensed.
I thought they outsourced the FP3 android software development to a company in asia because they don’t had the ressources in the past? (was topic at the last big issues around buggy network compatibility in european networks - this issues stayed undiscovered because the software company just testet the FP3 in asian networks).
This auto brightness error is nearly in all FP3s around me so I could think it’s a general bug. So FP didn’t test it itself before release or the software department has a very bad QA. I mean it’s not a tricky bug, it’s very obvious.
Don’t count on a fast fix or update. In the past, these kind of “non-showstopper” bugs did not got an extra hotfix update. My guess is november…
Today I was driving in my car using my Fairphone 3+ to navigate.
I was in a longer tunnel and here the brightness was reduced too.
The screen was so dark, that I could not see anything, so I missed the correct lane.
So i got the update and the ambient lighting issue is very prominent and sometimes even dims the light so far that i even at night can no longer read the text on my phone. I can understand that it could be the result of a fix to save battery (if that was the motivation behind it). I also want to try to leave some room for thought. Is it maybe possible to make smaller jumps from being bright to being dim but therefore have more of them? I can imagine that could maybe help with these big jumps from being bright to being dim. (I have checked that and most of the time it was switching from the dimmest setting to half brightest setting and vice versa if you tilt the phone the right way (I use a FP3+). Hopefully this is more helpful to you than my initial comment.