I bought my Atrix last Saturday. Rooted it using SuperOneClick. Noticed the following problem:
I dial an access code to a VoIP service, listen to a dial tone, bring up the dialer and are trying to dial an exension number. If any part of my hand goes directly over the proximity sensor, even within 2" of it, the screen goes blank, numbers are not registering. It appears that the proximity sensor does not shut off when the dial pad is being opened to dial an extension.
I wonder if rooting could have caused this problem or it is Motorola's shortcoming?
Strange. I am having the exact opposite problem. When I make a call from time to time, the proximity sensor fails to kick in and the screen stays on. I end up either dialing digits or hanging up on the person.
It doesn't happen all the time. I am trying to narrow it down, but I think it happens only after I use my in car bluetooth unit to interact with my phone.
After a reboot - all is well. The proximity sensor functions normally.
Check your horizontal calibration. I found that the screen-off is triggered when the phone goes vertical. Try it. Cover the prox and tilt the phone vertical
Sent from my SAMSUNG-SGH-I897 using XDA App
I tried in horizontal and vertical positions. Same result. I am not sure I know how to check horizontal calibration.
my proximity sensor was not working either, it would not shut off the screen during a call. i too use a bluetooth speaker in my car so i tired the reboot and it worked.
i also then tried putting my finger over the sensor and after the screen went blank i swiveled the phone horizontally and the screen came back on even though my finger was covering the sensor. while keeping my finger on the sensor i could get the screen to turn off by rotating the phone back to a vertical position. it would seem there are two issues here
I am having the same problem as Ed and hondaguy. I too have isolated my issue to using my cars bluetooth as well. It only occurs when I have the phone connected and choose to talk on the headset (unclick the bluetooth button on the phone). I can talk over bluetooth and not have this issue afterwards.
Related
Well, I've searched the forums for this phone and I haven't found anyone with this issue.
When I make or receive calls, the proximity sensor either doesn't turn off the screen or, more often, it does but turns it back on after a while. This results in random keys being pressed making noise and, eventually, it presses the button to end the call or puts the call on hold and dials another number.
It's very, very annoying. Could it be something on the settings? Hope it's not hardware... Any sugestions on how to solve this?
I'm using Miui 1.9.9 with franco.kernel from 10 set.
The proximity sensor is located at the top left corner of the phone (next to the speaker) and flashes red while active. Make sure you cover this area with your head when speaking. I am left handed and sometimes the sensor doesn't detect anything because of the way I hold it, this could be the case with you also...
There are some apps that can help you test the sensor if it works or not.
Mine was stupid too with stock rom, but with custom roms it works very good. detects even finger in 3cm range and turns on screen after 2 seconds.
My defy+ proximity sensor is not working.
As soon as I make a call, the phone screen goes black. The call goes thru fine, but the screen goes black.
No, I don''t have my finger or face near the proximity sensor.
No mods on the phone OS.
I did some debugging-
Cleaned the back of the phone by blowing air.
Tried the screw loosening like in the youtube video
Changed brightness settings from auto to manual.
Changed display turn off from 1min to never.
Finally, I downloded a sensor app and checked for change in the value of the proximity sensor when put by finger in the sensor area. The value was stuck at 3%, no matter what I did.
I was playing around and when I pressed the speaker area near the proximity sensor, the sensor value jumped to 100%
So I think the glass is blocking the sensor (or acting as a reflector).
Just to make sure the glass was the issue, I made a call by keeping the speaker area pressed. It worked as expected - no screen blanking after call. It does go black if I put my finger in the proximity sensor area.
I have no idea how to fix it.The screen & sensor need to be pressed closer.
Only thing I have tried is tighten the screws in the back. But no use.
Any help?
Since you don't have mods, it's probably broken, go to customer care.
Or you can maybe try factory reset
Do you have a screen protector?
Out yes remove it.
If not your sensor is broken.
Sent from my MB526 using XDA Premium 4 mobile app
Hi everyone,
since a few weeks i got problems with the proximity sensor on my i9505
First i thought that it is software related but after clean installing a new ROM yesterday i see that the problem still exists...
It happens when the proximity sensor should react, when i am close to it, it reacts and activates but the problem is that it wont turn off again...
i dialed the test menu and went to sensor test, as i see the sensor sees the distance normaly, when i bring it close and when i move it away i see that the numbers react how they should, however after the sensor is once trigerred with a close object it starts to vibrate and the screen turns green (how it should), but after moving away it registers the distance but it won´t stop to vibrate and turn off :/
Anyone who knows what could be wrong?
I have to mention that the display was changed once (because of the glass broke) but it was working normal for months...
EDIT: after testing again i see that the sensor sees the distance just as it should the only problem is that once that the sensor action is triggered to 1.0 from 0.0 it stays at 1.0 no matter if i remove my hand...
After LP update I noticed, that my phone is having issues with proximity sensor during calls. Usually it happens more often when I hold it by my ear with left hand, but happened already even o right ear. Screen goes on during call and I press buttons with my ear, usually ending up with call on hold. I dont remember these problems on KK.
So I went to service menu and tried HW Device Test (2nd option in service menu) - ACL Proximity test. It seems to work quite well, phone detects my hand closing to proximity sensor at cca 3-4 cm activating NEAR state.
But when I go to Device test (1st option in service menu) and select Service Menu - Auto Test then in shows Pass on first screen, so I manually touch Pass button. And on second screen it says in red Proximity Cal Fail. And only option is to slide Exit button to end test. Seems that my proxy sensor calibration is failing, but maybe I'm supposed to do something to avoid that? Can someone verify, if it is standard behavior of this test? Thanks ahead...
@Wlk is this issues resolved sir ? I got the same with yours
Here's a solution that I discovered. In the Autotest (see OP post), choose "FAIL" instead. Then, it will let you calibrate the sensor by asking you to cover the sensor, and uncover the sensor. Then, it will recalibrate properly and all the proximity sensor issues vanish . Exit the Hidden Menu and you're done.
I have problem with my s10+ exynos.
When calling and the phone is on my ear, the screen turns off.
However when moving my phone away from my ear the screen stays off during the call.
I have to push the power button to wake the screen up.
With my s7 edge the screen used to turn on when I moved my phone away from my ear when in a call.
When dialing *#0*# for the test menu's, clicking the sensors button doesn't show any proximity sensor at all?
I removed the screenprotector and the issue happends with both case on and off.
When recording sensor activity with the app Androsensor, the generated csv clearly shows that the proximity sensor goed from 2 to 0 and back to 2, so I don't think it's a hardware issue.
Also booting in safe mode and factory reset doesn't resolve the issue.
Am I missing somthing in the settings?
Is anyone else running into this issue?
I contacted the shop where I bought the phone and they told me that it's very likely to be a defective phone.
So I will send the phone back and once they have confirmed the issue, they will send a new device.
same thing happens to me
Update - it stopped happening on my phone all of the sudden. Now it is working fine.