I notice this both in my trouser pocket, and also in my shirt pocket. The sensor is detecting touch and waking the phone, and you can feel the short vibration.
I know the Oneplus3 had this issue, and I believe it was fixed by using the proximity sensor to deactivate the fp sensor. I don't suppose this is possible to do as of now for the 5s? If not, could it be implemented?
I am using the latest nightly Lineage build.
I see the options has "Display->Prevent accidental wake-up", but this seems to only be for gestures and not for fingerprint/home button.
I've raised a Lineage jira ticket. Can anyone else confirm they are getting the same issue?
https://jira.lineageos.org/browse/REGRESSION-1154
Only seems to happen with certain fabric. In my 'smart' work trousers, its always waking up. In my tracksuit trousers, it doesnt seem to do it.
Seems much better, if not fixed, with the current Nightly 14.1 build.
I have this problem in mi5s.
Related
Is there a fix for the fingerprint sensor going off randomly when its in your pocket? I feel it vibrate when its in my pocket, its sort of annoying.
There's no fix for it yet. Only solution temporarily until there is a fix is to face the screen away from your thigh.
hello I have been trying to find a rom that has a working proximity sensor or to stop accidental wakeup when in my pocket. I wear shorts a lot which are a bit thin and I feel the phone vibrating as if it got a wrong fingerprint every now and than so I have tried to cover the proximity sensor and attempt to unlock the phone and it unlocks no problem. also when making phone calls the screen stays on causing me to touch random buttons.
so may questions is there a rom that has the proximity sensor working? and please is you could just cover the sensor and try to see it prevents the phone from waking up.
thank you for any feed back.
NOTE: might need to turn on "prevent accidental wake up" under display settings.
ROMS ive tried and did not work: PURE CM, Resurrection.
Sometimes screen just turn off and wont turn on until call is done ,sometimes it works fine,sometimes it wont work at all and screen is on all the time...Anyone else had these problems?
Using latest OMNI build
Yes. I think it's quiet common. Just remove Proximity sensor. Download Magisk and disable Proximity sensor.
Yeah the proximity sensor is a little hit or miss. I keep hitting the mute button with my cheek during calls ?
I had this problem for a lot of time and just fixed it with a small piece of plastic, I cleaned the phone starting from the speaker and going both left and right while using an app that show sensors stats live, cleaning it restored full functionality, god it was so easy I can't believe it.
Anyone think that perhaps the proximity sensor of this device doesn't work always?
After using my phone if I put it in my pocket without locking I expect that it will not register ghost/accidental touches but I don't think the phone handles that very well. Often when I pull out the phone I can see some random screen got opened.
Are others also facing this issue?
manish_bhaumik said:
Anyone think that perhaps the proximity sensor of this device doesn't work always?
After using my phone if I put it in my pocket without locking I expect that it will not register ghost/accidental touches but I don't think the phone handles that very well. Often when I pull out the phone I can see some random screen got opened.
Are others also facing this issue?
Click to expand...
Click to collapse
Not random screen opening but once i remove it out of my pocket i get a warning screen saying accidental touch protection is on or something.
Or sometimes a clock, the one on the lock screen where you just tap on it and it zooms in the clock.
Have you turned ON the Accidental Touch Protection? I initially had Ghost Touch problems during jogging but with the change of placement of the phone, i now dont have the problem. Make sure that the screen faces the pocket side not the thigh side. Most of the ghost touches happen while interaction with the thigh.
Sent from my SM-A505F using Tapatalk
Sukhi said:
Have you turned ON the Accidental Touch Protection? I initially had Ghost Touch problems during jogging but with the change of placement of the phone, i now dont have the problem. Make sure that the screen faces the pocket side not the thigh side. Most of the ghost touches happen while interaction with the thigh.
Click to expand...
Click to collapse
The setting was already on. Anyway I toggled it off and on again just in case. Making the phone face outwards in the pocket may work as a suggestion, but it still probably implies that the phone is not doing a good job in blocking these accidental touches. I also like the screen inwards in case I hit a table edge or something.
The other setting I did is to ensure the phone locks itself quickly after the screen goes off. Earlier I had it at a higher value and its possible the device was switching on to an unlocked state. This is working a little but in my old devices I recall I was able to pocket even if the screen was on and i didn't really have this issue.
Accidental Touch option don't working well as need it.
Sometimes working and sometimes don't but proximity sensor working like a charm
Think it's a software bug.
Working like on a wind
One of the touch screen issues I sometimes experience is when swipes are "broken" and register as shorter swipes and taps. This makes me think maybe the accidental touch protection, which is supposed to be triggered by the proximity sensor, is being triggered when it shouldn't. We all have read complaints about how the proximity sensor does not work very well.
So on a hunch, last time I had this issue (trying to swipe in gboard), I stuck my finger on the front-facing camera, and interestingly, swiping worked fine (I expected the screen to be disabled - guess that only actually is supposed to happen when you're on a call?).
Since this issue is so random it's hard to really test it. But I've had quite an experience with the proximity sensor.
I wanted the AOD to turn off when the phone is in my pocket, which is the norm on other phones I've used but for some reason Samsung does not do. So I set out figuring out how to do this in Tasker. I got a sensor test app and noticed the proximity sensor basically has two values: 0.0 and 5.0. It is very slow to respond (slower for "uncover" events) and seems to only switch to 0 if my finger is right on the camera. So I set up Tasker to turn the AOD off if the proximity sensor value is < 1, or on if it is >= 1. I also made it vibrate briefly so that I could tell when the sensor was toggling even if I couldn't see the AOD.
At first it worked fairly well. If I manually covered and uncovered the camera, the AOD would dutifully toggle (not instantaneously). But in "real life" practice, it turned out to be quite unreliable. There would be phantom proximity changes while I was using the phone or carrying it -- most interestingly, it often toggles the AOD off briefly when I pick up my phone -- but I didn't really notice any surprise vibrations while the phone was in my pocket. After a couple hours, when my living room got darker (not completely dark), the whole thing went crazy and the AOD would toggle every few seconds with the phone sitting on a table.
So I think the whole "let's ditch a dedicated proximity sensor and use other things to get the same result" is not quite mature yet. And perhaps it is buggy enough to cause one of the issues we think of as a touchscreen one.