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.
Related
I always seem to touch the "end call" button with my cheek when I'm calling someone since my god damn screen wont turn off when I'm in-call.
Anyone else experienced this ?
depends on my experiences, the screen turn off when u r in call after (5-10 sec) coz the sensor of screen in covered thought in call just in foryo 2.2 the screen turn off directly( this sensor located in the upper right corner of screen in x10
So if your screen not turn off all the time when in call is active ,so you need to check the sensor it's work or not
i think the is software to check all the sensor and bluetooth,wifi....etc named benchmark in the market try to download it but first check ur screen after 10sec when u r in call and check the sitting ok
Hi - The proximity sensor disables the screen - you can test that it's working by going into the service menu and checking it.. it's Menu, Back, Back, Menu, Back, Menu, Menu, Back.. Then go into the service tests menu and check if it works... if it's working in there, then I suspect that you may be using a task killer and it's interfering with the workings of your phone.. ditch the task killer, it's a waste of resources anyway..
I have this problem as well & I know the sensor is working because I went into test mode & ran the test. I have no task killers installed & the screen stays on during a call. The screen shuts off at the set screen timeout interval but the sensor doesn't seem to do anything, except in the test mode.
On other phones like the N1 & IPhone 3GS if you cover up the sensor the screen will shut off but with the X10 it stays on.
I have this problem to! If anybody knows something please tell us.
Me too, may because Firmware bug?
Sed from my X10i @BKK
phoneguy 4567 said:
I have this problem as well & I know the sensor is working because I went into test mode & ran the test. I have no task killers installed & the screen stays on during a call. The screen shuts off at the set screen timeout interval but the sensor doesn't seem to do anything, except in the test mode.
On other phones like the N1 & IPhone 3GS if you cover up the sensor the screen will shut off but with the X10 it stays on.
Click to expand...
Click to collapse
no this sensor responsible to check in call and turn off screen but i guess there is problem in firmware (BUGS) coz if there screen not turn off the battery will drain via (2-3)H of call !!! not possible
The sensor disables the screen ...
It doesn't turn it off. Your screen will turn off after your normal screen time out.
Easy to test, ring someone then cover the sensor with your finger and try pressing end call. It is locked so won't end the call. Remove your finger and press the end call. Call ends!
Your right!!!
Strange way to do things IMO because it's a waste of battery leaving the screen on. I still think the sensor software is buggy because I've been in calls where I accidentally hit end call with my face .
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.
For the last 2 or 3 months I've noticed my proximity and light sensor don't work on my Focus 1.3.
The screen doesn't turn off while on a call and the camera button can wake the phone with the screen turned off.
I've also seen that the screen doesn't auto dim any longer when in a dark room.
I held off on doing the warranty swap with ATT because I thought Mango might fix it but I haven't had any luck.
Do you have any suggestions?
When you mean the camera button wakes the phone up, does it launch the camera app, or is it like the power button is pressed (when the screen is off)?
Archange1 said:
When you mean the camera button wakes the phone up, does it launch the camera app, or is it like the power button is pressed (when the screen is off)?
Click to expand...
Click to collapse
That I have seen was a setting I had in the camera settings but the rest I've seen still stands.
Diagnosis app
So basically you need to recalibrate your proximity and light sensors with the diagnosis app. Please read the sticky thread for diagnostic codes. This issues has been discussed. Off the top of my head I can't remember the codes how to do it. I would search the forum for proximity sensor and light sensor recalibration.
Update-
1. If you don't have the diagnosis app you need to type ##634# in your dial pad
2. type *#0*# - diagnosis app not the dial pad
3. Recalibrate the Light and the proximity, then restart your phone. Should be fixed.
As for holding the camera button and the screen lights up. That is an advantage/shortcut to get to picture mode. That setting can be disabled if you go
1. Windows home live tile screen
2. settings
3. Swipe over to applications
4. pictures + camera
5. disable press and hold camera to wake up the phone or enable prevent accidental camera lauch when phone is locked
siralex241 said:
So basically you need to recalibrate your proximity and light sensors with the diagnosis app. Please read the sticky thread for diagnostic codes. This issues has been discussed. Off the top of my head I can't remember the codes how to do it. I would search the forum for proximity sensor and light sensor recalibration.
Update-
1. If you don't have the diagnosis app you need to type ##634# in your dial pad
2. type *#0*# - diagnosis app not the dial pad
3. Recalibrate the Light and the proximity, then restart your phone. Should be fixed.
As for holding the camera button and the screen lights up. That is an advantage/shortcut to get to picture mode. That setting can be disabled if you go
1. Windows home live tile screen
2. settings
3. Swipe over to applications
4. pictures + camera
5. disable press and hold camera to wake up the phone or enable prevent accidental camera lauch when phone is locked
Click to expand...
Click to collapse
So this should work for both?!
This makes me very happy! I'll report back soon.
Huh when I get into the Proximity recal it only shows XXX (No Detection) and never changes anything.
Am I doing it wrong?
EDIT: The value reported for light is staying at 0000 too.
http://forum.xda-developers.com/showthread.php?t=1045167&highlight=proximity
Is hinting that I have a busted set of sensors and will need to warranty it.
play with the set and reg button. Also, restart the phone to see if it will work. Not to insult your intelligence but you know where the proximity and light sensor are right? Hold your finger in front of it on it moving it further and closer. If none of these work you might have defective sensors. I like to try everything a couple of time before I take it in for warranty.
I do know where the sensor is, right next to the earpiece.
I've restarted the device and tried the sensors again but no luck.
When I try to set the light value at something I get some error about "Light_SetCalValue : DeviceloControl failed" and for the proximity test the screen always stays red even if I cover the whole phone with my hand.
I'm in the same boat. I've been debating on just rolling all the way back to stock and starting all over. Of course if it is a hardware issue I'm just going to be wasting time. Then again it probably would be best to roll back before sending it in on a warranty issue...
My other concern is if they do cover it what am I going to get back? Don't really want to be stuck on a Rev 1.4 focus as that STILL seems to be causing issues.
I hear ya tanders04, it would stink to get a 1.4 back.
Also, thank you siralex241 for the help.
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...
I´ve searched this forum, but found nothing like what I am facing. As per title, whilst on a call, with the phone on my ear (left ear usually, if that means anything) the on screen buttons are pressed, because I usually end up with the call on hold. Other times, it finishes the call, other times it dials a number from the contact list...Here´s a list of what I have done so far with no success:
1. Calibrate proximity sensor with apps
2. Use hidden menu to test functionality (it works as advertised)
3. Calibrate motion sensor
4. Full reset of the phone
5. Clear dalvik cache
6. Test sensor functionality with app (again, works as it should). It detects when my hand is covering the sensor and it detects when my hand is taken away from it. Instantly. Also, left my hand covering the sensor for a while (simulating a call) to see if at some point it stopped working, but no, the darned thing worked as it should.
I read somewhere here that a mod on build.prop might help (it has to do with the delay time of the proximity sensor) but since the post didn´t explain the exact setting, i googled it, and found 2 settings that might apply:
1.) ro.lge.proximity.delay
2.) mot.proximity.delay.
Neither of them is in my build.prop file, so, the questions that pop to my mind are:
1.)Which one of the two would affect the described issue? Apparently those settings are modified by users that had a problem with black screens after a call or with long delays for the screen to come back after taking the phone from their ears to use the keypad, but no post that I read indicated which one of the settings influenced what. I have the feeling that one of them is for the proximity sensor to "kick in" while the other controls how long does it take for the screen to come back after the proximity sensor stops detecting your ear.
2.)Can I add that setting to my build.prop without risking a bootlop or a brick?
As the title say, I have a D800, with official AT&T 5.0.2 ROM, rooted, with stock recovery.
Any help would be highly appreciated. As you can imagine is terribly frustrating that I cannot use my smartPHONE as a PHONE because of this!
Thanks in advance!
Frank.
a small, shameless bump!