Before ICS one of the stranger "features" I noticed was that the browser had its very own brightness setting. Until recently the mindset of the person who thought that little gem up (someone who must LOVE changing multiple brightness settings when ambient light changes) was just a curiosity, because, afterall, opera worked better than the standard browser anyway.
But now that this fantastic idea has spread to other apps (like the media player) it has become more than annoying - is there an easy way to stop this short of custom roms or modifying the apps in question?
YOu can use smart screen filter manually, havent found any apps to do it automatically. interesting..!!
I have a couple of "issues" with the phone. Not sure if its software related or hardware related. Maybe you guys can check on yours too see if it happens. This is all on stock ATT rom
It seems the One has "dynamic contrast" enabled by default. When scrolling on webpages, for example, if I come to an area with a dark advertisement, the brightness adjusts very slightly most of the time. Thats all well and good but the annoying thing is that it does it in steps causing quick blinks of the backlight. Its most pronounced at medium brightness. The same "blinking" happen when autobrightness wants to set the brightness to a very low level . It does it in very discrete steps and it takes a long time for the brightness to settle to its minimum.
If i set my brightness to 50% (most prevalent when the slider is under the "t" in brightness) I get a VERY subtle, but constant pulsating of the backlight. Again, Its a very subtle but my eyes pick it up regardless and its distracting as hell. I wouldn't mind it if autobrightness didn't hit this brightness level, but it does sometimes indoors. The effect is best seen on a mixed white and color screen, like a homescreen with a white widget and most websites. If the brightness goes a bit above or below this level, the pulsing goes away . Anyone else seeing this? maybe it happens at a different brightnesses on different screens.
Thanks
I noticed this when watching a video today. Maybe it only happens if you have autobrightness on?
Sent from my HTC One
It happens with autobrightness off for me. I actually tested it a bit more. I happens on a variety of backlight settings depending on what's on the screen.
At approx. 33% brightness (im using an app called screen adjuster to set the system brightness to a specific value), the screen does heavy pulsating on an all white image. For example, if I go to "about:blank" in the web browser. I can be seen on a desktop screen with a white widget or the settings menu.
Same thing at 40. Worst is 33% though. I have a feeling its dynamic contrast going haywire at certain brightnesses. If you turn the screen off then on, it doesnt do it for a second or 2, but then it will start. I haven't been able to find a demo unit anywhere around me to test this out. So if someone can check this on their device, I would appreciate it. Please use Screen Adjuster to get a definitive reading on the brightness. (Use the slider in "system brightness" to set it to a specific brightbess) and go to "about:blank" in the default browser
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
shep98 said:
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
Click to expand...
Click to collapse
Thanks for the response. I ended up looking at 4 more devices at 2 different stores and they all had the flicker. The sales associates even saw it. I got tired of doing exchanges and I ended up reversing my upgrade. Im going to wait and see what happens with this issue. Hopefully it gets sorted out with a firmware update, because otherwise its an awesome phone. Its a shame that the $100 trade-in offer is going to end by then and I wont be getting a free medialink device, but atleast i'd be able to get it in black, which is what I originally wanted.
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Mr Sliff said:
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Click to expand...
Click to collapse
In addition to the phones I exchanged, every display model that I've come across has had it. I'm was a bit surprised at first that not many people have come across this. I'm starting to think that maybe the One has a PWM backlighting, which some folks are sensitive to and some don't even notice. I'm in the former category and I think you are too. It a shame really that this problem exist. Besides that, I couldn't find any other faults with the phone. It was perfect in every other aspect
I've run Into the same exact behavior using the HTC droid DNA with both sense 4+ and sense 5 ROMs. I smell tomfoolery afoot.
Screen Flicker
I'm glad I'm not the only one that has noticed this. It doesn't stay that way very long for me, but it is quite annoying. Seems to happen when there's a white or light-colored background the most. So I guess there's nothing specifically wrong with my phone and we'll either have to live with it or wait until someone figures out how to fix it?
I guess most people don't notice this.m it's extremely irrational going between this and my tablet and having the black.ighting flashing in my face when I scroll through webpages.
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.
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
more than that:
can only set one volume at a time.
either portrait or auto, you can't force landscape like in KK.
animations are fluid, but the functionality isn't. My opinion is, if the device has extra power that it can use to make things animate, slide and fade all over the place, better to put that extra power into making the device perform faster. Anyone here who prefers prettier animations instead of faster functionality?
low resolution screenshots in the recents screen. wat. Seriously... wat? Also, the way they've made it it is faster to just go to the apps screen and open whatever app i want, instead of waiting for the recents screen to load and then scroll awkwardly through the programs... Also, you can only see three recent apps. On a device with 6" of screen. three. think about it.
Also... what is the point of having screenshots, anyway? icons are faster, easier to distinguish, take fewer resources and smaller area on screen.
I agree fully on the recent apps screenshots. The blurry images are embarrassing and don't at all go with the clean/sharp theme of everything else. I don't understand why they've made it low res, can't be for performance given no restraint or need anywhere else. Bizarre!
There is over-prettying. For example, the stupid screen swipe up to unlock (after hitting the power button already), the sparkles are just so unnecessary, it is one of the few places the phone actually seems to struggle pulling off the effect.
At the moment my biggest problem is with Yahoo Mail. The account does not seem to auto-sync despite all the settings being correct and even when I force the sync manually the notifications don't show. I've uninstalled and reinstalled, most likely Yahoo to blame, their webmail is always breaking but never ever had a single issue before with KK. This is problematic because it is effectively no longer push email, I have to manually check 50 times a day.
My biggest annoyance is the inability to reclaim the Google search bar area in the Home Screen. I don't want that search button, why can't I use that space, and why a stupid dot to represent the pages of the Homescreen when I only have 1.
Is there actually anything different/new on the backend? My issues aren't severe enough to go back to KK (yet) but seeing what I see, I would have no problem whatsoever buying an Xperia Sony will not upgrade beyond KK.
jess91 said:
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
Click to expand...
Click to collapse
I agree with you about small changes. I even face some strange problems in my WiFi. the mac address haven't change, but I can't connect to my work WiFi protected network. Sometimes it connects in limited status. One of my friends which updated his Ultra has this problem too.I could connect it to my laptop adhoc wifi netwrok, but for one time. it even can't connect to that network anymore. I rolled back to my stock 14.4.A.0.133 backup. and a'm waiting to fixes from sony.
Agree with you guys. And that stock greenish blueish greyish statusbar color pisses me off! Anybody knows how to change that color?
Quite pathetic attempt by a mod to bury this thread by moving it to this section. If negative feedback on L bothers you so much, delete the thread and censor it outright. Sad day for xda.