Related
Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.
Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.
gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.
Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.
Does anyone else use the smart lock based on location and get inconsistent behavior? I work from home, so I spend about 90% of my time here. I set up smart lock for the location. Sometimes, it works like a champ. Other times, not so much. I've currently been "at home" for the past 14 hours or so, but it keeps insisting on a fingerprint or pin. It's making me crazy.
If anyone has found a solution to this issue, I'd appreciate it.
Oh, also, a reboot doesn't help. I really wish they had added wifi network as an option.
I'm seeing the same issues.
It seems to me that it is working after using Google Maps and clicking on the button to locate my position.
I think it helps if wifi is on and google location history is on, along with high accuracy locations.
my wifi is always on and locations are set to high accuracy with history on and it still finds a way to mess up
every time its happening i clear google location history, clear maps cache and data then open map again to check then its right
happening almost always once week
i may try to factory reset but have to wait till weekend, so i have time in case something get out of whack
This happened to me yesterday. I was home but it kept trying to ask for my pin. It turns out my pinned home location in the smart lock setting was turned off. You can manually edit the location and turn it on/off, which I found out yesterday.
My experience with location based smart lock has been bad across three different andriod devices.
Using the Bluetooth smartlock with my gear s2 has been flawless though.
Was happening to me to. Here's what I did yesterday and seems to have fixed it..
Go into the smart lock settings and delete/remove all saved locations, devices, etc. Now back all the way out and go back and add everything back. A reboot might help afterwards also.
Sent from my SM-G955U using Tapatalk
I turned that crap off. For that reason as well on the s7e. Imediately turned it off on the s8+. Same issues with the app IFTTT and recipes, sometimes it works and sometimes it wont.
I have had nothing but difficulty with it also. Going to turn it off and try the Bluetooth paired with smartwatch.
flu13 said:
Does anyone else use the smart lock based on location and get inconsistent behavior? I work from home, so I spend about 90% of my time here. I set up smart lock for the location. Sometimes, it works like a champ. Other times, not so much. I've currently been "at home" for the past 14 hours or so, but it keeps insisting on a fingerprint or pin. It's making me crazy.
If anyone has found a solution to this issue, I'd appreciate it.
Oh, also, a reboot doesn't help. I really wish they had added wifi network as an option.
Click to expand...
Click to collapse
I solved it on my phone. I switched off every other SMART lock feature and just left Trusted Places on. Been working for over a day now after having not worked at all for 3 or 4 months.
Obviously one of the other Smart Lock features - voice, trusted devices or on-body detection is interfering with trusted places, but not sure which one at this stage.
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
Just a sharing of personal experience. I got my essential white from amazon few days ago and was upset why the phone frequent lockup and touch issue. My phone installed November OTP but still suffering the issue. The hell gone after I done a simple trick by disabling fingerprint gesture. This is a vast difference and everything become perfect now.
Guess I'm not the only one then. Mine locks up about once a day. 3 times the first day. I read somewhere that turning off the fingerprint gesture helps. For me it was less frequent lockup. Hope they fix this soon. May try the oreo beta and see if that helps
jybsze said:
Just a sharing of personal experience. I got my essential white from amazon few days ago and was upset why the phone frequent lockup and touch issue. My phone installed November OTP but still suffering the issue. The hell gone after I done a simple trick by disabling fingerprint gesture. This is a vast difference and everything become perfect now.
Click to expand...
Click to collapse
Where do you turn that off?
Mania626 said:
Where do you turn that off?
Click to expand...
Click to collapse
Setting > Gesture > Swipe for notification
jybsze said:
Setting > Gesture > Swipe for notification
Click to expand...
Click to collapse
Forgot to tell you ,I'm using oreo
In Oreo you can turn off swipe for notifications somewhere in the Notifications section of your settings. I can't recall exactly where but poke around and you'll find it, it's a few levels deep though.
I was having issues with the newest Nougat update. It seems after a couple of hours. The phone would slow down quite a bit. I don't know how aggressive the memory management is so I enabled this in development options.
It's so much better after this! I hope essential fixes memory management of the next update.
This is one hell of a issue that I've never read about online but somehow I'm experiencing.
To make a long story short, a few months ago I bought a OnePlus 6T, after some heavy modding something went wrong and had to hard reset. For some reason, haptic feedback stopped working and never turned back one. Since I was still within the two months that Amazon warrants during christmas season, I asked for a refund and bought another OnePlus 6T of a different colour from a different store (for a much lesser price). Even the new OnePlus 6T had an issue with haptic feedback, when I first turned the phone on, during the setup, the haptic was there, but then after logging in in my Google account (which of course happens pretty early in the setup) again it stopped working.
It is NOT an hardware issue, becuase the feedback works when I receive notifications or a call, but it doesn't work when typing on the keyboard or while navigating the system (or even when I move the slider to vibration which should emit a light feedback).
Since I was tired of asking for a refund, I just kept the phone as is.
Fast forward a few months and today I pick up my new, beautiful and amazing, OnePlus 7 Pro and guess what... THE ISSUE IS STILL THERE.
The haptic was working fine while first setting up the phone, but after the Google log-in, now once again it only works with notifications and not with the keyboard (I tried both Google Keyboard and Swift key) or the alert slider.
YES, vibration is turned ON in the setting.
NO, the phone is not in battery saving mode.
YES, i've tried rebooting a few times
Anyone has any idea why the hell this keeps happening to me and how I could fix it?
Did you try turning on haptic feedback in the Gboard settings?
Dr. Krieger said:
This is one hell of a issue that I've never read about online but somehow I'm experiencing.
To make a long story short, a few months ago I bought a OnePlus 6T, after some heavy modding something went wrong and had to hard reset. For some reason, haptic feedback stopped working and never turned back one. Since I was still within the two months that Amazon warrants during christmas season, I asked for a refund and bought another OnePlus 6T of a different colour from a different store (for a much lesser price). Even the new OnePlus 6T had an issue with haptic feedback, when I first turned the phone on, during the setup, the haptic was there, but then after logging in in my Google account (which of course happens pretty early in the setup) again it stopped working.
It is NOT an hardware issue, becuase the feedback works when I receive notifications or a call, but it doesn't work when typing on the keyboard or while navigating the system (or even when I move the slider to vibration which should emit a light feedback).
Since I was tired of asking for a refund, I just kept the phone as is.
Fast forward a few months and today I pick up my new, beautiful and amazing, OnePlus 7 Pro and guess what... THE ISSUE IS STILL THERE.
The haptic was working fine while first setting up the phone, but after the Google log-in, now once again it only works with notifications and not with the keyboard (I tried both Google Keyboard and Swift key) or the alert slider.
YES, vibration is turned ON in the setting.
NO, the phone is not in battery saving mode.
YES, i've tried rebooting a few times
Anyone has any idea why the hell this keeps happening to me and how I could fix it?
Click to expand...
Click to collapse
Settings, System, Accessibility, Vibration, Touch Vibration [On]
dynospectrum said:
Settings, System, Accessibility, Vibration, Touch Vibration [On]
Click to expand...
Click to collapse
I had a haptic feedback issue with my Huawei P30. Haptic feedback setting was switched on in Gboard settings but it wasn't providing any haptic feedback in the actual keyboard. Turns out I had to go to Settings-->Sounds-->More sound settings and turn "Vibrate on touch" on. I think you might have already tried something like this but it seems like there's a system-level switch that overrides app-level haptic feedback settings.
If it doesn't work, try using a different launcher like Nova and see if it works. It might be able to override some system-level haptic feedback setting on your phone.
Galaxy note 10+ 5g here, tried all suggestions I found with the keywords I searched. If anyone has fixed this or has any insight, I'd appreciate hearing your experience.
My solution was to disable accessibility feature "Select to read". After I disabled it haptic feedback was working again.
Try to disable any of your accessibility features.