Auto brightness getting stuck on high even in darker location - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Has anyone ever had this issue if so how do i fix it anyhelp is cool im running stock lollipop just received the updated and im not blaming 5.0 foe this bug because this bug has been with this phone since kitkat, so the brightness works but sometimes i notice that the screen is brighter than it needs to be, then if I toggle the auto brightness off then back on it corrects it's self. Its very annoying if you want your batter charge to last longer.

Related

Adaptive brightness weirdness

This is my first Lollipop device after a long time with Kitkat, so I may be missing something obvious, but I just can't wrap my head around Adaptive Brightness.
So when it's set to on it adjusts the brightness based on the light sensor, but I can also use the slider to tweak it, correct? But then sometimes the slider just stops working, moving it doesn't change the brightness at all. Only way to make it work again is to change the lighting significantly (for example I point the phone at a lamp). After the auto-adjustment kicks in I can tweak it with the slider again. Is this a bug, or yet another misguided "feature"? Do I have a hardware problem? I've tried a few sensor apps and everything seems to work fine. On top of the auto adjustment not being as good as Kitkat's, the inconsistency is really bothering me.
EDIT: I am on stock rom. I'm sure that CM12 would solve this problem if it's a Lollipop bug, but I can't be arsed with a custom rom a this time. Looking for a stock based solution, or at least an explanation for this strange behaviour.

Strange Adaptive Brightness issue

Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048
I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.
Same issue here.
Woah. I'm not alone. So for all you guys, it started just recently?
yeah. I noticed it a little less than a week ago
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).
I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?
I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.
I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?
Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.
i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!
The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.
I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.
Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.
I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.
Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.
Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.
I think we should file a bug report here.
https://code.google.com/p/android/issues/list
I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.

Do I have night mode left enabled in 7.1.1?

Hello everyone and sorry in advance if my question seems too stupid or issue looks non-reproducible.
I suppose everyone here agrees that there is no night mode in 7.1.1 on Nexus 6.
But nevertheless I have very odd 'night-mode'-like issue in auto-brightness behavior on my Nexus 6 running stock 7.1.1.
I have noticable brightness jumps exactly on sunrise and sunset times (up and down respectively) and much darker brightness levels at night. This is sometimes annoying and sometimes useful.
Earlier when flashing OTA from 7.0 to 7.1.1 I've unintentionally left night mode turned on (feature enabled by eponymous app).
Can anyone give advise on ADB commands to modify possible reminiscent auto-brigtness-related settings?
I want to to turn off this mode or at least confirm I'm not hallucinating on this but don't want to make the whole factory reset.

adaptive brightness in rooms with bad lightning too dim?

anyone noticed this too?
i have to adjust almost everytime the slider because it stays around 15% in dark rooms.. after some time it wents back to this.
its not 100% dark, tv is running and some passive lightning is on..
i have read the machine learning should soon know what i prefer..
never got this problem so hard before..
with google i found the information about the machine learning on adaptive brightness in pie, and 1 of 2 commenters have exactly the same problem with his pixel phone.
is this now a known bug, anyone here has the same problem? is there maybe some good app to fix this? i tried one but thats just the same as disabling adaptive brightness..

Auto brightness to low

Hi i am on gloabal stable rom and i have noticed that the brightness in low light goes to low and iff you change it manually to slightly higher it wont stick and after the phone screen is turned off and then back on the brightness in darker areas is to low again. Most android phones on Pie i have had have adaptive brightness meaning it will adapt to how you set it in each environment but on Miui i think it is different and it is also called auto brightness rather than ambient brightness. I am rooted and i have tried a couple of magisk fixes but nothing changed and in dark area it is still to dark and this is a big annoyance for me and i think it should an easy fix. Maybe someone know where the brightness values are located and can explain how to change this manually so it does not go so low in dark areas.
I have the same problem with 10.3.1 mi 9t pro
I don't have the problem anymore I moved to lineage
sam00561 said:
Hi i am on gloabal stable rom and i have noticed that the brightness in low light goes to low and iff you change it manually to slightly higher it wont stick and after the phone screen is turned off and then back on the brightness in darker areas is to low again. Most android phones on Pie i have had have adaptive brightness meaning it will adapt to how you set it in each environment but on Miui i think it is different and it is also called auto brightness rather than ambient brightness. I am rooted and i have tried a couple of magisk fixes but nothing changed and in dark area it is still to dark and this is a big annoyance for me and i think it should an easy fix. Maybe someone know where the brightness values are located and can explain how to change this manually so it does not go so low in dark areas.
Click to expand...
Click to collapse
Somebody on forum said that you have to train your adaptive brightness. Every time it is too low you bring it up with slider and after few times it should learn your preferences. I didn't yet try this, but I will...
Usually on Android it works like that but on miui its called auto brightness rather than adaptive brightness and didn't work in the same way.
Any news on this? Does it work on MIUI 11 / Android 10 better? I love this phone but this issue is really annoying.
I'm on miui 11 EU it works perfectly.
sam00561 said:
I'm on miui 11 EU it works perfectly.
Click to expand...
Click to collapse
Awesome, thanks for that, great to hear your problem is gone after the upgrade!
Codeman2000 said:
Awesome, thanks for that, great to hear your problem is gone after the upgrade!
Click to expand...
Click to collapse
sorry which problem are you refering to please.
The automatic brightness issue - it's mostly too dark in darker rooms.
https://forum.xda-developers.com/showpost.php?p=81436013&postcount=6

Categories

Resources