yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] steve3194:
ts 10 fixed grounding

sfhub you are a legend. I'm on my third nexus 7 all 3 had the "grounding" issue just flashed ts10. Not only has it fixed the issue the screen is also more sensitive which is definitely a positive for me. Thanks a million
[Nexus 7 (2013) General] getupandbeit:
Thanks so much for this. I flashed ts14 after no luck with 10, 20, or 30. Was planning on returning this tablet to Best Buy tomorrow. Not anymore!

Cheers.
[Nexus 7 (2013) General] manore:
Amazing

I had the problem that touchscreen didn't work when tablet was lying on the table. When held in hand it worked perfectly. I tough it is hardware grounding problem.

I was wrong and happy about that! I installed ts10 patch and now my tablet is perfect! Works on the table, in case on the table with screen protector. So this really fixed all of my issues!

Huge thanks to creator! :victory:
[Nexus 7 (2013) General] HTC Venom:
Where can I get the ts14 one ? I couldn't find it anywhere

update : sorry I have just notices that other zips have different boot.img , i though 1,2 and 3 where only available , now im testing with 11 then we can see
[Nexus 7 (2013) General] kingston73:
Is there anyway to do this without a computer? Can the flashify app be used?

EDIT: I just tried ts10 and it is working great. I'm on Bruce's cm11 with bricked kernel and my problem was the screen wouldn't work unless I was holding with both hands. The ts10 patch seems to be working great, I just typed this message 1 handed.
[Nexus 7 (2013) General] konradsa:
OK, so I installed ts10 to fix the issue where when tablet is lying down, it fails to recognize some touches. Ts10 seems to have fixed that, however, there seems to be a side effect. One in a while, the screen becomes a little erratic, where it seems to have some sort of dead bands where touches are missed in, but some touches are also recognized twice outside of those. Turning screen off and on again usually fixes it before it comes back after a day or so again.

Had anybody else experienced the same issues with ts10 and found that another version works better for them? Thanks.
[Nexus 7 (2013) General] kingston73:
After reading through this it seems like the right file is pretty individual so you'll probably just have to try some others. Also, did you reboot a few times like it said in the op?
[Nexus 7 (2013) General] HTC Venom:
Ts11 on Slim rom works like magic for me, been using my device for all day and it works flawlessly , thanks a lot , you have managed to fix the only nexus 7 tablet in my country
[Nexus 7 (2013) General] Coronado is dead:
Exact same here.
[Nexus 7 (2013) General] Daydog:
Thanks

ts10 can fix my Nexus 7

Thank you!
[Nexus 7 (2013) General] Omar04:
I had a perfect device till 4.4.2 came and messed my touchscreen badly. Random touches, not responsive selections, phantom touch all around. Today I decided to test boot-ts10-lock.img and so far so good. Will report later if anything comes up. Thanks.
[Nexus 7 (2013) General] Matrix_19:
Same issue with my ts09 but it is happening once a week. So I can live with that since it's way better than my issues on stock 4.2.2
[Nexus 7 (2013) General] dentax:
Thank you very much I worked the touchscreen problem "ts10." But I had to install with roolkit robot boot option as instructed gave me error
[Nexus 7 (2013) General] ehasley:
So tried flashing boot-ts10-lock.img on my tablet running 4.4.2 KOT49H and now its hanging at the bouncing balls boot screen. I read the note about this happening in the OP BUT it says nothing else about it, how to fix it, over come it or anything. Would really like to use one of this fixes for the wonky touch screen.
[Nexus 7 (2013) General] mdamaged:
What were the exact steps/commands you used? Because if you used "fastboot flash boot-ts10-lock.img", that's your problem.
[Nexus 7 (2013) General] ehasley:
adb reboot bootloader

then

fastboot boot boot-ts10-lock.img

The device rebooted to the bootloader correctly after the first step then I got confirmation of the flash before the device rebooted again. After letting it sit there 10 minutes I rebooted it through abd command and it was successful. It rebooted succesfully, but I have no idea if the patch worked.
[Nexus 7 (2013) General] 77kdv77:
check firmware version in the terminal emulator after applying ts patches

su
dmesg | grep ektf

it looks like this

[2.208709] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa044

a044 is the default firmware version in 4.4.x kernels (a042 in 4.3 kernels). for example, ts10 flashes a059… all ts patches replace touchscreen controller firmware and you can see the firmware version in the kernel log to be sure that the patch was applied…
[Nexus 7 (2013) General] Danstroem:
The same for me on KOT49H. One difference: after waiting ten minutes for the first boot to complete, I had to shut down manually by pressing the power button for 10 seconds. After powering it on again, it booted and solved my touchpad issues with ts10.

Thanks to [MENTION=1299673]sfhub[/MENTION] and this thread!

dmesg|grep ektf shows

<4>[ 1.769500] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 1.769775] [ektf3k]:[ELAN] Start HW reset!
<4>[ 2.022949] [ektf3k]:[elan]detect intr=>Old FW
<4>[ 2.023071] [ektf3k]:The boot code is old!
<4>[ 2.053222] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:55
<4>[ 2.053344] [ektf3k]:[elan] hello packet's rc = 0
<4>[ 2.265289] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa059
<4>[ 2.267333] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x007e
<4>[ 2.269439] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00d2
<4>[ 2.271453] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029
<4>[ 2.273193] [ektf3k]:[elan] __fw_packet_handler: boot code id: 0x6047
<4>[ 2.273315] [ektf3k]:[Elan] Max X=2239, Max Y=1343
<4>[ 2.274078] [ektf3k]:The firmware was version 0xA044 and id:0x3029
<4>[ 2.274322] [ektf3k]: /proc/ektf_dbg created
<4>[ 2.274780] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrupt mode
<4>[ 2.275054] [ektf3k]:[ELAN]misc_register finished!!

Don't know what firmware version is expected with ts10... :)
[Nexus 7 (2013) General] 77kdv77:
a059
[Nexus 7 (2013) General] Danstroem:
Yeah, thanks! Didn't see your last sentence in the first place.
[Nexus 7 (2013) General] sam298:
Which ROM are you using? Some ROMs are working fine, may be they have the proper drivers. I was using TS14 but wasnt perfect. Flashed DJL ROM after ts unlock and no issues so far. No grounding errors too. I heard PA beta also has no touch issues.
[Nexus 7 (2013) General] Omar04:
I don't use custom ROMs on nexus devices. Full stock not even root. TS10 fixed my issue so I relocked bootloader and installed everything back. I'm happy now with touch performance.

---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------

If you follow every single step to a T and if you are on 4.4.2 it say it will hang in there, then it say to reboot manually holding down power for a few seconds. Then proceed with next steps. ;)
[Nexus 7 (2013) General] thisisfraa:
Nexus 7 (2013), 4.4.2 stock, rooted with SuperSU v1.91.

Tried TS10 & all my touchscreen problems were gone immediately. The boot logo hanged for a couple of minutes, I just turned the device off and rebooted, worked fine. I rebooted two more times after that to be sure it was working without any problems, thanks!
[Nexus 7 (2013) General] Nyckrs:
Can someone help me please. I fastboot unlock.img and i am just stuck on the google screen with the unlock lock. Held power button to restart and still won't boot pass the google screen. How do i go back to original?
[Nexus 7 (2013) General] omgsy:
It's been 2 days since I got my nexus.

I tried the Multitouch app to test my multitouch and when I press corners when lying on my bed and on my pillow, the problems comes up. (boucing and ghosting.)

I tried ts10,ts20 and it still does it.

It's fine when I'm holding it up though. You can't fix the multitouch when lying on bed?

EDIT: Tried ts10, ts20,ts30, ts11, and lastly ts14.

None of the things fix when on bed or pillow BUT if its connected to usb connector, it has no problems.

If i hold it on my hands w/o the usb connector connected, there are no problems.
[Nexus 7 (2013) General] daryllh:
4.4.2 (KOT49H)

PA 4.0 BETA 4

Franco Kernel #12

Purchased tablet new at Microcenter 3 days ago.

I tried a couple screen touch programs. I was fine in portrait mode. I thought I was fine in landscape mode until I was watching Netflix for the first time.

The slider bar in Netflix wasn't responding to my touch with the N7 in a case, propped up in a viewing angle in landscape mode. The section of screen near the bottom left corner wasn't responding. I couldn't move the Netflix slider to the right to jump 4 minutes ahead nor could I hit the PAUSE/PLAY button next to the slider.

Tried YAMTT again in the same environment and sure as hell, i wasn't' registering touches in the lower left part of the screen. If I held it, I could register and the same part of the screen in portrait seemed to work (although I do remember having to tap google search bar more than once).

Long story short, I found this thread, followed instructions, installed the ts10 file and after the waiting period, the same Netflix test came up with positive results. I will monitor closely but I think it was a fix that saved me a lot of hassle with RMAs. Thanks to the OP.

EDIT: I forgot to add, after entering this command: fastboot boot boot-ts10-lock.img, I had a blank screen and it didn't reboot the tablet back to Android OS. I waited 2 minutes and held the power button down.
[Nexus 7 (2013) General] _MetalHead_:
Stock rooted KOT49H, purchased in January

TS10 worked like a charm. For the life of me I cannot reproduce any touchscreen issues now, whether plugged in/unplugged, holding in hand/laying on bed, stylus/no stylus.... effing beautiful.

THANK YOU OP!!!
[Nexus 7 (2013) General] jjrojo:
Thank you op

Tried ts10, bootloop ever. Rebooted some times, wait some minutes and nothing.

So, i restored a nandroid backup, it booted fine.

Can someone confirm to me if still i have ts10?

Or with nandroid backup is restored to default value?

My touchscreen is more responsible and more sensitive.

Thanks a lot op.
[Nexus 7 (2013) General] Pandae:
You should still have it. These fixes are in boot, so they aren't in the /system or /data areas and won't be affected by flashing a ROM.
[Nexus 7 (2013) General] _MetalHead_:
I take this back. Everything was fine for about an hour and then it started acting up again, worse than before. Tried ts-20, same thing. Now I'm trying ts-30, keeping my fingers crossed.

question for [MENTION=1299673]sfhub[/MENTION]- If there are only the three variances of touch screen, what are all the files in the exp folders for?
[Nexus 7 (2013) General] jjrojo:
Thank you for you response. If i remember fine twrp backups have option for backups and restore /boot, what's i did.
[Nexus 7 (2013) General] HTC Venom:
Did you check all zip files in the op? Each zip file there has different drivers ,
[Nexus 7 (2013) General] _MetalHead_:
I downloaded all of them, just gonna try them one by one until something works. What's the deal with the exp files? Are they just other ones to try? There's nothing about them in the OP.
[Nexus 7 (2013) General] HTC Venom:
Different ts files as ts11 was one of them , I were lucky enough to try ts11 from the first try and it's now working for me like a charm for all last week
[Nexus 7 (2013) General] _MetalHead_:
Yeah that's what I figured. TS-30 has been good so far... though now that I said that it'll probably take a dump on me.
[Nexus 7 (2013) General] mooseass:
yessir ts10 first try

you da man
[Nexus 7 (2013) General] HTC Venom:
So how does it work for you now ? any success?
[Nexus 7 (2013) General] _MetalHead_:
Honestly, I'm not sure. I get occasional erratic zooms in Chrome and Dungeon Keeper which would lead me to think I'm still having issues, yet in any multitouch visualizer app I am not getting any ghost touches or dead zones or anything like that. Before I flashed any of the fixes, I could clearly see issues in testing apps, yet now it behaves perfectly. I'm kinda confused as to why it's perfect in some apps but in others not so much. I'll likely try some of the other TS files just to be sure, but the way it is now is acceptable to me for at least a bit. It is a marked improvement over the way it was originally, that's for sure.
[Nexus 7 (2013) General] TheMaskedHamburger:
I am running stock 4.4.2 KitKat. With any luck this may fix my grounding issue(no multi touch, ghost or sticky touch issues present). Here are my results with the different TS packages:

TS-10 - Fixed Grounding issue, worked perfectly for about half an hour, and then... terrible ghost touches along the y-axis kicked in (or as sfhub put it, it started wigging out). Shutdown that night, it worked perfectly the next day for about half an hour and then these ghost touches came back. Weird.

TS-20 - Only used for about 10 minutes, back to having grounding issue. Switching.

TS-30 - Same as TS-20 as far as I saw, grounding issue.

TS-09 - Was curious to try as I read that Sfhub himself had similar issues with TS-10 which TS-09 fixed. ANDD missed touches, not quite deadspots, more like every second or third touch is missed.

TS-08 - Solved my grounding issue!!! :D However, I found out I now have slight 3 finger multi touch issues in yammt. But they are occasional. I'm not sure if I'm out of the woods yet, as my typing is a bit wonky occasionally. Its either me adjusting to the responsive keyboard, or it could be ghost touches. However, this is NEAR PERFECT.

Will report back another time. For now, TS-08 has fixed my nexus.

Current state: Grounding (fixed). Multitouch issue introduced(minor). Possible (?) ghost touches (unconfirmed).

Thank you very very much Sfhub.

Sent from my Nexus 7
[Nexus 7 (2013) General] rioru:
guagnitu very

First one perfectly worked for me. Flashed it on stock rooted Android 4.4.2. Then i flashed CleanROM and Glitch kernel. It works pretty fine.
[Nexus 7 (2013) General] rubene66:
Testing ts08 until now it is working well i hope it stay because i was starting to hate the tablet

I have test ts10,12,14,20,30 no luck
[Nexus 7 (2013) General] sakuhei:
Tried ts10, 20, 30 14, 8, all fails with different types/styles multitouch issues persist... quite fed up with this machine...
[Nexus 7 (2013) General] kingston73:
I"m just curious so don't get offended, but do you notice issues during normal use? If so, what exactly? Sometimes I feel like some people are looking to find problems using some of these testing apps.
[Nexus 7 (2013) General] sakuhei:
I am not using multitouch test to derive this baaaaad result. Purchasing the n7 2013 was mainly for the replacement of my old n7 letting me play gta san andreas and many other games. This machine just help me jump out of the car when I was driving in gta, or turn my car right when I wanna go left! Many other apps got the same multitoch issue. Though the freqency is not high but I am not expecting it when buying this NEW machine, esp my all others nexus devices running well (galaxy nexus, n4, n5 and even my old n7)
[Nexus 7 (2013) General] ednometry:
Thanks Man!!!

Wow!!! Thank you very much! I'm running the Dirty Unicorns 4.4.2 rom and it really made the touchscreen problems more prevalent than before. I've always had a few problems here and there typing with double button presses and what not but the dead spots got really crazy while using this rom for some reason. I got it fixed first time out with the ts10 fix. Thanks a lot for making my tablet perfect! I just hope it stays that way.:good:
[Nexus 7 (2013) General] mpiwosal:
I bought a nexus 7 3 days ago and no problems with touch screen. As well on jelly bean as on kitkat. My production date is 09.2013 and number starts with D90...;)
[Nexus 7 (2013) General] jfriend33:
Must be nice. The issue is randomly affecting units.

I am only severely impacted when using tablet on a flat surface. In hand is occasionally. If I press harder it solves the problem.

I know with phones, unlocking the bootloader may void a warranty. How about tablets?
[Nexus 7 (2013) General] Stalko:
THX !!! Im very very happy solve two problems.

Screen PROBLEM !

WIFI and Bluetooth PROBLEMS.

Listen music on bluetooth audio reciever (bt version 3.0), WIFI stuck and dont work.

NOW wifi WORK and music PLAY.

WIFI speed NO music 2,4ghz connection 65Mbps 5.0-5.5 megabyte per second. MUSIC PLAY 2.0-2.5 megabyte per second.

!!! boot-ts20-lock !!!

Sorry my english very very BAD.

:laugh::laugh::laugh:
[Nexus 7 (2013) General] ShinnKQ:
Sadly tried all and none of it works perfectly. :( I'm using my N7 to play some daily games and the touches are fkn my games up hard. Especially those gem turning (time based) games =.=
[Nexus 7 (2013) General] mpiwosal:
Same as phones unfortunately. But i unlocked it anyway:) cant live without root ;p
[Nexus 7 (2013) General] kingston73:
I'm not highly technical so maybe this is a dumb question, why would a new rom affect touch screen? Ts10 was working great but I just flashed a new cm11 based rom and suddenly have touch issues. Missed touches and ghost touches, bad enough that it's hard to type. I had been using another custom rom when I did the ts10 fix and that seemed to work well but now it's definitely worse and the only thing I changed was the rom. Guess I'll try some others.

Is there any strategy to trying these? Any numbers working better with certain roms or whatnot?

Also, just so I'm clear, the boot-ts-unlock.img will basically reset things back to what they would have been if we never did any of this?
[Nexus 7 (2013) General] sam298:
Each ROM has built in driver for touchscreen. Previous versions of Google had issues. They fixed it in one build. I think some ROM developers use the best driver. I tried some ROMs most work good - had issues with cleanrom and also touch control module.

For me touch is more important than features battery and even stability. So finally settled with one that works best. Used the ts fixes in this post it is great but you have to have patience - try one, do some reboots, use for a week to stabilize and see if it is good or not. Then try a diff variant. Asus service sucks. They told board is bad and needs 200$ to fix. Glad I found xda forum.
[Nexus 7 (2013) General] afremont:
Try this:

http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/

Edit: You only need fastboot to put it all back to something that the retailer won't notice has been hacked. Its real easy to do as long as you can get to the bootloader screen and "fastboot devices" can see the tablet. The stock recovery program is fine, no need to load anything else to put it back to stock. If you've already changed it, the "flashall" script will handle everything but relocking the bootloader.

You can then flash in sfhub's fix or take it back.
[Nexus 7 (2013) General] astuermer:
I am on JSS15Q.

Bought the N7 last saturday, updated to JSS15Q immediately after reboot.

Ghost touches appeared first on sunday evening.

For me "10" only helps a bit...

Still random screen touches or screen looses touch for a second.

As a user described earlier: It seems it occurs as soon as you put more than 2 fingers on the screen the same time. As long as I am scrolling or typing with max. 2 fingers everything's OK.

As soon as I put 3 or more fingers on the screen the touch goes crazy.

Only a reboot helps in this case.
[Nexus 7 (2013) General] lespaulman67:
I tried to load the TWRP and now messed up my Nexus.

From the command window from windows.

I do a adb devices and it finds it. So that part works. Its when I do the command adb reboot recovery it reboots fine. But then a I get a android laying down it will not go to recovery mode by window commands anymore. I can reboot it with volume down and power. But it will not find my device in the command window if I manually do recovery mode. That damn TWRP file I knew I shouldn't mess with anything I never used before.

Damn it.

So I need help

I was lucky I was able to run the fastboot oem lock from windows and it said waiting for device and I manually put the device into recovery mode. otherwise I would be screwed.
[Nexus 7 (2013) General] afremont:
First off, don't panic, I'm sure you can fix this unless there is some hardware fault of some kind. You don't need to boot into recovery program, you just need to be able to boot to the bootloader with "adb reboot-bootloader". You then need to unlock the bootloader again so that you can flash the factory image for JSS15Q that you downloaded and unpacked into the .zip file and a few extraneous files contained in a directory named "razor-jss15q. Then you just need to go into the razor-jss15q directory and do "fastboot -w" to clear the user data and then run the flashall.bat file OR (this is what I do) just do the command "fastboot update image-razor-jss15q.zip". The zip file contains images for USER, SYSTEM, CACHE and RECOVERY (this is what removes the TWRP and puts back the original).
[Nexus 7 (2013) General] lespaulman67:
What is the easiest way to load TWRP then.
[Nexus 7 (2013) General] sfhub:
You can do it via any custom recovery, but not stock, because I cannot sign it with Google keys.
[Nexus 7 (2013) General] lespaulman67:
well I have TWRP installed.

I did the update fix update-repair-JWR66N.zip

Everything installed awesome. I am now on JSS15Q and its smoking fast smooth and no problems at all.

I still have the boot-ts10-lock.img loaded I guess.

I will tell you this thing is running the best I ever seen. Perfect even the multi fingers I am not seeing any ghosting at all.

So if I have TWRP on my device and its unlocked right now. What happens if a Google update comes. What do I do about new updates?

Also will I have anymore problems with updates not verifying and not loading up or is it all fixed now.

Thanks guys its been a scary road but its worth it.
[Nexus 7 (2013) General] sfhub:
This is normal behavior for what you did.

First if you are seeing android laying down, you did not run TWRP, you are running stock recovery. People not used to fallen android sometimes get anxiety because they think something is wrong. It is actually just a screen image to hide the menu/status window for recovery (kind of like how windows put that windows logo with the scrolling bar to cover up the driver loading messages)

Whenever you see fallen android you can always get either the recovery menu or status+recovery menu by press/holding Power, then press/release VolUp, then release Power.

If you had run TWRP, you would see the TWRP menu, it would be obvious.

The reason your adb doesn't work anymore is because the USB ID changes when you use recovery and the standard drivers don't know how to deal with it. In device manager you'll notice an unknown device named "Flo". This is normal if you are running recovery without the drivers that have been modified to work with recovery.

[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)

You are not screwed at all. Don't panic. Nothing is messed up at all. You were just running stock recovery when you thought you were running TWRP.

As to why that happened, probably you reordered some step and went to recovery instead of booting to twrp.

I can walk you through it, but essentially you do

adb reboot bootloader

fastboot boot twrp.img

(I renamed the downloaded TWRP img to twrp.img for convenience)
[Nexus 7 (2013) General] afremont:
What do you have in there? When this eMMC problem occurs, can't you just flash in a factory image or doesn't that work?
[Nexus 7 (2013) General] lespaulman67:
I do have one big problem. If I try to boot to teamwin TWRP from bootup it gives me a android on its back with a red ! triangle .Its not working anymore. What's up with that.