Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.
Related
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Ever since I've updated to 8.1, I've had a strange problem with swiping up to unlock my phone. It doesn't happen every time, but when it does, I have to do a full swipe from the bottom almost to the top of the screen. Here's a video demonstrating this intermittent problem:
https://photos.app.goo.gl/ZA4Gyv9COepsw8aE3
You can see the touches on there showing how I am swiping in a way that normally would have "flung" the screen up and unlocked, but instead I have to do a long swipe up. Anyone else having this problem or have any ideas as to what could fix it?
That's a feature or some **** of 8.1. Gotta swipe up farther to unlock.
I say to everyone, stop using this garbage release. I came back to 8.0. There are so many things which are utterly stupid on 8.1.
ithehappy said:
That's a feature or some **** of 8.1. Gotta swipe up farther to unlock.
I say to everyone, stop using this garbage release. I came back to 8.0. There are so many things which are utterly stupid on 8.1.
Click to expand...
Click to collapse
Dang. so that's really a known "feature" of 8.1?
I've been having issues with touch responsiveness off and on for the last two weeks or so, and I'm wondering if somehow the last security patch could have caused it. Like, I will be typing with the swipe and it will stop halfway through a word and spit out random stuff, or sometimes I have to pull a few times to bring down my notification bar
Everything's ok for me. Are you using a glass protector?
No such issue here either, I don't use a screen protection.
Phazonclash said:
Everything's ok for me. Are you using a glass protector?
Click to expand...
Click to collapse
I am using a glass screen protector, but I've had it since I had the phone
I'm having the same issue. And of course, it's not doing it now as i swipe. Happens more when i type.
CrimsonToker said:
I've been having issues with touch responsiveness off and on for the last two weeks or so, and I'm wondering if somehow the last security patch could have caused it. Like, I will be typing with the swipe and it will stop halfway through a word and spit out random stuff, or sometimes I have to pull a few times to bring down my notification bar
Click to expand...
Click to collapse
Larzzzz82 said:
I'm having the same issue. And of course, it's not doing it now as i swipe. Happens more when i type.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I have noticed something similar. My issues has been like this since I got the phone and upgraded to 8.1. I heard of others also making this complaint after the fist update to 8.1.
For me... When I try to silence a call it will not let me swipe down on the end button. Unlocking can also be a challenge.
Scott said:
For me... When I try to silence a call it will not let me swipe down on the end button. Unlocking can also be a challenge.
Click to expand...
Click to collapse
I use a pattern and sometimes getting to that can be an issue.
The only problem I've noticed, and I'm not positive this is from the OTA, my Gear S3 stopped vibrating and showing notifications from Android Messages. It was literally the day or the day after I took the OTA. But, who knows. All other SMS apps seem to work fine though.
I still haven't unlocked and rooted mine yet, so I'm hoping by doing so maybe this issue will disappear. Lol at least it doesn't seem to be just me. Though I'm glad to have this issue and not one of the other, worse issues I've heard of people having ?
I'm unlocked with root...
I have screen touch issues. Answering or declining a call is frustrating.
I get it still when I try to swipe away a notification or if i'm pulling down the Notification shade to access the quick toggles, it goes up and i gotta pull it down like 4 times to get it to stay
Yeah I've noticed this as well, have issues answering and rejecting calls and typing on the phone the touch screen responsiveness is off. Hopefully they fix this and the battery drain issue in the March update, because you know we wont get an update before March 5th lol. Also noticed my Gear S3 doesn't receive notifications properly anymore, tried factory resetting the watch and the phone and no resolution unfortunately.
I noticed this both on factory 8.1 image AND on DU RC22 Rom.
Once in a great while, usually when playing a game, I have to tap twice to get a recognized touch, especially near the edges.
Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!
Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?
yetiweston said:
Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?
Click to expand...
Click to collapse
everywhere all apps all places
omer919 said:
Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!
Click to expand...
Click to collapse
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
All stock, latest update no unlocked bootloader (EVR-L29)
I disabled all gestures, I dont have a nano memory card, its not app related, it even happens on the notifications tray when I try to reply to someone but the button doesnt work. even when I type there is a delay that make me miss some clicks I have done
omer919 said:
everywhere all apps all places
Click to expand...
Click to collapse
Have you tried a hard reset to see if that fixes it?
yetiweston said:
Have you tried a hard reset to see if that fixes it?
Click to expand...
Click to collapse
yes, from recovery. didnt help
also scrolling is very slow compared to other phones even when scrolling the fastest I can its very slow.
ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
Exactly the same a few times a day on stock or openkirin rr
Sent from my Kirin Treble using Tapatalk
sometimes when I touch with 2 fingers to zoom (for example on a document) it just stays on zoom mode even when I touch with 1 finger (so when I try to move around it will change the size like a 2 fingers gesture).
scrolling is way slower than any other phone I tested, has anyone else noticed that?
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
It's not a screen issue, it's a software issue.
stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
tried both, didnt help.
I thought I was the only one with this issue.
After flashing the Resurrection Remix rom I have never encountered this problem.
I'll be going back to stock soon so I'll see if the problem still exists.
Mine works perfectly. Even with the protective film scratched. Worked perfectly with my previous screen protector, a tempered glass type. I have the chinese EVR-TL00 midnight blue model. Everything stock, no root.
I also have this problem
You're not alone, this is happening to me as well on the EVR-L29. In my experience it is most noticeable when tap typing and a letter I tapped on does not register. Also, once in a while when I tap on an app to open it nothing happens and I'll have to tap it again for it to open. It's a mild annoyance for me, but not to the point of ruining the experience. I'm hoping a future software update addresses this, unless it's hardware related. I love the phone, but this is probably my biggest gripe outside of the possibility of no future upgrades in Huawei's spat with the US.
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.