Related
I realized today my phone was facing inwards towards my leg and that it may be double tapping and turning on in my pants. Any way of stopping this, but also monitoring? I am just curious as I faced my phone outward it kept my battery lasting much longer today.
Dsmwookie said:
I realized today my phone was facing inwards towards my leg and that it may be double tapping and turning on in my pants. Any way of stopping this, but also monitoring? I am just curious as I faced my phone outward it kept my battery lasting much longer today.
Click to expand...
Click to collapse
I had the same issue, but for me it turned out to be neither the back button nor double tap to wake. For me it was greenify, which does evil things when it doesn't have root: it turns on the screen, goes to the app info of an app it wants to hibernate, and "clicks" the "force stop" button, before going back and just leaving the screen on.
Of course this may not be the cause of your problem. You may not even have greenify installed. Have a useful way to debug the issue: install tasker (or something similar, maybe condi can do it too), and make a profile that makes your phone vibrate when the screen turns on. Make sure the vibration duration is distinguishable from notifications, 200 ms worked for me.
This way, you will know exactly when your phone turns on in your pocket. You will be able to reason about whether the back button was accidentally pressed or whether it's double tap to wake, or something else altogether, like greenify in my case.
Just a side note: it's unlikely to be double tap to wake, because double tap to wake will not turn your screen on when the proximity sensor detects that something is close. You can try that by holding your finger over the proximity sensor while trying to turn it on. Double tap to wake won't turn the screen on in the first place, and the screen will turn on and immediately off when using the power button.
So yeah, try the tasker/condi profile and see what your phone does right after it wakes. I saw mine force closing Facebook messenger like 7 times in less than an hour, and it stopped after I uninstalled greenify.
Sent from my LG-H815
Ive noticed the screen on out of pocket but rarely. One new feature is the "slide down" quick peek while the display is off. This new feature may have new side effects.
player911 said:
Ive noticed the screen on out of pocket but rarely. One new feature is the "slide down" quick peek while the display is off. This new feature may have new side effects.
Click to expand...
Click to collapse
That too doesn't work when the proximity sensor senses something is close. Try it by holding a finger over it while trying to pull down the thing with another finger.
Sent from my LG-H815
My tap to wake and lift to wake are not working. I tested the accelerometer and gyroscope and both are working ok. Screen rotation is working too. Does anyone have these issues?
Try lock screen immediately
By going setting/security & location/screen lock setting/automatic lock to immediately.
Android 7?1 on Pixel XL had tap to wake and lift to wake.
Android 8.0 removed all that. Doesn't exist on Pixel 2 XL.
Icyou said:
Try lock screen immediately
By going setting/security & location/screen lock setting/automatic lock to immediately.
Click to expand...
Click to collapse
I tried the screen lock immediately.. Didn't work.
Already factory reset too
nxt said:
Android 7?1 on Pixel XL had tap to wake and lift to wake.
Android 8.0 removed all that. Doesn't exist on Pixel 2 XL.
Click to expand...
Click to collapse
Sorry, not tap to wake.
It's called double tap to check and lift to check. Even twisting the phone to switch between the front and camera is not working....
ultrastranger said:
Sorry, not tap to wake.
It's called double tap to check and lift to check. Even twisting the phone to switch between the front and camera is not working....
Click to expand...
Click to collapse
just stating for the record, they all work fine in 8.1
hmmm.. so these features are not working on 8.0 for pixel 2 xl? Im just concerned whether its a hardware or software issue.
Do these features work for you guys?
The double tap and lift to check (grayed out) phone options are in ambient display settings. Double tap works, lift does not, 8.1.
ultrastranger said:
Sorry, not tap to wake.
It's called double tap to check and lift to check. Even twisting the phone to switch between the front and camera is not working....
Click to expand...
Click to collapse
Go to Settings, type Double at the top, you should see three settings for the various wake and camera flip. Make sure they're on.
Personally Lift to wake o haven't seen it work on my 2 XL. I'm pretty sure it's been removed.
My double tap n lift are both working fine on 8.0, and my hardware rev is 10 on penguin/panda
Both are working for me, 8.0. Maybe a factory reset will work?
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Both work fine here on 8.0
Sent from my Pixel 2 XL using Tapatalk
Ditto, both working fine on 8.0 for weeks...
Lift to wake only works if always on display is off.
https://tunecomp.net/disable-raise-to-wake-lift-to-check-google-pixel/
I have a Pixel 2 XL and double tap to wake, ambient display, wake on receiving notifications and the camera flip gesture, are all not working on my device. Those options are all selected, and I have tried safe mode as well as a factory reset to no prevail. Google's response was to send a replacement however all of the hardware is confirmed as operational. This all occurred after a software update.
Double tap is inactive and does not work. It is selected as on.
Ambient display is on, screen is locked after 5 seconds, however the ambient display turns off after 10 seconds of inactivity.
Wake for notifications, does not wake the screen.
Flip for selfie camera does not work no matter which way I hold the phone.
Android 8.0.0
Same here, pixel 2 XL double tap to wake completely unresponsive. On 8.1 and factory reset.
I have enabled double tap to show ambient display for time and notification and i updated to 8. 1 manually no wipe or reset and that is working normal as on 8.0
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
Hey guys
I noticed all these problems after the update to 8.1.
it seems like Google somehow messed up the proximity sensor, that's why ambient screen is turning off and you can't use double tap to wake.
there are several threads to this but nobody really has a fix.
https://forum.xda-developers.com/pixel-2-xl/help/8-1-update-broke-proximity-sensor-t3718659
for some people the problem was solved after removing their screen protector. But I don't have a screen protector so..
I hope Google is aware of this.
Hey..i found the problem
I had the same issue. the following fixed it.
Settings -> Security -> Smart lock -> Disable all.
Smart lock kept my phone unlocked at home.
After i disabled trusted places....the double tap works just fine. The Flip camera works too after i disabled smart lock.
I hope this works for you too.
Hello guys
I have bought my pixel 3 xl recently
Today i tried to take a picture for my phone and it is locked ( screen off)
I noticed the sensor is always on in the notch
It is infrared sensor
I think it is the proximity sensor
I think this caused a huge battery drain in my phone
Maybe 2% per hour
Do you have the same sensor always on condition ?
Looks like the sensor is always on whenever the ambient display / double tap to check the phone is triggered
I have turned it off and i will monitor battery behavior
Eiad Ajam said:
Looks like the sensor is always on whenever the ambient display / double tap to check the phone is triggered
I have turned it off and i will monitor battery behavior
Click to expand...
Click to collapse
You shouldn't have to turn off AOD, and double tap does not use the proximity sensor. AOD is a key feature of the phone and I'm not seeing this. Try setting it back the way it was originally and running in safe mode to rule out a possible errant user app.
v12xke said:
You shouldn't have to turn off AOD, and double tap does not use the proximity sensor. AOD is a key feature of the phone and I'm not seeing this. Try setting it back the way it was originally and running in safe mode to rule out a possible errant user app.
Click to expand...
Click to collapse
Double tap to wake needs proximity sensor to detect if the phone in your pocket
I have disabled AOD and double tap to wake
My battery has improved, also the phone now has less battery drain.
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
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
vinay3190 said:
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Click to expand...
Click to collapse
It's issue on most OnePlus phones.. I had the issue on 6T, 7 Pro.. annoying
1rahul1996 said:
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
Click to expand...
Click to collapse
This is the biggest reason I may be going Pixel 4...
Yes I too have this issue with my OP7T
Yup, same issue here.
Another thread about it here - https://forums.oneplus.com/threads/proximity-sensor-doesnt-work.1147600/
Also issue present on OP7Pro forums.
Seems to be related to this "Virtual Sensor":
https://www.ellipticlabs.com/2019/0...eaner-design-to-oneplus-7-series-smartphones/
So we have to wait and hope (could be this same as Never Settle? :d) that can be fixed with a software update.
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Josh McGrath said:
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Click to expand...
Click to collapse
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
trveller72 said:
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
Click to expand...
Click to collapse
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Josh McGrath said:
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Click to expand...
Click to collapse
Yeah, I am starting to remember good ol' days with the OPX. Every OTA was fixing one thing and breaking 3 other.
At that time I said no OP again, but still, this one seems to be be a good phone. Time will tell.
Coming back to our issue, I am puzzled that only a few people reported this.
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
roofrider said:
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
Click to expand...
Click to collapse
Not rooted, but using a custom dialer as the default Phone app (True Phone).
When I switched the default Phone app to Oneplus App, I could not reproduce the issue.
Testing for a few days to see if this works. Would be such a pity if the app is the problem because I really like it.
Also I just sent a log to OP support (they contacted me after I logged the issue on the feedback).
Yes, it is using the virtual sensor as you said (link in my previous post).
How does the virtual sensor work?
Sent from my [device_name] using XDA-Developers Legacy app
I couldn't find anything concrete on how this software-based proximity sensor, Elliptic Labs INNER BEAUTY, works. The keywords are: ultrasound, sensor fusion, and machine learning. A hardware-software I guess.
The 7T does have an IR sensor under the display, but I think this is only used for DT2W and Tap to Show to prevent the display from accidentally turning on when the phone is in the pocket and so on. Not for calls.
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
igotlostintampa said:
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
Click to expand...
Click to collapse
Twrp is out for the 7t. It's not flashable last I checked but it is bootable and usable for what I used it for which was a backup of stock rom