Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Biges said:
Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Click to expand...
Click to collapse
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
hammered58 said:
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
Click to expand...
Click to collapse
Nova Launcher, my favourite app!
Seems like some shortcomings of Pixel 7 can be solved using the root access, however it seems crazy I need to root the phone to get the same functions as on a Samsung or a OnePlus phone :-/
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Yes, it is as you describe. But don't hope too much, this behavior about missing already animated taps had been reported for Pixel 6 by many people, but Google seems to ignore it or what, they just don't give a care?
I encountered this issue in the beginning. Try the following and see if it solves your phone being unresponsive to tapping to unlock the device. Go to: Settings>Display>Lock screen and turn off Lift to check phone, turn on Tap to check phone.
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Hey, same here sometimes. I got a pretty good but cheap tempered glass screen protector with which FP works 8/10 plus using face unlock. Better touch input option with protector is enabled in settings.
The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap ...
Click to expand...
Click to collapse
Exactly this happens more often and I had that on my Pixel 6 too which I replaced with a Realme GT2 Pro (no problems with the Realme) but on Pixel 7 now again. Still using three buttons navigation bar, and often the taps don't work there too.
LOL f* Google, can't they get their stuff fixed? I mean the company which codes the OS sucks regarding their flagships more than other OEMs which only adapt the OS. Jesus f* christ.
Related
I am not sure whether it is my mind playing trick with me or not, but I feel like my phone is less sensitive after I did the hard reset (power+volume down). Sometimes I need to press 2-3 times because the first light tap was not detected.
So is there anyway to increase the sensitivity?
I have the same problem, but no idea that is the hardware or only software problem.....
Fresh owner of this Optimus 2X in France, in our community, frandroid.com, we encounter the same problem , I think this is a software issue.
Did someone already contact LG??
Maybe they should include this into the bug list thread.
May I know were you guys having this problem since it is out of the box? or after reset?
I have the same problem started from day 1 till now
I have the same issue and already thought I'd be the only one having this problem.
I would not say it's a problem with sensitivity, but it feels like the touchscreen goes into some kind of sleepmode where then you need to press a second time, to wake it up.
Continuous touching is no problem. (like when typing rapidly on the keyboard)
This video is not from me, but it shows the problem.
Have a look at 13:28 and 13:37. The reviewer tries to hit the "Ackermann" entry, but the touchscreen does not recognize the touch. At 13:37 the guy has to press another time to get the entry selected.
http://www.youtube.com/watch?v=VRid-Yhu7Gg&feature=player_embedded
Yes! The touchscreen is definitely less sensitive than my old HTC Hero, and gets quite frustrating sometimes when a scroll misses the first part of the movement or a click is missed.
Sent from my LG-P990 using XDA App
just in case, are you guys using 20110218 baseband too?
The same problem here. If I unlock the screen and then tap on any on screen apps, I need to touch again for it to open. Only the first time though, after that it function ok. I think this is a bug and needs to be fixed... I have my pc for double-click.
Yep, count me in. Same problem here. Sometimes screen taps aren't registered. Will do some research later on, but I think it's a software problem. (maybe you have to tap 2x as fast )
Hi,
same problem here!
Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.
9mmBullet said:
Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.
Click to expand...
Click to collapse
I see, then probably they will fix it on the next update/gingerbread?
Same issue here.
Correct me if I'm wrong, but the problem seems to be that the screen has zero tolerance when it comes to tapping and swiping together. If you tap and slide your finger a bit directly after the tap, the tap is ignored. In other words your tap has to be a steady tap when you click on a button or an app. Right on the spot and with no swiping or sliding afterwards. I can't reproduce this on any of my other devices.
Ergo, it seems that the natural tapping I'm used to isn't working on the x2. It seems like I have to adjust my tap. I think that this could in principle be solved with a setting somewhere, because clearly the x2 is capable of registering this in for example a web page.
The great thing of this is that you can safely tap and swipe in the app drawer to scroll up and down or left and right. The downside is that a tap with a little swipe isn't registered at all. I would say that LG has choosen here for a wrong setting.
My personal experience about screen sensivity.. can you confirm if it's the same for your device?
I noticed a strange touch response.. and after some tests, I can say that the touch screen and icons are influenced by the surface where the phone was put!
with the phone in my hands, it's all ok (only sometimes - rare - I need to tap more than once).
If I put the phone over a glass surface (like a glass table) without touching it with both hands, the touch and the icons not respond!! NEVER!
If I put the phone on my scanner the touch screen works ok, but the icons not (or only few and rare taps was detected).!
If I put the phone over my big Onkyo amplifier.. It works like in my hands.. or better!! even without touching with hands.. only with a finger!
Put it back on my glass table.. and all stop working again. If I put a aluminium foil under the phone (between phone and table).. the touch and the icons works again !!
If I put it on the bed.. it don't work.
LG support say that they have tested the phone about this issue after my report.. but no strange response was detected by them. I don't know if they really tested it..
Try it and let me know what you think about!
tested on glass surface, I can press and swipe through pages with a finger without problem.
it is true that my device is not so responsive, but aint reaching that level yet
i read about a similar behaviour on other devices because some devices need a proper grounding for the capacitive screen to work correctly. You can find this problem via google.
Some devices have problem in a car-mounting, for example.
But i think thats not the problem the thread-opener talked about?
Guys I'm looking to get this phone and after reading Engadgets review of the X2 where they mention that the screen is not as sensitive to the touch as other phones I got a bit worried and started googling which lead me here!
Is this true? The screen isn't very sensitive and you have to apply more pressure than other capacitive phones?
I know that the OP is talking about a different issue but I reckon LG will get that sorted out via software update, or at least hope so!
Please do post your experience about the screen sensitivity of the X2 as this is putting me off. I currently have the Motorola Milestone 2 which is very sensitive to the touch even with a screen protector on it.
Cheers
I took delivery of my Z3 Compact yesterday, replacing a Moto G. Lovely phone but I am seeing issues when swiping between home screens, swiping between pages in apps like the dialler, and swiping to unlock. When unlocking for example, it doesn't always work: I see the particle trail following my finger but the phone doesn't register this as a swipe. Sometimes it takes 3 or 4 attempts to unlock. This is odd. Similarly, swiping left/right to switch home screens is hit and miss and the pages often bounce back. It's quite frustrating. Are there any settings that could be affecting this?
Can't confirm this for my Z3C, works as expected. Not sure, but could it be you turned on glove mode in screen settings (though this would make the screen even more sensitive)?
This happened to me a couple of times after enabling Double Tap to wake phone - hasnt happened since
rec71 said:
I took delivery of my Z3 Compact yesterday, replacing a Moto G. Lovely phone but I am seeing issues when swiping between home screens, swiping between pages in apps like the dialler, and swiping to unlock. When unlocking for example, it doesn't always work: I see the particle trail following my finger but the phone doesn't register this as a swipe. Sometimes it takes 3 or 4 attempts to unlock. This is odd. Similarly, swiping left/right to switch home screens is hit and miss and the pages often bounce back. It's quite frustrating. Are there any settings that could be affecting this?
Click to expand...
Click to collapse
I can confirm the swiping to unlock, needs 3 or 4 swipes until it unlocks on mine. I have double tap to wake up checked.
Servaas said:
I can confirm the swiping to unlock, needs 3 or 4 swipes until it unlocks on mine. I have double tap to wake up checked.
Click to expand...
Click to collapse
by chance, do you have any screen protectors or glove mode switched on
Glove mode is off and I dont have a screen protector.
This sounds like what happens with my Xperia Acro S when the display is wet; I can see the visual feedback from the swipe, but it doesn't actually unlock the phone. But I take it your Z3C is completely dry?
I need to swipe the pattern to unlock my phone several times if I use my left hand. With my right hand I only need to swipe once. I wonder if I used my right hand to swipe the pattern originally. No trouble swiping for the rest.
mercje said:
I need to swipe the pattern to unlock my phone several times if I use my left hand. With my right hand I only need to swipe once. I wonder if I used my right hand to swipe the pattern originally. No trouble swiping for the rest.
Click to expand...
Click to collapse
I only seem to have this issue with the PIN entry - for whatever reason, the phone responds quite slowly when entering PIN, to the point I have to wait about half a second between each digit. My Moto G, a much slower phone, responds instantly when entering the PIN digits.
I ended up switching to a pattern that mimicked my PIN entry motions, as the pattern swipe seems to respond properly.
Kind of weird, since the rest of the phone is very snappy and responsive.
I don't have the glove mode on bh5 the screen seems super sensitive, maybe too much. Also in combination with a different phone size than what your hand is used to. This is how I explain some weird swipes. A few times I swiped and the screen moved, then bounced back. I think we probably have to use wider/stronger swipes? I'm sure I'll get used to it. I remember the same thing happened a few days after I got my previous phone. I think it's a matter of getting used to the sensitivity of the screen. I don't think there is something wrong with it.
Sent from my C5503 using XDA Free mobile app
I have the same problem. I even returned my first Z3 compact, but now the second one has the same problem.
When I am using my phone one handed with right hand and swipe with my thumb from left to right pages would oftentimes not turn or bounce back. Occasionally swipe right in is executed even though i just did a normal swipe right.
Swiping in 2 handed mode with my index finger seems to be PERFECTLY alright.
This is REALLY annoying!!! Does anyone have a clue if this is a software or hardware issues? Could the displays be faulty in design or is it something they can repair in a software update.
I am willing to wait for a software update, but if its hardware I'd like to return it right away. I have owned plenty of touchphones over the year, I have never experienced anything like this!
Have any of you who are experiencing the issue used Sony phones before?
I'm not ruling out that there is a problem, but perhaps Sony's UI requires longer/faster swipes than you're used to?
I've not noticed it myself, but I'm coming from a Sony phone previously. May or may not be a factor.
Sent from my LT26i using Tapatalk
Why So Serious? said:
Have any of you who are experiencing the issue used Sony phones before?
I'm not ruling out that there is a problem, but perhaps Sony's UI requires longer/faster swipes than you're used to?
I've not noticed it myself, but I'm coming from a Sony phone previously. May or may not be a factor.
Sent from my LT26i using Tapatalk
Click to expand...
Click to collapse
I have a Sony Z1 compact. No issue whatsover. I have it still here for comparison. I think you will only experience if you swipe in a particular way, while there are some other ways to swipe where the problem is not there at all.
Why So Serious? said:
Have any of you who are experiencing the issue used Sony phones before?
I'm not ruling out that there is a problem, but perhaps Sony's UI requires longer/faster swipes than you're used to?
I've not noticed it myself, but I'm coming from a Sony phone previously. May or may not be a factor.
Sent from my LT26i using Tapatalk
Click to expand...
Click to collapse
Agreed.
Coming from a moto G
Not had an issue with unlock, but I did notice I had to do different swipes when flicking between different panes of the home-screen, no biggie now I think I've adjusted.
https://www.youtube.com/watch?v=B60caaAbz4M&list=UUJ0V12wYDgAnWEZREqe_j-g
I have made a video about the issue.
I'm experiencing the same regarding having to use wider swipes sometimes. As far as the lockscreen goes, I have double tap to wake, and have not yet had an issue unlocking the phone.
I also had the same problem and it seems that it's not a software problem (mine was branded Orange with this problem and also after unbranding the problem remains)
Ichanged it today the new one doesn't have this kind of problem (or very rarely)
OK, I've done some more experiments.
Holding my phone in my left hand and swiping using my right index finger is perfect. It's using my thumb that seems to be the issue: it has a larger surface area so my money is on a software issue.
Also, I enabled Sramina mode and checked "Extended usage" (which lowers the processor speed I think) and it works perfectly! Swiping with my thumb shows no issues.
I'm getting used to it now: it's still annoying but muscle memory is starting to kick in and I'm adjusting my swipes to compensate.
Still odd though but I don't think it's a hardware issue,
Had the Z3 compact for a couple of days and I noticed this issue too. However after messing about holding it various ways I believe it is down to the screen being close to the edge of the body of the phone and with one handed use you inadvertently touch the opposite side to the direction you are swiping with the base of your thumb. Result is when you release your swipe, the unwanted contact sends it the other way.
Try verifying this by using two hands and ensuring no other contact when you swipe. Works fine for me, and I can reproduce the problem with one handed use.
Mine has this issue as well. Sometimes it even happens up to 3 times in a row. Maybe it is related to whether it has dragontrail or gorilla glass? Both are used for the z3c.
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
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Mike20017 said:
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Click to expand...
Click to collapse
what mi8have Home button?
PUBGKING12 said:
what mi8have Home button?
Click to expand...
Click to collapse
I'm talking about the home screen gesture.
Try to test if your screen has some issues, I don't experience any problem
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Crossvxm said:
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Click to expand...
Click to collapse
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
Mike20017 said:
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Click to expand...
Click to collapse
That's very odd. Does the oleophobic coating in that area feel worn or anything? Does the friction feel high? Mine never fails, not even to open the multitasker. Do you have "Double Check for Gestures" enabled? Try turning this off perhaps? The battery drain I definitely agree. I went from 7 hrs of SOT to less than 5.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
ok
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.