So here is my problem: Some time ago i was using the "in pocket detection" and it was working perfectly fine, then i disabled it, then yesterday i enabled it and it wouldn't work :/
Since i thought it has something to do with the proximity sensor i downloaded some app that checks sensor output data and it reports value either 3.0 when i move something towards the sensor or 100.0 when i move away. I was wondering if that's the normal behavior. (not increasing linearly but rather acting more like a switch 1-0 behavior)
Also, i have no problems with screen blacking out during calls (it turns off and back on as expected), proximity lock works fine with an external app, but not with the "In Pocket Detection" in settings/display.
Any clues on what could be causing the problem and any suggestions how to fix it?
It is by no means critical but I just want to figure out what's wrong.
I think it's the correct behavior. The proximity sensor works more like a switch. I belive the In Pocket Detection also uses the camera and/or the accelerometer for the "detection" ...
Thanks for your reply.
Well, in the end i just flashed CM7 on it so i don't have the in pocket detection anymore
Related
Hi
how can i disable the proximity sensor on my HTC Touch Pro 2, windows mobile 6.1 ?
I use a screen lock app that dims the screen during calls but when coming near proximity sensor during call, the screen is turned on again - a real pain.
Please if any onw have an advice to shut it off cpmpletely or when i am on bluetooth i would be really happy for some help
PS i thought paroximitysensor was supposed to disable when tp2 is connected to bluetooth - but its not ??
thanks
Nolan
no one ?
regards nolan
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
thisisallen said:
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
Click to expand...
Click to collapse
Hi
could you test teh cab and tell us here if that can turn of permanemtly the proximity sensor ?
regards Nolan
TurnOffTheLight works to turn off the backlighting but as soon as you move the phone the proximity sensor kicks in again.
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
thisisallen said:
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
Click to expand...
Click to collapse
Hi
light functionality would not solve the problem regarding proximity sensor - its 2 different matters unfortunately
regards Nolan
i have allmost the same problem. my sensor is broken and alwayas is "On". so when i make a call on my hd2 android 2.2 screen goes off and never goes on again. how to kill it???
Called today helpdesk with same problem, cant be turned off , must go for a repair.
Proximity Sensor behavior and solution
I am a late comer to this bb! Hey,I thought all the bugs would be worked out by now! My keyboard did not work right, .... and I have had several other problems with the touchpro2. What are the Chinese doing over there? I had programmed many embedded units and microprocessor systems, but, really, how can they mass produce units like these? Too many cooks in the soup? They are leaving their quality control to the general community.
My problem was I use my gps for bicycling, and if I place it in the support case, the proximity sensor would shut off the screen, even though I was not placing a call. The screen would blank and not come back on. I noticed there was no problem if the physical keyboard was opened and also if the unit were held horizontally. It did this all the time, regardless of the app running.
There are two sensors at the top of the unit: proximity sensor and light sensor. This is a problem with the proximity sensor, at the left.
So I just placed duct tape over it. Now it does not blank.
Noticed recently that When a phone call is in progress, the screen will go black no matter what and to get it to come back i have to manual hit the top power button.
I first noticed it with energy rom. When autobacklight was enabled, their was no getting back to screen at all. Disabling autobacklight at least allowed me to get the screen back after clicking the power button.
I switched to core cell rom and noticed the same issue, however, i can manually turn the screen on again even if autobacklight is enabled.
I have no further problems with the proximity sensor, just this one.
Is their perhaps some sort of proximity app that i could use to diagnose whether this is a hardware problem or software problem?
Ok, I had a similar issue, where the phone screen would turn off as soon as the "send" button was pressed, and the only way to turn it back on was either hanging up, or waiting till it felt like coming back on.
My proximity sensor was stuck "on". I could see the sensor status in the registry (don't remember offhand the reg entry, but it's a live reading of the sensor, 1 or 0). I installed "Proximity Sensor for Screen Off v0.2" from http://forum.xda-developers.com/showthread.php?t=624206
That was a mistake on my part, though... then the screen wouldn't come back on! It took some real finagling to get the screen on.
To fix it (temporary? permanent? dunno...) I waved a small neodymium magnet over the sensor (near the ear speaker). I have no clue why that worked. I don't know why it stopped. I *definitely* don't know if that's the issue you are having. But it's worth a shot
I've never had this issue after many different iterations of the Energy ROM.
Do you run Task29 when you flash ROMs?
Yeah i always task29. I don't believe it is the rom since i have tried another rom and the problem persisted. I tried the magnet idea but it didn't work. It was a refrigerator magnet though so i didn't expect it to. Anything else that requires the prox. sensor to work, has no problems and that is why this is weird to me.
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
Dont know about the bluetooth thing because i dont have one, but i do have issues sometimes with the proximity sensor when on calls. For example i will dial a number and put the phone to my ear talk awhile and then need to switch to speaker or look at something on the phone while still talking. But when i take the phone away from my ear, the screen stays off, and i have to swipe my finger over the sensor to get it to come back on.
I don't seem to have an issue with that. What seems to happen is that, IF the proximity sensor is covered, and you place a call or answer a call with your headset, when the device "wakes up" to the call screen the proximity sensor defaults to uncovered ( "far" ). Then the sensor does not start responding again until it is actually uncovered.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Anyone?
Hmmm... So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
Hello!
I've started to have a problem with proximity sensor. While calling, the screen get black and there is no way to turn it on (it turn if the other persone close the call only).
I tried to install a proximity sensor controller utility and it says it's always 0cm distance. By touching it I found it unlocks sometimes under pression or temporarily if I blow in it (but after a little it locks again).
I searched in settings an options to deactivate it but I really can't find it..
Can you tell me where I can find the option to turn off the proximity sensor, please?
And is there any way to fix this problem eventually? However I'd be happy if I can just deactivate the sensor..
Thanks
One of the touch screen issues I sometimes experience is when swipes are "broken" and register as shorter swipes and taps. This makes me think maybe the accidental touch protection, which is supposed to be triggered by the proximity sensor, is being triggered when it shouldn't. We all have read complaints about how the proximity sensor does not work very well.
So on a hunch, last time I had this issue (trying to swipe in gboard), I stuck my finger on the front-facing camera, and interestingly, swiping worked fine (I expected the screen to be disabled - guess that only actually is supposed to happen when you're on a call?).
Since this issue is so random it's hard to really test it. But I've had quite an experience with the proximity sensor.
I wanted the AOD to turn off when the phone is in my pocket, which is the norm on other phones I've used but for some reason Samsung does not do. So I set out figuring out how to do this in Tasker. I got a sensor test app and noticed the proximity sensor basically has two values: 0.0 and 5.0. It is very slow to respond (slower for "uncover" events) and seems to only switch to 0 if my finger is right on the camera. So I set up Tasker to turn the AOD off if the proximity sensor value is < 1, or on if it is >= 1. I also made it vibrate briefly so that I could tell when the sensor was toggling even if I couldn't see the AOD.
At first it worked fairly well. If I manually covered and uncovered the camera, the AOD would dutifully toggle (not instantaneously). But in "real life" practice, it turned out to be quite unreliable. There would be phantom proximity changes while I was using the phone or carrying it -- most interestingly, it often toggles the AOD off briefly when I pick up my phone -- but I didn't really notice any surprise vibrations while the phone was in my pocket. After a couple hours, when my living room got darker (not completely dark), the whole thing went crazy and the AOD would toggle every few seconds with the phone sitting on a table.
So I think the whole "let's ditch a dedicated proximity sensor and use other things to get the same result" is not quite mature yet. And perhaps it is buggy enough to cause one of the issues we think of as a touchscreen one.