Develop Bugs

[Q] Proximity sensor problem(?)- can flashing a ROM solve it?

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 always on

Hi guys m facing a strange issue. I have observed that sometimes my proximity sensor remains on. I tried to find out the app causing it by Force Stopping each app one by one but that doesn't solve the problem. .
I am not using any motion like quick glance which uses the sensor or any other app like turning the screen on off (eg smart cover etc)
only a reboot fixes this issue but after sometime (say few hours or 1-2 days) the sensor turns on. . Can you suggest me what else shall I do? coz m observing more than normal battery drain in stand by mode. . Please help!
Sent from my GT-N7100

Try turning off "quick glance" under settings--> motion.
Sent from my GT-N7100 using xda app-developers app

bkgoyal said:
Try turning off "quick glance" under settings--> motion.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
kuberchib said:
....
I am not using any motion like quick glance which uses the sensor...
Sent from my GT-N7100
Click to expand...
Click to collapse
So it helped a lot are you using custum rom or stock? With stock I only have this on when quick glance on. I helped a lot too :s
Kalgan :s

m using stock rom and kernel...and I am not using quick glance..my phone's proximity sensor remains on even when the screen is on (unlike quick glance)
Sent from my GT-N7100

I have the same bug... only a reboot solves it.

mdalacu said:
I have the same bug... only a reboot solves it.
Click to expand...
Click to collapse
at least m not alone
Sent from my GT-N7100

me too same here dagnamit

I too have noticed it and posted it on a thread also
I also notice this..only now i came to know that it is proximity sensor..will appear as a dim red right and if it stays on, it turns off only if restarted..might be a bug..should we report it to samsung so that they will fix it in updates?

I have noticed one thing that after 2+ or more (random) days of usage if I receive/make a call the sensor doesn't turn off. .might be this is a s/w bug. .but this is what I have noticed after closely monitoring my phone. .
Sent from my GT-N7100

I've noticed this too! Didn't know the dim red light was proximity sensor. But i've noticed it only twice (with battery below 40% on both occasions).

Viber has a known bug that cause the proximity sensor to be always on. If you uses it, u need to update to the latest version i think its v2.2.3.109.

antt00 said:
Viber has a known bug that cause the proximity sensor to be always on. If you uses it, u need to update to the latest version i think its v2.2.3.109.
Click to expand...
Click to collapse
Viber's bug was fixed months back and I have the updated version too
Sent from my GT-N7100

Got the same thing, however i didn't notice it affecting battery life whatsoever, still an awesome battery life.
Still, I would love to see what's the cause of this and how to resolve it.
Sent from my GT-N7100 using xda premium

I have the same problem

I don't know y but I turned off "Increase volume in pocket" in settings and rebooted my device and the problem didn't return since last 4 days. . strange!
Sent from my GT-N7100

Its on on all gn2 i have seen. Im getting 8hrs screen on time so i dont really care if it stays on as long as its not affecting my battery i'm happy
Sent from my GT-N7100 using xda premium

kuberchib said:
I don't know y but I turned off "Increase volume in pocket" in settings and rebooted my device and the problem didn't return since last 4 days. . strange!
Sent from my GT-N7100
Click to expand...
Click to collapse
Even though I first got this proximity sensor bug after I turned on "increase volume in pocket" (only 1 time so far), I'm pretty sure it's not related, because I did a few tests and as far as I could tell the phone increases the volume based on its position (and possibly movement) in the second it receives the call. If it's vertical (like in a pocket), or on its side (like in a bag), when you get a call, it will increase the volume. If the phone is horizontal, like on a table, and starts ringing, the volume doesn't increase, and it won't increase even if you pick it up and move it around while it's ringing.
I also thought initially that it uses data from the proximity sensor, but I tested and it doesn't care if it's covered or not when the phone rings, it appears to use data from the accelerometer/gyro exclusively.

I'm try turn all motion off right now. Let see if it can solve the problem

I have the same problem.
I resolve it by pressing volume up + home + power.
Let it restart and so far after about 1mth+ did not encounter this issue any more.
Hope this help :fingers-crossed:

i have the same problem
all motions are off
and still have it random....only restart to close the sensor

Proximity sensor seems to not work anymore

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 !

Proximity sensor calibration or fix?

OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.

absinthesummer said:
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.
Click to expand...
Click to collapse
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy

absinthesummer said:
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy
Click to expand...
Click to collapse
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure about changing the range, I'll look into that but yeah depending on the screen protector it could interfere with the sensor, especially if it's particularly thick or dirty. I don't use screen protectors anymore for that very reason. They can muck up the sensor and make the front camera take fuzzy pics.

[Q] Accelerometer Calibration?

So it seems the y axis is off a few degrees. Which is noticeable when play games like Bike Race where you tilt the bike. While holding in landscape the phone shows level if you tilt to the right a tad. Anyway, is there a way i can calibrate the accelerometer. I see some apps that have calibration tools but that only fixes it within that app. I just got the phone and i am within my 14 days to return, if returning would be a simpler option.

Try *#0*# in dialer and hit sensor hub test that and sensor, sensor lists everything individually

Ok that's what I did to find the issue. I think you hit sensor button. Sensor hub test just runs some test and comes back with passed, but no options. Under sensor you can see the accelerometer data and that it's off but no way to calibrate.

So I took my phone back to at&t to get an exchange because of the accelerometer. While waiting i tested the display model and guess what. Same issue. So I asked if i could get a replacement he said yes. When i explained the problem he said he hasnt heard of that before. Then tried the same thing i did with the display model. So if anyone would perform this test on theirs for me i would be appreciative. Just go to Test menu (*#0*# in dialer) and hit sensor and see if your Y axis is correct. Mine shows -3 when on the level surface.

X=0,y=0, 90 degree angel, with and without case on

Didn't there used to be a calibration setting in device settings to get the accelerometer back on its appropriate axis?

arjun90 said:
Didn't there used to be a calibration setting in device settings to get the accelerometer back on its appropriate axis?
Click to expand...
Click to collapse
Way back on the note 2

Yep I wonder why they removed such a basic function. Anyone else with their stats before I exchange tomorrow? It's the 14th day.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

thejanitor86 said:
Yep I wonder why they removed such a basic function. Anyone else with their stats before I exchange tomorrow? It's the 14th day.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
X=0, Y=0, 90 angle laying on the table
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

So I had it swapped out today. Same results. So the only thing i can think off is its something wrong with the batch there. So i will have to see if i can get a different one from somewhere else. I will call At&t Monday. Hopefully they wont be too difficult to deal with on this issue. On the plus side the new one isnt quite as off.

Mine