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
Since earlier today I started experiencing problems on my HTC Desire with the proximity sensor. For those that does not know, the proximity sensor switches the screen off when you receive or make a call and places the phone against your ear. When the call is completed and you remove the phone from your ear, the screen become active again.
In my case the moment I make or receive a call, the screen gets disabled. I do not even have to put the phone against my ear. It also means that the touchscreen is disabled and all buttons are disabled which means I cannot end the call, switch on the speaker or enable the keypad. None of the buttons, even the power one works. When the call gets ended by the other party the the screen will be enabled again. The only way to get a working phone again when there is nobody on the other side to end the call is to remove the battery.
What I also find weird is where the sensor should be, top left next to the HTC logo, is nothing. Does not matter how I look at it, there is just the black strip.
I have searched to see if there is some app that can disable the proximity sensor since I do not really need it but have found nothing. So if anybody knows of an app that can disable the proximity sensor then I would appreciate the link. If you have any other suggestions, please comment below.
Can't you enable your screen by the power button?
No i can`t
Vous.Thal said:
Can't you enable your screen by the power button?
Click to expand...
Click to collapse
I just installed CM7on my phone and the power button works.
My first suggestion would have been to test if and how the proximity sensor works, for example with this app:
play. google.com/store/apps/details?id=com.tigermonster.proxfinder
Otherwise, for just disabling the sensor there should be another app (which however requires root):
play. google.com/store/apps/details?id=com.hatcyl.android.Hardware_Disabler
(you have to remove the space in the link because as a new user I'm not allowed to post links... they don't like new users here, right?)
A bad kernel flash can cause it... flash another kernel according to the android version and rom you are using.. If cm7 and android 2.3.7 then snq- 's kernel would be nice .. if on ICS then I recommend tiamat's kernel..
http://forum.xda-developers.com/showpost.php?p=25782354&postcount=3
Is there any way to calibrate the light sensor? It works when under direct light from a strong lightsource.
Sometimes when im getting calls, it just get stuck, and keep locking the screen.
And it never works other then under a lamp, for example.
If its not possible, can i turn it off permanently?
you are confusing Ambient light sensor with proximity sensor. (they are both built into the same unit)
They are both located approximately 1cm left of the htc-logo-right-under-the-earpiece
Ambient light sensor is responsible for autobrightness.
Proximity sensor is responsible for checking if anything is close to the earpiece(your ears during calls)
proximity sensor turns on an extremely dull-red light(infra-red) which may not be visible to some people (you can see it clearly through another phone camera)
About your first problem you can simply look in the market for an Autobrightness app and turn off system autobrightness(you can choose what brightness at what sensor reading)
About your second problem it seems its a bug, probably in most cases i've seen in this forum caused by Viber app (or any other data-calling apps), either try uninstalling those apps or choose in their settings not to control normal phone calls and proximity sensor.
Give feedback if it works
O and yeah, this have been "working" with venomrom, simply pressing power button, to turn screen on, mostly,
But now when i installed CM10, I simply cant turn screen on, by pressing the power button, so i have to turn off the device.
There are 2 different sensors that you're talking about. Ambient light sensor and proximity sensor. The proximity sensor turns off the screen completely when you're in a call and it senses your head up against the phone. The ambient light sensor will only chance the screen brightness. You can tweak values for the screen brightness but not that I'm aware for the proximity sensor (turning the screen off completely).
---------- Post added at 03:08 AM ---------- Previous post was at 03:06 AM ----------
That "screen of death" problem is only with the latest builds of CM10 as far as i know. If you go back to a beta / sense ROM you should stop getting these. Nightlies will always have these kind of bugs.
Alright, what im meant is the Proximity sensor. This happend after my phone got a new screen from repairment. (Dont wanna sent it back, way to slow)
When i start a phonecall, the screen goes off, and during that call i cant get the screen back on. Have to longpress the power button, to reboot the device
And now the device is completely fresh installed with CM10
I had the same problem after a repair. Thought it was just a bad install but the problem was persistent. Even on other Roms. It was a hw problem. Hopefully for you its not that.
Sent from my HTC One X using xda app-developers app
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 guys,
Reading around this seems to be a rather common issue among lg g2, lg g3 and lg g4 users.
the first one regards the light sensor. In relatively light environments, the light sensor value is too low, leading to the screen turning off soon after hitting the power botton and disabling the double tap. The same thing happens when you cover the sensor with the finger and is meant to be active while in our pockets, which is great, but the problem itself is very annyoing.
Initially I thought this was due to a software problem, but after performing a kdz reset on KK (from lollipop) I can assume that it has nothing to do with the OS.
The problem seems to diseappear soon after the reboot, but reappearing shortly after and it appeared later in the life of the phone, it worked fine for a long time.
But the first issue to appear to is the proximity sensor issue. Most of the time it is set to "near" even though there is nothing covering it. I opened the phone, cleaned it, hard resetted but still nothing. no solution seems to be effective. Of course this is very annoying during phonecalls and this is also disabling the double tap feature.
In a normal room situation during the evening with the light turned on and my body projecting a shadow over the phone, proximity: "near" and lightsensor: "2"
The combination of these 2 problems is making my experience with the G3 very unpleasant.
I don't who builds sensors for LG but they are not doing a great job!
So if you have the same problem you are not alone!
some tricks that I "learned" in order to overcome these problems are.
1) Light sensor:
- point the device towards a light source to unlock the device
- repeatedly press volume up after pressing power button to prevent screen turning off
2) proximity sensor
- reboot the phone before a phonecall
- running a device test through 3845#*855# (international version of the phone)
- using bluetooth systems during calls
- using headphones
If somebody has additional suggestions to provide me and the others please share.
Thanks!