Hi
how can i disable the proximity sensor on my HTC Touch Pro 2, windows mobile 6.1 ?
I use a screen lock app that dims the screen during calls but when coming near proximity sensor during call, the screen is turned on again - a real pain.
Please if any onw have an advice to shut it off cpmpletely or when i am on bluetooth i would be really happy for some help
PS i thought paroximitysensor was supposed to disable when tp2 is connected to bluetooth - but its not ??
thanks
Nolan
no one ?
regards nolan
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
thisisallen said:
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
Click to expand...
Click to collapse
Hi
could you test teh cab and tell us here if that can turn of permanemtly the proximity sensor ?
regards Nolan
TurnOffTheLight works to turn off the backlighting but as soon as you move the phone the proximity sensor kicks in again.
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
thisisallen said:
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
Click to expand...
Click to collapse
Hi
light functionality would not solve the problem regarding proximity sensor - its 2 different matters unfortunately
regards Nolan
i have allmost the same problem. my sensor is broken and alwayas is "On". so when i make a call on my hd2 android 2.2 screen goes off and never goes on again. how to kill it???
Called today helpdesk with same problem, cant be turned off , must go for a repair.
Proximity Sensor behavior and solution
I am a late comer to this bb! Hey,I thought all the bugs would be worked out by now! My keyboard did not work right, .... and I have had several other problems with the touchpro2. What are the Chinese doing over there? I had programmed many embedded units and microprocessor systems, but, really, how can they mass produce units like these? Too many cooks in the soup? They are leaving their quality control to the general community.
My problem was I use my gps for bicycling, and if I place it in the support case, the proximity sensor would shut off the screen, even though I was not placing a call. The screen would blank and not come back on. I noticed there was no problem if the physical keyboard was opened and also if the unit were held horizontally. It did this all the time, regardless of the app running.
There are two sensors at the top of the unit: proximity sensor and light sensor. This is a problem with the proximity sensor, at the left.
So I just placed duct tape over it. Now it does not blank.
So I've noticed my AOD isn't turning off at all. While I do have it set to "Show Always", it should still turn off after a short time if the proximity sensor is covered., as was the case with the S7, S8 and S9.
Could you guys please confirm if this is the case for your AOD too? Turning the phone face down or put it in your pocket (or just cover the top half of the display) for a few minutes, see if the AOD turns off. Let me know if anyone sees it turn itself off.
You have to have AOD set to "Show Always" for this test to be valid.
I suspect this could be a bug which Samsung might need to be made aware of, hence my request for others to test. Unless I'm missing something VERY obvious. Or Maybe this is by design?
Thanks :good:
EDIT: thinking about this further, I reckon the proximity sensor is only active while it's flashing, such as when a call is being made. Because it's a "behind the display" type sensor. So maybe they made a trade off with AOD?
It's a sad news for you. S10+ doesn't have a proximity sensor as a trade-off for the screen (sounds ridiculous?). And some features are like sh*t due to the lack of proximity sensor. I don't know if I can go through with this so-called flagship
GialanG said:
It's a sad news for you. S10+ doesn't have a proximity sensor as a trade-off for the screen (sounds ridiculous?). And some features are like sh*t due to the lack of proximity sensor. I don't know if I can go through with this so-called flagship
Click to expand...
Click to collapse
Ummm, of course it has a proximity sensor.....
Try making a call to someone (use voicemail if you want). You'll see a little white flashing dot to the left of the cameras, near the battery icon. This is the proximity sensor: https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
the_scotsman said:
Ummm, of course it has a proximity sensor.....
Try making a call to someone (use voicemail if you want). You'll see a little white flashing dot to the left of the cameras, near the battery icon. This is the proximity sensor: https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
Click to expand...
Click to collapse
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
the_scotsman said:
So I've noticed my AOD isn't turning off at all. While I do have it set to "Show Always", it should still turn off after a short time if the proximity sensor is covered., as was the case with the S7, S8 and S9.
Could you guys please confirm if this is the case for your AOD too? Turning the phone face down or put it in your pocket (or just cover the top half of the display) for a few minutes, see if the AOD turns off. Let me know if anyone sees it turn itself off.
You have to have AOD set to "Show Always" for this test to be valid.
I suspect this could be a bug which Samsung might need to be made aware of, hence my request for others to test. Unless I'm missing something VERY obvious. Or Maybe this is by design?
Thanks :good:
EDIT: thinking about this further, I reckon the proximity sensor is only active while it's flashing, such as when a call is being made. Because it's a "behind the display" type sensor. So maybe they made a trade off with AOD?
Click to expand...
Click to collapse
tried it on a S10E, the AOD always stay on even when in pocket.
Can confirm on my s10+. AOD does not turn off in my pocket or laying face down.
did anyone notice the werid little flashing spot above the the signal bars? that`s the only place where when I put my finger over it the screen goes off during call
GialanG said:
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
Click to expand...
Click to collapse
Seriously, it has both a proximity sensor and light sensor as per normal. They may work slightly different, hence why crappy test apps from the Play store don't work. And why AOD is no longer turning off in pockets.
Watch JerryRigEverything's teardown, specifically here, where he physically points them out: https://youtu.be/kHzmFPoZbCA?t=427
2003vstrom said:
did anyone notice the werid little flashing spot above the the signal bars? that`s the only place where when I put my finger over it the screen goes off during call
Click to expand...
Click to collapse
Read the link I posted in my earlier post. That's the proximity sensor.
the_scotsman said:
Seriously, it has both a proximity sensor and light sensor as per normal. They may work slightly different, hence why crappy test apps from the Play store don't work. And why AOD is no longer turning off in pockets.
Watch JerryRigEverything's teardown, specifically here, where he physically points them out: https://youtu.be/kHzmFPoZbCA?t=427
Read the link I posted in my earlier post. That's the proximity sensor.
Click to expand...
Click to collapse
Not only apps in Store, but the SS diagnostic mode doesn't show either. Check the attached pics of S10+ and Note 5 in SS stock diagnostic mode
the_scotsman said:
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
Click to expand...
Click to collapse
Same here.
Tbh it's not really a trade off I'm happy with because it makes AOD a source of battery drain at this point. I want to be able to put my phone face down to save battery. Do you think this might actually be a bug?
Started a thread in the Samsung community forum. Maybe some of you guys can top up with your own findings.
https://us.community.samsung.com/t5/Galaxy-S10/Always-on-display-not-turning-off/m-p/473981#M2111
Sent from my SM-G975W using XDA Labs
GialanG said:
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
Click to expand...
Click to collapse
Found this article which confirms the existence of a proximity sensor.
https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
The trade-off might be due to the fact that's the sensor is tied to that blinking pixel and is only active while making phone calls.
Sent from my SM-G975W using XDA Labs
Same here, AOD doesn't turn off when flipping it over or covering top portion of the screen.
I'm starting to think this is why they added the feature of AOD only turning on when you tap the screen once as a trade off for it not automatically turning off
mrnovanova said:
Found this article which confirms the existence of a proximity sensor.
https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
The trade-off might be due to the fact that's the sensor is tied to that blinking pixel and is only active while making phone calls.
Sent from my SM-G975W using XDA Labs
Click to expand...
Click to collapse
I tend to agree. I carry my S10+ in my shirt pocket and have noticed that AOD remains on.
Additionally, if double tap to wake the screen is on, the screen will wake on in your pocket without double-tapping it. I have disabled this feature as its annoying that this is also buggy!
pickwit said:
I tend to agree. I carry my S10+ in my shirt pocket and have noticed that AOD remains on.
Additionally, if double tap to wake the screen is on, the screen will wake on in your pocket without double-tapping it. I have disabled this feature as its annoying that this is also buggy!
Click to expand...
Click to collapse
This combined with the lift to wake option interpreting placing in pocket as lifting and the ultrasonic fingerprint reader activating in pockets is giving us of a real annoyance.
I hope Samsung are aware of this and do something about it.. .. ..
---------- Post added at 06:48 PM ---------- Previous post was at 06:23 PM ----------
Very strange... just tried disabling double tap to wake the screen and it didn't stop it happening... Doh
It's a bug, they forgot to link the older aod behaviour with the new implementation of this sensor, I expect it to be fixed in the next update, along with everything else.
I'm constantly getting this too. Even with AOD off and the option to not turn screen on when in pocket(can't remember exactly name) I'm still constantly having my phone turn on in my pocket. At work I get a break every 2.5 hours and sometimes 45 minutes or more of that it'll be on in my pocket. I've pulled it out several times and the emergency call screen be on with a lot of numbers pressed. It's definitely a huge annoyance. My battery almost died during a 10 hour shift because of this.
Sent from my SM-G975U using Tapatalk
Hi everyone. Any thoughts on this issue? This still persists for me even though my phone is up to date and it's may already.
I too think that there's a trade off with the in-screen proximity sensor and the fact that the phone doesn't recognise that's in a pocket. Mine keeps going on while in it.
There must be a way to get around this issue but I'm suspecting we'll never see an optimal fix since the proximity sensor uses that lit pixel to work and nobody would like to see it blinking every second.
I blame bad engineering here. Thumbs down for Samsung mobile.
I blame the new in screen proximity sensor. I doubt they will ever get a fix for their first gen type used on our devices. It'll probably be fixed on the note 11 or S11. I hope not though.
Sent from my SM-G975U using Tapatalk
folks, its a bug in Oneui which existed in all S10 and s10+... its had been reported since day one and still Samsung still unable to solve this issues till date. And they published an notice in Samsung member app, next update will be addressing this issues finally. so lets wait for May updates and see they really solve it.
https://www.sammobile.com/2019/05/13/samsung-galaxy-s10-future-updates-improvements
ramnkc said:
folks, its a bug in Oneui which existed in all S10 and s10+... its had been reported since day one and still Samsung still unable to solve this issues till date. And they published an notice in Samsung member app, next update will be addressing this issues finally. so lets wait for May updates and see they really solve it.
https://www.sammobile.com/2019/05/13/samsung-galaxy-s10-future-updates-improvements
Click to expand...
Click to collapse
Oops accidentally thanked you.
Samsung will never resolve it on the s10, you heard it from here first.
Sent from my SM-G975U using Tapatalk
I've been using Tasker to keep my phone off in my pocket with a combination of 'orientation on right side' and 'proximity sensor' active. Googling a bit, I see some mention about a software upgrade breaking the proximity sensor not long ago.
Anyone know more about it? Sensor seems to work ok when phone is on - maybe it got broken for non-phone things?
(note - turned off double-tap to wake & lift to wake to try to keep phone off when in my pocket)
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
jemfalor said:
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now - actually that won't work, would require the camera to always be on.
Hmm.
polstein said:
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now.
Click to expand...
Click to collapse
tried. had tasker as well and was relying on proximity sensor. gave up
jemfalor said:
tried. had tasker as well and was relying on proximity sensor. gave up
Click to expand...
Click to collapse
I was trying to play with the light sensor with no luck - so I stripped my profile down to just Orientation Right Side = off...and it failed. The screen off works when i manually test it in Tasker, not sure why orientation fails too.
Maybe this is for another thread - what the heck are people that keep the phone in their pockets doing? I've read keep screen away from leg which is a pain for me and the flygrip I use on my phone. Must be a better way!
In searching through the forums I find that many of the other phones have methods of disabling the proximity sensor. However, I do not see a method of disabling the proximity sensor on the Pixel 3a XL. I am using a transparent plastic case to provide waterproofing and prevent loss. Therefore, as soon as a phone call Connects, the screen goes black and all touch screen control is disabled. I have programmed the power key to disconnect phone calls so I no longer leave pocket messages on people's answering machines. I would also like to be able to use speakerphone.
Best and worst phone ever
Seems the proximity sensor is either on or off with no successful way to calibrate it. This phone is a lemon, and nobody supports it.
One of the touch screen issues I sometimes experience is when swipes are "broken" and register as shorter swipes and taps. This makes me think maybe the accidental touch protection, which is supposed to be triggered by the proximity sensor, is being triggered when it shouldn't. We all have read complaints about how the proximity sensor does not work very well.
So on a hunch, last time I had this issue (trying to swipe in gboard), I stuck my finger on the front-facing camera, and interestingly, swiping worked fine (I expected the screen to be disabled - guess that only actually is supposed to happen when you're on a call?).
Since this issue is so random it's hard to really test it. But I've had quite an experience with the proximity sensor.
I wanted the AOD to turn off when the phone is in my pocket, which is the norm on other phones I've used but for some reason Samsung does not do. So I set out figuring out how to do this in Tasker. I got a sensor test app and noticed the proximity sensor basically has two values: 0.0 and 5.0. It is very slow to respond (slower for "uncover" events) and seems to only switch to 0 if my finger is right on the camera. So I set up Tasker to turn the AOD off if the proximity sensor value is < 1, or on if it is >= 1. I also made it vibrate briefly so that I could tell when the sensor was toggling even if I couldn't see the AOD.
At first it worked fairly well. If I manually covered and uncovered the camera, the AOD would dutifully toggle (not instantaneously). But in "real life" practice, it turned out to be quite unreliable. There would be phantom proximity changes while I was using the phone or carrying it -- most interestingly, it often toggles the AOD off briefly when I pick up my phone -- but I didn't really notice any surprise vibrations while the phone was in my pocket. After a couple hours, when my living room got darker (not completely dark), the whole thing went crazy and the AOD would toggle every few seconds with the phone sitting on a table.
So I think the whole "let's ditch a dedicated proximity sensor and use other things to get the same result" is not quite mature yet. And perhaps it is buggy enough to cause one of the issues we think of as a touchscreen one.