Develop Bugs

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to

Your hands are really dirty or really dry. Try moisturizer or something.

Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.

Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.

@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.

I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.

I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.

I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.

My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.

I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus

gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.

I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk

Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...

I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA

I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.

I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0

Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.

TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

Touch screen issues?

Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...

RealEvil_UK said:
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
Click to expand...
Click to collapse
I have same issues with my g4 here in the US.

Unfortunately same here, on a G4, korean model F500S.

I have the same issues on my G4. So probably returning it won't solve it. I notice it the most when I am scrolling in Facebook or web pages I will open a link accidently.

I have the same, occasionally it just won't respond to some taps, i find just pressing the standby on/off button quickly sorts it but it is very annoying.

same here in israel, sometimes do not respond to double tap on lock screen to wake the G4 up
im sure its a software issue, prolly the LP 5.1

Are so you guys using screen protectors? That was the issue for me with g3 and g2.

20degrees said:
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
Click to expand...
Click to collapse
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?

Try...SGS Touchscreen Booster - Google Play Store
I have run into this same problem with my Verizon G4 (VS986). Many of my taps have gone unrecognized.
I did find this.... http://forum.xda-developers.com/g4/help/fix-touch-screen-registering-touches-t3128518
I tested the software that was recommended...and IT WORKED!
Give it a try...can't hurt!

nipun1110 said:
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Click to expand...
Click to collapse
After market but plastic.

Just started to get issues where taps on the far left-hand side of the screen don't work.

blackknightavalon said:
Just started to get issues where taps on the far left-hand side of the screen don't work.
Click to expand...
Click to collapse
Okay, I was able to replicate my bug. It happens after playing a game and stops after some time. Turning autorotate back on and switching back and forth from landscape view fixed it.

Hey guys.
I was searching the forums for a fix that solves the phantom/ghost touches I'm getting frequently on my LG G4, H815 model.
Sorry for the long post but my case looks a little more complex than the ones I've been seen in here.
In my case, that's how it happens:
I receive several multi-touches at the same time, usually when Data is enabled. Sometimes it starts right when I switch from Wi-Fi.
It happens often when I'm driving and using Location+Data as well, which drives me crazy. I does also happens (like another user mentioned in this thread) when scrolling down a feed (such as on Facebook) and it suddenly likes/shares a photo/post. It also drives me crazy! And there is also the case where it taps the keyboard and send crazy typos on chat apps when you are real-time texting someone! Another hassle is right after using the camera and opening the gallery to show someone the taken photo...it suddenly scrolls the gallery and open another photo. I just can't make it to see the taken pic. Therefore, I really wanna fix this so bad since it happens every time I need something right away.
A workaround that's been helping, though it's a pain:
I found that pressing the On/Off button and giving it a few seconds will return it to a normal state. The problem is when it happens while I'm driving and are supposed to take an exit/make a turn at the moment. There are some other cases where I'm into something and giving this few seconds is not an option.
Trying right now:
Someone suggested in this thread to use the SGS Touchscreen Booster. I'm giving it a try right now.
Important notes:
This issue has been happening since I got this phone on November, 2015. We got this 6.0 update recently and I was hoping that it would fix it. It didn't.
I have an after market screen protector that I applied in order to see if the issue would go away. It also didn't.
I have been searching about a digitizer replacement but I don't think is a hardware issue, since it just doesn't happens when I'm only on Wifi at home with Data disabled. I believe that the problem is the Data connection that triggers smth.
Any thoughts?
Does anyone have any idea or have experienced the same scenario before? Any thoughts on my guess of data enabling triggering the ghost touches?
Sorry for the long post and thank you so much for reading it.

I think it's both, its hardware and software, LG tried to fixed it but it makes it worst. You can solve the problem for few seconds putting your five fingers at the home menu, It goes crazy and after it stopped making ****. Anyway this phone is great but all the problems make it ****.

I am going to use this thread even though I think my problem is not as serious as yours are.
My problem is that touches are registered, but no action is taken.
For example. Quickly tapping on an icon on the home screen will highlight it, but it will not open the application. I enabled the option in Developer mode to display the touches and the touch is registered. It's just that the app will not load. If I click for a tad longer - it loads. Happens on both stock Launcher and Action Launcher. I have not noticed it happening outside the launcher.
I read something about a keyboard update, but in the Update Center I don't have anything related to the keyboard.
The icons I see it happening with are located in the lower part of the screen.
I am almost sure that this is a software problem, but several updates have not fixed it. Currently on v20d.
Any suggestions or ideas?

After a few more testing and monitoring, I found out that the ghost touches only take place when I'm on LTE.
And even more weird, while driving through some specific areas when I'm commuting.
It's just so weird to think that some towers may send a LTE signal that may cause the ghost touches.
At home, at work, wifi or data, it doesn't happen.

Touchscreen scrolling and swiping problems?

Is anyone else having issues with what appears to be dead areas when scrolling, swipe texting or otherwise using your phone? In typing this message the phone just lost my finger on 4 occasions. When scrolling webpages it often just stops and clicks an area where my finger was. I'll get occasional double clicking on things when I do try to click. I have trouble purposely replicating my problems but in regular us it is driving me nuts. Because I can't constantly replicate I'm not sure trying to take the phone back will be successful. Anyone else having issues? Could there be something I'm missing somewhere?

Sounds kind of mean but I hope your issue is isolated. I saw the ifixit teardown and the ease with how the digitizer came off of the glass has me worried about the longevity of the digitizer.

Happening to me insanely often on my regular Pixel.

This happens to me occasionally. Sometimes, when typing it spams v and b. If I find anything I will fill you in.

Yes, I'm having this problem with my Pixel. It happens across all apps, even in Settings. Generally it happens if I start scrolling after not touching the screen for a little while.. for example when reading a news article. The scrolling freezes, and I can move my finger around on the screen and it doesn't react, but then it might pick up my finger again and the screen jumps around or clicks on something even though I've not lifted my finger from the screen. I tested it in safe mode and it happens there also. I even got my original device exchanged, and the same thing happened immediately on the new phone. I've been in touch with Google Help this morning and they've confirmed it's a software issue. They've asked me to submit a bug report. It'll help them if more people report the bug though and they have more data to fix it, so if you're experiencing the same issue, please report it! You can chat directly to Google support through settings on your Pixel.

Haven't had any issues but I know the google keyboard can be a bit glitchy at times. I used to have a nexus 6P and I would get weird issues with that keyboard as well on that phone. Getting them less on my Pixel though.

Having issues with typing on my 6P, it's so odd as sometimes I can not type when in desktop mode and sometimes not when in mobile. Switching the webpage screen mode and also doing a soft shut off on the phone and coming back both fix it temporarily. Thought at first using a different keyboard app might help but what app it runs does not solve the problem.

Same problem here. Google pixel

Happening to me as well. Did a factory image flash and it seems to have helped but still happens once in a while. I notice it the most when I'm using reddit sync. Seems to just happen too frequently.

Just an update on this... After doing a few steps suggested by google tech support like, test on safe mode, factory reset using bootloader method, etc... They just replaced my unit. I'm using a new one today and problem is not existent now. I would assume the problem would be hardware.
To be honest, I'm quite happy with their tech support...24/7 support and the staff are really competent. This in my opinion, is worth the high price of the pixel. Good job google!

I have the standard Pixel, and I too had issues with typing (occasionally wrong letters or spaces would register), and dead areas in the top corners of my screen when trying to open apps. I was going to return it one day after confirming that the dead areas at the top of the screen were persistent, but for some reason I decided to grab an App from the bottom of the screen and move it by sliding to the top area. Instantly this cured the dead area issue, even after I moved the app back to the bottom of the screen. It's as if it recalibrated the touch sensitivity vertically as it stopped erroneous spaces when typing too.

Pixel 2 one handed thumb scrolling issue
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.

Newpixel2 said:
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.
Click to expand...
Click to collapse
You should probably post about that in the Pixel 2 forums.

Android 8.1 slow fingerprint reader

Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.

1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.

I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?

To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.

1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly

I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.

Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more

I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.

SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.

sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...

I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck

I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153

Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.

SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.

1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.

Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.

I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon

I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.

jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?

fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here

Pixel 2 XL - Touch sensitivity issues?

Hi there,
So I finally got my beautiful panda Pixel 2 XL and I absolutely love it, except for one thing - touch latency or sensitivity.
UPDATE
If you're having similar issues, be sure to "+1" the following thread on Google forum and also comment: https://productforums.google.com/forum/#!topic/phone-by-google/3XDqX3LgpvQ;context-place=topicsearchin/phone-by-google/category$3Agoogle-pixel-2%7Csort:relevance%7Cspell:false
I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.
I'm not entirely sure what's going on, but basically I feel like I'm having a hard time registering a touch on the first try TOO OFTEN. Sometimes I would even try to scroll up or down a web page and it wouldn't register for a few tries.
Things to note I'm NOT using the screen naked, I'm rocking an AmFilm tempered glass screen protector, it's a dot matrix kind of screen protector, one that doesn't actually stick to the screen entirely, only at the edges. Could this be the issue?
Is anyone else having similar issues with or without a screen protector?
Again, other than that, the device is perfect. Also very minimal blue shift that doesn't bother me at all.
Thanks for your help

How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app

Patch7 said:
How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I know it's silly, but I don't want to take off the screen protector because I got it aligned perfectly and the only replacement I have is a different type - a tpu film.
The thing is, I didn't even have a chance to try out the phone without a protector since this was the first thing I did when I unboxed it :/

Was mainly wondering if anyone else is having touch screen issues with a tempered glass screen protector of any kind?
UPDATE I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.

You on latest 8.1?

I notice some touch sensitivity issues in the far edges of the screen. I'm not using any screen protection at the moment.

galaxys said:
You on latest 8.1?
Click to expand...
Click to collapse
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.

nimrodiny said:
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.
Click to expand...
Click to collapse
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...

galaxys said:
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...
Click to expand...
Click to collapse
Yeah, definitely. I'm already on 0.5 scale unfortunately so this can't be it. Thanks for your help anyways! Appreciate it

Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.

mikepopo99 said:
Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.
Click to expand...
Click to collapse
Agreed. I actually miss my Oneplus 3 in terms of performance and fluidity. I can't type or browse with this phone without having weird glitches. Sometimes the tap wouldn't register, sometimes it's the scrolling acting up.. Very annoying as I said

I'm having similar issues. Randomly my phone decides I touched somewhere in the middle of the screen I didn't at all, or when scrolling down a list eg. YouTube or Twitter, it suddenly jumps me back to the top as if I swiped down at super human speed.
More over the most consistent issues I'm having is tapping on the edge. Eg. The elipsis (3 vertical dots) when looking at 'my channel' or a playlist such as my attached screenshot. I cannot touch the elipsis at all even with a stylist.
My device is Google Pixel 2 XL, 8.1.0, build OPM 1.171019.011
P.S I'm using the phone 'naked', no case, no screen protector.

Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.

It also happens to me, sometimes, while scrolling up or down, 5 or 6 times successively, it doesn't recognizes one of the touches.

nimrodiny said:
Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.
Click to expand...
Click to collapse
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.

I have noticed sometimes it freezes when loadng a web page thought it was chrome but updated to the beta.
Same effect, something is off with the touch sensitivity but not always.

Dav_Edward said:
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.
Click to expand...
Click to collapse
Yep. I can definitely tap on the ellipse on YouTube via my channel.
BTW, just made a scrolling comparison - same website, same browser, on my Pixel 2 XL vs the OP3 and... The OP3 absolutely killed it. It was way smoother and never stuttered while the Pixel had tons of stutters and misreading of my swipes

Thanks for testing Nimrodiny. In that case I best go back to the store and exchange my phone, as edge tapping is definitely broken for me.

Ya. Happens to me.. not acurate touch.. try touching that 3 dots on YouTube app on full screen ( where u change resolution of youtube play back)
Ufff fed up with this.. display, speaker, touch.. how many more

I came from OnePlus 3 n got panda pixel 2 xl. I faced some touch sensitive issue while typing n sometimes browsing. M using my pixel with iq shield screen protector film. I did a factory reset it did helped with swipe issues to some extent. Also I disabled vibration n sound for touch and feel bit better while typing. Mostly while typing I had hard time pressing space bar , most of the time I had to press twice to register a space. lts like phone is unable to keep up with my typing speed(m not that fast though). It doesn't feel like using a flagship phone . I would say touch is good but definitely not great.
Other than that I face no display issues like screen burn in or weird sound issues . Ya blue tint is there but it's part of the display not an issue.
I would suggest try factory reset once n disable sound and vibration on touch and see if it does help some how.