Related
Hi
my woman got the Galaxy S2 and has a problem with the camera app. The app shows a very dark screen like a maximum power saving mode. The rest of the apps are Ok. It can help then if I turn off the automatic brightness of the screen and the energy saving settings and turn them on again. But after a couple of days you have to the same again. So she is a bit p...ed about that. Does anybody of you have an idea how to get it stable bright?
BR MArtin
'my woman'...lol.
Anyway if you go into the camera app settings, scroll to the bottom and click 'reset'. Maybe your exposure settings or contrast etc were changed somehow. If that doesn't work...might be something up with the camera, or even some rubbish on the lens. You could just take it back and get a new one..
Never had problems with that, but all I can think of is that the illumination-sensor next to the front-face cam is dirty?
(less light coming tru makes everything darker?)
Sent from my GT-I9100 using XDA App
With the settings in the picture everything is ok. The picture taken with the camera are ok. Also the Sensor is ok as it is working fine everywhere else. Any other ideas?
Br Martin
And yes it's my wifes phone I have a HTC Sensation
msichler said:
With the settings in the picture everything is ok. The picture taken with the camera are ok. Also the Sensor is ok as it is working fine everywhere else. Any other ideas?
Br Martin
And yes it's my wifes phone I have a HTC Sensation
Click to expand...
Click to collapse
Strange. Was it like that when she bought it? Just take it back and exchange it for a new one...
Sent from my iPad using Tapatalk
666fff .. Why take it back to the store immediately?
Anyways... So I you have the app (camera) open.. Do the bars (with the icons in it) also seem dark or do they look (normal)bright?
Sent from my GT-I9100 using XDA App
Yes everything is dark must be some problems with the energy settings or whatever
BR MArtin
Let me eliminate some causes:
- you've unchecked 'automatic screen brightness'?
(@settings)
- you've tried maximizing brightness manually?
- you've rebooted throughout the process? (giving the phone the chance to apply it's settings, sometimes all it needs is a reboot)
Let me know.
Sent from my GT-I9100 using XDA App
Basically I tried evrything you said with unchacking and Checking the automatically settings and also the additional Energysaving settings it gets back fine for some days but then it changes back to the dark setting unless i check and uncheck the boxes again. So it seems not to be a stable sollution. So I search now for a sollution that the camera app always runs with maximal display brightness
I've tried about everything then.
I ran some tests on my own SGS2 but I can't emulate the dark bars.
Not even by holding my finger over the light-sensor.
But I guess it's like this and I DO NOT know a fix for it: seems like the phone is learning that you don't use the camera much. So if you do. It will automatically go into power saving mode since the priority for battery-use is for system instead of cam (due to low-use)
So the only last thing I could think of, is that you've enabled automatic power saving?
Uncheck it and take Juice Defender as your 'battery saver' fixed alot of issues with brightness going up and down for me(very annoying) never goes up and down for me anymore!.
I hope this is of good help.
Sent from my GT-I9100 using XDA App
Ok will try that with Juice Defender.
BR MArtin
I have write me a task with Tasker witch put me max sensor light and auto rotation on when I open the cam. after closing it revers to the normal state! ,-)
I think I had the same problem as you.
In the camer app > Settings > Outdoor Visibility > ON
(it unfortunately resets everytime I exit the app)
Hope it helps
I tried with the Outdoor visibility but this seems to change the colors of the screen and not the brightness.
You are right, that does not work. I was at work when I tried this and it seemed to make the screen brighter, but outside in the sun light it does not make any difference. So I have the same problem as you lol
It's not his screen or image. It's the gray bars on the sides that he means.
Sent from my GT-I9100 using XDA App
I tried the following thing and it's work :
1. Uncheck auto brightness
2. Make the brightness 100 %
3.Check again auto brightness.
On my phone when i made this the brightness on the camera is 100% and is not depending from auto brightness.
this totally worked! seems like within the camera app, there is no auto-adjusting of brightness and it always defaults to what the last brightness setting was set, regardless of auto-brightness status (checked/unchecked).
Hi,
Since a couple of days I've noticed that my screen flickers sometimes.
Mostly when I'm moving my hand while holding the phone...
Is it possible that the light sensor auto adjusts my screen brightness ?
If so, how can I turn it off ?
Thanks in advance,
Niels
If you have rooted the phone, you can install Disable Auto Brightness for Xperia phones. or you can disable it manually editing the file /ect/hw_config.sh.
Search the forum for the tutorial
Thanks for your answer !
So unless you start rooting or changing files there's no way to stop the flickering ?
Unfortunately, no. By the way, this problem usually affects st15 models... as far as i know, you've been unlucky
Okay, I'm sure now that it's really because of the lightsensor and not just a problem with my screen.
I was standing near a window and when I put my finger on the lightsensor a few times the brightness was clearly automaticly adjusted...
I'll look for the tutorial, thanks for the info !
Other solutions, if any, are still welcome though
Niels
NelisC said:
Okay, I'm sure now that it's really because of the lightsensor and not just a problem with my screen.
I was standing near a window and when I put my finger on the lightsensor a few times the brightness was clearly automaticly adjusted...
I'll look for the tutorial, thanks for the info !
Other solutions, if any, are still welcome though
Niels
Click to expand...
Click to collapse
Hey, my ST15i does also automatically adjust the brightness....it's not a problem mate When i am outdoors the screen get brighter but when i am indoors my screen automatically gets darken
Yes I now, but I find it annoying, it gets flickery sometimes..
I want the screen to stay on the brightness I've set.
today I was wondering why this phone doesnt have auto brightness adjustment feature, because I have to manually turn brightness to zero when using phone while on bed at night. I looked into settings and no such feature found, I wonder the light sensor actually works
Yes it does, I've tested it.
Try standing near a window or holding it near a lamp and put your finger on the sensor... (The screenbrightness may not be set to 0 if you try this..)
I too find it strange that there's no possibility to set the auto adjust on/off..
Niels
I don't think there is any auto-brightness option in LWW as I've not found any. if there were any then they would have provided an check box option turn it on/off. but the brightness ups and downs happens to me to specially when i've put the brightneww to lowest level at night. could not explain myself.
yup it works (just checked thru window operation )
S.Nahid said:
I don't think there is any auto-brightness option in LWW as I've not found any. if there were any then they would have provided an check box option turn it on/off. but the brightness ups and downs happens to me to specially when i've put the brightneww to lowest level at night. could not explain myself.
Click to expand...
Click to collapse
The fact that you can't turn it on/off doesn't mean it doesn't work. Actually, the auto-brightness is always on. You can disable it manually editing /etc/hw_config.sh or using the app Disable Auto Brightness Xperia. You need root anyway.
When I unlock the phone it always starts up very dim and sometimes it turns bright sometimes it doesn't. I have auto-brightness off and I have my brightness set to 100%. I have to move the slider off of 100% and back to 100% to get it that bright. It is very weird. Anybody know how to fix this?
I have the same problem.
Sent from my GT-I9300 using xda premium
Settings > Display > Auto adjust screen power (untick). Try now.
Been unchecked since day 1. Still does it. Possible that I have a defective unit?
HaruSoul said:
Been unchecked since day 1. Still does it. Possible that I have a defective unit?
Click to expand...
Click to collapse
Is it dim on the home screen or certain apps? cuz internet browser, video etc got their own brightness settings built in that you have to change from the settings within the app.
manbatistuta said:
Is it dim on the home screen or certain apps? cuz internet browser, video etc got their own brightness settings built in that you have to change from the settings within the app.
Click to expand...
Click to collapse
It is dim from the lock screen. Everything once I unlock it is dim. If I lock and unlock the phone like 3 times fast it is fine, but it's a pain in the ass. I'll see if I can take a video of it later when I get home.
I know you said "everything" but try to go to internet browser and disable "auto-brightness" under brightness setting.
Also upgrade your firmware to the latest one to see if that help. My Smart detect is not working and after upgraded it work every single time plus the cell stand by is much improved
I just got my phone back from service, they updated to LF5 - so far it has solved my proplems with dim
I have had 2 handsets that do this now. Its really annoying especially when you are outside.
Basically what is happening is that when your screen dims down before it goes off thats what is happening when you unlock the phone.
I can be using it for 5-10 secs before the full brightness kicks in.
It has nothing to do with power saver or internet. Just running through the home pages and apps list it is doing it.
I am on the latest firmware too.
Does anyone know whats causing it? Is it just a faulty handset (or 2)?
Mine the same. I don't think there bad devices I think its just software related tbh
Sent from my GT-I9300 using xda premium
Well im glad some others of you have experianced this also.
I just hope its something that will be fixed in an update.
It really p****s me off when it does it and im outdoors.
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.
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
xclaw said:
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
Click to expand...
Click to collapse
When you flashed to 4.3 did you do a wipe? Have you tried a reset at any time? If you just updated without wipe it would have retained any previous settings or conflicts that may cause this.
Sent from my C6833 using XDA Premium 4 mobile app
I'll do a quick backup and then try a wipe to see if that clears it up. Thanks for the suggestion.
maybe you has to sent to service central but before just update again ,hope will fine
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
xclaw said:
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
Click to expand...
Click to collapse
Are you sure you flashed the device correctly and followed the procedures in LordManhattan's guide or [NUT]/blueether's posts?