So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
settings - display- blue light filter - custom schedule
vivilxw said:
settings - display- blue light filter - custom schedule
Click to expand...
Click to collapse
Blue Light filter is disabled and schedule is disabled as well. I've tried turning ON the blue light filter when the issue happens and it actually kicks in on top of the other issue and makes it even MORE yellow.
Seems unrelated to that.
Have you checked the sunset to sunrise toggle..?
Anyone having this blue light issue...blue light is enabled. When I turn on phone from sleep mode it takes like a second to switch to blue. Very weird
Sent from my SM-G965U1 using Tapatalk
zeebone said:
snip.
Click to expand...
Click to collapse
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
(ORIGINAL, not needed, left for posterity)
This needs more attention. I know EXACTLY what this is. You came from a more recent Android device that uses Google's own "night mode" settings. I know, because I did too. I came from the Razer Phone and had night mode enabled on that on schedule. After my screen turned a real dank orange color at night, I started looking for the setting and discovered Samsung's "Blue Filter" setting and that enabling it made the orange color even more dank. So I immediately knew that the setting must have carried over when I logged into my google account and carried over my settings.
I have a workaround, but it is just that, it's not a permanent fix and I'm still trying to figure out how to fix it permanently. You need to install System UI tuner from the playstore. Follow the instructions to make the app work by granting permissions using ADB while connected to a PC. This is not root and will not void your warranty as such. From here, you can either just disable "Night Mode" under the miscellaneous tab or you can go to the playstore and install "Nougat / Oreo Quick Settings" which will allow you to add the toggle for "Night Mode" to your quick settings pull down bar. Unfortunately, you have to do this every night to get rid of the ugly orange color.
I've tried disabling the setting on my Razer and syncing everything in my google account from that phone, then restarting my galaxy and hoping that the settings would transfer over, but it hasn't worked. My fear is that I will have to factory reset the Galaxy, go back to Razer, toggle the night mode on and back off. Sync settings, then sign back into my galaxy and hopefully the settings will not come back this time. I just haven't because I don't want to set EVERYTHING back up again, ugh.
If anyone is aware of how to disable the "Night Mode" schedule feature in a different way without factory resetting the device, please let me know. Thanks!
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
cawith said:
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
Click to expand...
Click to collapse
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
lessthanzach said:
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
Click to expand...
Click to collapse
Wish I had waited a little bit longer and had done this. I ended up backing everything up to my SD Card using Smart Switch and then wiping and rebuilding the phone yesterday afternoon. However, I didn't choose to restore from Google and only from Smart Switch, so the night light setting didn't end up carrying over again.
Good to know I wasn't crazy and that my phone wasn't defective.
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
I was all ready to get adb working and use the above workaround, and / or install nova launcher and fix this issue but THIS WORKED.
THANK YOU it has been bugging me for WEEKS.
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
You are amazing! It was the Google play books settings.
Thank you so much! It just started happening last week so I knew that it didn't come from my smart switch settings. Google play books was on night light settings from 10p-6a. I can see my phone again at night without my screen being yellow or without having to restart my phone. Thank you so much!!! I NEVER would've looked there.
Works like magic on my S7. Thanks a lot!
Perfect!
This fixed my problem, so thank you!
Google play book... who would have guessed..
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
zeebone said:
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
Click to expand...
Click to collapse
You might have your blue light filter turned on to a specific time. Mine is set to come on at 6 pm and go off at 6 am. Check that in settings.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Did you tripped your knox warranty, when using this ??..... I want to disable night mode on my note 9.....did adb trigger knox ??? Please advice sir... And thank you
Click to expand...
Click to collapse
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Buddy ur basically a lifesaver. Note 10+ fixed too, can confirm!
Buddy the workaround just saved me at least one trip to SES which is like 30 mins away from my house in Long Island, saved me from erasing the phone and restore it which would definitely be a nightmare and also u just saved my one big annoyance with this phone for the first week of usage!! U are the man!!
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
Vinay_sandy said:
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Click to expand...
Click to collapse
I tried it, both options switched off.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Click to expand...
Click to collapse
Huge thanks as you saved me from factory resetting my new Mi 9 Lite. That's why I love the internet.
Related
Hello,
Anyone have an idea of how to simply turn off LED button back lights?
It seems it could be done as there is already at least one app that uses them for notification.
Here is what I am trying to do:
I've downloaded a desktop alarm clock app that turns the screen back light WAY down so it is not disruptive in a completely dark room while sleeping. But, the buttons remain illuminated.
Basically 8 want to use tasker to launch those clock and turn off the button back lights if the phone is charging and the time is after a certain hour.
I am thinking I could fire off a script with tasked to do thwarting back lights portion of this as well, but I don't even know where to begin.
Any ideas? Thanks!
Sent from my Dell Streak using XDA App
I'm rooted, and use an app called AdjBrightness. Works wonders, and also via menu, you can totally turn off the LED lights.
Hope that helps.
Cool, I will check it out. Ideally I would like to do it automatically, without having to open another app, but this tells me it ostensibly at least doable.
Thanks!
Sent from my Dell Streak using XDA App
If you want the code, just do this from adb or from your phone's terminal.
echo "0" > /sys/class/leds/button-backlight/brightness
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Spleisher said:
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You could always leave your computer on overnight and make a macro that executes the adb command to dim the leds and then executes another that makes them bright again at a certain time.
There must be something similar you can do on the phone though.
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Spleisher said:
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Click to expand...
Click to collapse
Good job, sounds pretty cool
I'm sure many people will find this useful!
Does the louder volume app work with the streak?
SeanH said:
Does the louder volume app work with the streak?
Click to expand...
Click to collapse
No i'm afraid it doesn't. Also, send me a pm next time rather than ask in someone else's thread
I did turne off button's back-light by adjusting the context of "/sys/class/leds/button-backlight/brightness" file from 255 to 0, it works great, but it gets back to normal after phone restart, I even went to properties of the file and removed all the "write" rights, but it won't give in.
1) When going to unlock my phone using the screen pattern, I've noticed that recently the screen rotates. As far as I remember, it has always been in portrait which is the easiest way to quickly unlock -- rather than waiting for it to rotate from landscape back to portrait so i get the pattern correct.
2) Every time I answer my phone it goes automatically to loudspeaker. I keep forgetting and I'll end up deaf. This is very annoying!
3) Sometimes I'll be playing a game or whatever and 'car mode enabled' (something like that) will appear. I click to deactivate it but I didn't actually do anything to activate it in the first place. Why does this keep happening?
Sounds to me (noobie) like it's constantly in car mode or something. How can I turn this off? It doesn't say anything in the notification bar about it.
Thank you.
It sounds like moisture in the microUSB connector. It has a known problem of putting the phone into Car Mode - calls are via loudspeaker.
I would do a Search on here about Car Mode problems. I think a bit of DW40 resolves the issue.
b33p_ said:
1) When going to unlock my phone using the screen pattern, I've noticed that recently the screen rotates. As far as I remember, it has always been in portrait which is the easiest way to quickly unlock -- rather than waiting for it to rotate from landscape back to portrait so i get the pattern correct.
2) Every time I answer my phone it goes automatically to loudspeaker. I keep forgetting and I'll end up deaf. This is very annoying!
3) Sometimes I'll be playing a game or whatever and 'car mode enabled' (something like that) will appear. I click to deactivate it but I didn't actually do anything to activate it in the first place. Why does this keep happening?
Sounds to me (noobie) like it's constantly in car mode or something. How can I turn this off? It doesn't say anything in the notification bar about it.
Thank you.
Click to expand...
Click to collapse
what firmware are you running on the phone?
It should not default to loudspeaker unless car mode is running, check setting phone to make sure that there is nothing is running that shouldn't.
If there is nothing turned on, then it you may have problem with your hardware.
What type of game are you playing, It sounds like during the game there maybe an extra button being pressed by accident.
Cosmic Blue said:
what firmware are you running on the phone?
It should not default to loudspeaker unless car mode is running, check setting phone to make sure that there is nothing is running that shouldn't.
If there is nothing turned on, then it you may have problem with your hardware.
What type of game are you playing, It sounds like during the game there maybe an extra button being pressed by accident.
Click to expand...
Click to collapse
See the attached pic.
Where do I look to see if it's in car mode or not? When it switches on there is usually a notification and I can deactivate it from there -- but the notification bar is empty and there are no unusual icons.
The game is called WordFeud, it's like scrabble.
Thanks for your help.
I searched the forum and can't find how to check car mode.
in another forum (androidpit) i found a hint to try "Dock No-Op" with this "car-mode-problem" :
https://market.android.com/details?id=com.megagram.docknoop
i dont know if it helps
Moreover you can also try out this:
1) factory reset (wipe all?)
2) flash original firmware!
3) take out the battery for an hour or two
4) power on
5) check if all is ok now
if yes:
6) flash whatever you want
raziel19 said:
in another forum (androidpit) i found a hint to try "Dock No-Op" with this "car-mode-problem" :
https://market.android.com/details?id=com.megagram.docknoop
i dont know if it helps
Moreover you can also try out this:
1) factory reset (wipe all?)
2) flash original firmware!
3) take out the battery for an hour or two
4) power on
5) check if all is ok now
if yes:
6) flash whatever you want
Click to expand...
Click to collapse
I'll try that app today. I won't be happy if I have to factory reset Thanks.
That app didn't do anything unfortunately
b33p_ said:
I searched the forum and can't find how to check car mode.
Click to expand...
Click to collapse
go to voice program in your apps the one by vilango, it has a car mode toggle.
it will let you see if it is on or off.
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
If you don't know how to launch an activity, you can do the following:
Via ADB:
Code:
adb shell "am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences"
Via Terminal on your phone:
Code:
am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
I haven't done any more checking, but I'm guessing this is just a flag that could be set in sys/devices/blah... by init.d script on boot as well.
If you prefer a gui, there are plenty of launchers out there that can select an activity to start. I actually had it set up as a long-press pie on LMT while I was playing with it.
It seems (on my phone, at least), that the app wasn't as good at turning it back on, but you can just clear the app data/cache on "Content Adaptive Backlight Settings" in application manager, reboot, and you'll be back to stock behavior.
Sorry I didn't post this sooner. I've been too busy playing with the G2!
this doesn't work.
I've tried this weeks ago. simply telling the app to turn it off does nothing, as it's still on no matter what. deleting the app produces the same exact effect.
in the build prop, the line pointing to cabl is set to false. therefore it's really not even reading what the app is saying it seems.
I believe it's a kernel issue that can only be solved once we get a custom one.
again, this isn't a fix and doesn't turn it off at all sadly.
Sent from my VS980 4G using Tapatalk 4
https://www.youtube.com/watch?v=slwkFhpiYbs&feature=youtube_gdata_player this video was made when it was set unchecked and set to off.
Sent from my VS980 4G using Tapatalk 4
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Is this issue on all carrier versions?
I use auto-brightness and the annoyance I have is that it doesn't change brightness right away when entering different lighting environments. It either takes time or doesn't change at all until I uncheck/check the auto-brightness setting.
xdabbeb said:
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Click to expand...
Click to collapse
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
jayochs said:
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
xdabbeb said:
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
Click to expand...
Click to collapse
I believe the original Nexus 7 had this feature in the kernel too. However, in custom kernels you could use Trickster mod to toggle the feature off. I think the kernel devs had to expose the setting though, so maybe we'll get this taken care of if we can get a custom kernel.
Here are some build props for Qualcom devices that control the CABL
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
By adding / editing these lines in the build.prop you should be able to adjust as noted in the lines.
And yes, it is in the kernel.
Dont know why LG has an app for it?
Scott, I sent you a message on hangouts but in my build prop, i don't show a 1 for the cabl setting.. i show false... as if it's already turned off in the build prop. I changed it to true once and it didn't do anything. those two top settings seem to be what's in the app.. you can check a box to turn it on and off (the first line) and then you can set the degree to which it handles the cabl (second line.) I've messed with both in the app and it did absolutely nothing... does the kernel need to be changed as well?
Sent from my VS980 4G using Tapatalk 4
xdabbeb said:
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
Click to expand...
Click to collapse
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
we do want to bc it causes horrible screen flicker issues. you can be sitting on a pic and it doesn't know what to do so it flickers badly
Sent from my VS980 4G using Tapatalk 4
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
I did not know about the contrast ratio on these screens. Makes sense what you are saying.
However like Jay said it does not react smoothly or at appropriate times.
Some will need to edit the kernel code to fix this.
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
Yep. What @jayochs and @scrosler said. What you wrote does make sense, and I had noticed that it behaves the opposite of the CAB implementation on AMOLED screens (where it dims on lighter colored content)...so that gives even more credence to what you're saying, but the implementation is a little buggy. It transitions abruptly and causes the "flickering" that many have reported. I certainly wouldn't mind having it enabled if the transitions were slower/less frequent, but it's kind of annoying as it is. I never was able to find a way to disable it in the stock kernel anyway, so hopefully it can be fixed one way or another now that the source is available. Still the best phone I've owned!
So any success with any method here or elsewhere?
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
antinorm said:
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
Click to expand...
Click to collapse
i'm thinking it's CABL, but it's kernel level, NOT software level, which is why disabling it does absolutely nothing.
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Rayan said:
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Click to expand...
Click to collapse
it's not an issue with auto brightness, that's a completely different problem.
this is the content adaptive backlight problem.
so no solution was ever found for this (besides a new kernel)? my phone doesn't flicker but on the brightness below 50% i can notice it's trying to readjust itself slightly once in awhile (with xda app or play store for example).
Encountered this issue as well. So, the cause of this has something to do with the software and not the hardware? Don't want to send my phone back just to receive yet another problematic set.. I set my screen brightness to 38 which it flickers on certain photos and apps. Bumped it up to about 45 and it seems to have stopped.
I've noticed that no matter what setting I have it on, my tablet (M5 8.4) automatically lowers the screen brightness in Chrome and YouTube, but more noticeably in Chrome.
Any way to disable this?
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
thref23 said:
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
Click to expand...
Click to collapse
I've checked every possible setting, and read online everywhere, but to no avail. It also dims in Firefox. It dims as soon as you go into the app. After an online search, I found many Huawei owners with EMUI 8.0 having this issue. There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Funny. Would love a solution as well as this is rather annoying
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
thref23 said:
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
Click to expand...
Click to collapse
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Click to expand...
Click to collapse
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
kev1807 said:
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
Click to expand...
Click to collapse
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
xKevin said:
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
Click to expand...
Click to collapse
hmhm. I was quite sure it was a System process - since the "bug" (dunno whether you read the thread on keyboard and brightness ...) appears with the system-icon when in Desktop-Mode ...
Great. there is a fix for this. now I need a non-root fix ... :-/
Yes, try the app ilux. Let that control brightness.
Steffe89 said:
Yes, try the app ilux. Let that control brightness.
Click to expand...
Click to collapse
Do you have a link to this app? I can't seem to find anything relevant when searching for ilux.
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Up until now I thought a reboot would bring the "wonderful" feature back ...
How comes that you mention a reboot is needed?
How do you disable it? I can only do a force stop
I'm not sure how to disable it without root (I imagine adb might work). With root, most use Titanium Backup to freeze it. I'm using Service Disabler to disable the associated services instead. Service Disabler is awesome if you are rooted, underrated app and great for EMUI because, for example, you can disable individual parts of the Tablet Manager app without breaking the features you want.
You might not need to reboot. When I initially froze it using Xposed Edge Pro, but didn't reboot, it didn't change anything for me. Could have been due to Xposed Edge Pro.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
scott.eden said:
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Click to expand...
Click to collapse
Was there any negative outcome from disabling power genius?
krisu253 said:
Was there any negative outcome from disabling power genius?
Click to expand...
Click to collapse
None for me.
thref23 said:
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Click to expand...
Click to collapse
I cannot find Power Genius?
I can confirm following the above article will allow you to remove the power genius package from the Mediapad M5 8.4 on EUMI 9.1 without root.
Thank you sooooo much... You can't believe how annoying this was. No need to even reboot either and it doesn't return if you do.
Now I just need a way to too keep the custom 740DPI after reboot and this tablet will be perfect
Can anyone tell me how to change the screen timeout/sleep time on the M5? I've tried display, battery and security settings but it doesn't appear to be in any of them. It's a real pain trying to read emails, news, flipboard etc with the standard (30 seconds?) timeout.
mickrick said:
Can anyone tell me how to change the screen timeout/sleep time on the M5? I've tried display, battery and security settings but it doesn't appear to be in any of them. It's a real pain trying to read emails, news, flipboard etc with the standard (30 seconds?) timeout.
Click to expand...
Click to collapse
If it's not under >Display>Sleep, you are in trouble!
Should be there, try again!
kupa said:
If it's not under >Display>Sleep, you are in trouble!
Should be there, try again!
Click to expand...
Click to collapse
Just discovered it is under Display/Sleep. But Sleep option is greyed out.
*UPDATE* Aha! Power saving mode was on. It must be enabled by default because I can't think why I would've enabled it. Sorted now.
mickrick said:
Just discovered it is under Display/Sleep. But Sleep option is greyed out.
*UPDATE* Aha! Power saving mode was on. It must be enabled by default because I can't think why I would've enabled it. Sorted now.
Click to expand...
Click to collapse
I've had the CMR-W09B for a week now and found that when I change the sleep time it always reverts to the default 30 seconds after a while. Power saving mode not active. Installed Screebl Pro to manage timeout, but unlike my many other devices using the app, it seems to be overridden by the system and doesn't work. Whether Screebl is active or not, or what I set the timeout to, the timeout returns to 30 seconds.
This happening to anyone else, or am I just special?
I got it just turn off your battery savers
How to change the battery in Huawei P 10 lite?