Hello,
I know this has been posted couple of times already, but I think I found some new information why this is happening. Yesterday I noticed that when you press fabric against the proximity sensor you can wake up the screen and input knock code. This doesn't happen with all fabrics, when I pressed my T-shirt against the sensor I couldn't wake up the screen, but when i pressed my shorts and jeans against sensor, I was able to input my knock code. Video of testing can be found here
Can someone verify if they are noticing the same problem? I think that there might be some bad sensors on these phones.
It took pictures itself in my jeans pocket. I am using quick circle case and in order for it to do that first a double tap must be executed, then swipe the screen on any direction to get to the icons and tap on the camera icon, then again to capture a pic. All done in this order apparently. Besides, not just once.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
... also it means that it can place a call by repeating the same on recent calls log.
A easy solution is to put the phone in your pocket facing outwards instead of inwards.
navlem said:
A easy solution is to put the phone in your pocket facing outwards instead of inwards.
Click to expand...
Click to collapse
Doesn't help, it still does it when it moves in my pocket.
Related
Has anyone noticed their phone likes to turn itself on during phone calls as the phone touches your head?
I thought that could be fixed with Advanced Configuration Tool and these options:
◦Phone sleep during call
◦Fast sleep during call
But they both are gone. They were there on my Kaiser. Any ideas?
It's supposed to turn off due to the proximity sensor. I'm using a T-Mobile USA TP2 and it turns off as it touches my ear. One way you can test this, if you haven't already, is to call a phone, then as it is in progress, lay the phone with the screen up, and put your finger across the top of the facade of the phone (cover the top area where the earpiece is). When I do that, in order to replicate my ear towards the phone, the proximity sensor blanks the screen.
As for the AC tool settings you mentioned, I've never touched those, so mine are on the default settings.
Hey, wow! You're right! When the device is against my ear, the display is out. As soon as I pull it away, even slightly, it turns it on!
I'm simple, I know. My wife tells me that all the time.
motocrossmann said:
Hey, wow! You're right! When the device is against my ear, the display is out. As soon as I pull it away, even slightly, it turns it on!
I'm simple, I know. My wife tells me that all the time.
Click to expand...
Click to collapse
It's okay, when I first got my TP2, I encountered the same thing you thought was a problem. Then I saw a video online demonstrating proximity sensors and the guy on the video put his finger along the top/speaker area of the device and the screen turned off. I replicated his actions on my TP2 and realized that the proximity sensor activates when something is touching it or gets fairly close to it. BTW, we're all simple; we just excel in different ways!
LOL, me and the wife learning this stuff too. Hey, heres another (which i just created a post for), GO rub a magnet on the face of the phone while the screen is OFF, right over the tiny keypad. If you have a soft case with magnet in the flat, go see the funky result
carhigh said:
LOL, me and the wife learning this stuff too. Hey, heres another (which i just created a post for), GO rub a magnet on the face of the phone while the screen is OFF, right over the tiny keypad. If you have a soft case with magnet in the flat, go see the funky result
Click to expand...
Click to collapse
Well since I'm already here and I don't want to search for that post (sorry to the Mods since this is irrelevant for this thread), I can answer that too. It's already a well-known issue. The magnet tricks the phone into thinking either the keyboard and/or the stylus is being opened/taken out. However, it is more accepted that the phone is being tricked into the keyboard being opened. There's a registry edit posted on these forums that can fix that, but the downside is if you want the screen to turn on when the keyboard opens, it will no longer turn on without having to press the screen wake-up button.
I'm just using the Slide2Unlock v.204 for WVGA devices. It keeps the phone locked even if the screen turns on. When I slide my phone into my magnet-clasped holster, it sometimes turns on. It's just a habit for me now to check the screen once it's in the holster, so I can turn the screen off if it woke up by itself.
Using Desire for months and everything prefect except one thing. Sometimes I need to press the button on the screen after some system message which need to be heard first. When I put the screen on my ear then its off. I can use the headphone sometimes but not always. I believe its because of the sensing function but cant find the place to turn it off. Could anyone who can tell me how to keep screen on when answering the call? Thanks in advance.
The screen goes off due to the proximity sensor, but it should be back on again when you take the phone away from your ear.
This definitely works for me, though I can imagine that if you have your hand close to the proximity sensor it could cause problems.
Regards,
Dave
I tried again and notice that, sometimes the screen can come back but after long time waiting, but in most case it cant. I am not sure the position where the sensor located. I am using the zagg invisible shield screen cover and not sure if that caused the error of the sensor. Anyhow, is here a place to turn this face sensing function off?
PS, after I cleaned the screen cover then it seems get better response time to show the screen after move the phone away from my face. But still not rapidly as normal phone with keyboard and influence the using experience. So if there was a option to turn this face sensing feature off then it could be better.
I found this link where some one who had the same issue found it was related to their Zagg protector, but on the same thread there are others who have had no such problems.
The proximity sensor is in the top left of the screen, within the black border. circles - see here.
Regards,
Dave
Hi,
Using a lot the double-tap to wake gesture. Was working ok on 3.2.1.
After upgrade to 3.2.2 I need to tap 10 times more to awake the phone.
Dose anyone encountered this problem?
Is there a solution for it?
Thank you.
working well for me on 3.2.2
For me too.
Sent from my ONEPLUS A3003 using Tapatalk
Yeah, I have experienced it not working that well...
---------- Post added at 05:49 PM ---------- Previous post was at 05:49 PM ----------
Yep, not working as well for me too
It's especially happens when I take the phone out from the pocket.
I tried to restart the phone, disable and enable the gesture and wipe cache partition.
Nothing helped.
Any suggestions how can I resolve the problem?
Me too
I went into gestures and enabled "Double tap to wake" and it seems to work fine. Although it seems faster just to unlock the device via the finger scanner.
I don't want to unlock the device, just want to see the notifications on the locked screen.
Its because the pocket mode. Try to cover the top area of the phone with your hand and double tap on the screen... it won't turn on. I don't have this issue on 3.2.2, maybe you have dust or smudge on the proximity sensor next to the front facing camera, so the phone thinks its in your pocket... or you have a faulty proximity sensor. Wrong placed screen protector can cause that too.
So the problem continues in OOS 3.2.4...
The problem is not only in the double tap it's in all available gestures.
When I pull out the phone from the pocket the gestures not working, manual wake up by clicking on the power button resolves the issue.
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 just noticed a little dark flickering spot on my screen just to the right of the front facing camera when making a call and holding the phone away from my face.
I'm assuming this is the proximity sensor causing this and is anyone else having the same event?
Yes I too noticed, only when I’m in call . That’s when proximity sensor is required !
There is already a post about this sensor
yes that spot also flickers when notification arrives or battery low
winol said:
There is already a post about this sensor
Click to expand...
Click to collapse
You are absolutely right! Unfortunately when I typed in the search term nothing came up so I decided to post that question in the Q&A.
Thanks for the heads up though. Dont mean to step on anyone's toes!