Hey guys, now that I'm all caught up and on MM, I've found an issue that's really kind of annoying.
Not sure how many people use Lux Auto Brightness over the default, but I've personally become very used to having it. Now with MM, Lux's notification overlay (which would normally replace the standard brightness slider) shows up as it's own notification rather than as a replacement. Kind of annoying to see 2 brightness sliders especially when the default brightness doesn't work while Lux is enabled.
Has anyone else experienced this and found a fix? I'm assuming this is an MM issue and I do plan on rooting once I get more than a couple minutes to do so, I'm assuming Xposed could fix it although I'm not too experienced with this alternative.
Thanks for the help!
+1
I tried a lot with and without root, unfortunately to no avail. There is a Russian patch for S7 but I do not dare to try on S6.
Related
Guys
I have a new galaxy tab and got the recent update as well from 10 days ago. I've used an ipad before and the auto brightness worked very well. However, with the galaxy tab it keeps changing during the day time when there's consistent sunshine coming into the room (not directly though) and also at night with my CFL's turned on. Has anybody else noticed that? I see a plethora of apps to handle this and allow easy adjustment of brightness level but I thought auto-brightness should be an easy function to implement which Samsung hasn't pulled off well
Any solutions?
Thanks
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.
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.
Has anyone noticed an issue with the auto brightness of the note 8 ? It seems it doesn't get adjusted efficiently! Sometimes it's too dim and sometimes too bright, that's so disturbing
It's really funny, it worked after I installed an application called lux lite, that's unbelievable.. I need to install a third party application on a 1000$ cellphone to get such a basic function working. Thanks Samsung !
ghassan haddad said:
It's really funny, it worked after I installed an application called lux lite, that's unbelievable.. I need to install a third party application on a 1000$ cellphone to get such a basic function working. Thanks Samsung !
Click to expand...
Click to collapse
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.
pedmond said:
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.
Click to expand...
Click to collapse
I find that is not doing such a hot job at learning my preferences. I keep having to manually adjust because my phone thinks it knows what I want. It's annoying.
pedmond said:
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.
Click to expand...
Click to collapse
do you mean that it has a new functionality that has not been in old phones? I have the Note 4 and it works like a charm, but the note 8 auto brightness works strangely, when I'm in a room with low brightness the screen light goes so dim that I can barely see anything!
Ive experienced the same thing, I have to do a screen lock for its auto brightness to work correctly
Hi,
(sorry for my English)
Your message was one month ago but I reply just in case some people have the same issue.
You have to call samsung about your issue. I have done that there are 2 months ago and Samsung are going to change the settings only if they have lot of complaint about this weird behaviour of the note 8, S8 and S8+.
The new settings of the auto brightness is "smart" but often it's more like "lost" than "smart"... :/
I adked to Samsung to give 3 choices for the settings of the auto brightness for the user instead of 2:
1) manually
2) auto "smart"
3) auto "not smart" => so the phone adjust the brightness depending only of the light sensor.
They told me that my proposition can be integrate only if they received lot of complaint.
Seems to come with last update
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.
N1T15H said:
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.
Click to expand...
Click to collapse
I don't recall having issues on the last update, but I am on the latest CRG1 now and it's working fine on my N950F.
N1T15H said:
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.
Click to expand...
Click to collapse
same here. Auto brightness not working after update. Hope they will release fix soon
Sent from my SM-N950F using Tapatalk
I ran the sensor tests, and it seems that more than the lux sensor is not responding ...
My heart rate sensor seems to work on a hit-or-miss basis..
SpO2 working fine though.
ghassan haddad said:
do you mean that it has a new functionality that has not been in old phones? I have the Note 4 and it works like a charm, but the note 8 auto brightness works strangely, when I'm in a room with low brightness the screen light goes so dim that I can barely see anything!
Click to expand...
Click to collapse
Try and reset your usage pattern and give it time to learn your usage. You will have to adjust the slider for your preference while its learning. I'm on the latest oreo and have no issues with it.
Reset phone to factory settings..
Issue persists!!
Hello Guys,
Yesterday I received the August 1 Update on my note 8.
After the update, I confirm the matter has been tackled
Screen rotation, auto brightness all working fine now.
N1T15H said:
Hello Guys,
Yesterday I received the August 1 Update on my note 8.
After the update, I confirm the matter has been tackled
Screen rotation, auto brightness all working fine now.
Click to expand...
Click to collapse
That's strange. My auto brightness worked fine up until the latest update. It is the August update that caused the problem for me.
Actually, providinf an update on the matter.
Some days later, situation came back to square one!
Not working:
Light sensor
Heart Rate sensor
Proximity sensor
Gyro sensor
Magnet sensor
Accelerometer
Just fingerprint sensor seems to be working fine.
I was on a trip in Malaysia and was at a Samsung store. They told me this is a very common issue and easily solved by 'software update' but when I went on to the service centre, they denied me since my phone was bought in different country. Phff
If the next OS update doesn't resolve this then I would recommend that you take your device to a Samsung Service Center
Anyone got their unresponsive device working back again ?
This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Edit: vivo pushed an OTA update today, and after installing that, it seems the issue has been resolved. There's no mention of such an issue in the bugs fix list, let's still assume it was a bug.
Edit 2: Well, the problem persists (also deleted attached image of update which did not help resolve the issue).
daftdrift said:
This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Click to expand...
Click to collapse
Just try NOT to set auto brightness ON and see things can improve.
rnjsx100 said:
Just try NOT to set auto brightness ON and see things can improve.
Click to expand...
Click to collapse
Sorry i did not mention I did try that method in the first place of all. We could tell it isn't the auto brightness causing the issue if the status bar and notifications are displaying in normal brightness.
The issue was resolved with an update.
Edit: not really. Sick.