The proximity sensor seems unreliable, and the screen keeps turning on/off repeatedly, while keeping the device close to any object while mid call. I've had all sorts of things happened to me post call, because aparantly my face/ear keeps touching the screen.
Has anyone else experienced this with this phone?
Also, does anyone know of the "Special Codes" etc for this phone to enter Diagnostic mode (I've used that on Galaxy phones in the past) or something similar so I can more objectively quantify the behavior?
Silver-Hawk said:
The proximity sensor seems unreliable, and the screen keeps turning on/off repeatedly, while keeping the device close to any object while mid call. I've had all sorts of things happened to me post call, because aparantly my face/ear keeps touching the screen.
Has anyone else experienced this with this phone?
Also, does anyone know of the "Special Codes" etc for this phone to enter Diagnostic mode (I've used that on Galaxy phones in the past) or something similar so I can more objectively quantify the behavior?
Click to expand...
Click to collapse
You can choose to disable or edit Proximity Sensor Settings using this app.
Try this app from Play Store: Proximity Screen Off Lite
If it is useful and you want Full Version, either google "Proximity Screen Off Pro" or buy it.
Hope this helps
Related
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?
This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...
Wondering if anyone has any advice for my weird mic issue - it's a little different to the others I've seen but willing to try anything at the moment. Here's what I've found so far:
*People can't hear me when I talk into the phone. I've tried calling my home phone and listening and I don't hear anything either.
*This problem seems to happen when I'm holding the phone normally (i.e. against my face - ear to the ear speaker and mouth near bottom of the phone's mic)
*If I talk right into the bottom of the speaker (as in have the bottom mic and speaker right in front of my mouth), it picks up audio fine on the other end.
*Speakerphone appears to be fine so secondary mic is working fine.
*Done the usual clean the mic hole with pin (and compressed air), made sure my finger wasn't covering the mic hole, removed any cases, etc.
My suspicion is maybe the proximity sensor is doing something to cause the audio to cut out? I can't imagine the bottom mic being that directional that it picks up nothing in one particular direction while works fine in another.
Phone is bone stock S6 - SM G920W8 running 6.0.1 (Build G920W8VLU3CPC8)
I've already done a factory reset so this thing is as clean as it gets and still no luck. Help!
Apps could be the issue.
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
WSADKeysGaming said:
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
Click to expand...
Click to collapse
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
syee said:
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
Click to expand...
Click to collapse
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Don't mention it!
There are so many settings nowadays that its hard to remember whats on and off, left and right. Glad I could help!
syee said:
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Click to expand...
Click to collapse
Sorry for bumping an old thread, are you familiar with why the Smart Alert feature would do this? Thanks!
I want to set up my phone to turn off automatically when i close the door on my flip case and turn back on when I open it, I also want to do the same thing when I have my phone face down on my desk at night. I was suggested an app called Gravity Screen, but it didnt seem to work properly. For whatever reason it seems the Proximity sensor that is supposed to detect this, cancels out when something like my case or table gets to close too it, I even used another app called "Sensor Test" to prove this. Even Samsungs own diagnostic (*#0*#) has the same issue, I even tried it on my mothers s8 with the same results?
Anyone else have issues with the Prox Sensor
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.
apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.