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, everytime I am in a call, my ear taps the taskbar and it opens the notification window which covers my call screen. I have googled and searched this forum with no success.
Apart from TouchLockPro, was just curious as to if there is anything that addresses this issue?
Thanks in advance.
Do you have something (case?) blocking the proximity sensor? The screen should be turning off as soon as you put the phone to your ear.
Yes I do. I've just tested it out, that seems to be the problem. So is there any tweak to prevent this?
i know even with the screen turning off with the proxy censor i will find i am in the screen with the connections and battery info when i am done with a call... its kind of annoying and worrys me a bit i might accadently end the call when the screen is off.... also the flip over to make it a confrence phone is a 50/50 thing... this device is so glitchy
I randomly get this too, I think sometimes the sensor isn't used.. There are times I've noticed I can cover it up completely with my thumb and the screen doesn't go off, but other times it works just fine.
Ryryq said:
Yes I do. I've just tested it out, that seems to be the problem. So is there any tweak to prevent this?
Click to expand...
Click to collapse
Tweak...some testing to see where the sensor is (somewhere along the top near the HTC logo) and an X-acto knife to the case?
same thing happens to me, most of the time somehow I turn on airplane mode and the call disconnects.. sigh
TouchLockPro has a feature which turns the screen off using the G-sensor, but it's not just for calls, if you have it horizontal it'll be on, and if vertical it suspends/screen turns off; this would be good if it was just for calls, especially for those that use a case.
I'm just starting to use TouchLockPro (http://forum.xda-developers.com/showthread.php?t=444215) and I have most of the locking features turned off - I just hit the power button if I want to lock it.
It does keep the screen locked during a call so I no longer hit the buttons. Plus - when it unlocks I'm right back, exactly, where I left off.
There's lots of options to tweak, I think there's something for just about everyone.
I LOVE unlocking with the zoom bar - first time I've used that thing on my phone
~Eric
eknutson said:
I'm just starting to use TouchLockPro (http://forum.xda-developers.com/showthread.php?t=444215) and I have most of the locking features turned off - I just hit the power button if I want to lock it.
It does keep the screen locked during a call so I no longer hit the buttons. Plus - when it unlocks I'm right back, exactly, where I left off.
There's lots of options to tweak, I think there's something for just about everyone.
I LOVE unlocking with the zoom bar - first time I've used that thing on my phone
~Eric
Click to expand...
Click to collapse
Awesome. Mind sharing what settings you have enabled, please?
Sure
Light Sensor, Stylus Sensor, GSensor, Nav Sensor, :
Nothing checked (all disabled)
Keyboard:
Use Slider, Suspend On Slider In, Slider Out Disables LockMode and EnableInputAtSuspend are all checked, everything else is un-checked (HTC Lock API, Double TouchPanel Lock and KeepAliveAlways are un-checked.
BattClock:
just some preferences set for appearance
Telephone API:
Everything is checked (except light)
Software:
Nothing set up
Other Settings:
AutolockOnPowerOn and UnlockOnACPower are checked, everything else is un-checked (added vibrates Lock/Unlock once - I like the extra notification)
~Eric
thanks! works like a charm now, is there any way to lock it if it is idle for like 30 secs or something without havin to hit the power button
There's a number of ways to lock it using the various sensors - you can try one of those and see what fits your habits / style best. You can also click on the BattClock icon to get the menu - the lock icon is right there. That's 2 steps though...
~Eric
my phone locks up every time i dial a phone number. the screen gets locked up (black screen) and even if i press the home button or the sleep button, it won't come back on. the only way it would comeback on is if the other person hangs up the phone. for example, i call 611, now as soon as i dial that number, the screen goes BLACK. nothing shows up on screen. only choice i have is to WAIT for the other person to hang up for my screen to light back on again. i can't hang up because the screen won't come back on until the other person hangs up. if i press power button, nothing happens. something if i press the home button. what is wrong with this phone?
btw, it is running lean rom. i previously had another rom (samething happened on it tahts why i'm on lean rom, and same issue).
i'm currently downloading the stock tmobile rom, lets see if this issue is resolved. if any of you have faced this issue please comment. thanks.
also, when flashing the roms, i always follow the correct procedure (recovery > wipe data > wipe cache > wipe delvic > install from zip. )
JoJo2211 said:
my phone locks up every time i dial a phone number. the screen gets locked up (black screen) and even if i press the home button or the sleep button, it won't come back on. the only way it would comeback on is if the other person hangs up the phone. for example, i call 611, now as soon as i dial that number, the screen goes BLACK. nothing shows up on screen. only choice i have is to WAIT for the other person to hang up for my screen to light back on again. i can't hang up because the screen won't come back on until the other person hangs up. if i press power button, nothing happens. something if i press the home button. what is wrong with this phone?
btw, it is running lean rom. i previously had another rom (samething happened on it tahts why i'm on lean rom, and same issue).
i'm currently downloading the stock tmobile rom, lets see if this issue is resolved. if any of you have faced this issue please comment. thanks.
also, when flashing the roms, i always follow the correct procedure (recovery > wipe data > wipe cache > wipe delvic > install from zip. )
Click to expand...
Click to collapse
I'm having the exact same issue, when I make a call the screen guess into sleep that can't be awaken unless whoever I was talking to hangs up. the only exception is when I'm in speaker mode but I would have to be quick before the screen guess black. I'm running ogwisdom's paranoid android and I flashed from stock Rom. any help would be greatly appreciated.
Sounds like your guys' proximity sensor isnt functioning properly.... it controls the screen dimming during calls by detecting our face. If it's not detecting your face properly, then when it thinks you have put the phone down (always) it will dim the screen and keep it that way until the call is completed like you described...
This happens often to some of us who have screen protector covering the sensor.
If the sensor is actually broken obviously you will have to replace it, but more likely its just being blocked by your screen protector or fingerprints?
You can just disable the proximity sensor like many people do. It's really not necessary anyway imo..
To diable it go to the "phone app" where your dialer is just bring up the menu, go to settings and uncheck the box that says "detect your face during calls and dim screen". Then you can just use your power button to bring the screen on and off during calls. Proximity sensor kinda worthless anyway...as far as I know.
Anyone know what use the sensor has other than screen dimming during calls? Theoretically I think it controls dimming at all times, but by default the dim kicks in after what 30 seconds(?) and who looks at their phone for 30 seconds without touching the screen unless a movie is playing (in which case auto dim is disabled!). So thats why I kinda think the sensor is useless...unless its doing something I dont know.
---------- Post added at 02:02 PM ---------- Previous post was at 01:49 PM ----------
Sounds like your guys' proximity sensor isnt functioning properly.... it controls the screen dimming during calls by detecting our face. If it's not detecting your face, when it thinks you have put the phone down it will dim the screen and keep it that way until the calls completed like you described...
This happens often to people who have screen protector covering the sensor.
You can replace the sensor if its broken cheaply,
You can remove whatever item is blocking the sensor if its being block
Or you can just disable the sensor like many people do. It's really not necessary.
In the "phone app" where your dialer is just bring up the menu, go to settings and uncheck the box that says "detect your face during calls and dim screen". Then you can just use your power button to bring the screen on and off during calls. Proximity sensor kinda worthless anyway...as far as I know. Hope that helps..
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.
I have a brand new A3(2017) with a genuine Samsung Neon flip cover. I'd expected the phone to switch on/off when I open/close the cover. However, when I open the cover it starts displaying the time instead of the lock screen, and when I close the cover it doesn't switch off (as can be seen by the glowing edges).
Did I overlook an additional setting?
After some fiddling with the settings it suddenly works as expected. Unfortunately I have no idea which setting did it ... .
sciurius said:
After some fiddling with the settings it suddenly works as expected. Unfortunately I have no idea which setting did it ... .
Click to expand...
Click to collapse
To work properly you will need to turn on both NFC and Android Beam.
Interesting... I have NFC disabled (don't know about Android Beam??) but closing the cover still works.
I had this issue and fixed like that :
- disable NFC
- turn off the phone
- remove the cover
- turn on the phone + PIN
- insert the cover
- enable NFC
the cover should work again now, you can disable the NFC if you want
I noticed the cover stops working after I answered a phone call.
To fix:
- open cover
- reboot
- close cover
A bit annoying...
Solution found!
Hi. I have found a solution to this issue.
I have a brand new A3 2017. One day after I purchased it I upgraded it to Android 7 Nougat. After this update the neon flip cover didnt6work anymore. NFC and other settings didn't change anything.
I finally managed to solve the issue in NFC/NFC and paying settings. I cancelled the default option "automatically detect NFC setting" to something like "use normal Android settings.
Then I disabled NFC and my cover works like under Android 6.
Hope this helps.
Benjamin
I'm still stuck.
Sometimes it works, sometimes it doesn't. The funny thing is that it seems the cover is detected. The 2 buttons on the bottom light up when I open the neon cover. However, the screen is not switched off nor on.
I tried playing with the NFC settings and read on another forum that you need to install the flipcase when the device is on but not screen locked. Only little success from time to time. This seems not very properly programmed
berkely said:
I'm still stuck.
Sometimes it works, sometimes it doesn't. The funny thing is that it seems the cover is detected. The 2 buttons on the bottom light up when I open the neon cover. However, the screen is not switched off nor on.
I tried playing with the NFC settings and read on another forum that you need to install the flipcase when the device is on but not screen locked. Only little success from time to time. This seems not very properly programmed
Click to expand...
Click to collapse
I'm having the exact same problem, my cover was working for over two months and suddenly it's not. The two buttons on the bottom also light up and off when I open and close the case, but the screen is not responsive.
A3(2017) Neon flip (Illuminated Edge Notifications) turning off?
I'm looking to turn it off, I'm trying to take photo's with the cover closed, but the neon flip cover closes my whole phone, and I don't want that, I only wanted a random phone cover my parents got me.