yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
Turning squeeze for assistant on seems to have fixed my issues for the time being as well. I usually notice it after charging and just charged it for 30 min after enabling squeeze for assistant and touchscreen is currently perfect.
[Google Pixel 2 XL Guides, News, & Discussion] Ferenczy68:
So which one of you guys is going to submit the bug report to LeGoogs? ?
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
I'd give it 24 hours at least since the issue seems to come back randomly.

I (regrettably) just opened up touchscreen test and did some testing and still noticed a few missed taps. After noticing one or two missed taps in chrome. So my touchscreen registration is certainly better but not flawless.

My missed taps seem to happen in the same area - around the "jki" keys on the keyboard, and around the "wes" keys on the keyboard. Same areas I noticed missed taps in safe mode.
[Google Pixel 2 XL Guides, News, & Discussion] Ferenczy68:
8 hrs and counting here, no issues. Maybe your RMA was a good thing. Sounds like you may have a defective display, squeeze gesture notwithstanding...
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
If I go back and toggle squeeze for assistant it starts working again. It seems like a number of things fix it temporarily for me:

- Clearing app preferences

- Clearing app store data

- Uninstalling any app

- Adjusting pointer speed

- Toggling squeeze for assistant

- Reboot

And it seems to always come back after charging.
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
http://www.androidpolice.com/2017/11/11/pixel-2-xl-touchscreens-unresponsive-near-edges-fix-coming/
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
Sorry to keep bumping this thread but question for those who have been following the issue.

Specifically those who see improvement when enabling squeeze for assistant. Do you have the nav bar hidden with immersive mode?
[Google Pixel 2 XL Guides, News, & Discussion] keith.mcintyre26:
I have an immersive mode tile and touch response is fine regardless of immersive mode as long as I have squeeze for assistant active.
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
Are you rooted?
[Google Pixel 2 XL Guides, News, & Discussion] keith.mcintyre26:
Yes but before I was rooted I used adb for the tiles app to get immersive mode.
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
Have you made any changes to your build.prop to enable hardware keys?

What I'm noticing is squeeze for assistant seems to fix the touch screen problems, but when hiding the nav bar through immersive mode which blocks active edge from working, the poor touch registration returns. Regardless of whether the squeeze for assistant is enabled. This is the case on my replacement device as well.

I suspect enabling hardware keys in build.prop may fix it. May test today if I have time.
[Google Pixel 2 XL Guides, News, & Discussion] keith.mcintyre26:
I haven't touched the build.prop.
[Google Pixel 2 XL Guides, News, & Discussion] obsanity:
I have the squeeze function on and touch issues are present without turning the immersive mode on. I don't think it's related to either.

---------- Post added at 10:08 PM ---------- Previous post was at 09:53 PM ----------

I've mostly noticed it on webpages in chrome. Some pages will not register a horizontal swipe and must have at least a 45 angle swipe to start scrolling. Others will register the touch but not start scrolling unless you start moving vertical.

Everything else swipes and registers a touch even with a horizontal swipe.
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
So I believe the touchscreen issues are related in some way to active edge. I'm not sure why or exactly how. It seems when squeeze for assistant is on, there are no issues.

However I was having issues in immersive mode (w/ squeeze enabled). My device is not currently rooted and I've been using Nougat & Oreo quick settings (free) https://play.google.com/store/apps/details?id=it.simonesestito.ntiles and granting secure settings over ADB to expose the immersive mode tile. When hiding ONLY the nav bar I would experience touch screen issues.

I uninstalled that app and switched to tiles by rascarlo ($0.99) to expose immersive mode tile, and strangely enough I was able to hide only the nav bar (same setup) and the touch screen is flawless.

It should be noted I am also using LMT pie control. I suspected any apps that draw over the entire screen may be the culprit but apparently not. Should also be noted I am on 8.0 w/ the Nov security patch.

Is it just chrome? It could be poorly coded web pages. Also, have you setup the assistant?

Again no clue why or how the squeeze function is related but it appears to be in my case. Could be squeeze sensitivity, assistant settings. I have my sensitivity slider in the middle.

Either way I think the best thing to do is keep sharing what works and what doesn't and hopefully it will get fixed down the line by a software patch. I've ruled out hardware- I've already exchanged devices through RMA.
[Google Pixel 2 XL Guides, News, & Discussion] obsanity:
I'm also using tiles for immersive mode switching but it is off when issues with touch show up. Turning immersive mode on doesn't fix the issue.

Interestingly, I have the squeeze option on full hardness because I was getting too many accidental triggers. I'll give it a try with a medium setting. Yes I have the assistant turned on and set up.
[Google Pixel 2 XL Guides, News, & Discussion] zathus:
It would make sense that touch sensitivity issues are related to The Squeeze function because of palm rejection.
[Google Pixel 2 XL Guides, News, & Discussion] r0adki111:
I was having this issue in the bottom right corner. Most noticeably in the xda labs app when trying to press the yellow reply button. I pressed it maybe 20 times sometimes and nothing. Was using custom navigation bar to hide navbar and status bar. I have since edited build.prop to enable hardware keys. Still using custom navigation bar app to hide status bar. Have not had one failed touch since. I have had squeeze for assistant enabled the entire time. I also agree that this problem is somehow related to active edge being enabled/disabled.

I should mention it has been around a week since enabling hardware keys.

Been on 8.1 dp1 for a few weeks now too. I can't comment on whether this happened when on 8.0 I think I opted in to beta the day I received the device.
[Google Pixel 2 XL Guides, News, & Discussion] numerouknow:
I got my device on 16 Nov and started noticing touch responsiveness issues just recently. Read each and every post in this thread.

I majorly have this issue while typing on SwiftKey in Whatsapp. The backspace button doesn't register half the times. Long pressing the backspace generally deletes the whole word but I rarely succeed in deleting the whole word/multiple words in one long press attempt. I'm forced to tap the backspace key multiple times so it registers 50% of the times and deletes a few letters from the word. And like most people have reported, this is pretty random. This doesn't happen all the time.

I tried using the backspace key right now within xda app and it worked flawlessly. Even the long press worked perfectly. I've encountered this only on the lower part of the device, at right and left edges. I've not been able to test this exhaustively to rule out the possibility that it happens in other parts of the display as well.

I am on Nov build, rooted, disabled navbar thru build.prop edit and using LMT pie for navigation. Active Edge has been enabled since initial setup and squeeze sensitivity is set to firm (almost the extreme right end of the bar). I had initially installed SystemUItuner to try immersive mode and to increase the number of quick tiles that appear in 1 row. (I've uninstalled SystemUItuner but strangely the changes I made to the UI persist even after multiple reboots. Though this isn't relevant to the discussion, I'm mentioning it just so everyone knows the exact setup.)

Has anyone experienced this issue out of the box? I've not read any reports of this kind. People who've got a replacement device can probably check if this happens out of the box, just to be sure it's not caused by some app/feature that we enable/disable.

Thanks to everyone making an effort, experimenting, sharing info to help each other and find a fix to this annoying issue. Much appreciated.

PS: People here have already tried enabling/disabling different features of the device in an attempt to narrow down the culprit but in my case, I haven't changed anything and the issue didn't show up even once while posting this long message. In fact, It didn't show up since morning, its been over 4hrs since I last encountered this issue. Suddenly, I'm not able to reproduce it now. I'll see how long it stays this way.
[Google Pixel 2 XL Guides, News, & Discussion] mrcndr82:
I'm exactly experiencing this issue, from first day I received the device: the 15th of November.

I phoned the support ant told me they're aware of the issue and planning to release a fix for it. Hope it's totally a software issue and no hardware.

Pressing backspace is giving me headache also right now :silly:
[Google Pixel 2 XL Guides, News, & Discussion] fearfighters:
So factory resetting has not helped in fixing this issue? That sucks.
[Google Pixel 2 XL Guides, News, & Discussion] fearfighters:
Is your issue completely resolved now? Has it come back?
[Google Pixel 2 XL Guides, News, & Discussion] mrcndr82:
No, i factory resetter my phone but it's still present.

I'm wondering how many users are affected...if it's a software issue, like support claims, everyone should notice it... but seems that some users are not reporting it.
[Google Pixel 2 XL Guides, News, & Discussion] dekciw:
I haven't had a single issue since I installed it.
[Google Pixel 2 XL Guides, News, & Discussion] crowsnestitsupport:
I noticed it on all 3 of the 2 xl's I have used.. telegram and WhatsApp push to talk button in the bottom right corner are a nightmare.. I basically live in those apps and it's driving me nuts. I have 2, 1 personal and 1 for work. Both did it from day 1, right out of the box. I RMA'd the personal one and the replacement is just as bad. Apparently, as has already been stated, it's something that Google should be able to fix with future software updates, and according to Google it's not a bug, but rather to prevent accidental side touches. Whatever it is, it's driving me nuts.. I'm bone stock on both at this point. Waiting for official TWRP before I root.
[Google Pixel 2 XL Guides, News, & Discussion] Ady1976:
I have this issue too, not just at the edge that is being more widely reported but like many in this thread, thought it was me at first, asked in the UK pixel forum no one seem to have the issue but yes this damn thing keeps missing touches randomly! I can't type a text without it missing characters and it not being my fault because i'm 100% positive I pressed the screen, thought I was going insane at first thinking is it me or is it this damn phone! I hope they sort this out or i'm going to have to send this back alone for this fault as I can't live with this keep missing touches, not happened on any other phone I've owned so I don't expect it to happen on an £800+ phone! has everyone here reported this via the phone's support link?
[Google Pixel 2 XL Guides, News, & Discussion] Neverendingxsin:
Apparently a lot of things are "not bugs" and/or "working as intended" when they are in fact issues with the phone.
[Google Pixel 2 XL Guides, News, & Discussion] mrcndr82:
Yes I've your same problem. Many missed touches, it's difficult to type, and also to tap in any edge of the screen. Initially I tried to wait, for a fix via software, than realized that many other people are not complaining about.

So went for an RMA, which is already shipped. My only fear is to receive a unit that's worse than this.

Never had such problems with Samsung, OnePlus, Huawei. It's almost comic that one has to be scared to RMA because the probability to get another faulty device seems high, for sure higher than normal.

The other "comic" thing is that it's my first time I invest 985 Euro for a device....

Hoping for the best, but prepared for the worst.

Let's see...
[Google Pixel 2 XL Guides, News, & Discussion] alyunes:
Oddly, the push to talk works fine in WhatsApp if I click on the input field first as if I was going to type. The keyboard then pops up and push to talk works everytime.
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
how did it go for you?

im having the same issue in the left and right bottom corner - even more severe when having navbar disabled. rest of the screen is fine except perhaps a little bugginess at the left and right edge. since that seems to be software related, can sth specific like "only in corners" be not hardware related?
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
For those of you with more severe touch screen issues with the navigation bar disabled- if you're rooted enabling hardware keys in build.prop seems to fix it.
[Google Pixel 2 XL Guides, News, & Discussion] crowsnestitsupport:
LOL :) I badly want to like the 2 XL. And I do, to some degree. I have had every single nexus and pixel device so far since the Nexus 5. But I just got the OnePlus 5T and I can't get done being impressed with it. Maybe I'll just use it for a while and give Google some more time. Funny that a small company like OnePlus delivers a "better experience" " in some areas" for less money that a giant like google.

---------- Post added at 02:28 PM ---------- Previous post was at 02:22 PM ----------

I found that to work in WhatsApp and Telegram.. Its just annoying because I always forget, so 1 touch on the PTT button, nothing, another touch to bring up the keyboard and then a 3rd touch to actually start recording.. By them I want to bounce the phone off a brick wall :(
[Google Pixel 2 XL Guides, News, & Discussion] dekciw:
Did you guys install the dp2 update? I woke up and had it and I still don't have any issues
[Google Pixel 2 XL Guides, News, & Discussion] numerouknow:
I agree. I re-enabled the navbar thru build.prop edit and the touch responsiveness issues have almost disappeared.

---------- Post added at 05:28 PM ---------- Previous post was at 05:21 PM ----------

I too own a OP5T besides P2XL and I have to admit that its difficult to find fault with 5T. It's an impressive device at an unbeatable price.
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
you guys having the touch issues mostly in the bottom part, too? and there in the corners?
[Google Pixel 2 XL Guides, News, & Discussion] x201s:
I thought i was the only one. Comparing my 2XL with my N5, I noticed some inputs would not register but on my N5 it works just fine. Fingers crossed its software related!
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
manufacturing date? :)
[Google Pixel 2 XL Guides, News, & Discussion] x201s:
10/15
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
I enabled immersive mode by only hiding navigation bar and can pull it by swiping at bottom

No such issue
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
is anyone here on 8.1 and can confirm that touch registration has not only been fixed for the edges but for the whole screen as well?

since i am experiencing some issues over the whole screen where i need to tap a second time to make it count.
[Google Pixel 2 XL Guides, News, & Discussion] r0adki111:
It fixed for me when I enabled hardware keys on build.prop. Was using immersive before and had touch issues. They went away after enabling hardware keys on 8.1. Installed 8.1 dp2 the other day aaannnnd the issue is back.
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
and you had/have them all over the screen occasionally? not only at the edges and corners?
[Google Pixel 2 XL Guides, News, & Discussion] Sudsington:
I had touch issues (multiple taps to recognize input) and scrolling issues. The scrolling issues were scrolling a slight diagonal angle in apps that had a horizontal component (eg Chrome and moving horizontally in a web page, or in Relay for Reddit, where you can swipe back from comments or into the menu) would result in a horizontal scroll when you were trying to scroll vertically.

Oddly, nothing worked to fix this (safe mode, factory reset), until I realized I set up one app to relogin after a reset before testing apps...LastPass. So I turned off accessibility control for LastPass and the issues went away. The only thing I can presume is that the accessibility options are causing some kind of lag or something.

I don't think this is the root of everyone's issues in this thread, but it's one possible troubleshooting step. I'm submitting this same feedback through the Support tab in Settings.
[Google Pixel 2 XL Guides, News, & Discussion] Deeco7:
I'm assuming most of you guys are saying it has been fixed in 8.1 DP2?
[Google Pixel 2 XL Guides, News, & Discussion] fearfighters:
Mine wasn't fixed. On a second pixel atm, seeing if there is this problem.
[Google Pixel 2 XL Guides, News, & Discussion] biffwitch:
I have this issue, whole screen. I think it's sensitivity issues because I believe the phone thinks you are moving your finger when you press or it isn't accurate as if I use a stylus it works with no issues.
[Google Pixel 2 XL Guides, News, & Discussion] ehampshire:
On 2nd Pixel2 XL

I have this issue and it really annoyed me, so I RMA'd my Pixel2 XL (Panda, 128gb). I just got the new phone yesterday, same issue, so now I am really torn about what to do. Since support made me factory reset my og pixel2 I thought I'd try 8.1 DP2. That made it slightly better, but the issue was still there. It just didn't happen as much. I could live with it missing some inputs, but it gets really annoying when scrolling and reading an article (which I do a lot of on my phone). I'm aware of it now that I don't replace my finger and just keep swiping, noting that the phone is ignoring my input entirely.

OG Pixel 2 manufacturer date: 10/26/17

New Pixel 2 manufacturer date: 10/13/17

So, this doesn't seem to be something they can fix entirely with software. What are people doing? I love this phone except for this one annoying thing, tempted to just return it.
[Google Pixel 2 XL Guides, News, & Discussion] Ady1976:
I'm on 8.1 dp2 and it seems typing now is much better without any hitches missed touches, however now it seems they've introduced some scrolling stutter, like a hitch when scrolling, Facebook is a good example of it, some people probably won't notice it but it's the first thing I noticed, it doesn't stutter scroll on 8.0 so if this isn't fixed in the final I'm going back to 8.0
[Google Pixel 2 XL Guides, News, & Discussion] r0adki111:
No, not all over, just on the bottom. I have noticed since dp2 that about halfway up when I click on something, it quite frequently thinks I clicked about a quarter inch higher.

Most noticeable when clicking on a forum thread using chrome. It will actually select the topic 2 or 3 lines up.

For me personally, dp2 has made it worse.
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
In the android authority latest video the person mentioned about the touch latency issue around the edges and said that Google said they will fix it :highfive:
[Google Pixel 2 XL Guides, News, & Discussion] dekciw:
I left the beta cause I saw the thread about 8.1 OTA going out, I didn't get it so I tried to sideload it and it just gets stuck on verifying so hopefully the OTA gets pushed to me soon because it's like night and day between 8.0 and 8.1 dp2 with the touch reg, scrolling, swiping etc issues. Overall 8.1 is significantly better than 8.0 performance wise. I've also noticed in chrome I long press on text to try to copy it and it will copy stuff above what I tried to copy but it depends on the website
[Google Pixel 2 XL Guides, News, & Discussion] Heisenberg420:
Try a different cable. Not sure exactly what the issue is but if IIRC I couldn't sideload (stuck on verifying) with the included Type-C to Type-C OR a 3rd party USB-A 3.1 to Type-C; a USB-A 2.0 to Type-C did work though.
[Google Pixel 2 XL Guides, News, & Discussion] mlin:
Just finished sideloading the OTA. Touch registration issues are fixed. Yay!
[Google Pixel 2 XL Guides, News, & Discussion] nimrodiny:
Hey, just wondering if you're still experiencing these issues?

I'm on 8.1 and having massive scrolling or swiping glitches and random touch registration while scrolling. Super annoying.
[Google Pixel 2 XL Guides, News, & Discussion] ehampshire:
Yup, still have them. 8.1 made it better, but didn't fix it entirely. I'm contemplating another RMA, but haven't felt like going through the hassle. There's a thread on Reddit about it (sorry, won't let me post the link), someone said they still have the issue in 8.1, it's definitely a software thing that Google can fix. I'm just not sure it's on their radar. Also, it seems to me to be a combination of the hardware and the software - some screens are more responsive than others as this isn't a widespread issue that people have all noticed.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If any of you are rooted, you may want to give this a try. I think you'll like the changes :good:

https://xdaforums.com/pixel-2-xl/how-to/fix-touch-screen-issue-t3723717
[Google Pixel 2 XL Guides, News, & Discussion] nimrodiny:
I see. Thanks for answering! It's driving me nuts. I also won't go through the whole RMA process because I don't live in a country where Google has an official store, unfortunately. Can you send me the link to the Reddit thread on a private message please? Did you get in touch with Google regarding this? Did anyone? Thanks again, I appreciate it
[Google Pixel 2 XL Guides, News, & Discussion] ehampshire:
Sent you a private message with the link, will post the rest of the stuff here for others.

Yes, I have filed a bug with Google and so did someone else in that thread. I'm not rooted, but seriously contemplating it to try the steps linked a couple posts up. Aggravating to have to root and do workarounds for a problem like this on a $1000 phone. =(
[Google Pixel 2 XL Guides, News, & Discussion] 水攸月羽:
Confirm this, oreo colorizer set to aggressive make the touch 100% registered. However this will make phone a little bit laggy.

It's my 3rd pixel2, still same behavior, must be software related issue.
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
Do you have the Google assistant squeeze feature disabled? Enabling it fixed the issue for me.
[Google Pixel 2 XL Guides, News, & Discussion] 水攸月羽:
You are right, touch got perfectly registered (even with nav bar disabled in build.prop) after I enabled that.

Actually I didn't turn off any squeeze feature, instead I changed the system language to traditional Chinese and the system automatically disabled squeeze for assistant.
[Google Pixel 2 XL Guides, News, & Discussion] dieselhazza:
You would expect such a problem will be non existent on a pure Android device. To me its more of a hardware issue. If it was software it would be more widespread to other devices/manufacturers. However it is not the case so this can only mean hardware is to blame. I doubt software would fix it
[Google Pixel 2 XL Guides, News, & Discussion] Devhux:
And what other phone is running 8.1?
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
It's not hardware. I can replicate the exact problem without fail. If I turn off squeeze for assistant my touches are only recognised 3 out of 5 times. With squeeze off & Oreo colorizer set to aggressive, no problems. Squeeze on, no problems.

I have no doubt that there are other users with a slightly different problem. i.e. whole areas or edges that never work properly. But in my case, it's definitely software.
[Google Pixel 2 XL Guides, News, & Discussion] dieselhazza:
Haha thats not logical at all. So in order to run 8.1 there should be problems that exist. What a shame to accept something like that. This phone should be close to flawless on the software end. So don't fool yourself