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

Light Sensor request for HTC Blackstone / Touch HD

I am looking for a light sensor solution like on the IPhone. If u get a call and you put the phone at your ear, the phone screen gets dark, thats normal,
but what is, if I want to turn on speaker or something during a call? I allways have to press the ON/OFF button.
At the Iphone, they got a better solution for that.
Can anayone manage a little plugin cab or does anyone know a registry solution?

you need Touch_InCall_Screen_Tweak, It can do what you want but it is not using the light sensor.
It uses the G-Sensor, when the device is not in vertical position (closed to your ear), phone will wake up automatically and sleeps again when you take it close to your ear to speak (vertical position).

thank u for your reply, but I want a light sensor app.

Am not sure
but there isnt a light sensor in the blackstone to start with

eI am looking for a light sensor solution like on the IPhone. If u get a call and you put the phone at your ear, the phone screen gets dark, thats normal,
but what is, if I want to turn on speaker or something during a call? I allways have to press the ON/OFF button.
At the Iphone, they got a better solution for that.
Can anayone manage a little plugin cab or does anyone know a registry solution?
Click to expand...
Click to collapse
+1 for that
Am not sure
but there isnt a light sensor in the blackstone to start with
Click to expand...
Click to collapse
i think you'r wrong m8 ... From what i know there is a light sensor in blackstone

the blackstone has a light sensor next to the ear speaker. It is oossibble to turn it on. but wehen you remove it from your ear, the light does not turn back on

Search for "PocketShield", this program has the requested feature, and much more.

yes, 3.0 is very cool
bouwew said:
Search for "PocketShield", this program has the requested feature, and much more.
Click to expand...
Click to collapse

Pocket Shield is not freeware and is definetly not what I want.
I just look for a solution auto-lock un-lock when you remove or taken to the ear.
Microsoft developers will read this thread and bring it into new builds.

Ok, try this one. It seems to be available for free or at least the minimum version ,the full version is around the 7 $. You can measure the Brightness at your workplace, in rooms, use it for Photography or to set up aquariums and terrariums. Works fine although I use it just like for fun maybe is useful for your work.
http://www.pocketpc-software-downlo...-for-htc-touch-diamond-download-ygwklytx.html
The software is called Kai's Luxmeter pro 1.2

Rocheau said:
Ok, try this one. It seems to be available for free or at least the minimum version ,the full version is around the 7 $. You can measure the Brightness at your workplace, in rooms, use it for Photography or to set up aquariums and terrariums. Works fine although I use it just like for fun maybe is useful for your work.
http://www.pocketpc-software-downlo...-for-htc-touch-diamond-download-ygwklytx.html
The software is called Kai's Luxmeter pro 1.2
Click to expand...
Click to collapse
I dont want a Luxmeter, if I want a Luxmeter than I take mToolbox.
I tried Pocket Shield and after uninstalling this program, the light sensor does not work anymore.

Try TICST
really, just try it.
http://forum.xda-developers.com/showthread.php?t=488991
This is what you want to adequately switch the screen off as it comes to your ear and then on again as it comes away from your ear.
I've been using it on a an HD since March/April and it works flawlessly. It even has intelligent options to handle bluetooth calls and control of the speakerphone.

hmmm sounds good but what happens if you get a call at night and there's no light?
Need a combination of light sensor and g-sensor I think.

Yes it has it - please just try it before finding problems with it. It will work for you!!!

NeoXTC said:
hmmm sounds good but what happens if you get a call at night and there's no light?
Need a combination of light sensor and g-sensor I think.
Click to expand...
Click to collapse
Yes this is one of the biggest problems with lightsensor...
Tested the detection range with mToolbox and Lumos - and it shows "0" very early even if there's a bit light around - so the light sensor in-call-detection wont work very good.
How is it solved at iPhone?
BTW:
[APP]Touch InCall Screen Tweak v1.2.0 - Updated 3 Sep 09 - Battery Drain Fix
So it doesn't use the light sensor then?
From v1.0.6 it DOES use the light sense to detect if it is against your ear. This is really a double check to back up the orientation. It doesn't use it to determine if it's away from your ear because the sensor doesn't seem to work when the screen is off, so it's of no use for switching the screen back on.
so - what else you want?

The iPhone doesn't use the light sensor to toggle screen, it uses proximity sensor - it turns off the screen when something approaches the area near the speaker and turns it back on when there's nothing near it.
Light sensor can't work reliably because you can get a call in a dark room.
TICST is a workaround using both the light sensor and the g-sensor, it's rather good but not perfect.
A perfect solution requires hardware that's missing in Touch HD. HTC HD2 will have the proximity sensor so screen toggling will be working there, hopefully.

Proximity Sensor

Hey i don't know if this deserves its own thread or not, but i think it'd be pretty cool if the proximity sensor on the Touch Pro 2 could be used like those on blackberries, that when you put the phone in your pocket or a case with the screen on the screen would automatically turn off then turn back on when you took it out. Don't know if this would be possible but it is a really cool concept. Thanks

blackberries turn on cause theres a little magnet in the cases that turn on and off the screen. i dont think any blackberries have a proximity sensor. the storm is the only one with a touch screen to accidentally hit but you have to click it to do anything, and if your pushing a bb hard enough into your face to make the screen click, you deserve the have it push random buttons.

oh ok, that kinda sucks, still be kinda cool if it could be done though

i was wondering if theres some way to change the sensitivity or distance of the proximity sensor, i notice when my wife was using the phone the screen would turn on and off randomly i guess because of the way she was holding it to her ear, then i started noticing through the corner of my eye that my phone was doing this as well, it must think i've pulled it away from my ear when it senses different cavities in my ear, i'd like to turn it up to an extra 1/2" or so when i do hold the phone to my ear i know for certain it stays off, and when i really do pull it away from my head the screen wakes up. has anyone found the settings for this yet? i'm running juicy rom and my wife has mightyrom

TheLetterMan said:
Hey i don't know if this deserves its own thread or not, but i think it'd be pretty cool if the proximity sensor on the Touch Pro 2 could be used like those on blackberries, that when you put the phone in your pocket or a case with the screen on the screen would automatically turn off then turn back on when you took it out. Don't know if this would be possible but it is a really cool concept. Thanks
Click to expand...
Click to collapse
you could have it that way but you would need to disable the power off after x minutes. then all you would need to do is keep the proximity sensor enabled

Changescreen has an option under the advanced settings to suspend the phone when it's placed face down or in your pocket (as long as its put in your pocket upside down). It doesn't turn back on when you pick it up or take it out of your pocket though, you have to hit the suspend button for that. I'd reccomend checking it out.
Oh ya it also does screen rotation via the G-sensor.

trevoroni said:
Changescreen has an option under the advanced settings to suspend the phone when it's placed face down or in your pocket (as long as its put in your pocket upside down). It doesn't turn back on when you pick it up or take it out of your pocket though, you have to hit the suspend button for that. I'd reccomend checking it out.
Oh ya it also does screen rotation via the G-sensor.
Click to expand...
Click to collapse
I'm not sure if Changescreen actually uses the proximity sensor. It will shut off the screen even if you turn it upside down in the air. And I have found on numerous occasions that it still leaves the screen on in your pocket, which is too bad because it's handy to have.

Try PocketShield. It will automatically shut the screen off when put in your pocket or case. There is a free and paid version.

t0mmyr said:
i was wondering if theres some way to change the sensitivity or distance of the proximity sensor, i notice when my wife was using the phone the screen would turn on and off randomly i guess because of the way she was holding it to her ear, then i started noticing through the corner of my eye that my phone was doing this as well, it must think i've pulled it away from my ear when it senses different cavities in my ear, i'd like to turn it up to an extra 1/2" or so when i do hold the phone to my ear i know for certain it stays off, and when i really do pull it away from my head the screen wakes up. has anyone found the settings for this yet? i'm running juicy rom and my wife has mightyrom
Click to expand...
Click to collapse
I'm with t0mmyr on this issue.
I too find that when having been on a call, my screen can end up with started apps, on the programs page, etc.
I too think that a 'tweak' on the proximity sensor will go a long way to fixing this issue. The trick is to find exactly what to tweak and this is where we need a little guru-like guidence.......!!!
Cheers
Jabberoo

theres a few interesting keys in hklm\software\htc\proximity. i wont mess with them. i wouldnt like the screen to turn on every time i pick my phone off a table or something.

The Jack of Clubs said:
theres a few interesting keys in hklm\software\htc\proximity. i wont mess with them. i wouldnt like the screen to turn on every time i pick my phone off a table or something.
Click to expand...
Click to collapse
Thx for the heads-up
I looked into them but with no result.
There must surely be a way to 'fiddle' with the range..?
Cheers
Jabberoo

i dont think there is a boost on range. i think the emitter intensity is fixed and would require hardware tinkering to make reflections on object brighter for the receiving sensor.

trevoroni said:
Changescreen has an option under the advanced settings ....
Click to expand...
Click to collapse
Actually I played with it a little and realized that it does in fact use the proximty sensor and g sensor. It just seems to bug up some times (or it just might be my device)

Not just yours mine does this as well. I make sure I don't move the phone away from my ear at all but if it is a long call it always seems that either the notification bar or the start button got pressed during the call. It is driving me nuts. I had a program written by someone on XDA for my Fuze that worked awesome called touch in-call screen tweak I want that functionality with the tilt 2

dalavar said:
Not just yours mine does this as well. I make sure I don't move the phone away from my ear at all but if it is a long call it always seems that either the notification bar or the start button got pressed during the call. It is driving me nuts. I had a program written by someone on XDA for my Fuze that worked awesome called touch in-call screen tweak I want that functionality with the tilt 2
Click to expand...
Click to collapse
TouchLockPro has InCallTweak built in. See youtube video in the link. And recently also has added ZoomBar unlock. And it is *FREE*

AOD Not Turning Off In Pocket / Overturned - Can You Test

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

Proximity Sensor not working?

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!