Develop Bugs

No in-call curtain in TP2

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

Possible SOD issue...

Hey guys so my Tilt 2 has been having an issue when I put it to sleep. It goes to sleep fine, but when I wake it up the screen remains black. The actual device turns on, but the screen stays black. I can still make calls, receive calls, play music, etc. but I have to soft reset the device if I want to be able to see what I am doing.
From what I can tell my problem is different from the normal Sleep of Death issue where the device simply won't wake up.
I've searched through the forums looking for solutions and have tried pretty much everything from doing a hard reset, using different roms, formatting the internal memory, etc. Even after doing all of this, my device still suffers from this issue.
Any insight into my problem would be greatly appreciated!

I assume you've tried a simple reset using the reset button or pulling the battery out and putting it back in?

Aaron McCarthy said:
I assume you've tried a simple reset using the reset button or pulling the battery out and putting it back in?
Click to expand...
Click to collapse
Yeah every time I the screen goes black I soft reset it in order to get the screen to turn back on. The problem is that the issue persists through soft resets. I currently can't suspend my device because I can't get the screen to turn back on...

hold down the volume down button and then press the reset button (the physical reset button) this should bring you into your bootscreen the multicoloured screen.. if you can get there then you can flash a new rom on your phone... and thats a whole other ball game. It gets a lot of hype as being hard but its really super easy to do if you just follow the directions.

Tilt 2 dark screen solved
With the tilt 2, if the screen does not wakeup, but you can answer the phone, hear music, etc..., it is a malfunctioning light sensor, maybe hardware, or software related (drivers), but it is fixable. Just eliminate all calls for use of the light sensor.
I had this problem and took quite a while to figure it out, as there are several apps that poll the light sensor that cause problems.
First, go to start/settings/system/power/backlight and uncheck the auto adjust backlight option
Second, go to start/settings/personal/buttons/backlight and uncheck the enable keyboard auto backlight sensor.
Last, open advanced config (need to download and install from touchxperience.com, if you do not have it), tab to light sensor and set light sensor polling to disabled.
Now, my phone works normal and will wake up properly from standby like it should. this all seems hardware dependant, as I have in my family 3 of these things and I dropped and broke mine, so bought a new one (4th in the series) and it had the SOD issues, but could restart with softrest. Took me the better part of the day to find a reliable fix, but now all is well again.
Hope this helps other Tilt 2 and similar issues.

[Q] Phone Call Proximity Sensor

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.

Display Graphic problem

I've got a problem with a OneX I'm trialling for work.
This is a stock device with the latest OTA update applied. I installed Good for Enterprise, activated it, and got my work emails. I opened a PDF attachment which opened for a couple of seconds then the display glitched.
The attached images show what I mean. The display is glitched for every screen. Soft resetting the phone was okay until it started again a couple of minutes later.
Soft resetting a 2nd time was where my real problems started. The phone vibrated as it started, but the display stayed dark. If I tap the power, the touch buttons light up. If I go through the motions of the lock ring and my gesture lock, I feel vibrations of my actions but can't see a thing. If I ring the phone, it rings, the touch buttons light up and the LED blinks. The display stays dark at all times.
Does anyone have any idea what's going on here? It's almost like when a graphic card overheats in a PC.

I would try a hard reset, see what that does, it should fix it as it looks like software problem

Squeeze your phone between thumb and forefinger (on the screen and rear cover) about 1.5-2cm in from the USB port, and slightly below. Let us know if the screen comes back on.

ZenithUK said:
I've got a problem with a OneX I'm trialling for work.
Click to expand...
Click to collapse
I think your phone is on drugs.
Seriously though, that's the scariest gfx bug I've seen on a phone.

Work were just as surprised as everyone else.
It's been sent back to them so they can talk with Vodafone about just what's happened with it.
In the few days I had it, it's a decent phone. The primary reason for considering the OneX is the screen size, and the fact you can read a PDF clearly on it.

ZenithUK said:
I've got a problem with a OneX I'm trialling for work.
This is a stock device with the latest OTA update applied. I installed Good for Enterprise, activated it, and got my work emails. I opened a PDF attachment which opened for a couple of seconds then the display glitched.
The attached images show what I mean. The display is glitched for every screen. Soft resetting the phone was okay until it started again a couple of minutes later.
Soft resetting a 2nd time was where my real problems started. The phone vibrated as it started, but the display stayed dark. If I tap the power, the touch buttons light up. If I go through the motions of the lock ring and my gesture lock, I feel vibrations of my actions but can't see a thing. If I ring the phone, it rings, the touch buttons light up and the LED blinks. The display stays dark at all times.
Does anyone have any idea what's going on here? It's almost like when a graphic card overheats in a PC.
Click to expand...
Click to collapse
Mine looks exactly the same once Ive had a few whisky's...

I had the exact same problem, so I shipped off my phone to service.
They actually changed the whole motherboard. I got my phone back 2 days ago, and it is working better than ever. Even better than before they changed the board.
My guess; Same problem as me. Busted motherboard. Im waiting to get a reply from the service guys that fixed my phone, so I can get some solid answers about what was actually wrong.
Hope this helps!
Best regards,
Sebastian

Is anyone facing an issue with the proximity sensor in OnePlus7T

Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.

Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.

vinay3190 said:
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Click to expand...
Click to collapse
It's issue on most OnePlus phones.. I had the issue on 6T, 7 Pro.. annoying

1rahul1996 said:
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
Click to expand...
Click to collapse
This is the biggest reason I may be going Pixel 4...

Yes I too have this issue with my OP7T

Yup, same issue here.
Another thread about it here - https://forums.oneplus.com/threads/proximity-sensor-doesnt-work.1147600/
Also issue present on OP7Pro forums.
Seems to be related to this "Virtual Sensor":
https://www.ellipticlabs.com/2019/0...eaner-design-to-oneplus-7-series-smartphones/
So we have to wait and hope (could be this same as Never Settle? :d) that can be fixed with a software update.

It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it

Josh McGrath said:
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Click to expand...
Click to collapse
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.

trveller72 said:
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
Click to expand...
Click to collapse
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue

Josh McGrath said:
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Click to expand...
Click to collapse
Yeah, I am starting to remember good ol' days with the OPX. Every OTA was fixing one thing and breaking 3 other.
At that time I said no OP again, but still, this one seems to be be a good phone. Time will tell.
Coming back to our issue, I am puzzled that only a few people reported this.

Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.

roofrider said:
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
Click to expand...
Click to collapse
Not rooted, but using a custom dialer as the default Phone app (True Phone).
When I switched the default Phone app to Oneplus App, I could not reproduce the issue.
Testing for a few days to see if this works. Would be such a pity if the app is the problem because I really like it.
Also I just sent a log to OP support (they contacted me after I logged the issue on the feedback).
Yes, it is using the virtual sensor as you said (link in my previous post).

How does the virtual sensor work?
Sent from my [device_name] using XDA-Developers Legacy app

I couldn't find anything concrete on how this software-based proximity sensor, Elliptic Labs INNER BEAUTY, works. The keywords are: ultrasound, sensor fusion, and machine learning. A hardware-software I guess.
The 7T does have an IR sensor under the display, but I think this is only used for DT2W and Tap to Show to prevent the display from accidentally turning on when the phone is in the pocket and so on. Not for calls.

Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability

igotlostintampa said:
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
Click to expand...
Click to collapse
Twrp is out for the 7t. It's not flashable last I checked but it is bootable and usable for what I used it for which was a backup of stock rom