yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] hmo66:
Thanks a million!!

Had my nexus 7 shipped overseas and had no easy way to return/fix. Your ts10 image did the trick. That double/triple click was driving me nuts, especially when entering passwords!

Thank you and shame on you GOOGLE!!!
[Nexus 7 (2013) General] thecapsaicinkid:
I'm going to return mine if 4.4 doesn't resolve the issue. Note to self, test hardware thoroughly before fitting a screen protector.
[Nexus 7 (2013) General] di11igaf:
My nexus 7 is the same, rarely have any touch screen issues, and that app, on most patterns went nuts with touch events. Some seemed OK. Funny thing is, my nexus 4 displays every pattern perfectly with flawless touch events on that same app.
[Nexus 7 (2013) General] di11igaf:
There is no updated binarys/drivers from Google for Kitkat for the nexus 7. Maybe when its official it will fix issues for those that have them, but not yet.
[Nexus 7 (2013) General] OsoAlgo:
Thanks a lot! I'm currently using IceCold's AOKP ROM and I could clearly see some ghost touches and weird behaviors using this app. I flashed the ts10 and it seems a LOT better. I'm gonna test it for a few days and see how it goes, before my return period runs out :p
[Nexus 7 (2013) General] G2xer:
Worked Great!

So far so good. I only experienced a mild stuck touch and the keyboard hold bug as well as the ground issues. After flashing ts10 it seems to have solved it all. Got mine in around September 17 not sure when it was built
[Nexus 7 (2013) General] balboarocky:
I have got similar touch/grounding issues in my xperia sp.Can these files be used with my device>?
[Nexus 7 (2013) General] stfudude:
With stock TS firmware, I've got stuck touches when tapping the keyboard, which doesn't annoy me that much since I use Swiftkey Flow typing method.

With modified TS firmware (shared by OP), from TS10-TS30 + TS11 + TS16 ==> I've got major problems like poor sensitivity, ghost touches, no response when grounded and many more issues listed here.

With that I will stay with stock TS firmware because stuck touch is not a major problem for me.

Thanks to OP though, because he's doing something that Google can't fix for certain devices.
[Nexus 7 (2013) General] sciphonic:
TS10 solved my issues. About 2 hours of use and all is well. Really appreciate your work.

Before applying this fix my screen was too sensitive and registered phantom holds and second touches.
[Nexus 7 (2013) General] sfhub:
No.
[Nexus 7 (2013) General] durrantie:
Dont suppose anyone has any idea why i'd be getting the following error while trying to load ts-10?

cannot load 'boot-ts10-lock.img': No error

i'm following this to the letter I think.

Thanks.
[Nexus 7 (2013) General] sfhub:
Are you on windows, Mac, or Linux?

Do you have a permission problem?

If not windows, do you have fastboot executable installed?

Is there a boot-ts10-lock.img in the directory?
[Nexus 7 (2013) General] durrantie:
Ive tried in Windows 7 & XP, 2 different computers.

I must be doing something wrong that's really obvious since no one else seems to have had this problem!

Command prompt as administrator makes no difference.

The TS-10 image is in the same folder, strange.
[Nexus 7 (2013) General] sfhub:
Is it possible something got unpacked incorrectly? Try unpacking with 7zip again.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Hi, just got my new nexux 7 2nd gen 3 days ago. I am experiencing touch issues like what you've describe on your thread. My nexus is build JSS15R. I wanna try these solutions that might fix the problem. I have some clarifications below:

1. Can I install your zips even if when I am not rooted?

2. If I install those zips, can I still receive OS updates straight from google? Because im looking forward for the 4.4 Kitkat update on my nexus 7.

Thanks sir!
[Nexus 7 (2013) General] sfhub:
1 yes

2 yes

These aren't zips to be installed in custom recovery, they are kernels that you boot.

To boot unsigned kernels, you do need to have an unlocked bootloader, but you don't need to be rooted.

Nothing that would affect an ota is changed, so you'll still be able to get kit Kat.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Thanks sir, by the way, how can I unlock bootloader of my nexus 7 2nd gen? I've read the instruction on the first page but still im clueless. Can you tell me what to do first? Sorry for this dumb question :)
[Nexus 7 (2013) General] jzsax1:
Cant Get past the X boot logo

I have a Nexus 7 LTE. it is boot-loader unlocked and rooted. Not running anything special but BulletProof kernel and TWRP Recovery... im following the instructions to the teeth but for some reason when i get to the fastboot boot boot-ts10-lock.img command it gets stuck on the X boot logo and doesn't do anything at all....
[Nexus 7 (2013) General] sfhub:
If you've experienced a 20 second pause after "fastboot boot boot-ts10-lock.img" the work is already done. Wait about 2 minutes to make sure things are settled down, press and hold the power button until the unit reboots. It'll go back to using your existing software, except you've got the new touchscreen software installed.
[Nexus 7 (2013) General] sfhub:
http://xdaforums.com/showthread.php?t=2379618
[Nexus 7 (2013) General] jzsax1:
there is a new app that checks for the screen touch bug in the Google Play store. After flashing TS16 which seems like the one that works the most. i used image pattern 1 and the device starts doing all sorts of crazy things. Should i use this app as reference or should i ignore it after i flash these image files?
[Nexus 7 (2013) General] Treggs:
Just posting to say Thanks and after a bit of testing TS16 seems to have done the job for me too. Oddly my Poetic slimline seems to effect touch performance though.
[Nexus 7 (2013) General] alexoz:
The app seems legit. After enabling the "Show touches" option from developer options and showing pattern 1 in this app, it went crazy with lots and lots of ghost touches. At first I thought something fishy was going on with the app (although it requires no permissions so how could it do that?). Then I also tried this app: https://play.google.com/store/apps/details?id=com.yota.screentest&hl=en which I have used previously in other devices and sometimes my nexus 7 goes crazy in the pattern screens of this app too. I don't have the slightest idea why anything shown on the screen could cause this...
[Nexus 7 (2013) General] mertzi:
I have postponed trying your fix until 4.4 arrives OTA, but what is your opinion on this, do you think there's a possibility that Google have fixed the touch problems? With so many variations, can they really address this correctly if they made an effort?
[Nexus 7 (2013) General] sfhub:
Depends whether your goal is to get that test app working or to get your tab into a usable state.

Imo if you find the tab is usable with your everyday usage, just enjoy it.
[Nexus 7 (2013) General] sfhub:
With a combination of os and touchscreen software changes they should be able to mitigate for most, but I don't know if it will ever be perfect. They'll probably just let the rma and return process take care of the rest.
[Nexus 7 (2013) General] player911:
I wouldn't postpone anything if you don't have to.

Kitkat 4.4 maybe a month away until an official build and that isn't even guaranteed to fix it. This isn't a permanent fix and can always be undone if Google does it better.

Just remember to start with TS10 and give it at least a day along with several reboots. The new driver has to calibrate.

Also TS10 might be a huge fix but 20 or 30 might really hit it home. I used 10 for a month before trying 20 and it was a 99% fix. Actually I don't think I've had any issues with 20 at all.

If you wait, you're just torturing yourself, especially if you're already unlocked. It takes just seconds to flash.

-sent from my LG G2 using XDA Premium 4
[Nexus 7 (2013) General] durrantie:
Sorry sfhub but i'm still having this problem, i'm unlocked on 15R, ADB reboot bootloader works perfect, the unzipped files are located at C:\boot-ts

When I enter C:\boot-ts\fastboot boot boot-ts10-lock.img into command prompt i keep getting the message: cannot load 'boot-ts10-lock.img': no error.

Thanks for your help this far. :cyclops:
[Nexus 7 (2013) General] Wrngway:
The app is legitimate, but I believe what it's showing is a symptom of some other issue that won't effect your device in regular usage. All it does is display an image, but the image has to be displayed at the correct scaling to cause these touch inputs.

I'd recommend enabling "show touches" under developer options. That way you'll see if your touches are indeed registering under regular conditions.
[Nexus 7 (2013) General] mertzi:
Hehe well I did get a whole message erased yesterday when the backspace froze so you might be right. Let's a say i find TSXX to work great AND kitkat includes some kind of fix, wouldn't it make it even better in combination? Or is it possible that kitkat makes a TS that works good on 4.3 worse in 4.4? I wish I understood better how these fixes work.
[Nexus 7 (2013) General] sfhub:
Try this:

c:

cd \boot-ts

fastboot boot boot-ts10-lock.img
[Nexus 7 (2013) General] player911:
Haha. Just have him connect it and teamviewer in and do it.

I've flashed tons of people phones remotely like this!

-sent from my LG G2 using XDA Premium 4
[Nexus 7 (2013) General] durrantie:
That worked perfectly, thank you very much!

Steve.
[Nexus 7 (2013) General] kryostorm:
Works well!

JSS15R on the 16GB model, using ts10 and works well! Seems a little too sensitive though.

Also, I'm getting random reboots now, but not sure if the cause is related to this fix.

Thanks
[Nexus 7 (2013) General] sfhub:
Highly unlikely this fix is the cause of your reboots. It is running on the touchscreen dsp, separate from main CPU/memory.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Device : Nexus 7

Build : JSS15R

Hi, I've tested the boot-ts10. So far so good I like the sensitivity. No more missed and sticky touches for now but still monitoring. For now I like it. By the way, will it be loss if I factory data reset my device? Is it ok to perform factory reset? Thanks!
[Nexus 7 (2013) General] sfhub:
Factory reset is fine. It will survive factory reset, rom flashes, kernel flashes, etc. and stay in place unless/until you run ts-unlock.
[Nexus 7 (2013) General] mertzi:
I took the advice to try ts10 and two days now with no issues at all (knock on wood). So a really big thank you!

Might be worth mentioning that I use Swype keyboard for typing. And I'm on jss15r.

---------- Post added at 04:45 PM ---------- Previous post was at 04:43 PM ----------

Is there a way to see what ts number you use e.g. if you don't remember which one you flashed?
[Nexus 7 (2013) General] Yuccaman:
tbh, I didn't think I had multi-touch problems.

What I did have was a pretty much dead area on the left of the screen when the Tablet was in a stand and not charging....

The first 3 keys in each row on the keyboard only registered about 20% of key presses in the stand...

Touch the tablet with the other hand whilst typing or connect the charger and it worked fine...

Flashed ts10 and I can type once more in the stand without touching or being on charge.

Many thanks for the fixes sfhub !!!!
[Nexus 7 (2013) General] LittleConfucy:
Anyone using Paranoid Android found one package that fixes it?
[Nexus 7 (2013) General] DowntownJeffBrown:
Its different for every screen

>^.^< Sent from meow MotoX
[Nexus 7 (2013) General] LittleConfucy:
I have Paranoid Android Unofficial. I installed ts10 and it worked perfectly, but it progessively got worse? Anyone having the same problem?

Also, when you flash a ROM, does the build change?
[Nexus 7 (2013) General] Si73:
I had 'mild' multi touch problems but it didn't really bother me as I manly just used my N7 to watch films. Recently after selling my Ipad and then using the N7 to browse the web I noticed it more and more and then it became just irritating. Ts-10 worked perfectly for me and I now have no touch screen problems what so ever. I hope Google look at XDA and perhaps look at including this fix in their updates!!! Many thanks OP
[Nexus 7 (2013) General] squeeish:
I'm on stock rom and kernel, rooted with TWRP. TS-30 works for me so far. I want to give thanks to the OP. You saved many people hours of frustration good Sir.
[Nexus 7 (2013) General] Ronde90:
Hi. I keep trying to flash the fix. Every time I flash it in as, it says it flashes successfully but then when the tablet reboots on its own, it never fully boots into the OS and I have to reboot it with the buttons. I've tried all the image files but I can't figure out what I'm doing wrong. I'm rooted on AICP 4.3.1 using twrp. Any help would be appreciated. Thanks.
[Nexus 7 (2013) General] sfhub:
There are some custom ROMs which won't boot with a stock kernel.

As long as you experienced the 20 second pause before the Google splash, then the job is done and the touchscreen software is loaded. Just wait 2 minutes for everything to settle down, then press and hold power until the tablet reboots. You'll be back to using your original kernel with the new touchscreen software loaded. If there is slight instability add in a few more reboots before judging the performance of touchscreen.
[Nexus 7 (2013) General] thecapsaicinkid:
Man, using the Nexus 5 touchscreen makes the N7 feel horrid :crying:
[Nexus 7 (2013) General] iamnotkurtcobain:
Same as S4... Using the S4's touchscreen and then the N7's is without words...

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) General] hrtbrk:
I'm on the jss15r stock build with stock kernel, and after flashing the ts20 all the gost and teleporting touches my nexus7 was having are gone.

Great job man!
[Nexus 7 (2013) General] sfhub:
It is funny when nexus 7 users are so used to suboptimal touchscreens that they are convinced all touchscreens behave this way when you align your fingers.

Then you breakout a Samsung, lg, or even cheap nexus 7 clone from Walmart and show them the touchscreen works perfect.

I guess when you have never known any better you assume your world is normal.
[Nexus 7 (2013) General] destructogirl:
I need help!

These touchscreen problems are really starting to bug me. I came across this and got as far as the first two steps. I'm really crap when it comes to this stuff, so if someone wouldn't mind dumbing it down a lot more for me, that would be awesome! I need this tablet to bloody work properly! Any help would be very much appreciated.
[Nexus 7 (2013) General] sfhub:
Did you unlock your tablet? Unlocking will erase your user data as a security measure so back up your data if needed.

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

Did you unpack the files?
[Nexus 7 (2013) General] destructogirl:
Is there a Google USB Driver for Mac? I can only find it for Windows..
[Nexus 7 (2013) General] jjdoctor:
Man you made my day... :D

I almost gave up on this issue for past one month and was looking for pathetic solutions like sticking a wire to sides or inserting a pin in Headphones jack all the time or to just live with it coz it ws so annoying using the touch screen to type on keyboard or even play those simple games when tablet was lying in bed or a pillow.. There were huge dead areas in screen which would only recognize touch once in 5 attempts, sometimes not recognize even multiple attempts. Those dead areas were spread in all 4 corners of screen.. I was really disappointed with this issue. Never thought a software patch would solve it.

Searching the Nexus 7 forums, I was making sure I am not alone as this problem lasted too long now. I was somehow sure it was hardware issue but your thread is just ingenious and made me wrong.

Before flashing this stuff I tested Touch screen with Multitouch application... Identified all dead areas when it was placed on a pillow. Then I flashed the boot-ts10-lock.img. Rebooted and BINGO !!! the problem was over... Not even a single dead area is identified now... works like a charm lying flat on pillow, bed, table watever...

Thanks a Million mate... :highfive::good:

PS: Version of Software is Clean ROM 1.7, remaining things I have explained above already.. :)
[Nexus 7 (2013) General] sfhub:
I don't think you need USB drivers for mac, just the sdk apps like fastboot and adb.

Try following just the portion of this guide regarding unlocking bootloader (you don't need to root)

http://xdaforums.com/showthread.php?p=44192439
[Nexus 7 (2013) General] destructogirl:
It's perfect

Thank you for the links. I finally figured it out and installed ts10. It works perfectly! After two months of regretting buying this thing, I'm finally using it for the purposes I purchased it for - writing! Is this a good enough occasion to throw a Nexus fixing party?
[Nexus 7 (2013) General] gSantanik:
Thanks!

YOU sir, are awesome! i got the nexus 7 2013 as a gift from my girlfriend four days ago, and i was very bummed to find out that the device was faulty. after finding this post, i thought to myself that maybe i should w8 for the 4.4 and see if it'll resolve the issue. i couldn't live with this tho so i decided to try this out. i don't regret it, to say the least! :p

Nexus 7 2013 16gb

JSS15R

boot-ts10.img

works like a charm - :D
[Nexus 7 (2013) General] GTMoraes:
Btw I had a look at the nexus 7 II screen test. It's legit. I managed to take a screenshot before it goes nuts, and the bug happens on Gallery, upon loading the picture as well.

It also takes a while to load it up.

I've attached it. You can download and see for yourself. Landscape only. Make sure it's full screen :)

(my menu buttons are hidden, Idk if that will alter the results for the people that have the menu button visible)

----

Oh, should have expected that. It compressed it way too much. Here's a direct link. I've been able to bug the hell out of it on Chrome too. Just change the orientation to portrait to stop

[quote="so Tapatalk won't turn it in a compressed picture" ]http://img208.imageshack.us/img208/4215/x6er.png[/quote]

Clickable link:

http://bit.ly/1gATycB

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) General] sfhub:
IMO unless you are going to use that image as the home screen background it is better to work on getting the tablet usable for everyday needs.
[Nexus 7 (2013) General] ryco1008:
Thank you for work on this! My feedback is as follows. I have a month old 7 LTE on stock 4.3.1 JLS36I, only had issues mainly when not grounded. Tried ts10 and fixed most issues except the following day had ghost touches. Tried ts20 and some changes, tried ts30 and again changes but still issues (dead areas). Tried exp ts11 and best one so far, no dead spots or bands on the screen. the only issue is zooming but it is only 2 out 10 times i try it. I hardly use my tablet without holding it and if I'm not holding it it is just to check something quick and be done using it. With how I use the tablet it is no longer annoying and will post more feedback if it changes. Thank you again!
[Nexus 7 (2013) General] LittleConfucy:
Help, I'm stuck on Unforunately, Nfc Service has stopped an Unfortunately, the process com.android.phone has stopped. Can't enter the reboot menu, or through the command prompt!!!

Edit: fixed it
[Nexus 7 (2013) General] The_Stranger:
Thanks OP, you made my nexus 7 even better. Didn;t have a huge issue with the screen, or so I thought, but applying "number 10", it did make a big difference. Now longpressing to select an app in the drawer feel natural, where at first it was something I had to do with care.

So again thanks...
[Nexus 7 (2013) General] Sensamic:
Does the grounding issue disappear with the TS files?
[Nexus 7 (2013) General] sfhub:
Depends how bad your touchscreen issues were to start. In many cases they will be greatly minimized or not noticeable. In some cases they will still persist.
[Nexus 7 (2013) General] fuser-invent:
In my case TS-10 fixed the grounding issues.
[Nexus 7 (2013) General] airmaxx23:
So after flashing any of these files it makes my device take about 4-5 minutes to reboot every time after it's installed. Is this behavior normal?
[Nexus 7 (2013) General] sfhub:
If you followed the directions, after the first reboot, you'll be back to your original kernel so there shouldn't be any difference from what you are used to.

If you are talking about the first boot, then it might take a little longer depending on what rom you have installed.
[Nexus 7 (2013) General] airmaxx23:
I'm talking about any boot up after installation is complete, not the first boot. Without this mod my device is on the Nexus "X" logo for maybe 20 seconds when booting up, with this mod enabled it's a solid 4-5 minutes that I'm on the Nexus "X" before it finishes booting. Once I disable it everything is fine again.
[Nexus 7 (2013) General] sfhub:
I've never seen that installing on probably 30 tablets now.

Are you sure you did "fastboot boot boot-ts10-lock.img" amd not "fastboot flash boot boot-ts10-lock.img"?

That's the only thing I can think of that might explain what you are describing.

The fix loads onto the dsp onboard memory so it doesn't affect your kernel.

By the time you get to the X logo you've already passed the kernel and gone into the android boot which doesn't communicate directly with the touchscreen.
[Nexus 7 (2013) General] airmaxx23:
I'm 100% positive that I'm entering "fastboot boot boot-ts10-lock.img". I recently switched ROM because I was having the long boot issues on the previous ROM. I flashed AICP 3.0 then the touch mod and had the reboot issue, if I dirty flash the ROM and reboot a bunch of time it's fine. As soon as I do the mod then first reboot takes about 4-5 minute and every reboot from then on is the same until I remove it.
[Nexus 7 (2013) General] sfhub:
Ok, maybe that gives some clues to understand what is going on.

I assume you have stuff backed up. Try rebooting to recovery and do a wipe data/factory reset. See if it is still takes a long time to boot.

Also if it isn't too much effort, could you see what happens if you go to stock by doing a factory image restore of one of the JSS15* ROMs, then apply ts10?

BTW which ROM were you on before?
[Nexus 7 (2013) General] yofa42:
works, but...

Works so far for me. I was trying to correct a sticky touch issue. But it unknowingly wiped all my user data. I was greeted with an initial setup screen. Damn... No backups, not expecting that.

Was that supposed to happen?
[Nexus 7 (2013) General] sfhub:
Not at all. In over two months yours is the first post with that outcome.

I'm wondering if you had coincidental corruption of your user data. Are you on stock?
[Nexus 7 (2013) General] yofa42:
yes, stock jss15r.

when i installed it, it wouldn't boot properly. it sat at the nexus "x" logo for 15 minutes until i finally decided to shut it down and boot it up again. then it showed the android flashing progress bar, then booted up with the system language initial setup screen.

maybe it's the way i installed the adb drivers in windows 8.1. i didn't give it a proper reboot. anyway, it's no big deal. i'm well-committed to the cloud. just lost some game-saves.

i'm pretty happy with the outcome given that i wanted to return this american-bought nexus 7, but i live in canada, so best buy canada won't accept the return. a software fix was very much appreciated. thanks!
[Nexus 7 (2013) General] airmaxx23:
The boot times are normal after a factory reset, and I honestly don't remember which ROM I was on before AICP, I switch quite often. Could you please give me a link to your ROM and I'll gladly test it out.
[Nexus 7 (2013) General] sfhub:
Glad your screen is behaving better.

I think you just got hit with coincidental emmc corruption. Not having anything to do with this thread, you'll read scattered posts about folks who rebooted and just got stuck on X without making any changes. Alternately you'll see some people get uidl inconsistent all of a sudden after reboot, also with no changes.