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.
Related
Hi,
I'm using an original ROM for TP2 with Manilla 2.1.38158.2 (as shown in Settings | About).
AFAIK this version should include the "in-call curtain" functionality, on which the call buttons are locked during a call. However, I see no sign for this anywhere.
Does anyone have an idea how this feature can be turned on, or how do I add it?
The curtain is unnecessary. Your device as a proximity sensor that turns off your display when you hold you face it. You don't need the curtain to lock the buttons. When you move the device away from your face, you probably want to use the touch screen so it turns back on.
I usually talk using a Bluetooth headset while the device is kept in my bag or pocket. The proximity sensor should theoretically detect that the device is covered and keep the screen off, but it often fails to do so, allowing random buttons to get pressed.
S2U2 doesn't solve this either, as it keeps the device unlocked during phone calls. There's TouchLockPro, but I don't like the way it works.
Have you tried CSDEVCTRL? I recall it allows you to lock the device during and after a call.
Yes, I found it in one of the forums here a couple of weeks ago. For some reason it didn't keep the device locked during calls, though specifically configured to do so. I haven't looked deeper into that, since I thought that the supposedly built-in curtain would do.
BTW, a simple test shows that the proximity sensor is completely useless for this scenario. I put a small object on the sensor, locked the phone and turned it off. I then called it from another phone and answered using the Bluetooth headset. Although the screen was blocked with an object, it was completely unlocked and could be pressed. The proximity sensor turned the screen off only if a movement was detected towards the screen, and not when something was already blocking the screen.
I repeated this test several times with the phone in a bag. I locked it, called, answered using the Bluetooth headset and tried to press against it from outside the bag. In every single time on-screen buttons got pressed.
As a matter of fact, the TP2 is way worse than the original TP in this sense. In my previous TP I could answer a call using the headset, take out the phone (carefully so it won't hang up by a screen press), lock it again and put it back in the bag/pocket. Now with the TP2 the proximity sensor wakes up the device unexpectedly, so I can never keep it inside anything during a call.
There is a shareware Pocket Shield which provides a screen curtain. You may have a try for your TP2 at this link:
http://pocketshield.netserver01.com/download.htm
erezshermer said:
Hi,
I'm using an original ROM for TP2 with Manilla 2.1.38158.2 (as shown in Settings | About).
AFAIK this version should include the "in-call curtain" functionality, on which the call buttons are locked during a call. However, I see no sign for this anywhere.
Does anyone have an idea how this feature can be turned on, or how do I add it?
Click to expand...
Click to collapse
I tried installing the InCallCurtain from my Touch Pro ROM and it does not work with the TP2. It is a different dialer so the calls for the curtain may not be in there.
My phone has no problem turning itself off when it gets near my face. Why would you want a call curtain?
Kloc said:
My phone has no problem turning itself off when it gets near my face. Why would you want a call curtain?
Click to expand...
Click to collapse
Did you read the thread ?!
Thanks Angler, I just tested Pocket Shield. I must say I like the progress of this program since the last time I tried it.
I won't use it as a general lock utility because of a severe issue: for some reason my Bluetooth headset loses the ability to answer calls while it's locked. I click the headset button, the ring sound moves to the headset, and the call is not picked up.
I'm thinking about only using its curtain feature - use only the protection during phone calls without locking. This seems to work, however PocketShield locks my device whenever it powers on and I can't find a way to cancel that without completely turning it off. Any ideas here?
(edit: removed double post)
erezshermer said:
BTW, a simple test shows that the proximity sensor is completely useless for this scenario.
Click to expand...
Click to collapse
Prox sensors come in different types. They aren't all configured to turn off "when covered" by just anything. Since the primary purpose is to save screen power when held against your face, it may well be technically designed to detect things that can conduct electricity, like you. If you're curious about it, as I am, next time you test it, cover the prox sensor with your thumb.
If that doesn't work, I recommend on second test. Just because there is a prox sensor doesn't mean that HTC is using only that for turning off the screen. In order to avoid accidentally turning it off while you're trying to use it, which would be annoying, they might be using the accelerometer to detect whether it's being held like a phone or not, and not turning it off if it isn't. Test two is to hold it in a position at an angle as if you would if you were talking on it, and hold your thumb over the prox sensor.
I don't have my TP2 yet, that's why I haven't tried it myself. If you're already on to your current solution and don't want to I understand, but if you do, I'd be curious as to your results.
fortunz said:
Prox sensors come in different types. They aren't all configured to turn off "when covered" by just anything. Since the primary purpose is to save screen power when held against your face, it may well be technically designed to detect things that can conduct electricity, like you. If you're curious about it, as I am, next time you test it, cover the prox sensor with your thumb.
If that doesn't work, I recommend on second test. Just because there is a prox sensor doesn't mean that HTC is using only that for turning off the screen. In order to avoid accidentally turning it off while you're trying to use it, which would be annoying, they might be using the accelerometer to detect whether it's being held like a phone or not, and not turning it off if it isn't. Test two is to hold it in a position at an angle as if you would if you were talking on it, and hold your thumb over the prox sensor.
Click to expand...
Click to collapse
Tested that with some objects and with my hand. Same results. Even with the phone being held vertically like I'm talking with it, the screen won't turn off if it was covered before the call. When removing the hand/object from the proximity sensor and covering it again - the screen turns off immediately.
Maybe this is not a limitation of the sensor but a simple programmed behavior. If so, perhaps it can be patched... <evil grin>
Update. Under HKEY_LOCAL_MACHINE\Software\HTC\Proximity there are 3 keys: ProximityDetectStatus, ProximitySensorOn, UnexpectedWakeup.
The first key is updated live by whatever the sensor detects. I now know for sure that the sensor continously knows if there's something on top - the dialer behavior is programmed.
I'm not sure what the other keys do. ProximitySensorOn was set to 0 on my registry and now when it's 1 I see no difference. Gotta go, will continue with that later.
Switching the Proximity Sensor off...?!
erezshermer said:
Update. Under HKEY_LOCAL_MACHINE\Software\HTC\Proximity there are 3 keys: ProximityDetectStatus, ProximitySensorOn, UnexpectedWakeup.
The first key is updated live by whatever the sensor detects.... I'm not sure what the other keys do. ProximitySensorOn was set to 0 on my registry and now when it's 1 I see no difference.
Click to expand...
Click to collapse
Although I was looking for other reasons -- see below -- I get the same result; & even when you do change ProximitySensorOn to 1, it doesn't survive a soft reset: simply reverting to 0....
What I was looking for was some way of disabling the Proximity Sensor (PS) altogether: because (i) I'm deaf, & I therefore Bluetooth all calls directly to my 'hearing instruments'; & (ii) I've just bought a case which covers the darned thing (meaning the PS) up, permanently locking the touch-screen when it's on! (Aargh.)
Having spent the last couple of hours (plus) searching the TP2 forums on here (& a related one on PPC Geeks...), I've discovered that: (i) lots of people are having PS-related problems; (ii) some of these problems are to do with TouchFLO 3D; (iii) some may be related to various forms of screen-locking; (iv) some may even be caused by other tweaks or hacks we've carried out; & -- last, but not least, as lots of other proud TP2 owners have bought similar cases -- (v) I appear to be the only one having this particular problem (...probably caused by (iv)?)!
It's as if my particular sensor thinks my ear is permanently glued to the screen... -- I can operate all the buttons & the keyboard; but the screen (even though I can turn it on with the power switch) just will not respond while the case is attached (& therefore covering the sensor...).
If anyone has any ideas -- apart from drilling a hole in the case, somewhere (randomly) to the left of the HTC logo... -- please let me know!
Thank you for reading...
- $.
PS: I have a UK-spec., unbranded, GSM Touch Pro2 (...not that this seems to make any difference); & I've already tried turning off any locks & PINs (& changing their duration), as well as the owner information screen....
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
leepriestenator said:
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
Click to expand...
Click to collapse
What is this CAB doing? Because I am also interested in adding support by the Proximity Sensor in TouchLockPro. So how can I start programmatically the proximity sensor? Just changing a registry key
leepriestenator said:
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
Click to expand...
Click to collapse
It works 。Thanks
Hey guys.
I have a desire which has been dropped and the screen in the top left corner cracked. The proximity sensor is damaged, and I can test with various apps that this is indeed broken.
Now, when I get or make a call, the screen turns off, but since the proximity sensor isn't working, it's not turning on again when I move the phone away from my ear. So I wanted to know if anyone knew of a way of either completely disabling the feature, or a way of manually "waking" the screen again, by using any of the hard-buttons?
Thanks
what happens.. when you press power button
Sometimes it comes on, but mostly it doesn't... Regardless of which button I press...
I have read somwhere.. that by blowing some air over that part.. may clear any blocakge.. and proximity sensor works fine.. just try this .. use any vaccume cleaner.. and blow some air over sensor part..
And if that doesnt work.. search for this app in market "'Proximity Screen Off' ".. it might help you.
Yeah, I read that too... Tried blowing with compressed air even. The sensor is dead :/
Try this app.. it will switch your proximity sesor off after call ended.. its not mine just found. you might wanna try this
Dynde87 said:
Hey guys.
I have a desire which has been dropped and the screen in the top left corner cracked. The proximity sensor is damaged, and I can test with various apps that this is indeed broken.
Now, when I get or make a call, the screen turns off, but since the proximity sensor isn't working, it's not turning on again when I move the phone away from my ear. So I wanted to know if anyone knew of a way of either completely disabling the feature, or a way of manually "waking" the screen again, by using any of the hard-buttons?
Thanks
Click to expand...
Click to collapse
Hy, i have got the same problem !
I have a Touch Pro2 Vodafone, but unlocked, and flashed with custom 6.5 ROM and it continually has the problem of the screen going blank and not coming to life.
I have tried Energy Rhodium 29022 and another ROM but both have the problem.
I guess it might be a hardware fault, but not sure really.
Any suggestions for fixing?
task29?
Does it "always" go to the blank screen, or is it intermittent?
Also, when you say going blank and not coming back to life - does this mean when the phone is rebooting? When it's off and being turned on? What are you doing that induces this behavior? Has the phone always done this? Have you tried the stock ROM?
You could also try remapping one of your buttons as a 'Power Management' button using the keyboard configuration to see if your power button is at fault. If all else fails, try flashing the shipped Rom to see if the problem continues. Good Luck!!
Sounds like a failed light sensor. Somewhere there was an app you could install that would display the sensor reading. If it was 0 then you had a bad sensor.
wizardknight said:
Sounds like a failed light sensor. Somewhere there was an app you could install that would display the sensor reading. If it was 0 then you had a bad sensor.
Click to expand...
Click to collapse
I know of such a thing for Android, but does one exist for WinMo?
arrrghhh said:
I know of such a thing for Android, but does one exist for WinMo?
Click to expand...
Click to collapse
I want to say that there was. It wasn't the primary function of the app, but info you could get from it. It has been more than 6mo since I was fooling around with WM on the TP2.
I ran task29 before
Have tried three roms
Problem occurs e.g., today, blank screen, cannot activate, remove battery, try to turn on, get the buzzing sound which means it's turning on but still blank.
Press buttons, oops looks like I'm calling someone.
Phone still blank. Then get incoming call - it wakes up.
This happens regularly, blank and cannot wake up.
Usually charging it wakes it up.
Flash back to stock, if it's still occurring there it's probably a hardware issue. As was stated earlier, the proxy sensor is suspect for sure.
thelawnet said:
I ran task29 before
Have tried three roms
Problem occurs e.g., today, blank screen, cannot activate, remove battery, try to turn on, get the buzzing sound which means it's turning on but still blank.
Press buttons, oops looks like I'm calling someone.
Phone still blank. Then get incoming call - it wakes up.
This happens regularly, blank and cannot wake up.
Usually charging it wakes it up.
Click to expand...
Click to collapse
That really sounds like a bad sensor.
And the advantage to that is, if it is a bad sensor, you could always perform some surgery on your device and install a new screen & digitiser as I did on mine. I had a problem with a slightly rattly earpiece afterwards but I think it was something I did. Handily I was able to purchase a pre-built screen and digitiser as a single unit complete with ribbon cables, I just had to swap it out and reattach the various ribbon cables. Proximity sensor and LDR are all in the one unit above the screen... Which is quite useful as they're all tiny surface mounted components
If you don't want to invest money, and like android I think that FRX07.1 does not use the sensor. That build would let you use the phone as is.
thelawnet said:
Any suggestions for fixing?
Click to expand...
Click to collapse
Any updates there OP? Did you make any advancement? =]
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.
When I make or receive calls the screen turns black and the touchscreen is disabled. I assume this is to avoid accidental keypresses with my ear or something, but my phone doesn't leave this mode until call ends.. I assume it would switch on screen/touch when leveled horizontally, but it doesn't.
I cannot end the call or do anything while the screen is disabled.
The only thing that works sometimes is to double press power button to turn on camera (thus enabling screen/touch), but it is no reliable method.
Sometimes, if I call a person not taking the call, without mailbox or automatic termination of connection, I have to reboot to phone to end this.
Any idea what I can do? Can this supposedly helpful behavior be switched off or fixed?
I am on Android stock 8.1.0 (OPM6.171019.030.H1, Aug 2018), rooted with most recent Magisk.
This bug is driving me nuts, so Thank You for any ideas or help!
Is there anything blocking the proximity sensor (below the right of the speaker)?
nowster said:
Is there anything blocking the proximity sensor (below the right of the speaker)?
Click to expand...
Click to collapse
Not that I know of. All is as normal as can be.
But right now, it seems the "trick" with the camera double click works more reliably (>50%) than before. Whatever reason..
If you've had the phone apart recently ... check proximity sensor. There's a little rubber piece tends to fall out.
Did You applied a screen protector recently? I had the same issue because of screen protector was covering the proximity sensor