yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] oneWAYup7:
I just flashed this (TS10). I've tested it with YAMTT (Yet Another MultiTouch Test) and so far after multiple tests only blue and red colors appear which is good because if anyone is familiar with this app it shows other colors such as green when it detects more than two touches. When I had the issue I would touch with my two thumbs only to see 1 or 2 more touches (colors) appear randomly in any part of the screen.

This has been a very frustrating flaw for me to deal with because it basically breaks at least 50% of your tablet's use. I was ready to give up on my tablet until I found this. Thank you for sharing this fix with us, hopefully it will not break again. You've saved the use of this tablet for me now.

Thank you, sfhub. Really helpful.

UPDATE: After trying it all day all was well until the night when it just started acting up again, so I guess the fix was only temporary. I will try the other two files later on today and hopefully they will work, otherwise I'm done with it.

Nexus 7 2013 WIFI. ROM: Slim-4.4.4.

---------- Post added at 03:33 PM ---------- Previous post was at 03:23 PM ----------

The shame is really for everyone that bought it and HAVE this issue. I'm sorry, I respect your opinion but this is a very real issue. I absolutely love this tablet, best I've owned, but a person cannot cover such obvious and troublesome flaw just saying that it hasn't affected them.

If yours is fine, awesome. But I personally have seen how bad this issue is.
[Nexus 7 (2013) General] mindmajick:
I'm not saying it's not an issue for some people. It obviously is. I'm just saying that it's not as common as it may seem to a casual observer.

I've also seen a number of people call this device a "piece of crap" because of manufacturing variations. That's what i was responding to. The complaints are valid... I'm just not sure why you wouldn't just exchange the device.

I think the OP said it best.... But much of the content of this thread has devolved into insulting the device.

--> Sent from my mind to your screen
[Nexus 7 (2013) General] sam298:
To check what version you installed, see post #1145
[Nexus 7 (2013) General] Sotodeshi:
Seems to be working

Stock 4.4.4 KTU84P

Had couple blind spots. Sometimes i had to press couple of times for the panel to register the touch or press harder (finger got flattened under the preasure and creates a larger touch surface. Probably screen recognised a nearby touch point.)

TS10 Helped

Thank You.

UPDATE:

Ok after a while it occured TS10 created a "crazy point" in the middle upperish area of the screen. When u try to press it screen starts to register multiple random touches along the middle vertical line. Now testing TS11 and YAMTT was showing occasional glitch on the right upperish border. After few reboots seems stable.
[Nexus 7 (2013) General] dr.m0x:
The first fix worked wonderfully for me, many thanks op. Still get some lag in the Swype keyboard but I think that's an issue with the keyboard itself.
[Nexus 7 (2013) General] UnionBlvd:
Is there a way to tell from within Android if this fix has actually been applied? Each file causes the screen to go bonkers after boot - it's a blue/cyan background with random black and green lines. Android seems to boot up in the background as it eventually starts responding to ADB commands, but so far I've tried ts10, ts11, and ts20 and the screen still goes crazy with multi-touch after some time.

I'm running the latest CM11 monthly snapshot if that makes any difference.
[Nexus 7 (2013) General] kicsrules:
i haven´t been able to make it work continously, its always like a temp fix, i´ve tried all ts imgs :/

im willing to solder a ground (if its grounding issues) the only thing is that i dont know where to start
[Nexus 7 (2013) General] UnionBlvd:
My mostly-uneducated guess is that most (all?) of these touchscreen problems are because of shoddy hardware, and changing the firmware is just an attempt to band-aid the issue.

I understand Asus had to cut some corners to make a tablet that offers this blend of capability and affordability, but the sole method of interacting with the device should not have been one of them. It's sad that the Kindle Fire I picked up for under 60 bucks can have a rock-solid touchscreen while my N7 costing more than triple that amount goes haywire half the time when I use more than one finger.
[Nexus 7 (2013) General] kicsrules:
what i´ve notices is that no matter if its only one finger in the screen, suddenly goes crazy, a lot of finger touches show up in the screen (i have enabled the visual feedback for touches) its usually on the right side of the screen (portrait mode)

:/
[Nexus 7 (2013) General] Persechini:
after flashing boot-ts10-lock.img on my N7 I don't think I've encountered this problem again more than once. I don't know if ghost touches show up if you enable touch tracing in developer options, but I can touch on the screen with 5 fingers and it registers all of them correctly. Previously I had a few issues where the notification shade would flickr as if I was touching the upper edge of the screen
[Nexus 7 (2013) General] Az-one786:
Mine also has this issues but not too bad.. It only happen when my screen is off about 2-3 hour.. When I turn the screen on, it seem not responding at all even the lockscreen can't be unlock.. It freeze and I need to turn off screen and turn on again to get it working again... No ghost touch issue..

My build date is March 2014..
[Nexus 7 (2013) General] demol3:
I have mainly use my nexus to play clash of clan and reading mangas. So it have been at most 4 fingers for me. The touch screen failed on me while I'm still in stock rom and had to root it to try fixing the problems. But it all seem futile now as I have tested everything I can ( even opened the back cover and re-secure the connectors). Testing EMI is just one way of showing the problem.
[Nexus 7 (2013) General] LemonPlusTea:
I've tried flashing almost every file, but my touch screen issue doesn't seem to get better. The touchscreen is fine when in most of the screen, cept for one part where it doesnt register at all. Any ideas?
[Nexus 7 (2013) General] player911:
You like playing frisbee?

Seriously I think this might be a hardware issue. My LG G2 did the same thing one weekend where it developed a gap. Seems the gap was right around the buttons, like a button was pressing on a portion of the screen and causing it to do the exact same thing. I just called in a swap through Verizon (next day replacement).

Depending on when you bought this, it still may be under manufacture warranty.

It is so sad because the N7 2013 is a super sweet device but the touchscreen issues make it so aggravating to use. It is even more useless and slow with Android L on it. Hopefully tomorrow when they announce Android L (hopefully tomorrow), we will get an official update that works better. If not I'll probably sell it at a loss and buy a different tablet. Maybe a Shield or Nexus 6. At this point I'm pretty leery of the Nexus tablet line. The 2012 Nexus had issues (including early touchscreen issues). The 2013 would be flawless if it weren't for the grounding/touchscreen flaw, which affects every single Nexus 7 2013 I've owned (7) and tested on (40+).

I'd really think I want a nice tablet, with a pen, and cellular LTE that works on Verizon.
[Nexus 7 (2013) General] AndyYan:
G2's screen issue is largely a hardware problem and is very widespread. Back in our own forums in China, everyday new reports of "screen gap" pop up at a consistent rate. The bad thing is that the issue applies to all versions of G2 - int'l, US, South Korean, and even JP's ISAI are all shown to have it. Best way round is a replacement and use better quality chargers.

I haven't seen large scale reports like this for Nexus 7 (other than my own), so I think it might be an individual hardware problem.

Sent from Google Nexus 4 @ CM11

[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
[Nexus 7 (2013) General] LemonPlusTea:
well, I'm outta luck. Bought this unit last year in August(?) or september... Honestly the problem just surfaced out of nowhere. I didn't change my ROM or anything. Well, I guess its time to look at another tablet.
[Nexus 7 (2013) General] sam10000:
Hi

I've been offered a good price for a Nexus 7 2013 in a closeout sale, and wonder if anyone can help me understand whether the touch screen will be a real problem for my usage.

I am aware that the problem is grounding-related.

I mostly leave a tablet on an aluminum stand. The apps (including a few simple games like backgammon) require single taps or scrolling with one finger.

Thanks in advance.
[Nexus 7 (2013) General] mdamaged:
The severity seems to vary from device to device, we do not have access to the specific device in question to be able to give you anything else other than a guess. That being said, based on anecdotal evidence, generally, if the device is not going to be held in usage (i.e. laying on a surface that does not provide a ground), the occurrence of problems rises. In other words, caveat emptor.
[Nexus 7 (2013) General] player911:
Yea it seems all N7s have the grounding issue. If I remove my case and hold it with one hand while operating on another, my screen is flawless.

If my tablet is in the case, laying on my bed, and I reach over to pause my Chromecast/Netflix show... it won't respond until like 10 taps. Skipping and rewinding is also such a chore that I want to shoot myself in the face sometimes.
[Nexus 7 (2013) General] sam10000:
Thanks for your feedback.

Does it mean that, when holding a Nexus 7 fitted with a case, the touch problem will always be present and cannot be avoided?

Thanks again.
[Nexus 7 (2013) General] AndyYan:
After flashing one of these images in the OP (specifically, TS11), I never had any of these touch issues, even when cased in. YMMV, of course.

Sent from Google Nexus 4 @ CM11

[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
[Nexus 7 (2013) General] player911:
Whats weird is I can be at work, with it on my desk, in the same case, using 1 hand... and it works great. When I'm at home, on my bed, same case, one handed, it sucks.

Maybe the environment has a play. I work in the basement office of an office building. Perhaps the it has more moisture and thus works better then my 2nd floor, dry, bedroom.
[Nexus 7 (2013) General] osm0sis:
It's got to be that the bed is a soft surface absorbing some of the impact. Easiest workaround is to put a finger on the bezel before you touch the screen. Hassle, but it gets the job done. :)
[Nexus 7 (2013) General] sam10000:
Hi, all

So it seems that ts11 is definitely worth trying. Thinking of taking the plunge and get a Nexus 7.

Does the combination KitKat 4.4.2 and ts11 work well? Can anyone comment?

Thanks!
[Nexus 7 (2013) General] Pandae:
The ts fix will depend on the device's own hardware tolerances/variances, not so much what ROM is used.

Take the plunge, and odds are you'll get a unit that is just fine. If not, it isn't hard to apply a fix, rather than go through the hassle of return (and possibly get another device that needs a fix).
[Nexus 7 (2013) General] bradders1234:
thanks

big THANKS for your help with this... i replaced the digitizer/lcd combo and it was all over the place. i spent a week touching changing fixing, removing the back.. building up the connector things inside... but the left side screen was no good. :( your ts10 file fixed it :) no way would i have been able to do this without your help. thanks :):good:
[Nexus 7 (2013) General] player911:
I'm running 4.4.4 and ts20 (always seemed to work best for me across multiple devices).

If you own a Nexus 7 2013, you pretty much are required to flash one of these before the device is usable in 1 handed operation.

Good idea on the soft vs hard surface too.
[Nexus 7 (2013) General] Sensamic:
Maybe Lollipop will definitely fix this issue.
[Nexus 7 (2013) General] mrDmola:
Question: After using ts10 for months, everything worked perfectly. I'm not sure when exactly (because it's on/off between days and weeks), but I've been having touch screen issues with tons of deadspots randomly, etc. Could this have been caused by flashing stock 4.4.4 odex over whatever I had before? I didn't think that it was going to wipe anything because the OP said that we should be able to use any rom after flashing this. I'm really hoping that the ts11 works.
[Nexus 7 (2013) General] mdamaged:
It could be warping of the digitizer due to battery swelling, or a loosening ribbon connector.
[Nexus 7 (2013) General] Dr0idG00di3:
Hey,

i got the Problem only in Landscape Mode (testet with YAMTT) and i use CyanogenMod 11 with ElementalX Kernel, can i flash this Fix over my Setup or i need to go back to Stock, than flash this Fix and than back to CM and Custom Kernel ?

Thanks for the Help !
[Nexus 7 (2013) General] mdamaged:
You do not flash this, you boot it, and no, you do not have to go back to stock.
[Nexus 7 (2013) General] Dr0idG00di3:
Thanks a BUNCH Bro !!

It worked for me on :

NEXUS 7 - 1A030A

90NK0081-M00740

DAOKBC.......

HW: rev_e

boot-ts10-lock.img

It worked so good, thanks so much !!
[Nexus 7 (2013) General] mrDmola:
Eh, well flashing ts11 got things back in working order for the most part. There are still occassional issues at the top right corner of the screen when it's laying flat, but it's still way better than before. So back to my prior question: would flashing an upgraded version of android cause that boot.img to be overridden?
[Nexus 7 (2013) General] mdamaged:
You misunderstand how this fix works, it did not touch your boot.img, it does not flash a boot.img, it only boots, changes the firmware and that's it, so, to answer your question, no it will not overwrite the ts11 firmware if you change or reflash kernels or flash roms, UNLESS and until you boot up the unlock ts first.
[Nexus 7 (2013) General] sam10000:
Hi

I just bought a Nexus 7 2013 in a clearance sale.

Is a fix like ts11 likely to work with Android 5.0 Lollipop? Should I wait for the OTA upgrade to be completed first?

Thanks in advance!
[Nexus 7 (2013) General] rand0m_insanity:
I would say go ahead do the update first and test to see if there are still issues.

Edit:

I read your post wrong. I thought you were pertaining to OTA update. Well, if you can hold out until Android L, then do so. i'm, It is likely this fix will work with L, so I don't think there will be a problem trying these fixes right now.
[Nexus 7 (2013) General] sam10000:
Thanks for your helpful reply.

I'll wait until an OTA upgrade is available, upgrade to Android L, and take things from there.
[Nexus 7 (2013) General] rand0m_insanity:
You're welcome. Glad I was able to help out.

Also, with my experience with my device, I noticed the screen to misbehave when being used a lot. This is likely due to the heat as most people reported here.

After using the fix, I noticed that the screen is still fairly accurate to touch input when under full load.
[Nexus 7 (2013) General] Persechini:
I used the ts10 image a while ago and so far I pretty satisfied, but if this doesn't patch the kernel, what exactly does this patches do?

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 7 (2013) General] mdamaged:
It writes new ts firmware to the device. ts firmware != kernel

While the following differs in its implementation, it may help understand: http://xdaforums.com/showthread.php?t=2800308
[Nexus 7 (2013) General] theSayan:
well thank you

...
[Nexus 7 (2013) General] predatorftp:
Thank you so much, you fixed my device !!!
[Nexus 7 (2013) General] afremont:
Wow, do we still have to do this? I haven't upgraded my nexus 7 since I use a hisense pro most of the time. I built a kernal last year to lock in the firmware that I liked. I guess I can't just update to the latest released update and expect it to just work, huh? I cant believe this is still an issue 12 months later.
[Nexus 7 (2013) General] mertzi:
I had my screen replaced in March because of severe bleeding and had used ts10 with success prior to that. After the screen change I had no problems until a month ago. I've now went through all fixes and ts14 and ts16 are best though not flawless. What strikes me is that I can use it for long periods with no problem and then out of nowhere it goes crazy for a minute and then back to normal. I really hope the people at Asus responsible for this mind blowing design flaw got fired, and everytime it disturbs my typing I wish I could slap one of them hard in the face.
[Nexus 7 (2013) General] afremont:
You gotta realize that they probably saved 15 cents per tablet manufacturing costs. :rolleyes:
[Nexus 7 (2013) General] serik21:
My nexus is now stuck on the bouncing balls.

I unlocked my bootloader and followed the directions in the OP. I am on KitKat 4.4 and it said that i would get stuck on the bouncing balls. so i waited well over 120 seconds and rebooted by holding the power button.

After i did this my tablet still sits on the bouncing balls, it will not respond to ADB commands even if i reboot into fastboot. And when i boot in to CWM it tells me it cant mount my flash drive, therefor i cant restore a backed up image.

Any help would be greatly appreciated!!!

UPDATE

I realize now i shouldnt have tried to load this file being on kitkat 4.4, have i bricked my device? I cant get abd to recognize it in windows at all. if i boot in to CWM and attempt to sideload stock 4.3 it transfers to the device, begins the update then immediately stops

UPDATE 2

Managed to flash stock 4.3 ( *phew*) and now that im back up and running my touchscreen is working flawlessly. Im not sure if running the ts10 img is what did this, but wither way im satisfied and happy.

Thanks,

Don
[Nexus 7 (2013) General] afremont:
Yeah, glad you got it. That's kinda interesting when stuff like that happens, isn't it? ;) So far, I haven't messed one up permanently; I've had some intense moments though.
[Nexus 7 (2013) General] Việt Hùng:
zenfone 5 multi touch fail

Software support zenfone 5? My device fail multi touch :(

Ht tp://youtu.be/kQCX8yEAypU
[Nexus 7 (2013) General] AndyYan:
NO. Nexus 7 (2013) only.

This is not a "software", after all.

Sent from Google Nexus 4 @ CM11

[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
[Nexus 7 (2013) General] Việt Hùng:
You can fix my zenfone 5? :(
[Nexus 7 (2013) General] _jis_:
Why you didn't read at least the post preceding your post?

This thread is about special modified firmwares for touch panel controller just for Nexus 7 2013 not for any else device.
[Nexus 7 (2013) General] tripp9r:
When i installt one of those fixes (ts10/20/30) my nx stucks in the bootloader - the cmd says "finished" after 0.84 seconds, but the nexus wont reboot itself.

Did i get something wrong?

I manually rebooted the nexus (by holding the pwr-button) - can i check if the ts10/20/30 is installed properly?

Chears

Alexander
[Nexus 7 (2013) General] kicsrules:
anyone tried the lollipop release and check if its working ok or has the same ghost touches??
[Nexus 7 (2013) General] Black_Tiger:
Same ...[emoji19]
[Nexus 7 (2013) General] oTeMpLo:
fastboot boot boot-ts10-lock.img ? does not work any more ? (it restarts -> boots to recovery)..

New booloader ?

EDIT: --- > but seems to doo well. as touch is working again...
[Nexus 7 (2013) General] Black_Tiger:
Yes there is a new bootloader, before flashing the Lollipop factory image I flashed ts-unlock.img

I didn't flash ts10-lock back yet, I'm tired of these workarounds ?
[Nexus 7 (2013) General] bossman013:
To be fair, I'm one of those people. This thing runs like a champ using ts-10 and I was already on Q having sticky touch and response issues.
[Nexus 7 (2013) General] afremont:
This much is exactly correct. After unlocking, sfhub's firmware remains until another update comes along.
[Nexus 7 (2013) General] bossman013:
Got it. That's what I thought and it makes total sense too. So if I want the firmware from "update B" then apply the ts-unlock and THEN install the pending OTA from Google. If the ota doesn't work to expectations, we can always go back to ts-10 or whichever works best for us.

You guys rock, hopefully this clears it up for others too. Cheers gentlemen.
[Nexus 7 (2013) General] trvbone:
Thanks for the clarifications everyone! Looks like I'm finally going to take the unlock and root plunge on my baby soon maybe this weekend, what is the preferred root unlock method?
[Nexus 7 (2013) General] bossman013:
While command line is respectable, I suggest making it easy on yourself and use Wugfresh. Just FYI when installing drivers and trying to get adb/fastboot to work I recommend putting the nex7 in camera mode instead of media device. I've had better luck that way on my win7 machine.
[Nexus 7 (2013) General] lespaulman67:
All I have to say is Thanks a million for a hard working group of guys. You guys blew my socks off with the fixes. I understand what your saying now. Thanks

Its funny that Google has not even put a small update out. They are slow with this fix problem. lol

So will we see android 5.0 some day soon. I hope so.
[Nexus 7 (2013) General] trvbone:
I'm leaning towards wugfresh method, thanks for the input!
[Nexus 7 (2013) General] bossman013:
Sure thing! Good luck
[Nexus 7 (2013) General] afremont:
The credit goes to sfhub, he did all the work. :). I bet he wishes that he had one of those PayPal buttons. jk ;)
[Nexus 7 (2013) General] big_b0sss:
Well my screen was OK sometimes it was a bit unresponsive needed couple of taps but ts10 fixed that however I'm getting ghost touches while typing. My device build date is 07/13. Should I go ahead and try the next one or should I stay on ts10? Also if I go ahead and flash ts20 should I unlock my TS first ?
[Nexus 7 (2013) General] spaceboar:
Amazing resolution!!!

After flashed by Nexus 7 2013, my touch screen was still not usable, especially when trying to use pattern to unlock the device.

After trying ts10, holy cow, this thing swords as perfectly as possible now!!! Why can Google pay the the ts10 developer a reward or job for fixing something that Good isn't capable of doing!!!???

Thanks much [MENTION=1299673]sfhub[/MENTION]! You are a genius! :good:
[Nexus 7 (2013) General] sfhub:
After you do the unlock in the example you gave you will be running firmware from update B. It doesn't matter whether you unlock before or after you apply update B.

Technically you'd be running my stuff until you do a reboot, but since the reboot is a mandatory part of applying any TS* package, we are only talking about a transient 30 seconds.

So if you do Update A, apply TS10, then TS-UNLOCK, you will the have Update A touch firmware.

If you do Update A, apply TS10, then apply Update B, you will have Update B ROM with TS10. If you subsequently unlock you will have Update B touchscreen firmware immediately with no further action necessary.

I spent some time designing the process and software to do the right thing under different scenarios including anticipating future updates from Asus/Google (both updates that improve and ones that regress)

Hopefully it all makes sense to you guys.
[Nexus 7 (2013) General] sfhub:
Just go straight to TS20, no need to unlock.
[Nexus 7 (2013) General] afremont:
This is wrong. After unlocking, at the next kernel boot it will update the touchscreen firmware with what is contained in the update B kernel. Sorry about that, wasn't thinking.
[Nexus 7 (2013) General] mishko:
I'm on PA 3.98 and the touch response was acting up, primarily in the top+bottom corners. The issues seem to have gone away after flashing the ts10.img! So a big thank you!
[Nexus 7 (2013) General] bossman013:
got it!!! thanks for the clarification, and a BIG thanks for doing all of this for the community. You're a savior to many right now man, thank you. :good::good: