its still working, just no to your satisfaction… and for the records, for me its also too dark in low light conditions and I increase it every time manually and there is indeed zero learning curve. In really drak conditions, I’m satisfied with the lowest auto-setting.
I was encountering issues with auto-brightness before update 15.162.0. Now it seems to work better. However, the phone always starts at minimum brightness (0%) after a reboot and requires manual adjustment.
This is still not fixed by the way, I can manually set the highest brightness while outdoors in direct sunlight in summer and seconds later it will automatically adjust it to about half brightness.
This issue is stated and IGNORED by FairPhone many times.
They make you do stupid tasks to “try to find out the issue” even though they KNOW that it’s a SENSOR PROBLEM!
The customer service is very slow and unprofessional.
FairPhone is FAR FROM FAIR if not a SCAM
Thats interesting and I dont see this behaviour. Is this really in bright sunlight or maybe in situations when you e.g. walk through tree shadows? Are you still using a CustomROM? Did you report the issue there?
Came to the forum for the first time looking for help with this. Like others, I find that the adaptive brightness feature on my F6 tends towards not-nearly-bright-enough in most light environments, and does not seem to learn from the manual adjustments I make.
I found that when I turned it off, and just adjusted my brightness manually, battery life took a noticeable hit over the course of an average day. And that seemed to be regardless of how bright I set it. Anyone else experience that?
It’s just like described in another thread:
The “viewing angle” of the sensor is too narrow. It’s a hardware flaw!
Same issue here. Also occurs with the camera, and when using scan app (i.e., Turboscan).
However with the scan app, by tapping twice on the phone, i get the screen bright again. Not true with the other use cases. Annoying.
Unresolved under Android16 - Build FP6.QREL.16.82.0 - all updated passed as of July 2026.
I assume you all reported this to Fairphone?
I guess most of us end up here either because it´s minor we wish it is fixed, or because it is major and nothing moves where it should in the first place.
On the Fairphone support, the first message is : “Replies are currently delayed due to high volume. Our team is working hard to get to every request. We appreciate your patience.”
It was the same message already end 2025.
From my experience on 3 different tickets regarding FP6, average response doesn´t count in days nor weeks…but in months…
Same issue here with Android 16 as of June 2026.