Does anyone know if there is a way to adjust the proximity sensor.
It's proving a problem for my wife who uses the phone. When she's on a call the phone is intermittently sensing if she's holding it to her ear.
Hence being a capactive screen, when her cheek brushes the screen during a call the other end either hears DTMF or gets cut off by it touching the end call.
I called her yesterday and kept getting random DTMF digits sent to me, then I got sut off.
I was watching her use the phone and the screen was de-activiting (correctly going blank) for part of the call then coming back on, this would happen several times during one call.
Is this a hardware issue or software bug. Has anyone else suffered this problem?
Also happened to me a few times touching end call wih my cheek, really annoying.
Anyone else having the same problem with the proximity sensor intermittently not working during a call?
I had that problem on the old 1.43 ROM but it was fixed when I upgrade to 1.48.
I have this problem and I constantly have to call back and say sorry to my customers and blame it on the phone...
I have reported several errors to HTC and all i get back is "Take it to the retailer and get it changed, it must be a hw error", annoying as hell
1.48 not yet official in sweden.
TouchLockPro
You can try TouchLockPro, it has an InCallTweak, using the GSensor. Searching for accessing programmatically the Proximity Sensor though, for more options (e.g unlock by Proximity Sensor). It works on HTC Leo, people confirmed.
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
philtrick123 said:
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
Click to expand...
Click to collapse
Indeed, TouchLockPro detects itself the available sensors and uses the available ones. Of course you can configure detailed things (via pressing the BattClock), but the defaults are already the sensible ones
Thanks again ZuinigeRijder.
Just been doing some more testing and occasionally the screen flashes on for a brief moment during a call. Could it be the proximity sensor trying to turn on the screen? Or is it the G sensor not being very accurate?
In the application is there a way for me to adjust the G-Sensor angles that activate the screen off? i.e. 45+ Degrees activate ??
Or are there any other adjustments I could make during testing??
I found one more problem... I checked it several times....
If u make a call using portrait orientation of phone app (Rotated using BSB Tweak). Proximity sensor doesnt work at all.... i made a while lyin on the bed and no matter wat i tried it wasnt turning off the screen....
Then i kept it in portrait position for a few seconds den proximity started working again...
Is there anyone who can confirm me with this problem.... or is this issue only with my HD2
Does proximity sensor work for anyone?
I don't see it listed as "not working" in any build and as far as I understand it's supported by kernel. But my screen doesn't turn of in calls and can sometimes turn on loud speaker or drop off a call with my ear. In WM screen is turned off automaticly and you can't click anything.
Works perfectly in the last 3 sense buils i tried , altho i do remember the screen flasing like a strobe at my ear in earlier cm builds
Sent from my HTC HD2 using XDA App
Hello all.
I have a Samsung focus with an "always on" proximity sensor. So the phone does not light up after it has moved away from ones face during a phone call, making it impossible to use after any call without a restart.
I have tried the following solutions.
1- Soft Reset by pulling the battery and waiting
2- Hard reset using numeric codes provided in the ref threads
3- Using the diagnostic menu.
With regards to the third one. The proximity sensor menu shows that the sensor is always "on" no matter where the phone is. But there is no "set" or "reg' button that I can find with which to recalibrate it, the only option is "exit"
It is quite possible that I am missing a feature or function or I need a new solution. If anyone has any insight that would be really helpful.
Thank you in advance.
Same
I have exactly the same problem. Did you solve it ?
You will need to give a little more information. What os version are you running and what diagnostic app are you running. I think the most up to date diagnostic app is ver(.0103).
1. uninstall your diagnostic app
2. install the diagnostic app again to get latest app ##634#
3. open the diagnostic app and type *#0*#
4. tap the proximity sensor button and see if you see set reg and exit soft keys
Issue with proximity sensor in Samsung focus sgh i917
I have the same problem. My LED screen broke recently and replaced it.
It looks like after the screen replacement, the phone's proximity sensor is always in detected mode [in the diag]. So when ever a phone is made or answered the LED screen goes blank disabling all functionality till the other person disconnects.
I ran the diag but it doesn't give me an option to calibrate the sensor. I tried to install the latest diag tool too but same results. There is only one button, "EXIT".
The diagnostic app version is .0628
OS version is 7.10.7720.68
Please help.
During a phone call any attempt to scroll down from the top of the screen turns the screen off.
This is caused by the proximity sensor, and according to Official Samsung representatives, cannot be disabled.
I have rooted my device.
Now, how can I disable this?
Thanks!
As with most things, a simple Google search finds the answer.
Google search: s5 disable proximity sensor xda
Third search result
.
it seems my proximity sensor is not working. when i receive a call the display stays black. is there any solution or does anybody knows a dialer that has the option to deactivate the sensor?
(currently i'm using crDroid 6.3, but it happened in other rom's too)
found a solution that works for me: it's an app called "Proximity Screen Off Lite"
this app uses the device administrator permission.
+++update+++
worked for a certain time but stopped because of unknown reasons