since years I had trouble with auto brightness. From day to day it became more and more bright. From time to time I recalibrated, but the setting drifted away to very bright display again and again. Often I had the impression that the automatically set brightness was twice as bright than the Point I corrected to. Some time I gave up auto brightness and and set a fixed brightness in the home profile and in the outdoors profile. The curious thing is, that the setting there must be about half the value you want the brightness set to. For example at home I wanted the brightness to be at 15%, but in the profile setting I need to set it to 5%. When setting the value in the outdoors profile to 70%, the brightness is switched to 100% when activating the outdoors profile. I need to set it to 25% to get about 70%.
In conclusion I have the impression that there is a bug which multiplies the set value by about 3. And this causes the auto brightness to malfunction.
With the new eOS version 4.3 I’m seeing adaptive brightness turning it down so low at night that I can totally not see to read. To be clear, this is in bed at night, with very low/no light. I have to manually turn the brightness up so I can read anything. Auto adapt is not working properly now - whereas it worked fine with eOS versions 4.2 and prior.
The Tideo App is great, although a bit cumbersome to operate. But it works like I imagine auto brightness should work. I am completely satisfied with it since the native android function does not work on FP4 nor on FP5. Thanks a lot for this hint!
For FP4 I still think it is a bug. In the Tideo App the brightness is set from 0..255. But the native android brightness slider moves from 0 to 100 % while the Tideo value is set from 0 to about 100. It looks like the native android forgot to scale the slider value by 100/255. In Tideo it is possible to scale the value. I used 100/255=0.39 as scale and the predefined curve worked out of the box. For me it is a strong sign for a bug in the brightness settings of FP4.
On the other hand the Tideo App has a possibility to capture the displays power consumption over brightness. When I do so, the display is set to much brighter values than I ever saw before. Maybe the brightness of 255 heats up the display more than it should be done. That may be the reason to limit the brightness to 100. But then this limit isn’t passed as 100% to Androids native auto brightness properly, so the auto brightness still seems to refer to 255 as 100% brightness.
With FP5 this theory does not work. There the display is much brighter and the Tideo curve needs to be scaled to 0.1 and changed to less slope.
I’ve noticed some kind of multiplication on my OnePlus 9 too, with v4.2, but for me it only surprised me when rebooting, which I’ve had to do a lot during the initial setup. All I could see was for relatively dark indoor values pre-reboot it would shoot up to about 75% post-reboot.
I didn’t tolerate that for too long, tried to transfer Velis Auto Brightness v5.0.1 over from my old phone, saw it wasn’t working on Android 16 anymore, found Tideo, used that for a bit, got annoyed with its responsiveness issues and weirder and more limited controls after a while, and went back to Velis since it went to v6.xx just this September as the developer restarted work on it and made it viable on newer Androids. Now I’ve got my comfortable reaction curve again, fast response according to my millisecond setting, but also doesn’t suck as much CPU power as Tideo.
Be careful with that one, it’s the v5.01. Don’t turn on Superdimming or you may lose all ability to interact with the system because the superdimming overlay could intercept all screen touches and not let you do anything after that.
The problem is Google are taking their sweet time updating the Play version after the dev sent in the newer v6.xx APKs, so you can only get the up to date ones from the top post in his XDA thread for now (or if you’re enrolled in some GPlay “beta program”, I haven’t looked into that).
