I've search for both "screen" and "brightness" without any results.
Is there anything we can do about the brightness of the screen? It's very low, even if you have it on max. Is it a hardware or software issue?
I've seen a lot of reporst of bad screen brightness, but can't say I've ever experienced a problem. I had more issues with my HTC desire, I could barely see it outside on a cloudy day. The XP I can see fine most of the time.
What are you using to turn the brightness up/down? There is a widget to turn it up and down, but it only makes it go up to 175 (iirc). I use power manager. This changes my brightness depending on different scenarios. Similar to juice defender type things but a lot more basic. The best part of it is the screen timeout and brightness settings.
wired84 said:
I've seen a lot of reporst of bad screen brightness, but can't say I've ever experienced a problem. I had more issues with my HTC desire, I could barely see it outside on a cloudy day. The XP I can see fine most of the time.
What are you using to turn the brightness up/down? There is a widget to turn it up and down, but it only makes it go up to 175 (iirc). I use power manager. This changes my brightness depending on different scenarios. Similar to juice defender type things but a lot more basic. The best part of it is the screen timeout and brightness settings.
Click to expand...
Click to collapse
oh cool, will check that out
Thanks,but don't disable sensor :-(
Brightness don't change :-(
That's one of my problem also, the poor brightness of our phone, At first I thought there is an app to increase it, but there's none..
When im using it under the sun, I cant really see what I'm doing to my phone especially when there's my finger print all over my screen, so i always bring my cleaning cloth.
Yeah i have tried every app out there in hopes one would work but that sensor just has to much control i guess.
Hopefully someone will figure it out eventually.
I guess some people are not bothered by it at all so possibly the people who would know how to fix it just dont care enough to.
On the R800x, there is no auto-brightness to enable. It is all manual. 100% seems to be bright enough to read stuff outside in the sun. I don't know that there would be a way to push it even brighter.
A number of people have been claiming that if you remove the pre-installed screen protector it becomes a lot brighter. Maybe that might help you if you are willing to risk the screen scratches.
ryocoon said:
On the R800x, there is no auto-brightness to enable. It is all manual. 100% seems to be bright enough to read stuff outside in the sun. I don't know that there would be a way to push it even brighter.
A number of people have been claiming that if you remove the pre-installed screen protector it becomes a lot brighter. Maybe that might help you if you are willing to risk the screen scratches.
Click to expand...
Click to collapse
Yeah by removing the protector the screen becomes much more brighter.. The toughened glass seems to be holding up quite fine though.
For a short 30 seconds experience with factory superglued protector, all I can say is remove it. Much better light sensor response, better contrast and much much much better finger swipeability on the mineral glass under the plastic protector...
Also now as I have phone, I'll see how to disable LS.
Sent from my R800i using XDA App
Blagus said:
For a short 30 seconds experience with factory superglued protector, all I can say is remove it. Much better light sensor response, better contrast and much much much better finger swipeability on the mineral glass under the plastic protector...
Also now as I have phone, I'll see how to disable LS.
Sent from my R800i using XDA App
Click to expand...
Click to collapse
I'm glad you finally got your device blagus now start developing lol
Sure, I'm dying too LOL
But first before unlock I have to sniff SEUS communication.
AndroHero said:
I'm glad you finally got your device blagus now start developing lol
Click to expand...
Click to collapse
Sent from my R800i using XDA App
Blagus said:
Sure, I'm dying too LOL
But first before unlock I have to sniff SEUS communication.
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Yeah Blagus,you are the best
Unlocks the brightness' and do a lot of us happy, Sony Ericsson to **** !!!!!!!
Blagus said:
For a short 30 seconds experience with factory superglued protector, all I can say is remove it. Much better light sensor response, better contrast and much much much better finger swipeability on the mineral glass under the plastic protector...
Also now as I have phone, I'll see how to disable LS.
Sent from my R800i using XDA App
Click to expand...
Click to collapse
I was talking to Doomlord the other day about this, the ALS seems to be part of the kernel. The exact location of the sensor parameters is /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als. You can edit those parameters but nothing sticks on save/exit.
If you want to see how crazy the ALS is, fire up logcat in adb and watch what happens when you pull the phone away from a bright light source.
The only problem is some people love the ALS, and some people hate it. I'm in the hate it camp. I'd rather be able to adjust full brightness manually. It would peg the CPU a lot less too in certain lighting conditions, actually improving performance.
To that end, wondering if there is some kind of kernel extension or module that can be flashed, or if it has to be the whole modified kernel that is replaced.
axiomjunglist said:
I was talking to Doomlord the other day about this, the ALS seems to be part of the kernel. The exact location of the sensor parameters is /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als. You can edit those parameters but nothing sticks on save/exit.
If you want to see how crazy the ALS is, fire up logcat in adb and watch what happens when you pull the phone away from a bright light source.
The only problem is some people love the ALS, and some people hate it. I'm in the hate it camp. I'd rather be able to adjust full brightness manually. It would peg the CPU a lot less too in certain lighting conditions, actually improving performance.
To that end, wondering if there is some kind of kernel extension or module that can be flashed, or if it has to be the whole modified kernel that is replaced.
Click to expand...
Click to collapse
I found it in kernel. I'll publish it today. Stable, OC, and light sensor will be separated as module.
Everyone who likes it, will have it automatically on, and who don't can remove module from /system/lib/modules.
Blagus said:
I found it in kernel. I'll publish it today. Stable, OC, and light sensor will be separated as module.
Everyone who likes it, will have it automatically on, and who don't can remove module from /system/lib/modules.
Click to expand...
Click to collapse
Problem: lightsensor and proximity are one device with one driver. So it'll have to be disabled in hw_config.sh
Blagus said:
Problem: lightsensor and proximity are one device with one driver. So it'll have to be disabled in hw_config.sh
Click to expand...
Click to collapse
I tried to solve it through editing the hw_config file, but had the same problem of results not sticking/working correctly. Enable would switch to 0 for a limited time before switching back to 1, and definitely after a boot, but still seemed to be functional and operating as if it was enabled, i.e. the functionality appeared to happen more slowly than rapidly on the fly. Also, the 254 variable never stuck at all, so that test failed, heh.
http://forum.xda-developers.com/showpost.php?p=13937021&postcount=13
Would you need a custom hw_config for a custom kernel mod?
axiomjunglist said:
I tried to solve it through editing the hw_config file, but had the same problem of results not sticking/working correctly.
http://forum.xda-developers.com/showpost.php?p=13937021&postcount=13
Would you need a custom hw_config for a custom optional kernel mod?
Click to expand...
Click to collapse
Because some people still like it, so I can't disable it for everyone.
Now this is where problem starts: no LS config in hw_config so I can't manage power modes like on older Xperias.
Blagus said:
Because some people still like it, so I can't disable it for everyone.
Now this is where problem starts: no LS config in hw_config so I can't manage power modes like on older Xperias.
Click to expand...
Click to collapse
Yeah they conveniently left that out!
I tried experimenting using different parameters and settings in hw_config but nothing would allow me to control it. I even poured over the technical info but couldn't find anything useful related to functionality in android OS.
http://www.austriamicrosystems.com/LMU/AS3676
Blagus said:
I found it in kernel. I'll publish it today. Stable, OC, and light sensor will be separated as module.
Everyone who likes it, will have it automatically on, and who don't can remove module from /system/lib/modules.
Click to expand...
Click to collapse
I would imagine we could alter the settings.apk framework to include a checkbox to enable/disable Automatic mode for light sensor, and if off, revert to manual change. Is this a correct assumption? It might be easier for the end user than enabling and disabling a module at terminal prompt or yanking things from the system image or (heaven forbid) the running OS. It would certainly involve a bit more work, to be sure. However, could also just alter the framework to run insmod commands through BusyBox so that we can insert and remove modules. *shrugs* Just thoughts, not mandates. ^_^
Blagus said:
Because some people still like it, so I can't disable it for everyone.
Now this is where problem starts: no LS config in hw_config so I can't manage power modes like on older Xperias.
Click to expand...
Click to collapse
Hello Blagus're really good, really compliments for the work you do for us now;-) I think that you release the modified kernel for the brightness?
Appearance? I would be happy and I think many users.
you're great !!!!!!!!
Related
Ok i wanted to start new thread with this issue
got a question about the screen. Some times I can sense and see that despite of auto brightness off that the screen adjusts its brightness by itself. It is a little change but my sharp eyes can see this... Do you have a similar thing?
I can easly notice this when playing my country game. When I click on the building menu the screen gets brighter. When i cancel the menu the screen makes darker
Also in sprinkle when I use water the screen gets little brighter
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
This only happens on mine while in power saving mode.
TF201 / XDA premium
wynand32 said:
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
Click to expand...
Click to collapse
Do you experince the same issue as me?
tdrussell said:
This only happens on mine while in power saving mode.
TF201 / XDA premium
Click to expand...
Click to collapse
I'm not sure, I'll have to do some more testing. I seem to remember it happening across the board.
I'll note that Battery mode really does make a HUGE difference in the screen's performance. Colors become very washed out, so much so that I'm really surprised by the impact.
Well in my case this thing occurs on every mode with the same strenght... That sucks
so anyone of you can confirm if this is normal? Do you have the same isue on your primes?
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
ankhazam said:
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
Click to expand...
Click to collapse
Like i said auto brightness is off. Can anyone install my country and check his out for me? Just enter build menu and chec if the screen gets a little brighter
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Ya I noticed this too last night and thought that I had a defective screen. Made a thread about it earlier. http://forum.xda-developers.com/showthread.php?t=1421002
jzen said:
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Click to expand...
Click to collapse
I should b off in perormnce mode. I understand this feature in saving power mode but not on others two. I hope it will be changed
Is there something that I am missing?
I included a very common build.prop script (windowsmgr.max_events_per_sec=x) and set x to the "recommended" 150. Then I tried setting it to 1 and rebooted. I didn't notice a difference between the two.
Am I misunderstanding something here? or is this build.prop script just baloney?
It works, try setting it to 500 and then back to 150. You should notice better touch responsiveness.
ryude said:
It works, try setting it to 500 and then back to 150. You should notice better touch responsiveness.
Click to expand...
Click to collapse
Hey thanks for the response, but I still don't see anything. I set it to 50000 and it still feels the same....
I have noticed a difference, but its pretty minor. I set mine to 300 and it feels a tad smoother.
Interesting. I want to say that I'm doing something wrong with the build.prop, but at least one modification (no boot animation) definitely works.
Some work well, some are questionable, some are useless.
That windowsmanager tweak is likely not useful for many people as the original value is just fine for most people. Only the exceptionally picky will notice a difference.
In the photography world, we call such pickiness "pixel peeping".
Entropy512 said:
Some work well, some are questionable, some are useless.
That windowsmanager tweak is likely not useful for many people as the original value is just fine for most people. Only the exceptionally picky will notice a difference.
In the photography world, we call such pickiness "pixel peeping".
Click to expand...
Click to collapse
Thanks man.
But how do you then explain that setting the value to 1 feels exactly the same as when on 100 or 200?
I would assume that everything should run noticeably slower? I understand what you're saying, I'm just having a hard time believing that its even a tweak at all.
Sent from my GT-I9100 using XDA App
patsmike said:
Thanks man.
But how do you then explain that setting the value to 1 feels exactly the same as when on 100 or 200?
I would assume that everything should run noticeably slower? I understand what you're saying, I'm just having a hard time believing that its even a tweak at all.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Because at some point, you reach either a cap due to something else bottlenecking (such as the screen refresh rate), or a cap on your ability to perceive any difference.
Entropy512 said:
Because at some point, you reach either a cap due to something else bottlenecking (such as the screen refresh rate), or a cap on your ability to perceive any difference.
Click to expand...
Click to collapse
Sorry I worded my question poorly. I meant to ask why doesnt the ui feel noticeably slower at the lowest possible value of 1.
I understand why we wouldnt notice any difference increasing the value, but what about the other way around?
Sent from my GT-I9100 using XDA App
patsmike said:
Sorry I worded my question poorly. I meant to ask why doesnt the ui feel noticeably slower at the lowest possible value of 1.
I understand why we wouldnt notice any difference increasing the value, but what about the other way around?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Because you're looking for the performance to change, which it doesn't do. It only changes how many times it checks for new touch input, which improves how responsive it is to your touches. Past a certain point, it ceases to improve to a degree that the human eye can see.
Dont for get
Sent from my GT-S5570 using XDA
ryude said:
Because you're looking for the performance to change, which it doesn't do. It only changes how many times it checks for new touch input, which improves how responsive it is to your touches. Past a certain point, it ceases to improve to a degree that the human eye can see.
Click to expand...
Click to collapse
Sorry, yes I meant touch responsiveness when I wrote UI response.
And again, I understand that if you set it to a very high value, you won't notice a difference. I am asking about what happens when you set it to a very LOW value (so that I can check if the build.prop tweak really changes anything).
So hear me out: I found an easy little test for touch responsiveness - if you use the LA4 circle lock screen and press on the screen, everything turns dark when the circle pops up. So if you tap quickly, you can see exactly how fast it registers your presses because the screen starts flashing from dark to your background and so on. So I set windowsmgr.max_events_per_sec=1 and then reboot.
Then if you try and tap on the lock screen very fast, you can still see the screen flashing at much faster rate than 1 time/sec. It is actually perfectly accurate and doesn't miss any of my taps. Therefore, it is not checking for touch input every second, but still at a very fast rate where the difference is unnoticeable.
Try it - its very easy and proves that this build.prop change doesn't change anything - all placebo (unless I am implementing something wrong).
Sent from my GT-I9100 using XDA App
*** YOU MUST BE ROOTED TO USE THIS APP ****
This app will recalibrate a worn or dirty proximity sensor. If your screen does not turn on after a call, then your prox sensor either needs to be recalibrated or is burnt out.
Usage:
1) Open the app. If your screen does not turn on after a call, it should report the word "NEAR."
2) Increase PS2_CANC (High Threshold) until it reports "FAR." Go one or two values past where it first changes.
3) Cover and uncover your proximity sensor and verify that it reports NEAR and FAR correctly.
4) If you want the values to be set on boot check the box.
5) Post the values that work best for you along with the ROM you're using in this thread. Hopefully we can use them to find better default values.
If any combination of low threshold and high threshold does not make your proximity sensor function as it should, then it is most likely burnt out and you need to warranty your phone.
Get it at:
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
This app was inspired by DHD proximity sensor calibrator by leppie:
http://forum.xda-developers.com/showthread.php?t=951858
Source:
https://github.com/Chad0989/Rezound-Prox-Sensor-Calibrator
Neat. Low 13, high 51 is the crossover point for my phone.
Works great, Chad. Mine was on the edge, so to speak. It worked sometimes, and didn't others. Bumping high up to about 54 and it's working great.
the defaults worked well for me. What does the low threshold do though? Changing it doesn't affect the responsiveness.
65 for the high works pretty well for the distance it should be when holding to your ear, but being more sensitive (detecting near when my hand was farther from the sensor) at the defaults also works.
This is great. Exactly what we needed. Thanks man
Had to set the high on mine down to 14 just to get "near" to show. Tested on a call and it works perfectly now. Thank you Chad. I'm using the global firmware and it never worked correctly after the ruu.
Low 12, high 53 works the best for me. thank you chad!!!!!!!!!!!!
Okay, this is pretty incredible. Thanks, Chad, invaluable fix for my poor Rezound's post-call-black-screen bug.
chad0989 said:
*** YOU MUST BE ROOTED TO USE THIS APP ****
This app will recalibrate a worn or dirty proximity sensor. If your screen does not turn on after a call, then your prox sensor either needs to be recalibrated or is burnt out.
Usage:
1) Open the app. If your screen does not turn on after a call, it should report the word "NEAR."
2) Increase PS2_CANC (High Threshold) until it reports "FAR." Go one or two values past where it first changes.
3) Cover and uncover your proximity sensor and verify that it reports NEAR and FAR correctly.
4) If you want the values to be set on boot check the box.
5) Post the values that work best for you in this thread. Hopefully we can use them to find better default values.
If any combination of low threshold and high threshold does not make your proximity sensor function as it should, then it is most likely burnt out and you need to warranty your phone.
Get it at:
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
This app was inspired by DHD proximity sensor calibrator by leppie:
http://forum.xda-developers.com/showthread.php?t=951858
Source:
https://github.com/Chad0989/Rezound-Prox-Sensor-Calibrator
Click to expand...
Click to collapse
Default settings work for me as well.
You are the best!
Sent from my HTC Rezound using xda app-developers app
Gotta say, this is a pretty awesome tool. I've been trying to use this app called "Wave Control" that uses the proximity sensor to control media players and have just had absolutely no luck until now.
Couldn't tell if my sensor was just worn, dirty, or burnt out. With this app, it was reading "Far" constantly, but after some messing around, I finally got it to register again. Oddly enough, the values working best for me right now are:
Low Threshold: 5
High Threshold: 36..
Not sure what this means, but I'm just glad it's working still. Thanks for all the work you do, Chad. You're invaluable to the Rezound community.
Sent from my HTC Rezound using Tapatalk 2
14 and 29 for me
Hoping this will work for me. CM9 light sensor hardly turns my screen off when in calls, so it would seem I'm collecting too much light. Was getting pretty angry at it when it dials numbers with my cheek.
Thanks for this.
4 and 15 for mine
Sent from my Rezound using xda app-developers app
THANK YOU.
I bought my Rezound off eBay so I had no idea if it was normal for the screen to be so glitchy during calls. I had to press the power button to turn the screen on during calls if I needed to use to dial pad or even hang up. I'm so glad I saw this app because it's all fixed!
I had to set my settings to Low: 22 / High: 86....not sure if that's good or bad, but the screen now turns itself on when I pull the phone away from my cheek instead of me having to do it myself so it's all I care about.
what were the default values again?
darienms1986 said:
what were the default values again?
Click to expand...
Click to collapse
Mine defaulted to 12/51.
Sent from my ADR6425LVW using Tapatalk 2
darienms1986 said:
what were the default values again?
Click to expand...
Click to collapse
It appears to be different for every device. There is some sort of in-built automatic calibration in the kernel but it seems to not work very well.
chad0989 said:
It appears to be different for every device. There is some sort of in-built automatic calibration in the kernel but it seems to not work very well.
Click to expand...
Click to collapse
Ok just trying to set mine back to default. No big deal. The settings are working great that i posted. Thank you so much for all your hard work. I love this phone and you keep making it better
Sent from my Rezound using xda app-developers app
mine is 2/36.
and how did you guys find out the low threshold value？that value seems to affect nothing even if i set it higher than the high threshold value.
Sent from my ADR6425LVW using Tapatalk 2
darienms1986 said:
Ok just trying to set mine back to default. No big deal. The settings are working great that i posted. Thank you so much for all your hard work. I love this phone and you keep making it better
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Uncheck set on boot and reboot?
Sent from my ADR6425LVW using Tapatalk 2
My screen of the Truemate is WAY too sensitive: moving above already gives a lot of input.
Touching is impossible: many inputs at the same time.
I cannot use it.
Factory Default reset doesn't work. Latest update installed.
Who can help?
There seems not to be a support dept. that reacts or answers.
Please help!
untruemate said:
My screen of the Truemate is WAY too sensitive: moving above already gives a lot of input.
Touching is impossible: many inputs at the same time.
I cannot use it.
Factory Default reset doesn't work. Latest update installed.
Who can help?
There seems not to be a support dept. that reacts or answers.
Please help!
Click to expand...
Click to collapse
I have had the same issue. Clean ur screen often. Static electricity is one of the bigger reasons this touchscreen becomes too sensitive. When this happens, grounding myself usually fixes the problem.
I read about this in another post....Go out and get yourself a ZAGG screen protector. Doesn't matter which phone model or make, as you will have to cut it down to the TS size. You can find many of these on sale from earlier released phones...the best to find is the Note 2....this gives you the largest sheet of their protection material. Just in case you have to do multiple tries.
Good luck
Sent from my Nexus 7 using Tapatalk
untruemate said:
My screen of the Truemate is WAY too sensitive: moving above already gives a lot of input.
Touching is impossible: many inputs at the same time.
I cannot use it.
Factory Default reset doesn't work. Latest update installed.
Who can help?
There seems not to be a support dept. that reacts or answers.
Please help!
Click to expand...
Click to collapse
When I receive my watch I'll build mod for lower brightness (longer battery life) and touch screen sensitivity tweak...
For now, root your device and wait for mod - we have to edit few files, cleaning screen or applying screen protector won't harn but won't help either.
It's ridiculous that developers edition comes last, but that's the way it is...
Sent from my C6903 using Tapatalk
Mine was originally WAY over sensitive as well... but after installing Loki's ROM and/or the patch I don't seem to have the problem. Don't know if it is related but if you haven't patched or updated.... DO IT!
funky0308 said:
When I receive my watch I'll build mod for lower brightness (longer battery life) and touch screen sensitivity tweak...
For now, root your device and wait for mod - we have to edit few files, cleaning screen or applying screen protector won't harn but won't help either.
It's ridiculous that developers edition comes last, but that's the way it is...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I did think the brightness is insane... I tried to use clock view to have an always on clock but even with the minimum brightness it's slaughtering it, in a dark room you can see just how much it's wasting
death_entry said:
I did think the brightness is insane... I tried to use clock view to have an always on clock but even with the minimum brightness it's slaughtering it, in a dark room you can see just how much it's wasting
Click to expand...
Click to collapse
Exactly...that's why we'll have few mods.
Sent from my C6903 using Tapatalk
Glad to see some help, however there is a proper Q&A section in this forum, please head there with your questions
So I, at first, thought Assertive wasn't working/enabled on my V20 but it turns out the stock settings are just pathetic. I spent some time adjusting the config file and had a few fellow V20 users test out my changes and they have all reported back that it works fantastically now.
For Assertive to function, your phone MUST be set to 'automatic' backlight control.
Decompress and copy my file to your phone and replace the calib.cfg located in /system/media/display/. Make sure to change the permissions on the replacement file to 644.
Reboot and enjoy
Test out in direct, bright sunlight. You'll be surprised.
Let me know your results in the poll and in comments.
Thank you for your work brother
what does this do exactly?
dimm0k said:
what does this do exactly?
Click to expand...
Click to collapse
Assertive Display was designed by APICAL. They are owned by Qualcomm and Qualcomm has built the tech into their SoCs.
Basically, it adjusts the gamma curve, white balance, contrast, etc. of the display based on intensity and amount of ambient light. It can take a display that would be utterly crushed by sunlight and make it readable.
Try it out.
Colours get really washed out in the sunlight but i can see the screen better
Builtfordtough1 said:
Colours get really washed out in the sunlight but i can see the screen better
Click to expand...
Click to collapse
yeah, product of how it works. I'm still fiddling with it. I'll update when I decide different settings work better.
i hope you dont mind if i use your file in my rom? i can give creds of course
elliwigy said:
i hope you dont mind if i use your file in my rom? i can give creds of course
Click to expand...
Click to collapse
Sure
This is a great MOD. Thank you OP for messing around with this for us! Great work! Looking forward to a few tweaks to optimize it, but works great!!!
The problem I have is in low light environment. Screen goes to zero as soon as the light gets dimmed. I can't think of any environment that I would want the screen at zero. That's just too dark for my old eyes
justthefacts said:
The problem I have is in low light environment. Screen goes to zero as soon as the light gets dimmed. I can't think of any environment that I would want the screen at zero. That's just too dark for my old eyes
Click to expand...
Click to collapse
sounds like another issue lol.. mines never gone to 0 on auto and this is on multiple roms and kernels and even my vs995 was very first vzw phone to be dirty santa'd
elliwigy said:
sounds like another issue lol.. mines never gone to 0 on auto and this is on multiple roms and kernels and even my vs995 was very first vzw phone to be dirty santa'd
Click to expand...
Click to collapse
I'm on T-Mobile H918. Mine jumps from 50 to zero as soon as the light gets dimmed .
Tap the light button in the pull down status bar. It corrects this issue. (Right above where it says 68%)
dfogelstrom said:
Tap the light button in the pull down status bar. It corrects this issue. (Right above where it says 68%)
Click to expand...
Click to collapse
That would bring it up to 50% which would be too lit for a dark place
justthefacts said:
That would bring it up to 50% which would be too lit for a dark place
Click to expand...
Click to collapse
Okay, then I'm having the same issue lol. I thought it was different from before. Just trying to help out ?
is this happening after changing the calib file out with mine?
helf said:
is this happening after changing the calib file out with mine?
Click to expand...
Click to collapse
Yes
ah OK. Did you verify that the file's permissions are set to 644?
helf said:
ah OK. Did you verify that the file's permissions are set to 644?
Click to expand...
Click to collapse
Yes. Do you get a different behavior on yours?
justthefacts said:
Yes. Do you get a different behavior on yours?
Click to expand...
Click to collapse
yes. mine only goes to 0 indoors if it's totally dark. have you tried moving your slider up a little like to 10% while automatic is set? that'll leave it automatically adjusting bit with a +10% to whatever it automatically sets