Related
When I am in a call, putting the phone to my face turns the screen off using the proximity sensor. However, removing the phone from my face does not turn the screen back on. Nothing turns it back on even if I push all the buttons or hold them or do anything unless the other person hangs up. I cannot remember when it started....before or after the recent update.....but it did start very recently. Any ideas? If I turn off the proximity sensor during calls it works fine by locking and unlocking the screen with the buttons.
MNDZA said:
When I am in a call, putting the phone to my face turns the screen off using the proximity sensor. However, removing the phone from my face does not turn the screen back on. Nothing turns it back on even if I push all the buttons or hold them or do anything unless the other person hangs up. I cannot remember when it started....before or after the recent update.....but it did start very recently. Any ideas? If I turn off the proximity sensor during calls it works fine by locking and unlocking the screen with the buttons.
Click to expand...
Click to collapse
Is anything covering the front facing camera, or light sensor? Like a case, bad screen protector, etc....
Does your front facing camera work just fine as a camera?
How about air gestures? Do they work?
I'm asking these things because it seems your proximity sensors aren't working properly. Your phone thinks it's next to your head all the time, so it's not waking the screen until the other person ends call. We need to find out which one is acting up and why.
The front camera works, but in my office it seems VERY sensitive to light. The lights are glaring heavily. I never use the front camera so I don't know if that's normally how it was. Air gestures work when the screen is on (swiping left and right to view my photos), but the quick glance won't work when the phone is locked. The weird thing is that quick glance works when I do the "try it" tutorial only.
440bro said:
Is anything covering the front facing camera, or light sensor? Like a case, bad screen protector, etc....
Does your front facing camera work just fine as a camera?
How about air gestures? Do they work?
I'm asking these things because it seems your proximity sensors aren't working properly. Your phone thinks it's next to your head all the time, so it's not waking the screen until the other person ends call. We need to find out which one is acting up and why.
Click to expand...
Click to collapse
Ok now it seems quick glance DOES work when the phone is off....I just couldn't do it correctly.
Main problem still exists though.
What rom are you using
Sent from my SAMSUNG-SM-N900A using Tapatalk
My note 2 started like this also. I don't know what's wrong with it.
Sent from iNew V3 using Tapatalk
My phone is completely stock and not rooted.
MNDZA said:
My phone is completely stock and not rooted.
Click to expand...
Click to collapse
then i would contact att and get a warrenty replacement
jerrycoffman45 said:
then i would contact att and get a warrenty replacement
Click to expand...
Click to collapse
I was thinking that, but I'm tempted on resetting my phone and seeing if that helps. The problem is that I would lose all my app data and I'd hate to deal with that.
MNDZA said:
I was thinking that, but I'm tempted on resetting my phone and seeing if that helps. The problem is that I would lose all my app data and I'd hate to deal with that.
Click to expand...
Click to collapse
att will ask you to do that when you call
MNDZA said:
When I am in a call, putting the phone to my face turns the screen off using the proximity sensor. However, removing the phone from my face does not turn the screen back on. Nothing turns it back on even if I push all the buttons or hold them or do anything unless the other person hangs up. I cannot remember when it started....before or after the recent update.....but it did start very recently. Any ideas? If I turn off the proximity sensor during calls it works fine by locking and unlocking the screen with the buttons.
Click to expand...
Click to collapse
Unfortunately this sounds like a bad proximity sensor. This can be verified by testing the sensor by dialing *#0*#
I had this happen to my last Note 3. The only difference was I could turn the screen back on with the home button.
done12many2 said:
Unfortunately this sounds like a bad proximity sensor. This can be verified by testing the sensor by dialing *#0*#
I had this happen to my last Note 3. The only difference was I could turn the screen back on with the home button.
Click to expand...
Click to collapse
I tried that *#0*# test and I can activate the proximity sensor, but it seems to stay on after that.
This is a known issue with our phone. I had this issue myself. Plenty of times. Just call ATT and ask for a replacement.
Yeah I just found this:
http://forums.androidcentral.com/sa...-3-proximity-sensor-issue-during-calls-5.html
It's not a software issue use canned air and blow by the speaker and the headphone jack als o press on the back of the phone . This has happened to me
Sent from my SAMSUNG-SM-N900A using xda app-developers app
i stumbled upon this thread and took my phone apart and sure enough there was lint in it. in the dial pad using the *#0*# method, when i covered the sensor the screen would light green, vibrate, and stay that way after i moved my hand away. i cleaned it and everything is perfect!!!
Try this
https://www.youtube.com/watch?v=fls4NIRJ1IQ&feature=youtube_gdata_player
Sent from my Note 3 SM-N900A rooted by Designgears
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.
Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.
quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.
Tried Apex for a day as well. No different than Nova for me.
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.
quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.
AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]
Did Lollipop fix this problem?
quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.
quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal
Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.
pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints
I just updated my LG G4 h811 to the newest build for lineage OS 10 / 24 and tap to wake is no longer working the way it's supposed to only one in about every 20 attempts it will turn on is there any way to fix this or do I have to wait for a new update?
Same here, not sure how to fix it.
demoncamber said:
Same here, not sure how to fix it.
Click to expand...
Click to collapse
I've been looking everywhere and can't find anything to solve it I've even changed to a different ROM CR Droid so I'm not sure what's causing it it may possibly be Hardware but I really doubt it since it was only after an update
i have it to. try KDZ if its same then its a hardware problem. like mine i tried and same for all roms sometimes it turns on inside pocket. very sensitive . sometimes just place my palm in screen and turns on. now it doesnt turn on lol not even tapping 1000 times.
if you have warranty send it to repair. if that is important get another screen.
raptorddd said:
i have it to. try KDZ if its same then its a hardware problem. like mine i tried and same for all roms sometimes it turns on inside pocket. very sensitive . sometimes just place my palm in screen and turns on. now it doesnt turn on lol not even tapping 1000 times.
if you have warranty send it to repair. if that is important get another screen.
Click to expand...
Click to collapse
I remember having this problem on my LG G3 and thinking that a new screen would solve it it turned out to be the processor... Hopefully that's not the case here but sometimes when I use the button to turn on the screen it comes on but extremely dim I have to turn it off and turn it back on again so I'm thinking maybe it is a processor on the G4 as well
virgil1381 said:
I remember having this problem on my LG G3 and thinking that a new screen would solve it it turned out to be the processor... Hopefully that's not the case here but sometimes when I use the button to turn on the screen it comes on but extremely dim I have to turn it off and turn it back on again so I'm thinking maybe it is a processor on the G4 as well
Click to expand...
Click to collapse
well not sure what causes it. but on mine waking it up dont work anymore unless it gets sensitive again... wierd thing is double tap to sleep works everytime. when screen on .. only waking up phone is the problem
raptorddd said:
well not sure what causes it. but on mine waking it up dont work anymore unless it gets sensitive again... wierd thing is double tap to sleep works everytime. when screen on .. only waking up phone is the problem
Click to expand...
Click to collapse
Yes same with mine I can tap to sleep and it works every single time no problems but tap to wake does not work very often sometimes it takes up to 20 tries to get it to work
virgil1381 said:
Yes same with mine I can tap to sleep and it works every single time no problems but tap to wake does not work very often sometimes it takes up to 20 tries to get it to work
Click to expand...
Click to collapse
am afraid its hardware related not software.. i already searched alot and found nothing.
Yeah, I luckily have the insurance, but last time my brother sent his they sent him back a G4 with boot loop issue lmao. So, for right now, I've just been using the power button. As for me, knock to wake, knock code, pull down status bar all doesn't work. Sometimes it will randomly work but tap to sleep works fine.
raptorddd said:
am afraid its hardware related not software.. i already searched alot and found nothing.
Click to expand...
Click to collapse
An app i have been using called KinScreen.
It works by waving your hand over the proximity sensor to turn the screen on. I have been using it a week or so and it doesn't seem to use a lot of battery power. I am using it on LineageOS.
fuzzy_ said:
An app i have been using called KinScreen.
It works by waving your hand over the proximity sensor to turn the screen on. I have been using it a week or so and it doesn't seem to use a lot of battery power. I am using it on LineageOS.
Click to expand...
Click to collapse
I tried that one also but it wakes up when you put it in your pocket and sometimes you end up pocket dialing people
fuzzy_ said:
An app i have been using called KinScreen.
It works by waving your hand over the proximity sensor to turn the screen on. I have been using it a week or so and it doesn't seem to use a lot of battery power. I am using it on LineageOS.
Click to expand...
Click to collapse
sorry am out of thanks button .. yes ive use one not sure if same. back when glaxy S2 skyrocket but it drain battery. and in our G4 battery isnt the best, so i rather use the power button. thanks:good:
I've the same problem since custom ROM(Android-Pie).
Code:
LG-LS991-UsU(ARB2) with h811-nonUsU | RR(v7.0.2) based android_Pie.
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
tomsag said:
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
Click to expand...
Click to collapse
Yep I have the same thing... Today my pocket took 9599295 pictures and movies.. also when I'm a bit sweat my pocket dial random numbers. I've noticed that when screen is touched and disnt recognize fingerprint then whole lockscreen shows up and its easy way to random open dial or camera... Its rly anoying, because I dont want to hide phone screen outside of the skin. (Its easier to break screen if I hit something with my leg.)
Dunno why it doesnt use proximity sensor to recognize that phone is in the pocket like every other brand... :/
Do you have the double tap to wake up activated?
I had this problem a while ago and it was the double tap that played all kinds of tricks calling emergency and taking pictures in my pocket! Disable double tap to wake up screen and the problem goes away.
Disable the fingerprint icon on when the screen if off.
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
tomsag said:
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
Click to expand...
Click to collapse
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
gerhard_wa said:
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
Click to expand...
Click to collapse
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
tomsag said:
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
Click to expand...
Click to collapse
My only solution was to buy a flip case. At first, I disabled the fingerprint reader by removing all fingerprints and setting up face recognition, but this didn’t fix the problem you are talking about. I don’t really like flip cases, but the Nillkin QIN Smartcase is rather good.
So now I ‘m eagerly awaiting a fix from Xiaomi so I can strip the Mi9 again!
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Where can the fingerprint icon be disabled? Thank's.
j4dotcc said:
Where can the fingerprint icon be disabled? Thank's.
Click to expand...
Click to collapse
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
gerhard_wa said:
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
Click to expand...
Click to collapse
Thanks for the prompt reply. I don't have the problem and just wanted to know where I can disable the fingerprint icon. Thanks again.
New uppdate out that include Pocket Mode. MIUI-V10.2.27.0PFAEUXM EEA version.
I use a widget called screen tap to lock or something or another for the double tap to sleep on any launcher. Have been using it for a while across a few phones. However when I got the S10 I just started using face unlock due to this slow and clunky FP sensor.....but I've discovered this issue where double tap to sleep with face unlock on makes the phone immediately wake back up to the lock screen for a second unlike pressing the power button which acts correctly. I tested it out on nova's built in settings without the widget (which I was using on one UI launcher) and it does the same thing so obviously it's some sort of conflict with face unlock and double tap to sleep. Anyone know why?
carnivalrejectq said:
I just started using face unlock due to this slow and clunky FP sensor.....
Click to expand...
Click to collapse
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Ripthulhu said:
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Click to expand...
Click to collapse
Oh, I'm on cricket in the US , so still stuck on 9 (with no hope in sight for 10 lol). I've deleted them and reset them a few times now and idk it's just not as fast as I'm used to with capacitive ones, there's an extra second, even compared to the one in the OnePlus 7t I was using for a few days , it cannot compete. It works a lot better if you press hard and firm I guess, but again I'm not used to that. But yeah idk why it's doing that, did it to me on Nova too if I use double tap to sleep at all it immediately opens back up to the lock screen. I don't think it's looking for my face in that scenario either because it doesn't face unlock when it does it, but it definitely IS happening because of the face unlock because it doesn't happen if I turn it off altogether and use the double tap to sleep......if I press the power button to turn the screen off this does not happen.