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
Has anyone noticed their phone likes to turn itself on during phone calls as the phone touches your head?
I thought that could be fixed with Advanced Configuration Tool and these options:
◦Phone sleep during call
◦Fast sleep during call
But they both are gone. They were there on my Kaiser. Any ideas?
It's supposed to turn off due to the proximity sensor. I'm using a T-Mobile USA TP2 and it turns off as it touches my ear. One way you can test this, if you haven't already, is to call a phone, then as it is in progress, lay the phone with the screen up, and put your finger across the top of the facade of the phone (cover the top area where the earpiece is). When I do that, in order to replicate my ear towards the phone, the proximity sensor blanks the screen.
As for the AC tool settings you mentioned, I've never touched those, so mine are on the default settings.
Hey, wow! You're right! When the device is against my ear, the display is out. As soon as I pull it away, even slightly, it turns it on!
I'm simple, I know. My wife tells me that all the time.
motocrossmann said:
Hey, wow! You're right! When the device is against my ear, the display is out. As soon as I pull it away, even slightly, it turns it on!
I'm simple, I know. My wife tells me that all the time.
Click to expand...
Click to collapse
It's okay, when I first got my TP2, I encountered the same thing you thought was a problem. Then I saw a video online demonstrating proximity sensors and the guy on the video put his finger along the top/speaker area of the device and the screen turned off. I replicated his actions on my TP2 and realized that the proximity sensor activates when something is touching it or gets fairly close to it. BTW, we're all simple; we just excel in different ways!
LOL, me and the wife learning this stuff too. Hey, heres another (which i just created a post for), GO rub a magnet on the face of the phone while the screen is OFF, right over the tiny keypad. If you have a soft case with magnet in the flat, go see the funky result
carhigh said:
LOL, me and the wife learning this stuff too. Hey, heres another (which i just created a post for), GO rub a magnet on the face of the phone while the screen is OFF, right over the tiny keypad. If you have a soft case with magnet in the flat, go see the funky result
Click to expand...
Click to collapse
Well since I'm already here and I don't want to search for that post (sorry to the Mods since this is irrelevant for this thread), I can answer that too. It's already a well-known issue. The magnet tricks the phone into thinking either the keyboard and/or the stylus is being opened/taken out. However, it is more accepted that the phone is being tricked into the keyboard being opened. There's a registry edit posted on these forums that can fix that, but the downside is if you want the screen to turn on when the keyboard opens, it will no longer turn on without having to press the screen wake-up button.
I'm just using the Slide2Unlock v.204 for WVGA devices. It keeps the phone locked even if the screen turns on. When I slide my phone into my magnet-clasped holster, it sometimes turns on. It's just a habit for me now to check the screen once it's in the holster, so I can turn the screen off if it woke up by itself.
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
I just bought a refurbished Tab S and it looks like it hasn't even been used. It came with Android 5 and I didn't notice the problem, although I only used it for a few minutes before doing the OTA update to Android 6.0.1. Although everything seems to be working, if I grip the tablet between the lower right corner and the usb charging port, the screen blanks. Then when I remove my grip from this location the screen comes back on! I know ... weird behavior, right? It only happens in this area and it doesn't happen if I just press on the back or on the screen in this area. I have to actually grip on both sides. It's a beautiful tablet and I would hate to have to return it, so I'm trying to figure out if there is a way to fix it. (In everyday use it is just to annoying to aviod touching this area.) I read a post by vndnguyen (14-Jul-2015) on this forum that said:
---------------------------------
Our Galaxy Tab S has a Grip Sensor. You can check it by:
1) Use *#0*# to open Hardware Test, select GripSensor. You will see the grip sensor is located at the upper-right corner.
2) Use *#1106#. You can set the Grip sensor on/off.
-----------------------------------
So maybe I could fix the problem by turning the Grip sensor off. However I couldn't figure out how to enter these secret codes since a wifi only tablet doesn't have a dialer. I found an application called "Secret Codes" with an icon that looks like a lighted match. It listed a code with a #0 for hardware test. I pushed that button and it said it was invoking the code but then I saw no response from that.
Would selecting "Factory Data Reset" from the Backup and reset settings menu be worth a try to fix this problem? (Would I have to do the Marshmallow update again?).
By the way, here are some additional things I did to see if I could make the problem go away (to no avail):
- Starting the tablet in Safe mode
- Turning off automatic brightness, screen rotation, smart stay, screen timeout, Adaptive display, and screen tone auto adjust
- Turning off lock screen
- Turning off Palm swipe to capture
Any advice would be highly appreciated.
~Paul
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.