*** 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
Related
Check out superdim (root), its in the market for free, it works amazingly well. I always noticed the atrix was particularly bright even at its lowest setting. I never *****ed because I was just happy to have a bright screen visible in daylight. Now we have best of both worlds.
Source: my twitter feed
Ps not the dev, just a satisfied customer.
Sent from my MB860 using XDA App
Sweet! thanks
AdjBrightness works well too.
Nice, I will have to check these out. The blindingly bright "dim" setting was one of my pet peeves with the Atrix!
I have check it now, and it works like a charm, very low bright. excellent.
I use this one:
https://market.android.com/details?id=com.haxor
Shaydar said:
I use this one:
https://market.android.com/details?id=com.haxor
Click to expand...
Click to collapse
Sweet, this one works better even. It has a widget, and stays active even after screen off, and back on!
scoob8000 said:
Sweet, this one works better even. It has a widget, and stays active even after screen off, and back on!
Click to expand...
Click to collapse
Thanks! I was actually just noticing that super dim didn't stay dark. What a great idea
Edit: I noticed that super dim actually darkens the screen while this new deal simply puts a dark patch over the screen. That's the difference between root and no root lol
Ps use both for super reading mode!
Sent from my MB860 using XDA App
I've been using Elixir which does all sorts of stuff but one of the options is a tggle widget that lets you shuffle through up to 5 brightness settings. I use Auto, 5%, 12%, 40%, and 60%.
Sent from my MB860 using XDA Premium App
Well after playing with screen filter, I'm not crazy about it after all. It does nothing to the backlight but puts a grey tint to everything which makes it hard to read at the lower levels.
However, I've been emailing the author of superdim. He's already put out a version with the home screen profile shortcuts I asked for.. wish more devs were that responsive!
scoob8000 said:
Well after playing with screen filter, I'm not crazy about it after all. It does nothing to the backlight but puts a grey tint to everything which makes it hard to read at the lower levels.
However, I've been emailing the author of superdim. He's already put out a version with the home screen profile shortcuts I asked for.. wish more devs were that responsive!
Click to expand...
Click to collapse
If you talk to him again tell him his app rocks and he's got the atrix communities thumbs up.
Side note I somehow got the dimness to stick through a screen off. Start at boot would be nice tho..
Sent from my MB860 using XDA App
ChongoDroid said:
If you talk to him again tell him his app rocks and he's got the atrix communities thumbs up.
Side note I somehow got the dimness to stick through a screen off. Start at boot would be nice tho..
Click to expand...
Click to collapse
I actually just found him here. [APP] Superdim
It seems like the brightness after wake sticks as long as it's at 20 or above. It's like 20 equates to 0% in phone settings.
It's funny, most noticeable at 0. Hit the power button to shut the display off, and you notice it gets brighter before turning off.
Just tested this on my MT3GS, I can set it at 0 and it stays there. Even after a reboot.
[EDIT]
Working with the dev some more, I think he's got this fixed in the next beta! It restores the dim settings after wake! Stay tuned!
Seems to be fixed... my phones lowest is 30... very weird
Sent from my Xoom using XDA App
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 !!!!!!!!
So since I've moved to CM7 I keep hanging up on people when I am trying to hold my phone between my ear and shoulder because my jaw bone hits the end button. I don't recall this happening ever with Blur. Is there a prox sensor that is supposed to disable the phone when it's up against your face? Where is this setting in CM7 or is it just an issue of buttons being in slightly different places w/ CM7 than with stock? If so, is there a phone replacement app that anyone could suggest?
Have you tried turning the screen off (via the power button) before holding it to your face? That was something I desperately wished I could do on my old Moment, because its proximity sensor sucked, but the power button served double duty as the end call button.
Interesting idea. I didn't consider trying that. I also noticed under Call Settings an option "always use proximity sensor" which I enabled and will try. Maybe my phone thinks it's horizontal when I hold it that way.
It is a vertical horizontal thing I believe. Phone needs to be pretty much vertical for the proximity sensor to come on. You can test this in a dark room. Call a number and watch the sensor illuminate. It should look like a red dot near the earpiece. Then move it towards horizontal. You should see it cut off.
Sent from my MoPho. All typos are the phones fault.
ypu may need to do another fresh clean install. completely wipe everything then flash the rom again?
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
jeggen said:
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I was just going to mention that. I found the setting while tooling around in the cm7 settings. Glad you got it fixed.
Sent from my MoPho. All typos are the phones fault.
will give that a try. im having same issue on cm7.2
I just noticed the past couple weeks that my light sensor does not read out less than 90 lux, even in total darkness. For reference, a totally dark room should read out at 0 lux. This affects any auto-brightness settings and apps.
I could almost swear that I tested this when I first got the phone, it did work correctly. So I was wondering first if anyone else has seen it happening to them, or if you could please test it.
The best way I've found to test is to use AndroSensor from the market. Also, just as additional info, I've tried this with an Otterbox Defender and with a naked phone, with the same results. Phone has never been dropped or wet and the proximity sensor works fine. I'm running stock ROM rooted.
Many thanks...
I can't help but I can say a few people have been having problems with there sensor... I had to replace my phone today because of it not working...
Sent from my EVO using xda premium
Slappy_G said:
I just noticed the past couple weeks that my light sensor does not read out less than 90 lux, even in total darkness. For reference, a totally dark room should read out at 0 lux. This affects any auto-brightness settings and apps.
I could almost swear that I tested this when I first got the phone, it did work correctly. So I was wondering first if anyone else has seen it happening to them, or if you could please test it.
The best way I've found to test is to use AndroSensor from the market. Also, just as additional info, I've tried this with an Otterbox Defender and with a naked phone, with the same results. Phone has never been dropped or wet and the proximity sensor works fine. I'm running stock ROM rooted.
Many thanks...
Click to expand...
Click to collapse
mine dont go less than 90 either???
Getting the same thing..
I'm curious, does anyone else that's getting the 90 lux reading also have light bleed from the home button? If you're getting a 0, do you have light bleed? Maybe something with how the glass is glue on?
I think we all are? Maybe the reason why the auto-brightness is so sensitive.
Just tested it... Mine stays at 90 to no matter what... Does not move in light or dark... I don't think the program is utilizing out sensor right??? Also my proximity sensor goes from 3.5in to 0 no matter how far or close I am... There is no in between???
Sent from my EVO using xda premium
Same here. No light bleed...
Check Me Out On The Google Play Store!!!
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
I'm getting the same reading of 90 lux and if I put it up to light it moves higher ... You think this can be fixed when we get kernel source?
Sent from my LTEeeeeevoo using xda premium
NissanNick said:
Just tested it... Mine stays at 90 to no matter what... Does not move in light or dark... I don't think the program is utilizing out sensor right??? Also my proximity sensor goes from 3.5in to 0 no matter how far or close I am... There is no in between???
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is as designed - the proximity sensors either read out "something is up against the phone" or not. So they all have only 2 values, zero and something else.
goffmj said:
Getting the same thing..
I'm curious, does anyone else that's getting the 90 lux reading also have light bleed from the home button? If you're getting a 0, do you have light bleed? Maybe something with how the glass is glue on?
Click to expand...
Click to collapse
No light bleed that I can see, and I used to have an Evo 4G, so I know what it used to look like on that device. I'm tempted to try a factory reset, but have not unlocked the bootloader yet, so no way to make a nandroid. Ugh.
Bump-bump-bumpity-doo...
Anyone else seeing their light sensor truly zeroing out? For now, I've reinstalled my purchased copy of Lux Auto Brightness and set it to use the camera as the light sensor, which does the trick, but only checks when the screen is first turned on.
My power button broke on my phone and so I purchased what was described as a "pulled from working phone" circuit board with power ribbon. Now when a call connects my screen automatically turns off. Depending on which ROM I either can do nothing until the call disconnects or I can press the power button and the screen turns on.
Anybody have any ideas on how to stop the madness. It is quite frustrating.
It sounds like a proximity sensor issue. It would be up there next to the power cable ribbon. Can you check to see if it isn't being obstructed or loose?
Sent from my HTC6500LVW using XDA Free mobile app
It is more of a software issue. I was using CM12 and when a call connected the screen would turn off and would not come back on until the call disconnected and if the screen was off and a call came in the screen would not turn on and you could not make it come on. I am now using Sense Six from Santod. Screen still turns off when a call connects but the power turns it back on and with an incoming call the screen actually turns on. Thank you for posting though.
Supashawn said:
It is more of a software issue. I was using CM12 and when a call connected the screen would turn off and would not come back on until the call disconnected and if the screen was off and a call came in the screen would not turn on and you could not make it come on. I am now using Sense Six from Santod. Screen still turns off when a call connects but the power turns it back on and with an incoming call the screen actually turns on. Thank you for posting though.
Click to expand...
Click to collapse
When the sensor recognizes "near" it will have the screen shut off during a call. That is why I suggest it is the sensor. Also you having the issue after you dealing with hardware near the sensor seems it is more than likely hardware than software.
Hitting the power button on some roms will turn the screen on and override the "near/far" of the sensor. Do a search for "rezound proximity sensor calibrator" on Google Play. Check to see if you are getting near/far correctly.
Edit: https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator just checked and it does show near/far for my phone correctly. This app works for pretty much all HTC phones to calibrate the prox sensor.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
When the sensor recognizes "near" it will have the screen shut off during a call. That is why I suggest it is the sensor. Also you having the issue after you dealing with hardware near the sensor seems it is more than likely hardware than software.
Hitting the power button on some roms will turn the screen on and override the "near/far" of the sensor. Do a search for "rezound proximity sensor calibrator" on Google Play. Check to see if you are getting near/far correctly.
Edit: https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator just checked and it does show near/far for my phone correctly. This app works for pretty much all HTC phones to calibrate the prox sensor.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well... I certainly stand corrected... Thank you very much. Now if I could get it right. It started out as 68 and I think like 12 and I have had to crank it down to 41 for my screen to not turn off when the call connects but then it does not cut off when putting the phone to my head. Why would this happen... Is my phone just old?
Supashawn said:
Well... I certainly stand corrected... Thank you very much. Now if I could get it right. It started out as 68 and I think like 12 and I have had to crank it down to 41 for my screen to not turn off when the call connects but then it does not cut off when putting the phone to my head. Why would this happen... Is my phone just old?
Click to expand...
Click to collapse
You would have to play with the settings. Best bet would be putting your finger over the sensor while in the app and scale it until you see near, then put finger away and see if it shows far. Be sure to check the option to "set on boot" when you get it perfect.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You would have to play with the settings. Best bet would be putting your finger over the sensor while in the app and scale it until you see near, then put finger away and see if it shows far. Be sure to check the option to "set on boot" when you get it perfect.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I am not sure this thing is working right. It never changes what it says. It always says Near and doesn't matter which I change while I put my thumb over the sensor. That is wrong... Right???
Supashawn said:
I am not sure this thing is working right. It never changes what it says. It always says Near and doesn't matter which I change while I put my thumb over the sensor. That is wrong... Right???
Click to expand...
Click to collapse
Yes, that is right, something is going on. You could have something covering the sensor when you put the power button ribbon in. At least we have checked and see the issue is most likely hardware. It has been awhile since I took my DNA apart, and can't again as it got lost in the mail, so I cannot check to see if the ribbon goes by the sensor.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Yes, that is right, something is going on. You could have something covering the sensor when you put the power button ribbon in. At least we have checked and see the issue is most likely hardware. It has been awhile since I took my DNA apart, and can't again as it got lost in the mail, so I cannot check to see if the ribbon goes by the sensor.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well I guess I will have to take it apart and try to fix it. Thank you for helping me. Smiley