yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] dexgen:
I think my problem is that restarting the device always fixes any issue for me. It's only after a little bit of use that I see touchscreen issues (areas of the screen not responding or multitouch going crazy) but again after a reboot it's all good for a while.

So it's really hard for me to decide if any of these files make the issue any better. It seems that I still have the same problem (good after reboot then bad after a little use) but just the area of the screen that gives the problem changes.

I guess it would help if I knew exactly what these files aim to do and what the difference between them is instead of just knowing that they have different numbers. But thanks very much to the OP for his work on the issue.
[Nexus 7 (2013) General] DowntownJeffBrown:
You flash in the bootloader using fastboot.

>^.^< Sent From Meow nexus5

---------- Post added at 11:43 AM ---------- Previous post was at 11:42 AM ----------

So u plan on selling a faulty unit to someone unknowingly? I feel bad for whomever you sell it too. Why not just use your warranty if you can't fix it using these files?

>^.^< Sent From Meow nexus5
[Nexus 7 (2013) General] Skinpipe:
hi guys im running stock 4.4 and franco r8 just flashed ts10 and im boot looping as i knew i would be from the op but it wont reboot into bootloader with the button press combo it will reboot but just to an infinite loop.

any help is greatly appreciated

im ok now thanks
[Nexus 7 (2013) General] Yuccaman:
Should the new Touchscreen files survive installation of the 4.4.1 Bootloader and a Custom ROM ?

I've been running CleanROM 1.7 with ts-10 for a while and not noticed any touchscreen issues....

I updated to CleamROM 2.5 today, flashing the new Bootloader first, with the same version of TWRP I already had as my Recovery.

I didn't notice anything obvious until playing around with some browsers where I found the text would start scaling when trying to scroll.

Launched YAMTT and this showed a second ghost touch half way up the screen with doing a one finger swipe upwards at least 50% of the time.

I've flashed ts-10 again and so far so good both with YAMTT and Browser, so wondered if the Touchscreen driver have been overwritten when Flashing a ROM ?

Of course, the Touchscreen could have just been having a funny 5 minutes and a reboot would have sorted it, but there you go :)
[Nexus 7 (2013) General] hahuhe:
again, as i did when updating to 4.4.1.... did ts-unlock, updated to 4.4.2... still have the same problem, non responsive touchscreen when not grounded. I wonder whether google had already given up to fix the touchscreen problem :(

went back to ts-10, now had a bit of a ghost touch near the front camera. finally arrived at ts-11. happy.

but still...Dear Google, when will we have an update that actually fix this problem for good?
[Nexus 7 (2013) General] DowntownJeffBrown:
I think the problem is no screen has the same touchscreen variance so when they fix it for some they break it for the others.

>^.^< Sent From Meow nexus5
[Nexus 7 (2013) General] Matrix_19:
So true... When I got my tab this summer, I had no touchscreen issues at all. And then update after update, it's always getting worse
[Nexus 7 (2013) General] Trevomader:
Since people are reporting improvements in 4.4.2, i want to test google's driver.

So i want to ask if only doing the ts-unlock is enough to get google's driver going when i flash the released stock rooted 4.4.2 rom through twrp?

Thanks in advance :)
[Nexus 7 (2013) General] player911:
I was on 4.3.1 using ts20. Had issues with one hand and occasional typing and gaming errors.

Unlocked touchscreen, Flashed stock 4.3, and downloaded/flashed OTA 4.4. ReBooted a few times and tested. Still wonky ungrounded single touches, but better. 2 handed feels better. Hopefully 4.4.1 is better. Didn't know 4.4.2 was already out. Damn.

-sent from my LG G2 using XDA Premium 4
[Nexus 7 (2013) General] graffixnyc:
Damn it .. I just noticed my device doesn't register taps when laying on a table/bed and I only use 1 finger to touch the screen..only when its grounded it seems based on the other posts in the thread.
[Nexus 7 (2013) General] dehsA:
I will send it to ASUS again in a few days. Trust me, I love the device to bits but I've made many trips to the ASUS service center ever since my 2012 days and I'm starting to lose faith in their QC.

So ts09 has made mine pretty useable over the past few days but last night I was starting to notice missed touches even when I was holding the device in my hands. Will try unlocking and try some other ts fixes tonight. :rolleyes:
[Nexus 7 (2013) General] lespaulman67:
You guys will not believe this crap. I loaded the fix #10 up and locked the boot loader. Went back in and did a adb reboot. Come back in and did a restore. Then when loaded up again I ran the JSS15Q OTA update. It rebooted and came back in. I checked the version and it said JWR66N.

I seen it update on bootup with the new firmware. I just tried my GPS and it locks in quickly and my touch is still awesome. Im still running JWR66N with the JSS15Q update installed.

I did it. unbelievable. I fixed this problem.

---------- Post added at 09:06 PM ---------- Previous post was at 09:00 PM ----------

The JWR66N was load right out of the box. 2 pieces of tape on my box. It had 2 updates out of box. One was mandatory it was the JWR66N it had to load it was 4.3. After you sign in again and boot into jellybean then the JSS15Q was sitting there. I skipped it for a while.

Go read what I did. I solved it. Im running JWR66N with jss15q loaded. But shows JWR66N. I tricked it with the FIX from this boot-ts10-lock.img

I locked the bootloader back up and restored it then ran the new update. JSS15Q
[Nexus 7 (2013) General] lespaulman67:
The update JSS15Q is not showing up in my update anymore. I check for update and its not nothing is there.
[Nexus 7 (2013) General] sfhub:
This is EXACTLY what the touchscreen packages in this thread are designed to do. Once you find something that works, it is essentially locked in place so no Google update will mess with it.
[Nexus 7 (2013) General] lespaulman67:
Other things I notice with what I did.

The screen is way crisper now .

Web pages are silky smooth.

Over all touch is amazing.

---------- Post added at 09:35 PM ---------- Previous post was at 09:30 PM ----------

So are you saying that it is possible that some of the update loaded from JSS15Q and fixed my GPS .

Will your fix allow the update to change version. Or will it block it like it did for me.
[Nexus 7 (2013) General] sfhub:
I know your previous unit came loaded with "4.3" so it never did the "mandatory" update, but your new unit was also loaded with "4.3". It was loaded with JWR66N with developer keys. The mandatory update was to bring it from 4.3 JWR66N developer keys to 4.3 JWR66N release keys. That is why the mandatory update was so small, only 524KB.

Well, that isn't quite what it is designed to do. It is designed to keep your touchscreen software but still allow everything else to update as normal. TS10 didn't cause you to be on JWR66N android OS. Something else caused that.

Are you sure the OTA update completed all the way to the end and rebooted on its own? There can be reasons why it would go most of the way or even 99% of the way and then crap out. For example if you rooted with pre-v1.55 SuperSU and didn't run the OTA fix, then the JSS15Q update would be 98% completed (all the files would be updated) but the bootloader, recovery, and build version would still be JWR66N.

Another possibility is if there was some corruption on the /system directory and that prevented the OTA.

There should be a recovery.log somewhere in your /cache directory that will tell you what went on with the update.

I'm glad you have a working system, but I would be suspicious of the system reporting JWR66N after the JSS15Q update.
[Nexus 7 (2013) General] afremont:
If you go to Settings/About Tablet you should see JSS15Q as your current version. Everything should look like it's on JSS15Q, but the firmware should still be locked on the T10 version. The only way that I know you could see that is with dmesg output from the touch driver loading.
[Nexus 7 (2013) General] lespaulman67:
Your right when I forgot to lock the bootloader and ran the JSS15Q when it went to reboot it stopped with the android on its back and said error. So I held the power till it turned off. Then I held the volume down and power went in to start and booted back in to Jellybean so I could turn developers mode on and turn debugging on. So I could do the fastboot oem lock. after locking the bootloader it booted up and I seen that small update that was JSS15Q loading something up. When I got in it wasn't there. It still says JWR66N.

So should I side load the JSS15Q now or just leave it for now if everything is working.
[Nexus 7 (2013) General] sfhub:
The update is downloaded based on your fingerprint in build.prop, which is also what populates about tablet.

So if you see it says JWR66N, I suspect your unit will eventually download JSS15Q again. Perhaps you can force the issue and check for updates and this time if you run the OTA, pay careful attention whether it completes the whole process.

Updating the build version is the last or one of the last things the OTA does, so it is quite possible you have mostly JSS15Q and just the build # didn't get updated.

I'll ask again, whether you had rooted with SuperSU 1.51 or lesser?
[Nexus 7 (2013) General] sfhub:
Ok, that makes more sense.

BTW next time you get the error with the fallen Android, press/hold Power, then press/release VolUp, then release Power.

There is a status window being hidden by the fallen android image and pressing those buttons will send fallen android away and show you the status.

I don't think you need to sideload. You can probably just check for updates in settings->about tablet and it will probably download again because the OTA whould be in general release now (and even if it wasn't your ID was already selected so it should keep on getting it until it is successful)
[Nexus 7 (2013) General] lespaulman67:
Well I did a restore and there was the update. I hit install it rebooted and started to load and the android fell again. ERROR!

So it will not update with your fix will it.

Here is the power and volume up and release log.

So how do I fix this issue. I can't load the update.

The Nexus 7 is not rooted and the bootloader is locked again only thing is your #10 file is loaded.
[Nexus 7 (2013) General] sfhub:
That has NOTHING to do with the touchscreen fix.

You are suffering the corrupt eMMC problem that affects a select few people.

There is a thread about this that predates by many weeks this thread, so it was definitely an issue that has nothing to do with the touchscreen fix.

What I believe is happening is when that first mandatory update (from JWR66N-devkeys to JWR66N-relkeys) applied itself, it hit the eMMC corruption issue. One or more of your files got corrupted and even though the JWR66N-release keys update completed successfully, it left you with some files that will not meet the SHA1 integrity check from JSS15Q.

So basically in this case you received none of the JSS15Q update. You are really still running JWR66N. If you run multiple GPS apps and sprinkle in some screen off/ons eventually you'll lose GPS lock and it won't come back until a reboot.

Now, if you want to be help me out, I would ask that you make a copy of

/system/app/PrebuiltGmsCore.apk

and download it to your computer. I want to see what exactly the corruption that occured in that file is. I've never been able to obtain a live sample.

The thread about this problem is here:

http://xdaforums.com/showthread.php?t=2380258

If you jump to page 28 here:

http://xdaforums.com/showthread.php?p=44447089#post44447089

I put together an update.zip that will possibly fix the problem for you, but only if that is the only file that was corrupted. It is possible you have multiple corrupted files, but most people just have one.

If you have multiple files, then it is probably easier to run the JSS15Q factory image restore than to figure out back-and-forth which files are bad.
[Nexus 7 (2013) General] lespaulman67:
how do I get that file I can't find it. I have it plugged in into my computer. Help
[Nexus 7 (2013) General] kenobiz:
Yey! #10 fixed my multi touch issue! Thanks a lot!
[Nexus 7 (2013) General] lespaulman67:
Well I tried to sideload the file 35d9b692a660c2ea96ce1181b006c7fddf2cb208.signed-razor-JSS15Q-from-JWR66N.35d9b692.zip

it loaded up ok but did the same thing as the OTA android down and ERROR!.

Does that mean this tablet is junk and will never load a update right again. I just don't understand why its not working.
[Nexus 7 (2013) General] lespaulman67:
Here is the file you wanted.

Is my tablet ok or is it going to have issues all the time.
[Nexus 7 (2013) General] sfhub:
Try starting up TWRP and install the zip file in this post:

http://xdaforums.com/showthread.php?p=44447089#post44447089

Then try the OTA again.

Thanks for the zip file BTW. Confirmed eMMC corruption. 7MB of zeros then 2MB matches what it is supposed to be.
[Nexus 7 (2013) General] stuart0001:
Can anyone that's fixed their touchscreen issues see if it resolves the problem below.

http://xdaforums.com/showthread.php?t=2430645

Touchscreen goes haywire when running a gamma test pattern

Thanks in advance :thumbup:
[Nexus 7 (2013) General] lespaulman67:
I am lost on what to do and what files.

It looks like I will be rooted. I will not know how to undo all of this.lol
[Nexus 7 (2013) General] Nbsss:
Hi, so which of these helps with random but rare stuck touches? Thanks
[Nexus 7 (2013) General] lespaulman67:
Can I do this update-repair-JWR66N.zip without TWRP?
[Nexus 7 (2013) General] KrisJ:
Relock boot loader after fix?

Just a small question...

Can I re-lock my boot loader after applying this fix?

Would the re-locking revert my application of the ts10 fix?

If I travel with the tablet, a locked boot loader would give some more peace of mind in the event of a theft...
[Nexus 7 (2013) General] DowntownJeffBrown:
Yes u can re lock and it will stick with ts10 through anything even updates from Google, until you flash the boot-ts-unlock.img file.

>^.^< Sent From Meow G2
[Nexus 7 (2013) General] Matrix_19:
This morning, my daughter was playing a game with the tablet on the pillow. She had a touchscreen issue... A little line in the center of the screen not responding (which isn't supposed to happen with TS09 that I'm using). I just closed the screen a few seconds and then... Everything was OK again.

So maybe you don't have to reboot the device to fix it quickly?
[Nexus 7 (2013) General] DowntownJeffBrown:
Yes sfhub has said for awhile to just turn the screen off and back on. Maybe try another package? Sounds like ts09 isn't exactly what your tablet needs now. Mine changed over time on my first tablet.

>^.^< Sent From Meow G2
[Nexus 7 (2013) General] tomsen0711:
So testing this on KOT49H... I've sent my N7 to ASUS last week but it didn't get better although they've changed everything except battery and backcover....

I have something like a dead spot under the front camera and upper screen is very unresponsive, doesn't recognize my fingers if not grounded. Some multitouch bugs, but they weren't the main problem. Testing everything twice with additional reboot.

ts10: upper screen responds really good but also a real 1cm dead spot occured. further more multitouch problems.

ts20: almost doesnt respond and more multitouch problems. no dead spot, it's more the whole screen is half dead.

ts30: same as ts20

ts03: lots of real big dead spots on upper half of the screen, bad multitouch

ts04: even more dead spots on upper half, very responsive/sensitive, bad multitouch

ts05: dead spots on upper half and nexus gets his own life on the lower half with lots of ghost inputs

ts06: real big dead spots upper half with multitouch bugs around them. very responsive/sensitive

ts07: dead spots all over the whole screen

ts08: very sensitive, upper third almost dead with 2 big dead spots. much better than 03-07

ts09: perfect sensitive but 2 long dead lines from top to bottom and bad multitouch along these lines

ts11: no dead spot, nowhere. great sensitivity. w00t. but stop, multitouch issues. one finger is sometimes recognized as a second finger, and using 2 fingers ends in a mess more or less. so far best improvement of the dead spots as there is no more dead spot.

ts12: like ts11 except that multitouch issue is 2 fingers on a vertical/horizontal line = no input. better than ts11

ts14: almost great. some multitouch issues if 2 fingers on a vertical/horizontal line, then no input or like 3rd finger. but only sometimes. better than 12.

ts16: not as good as 14. multitouch stays longer in wrong position, like 2nd finger does 3rd touch until releasing it when on vertical/horizontal line..

ts18: little bit worser than 16, even more multitouch problems

ts25: very bad, almost no input recognized

And the winner ist.... wait... there is no winner...

And the last loser is ts14!

So what to say... Google did big bull**** with this Nexus 7 2013. Wasting 2-3 hours for this now, wasted already lots of hours to make it work the last months... It's now better than before, very big thank you for this. But it's time for a refund soon... Maybe I pay some more bucks for the new Nexus 10... I'd like to smash this piece of crap now...
[Nexus 7 (2013) General] NiteFang:
TS10: Jumpy multi-touch when touches get close to each other (Y-Axis on landscape)

TS20: Works near perfect. When touches get close to each other on the Y-Axis (Landscape), they kinda pull near each other like a magnet but this EXTREMELY minor and not bothersome at all, sometimes it's like it's 100% fixed!

TS20 worked great. If I run into any problems in the future I'll try TS30. If that doesn't help, I'll try the ones in between. Thanks!

EDIT: I noticed later that TS20 became rather jumpy, but still not nearly as bad as TS10. I'll try TS25.

EDIT AGAIN: TS25 was much better, gonna try TS30 now.

TS30 works the best. If this messes up more I'll just bring it to BestBuy.

YET ANOTHER EDIT: I've also noticed that magnets will mess up multi-touch (Issues were far less common when I took off my case w/ magnet)
[Nexus 7 (2013) General] Sensamic:
I'm amazed how many people have multitouch problems (stuck touches, ghost touches, dead areas on the screen, etc) and yet they still keep the tablet and try this fixes.

I went through 4 Nexus 7 and returned all of them. On one of them TS10 made it better, but didn't try on the rest.

I'm looking for other tablets right now but Nexus 7 still is my favorite above all. It's a shame it has this problems. All of people affected should just return it so that Asus and Google take good note next time instead of keeping them.
[Nexus 7 (2013) General] dehsA:
I was at the ASUS service center on Saturday complaining about how my touchscreen wasn't fixed. One of the repair guys was telling me how all Nexus 7s have this problem (needs to be held in the hand to work properly), which he didn't think was a problem at all.

He proceeded to show me two more Nexus 7s and loaded up the MultiTouch Test app. Surprisingly both behaved exactly like mine. I placed three fingers to form a right angled triangle and the touch at the right angle would be undetected. Four fingers in a rectangular shape would also be very jittery and sometimes all touches would become undetected.

I'm just going to assume this is a happening to the majority of Nexus 7s and will be replacing it with a GPE LG G Pad instead...
[Nexus 7 (2013) General] meatsneakers:
Thank you for posting these fixes.

I have a 2013 N7 and was experiencing 'jitter' when holding down a webpage, or using the simulated touchpad in VNC apps etc. The touch input would bounce +/- a few pixels when my finger was perfectly still. TS10 solved it completely.
[Nexus 7 (2013) General] katsuru:
I have a small question,

I had a nexus 7 1st gen and decided to get the 2nd gen as well, now thats where my "problem" started, my 1st gen NEVER hat any touch problem, but i guess my 2nd gen has one, i will explain:

when im browsing webpages sometimes i tap on a link, Doesn't open.

when im typing sometimes, some letters arent registered.

when i want to open an app, sometimes doesnt open.

I tested my touch screen, and if i press it without any pressure, there is no recognition of touch... ( my htc recognizes touch without pressure, as well as my n7 1st gen )... i Feel like sometimes haven to really apply pressure in order to make my way trough apps and stuff.

( it was even worse when i had a screen protector )

it gets me mad that i have to press things twice sometimes to get there, feels like my touchscreen sometimes does not acknowledge my touch. Anyone had this problem ? will this fix help me ?
[Nexus 7 (2013) General] Sensamic:
When I returned my third one the guy at the store also told me every Nexus 7 has this problem, which I already assumed.

Some people never see it because they may think it's nothing strange or they don't know how to look for it.
[Nexus 7 (2013) General] DowntownJeffBrown:
I've had 3 n7 2013s and the first 2 had the touch screen bug like crazy. I was able to fix both of them using the ts files. But crazy enough once I was convinced that they all had it I got a 3rd one cause my 2nd decided to stop charging. I fully expected to have to run a ts file from sfhub. But this 3rd one seriously has no touch screen issues. I've ran it through the gamut and haven't had one hick up in the 3 months or so that I've had it. Now what I think is this one just happens to have the touch screen so close to perfectly calibrated that I don't see any issues. I totally 100% believe that all the touch screens are somewhat borked. But a small few are very very very close to perfectly calibrated And I just got lucky enough to have one.

>^.^< Sent From Meow G2
[Nexus 7 (2013) General] Sensamic:
There's a trick I used to check if the touchscreen was good or not in the Nexus 7. I tried 4 devices and all showed problems with this trick.

You need to install the Asphalt 8 game (it's free on the Play Store). Play in any of the scenarios (the best one to check this out is Tokyo because it has many straight streets) and when racing you have to move the car constantly to both the right and left. Every second press right, then left, then right, then left, etc. You need to do this very quickly.

Then the car will lose control and crash to the wall. This happens because of a stuck touch or ghost touch. When you take your finger of the screen the screen still thinks it is touching one of the sides (left or right) and the car goes to that direction until it crashes onto a wall.

This doesn't happen on any other devices I've checked with the game: SGS3, iPad 3, iPad Air, etc. It only happens with the Nexus 7.

Like I said, it's a stuck touch or ghost touch, and the car ends up crashing while you are touching the other side of the screen. So if I touch the right the car will crash to the left no matter what.

This combination of left/right has to be very fast, and with the touch controls enabled in settings (last option). Not the buttons that appear on the screen or the accelerometer. It has to be with your fingers acting as right and left.
[Nexus 7 (2013) General] DowntownJeffBrown:
I'll try it out when I get home but I do play asphalt 8 once a week at least and haven't noticed any problems. Also as far as I'm concerned if I'm searching for the one way to cause a defect then there is no real issue. As long as my real world usage is flawless then that's all that matters. Although the n7 has caused my an addiction to checking multi-touch using "yet another multi-touch test" And this n7 has zero issues there.

>^.^< Sent From Meow G2