Hi there, I think my DHD's proximity sensor is not working, i.e. screen is not turning off during calls resulting in disconnections. I installed Android Sensor Box from play store. Its indicating that proximity sensor is present but always at 9 cm even I covered the top portion of the screen. What do you guys suggest, is it a faulty sensor? I am using latest cm10.1 nightly.
Hey have you tested this proximity sensor app?
http://forum.xda-developers.com/showthread.php?t=951858
Sent It From Outer Space.
Thanks for the suggestion, I'll definitely try it and report back.
Hi,
disassemble the phone and clean up sensor
it work for me
I face the same problem and the app also always shows far
Yeah same problem. Its always showing far except 0,0
Sent from my Desire HD using Tapatalk 2
Easy Way Out!
Possible calibration procedure:
1. Put both values high (will show FAR).
2. Cover sensor with finger.
3. Lower High threshold till it says NEAR.
4. Lower Low threshold by a notch or 2.
5. Test behavior.
Different person will guide you different ways.....that's their way to explain,no offence here.And sometimes different ROM could also requires different calibration,best way to do it is mentioned above.
Example: I'm on AoCP my own custom way made look of 4.2.2 kitkat*
I've OK Google working and Everything as stated in KitKat.But obvious im on 4.2.2 instead of 4.4.2!
In this ROM ive sets Lower @ 13 and Higher @15 but it could be different by user to user.
Thanks.
the other sensor test app shows 9.0 cm always
Related
Update on Issue #1: 2010.11.29
This issue appears to affect all unlocked Froyo devices on the Rogers network. It MAY affect all Froyo devices, regardless of network lock status, but we have been unable to confirm this (yet) on the only Froyo device locked to Rogers - The Acer Liquid e.
There are currently 4 threads (that I am aware of) scattered around XDA. As this problem affects multiple devices I will start posting updates in the General Discussion/Q&A thread, and will stop posting updates here. If you are looking for more information, please refer to:
Main Thread: http://forum.xda-developers.com/showthread.php?t=845152
Other Device Specific Threads:
N1: http://forum.xda-developers.com/showthread.php?t=849969
DZ: http://forum.xda-developers.com/showthread.php?t=848793
SGS: http://forum.xda-developers.com/showthread.php?t=850784Wanted to see if this is isolated to my phone or if others have these issues.
_________________________________________________________________________________________________________________
Phone is Rooted, S-Off, Paul Obriens Custom ROM with HTC Sense on Rogers Network.
1. Cannot get a location lock unless I use GPS, it will not give me a location in Maps at all unless I turn on GPS.
2. Display is set to Automatic Brightness but the screen stays the same no matter if i'm in direct sunlight or in a pitch black room
3. Have SMS Timestamp fix but am still getting messages which sometimes show hours behind or hours ahead
Bump
Sent from my HTC Vision using XDA App
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Also have issue with automatic brightness adjusting not working.
ayewhy said:
Also have issue with automatic brightness adjusting not working.
Click to expand...
Click to collapse
I don't think I've seen anyone saying that it *does* work for them in the stock ROM. Anyone ?
steviewevie said:
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Click to expand...
Click to collapse
Will do, hopefully it can get fixed. The GPS works fine, locks fast. It's when I don't have GPS enabled that it won't give a location using the wireless network now.
Wonder if making a single thread regarding auto brightness would be good. I've emailed HTC and they gave the typical "pull battery, factory reset" garbage. And after "exhausting" those "fixes" they simply say to call and RMA the device...ugh
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Stealth1985 said:
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Click to expand...
Click to collapse
My phone is completely stock. The dimming might be too little to be noticed, have you tried to shine a light directly in the light sensor, while being in a fairly dark room, so that you can observe the maximum change of brightness?
You could also download one of the sensor apps out there and see if the sensor works. Mine says light level 0 in a darker room, and max when i shine a light in the sensor.
I doubt the sensor is very useful though, as the brightness only goes from approx. 50 to 80%...(going from zero light to lightest) might be better if these values could be set.
About the video, the only camera I have right now is the DZ, so I'll see what I can do.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away.
Click to expand...
Click to collapse
That's interesting, thanks, I'll give that a try.
Sounds like the auto-brightness and the keyboard/cap buttons backlight (both of which use the light sensor) might both suffer from the same thing - i.e. very poor programming/implementation.
I have issues 1 and 2 (but not 3).
I would like to add that auto-brightness seemed to work fine when I (briefly) used CyanogenMod RC2, though I have no other Android devices to compare with.
I dumped the stock Sense ROM pretty quickly so this might have worked fine on the original ROM.
This definitely sucks, what ROM do you have that the location doesn't work too?
Pretty disappointed that I'm having these issues and HTC's response is send it in. I am not paying to re-unlock another phone because they can't make something that fully works.
Sent from my HTC Vision using XDA App
I have some bad news for you about point 1. It looks like a number of people on various unlocked android devices (N1, Desire, SGS i9000m) are experiencing the network location problem.
http://forum.xda-developers.com/showthread.php?t=845152
There is w (crappy, but still functional) work around, but...
For most of us it started sometime around Nov 14th.
It has some pretty unhappy implications for those of us who prefer android and want a top-end phone.
Good luck.
Damn Rogers seems to have screwed things up.
Sent from my HTC Vision using XDA App
Yeah. Maybe.
It seems to be an interaction between Rogers and unlocked android phones. We don't know whether it is all unlocked android phones, though, or even if it is specific models (i.e. would an unlocked Rogers Captivate have the same problem), or a specific OS (i.e. we don't know yet if the problem happens on eclair - while not directly useful to the DZ owners, it would at least help to pinpoint the problem and might help to get Google to step-up).
There are just too many unknowns, and how do you speak with someone with sufficient knowledge to speak intelligently? Rogers tech support hasn't been much help, and Google and Rogers seem to want to bounce the problem between each other.
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Uk htc z, stock rom.
-- sent from htc z using xda app
tbalden said:
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Click to expand...
Click to collapse
Could be that the app doesn't work with the DZ light sensor properly though ? I know my light sensor does something, because the keyboard/cap keys backlight turns on and off kind of randomly depending on light levels (and if you block the sensor then the lights come on).
Thats true. It happens here too. But still might be related...
-- sent from htc z using xda app
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
-- sent from htc z using xda app
tbalden said:
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
Click to expand...
Click to collapse
Cool, kinda sounds like it works, just very very badly.
Hi,
I've searched high and wide for a solution (other than sending it back to Motofailure repair) and am failing at finding one so far. So I'm hoping I can get some help from here.
So, this is the situation: I make a call, screen instantly turns dark and will only light up again when I press on the area where the light (&) proximity sensor is.
I've already tried the following.
1.) Done a factory reset (3x) - with mem card, with reformatted mem card, w/o mem card.
2.) Clearing the dust on the earpiece hole using an air duster.
3.) There were times that I worked properly after I've uninstalled apps but the issue came about again after a couple of tries.
So, now I'm thinking that I might want to root my Defy to set things right. I'm quite familiar with RSD Lite as I've used it before on my RAZR2 V8.
A bit of background: I bought my Defy on pre-order so this is one of the earlier models. I had the earpiece problem and sent it to Motofailure repair and the whole process took a month (32 days to be exact - long story. I'm avoiding having to send this PoS back. They updated the software when I got it back.
As far as I can recall, I didn't had this problem before the earpiece problem. And I'm thinking it might be a software problem hence I'm now looking at a solution by rooting and flashing the ROM with an original one.
I have no way of finding out (as far as I know) whether this is a hardware problem (hence hesitating to have it sent back to Motofailure repair).
What I've also observed is that when there is direct bright light, it works normally but when its dim, then the problem appears.
I don't have any screen protectors, just so you know.
Can anyone advise me on what to do?
During a call proximity sensor is activated to turn off the screen at the moment it detects proximity and asumes you are using the phone against your hear, so it turns off screen to save energy.
I think you might have some app installed in your phone, using and reversing the sensor status so it detects proximity when there isnt, and viceversa
You might want to try removing apps using that sensor and see if problem gets solved, there is also an app in the masket called sanity; which makes extensive use of proximity sensor for vaqrious things, and have an option to reverse proximity sensor, you might want to try it and see if problem gets fixed.
You might try this things: remove apps using proximity sensor, test phone. Deactivate in pocket detection; test phone, and install sainity, test phone, install a new rom?
If speaker is bigger than original one, or there was an assembly error, light/proximity sensor won't fit into right place.
I've seen such reports and you can't do anything unless you open up thing and check the problem, but you haven't seen the right assembly so you may not know the right place.
Are you using any screen protector? I know some screen protectors cause this problem.
Edit: Nevermind, I see that you're not using any.
how to calibrate the proximity sensor?
My new defy 's proximity sensor seems cannot work correctly,when i making a call ,the screen shut off immediately，and the screen could not light on by any key,but when i touch the proximity sensor with my finger,the screen may be light on!
so i download a app to test the proximity sensor which name's"Android sensor data",this app fingue out the state of proximity sensor,"near" or "far",sometimes I just passing my finger over the proximity sensor, the reading will show 'near' and then remain 'near' even when my finger is moved away!
Can anyone else help me to calibrate the proximity sensor?google told me some android phone can do this ,such as htc, zte etc.
goole tell me android phone have some standard testcode,such as *#*#4636#*#* can show the phone statue,it works correstly in Defy,*#*#0588#*#* test the proximity sensor ,but it doesn't work in defy!!!
I don't think this issue could be solved trough software tweaks. Chances are this is a hardware problem. Maybe you should contact the Motorola support.
try disabling in-pocket detection
have the same problem. it started 2 days ago. Im using CM7. It just turns dark and wont wake up unless someone else is calling me. Just got it tested, and when i cover the sensor with my finger it says 0cm distance for long time.
I've tried data wipe and similar, but nothing helped so far.
EDIT: I've just tried wiping the place where proximity sensor is with some soft cloth and alcohol and for the time being, it works. O.O
Could Wipe Dalvik help?
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
My understanding is that proximity sensor in note 2 is set for 8 cm and values are either 0 or 1 above or below 8cm
Sent from my SGH-T889 using xda app-developers app
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I have this exact problem here was my thread a few months ago:
http://forum.xda-developers.com/showthread.php?t=2099898
and the only response was to factory reset (which I haven't done yet and from what you're saying that won't fix the problem either...)
Quick question, I only see 1 light coming out of the two holes at the top of the phone, are there supposed to be 2 lights? (you can check using another camera since it uses infrared)
-- edit --
just found this thread on sprint forums:
http://community.sprint.com/baw/message/544084
apparently the person had a tech open it up and air out the sensor
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
same issue
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I had the exact same problem with the proximity sensor and other weird sensor issues. I had never rooted or anything. T-mobile exchanged my phone for a new one.
vaghotstuff said:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
Click to expand...
Click to collapse
This fixed for me too. But the sensors start acting up like every couple weeks and I'd have to blow air into the ear piece.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
TRY THIS
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
Thanks for advise! I'll try it and revert!
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
It didn't help! After the fix is installed the sensor works at the same manner... Is it possible to try something else?
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).
iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app
Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
mrgwap said:
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Same Issue, would love some tips.
bobolinko said:
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Click to expand...
Click to collapse
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Martsmac said:
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Click to expand...
Click to collapse
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
thanks
I appreciate the response , however I'm sure its not dirt on the sensor and that its actually an issue with the software (in this case Cyanogenmod 11 nightly build) not detecting it/initializing it correctly. My reasoning for this is that as soon as I revert back to the stock ROM my issue is gone.
Really hope someone figures this out but for the time being I'm going to have to use a different ROM/stock. Love CyanogenMod though so hopefully it can be resolved soon.
Skipjacks said:
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
Click to expand...
Click to collapse