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 !
Related
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?
Proximity sensor kine of stopped working..
If I make a call and place the phone to my ear, the screen will turn turn off, but when the phone is pulled away it won't torn the screen back on.
This makes me believe is not a hardware issue just a little software conflict with maybe some app that maybe be solved by resetting the phone off but I don't want to do that.
Does anyone know which app I can clear off data/cache that may make this thing work again?
Note: I have used AndroidSensor and some other apps to test proximity ans light sensor and they don't seem to work, according to the app.
Thanks.
Edit: Never mind guys, I deleted the last 10 apps, rebooted and it came back to life.
Delete thread ......
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?
solved
seijidinzuala said:
Hello,
I bought a Redmi 1s online and from the very first day, the proximity sensor doesn't work well, whenever I made a call, after putting the phone near my face, the screen goes dark as normal but it sometimes just won't turn back on. I tried calibrating it through *#*#64663#*#*, I was able to calibrate fine 2 times, but after putting a screen guard on, the sensor became buggy again.
*I've tried flashing different ROM's which doesn't help
*I've removed the screen guard and still buggy
*I cannot calibrate the sensor anymore and just fails
*I've tested the sensor with a 3rd party app from play store and it seems to work fine in that app.
I'm currently out of ideas, can anyone help me?
PS: Sometimes, the screen goes off right after hitting the call button and wont turn back on until the call ends.
Click to expand...
Click to collapse
Yes problem with proximity sensor was their and because it was on base rom so it reflected in other roms too. Currently i am not experiencing it in miui 6. So either try miui v50 (Latest official stable update) or try miui 6.
Again its a software problem and will be solved.
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Hey, you can use the APP that comes with your phone to check if the proximity sensor fails.
How to open it: HiCare-Service-Smart diagnosis-Auto
Good luck
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Lord_Maumad said:
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Click to expand...
Click to collapse
Do you have a black screen when you are talking?
When the sensor is locked, no. Sometimes the screen turns black immediately when I get the phone call. That is, the sensor is locked. Passing the finger over the sensor a few times, it unlocks and goes back to work.
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
have upgraded to version 184 and the problem continues. I don't know what to do. Disappointment with Huawei
cashif said:
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
Click to expand...
Click to collapse
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Lord_Maumad said:
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Click to expand...
Click to collapse
Problem stopped after updating to latest firmware 184 version
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?
Unfortunately I'm not ?
I don't know if it is updated firmware bug or hardware failure. My friend's phone has this problem too, and even worse when dialing or listening to voice SMS in FB messenger, the screen was off until the voice finished. I thought it was full cover screen protector; however, it was not after I suggested him to take off the screen protector, and the problem still persisted. Anyway he told me there was not any problem before updating.
Lord_Maumad said:
Unfortunately I'm not
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?In addition, can you check whether the position of your sensor is clean.
I'm not, and it's clean. It works until I put it in my pocket, then it gets stuck.
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Lord_Maumad said:
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Click to expand...
Click to collapse
My friend just sold his mate 20x with proximity sensor error and bought a new one with the same firmware version 9.0.0.184. The new one worked functionally with its proximity sensor. I think that his previous mate 20x had proximity sensor hardware's problem, not dead but not functional.
Ich have the same issue with a P30 Pro New Edition. I hope it's a hardware issue and the replacement unit will be fine.