Related
As the title says my GFs 10.1 will go full brightness at random times. Only way to change it back is to go into setting. The slider is all the way down but have to slide it to full then back down. Any ideas guys?
The fix is: Go TO SETTINGS, SCREEN, AUTO ADJUST SCREEN POWER, UNCHECK. Thanks bd85!
Just-in-time said:
As the title says my GFs 10.1 will go full brightness at random times. Only way to change it back is to go into setting. The slider is all the way down but have to slide it to full then back down. Any ideas guys?
Click to expand...
Click to collapse
Is it set to auto-brightness? Sounds like it.
No its not on auto that was the first thing I checked when she told me.
stock room or something else? rooted?
Can you Post Questions in the New Galaxy Q&A Forum Thanks
Moving to Q&A
eugene22n said:
stock room or something else? rooted?
Click to expand...
Click to collapse
Its full stock.
mine too
it doesnt happen that often but it also happens to me i would be watching,a movie and out of nowhere its like if im facing the sun....
capufo said:
it doesnt happen that often but it also happens to me i would be watching,a movie and out of nowhere its like if im facing the sun....
Click to expand...
Click to collapse
Yeah its weird how random it is.
Just-in-time said:
As the title says my GFs 10.1 will go full brightness at random times. Only way to change it back is to go into setting. The slider is all the way down but have to slide it to full then back down. Any ideas guys?
Click to expand...
Click to collapse
I have had this issue as well when using auto brightness function. Only when viewing photo albums. Very annoying. I no longer use the auto brightness function now. Little issues like this drive me crazy. Add this to the keyboard lag and other small issues and i start to question the purchase.
Thankfully i found this site to help me realize its not just me...misery loves company. Lol.
Have you guys tried to shut off the option in setting that's can analyze the screen color and more and the adjust the screen for power savings.
I have noticed what you are mention. And it only appears in movie's because the picture change often so the tab tried to compensate the colors often.
Go TO SETTINGS, SCREEN, AUTO ADJUST SCREEN POWER, UNCHECK.
And I am not talking about the auto brightness that you can access from clicking on the lower right part of your screen
Sent from my GT-P7510 using XDA Premium App
bd85 said:
Have you guys tried to shut off the option in setting that's can analyze the screen color and more and the adjust the screen for power savings.
I have noticed what you are mention. And it only appears in movie's because the picture change often so the tab tried to compensate the colors often.
Go TO SETTINGS, SCREEN, AUTO ADJUST SCREEN POWER, UNCHECK.
And I am not talking about the auto brightness that you can access from clicking on the lower right part of your screen
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
That seemed to be it. Didn't think to check that since the Xoom doesn't have that setting. One thing i wish the xoom had was the whole different wallpaper for lock screen thing the 10.1 has.
Since the OTA I can't get my screen to dim enough. Does screen filter save battery.
Sent from my DROID RAZR using Tapatalk 2
i use screendim and i noticed i do save battery.
Sent from my A100 using xda premium
Yea I always wondered this but can anyone be certain for sure
Sent from my SAMSUNG-SGH-T989 using XDA
scuzzbag87 said:
Yea I always wondered this but can anyone be certain for sure
Sent from my SAMSUNG-SGH-T989 using XDA
Click to expand...
Click to collapse
why not try it yourself?
Sent from my A100 using xda premium
Try this app called LUX. It allows you to customise brightness.
The paid version allows dim below "0%".
You can set it to something like -40% in a dark room, and normal brightness when you're outside. Basically, it's like auto brightness which you can customise. This is so you don't have to on/off a screen filter app.
And yes lower brightness saves battery.
Nikorasu said:
Try this app called LUX. It allows you to customise brightness.
The paid version allows dim below "0%".
You can set it to something like -40% in a dark room, and normal brightness when you're outside. Basically, it's like auto brightness which you can customise. This is so you don't have to on/off a screen filter app.
And yes lower brightness saves battery.
Click to expand...
Click to collapse
LUX is awesome!!! TIP OF THE YEAR!!!
Could we get a market link?
Can't seem to find it, just get light meters and cheap screen flashlights in search results.
Sent from my EOS Xoom using XDA Premium HD
https://play.google.com/store/apps/details?id=com.vito.lux&hl=en (paid)
https://play.google.com/store/apps/details?id=com.vito.lux.free&hl=en (free)
Yep.
Check what is using your battery on your phone.
You will notice that screen mostly use up the power
Sent from my XT910 using xda premium
Nikorasu said:
Try this app called LUX. It allows you to customise brightness.
The paid version allows dim below "0%".
You can set it to something like -40% in a dark room, and normal brightness when you're outside. Basically, it's like auto brightness which you can customise. This is so you don't have to on/off a screen filter app.
And yes lower brightness saves battery.
Click to expand...
Click to collapse
i just tried this app and it killed my battery faster than using screen dim because this program is constantly running on the background. what settings are you using on it?
Sent from my A100 using xda premium
I'm an author of a program named Custom Auto Brightness, currently it's not under-dimming automatically but it'll be added soon.
Meanwhile, could I ask some of you to test it? I'll provide apk if anyone agrees. The problem seems that PoverVR GPUs seem to have problems with screen shading like in Screen Filter and the like, I'd like to check if I were able to circumvent the problem or not.
jahciple said:
i just tried this app and it killed my battery faster than using screen dim because this program is constantly running on the background. what settings are you using on it?
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Having something run in the background doesn't mean it's using a significant amount of phone's battery. The amount of battery saved from low brightness is much much more than the battery used for Lux to compute brightness level. Of course I did not test it, but it is common sense: as the display uses most of the battery. You can check your battery use in settings.
Lower brightness, longer battery. Lux doesn't even appear in battery use. My screebl app, which constantly uses CPU to check for orientation uses only 3% in battery use.
Download ES task manager to see what's running on startup, and look at what you do not use, it'll probably shock you.
As for my settings in Lux, I set it to dynamic and so far my linked samples are:
Lux ----- Brightness
2 --------- -40%
25 -------- -25%
550 ------- 20%
20000 -----100%
Been using these settings for a couple of weeks, and no problems. I have also added picture viewers, camera apps, and video players to ignore/compatible list.
Another tip to save battery which most already know: use setcpu to underclock your phone when screen is off to 300max/300min, or 600max/300min if you use your phone for music. Needs root though.
well i noticed after i wake up in the morning the battery has gone down so much more after i started using lux. i disabled it and everything was better. it probably used about 10% more battery in 6 hours.
Sent from my DROID RAZR using xda premium
I can say the same about battery drain. Been off full charge now for an hour, already down @ 78%.
Sent from my XT910-Rogers using XDA Premium.
I use the brightness control from widgetsoid. I leave it set at 10% and my battery still hase 40% or more charge after all day and evening, even though I read on the train for about 1 1/2 hours and do moderate email ---huge difference from auto brightness setting. Tap the widget to go to auto brightness when outdoors (although, frankly, I go days without using it outdoors so this works great for me).
Hi guys!
I just bought LG L5 II. It's still UNrooted, so I need a brightness control that doesn't require ROOT privileges. The reason is quite simple - the minimum brightness is too bright, when you're NOT outdoors (if you're outdoors, you better set the brightness on 40-60%). I'm posting here because it doesn't matter If I have Motorola or LG - the principle is the same - display is too bright.
I've installed Screen Filter. In this topic some of you lot are chatting about Lux app - is it better than Screen Filter? What's your opinion? Obviously I want to save some battery and to use my display at night or indoors (without causing pain to my feelings and emotions ).
I will test Screen Filter for couple of days and see what's what. Hope some of you have tested it already and give me some tips. Cheers!
PS: Sorry for reviving this old thread mods, found it on Google, dunno if there is a newer one 'bout the same problem.
I think Lux and other screen brightness modification apps use a transparent layer over the main ui and we actually darken and brighten that layer running over the Ui instead of setting a further down limit to the screen LCD power value. This might be the reason that using Lux or any other screen dimmer app consumes more battery~ the screen LCD uses same power and in addition an extra app is running in the background continuously . It is only the transparent layer that darkens to save your eyes in dark atmospheres~ LCD power consumption remains the same.
^^ This right here is what I've been wondering for some time, because I suspect that at least some of those apps work that way, and is also likely imho what the OP was really asking. Yes, everyone knows the display is by far the largest drain on battery, and so lowering the brightness helps with that, so the question is does the app in question actually do that or does it simply provide a customizable overlay, as the poster above me speculates. Because if an app is doing the latter, not only will it not conserve battery it will actually drain it more, to a point, because the actual brightness is still the same (even if you don't "see" it) and the app itself is running all the time. Granted its consumption may be very low, but the point is that scenario certainly wouldn't SAVE any battery. And my guess is that within this group of apps that are the focus of this thread, some are simply overlays and some (the very technical ones) are the real deal, and it's a question of knowing which to pick. What I'd really love is for someone who is very technical in this area to see this thread and provide some definitive info.
GuccizBud said:
^^ This right here is what I've been wondering for some time, because I suspect that at least some of those apps work that way, and is also likely imho what the OP was really asking. Yes, everyone knows the display is by far the largest drain on battery, and so lowering the brightness helps with that, so the question is does the app in question actually do that or does it simply provide a customizable overlay, as the poster above me speculates. Because if an app is doing the latter, not only will it not conserve battery it will actually drain it more, to a point, because the actual brightness is still the same (even if you don't "see" it) and the app itself is running all the time. Granted its consumption may be very low, but the point is that scenario certainly wouldn't SAVE any battery. And my guess is that within this group of apps that are the focus of this thread, some are simply overlays and some (the very technical ones) are the real deal, and it's a question of knowing which to pick. What I'd really love is for someone who is very technical in this area to see this thread and provide some definitive info.
Click to expand...
Click to collapse
This is partially right. If you have an LCD, you are just dimming your screen, not saving battery in the process. If you are using a LED screen, the app's will save battery since LED pixels can be individually lit. Using black or battery saving backgrounds will also help your battery life on LED screens. This is one of the reasons why LED screens are much more preferred than LCD.
I was messing around with the settings on my phone to try and eek out some more battery life. I noticed with the stock battery monitor that the screen was using the most battery (as is expected) so I turned the brightness setting all the way down using the slidebar in settings.
Then I went into the Sprint Zone app, clicked help, then my device, then power controls. There it shows what is turned on on the phone and a general breakdown of how much those things are drawing on the battery (kinda nifty). On the lowest possible brightness setting it says it's at 11% and that that's "medium" usage. Is there a way to get screen Brightness lower? I just find it odd that it still registers as medium usage on its lowest setting...
Also has anyone noticed that on the "Automatic" screen brightness setting that the screen doesn't go as dark as it could go when there is a low light condition? For example if I'm sitting in the dark with auto brightness on, I can turn it off then make the screen darker manually than it would go on auto.
Any thoughts? Or fixes?
Sent from my EVO using xda app-developers app
moses2303 said:
I was messing around with the settings on my phone to try and eek out some more battery life. I noticed with the stock battery monitor that the screen was using the most battery (as is expected) so I turned the brightness setting all the way down using the slidebar in settings.
Then I went into the Sprint Zone app, clicked help, then my device. There it shows what is turned on on the phone and a general breakdown of how much those things are drawing on the battery. On the lowest possible brightness setting it says it's at 11% and that that's "medium" usage. Is there a way to get screen Brightness lower? I just find it odd that it still registers as medium usage on its lowest setting...
Also has anyone noticed that on the "Automatic" screen brightness setting that the screen doesn't go as dark as it could go when there is a low light condition? For example if I'm sitting in the dark with auto brightness on, I can turn it off then make the screen darker manually than it would go on auto.
Any thoughts? Or fixes?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Try rootdim. Also, the screen brightness is going to be mostly controlled by the kernel, so try using a different kernel or build one from source.
sn0b0ard said:
Try rootdim. Also, the screen brightness is going to be mostly controlled by the kernel, so try using a different kernel or build one from source.
Click to expand...
Click to collapse
There's source?
Sent from my EVO using Tapatalk 2
It's not in the kernel, it's in an xml or something. There are seven brightness levels (I think it's seven) based on lumens, and there's an associated screen brightness value assigned to each on a scale of 0 to 255. Stock auto brightness levels set the bottom three levels to the same brigness value. I think it's 63. Setting the brightness manually, you can go as low as single digits, maybe even zero.
fachadick said:
It's not in the kernel, it's in an xml or something. There are seven brightness levels (I think it's seven) based on lumens, and there's an associated screen brightness value assigned to each on a scale of 0 to 255. Stock auto brightness levels set the bottom three levels to the same brigness value. I think it's 63. Setting the brightness manually, you can go as low as single digits, maybe even zero.
Click to expand...
Click to collapse
That's cool you can edit the XML files, but how can screen luminosity or display not be part of the kernel or kernel modules? I have an HD2 with CM7 on it, and through installing different kernels and whatnot, I can get different features for display like render effect, auto brightness, and whatnot. Is this only just for sense ROMs then?
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
Kcarpenter said:
There's source?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Not right now there isn't. Would be nice if there was.
fachadick said:
It's not in the kernel, it's in an xml or something. There are seven brightness levels (I think it's seven) based on lumens, and there's an associated screen brightness value assigned to each on a scale of 0 to 255. Stock auto brightness levels set the bottom three levels to the same brigness value. I think it's 63. Setting the brightness manually, you can go as low as single digits, maybe even zero.
Click to expand...
Click to collapse
So maybe the stock rom doesn't let you zero it out? It's posting the lowest value as 11% as read by the Sprint Zone app. Maybe they do it as a safeguard against setting it too low and not being able to see the screen to turn it up when it gets in a brighter environment?
That's a funny thought, I could see me kicking myself over something like that. Would be nice if we could make that call on our own though, wonder how dim it is...and why not make the auto brightness go to the lowest setting (or perhaps even lower than the stock setting)? At least then it would ramp back up as needed.
Sent from my EVO using xda app-developers app
Did you try rootdim? I'm pretty sure you can dim the screen lower than stock with it on this phone. I've only used it on my HD2, but it worked well with it and It's free.
Nm rootdim only allows the screen to go down to a value of 30. You can set lower values, but it doesn't change the brightness.
Sent from an EVO 4G LTE using Tapatalk 2.
moses2303 said:
So maybe the stock rom doesn't let you zero it out? It's posting the lowest value as 11% as read by the Sprint Zone app.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Correct - stock only lets the brightness go down to 11%. I'm not sure if auto brightness will ever set it that low though, doesn't seem like it does.
jpbme said:
Correct - stock only lets the brightness go down to 11%. I'm not sure if auto brightness will ever set it that low though, doesn't seem like it does.
Click to expand...
Click to collapse
Yea that's what I'm saying it doesn't go to the minimum. I mean I'm sure the battery savings isn't much, but another usefulness of it going that dark is when you check your phone at night in the car you don't want the phone to be all lit up inviting attention.
Sent from my EVO using xda app-developers app
moses2303 said:
Yea that's what I'm saying it doesn't go to the minimum. I mean I'm sure the battery savings isn't much, but another usefulness of it going that dark is when you check your phone at night in the car you don't want the phone to be all lit up inviting attention.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I think 11% is probably dim enough for most cases. If you have a dark background that will help with the car situation. The only time I find it still too bright is when I'm laying in bed at night. I haven't rooted yet so I can't comment on the solutions others suggested but give that a try. You probably won't save that much battery though unless you're in the dark a lot.
Oh - and don't text and drive
I use an app called screen filter at night. It allows the screen to get MUCH dimmer.
jpbme said:
Oh - and don't text and drive
Click to expand...
Click to collapse
Haha I knew that was coming :thumbup:
Sent from my EVO using xda app-developers app
I have the 5.0 and while I love the large screen, I find the screen can be too brighy even with the brightness at the lowest setting. Is the device hardware limited or is there anything that can be done?
Try screen filter: https://play.google.com/store/apps/details?id=com.haxor
Sent from my Nexus 7 using XDA Premium HD app
This has been a pain for me as well, and I make due with screen filter. I just wish there was some way to modify the system so you could actually lower it more and save battery.
Sent using Tapatalk
I have almost set up my development enviroment. So one more feature added to do to things
Send from samsung galaxy s wifi 5.0 running paranoidandroid.
Supermaster34 said:
Try screen filter: https://play.google.com/store/apps/details?id=com.haxor
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
if i'm correct, what screen filter does to make the screen looks dimmer is it "puts" a black image on top of the screen, so it always runs in the background to make the screen dimmer
on my tf300 i use rootdim, it actually lowers the brightness settings the way samsung/android/system does, the difference it lowers more than the system allows, even to completely black. so after you use it to lower the brightness, it doesn't have to always run like screen filter -> no (or at least less than screen filter) battery drain
I have had great success using RootDim on my Acer A500 (rooted, stock ROM). However, I could not get the brightness to go any lower than the system minimum when trying it on my Galaxy Player (5.0, rooted, stock ROM).
If you're on another ROM maybe you'll have better luck or there's always the Screen Filter method. Or if anyone else knows of a way to do this I'd be curious what worked for you.
yeah, your best bet is a third-party app that lets you specify the actual brightness level.
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.