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
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
Hi guys,
When I'm calling with my Desire HD there is pause button on screen and I accidentally touch the button which causes breaks in calls. Is there any way to change the default phoning app? I've tried GO Contacts, but it changes only managing contacts app. I'm using Cyanogen Mod 7 if this is revelant.
Hmm it seems you have a problem with your proximity sensor... Is the screen turning off when you talk on the phone?
The normal behaviour is that the screen turns off (from the proximity sensor action) when you put your phone next to your ear.
If that's the case, you can either try using Proximity sensor calibrate http://forum.xda-developers.com/showthread.php?t=951858 or contact your dealer for a repair.
You can also switch off the screen with the power button after starting a call, this should lock your screen as well.
Lastly, if you really hate your current screen and you feel adventurous, you can try flashing an AOSP Rom like MIUI (but that's a long story xD)
Hope that might help.
Hi,
as measured by Z-DeviceTest, the proximity sensor on my Desire is stuck at 0.000 cm in all lighting conditions (including a very bright torch right on top of it).
At first I suspected this was the known problem with dust settling on the sensor, but I've blown and sucked (teh-eh) with everything I have, from every angle, and the sensor is still stuck at that value.
The problem shows up both in CM7 and with the stock firmware.
I have to assume the sensor is broken.
I'm looking for ways to disable the proximity sensor, and in particular to stop it from locking the screen during calls. Naturally, since the sensor is stuck at 0.0000 cm, any time a call is initiated the screen locks up, preventing me from ending the call, dialing tones and so on.
Alternatively, I'd be happy with a way to override the screen lock via hardware buttons. The power\unlock button doesn't work
Inserting a headset during a call does unlock the screen, but naturally this is not a satisfying solution (for example, I can't use this method to make calls while driving, using the speaker).
Solutions tried with no positive effect:
- editing build.prop with "ro.proximity.delay=0"
- using trackball\volume button wake
- using screebl, screen off to control automatic screen locks
Thank you for your time.
Anyone have any pointers?
Is it really hopeless?
Are you root? If so have you considered flashing a rom with the option to disable the proximity sensor? (for example miui-au has that option)
Yes, I have a rooted device. I didn't know miui had that options, I'll check it out; thank you!
So recently my phone's screen had just been going black while I was receiving, making and mid phone calls. Including Skype Calls. So my search around the web came to the conclusion that it was the proximity sensor that caused this.
I'm rooted, running CM 12 and had been for 3 months until this issue arrived so I don't think it's from the ROM or the fact i'm rooted but if i'm to run a diagnostic on the sensor it always produces, "near"
i.imgur(dot)com/aFXCHUt.png
I can't post images or links yet ;-; so you'll just have to edit that screenshot a little bit to view it.
so I have evidence to believe that it's 100% busted and I don't really feel safe with unscrewing the back of my phone to try and fix it, is there any way that I can just disable it? I have Hardware Disabler but I don't know the driver name. Also I cannot install Xposed also for this reason:
i.imgur(dot)com/oy61YCY.png
Just wanting to bump this.
I have exactly the same problem with my G3, and unfortunatly have not found a solution yet.
With roms based on the original G3 rom I can somehow answer a call, and then the screen goes black, but after that I cannot end the call. With roms like PA or CM I can't answer a call (the screen goes black as soon as it rings), but I can end the call with the power button when I call someone myself. In the beginning the proximity sensor sometimes did show a distance other than 0, but now it's just stuck to 0. I'm fairly certain the actual sensor is just broken, and I hope there is just a simple mod or something to disable it completely, or a way to anwser calls with the volume or power button.
I have also tried the Hardware DIsabler app, and googled all the drivers it showed, but I couldn't find the proximity sensor.
FC_ said:
I have exactly the same problem with my G3, and unfortunatly have not found a solution yet.
With roms based on the original G3 rom I can somehow answer a call, and then the screen goes black, but after that I cannot end the call. With roms like PA or CM I can't answer a call (the screen goes black as soon as it rings), but I can end the call with the power button when I call someone myself. In the beginning the proximity sensor sometimes did show a distance other than 0, but now it's just stuck to 0. I'm fairly certain the actual sensor is just broken, and I hope there is just a simple mod or something to disable it completely, or a way to anwser calls with the volume or power button.
I have also tried the Hardware DIsabler app, and googled all the drivers it showed, but I couldn't find the proximity sensor.
Click to expand...
Click to collapse
Yup. I'd really enjoy a solution, it's just a constant issue for me.
Glad to hear I'm not the only one though haha!
Is it possible to enter this device test?
http://forum.cyanogenmod.com/topic/81988-black-screen-during-call-jfltexx/
Code 3845#*855# doesn't work
i have the exact same problem on my d851 and i dont think its software because everything was fine on cloudy then it started i tried changing the rom but its the same .....i have remarked some thing that the proximity sensor working sometimes when the phone is warm and doesnt work when its cool ....i also need a solution but i cant use xposed module because i am on MM..and i dont want to install supersu etc
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