Develop Bugs

Touch(screen) stops responding for a few seconds

OK, I'll admit it: I'm a huge fan of Defender 2 game. Downloaded because it was so heavily advertized that my phone suggested it in notification - and played ever since.
Initially, the game played lie a charm, no problems whatsoever. 4.0.2
However, I had some issues with the phone and took it to service a couple of times. After the second time at service, my phone upgraded to 4.0.4 and my troubles with the hame began. I should mention that I'm grateful I had a protective foil because the idiots there managed to seriously scratch it Anyway, the problem:
Every once in a while (2 - 3 games taking 2 - 3 minutes each), the screen just stops responding. My weapon no longer shoots arrows, I can't cast spells, etc, etc. This happens regardless of game time: it can happen during the second game as surely as during the twentieth. Edit: Lasts up to 5 seconds.
However, the non-responsiveness is limited: touch usually stops working on the right (bottom) part of the screen, but still works on the other side (where speaker + front camera are). I have managed to actually observe an instance where the border between working and non-working section was extremely clear at about 1/3 - 2/3 split. Moving my finger in and out of this zone would make the game start shooting arrows again or stop doing it, depending on the zone I moved my finger into.
Perhaps I should also mention that the phone heats up quite a bit during gameplay. However I'm not so sure it should be a factor since the unresponsiveness can happen even right after I start playing. But perhaps that's also a factor to consider?
Anyway - anyone else having these issues or someone that can explain what I'm experiencing?

I started having the same issue yesterday morning as well - except it seems to be ALL the time. The bottom 1/3 of the screen doesn't respond to touch about 50% of the time. Typing is virtually impossible and every touch must be made deliberately and repeatedly. I downloaded a multitouch test and it was quite obvious where the division was between responsive and un-responsive.
I'm rooted on 4.1.1 with stock everything. I restored to my previous nandroid backup from a week ago but still had the problem. Definitely seems like hardware now.
I really don't want to have to buy a third Nexus...

Funny: I just flashed minco ROM which has Francisco's kernel and this doesn't happen any more. Played some 20 rounds so far so I can't say for sure yet, but it seems this rom solves the issue where stock and some others didn't

Latest update: the minco ROM does help, but it does not solve the issue.
I will try to escalate this to Francisco, perhaps (look, I'm an optimist, OK? ) he'll be inclined to look into the issue. Seems to be something few people are aware of. I imagine there aren't many games where one has a fingen onscreen all the time...

A lot of people are experiencing this problem (including me). I'm pretty sure its a software issue. Mine started after I updated my phone from ICS 4.0.2 to 4.0.4...and with jelly bean. I would love for some one to find and correct this issue.
Sent from my Galaxy Nexus using xda app-developers app

Yes, me too - moving from 4.0.2 to .4 seems to be when they introduced the problem. Don't know about lot of people though: searching yielded almost nothing.

[Q] Nexus 7 owners...... problems, fixed or not?

Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.

I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4

Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.

Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:

I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.

madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.

I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app

GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.

Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app

sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!

Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.

New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2

Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.

Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4

To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"

My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4

Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.

I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app

madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates

sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.

Phone is now starting to exhibit glitches/problems

So I've had my XL2 for almost a month - original was RMA'd due to poor quality display at the beginning of the month. Anyways, everything has been great up to about the last 3-4 days. In that time I've noticed the following:
1. Phone would not stay on LTE. Only HSPA+ despite 3 other people(who were with me) with the same carrier all having LTE service all day. I restarted my phone 2 times. Toggled airplane mode several time. It only grabbed LTE for a few minutes then reverted back to HSPA+ when I would turn off cellular.
2. Android Auto. My vehicle detects the phone, in-car application launches, but either there is no sound from any song or when I hit play, song is automatically paused everytime. I have to unplug/plug phone for it to all start working. This doesn't happen everytime, but it's done this about a half dozen or so times now.
3. Last but by the far the most annoying and worst. Randomly, when I'm interacting with the Google keyboard or Swiftkey, the phone just starts to spaz out. Random apps open, incorrect text being entered(for example, I type "m" and instead "z" and 3 commas get entered in instead, and just total loss of control on the phone(can't keep anything open or incorrect actions happen).
So I'm the point where either I go for a factory reset(I hate doing this) or I contact support and see about getting an RMA.
FYI: I'm on the November update.

Went through 2 really blue displays to get what I thought was a keeper yesterday, my 3rd device. But now today I noticed the screen flashes bright white when going into always on display. Quality control must be non existent between Google & LG.

It's just unbelievable to me that a $1000 device is so poorly made or passed off as ready to be sold. I've been sticking up for Google during most of the screen blue shift fiasco, but after this last string of incidents, I'm losing faith completely. This is especially apparent when I see that my wife's iPhone X has had nothing to this magnitude.

I've been having major, major problems with SwiftKey myself, to the point where I no longer even want to use this phone until the situation is resolved.
Everything was fine, even on the beta, and then suddenly about a week or so ago - as you mention - SwiftKey just starts going nuts. Incorrect predictions, mistaken input, slow/lag, etc.
I wonder if it's something with the November Security Patch Update or SwiftKey's cloud network or what.

TokyoGuy said:
I've been having major, major problems with SwiftKey myself, to the point where I no longer even want to use this phone until the situation is resolved.
Everything was fine, even on the beta, and then suddenly about a week or so ago - as you mention - SwiftKey just starts going nuts. Incorrect predictions, mistaken input, slow/lag, etc.
I wonder if it's something with the November Security Patch Update or SwiftKey's cloud network or what.
Click to expand...
Click to collapse
Im using an older version of swiftkey without a hiccup

onishchuk4 said:
So I've had my XL2 for almost a month - original was RMA'd due to poor quality display at the beginning of the month. Anyways, everything has been great up to about the last 3-4 days. In that time I've noticed the following:
1. Phone would not stay on LTE. Only HSPA+ despite 3 other people(who were with me) with the same carrier all having LTE service all day. I restarted my phone 2 times. Toggled airplane mode several time. It only grabbed LTE for a few minutes then reverted back to HSPA+ when I would turn off cellular.
2. Android Auto. My vehicle detects the phone, in-car application launches, but either there is no sound from any song or when I hit play, song is automatically paused everytime. I have to unplug/plug phone for it to all start working. This doesn't happen everytime, but it's done this about a half dozen or so times now.
3. Last but by the far the most annoying and worst. Randomly, when I'm interacting with the Google keyboard or Swiftkey, the phone just starts to spaz out. Random apps open, incorrect text being entered(for example, I type "m" and instead "z" and 3 commas get entered in instead, and just total loss of control on the phone(can't keep anything open or incorrect actions happen).
So I'm the point where either I go for a factory reset(I hate doing this) or I contact support and see about getting an RMA.
FYI: I'm on the November update.
Click to expand...
Click to collapse
Seeing as you have to start from scratch anyway, I'd try a factory reset first. You can always RMA it if the problem persists. Why risk losing your "good" Pixel 2 XL for one that may have a crummy screen restarting the RMA cycle?
Also, was Swiftkey recently updated, like in the last 4 days or so?

mlin said:
Seeing as you have to start from scratch anyway, I'd try a factory reset first. You can always RMA it if the problem persists. Why risk losing your "good" Pixel 2 XL for one that may have a crummy screen restarting the RMA cycle?
Also, was Swiftkey recently updated, like in the last 4 days or so?
Click to expand...
Click to collapse
The RMA is a little better than the previous one in terms of how extreme the shift is, but overall it's not anything worth keeping. The bottom firing speaker buzzes like you wouldn't believe at 60% or higher volume. I don't recall the original one doing this although I did read in another thread that pretty much every phone is doing this.
If the replacement is worse, I'll send it back. It's not like it's a hassle for me. It's pretty much the same doing a factory reset.
Sent from my Pixel 2 XL using Tapatalk

onishchuk4 said:
The RMA is a little better than the previous one in terms of how extreme the shift is, but overall it's not anything worth keeping. The bottom firing speaker buzzes like you wouldn't believe at 60% or higher volume. I don't recall the original one doing this although I did read in another thread that pretty much every phone is doing this.
If the replacement is worse, I'll send it back. It's not like it's a hassle for me. It's pretty much the same doing a factory reset.
Click to expand...
Click to collapse
So, I guess the answer you wanted to hear for your either or situation is do an RMA... Good luck with it.

mlin said:
So, I guess the answer you wanted to hear for your either or situation is do an RMA... Good luck with it.
Click to expand...
Click to collapse
I pretty much wanted to hear if anyone else is seeing these issues. Also, this replacement that I have now is a mid October build.
Sent from my Pixel 2 XL using Tapatalk

Ghost Quick Scrolls, 8.1 issue?

Hi all,
I have recently been noticing ghost scrolls, where I would be slowly scrolling downwards, say, in the XDA app or reddit app, and randomly it would scroll quickly upwards when I lift my fingers. I was thinking this was a hardware issue so I got a replacement device on the way. However, I saw this https://www.reddit.com/r/GooglePixel/comments/7rczu2/scrolling_up_when_scrolling_down/.
Has anyone else been experiencing the same thing? I posted a vid and pic https://imgur.com/a/ny8fT. The second pic is touch input trace enabled in developer options, you can see there was a ghost long fast drag down to the bottom below the navbar.
Have been away from XDA for a while, please let me know if I am going against any rules about posting images hosted on other sites.

I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk

Devhux said:
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
yep, thats happened to me a few times before as well. Not twitter specifically, but in reddit I would click on a post, and somehow I would end up on some random other post like 2 post below it, and if I hit back once, I get to the post I originally intended to click on instead of the subreddit list.
So there must be some sort of ghost touches/scrolls on finger release, causing the unintended post to be queued up just before the intended one.
I'm surprised there hasn't been more people bringing up this issue (assuming this is indeed a software 8.1 issue and not an isolated issue in the touch panel).

Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk

Devhux said:
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.

ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it

elliwigy said:
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
Click to expand...
Click to collapse
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.

ethantarheels123 said:
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
Click to expand...
Click to collapse
prolly 8.1.. i got mine around december late nov. pretty sure its software related.. they had an issue with touch on the lockscreen right?

It seems like so many touch issues with 8.1 release. For this reason, I am still using 8.0.
https://productforums.google.com/forum/#!msg/phone-by-google/FfzV1578L8Q/1HcWw3CCAQAJ
https://issuetracker.google.com/issues/70344455

ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...

ayoraider07 said:
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
Click to expand...
Click to collapse
Replacement device has the same issue, so this is definitely a software bug. Hopefully Google fixes it soon in the next patch update.

Nexus 6P here. I started getting these ghost touches with the last security update. 8.1 is the problem, not a solution.

My mom has the same issue of touch on places she doesn't touch, on Pixel XL.
Could it be the same?
Here is a video about it that I took, just by scrolling in the settings screen:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
It's a bit hard to reproduce, but it occurs eventually.
Has anyone tried to use Android P, and see if it helps?
Anyway, I've reported about this here too:
https://forum.xda-developers.com/pi...h-pixel-xl-t3807188/post76879468#post76879468

Any fixes yet?
I know this is old, but I wanted to know if anyone found a fix for this. I eventually found an Oreo 8.1 Rom that I like and this is the only issue that's bothering me.

Touchscreen issue (PLEASE VOTE)

Please vote, lets see how many user has this problem. (I know the Q/A topic contains similar topic but w/o voting)

My problem is similar. Yes when I pinch or zoom with two fingers it gets a little wonky but nit too terrible. My issue is with the setting "accidental touch" not working. My screen keeps turning on when in my pocket. Tired of companies putting out buggy defective JUNK!

As much I'd like to get this phone seeing so many people have this issue is stopping me from buying it. Guess I'll have to wait for samsung to address that they're putting out a fix for this.

After I put a tempered glass screen protector on it I've had no issues. They have pushed an update to the FE in Germany to address the issue but it's not pushed in the US yet.

teegale said:
After I put a tempered glass screen protector on it I've had no issues. They have pushed an update to the FE in Germany to address the issue but it's not pushed in the US yet.
Click to expand...
Click to collapse
I am glad you don't have the issue, because not everyone has it. Actually, I have put the latest DBT (Germany) latest firmware version on the phone a few hours after it was available, but unfortunately, it has NOT solved the issue, as I described it in this video.

carlosmeldano said:
I am glad you don't have the issue, because not everyone has it. Actually, I have put the latest DBT (Germany) latest firmware version on the phone a few hours after it was available, but unfortunately, it has NOT solved the issue, as I described it in this video.
Click to expand...
Click to collapse
Just tried that test. I guess I do have it but have never noticed it.

Unbelievable i also have issue with my Australian s20 fe, did not noticed this until I run the touch screen test. Unfortunately I have not received any updates firmware yet to see if Samsung fix them or not.

I had this issue too but with 1ATJ5 update which i received 2 days ago the problem solved

I'm surprised what take Samsung so long to release the updates to the rest of the world when its clear the problem happen to a lot of regions.

I have had too Multitouch issues. I have it returned. I have Pixel 5 now.
Was S20 Fe 5G red DE region.

I just bought US t-mobile model and I do have the crossing lines in that blue screen test app. However I haven't experienced any issues in my day-to-day use.

I have the Exynos version with november patch here in Brazil, the issue is present.
Fast catch in PoGo is a nightmare since we need to use 2 fingers to do it.

Exynos with latest patch, no issues on normal usage, only a few crossing lines on the test app.

Just ordered the FE 5G (Snapdragon).
Will update it and run some tests. Should be here in a week.
Hopefully they fixed it or will fix it with Android 11/OneUI 3.0

Is it really a software issue that can be fixed or Samsung just trying to cover it up?

Bl4cK_Pho3niX said:
Is it really a software issue that can be fixed or Samsung just trying to cover it up?
Click to expand...
Click to collapse
I saw some posts on reddit that claimed it was fixed with the latest software but I don't know how true that is as I haven't tried it myself yet.
Hopefully it's something that can be fixed via software. I've gone through PLENTY of Samsung devices and the hardware is always of good quality, even on their lower end devices.

I very recently got the Exynos version, CSC is SEB, ran touchscreen tests, no problems at all.

I don't know if it's touchscreen related or maybe screenprotector that i applied, but after using this phone for a bit more I notice that sometimes it doesn't register my touches. For example in pogo when I spin a ball suddenly it stops tracking as if i lifted my finger and yeets the ball somewhere to the side. Similar with HP:WU, sometimes it doesn't track my casts. :/

mxxcon said:
I don't know if it's touchscreen related or maybe screenprotector that i applied, but after using this phone for a bit more I notice that sometimes it doesn't register my touches. For example in pogo when I spin a ball suddenly it stops tracking as if i lifted my finger and yeets the ball somewhere to the side. Similar with HP:WU, sometimes it doesn't track my casts. :/
Click to expand...
Click to collapse
Did you you enable increased sensitivity?
My Note 10+ be a mess if I wasn't using that and accidental touch protection. If you're running Pie you can also download the app Double Tap which works great with almost zero battery usage.
The case also makes a big difference as naked I hate this phone; in the Bolt case it's great and it helps to prevent accidental screen touches while making it easy to hold.
Don't be too hasty to ditch Pie for Q... Pie is a fast, stable and a relatively secure OS.
With Q comes the cursed scoped storage.
Make sure to cure isn't worse than the disease.

blackhawk said:
Did you you enable increased sensitivity?
My Note 10+ be a mess if I wasn't using that and accidental touch protection.
Click to expand...
Click to collapse
Yes, I tried both in all combinations.
blackhawk said:
If you're running Pie you can also download the app Double Tap which works great with almost zero battery usage.
The case also makes a big difference as naked I hate this phone; in the Bolt case it's great and it helps to prevent accidental screen touches while making it easy to hold.
Don't be too hasty to ditch Pie for Q... Pie is a fast, stable and a relatively secure OS.
With Q comes the cursed scoped storage.
Make sure to cure isn't worse than the disease.
Click to expand...
Click to collapse
This phone never shipped with Android 9 so irrelevant.
And the problem is not accidental touches. The problem is it stops tracking.