Related
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'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.
Hi
I have several questions :
1. I already experienced that the night clock doesn't appear instantly when you put the watch onto the charger. Sometimes it takes a time till it appears.
2. What about screen burn from the night clock? I read about it in the forum for the first gen moto 360. Is it still a issue with the 2nd Gen 360?
3. There are wear developer options in the developer options. And there is the option "burn-in protection" (I hope it's called that way in English, I've got it on German) but it won't activate even after reboot as it tells me to do.
XxM4tzexX said:
Hi
I have several questions :
1. I already experienced that the night clock doesn't appear instantly when you put the watch onto the charger. Sometimes it takes a time till it appears.
2. What about screen burn from the night clock? I read about it in the forum for the first gen moto 360. Is it still a issue with the 2nd Gen 360?
3. There are wear developer options in the developer options. And there is the option "burn-in protection" (I hope it's called that way in English, I've got it on German) but it won't activate even after reboot as it tells me to do.
Click to expand...
Click to collapse
I disable the night clock by turning on theater mode (double click the side button). But I do this because it seems to fix the heart rate monitor from tracking the apparent 100BPM of the charger lol.
I use the Slumber app that automatically turns the screen off as soon as you place the watch on the charger.
I don't think there will be any burn in issue, since Moto360v2 have LCD screen. Burn-in have place on OLED screens only (Huawei Watch for example) since they have organic diods which degrade over time. LCD don't have this issue at all because they have one backlit light for all pixels and 'rotating' pixels. With LCD screens nothing is affected by the picture on the screen (technically). With OLED screens each pixel emits light on its own, therefore degradation of pixels is dependant on the picture on the screen (whether this particular pixel emits the light most time or not) = burn in.
Therefore night mode on Moto360 can be used safely for as long as you wish.
morpheusgt said:
I use the Slumber app that automatically turns the screen off as soon as you place the watch on the charger.
Click to expand...
Click to collapse
Hola
I tried this slumber app but it did not turn my screen off during charging. Yes, I did launch the app from the watch and ensured that it was enabled.
Am I missing something?
Thanks.
"So what you want me to do 'bout that?"
QAM said:
Hola
I tried this slumber app but it did not turn my screen off during charging. Yes, I did launch the app from the watch and ensured that it was enabled.
Am I missing something?
Thanks.
"So what you want me to do 'bout that?"
Click to expand...
Click to collapse
The button to enable/disable Slumber wasn't very intuitive to me. I actually disabled it when I wanted to enable it, so you may have the same problem. Try toggling the setting the other way around.
also, incase anyone noticed, slumber only puts a black overlay on top of the clock. the screen is still lit up at night, but it's black. incredibly stupid on Motorola to not let us shut off the screen.
Sent from my Moto X Pure Edition
Yes there is a problem and a big one... my watch with less than 5 months old are all burned now
Stupid setting just kill the watch
shaneledford said:
I disable the night clock by turning on theater mode (double click the side button). But I do this because it seems to fix the heart rate monitor from tracking the apparent 100BPM of the charger lol.
Click to expand...
Click to collapse
That's the answer. Why is anyone doing anything else?
Sent from my Nexus 5X using XDA-Developers mobile app
bobby janow said:
That's the answer. Why is anyone doing anything else?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Because this no longer works since one of the updates
shaneledford said:
Because this no longer works since one of the updates
Click to expand...
Click to collapse
The most recent updates fixed it. I use it every night.
Kinsman-UK said:
The most recent updates fixed it. I use it every night.
Click to expand...
Click to collapse
Correct. It was the one before the last one. Every night here too.
Sent from my Nexus 5X using XDA-Developers mobile app
I put my watch in Theater mode (swipe down from the top, then swipe left) and the face stays off until I remove the watch from the charger and press the button to wake it.
Just wondering what app and settings you guys use as oreo doesn't allow overlay so night screen isn't effective anymore.. Thank you
I don't know which app are you using, but Oreo does allow overlay, you just have to give each app you want to overlay the permission to do it.
I tried using Twilight and Night Screen from Play Store and they both work well.
Night screen on oreo has bad image retention but naugat it didn't..
Cf.lumen works ok for me. Not nearly as good as with root access, unfortunately.
boxes said:
Cf.lumen works ok for me. Not nearly as good as with root access, unfortunately.
Click to expand...
Click to collapse
I tried all apps including cf.lumen but none worked
lg g5 h860
You might want to wait a couple of hours or a day. The image retention took a day on my h850 to disappear with cf.lumen under oreo (with root). So, dont give up if it does not disappear immediately.
jaggyjags said:
As you all might now, many models of the LGG5 suffer from image retention. There are some ways to fix it but wanted to create a thread which should probably get pinned for easy access.
Solution is simple, image retention is created by some pixels of our screen (normally at the corners of our device) when they are forced to brighten too much, we need to darken slightly the screen, lowering brightness does not help as pixels are still fully opened and this is what causes image retention. (I'm not too technical about this but I hope you understand what I'm saying)
An excellent app to fix is is CF.Lumen by chainfire. Rooted or not, it will still work.
https://play.google.com/store/apps/details?id=eu.chainfire.lumen
Set custom filter and apply a darkening one to a value that fixes your problem. My issue got fixed with a value between 5-7%, I had a severe problem.
The only price you pay for this fix is around 5% max brightness which I certainly don't notice. Colors remain the same.
View attachment 4556982
View attachment 4556983
View attachment 4556984
And everything fixed, press and hold on the notification bar and disable it if it annoys you.
Click to expand...
Click to collapse
Follow these directions.
Night screen with oreo works very well for me.
Hi, first off i want to start off by saying this.. ive had this device since April 29, 2020 and the issue has been noticeable ever since i got it, but it has gradually gotten worst. It usually happens when im browing in chrome or just using any kind of app for more than 3-5 minutes. Its gotten to the point where i literally just go into twitter browse my timeline for like a minute or two and i can noticeably see some tweets and the bottom navigation bar. Its so ridiculous that i started looking for threads and stuff on how to fix this issue but couldn't find anything until recently that i found a user on this forum explaining you can get rid of this by installing a rom on the device. For now im using an app called ghost screen and lowered the level of the intensity to 8% and the dim level to %8. That has fixed it but i don't feel like using the app all the time on the background. Can anyone recommend me the best rom i could use to fix this god forsaken issue? for now the only rom that im aware that i can fix this is pixel experience and just changing the color calibration on the display options. Is there a better rom that i could get that can do this too?