Join now - be part of our community!

Android Oreo Adaptive brightness bug

PSSmith
Visitor

Android Oreo Adaptive brightness bug

I've updated the new firmware a couple of days ago and noticed something wrong with the adaptive brightness.

It used to be slowly adjust the brightness but after this latest update, it's adjusting the brightness so fast and make me less comfortable to use it.

Sometimes it makes me feel sick. 😢

Does anyone have this problem too?

102 REPLIES 102
profile.country.DE.title
Felensis
Member

I can confirm this bug, too. Very annoying. Glad to see that it's not just my device. I think there will be a fix for this in the next update. At least I hope so. Other than that I'm happy so far with Oreo. Kudos to Sony for bringing it so fast to the Xperia XZ Premium!
Nano1
Visitor

Its true, i make a factory reset whit XC and install de last update but i still have the problem, a little less thats all

hno3_3hcl
Visitor

Same here. I've reported in my previous post but it seems that it's been neglected. The auto brightness feature worked fine under Android 7.1.1, but after installing the 47.1.A.3.254 (Oreo), the light sensor has become over-sensitive, especially under low light conditions. The following  47.1.A.5.51 update didn't solve it either. Hope Sony can fix it asap.

Joaquin11
Visitor

Translation via Google Translate:

I also have this error

También tengo este error 

profile.country.RO.title
razvpop
Member

Same isue here. 

Was anoying before oreo. 

Now i just turn off this feature.

Using manual untill they fix it. 

Was hoping a fix with oreo...

Still a Sony fan but Who know s for how long in this situation. 

JSteele
Visitor

Xz premium After Oreo update has a too sensitive sensor brightness. it constantly changes brightness and is really annoying. Solve please.

JSteele
Visitor

I nave the same issue . Vary annoying.

Solve It.

Snakepit1
Visitor

Me too. Same problem

Grumpydoggy
Visitor

Yes me also - disabled the adaptive feature for the time being. 

Borkson
Visitor

Same here. I confirm the bug.