A bug of pocket mode in OOS 5.1.6 - OnePlus 6 Questions & Answers

The problem is caused by aggressive doze and has been resolved.
--------------------
I upgraded to OOS 5.1.6 yesterday, then I found that I can't unlock my phone by fingerprint when the screen is off. After some tests, I realize this is a problem with pocket mode.
When the phone is in my pocket, which means that the distance sensor is covered by an object, I can't unlock my phone by fingerprint or use screen off gesture. When I take the phone out of my pocket, I should be able to use these features again. But in OOS 5.1.6, after I take the phone out of my pocket, I can't do these unless I press the power button.
Does anyone have the same problem?

Do you have ang Glass screen protector that covers proximity sensor?

Really strange. I also updated my OP6 to OOS 5.1.6 and I don't encountered any problem with fingerprint or face unlock. I also have a full and original OP screen protector.

That wasn't just 5.1.6 it happened in 5.1.5 too. It's because the proximity sensor isn't going to stay on 24/7 and waste battery just to see if it's in your pocket. It'll check, if it's in a pocket it'll disable the fingerprint sensor and double tap to wake for a short amount of time, then check again, repeat.

plantator said:
Do you have ang Glass screen protector that covers proximity sensor?
Click to expand...
Click to collapse
Nope

TheNetwork said:
That wasn't just 5.1.6 it happened in 5.1.5 too. It's because the proximity sensor isn't going to stay on 24/7 and waste battery just to see if it's in your pocket. It'll check, if it's in a pocket it'll disable the fingerprint sensor and double tap to wake for a short amount of time, then check again, repeat.
Click to expand...
Click to collapse
Yes, I think that if you are in doze mode, the system will check the distance sensor less. Or maybe this is just a problem of the optimize app.

Nope, no issues at all really and nothing with teh fingerprint sensor not responding from in pocket since being on 5.1.6 since Saturday. I have the regular pre-installed protector on. I also have the aggressive doze on and only Textra, Whatsapp and Blue Mail whitelisted.

Eric214 said:
Nope, no issues at all really and nothing with teh fingerprint sensor not responding from in pocket since being on 5.1.6 since Saturday. I have the regular pre-installed protector on. I also have the aggressive doze on and only Textra, Whatsapp and Blue Mail whitelisted.
Click to expand...
Click to collapse
You mean advanced optimization?

handsome_hell said:
The problem is caused by aggressive doze and has been resolved.
--------------------
I upgraded to OOS 5.1.6 yesterday, then I found that I can't unlock my phone by fingerprint when the screen is off. After some tests, I realize this is a problem with pocket mode.
When the phone is in my pocket, which means that the distance sensor is covered by an object, I can't unlock my phone by fingerprint or use screen off gesture. When I take the phone out of my pocket, I should be able to use these features again. But in OOS 5.1.6, after I take the phone out of my pocket, I can't do these unless I press the power button.
Does anyone have the same problem?
Click to expand...
Click to collapse
I just got my OP6 last weekend and I immediately took the OTA. I have had no problems with the pocket sense. I pull mine out of my pocket all the time and it immediately unlocks when I use the print sensor.

handsome_hell said:
You mean advanced optimization?
Click to expand...
Click to collapse
Yep

5.1.6 has officially been withdrawn by OnePlus today because of these freezing issues

i have a diff problem altogether where the phone screen comes on by itself despite me not touching the phone no one called in and no sms received.
---------- Post added at 07:35 PM ---------- Previous post was at 07:35 PM ----------
devnerd said:
5.1.6 has officially been withdrawn by OnePlus today because of these freezing issues
Click to expand...
Click to collapse
what!

devnerd said:
5.1.6 has officially been withdrawn by OnePlus today because of these freezing issues
Click to expand...
Click to collapse
God...
Waiting for 5.1.7

Related

Auto brightness not working?

Running 5.0 on AT&T model. I have auto brightness turned on with baseline at dimmest setting which as most know is bright enough for most indoor situations. When I go outside into broad daylight, the brightness does not change. I can manually increase to full (and then the display is readable) but nothing happens on it's own.
Is this normal, am I missing something else? Defective light sensor?
EDIT: According to the following apps, I don't have a light sensor and my proximity sensor is failing. Can anyone confirm good data from them? -- Sensor Box for Android, Sensor Test, Phone Tester, Sensor Kinetics
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Ace42 said:
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Click to expand...
Click to collapse
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Neo42 said:
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Click to expand...
Click to collapse
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Ace42 said:
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Click to expand...
Click to collapse
Tried factory reset last night with no change. This phone has never been rooted (and I received it new)
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Ace42 said:
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Click to expand...
Click to collapse
Thanks so much for the screen grabs, this confirms my results are abnormal.

proximity sensor

Hello, i found a problem or i don't know what to say, but the proximity sensor after screen looks, after a periode is off but it torns on, and stays on unless i unlook the screen. Your's mate 7 make the same or its just mine.? I run android L b331. Gesture are all off. Sorry for my bad language.
Chereches Paul said:
Hello, i found a problem or i don't know what to say, but the proximity sensor after screen looks, after a periode is off but it torns on, and stays on unless i unlook the screen. Your's mate 7 make the same or its just mine.? I run android L b331. Gesture are all off. Sorry for my bad language.
Click to expand...
Click to collapse
I have the same problem! when I restart the phone, it starts working but just after a while again stops. don't know what is causing it and how to resolve? though i reset my phone to the factory twice no difference yet.
---------- Post added at 05:34 AM ---------- Previous post was at 04:40 AM ----------
sabkt said:
I have the same problem! when I restart the phone, it starts working but just after a while again stops. don't know what is causing it and how to resolve? though i reset my phone to the factory twice no difference yet.
Click to expand...
Click to collapse
Just today when i was searching for a solution and found a clue and decided to try ! which is far a success!
try to disable screen unlock magazine(Magazine Unlock) and the sensor will remain working.
my huawei mate 7 proximity sensor froze the only thing that appears on my phone is the smart cover image i by accident put the huawei on water with soap then when i took it of the water i discovered that the proximity sensor froze.
my huawei mate 7 proximity sensor froze the only thing that appears on my phone is the smart cover image i by accident put the huawei on water with soap then when i took it of the water i discovered that the proximity sensor froze.
same problem with me and no solution yet

Proximity sensor issue

As I unbox n started using my brand new Samsung S8+, i am having this popup re the proximity sensor being blocked or something. Is this a firmware issue or hardware issue? Thanks if anyone is willing to entail their story re this matter, any fix would be of good help. Sorry if this question is being raised in this thread.
The proximity sensor is left to the earpiece, and right to the IR LED (the red IR sensor used with Iris scanner).
Is that area covered with anything? Screen protector, dust, whatever?
Skander1998 said:
The proximity sensor is left to the earpiece, and right to the IR LED (the red IR sensor used with Iris scanner).
Is that area covered with anything? Screen protector, dust, whatever?
Click to expand...
Click to collapse
I find this popup whenever I take the phone out of my pocket. So because of that the proximity sensor is blocked? Its covered by my pocket. But what is the solution. Its draining battery.
ifran13 said:
I find this popup whenever I take the phone out of my pocket. So because of that the proximity sensor is blocked? Its covered by my pocket. But what is the solution. Its draining battery.
Click to expand...
Click to collapse
That's odd, can not replicate.
Not an issue with software or hardware and its not draining your battery, LOL. It's a feature mate. You likely have "Keep screen turned off" enabled in your display settings. It uses your proximity sensor to turn off the screen for you if it senses that the phone is in a pocket or bag. I think it will throw up a dialog box if it gets triggered, that's probably what you're seeing.
xeathpk said:
Not an issue with software or hardware and its not draining your battery, LOL. It's a feature mate. You likely have "Keep screen turned off" enabled in your display settings. It uses your proximity sensor to turn off the screen for you if it senses that the phone is in a pocket or bag. I think it will throw up a dialog box if it gets triggered, that's probably what you're seeing.
Click to expand...
Click to collapse
Thanks mate. That makes lot of sense to me now! Lol. Why ddnt I think of that, must have slipped off my mind haha
I also have an S8 and while i am talking on the phone the screen lights up and vibrates,no reason,no message nothing.It's annoiyng i can't talk on the phone calmly because of this.Anyone with the same issue?Thanks
Many thanks it s very useful for me

Anyone else having this problem?

When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor.
Click to expand...
Click to collapse
No, mine isn't doing that. You might have a dud.
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
Click to expand...
Click to collapse
I've had that happen on my Pixel 2 XL. Only once or twice and restart fixed it every time.
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
fury683 said:
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
Click to expand...
Click to collapse
I had a case with a built-in screen protector on it and I thought that might be what was causing it but after taking it off it still did it. Weird thing though once I put it on the wireless charger it stop doing it. Hasn’t done it all day even with case on. Weird. Still thinking about taking it back to Best Buy and swapping it out.
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
tonic1080 said:
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
Click to expand...
Click to collapse
Had this very issue with my pixel XL and blowing on the top speaker grille of dust with compressed air solved it.
But if this is out of the box that sucks. It should not be like that. My pixel was approaching two years when that happened.

Question Ghost touches

Since the April update (US unlocked, 512gb), I randomly get ghost touches. I'll be in an app, and can actually see the back, recent and home button light up at separate times, causing the app to go back a page, reload or disappear. I do have a Whitestone glass protector, but as stated, this only came about after the April update 2 days ago. Anyone else? Really not wanting to (or have the time, takes me days) factory reset to see if this is hardware or software. And so very random, and in different apps so safe mode probably wouldn't help either. I rarely use the pen. Can't replicate so can't get screen recording.
pre4speed said:
Since the April update (US unlocked, 512gb), I randomly get ghost touches. I'll be in an app, and can actually see the back, recent and home button light up at separate times, causing the app to go back a page, reload or disappear. I do have a Whitestone glass protector, but as stated, this only came about after the April update 2 days ago. Anyone else? Really not wanting to (or have the time, takes me days) factory reset to see if this is hardware or software. And so very random, and in different apps so safe mode probably wouldn't help either. I rarely use the pen. Can't replicate so can't get screen recording.
Click to expand...
Click to collapse
Clear system cache.
If that fails use safe mode to see if a 3rd party app is the cause.
Updates can break things...
Android 11 and especially 12 aren't very app friendly. Google blames the developers... I blame Gookill. The usual suspect, tastes like Apple
Yeah, these updates aren't fixing as much as they break lately. I'll try the system cache. Thanks.
pre4speed said:
Yeah, these updates aren't fixing as much as they break lately. I'll try the system cache. Thanks.
Click to expand...
Click to collapse
Would help to put what firmware specifically.
I was on U1 AVCK with AT&T sim and was having way too many issues, so I reverted to U AVCJ and phone is normal again.
Kris_b1104 said:
Would help to put what firmware specifically.
I was on U1 AVCK with AT&T sim and was having way too many issues, so I reverted to U AVCJ and phone is normal again.
Click to expand...
Click to collapse
It's also U1 AVCK. What issues were you having? If I downgrade, don't I have to factory reset?
pre4speed said:
It's also U1 AVCK. What issues were you having? If I downgrade, don't I have to factory reset?
Click to expand...
Click to collapse
Yeah you would have to factory reset, but it's better than having ghost touches.
I was having ghost touch, battery drainage like crazy from Google Play Services, and bad SOT time, like maybe 4 hours.
On AVA6, AVC8, and AVCJ I always got about 8-9 hours SOT.
Your choice.
Kris_b1104 said:
Yeah you would have to factory reset, but it's better than having ghost touches.
I was having ghost touch, battery drainage like crazy from Google Play Services, and bad SOT time, like maybe 4 hours.
On AVA6, AVC8, and AVCJ I always got about 8-9 hours SOT.
Your choice.
Click to expand...
Click to collapse
I don't have drain issues thankfully, I can get a full 12 hours usage with probably close to what you got. But these ghost touches are annoying, yes. But man, factory reset and setup would take me more than 3 days which would be my days off and I just don't have time for it right now. Guess I'll have to deal. Crap.
I too have the ghost touches...It's random and it started after the 1st April update. There is another thread regarding the touches as well....It can happen in any app at any time...very annoying
termdj said:
I too have the ghost touches...It's random and it started after the 1st April update. There is another thread regarding the touches as well....It can happen in any app at any time...very annoying
Click to expand...
Click to collapse
Very much so. And I just don't have the luxury of time to reset. Or downgrade.
So according to the Samsung community, taking touch sensitivity and power saving off *should* stop the ghost touches. I didn't have power saving on, but did have the other due to my glass screen protector. I'll report back in a day or so.
have you tried enabling the "show touches" in developer options to see if it is the screen being touched, or wether its just a bug in the softwre causing it ?
gav83collins said:
have you tried enabling the "show touches" in developer options to see if it is the screen being touched, or wether its just a bug in the softwre causing it ?
Click to expand...
Click to collapse
I can actually see the buttons get highlighted when the ghost touches happen, so no need for the show touches option. But since turning off the touch sensitivity, I haven't had one ghost touch.
Ah ok, yh I did get that, that you could see them lighting up, but that wasn't necessarily ghost touches as it were and showing touches could have confirmed that, anyway your problems solved
TONS of posts on ghost touches on reddit. Try turning off screen sensitivity. That supposedly helps, but not 100%. You'll have to wait for another update.
I had ghost touches when power saving was on. Since the second April update, the problem was solved for me. Exynos version.
pre4speed said:
Since the April update (US unlocked, 512gb), I randomly get ghost touches. I'll be in an app, and can actually see the back, recent and home button light up at separate times, causing the app to go back a page, reload or disappear. I do have a Whitestone glass protector, but as stated, this only came about after the April update 2 days ago. Anyone else? Really not wanting to (or have the time, takes me days) factory reset to see if this is hardware or software. And so very random, and in different apps so safe mode probably wouldn't help either. I rarely use the pen. Can't replicate so can't get screen recording.
Click to expand...
Click to collapse
I've had the exact same ghost touches issue only since the April security patch update. I've got a Verizon S22 Ultra 512GB with the Whitestone Dome Glass protector and I usually run power savings mode.
I've noticed the ghost touches (I'll watch the home button or recent button light up on its own without me touching it) stop when I turn off power savings mode and they will start again once I enable power savings mode. I'll have to try turning off the touch sensitivity while power savings is enabled, and see if that stops it. But, I think it has to do with the 120hz down to 60hz while in power savings mode, seems there is a bug.
There isn't rhyme or reason for what triggers the ghost touches either from my experience. The ghost touches seem to happen most in the Samsung Internet Browser Beta for me the most, but it'll also happen in the settings menu or other apps from time to time, just not as much as the browser. It'll kick me out of the browser and bring me back to my home screen and or open the recents ui. Very annoying. Turning off power savings mode seems to stop it.
I am currently running power savings mode and have turned off the touch sensitivity and it seems to have stopped the ghost touches for now. I've only had it disabled for 10 minutes or so, so not long enough to truly tell, but it seems good so far.
termdj said:
I too have the ghost touches...It's random and it started after the 1st April update. There is another thread regarding the touches as well....It can happen in any app at any time...very annoying
Click to expand...
Click to collapse
This is what I have had happening! I really had no idea why. I thought maybe even though I did not touch the screen, maybe I got close enough so that I triggered the "touch". But it really did not seem like that was what was happening. I do not use power saving but I do have touch sensitivity on. It never happened until recently though.
So I've had touch sensitivity off now for quite a few hours with power savings mode enabled, and I have not had any ghost touches at all whatsoever. So, apparently it's touch sensitivity being enabled that triggers the ghost touches.
Kris_b1104 said:
Yeah you would have to factory reset, but it's better than having ghost touches.
I was having ghost touch, battery drainage like crazy from Google Play Services, and bad SOT time, like maybe 4 hours.
On AVA6, AVC8, and AVCJ I always got about 8-9 hours SOT.
Your choice.
Click to expand...
Click to collapse
termdj said:
I too have the ghost touches...It's random and it started after the 1st April update. There is another thread regarding the touches as well....It can happen in any app at any time...very annoying
Click to expand...
Click to collapse
gav83collins said:
have you tried enabling the "show touches" in developer options to see if it is the screen being touched, or wether its just a bug in the softwre causing it ?
Click to expand...
Click to collapse
Justinphxaz said:
I've had the exact same ghost touches issue only since the April security patch update. I've got a Verizon S22 Ultra 512GB with the Whitestone Dome Glass protector and I usually run power savings mode.
I've noticed the ghost touches (I'll watch the home button or recent button light up on its own without me touching it) stop when I turn off power savings mode and they will start again once I enable power savings mode. I'll have to try turning off the touch sensitivity while power savings is enabled, and see if that stops it. But, I think it has to do with the 120hz down to 60hz while in power savings mode, seems there is a bug.
There isn't rhyme or reason for what triggers the ghost touches either from my experience. The ghost touches seem to happen most in the Samsung Internet Browser Beta for me the most, but it'll also happen in the settings menu or other apps from time to time, just not as much as the browser. It'll kick me out of the browser and bring me back to my home screen and or open the recents ui. Very annoying. Turning off power savings mode seems to stop it.
I am currently running power savings mode and have turned off the touch sensitivity and it seems to have stopped the ghost touches for now. I've only had it disabled for 10 minutes or so, so not long enough to truly tell, but it seems good so far.
Click to expand...
Click to collapse
Will_T said:
This is what I have had happening! I really had no idea why. I thought maybe even though I did not touch the screen, maybe I got close enough so that I triggered the "touch". But it really did not seem like that was what was happening. I do not use power saving but I do have touch sensitivity on. It never happened until recently though.
Click to expand...
Click to collapse
Justinphxaz said:
So I've had touch sensitivity off now for quite a few hours with power savings mode enabled, and I have not had any ghost touches at all whatsoever. So, apparently it's touch sensitivity being enabled that triggers the ghost touches.
Click to expand...
Click to collapse
Seems as tho it's touch sensitivity confirmed. No ghost touches since turning it off and actually haven't had any issues with the Whitestone protector and TS being off. Unless another update comes and makes the screen unusable with it off, I'll just keep it off. Never really used power saving at all, no idea why it's auto enabled from factory, so having that off I'm not seeing any issues either.
I have turned touch sensitivity on and off and no real difference, still there with both settings....I did pick up that some days it's a lot less then other days...yesterday I has no touches, but today a lot....no matter what the sensitivity setting is...

Categories

Resources