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
Using Desire for months and everything prefect except one thing. Sometimes I need to press the button on the screen after some system message which need to be heard first. When I put the screen on my ear then its off. I can use the headphone sometimes but not always. I believe its because of the sensing function but cant find the place to turn it off. Could anyone who can tell me how to keep screen on when answering the call? Thanks in advance.
The screen goes off due to the proximity sensor, but it should be back on again when you take the phone away from your ear.
This definitely works for me, though I can imagine that if you have your hand close to the proximity sensor it could cause problems.
Regards,
Dave
I tried again and notice that, sometimes the screen can come back but after long time waiting, but in most case it cant. I am not sure the position where the sensor located. I am using the zagg invisible shield screen cover and not sure if that caused the error of the sensor. Anyhow, is here a place to turn this face sensing function off?
PS, after I cleaned the screen cover then it seems get better response time to show the screen after move the phone away from my face. But still not rapidly as normal phone with keyboard and influence the using experience. So if there was a option to turn this face sensing feature off then it could be better.
I found this link where some one who had the same issue found it was related to their Zagg protector, but on the same thread there are others who have had no such problems.
The proximity sensor is in the top left of the screen, within the black border. circles - see here.
Regards,
Dave
Hi;
While on a call, the screen will close. While still talking I press the side button to open the screen and the call will disconnect.
How do I correct this?
Thank you.
Same question. Its just stupid, how on earth I`m supposed to wake up screen without disconnecting a call ?!
Go to: settings>Accessibility>un-check-power button ends call
what's funny is i'm pretty sure that this setting is not selected out of the box, so you guys must have went and enabled it yourselves!
rbs_uk said:
Same question. Its just stupid, how on earth I`m supposed to wake up screen without disconnecting a call ?!
Click to expand...
Click to collapse
I don't know about yours but my SGN seems to have proximity sensor near the speaker and it seems to turn screen on as soon as I take it away from my ear auto-magically It may "lag", but it's fair enough for me...
Mine did the same thing today. I confirmed the accessibility link cited above was not checked. Proximity sensor is irrelevant, I was on a two hour conference call and speaker using speaker phone mode. Screen times out and shuts down on its own, which also shuts off the prox sensor.
is there anyway to lock this phone so when its in your pocket and you're jamming out to some tunes, the screen doesnt turn on or the volume doesnt change? I've had this phone unlock it self and its beyond annoying. Also the screen will be off, phone locked, and if i get an email or text or what ever, the screen comes on every time. It didnt bother me at first but its starting to get to me now.
Tell me about it. My Note 1 pocket dialed 911 recently; I noticed a stern voicemail an hour later telling me if it was a real emergency to dial back. For those who don't know, when you use a PIN lock, an "emergency dial" button shows up, and one swipe and a tap in the right place can dial 911 (the Note 2 / JellyBean helps by not having "911" as a single-tap choice).
Anyway, couple things you can try. The flip screen protector (from Samsung) will prevent inadvertent screen presses while in a pocket. It works very well, though I personally don't really like having to flip open a cover on top of a phone this size.
It might be possible to use another SMS app like Handcent that won't turn the screen on when you get a text, but I haven't verified that. I haven't figured out how to prevent the screen from lighting up when a text comes in using the stock app, but the flip cover would prevent any screen taps from happening when it does.
I tried a proximity lock (turns screen off when prox sensor is activated), which worked, but there is some odd behavior. When you get a text and the screen kicks on, the proximity sensor app doesn't know you want the phone to go back to sleep, so I think it prevents deep sleep after that (battery drain?). And it also interferes with the phone's ability to use the proximity sensor during phone calls, so after the first phone call and subsequent proximity lock, it no longer works at all during calls until the service is restarted. You might experiment with these though. There's one called "ProximityService 2.1" (Google it since it was released in a Droid forum IIRC) and others are available in the market.
No software tips on the volume buttons, but if you get a TPU style case the cutouts will make them less likely to get pressed. I wish they were recessed just a little more or harder to press. I don't like the TPU cases because they add bulk to the phone.
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