Related
I'm not sure if it's a proximity issue, software, or related to the phone app itself but quite frequently when I'm on a phone call my screen will stay black even if I pull my face away from the phone. Pressing the power button does nothing, double pressing it for the camera shortcut will have the phone vibrate but still black screen. If I place my finger on the fingerprint scanner it vibrates but still black screen. The only way to get the screen to come back on is for the other caller to hang up. It was especially bad when I called my voicemail and couldn't hang up so it was stuck like that until I held the volume up and power buttons to manually reset the phone. Is anyone else having this issue?
Shadowblade19 said:
I'm not sure if it's a proximity issue, software, or related to the phone app itself but quite frequently when I'm on a phone call my screen will stay black even if I pull my face away from the phone. Pressing the power button does nothing, double pressing it for the camera shortcut will have the phone vibrate but still black screen. If I place my finger on the fingerprint scanner it vibrates but still black screen. The only way to get the screen to come back on is for the other caller to hang up. It was especially bad when I called my voicemail and couldn't hang up so it was stuck like that until I held the volume up and power buttons to manually reset the phone. Is anyone else having this issue?
Click to expand...
Click to collapse
run it on safemode and see if it still happens, if not then there could be an app messing with the experience.. if still doenst turn on while on call on safemode, then call support.
Are u using immersive mode?
I've read that some experienced this after an update to the phone app. I had this problem and it turned out something was wrong with the proximity sensor. I downloaded an app to test the phones sensors and it always said near for the proximity sensor. Had an RMA done on it
I am having the same issue...
Funny thing, i can wake my screen well when I'm calling with my Bluetooth device (Alpine player). But if I'm using the phone, the screen stays dead.
They should at least give us an update that would let us to wake the screen manually.
You guys need to give more detail like are you stock, rooted, modded? Something to go off of
Shadowblade19 said:
I'm not sure if it's a proximity issue, software, or related to the phone app itself but quite frequently when I'm on a phone call my screen will stay black even if I pull my face away from the phone. Pressing the power button does nothing, double pressing it for the camera shortcut will have the phone vibrate but still black screen. If I place my finger on the fingerprint scanner it vibrates but still black screen. The only way to get the screen to come back on is for the other caller to hang up. It was especially bad when I called my voicemail and couldn't hang up so it was stuck like that until I held the volume up and power buttons to manually reset the phone. Is anyone else having this issue?
Click to expand...
Click to collapse
Here is what you do... Remove your screen protector and throw it away. Then, buy one with a proper cutout for the proximity sensor.
Sent from my Pixel 2 XL using Tapatalk
mackentosh said:
You guys need to give more detail like are you stock, rooted, modded? Something to go off of
Click to expand...
Click to collapse
I'm stock with no screen protector just an Incipio dual pro case. I've taken the case off and tried cleaning the phone but the still persists without the case on. I've also tried booting into safe mode and still the same problem occurs. At least now I've went into the settings and turned on power button ends call so I can hang up now. Talked with google support and sent them a bug report awaiting their response.
hatdrc said:
I've read that some experienced this after an update to the phone app. I had this problem and it turned out something was wrong with the proximity sensor. I downloaded an app to test the phones sensors and it always said near for the proximity sensor. Had an RMA done on it
Click to expand...
Click to collapse
What app did you use? I'll try it out.
Shadowblade19 said:
What app did you use? I'll try it out.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=asd.vector.sensor
hatdrc said:
https://play.google.com/store/apps/details?id=asd.vector.sensor
Click to expand...
Click to collapse
Yep mines saying NEAR for the proximity sensor. Guess I'm going to wait on the answer from Google support and RMA the device too. It's weird because I don't have any screen protector or anything to block the sensor and the proximity sensor was fine for the first 2 months.
Shadowblade19 said:
Yep mines saying NEAR for the proximity sensor. Guess I'm going to wait on the answer from Google support and RMA the device too. It's weird because I don't have any screen protector or anything to block the sensor and the proximity sensor was fine for the first 2 months.
Click to expand...
Click to collapse
Mine too. I had no case or screen protector on it. They had me send a bug report first.
hatdrc said:
Mine too. I had no case or screen protector on it. They had me send a bug report first.
Click to expand...
Click to collapse
Yeah I already sent them a bug report last night. Thanks for all the help appreciate it.
Closed per OP request.
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
Is there a way for aod to stay off in confined environments but immediately turn on when taken out off them?
asbogdan said:
Is there a way for aod to stay off in confined environments but immediately turn on when taken out off them?
Click to expand...
Click to collapse
It should automatically turn of if proximity sensor detects something.
You can test it by simply turning phone upside down on the table, after a couple of seconds, AOD will be turned off.
Same goes with pocket or whatever.
I am actually not sure if proximity sensor is in charge for that or just multi touches on the screen, but it works anyway.
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
winol said:
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
Click to expand...
Click to collapse
There is never.a setting for this since AOD.is born. Always automatica turn off in pocket
winol said:
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
Click to expand...
Click to collapse
Mine is also not turning off in pocket, etc.
My Note 8 always has.
it seems it does not work as intended. Should call customer support on Monday.
Might be due to the fact that the proximity sensor is in the screen now. The flickering point on the right of the camera when you initiate a call
Now that I check I don't think the proximity sensor is working at all when not on a call.
As reference, I have the T-Mobile Note 10+. Before the September update, the AOD on my phone used to turn off when my flip case is closed. Now that I updated to the September update, that function stopped working, the AOD is still on when my case is closed. The update fixed the flashing camera hole issue (now works great on apps like aodNotify) but now problem with the AOD. I hope they fix this issue asap with an AOD update or something.
After a few days of using this device i noticed that my screen turns on during phone calls. After doing some research it came out that the proximity sensor is not working properly when phone is being tilted to horizontal position with screen upwards. It just immediately shows that it is far away from any object even that it isn't. The fun fact is that when covering the sensor with my hand while phone is laying on his back doesnt switch it and rotating the phone to vertical position also does not make any effect like the sensor would be locked. Covering it again in that position makes it work.
Can anybody help me with this issue? It's very annoying for me and makes my phone unusable for making calls.
Edit: similar problem here https://forum.xda-developers.com/android/help/huawei-nova-5t-proximity-sensor-problem-t4136595
Same problem here...
here also
I am so lost. What do I do with the phone? What? When does it happen? (Also subscribing.)
Same here, and i notice i have also problems with whastapp and telegram audio notes.
Sometimes screen goes blank randomly and with no reason when i'm listening a audio note.
Hi. Its a well known problem. Its becouse the device has a ultrasonic sensor not like any other. Sensor like you already find out works only in vertical position of the phone. Its well described in the net how it works. Just search. In 4PDA in the section for our phone. But you need to know russian.
I found that thread and it seems that not everyone notices that... Not spending more time on reading this I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Same problem here, it's very frustrating. I can turn the screen back off during a call once I see it's turned on by itself, but it keeps turning back on. I'm sick of muting calls and hanging up on people by pressing buttons when I'm on the phone.
What is the app that you are using @Spectre45?
Spectre45 said:
I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Click to expand...
Click to collapse
Can you please tell us what app you are using?
kage00 said:
Can you please tell us what app you are using?
Click to expand...
Click to collapse
try proximity screen off or call proximity screen fix
LightSmok said:
try proximity screen off or call proximity screen fix
Click to expand...
Click to collapse
Thanks
Listen. There is no proximity sensor at all. The upper mic, speaker and the sensor for orientation are doing the job. When you pick a call the speaker is sending ultrasonic signal and if it locate your ear it dims the screen. Once it works it is working in all positions. But if you move your phone away only in horisontal position it will nit work untill you mive it in vertical again.
Edit: Experienced this issue too. Annoying.
Does using Xiaomi.EU fix this problem? This issue really gets on my nerves. I started daily driving this device (finally I was able to unlock) and I just cannot use it for calls, which is kinda ridiculous from a phone.
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
I was using the phone with cover provided by MI, upon removing that back cover I encounter no such issues.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I didn't have any proximity issues on stock with google dialer. It's not google dialer, it's how you position your head against the earpiece. Sensor is ultrasonic, so it probably doesn't detect properly depending on the position people hold their phones in...
I have the same problem with my work phone - redmi note 9. Tried the app "proximity screen off" but MIUI keeps killing it no matter what i do to keep it alive. It seems that sensor is located on front top right side of the phone so sometimes it gets behind your ear if you are right handed (mine are pretty small) and then the muting starts. When using the phone with left hand - no problems at all.
I would love to have a working app to keep screen off during call.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I also flashed EU rom and the problem persistes.
Hello to everyone,
I bought my OP9 pro 2 month ago, and I loved it since first day, but there are some bugs that I really hate!!
When I finish a call or when I finish to hear a voice message on Whatsapp, the brightness goes down, without I touch anything!
In last days I find another annoying bug, sometimes when i put off the phone from the pocket, the pocket mode remain activated, also if I turn my OP, also if I unlock the smartphone... These two bugs are getting me crazy!
Can anyone help me or I have just wait some software update from OnePlus?
xandrew92 said:
Hello to everyone,
I bought my OP9 pro 2 month ago, and I loved it since first day, but there are some bugs that I really hate!!
When I finish a call or when I finish to hear a voice message on Whatsapp, the brightness goes down, without I touch anything!
In last days I find another annoying bug, sometimes when i put off the phone from the pocket, the pocket mode remain activated, also if I turn my OP, also if I unlock the smartphone... These two bugs are getting me crazy!
Can anyone help me or I have just wait some software update from OnePlus?
Click to expand...
Click to collapse
I've exactly same bugs on my OP 9 Pro , sometimes brightness goes down by itself and without touching it, i've always automatic brightness switched off! Then taking it out from Pocket with Pocvket Mode switched off, i find apk opened by themselves, so a total mess!
brunochka said:
I've exactly same bugs on my OP 9 Pro , sometimes brightness goes down by itself and without touching it, i've always automatic brightness switched off! Then taking it out from Pocket with Pocvket Mode switched off, i find apk opened by themselves, so a total mess!
Click to expand...
Click to collapse
Yes! The same for me! I'm rally freaking out! And Oneplus doesn't care about these bugs!
I had the same problems, but interestingly I face it only when my Camera and Mic is turned off.
for me it was dirt an pocket lent, the sensor is very sensitive for some reason so when ever i get that problem I wipe it and it works flawlessly for the next few days until it needs to be done again
Same here, sometimes I can't even turn on the screen after a call...
awsan said:
for me it was dirt an pocket lent, the sensor is very sensitive for some reason so when ever i get that problem I wipe it and it works flawlessly for the next few days until it needs to be done again
Click to expand...
Click to collapse
I don't think so, I've already tried to wipe it, but nothing changed! I have this problem since first day... I thought they resolve it with an update, but after 4 months I'm still waiting
Hello. There is a solution to the problem with the proximity sensor. You go to the dialer enter *#808#, looking for "Device dubbing* and there are "proximity sensor test", tap and choose "infrared proximity calibration". You calibrate the sensor. it should help you. You can also calibrate other problem sensors. Try it with a brightness sensor too
020982 said:
Hello. There is a solution to the problem with the proximity sensor. You go to the dialer enter *#808#, looking for "Device dubbing* and there are "proximity sensor test", tap and choose "infrared proximity calibration". You calibrate the sensor. it should help you. You can also calibrate other problem sensors. Try it with a brightness sensor too
Click to expand...
Click to collapse
Can't use *#808#