yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] Wezi:
THANK YOU

Just tried fix 10 on my Nexus 7, Build number JSS15Q, Wed Aug 14 11:00.

I had touch issues on the top right of the screen, just below the notification menu within an inch, of the whole side / top. Unlocked the bootloader using WugFresh and Fastbooted the number 10 fix as recommended. Now on the stand, flat surface it recognizes the lightest of touches.

This was going to be my last attempt before returning the device to Tescos were i purchased it from for a replacement. I just wanted to make sure it wasn't a hardware issue.

Feels fantastic, thanks again!!!!!

Oh and thanks for recommending i tried the fix on the thread i posted asking about the touch issue!
[Nexus 7 (2013) General] afremont:
sfhub,

Is TS10 the same as A029? That's what I have loaded right now and it seems to work very well. I was using A038 before, but yamtt would show some strangeness. It works perfectly with A029.

Thanks!

Sent from my aosp N7 JSS15Q w/A029 TouchScreen firmware
[Nexus 7 (2013) General] Crittias:
Just another thanks to the OP. I wasn't really sure that I was experiencing touchscreen issues. The response seemed sluggish or imprecise on occasion, but it was intermittent. I figured it wouldn't hurt to try this fix, and WOW, it's much MUCH better now that I've applied fix 10.

Thank you so much!
[Nexus 7 (2013) General] sfhub:
Yeah, it is like struggling with a twisty puzzle for a week getting frustrated and thinking it is not solvable, then all of a sudden you get a clue and it becomes so easy.
[Nexus 7 (2013) General] sfhub:
It is equivalent to what you are expecting.
[Nexus 7 (2013) General] rubene66:
I flash ts-10 and it fix my touch issue thanks
[Nexus 7 (2013) General] Gekko-State:
Woo. ts10 seems to have fixed my sticky keys issue.

One question though, when using YAMTT (touch tester) my multitouch still goes to **** when the axis cross over one another (lying down with a cover, 3 or 4 fingers) is this the hardware grounding problem I've been reading about?

Want to know if I should keep trying to fix it or if I should just take it back for replacement.

In an unrelated note, this is my first nexus product...And I can't say I'm happy with it. :/ Shame on Asus & Google.

Viva La XDA though, this forum is still a beast....a sexy, sexy beat. :laugh:
[Nexus 7 (2013) General] sfhub:
It's a variance on the touchscreen hardware. Theoretically the touchscreen firmware should be able to handle it but it isn't clear if it is within a range that can be handle by a single touchscreen software.

I'd try some of the others and maybe the experimental ones in the second zip file. TS20 should help with the multi-touch but you might have reduced sensitivity in some areas (or you might not)

Sometimes the tester will show spasdic multi-touch but you don't actually use that motion in real-life so it doesn't really affect you. Sometimes you can slightly modify your motions to avoid the issue, like starting/ending your pinch/zoom with fingers 1" apart.
[Nexus 7 (2013) General] benjdm:
I am running stock JSS15Q. I was having problems with touches holding long when I wasn't doing long touches and scrolling jumping back when I next put my finger back down and tried to scroll. Also with touches not registering at all. HW says rev_E. Ts-10 seems to be helping immensely.
[Nexus 7 (2013) General] PJ Clifford:
BYW, isn't it about time to sticky this thread?
[Nexus 7 (2013) General] rafa3L:
sfhub: Can we get a description of the differences between these magic files?

I'm surprised we haven't heard a peep from Google in their forum recently. Or maybe I'm not. Hopefully they haven't completely given up on the issue. Its hard to believe that tons of people that have these tablets, that aren't aware of these forums, are not having these issues. I think many more are but are writing it off as a sensitive touch screen. Although we have had several reports of tablets with no problems from people that do visit these forums. So I guess it is possible that we are the minority? Hopefully my fourth device which arrives Tuesday will be 'the one' for me.
[Nexus 7 (2013) General] jogu73:
My device was broken from day one and after a few days it got to the point where it didn't even register single presses. So after alot of frustration I decided to try this one out and ts10 fixed the touchscreen problems for me :)
[Nexus 7 (2013) General] DowntownJeffBrown:
I have 2 n7 tablets. I ordered my original from the play store and I just received a replacement from the play store last week. My first one was perfect until the latest update to Q and that caused my tablet to have missed touches. So I ordered a replacement which has totally out of wack multi-touch. So I ran all three of your fixs on each tablet. Ts10 completely fixed my single touch issues on my original device so I'm sooooooo happy. My replacement device however was so far gone that none of the three files were able to fix is multi-touch issues although ts10 would have made the tablet usable. So anyways I'll be keeping my original n7 now that is got no touch screen issues thanks to sfhub and I'll send my replacement back to Google. I just really wanna thank you sfhub for all the work you have been doing for everyone in this forum. You have been front and center with this issue since day one and have been selflessly helping others when Google won't. You are what makes xda a great place :):beer:

>^.^< Sent from meow HTC One ?
[Nexus 7 (2013) General] astuermer:
Is it possible to get that as CWM/TWRP flashable ZIP?

Thx! :good:
[Nexus 7 (2013) General] sfhub:
While I could force this into a CWM/TWRP flashable zip, the procedure is set up this way by design because the goal is to isolate just the repair of the touchscreen software and lock in one that works. Everything else would be the way you had it originally.

By making a CWM/TWRP flashable zip you'd be forced into running a different kernel which might not even be compatible if you are running a custom or older ROM.

The only real advantage to a flashable zip is you'd be able to do it without a PC, but this isn't something you are going to be running all the time, so it doesn't seem like a big deal to wait until you are around a PC.

So yes it could be done, but it would probably add confusion, and I won't be doing it, even though it is trivial to do.
[Nexus 7 (2013) General] astuermer:
Oh ok I understand. That makes it clear ;)
[Nexus 7 (2013) General] ramdyc:
I was having problems with touches holding after I'd release but with ts10 it's not happening anymore. Thanks for this!

::EDIT::

After trying ts10 for awhile it was giving me a little problem in flipboard when I would scroll up with one finger it'd occasionally react as though I was pinching to close an article. Trying ts20 now and seems to be better.

::EDIT 2::

Ok after trying ts20 for a couple of days I have gone to ts30. This seems to be working the best out of all of them.
[Nexus 7 (2013) General] Reckoning:
I updated to JSS15Q and screen touches went bad, installed ts10 and back to normal. Many thanks!
[Nexus 7 (2013) General] Gekko-State:
[MENTION=1299673]sfhub[/MENTION] Ahhh. Thanks that clears things up. So what exactly is the grounding problem I've been reading about then? Trying to get a grasp of it...but Information on it varies wildly in terms of what it's symptoms are.

Like Nessie....or a female orgasm.
[Nexus 7 (2013) General] deezid:
How long should the boot after the install take?

I rebooted mine after 10 Minutes still showing the nexus (X) bootscreen. Didn't notice any difference after the reboot. :(
[Nexus 7 (2013) General] sfhub:
There should be a 18-24 second pause, right at the start after fastboot boot, then it should continue booting as normal.

As long as you got that pause, the touchscreen software is installed.

I would just press and hold power to reboot.

BTW are you running a custom ROM that requires its own kernel?
[Nexus 7 (2013) General] deezid:
Not using any custom rom (Nexus 7 2013 LTE razorg deb europe). ;)

Tried that, too. But I'm not sure if the driver is installed... The bootloader halts about 12 seconds then the Google Logo appears, then the X screen and stays there for hours... (I rebooted manually after 10 minutes).
[Nexus 7 (2013) General] sfhub:
Are you saying it is still stuck on X currently when you are booting or it is booting ok now and it was just the first reboot that hung? As long as you saw the Google logo the first time, the touchscreen software is installed.

If it is still on X now when you are booting, let me know.
[Nexus 7 (2013) General] deezid:
It rebooted just fine after I rebooted it manually. So everything should be ok I think.

Noticed no difference though. Swype is still acting strangely... I switched back to the aosp keyboard and everything seems to be fine. :)
[Nexus 7 (2013) General] sfhub:
Which ROM version are/were you on?
[Nexus 7 (2013) General] deezid:
Stock ROM.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) General] sfhub:
What I meant was which version of the stock ROM are/were you on:

JSR78D

JSS15J

JLS36C
[Nexus 7 (2013) General] deezid:
JLS36C, TWRP 2.6.0.0 installed.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) General] Chadneu:
So after flashing ts10 i thought my issues were gone.

It occasionally seems to re-calibrate itself incorrectly, specifically along the top row of keys on the Google Keyboard and along the right side(sometimes when I hit backspace itll hit enter)

When it does this there seems to be a dead area where touches aren't recognized, and when touches inside the dead area are recognized they don't apply inside of the area, it moves the touch outside of it.

Additionally, sometimes when scrolling it will randomly detect a second touch/input right next to the correct one. After scrolling a little more the second touch disappears.

A restart doesn't really fix it, it just eventually goes away.

I haven't tried ts20 or ts30

I apologize if my descriptions are bad. :)

Edit: Tried out the ts11 exp and it works a lot better so far. Thank you :)
[Nexus 7 (2013) General] astuermer:
Which firmware version JSS15... are you on and which HW-version does your Nexus 7 have?

Thx.
[Nexus 7 (2013) General] Chadneu:
Jss15q and jdi/Japan display
[Nexus 7 (2013) General] astuermer:
how to find out my display or touchscreen version?

I am on JSS15Q too.
[Nexus 7 (2013) General] Chadneu:
There's a beta app called Voodoo. Have to join the google+ community and then download it.
[Nexus 7 (2013) General] kh5:
Hi, thanks a lot for this!

ts10 solved the problems on my device (at least as far as I can tell).

I had a horizontal strip in the middle of the screen where touch inputs would not be registered correctly. Was especially annoying as it would break scrolling an then register a tap when I reached the part where it worked again.

I have version JSS15Q on the device. (It might have worked with the version it came with out of the box, but I can't really tell, since I installed the update shortly after unboxing.)

P.S.: Is it possible to donate to you somewhere? This is such a help that I would gladly donate some money to you.
[Nexus 7 (2013) General] sfhub:
Glad it helped. Thanks for your kind thoughts. No donations necessary.

I just put this together to help address issues I was encountering and thought it could help others.
[Nexus 7 (2013) General] NekroWolfen:
Just to be clear, with what I have read, after I've done this I can flash any ROM, restore, back up and a lot more flashing but this will not be deleted since it's locked right? So practically this is a "one time" thing, given that I've found the one that solved the issue. Please someone correct me or confirm this. :) thanks for the patience.
[Nexus 7 (2013) General] PJ Clifford:
Pretty much, yup! You CAN always unlock the TS update and go back to whatever version you were running prior to flashing, if you feel the need.
[Nexus 7 (2013) General] sfhub:
Yes, what you and PJ Clifford said are both correct.
[Nexus 7 (2013) General] NekroWolfen:
Thank you both for confirming this so fast! Will try as soon as I get home!
[Nexus 7 (2013) General] Imppy:
Will this solve the problem whereby the touchscreen becomes totally unresponsive and that I need to restart to solve the problem?
[Nexus 7 (2013) General] sfhub:
I've only seen touchscreens that become temporarily unresponsive, which this did address, but if your screen is becoming permanently unresponsive, until reboot, then maybe not.
[Nexus 7 (2013) General] rmagruder:
Wondering if anyone has seen this behavior (I haven't seen it mentioned on this thread so far)

With TS10: When I get a notification, I enter my PIN to unlock the tablet and then try to swipe down -- nothing happens for 5-7 seconds, and then the notification area comes down (often to the bottom of the screen). Also, it seems SystemUI is somehow locked up, because it only paints the recent apps navbar button for that same amount of time. It draws the home and back navbar buttons around the same time the notification drops. I set developer options to show touches, and see the touch happens immediately, but SystemUI just doesn't react for 5-7 seconds.

This doesn't seem like it should be related to ts10/touch screen, but when I flashed ts20 or ts30, the problem seems to have gone away. I returned to TS10 only because I was getting 'missed touches' in the other ones, and sure enough the 'wait a minute while I get my stuff together' lag came back.

Is there anything you can think of with ts10 that might impact SystemUI/NavBar/Notification bar delayed responses on unlock?

Thanks,

Randy
[Nexus 7 (2013) General] sfhub:
The only thing I can think of is if you missed/skipped the mandatory reboot after booting TS10 the first time.
[Nexus 7 (2013) General] rmagruder:
Each time I flash, I do a second album reboot after it boots up. Nonetheless with nothing to lose I rebooted again and the problem seems to have gone away for now. I'll keep watching it to see if it returns.. Thanks!
[Nexus 7 (2013) General] aerdely:
Thanks, flashed boot-ts10 and seems to have fixed my sticky key issue, also seems a little more responsive. Worked great.
[Nexus 7 (2013) General] Coronado is dead:
TS10 made my multitouch a tiny bit worse, but my ungrounded single touch perfect. Will stick with that, thanks TC! Time to try another ROM with this new found single touch goodness :)
[Nexus 7 (2013) General] NekroWolfen:
I'm running CarbonRom sep-10 for flo, and sadly there was no improvement. But the process was smooth and your instructions are clear, maybe mine won't help it. I took my time to test it all, rebooted even 3 times after each "ts.img".

Just curious, I know there's meant to be instability after the first boot and to ignore the first boot after locking an TS(and I did) but is this normal?

"Unfortunately, the process com.android.phone has stopped" - Is the notification pop-up that appears after the first boot. And on top of that pop-up it appears another one.

"Unfortunately, Nfc Service has stopped."

I am not able to "abd reboot" nor reboot by pressing the power button menu because the pop-ups won't allow me to press it. So I always did a hard reboot by turn it off and then on.

If that's normal then I did everything right and my Nexus won't improve, thanks for your help.
[Nexus 7 (2013) General] sfhub:
It is normal because you are booting off of a stock wifi kernel, which isn't harmful, but might not work with the custom ROM.

When you say no improvement, does that mean no change or just no improvement. You should see at least some change in behavior, but not necessarily completely fixed.

Was there an 18-24 second pause after you boot TS10? As long as you got that, the touchscreen software should be loaded.
[Nexus 7 (2013) General] NekroWolfen:
With ts-10 there was no change, with ts-20 and ts-30 it was actually worse, and yes there was the pause. I'm gonna try again with ts-10 and keep it for an entire day to test further, I'll comeback tomorrow with the results or before if it becomes worse.

By the way, those ts-15...ect it may help? For example, if there was no change with ts-10 and ts-20 got it worse, I could try ts-15 right?

Edit: I meant ts-14
[Nexus 7 (2013) General] sfhub:
Yes, sometimes the experimental ones will help. Most will be good with 10, 20, 30, so that's why I keep the experimental ones in a different download.

You might just have one of those touchscreens that are too far off to be made usable. One out of the 4 I tested with was like that.

However, I would let it run overnight, sprinkling in some reboot fairy dust. I've noticed, sometimes the behavior will change a little over time, probably due to some internal calibration.
[Nexus 7 (2013) General] NekroWolfen:
Ok, I'll do the ts-10 and keep it for a day, thanks a lot!
[Nexus 7 (2013) General] frankhart:
sfhub, you've made my day :)

Issues I had: there seemed to be a dead 'row' in the upper area of the screen, so when I was scrolling, the swipe got interrupted and interpreted as a click. Very annoying. I also had the multitouch issue, the know one where it goes berserk when being placed on a flat surface.

I live in Holland, and as I bought the N7 in the US, I was not very eager to return it. And I don't need to, because after flashing ts10, both issues are completely resolved.

Thanks a lot!
[Nexus 7 (2013) General] uprightbass360:
Man, I'm right with you. I thought I was in the clear. I went and bought this unit 3 days ago, and multitouch looked good (turns out I just did a bad job testing in YAMT) then started noticing bad keyboard accuracy. I then sat down and spent a bit more time in YAMT, and thats when I was able to see how bad it was(alsmost as bad as the videos). After trying all your packages tm10 seems to fix it. the test does show the dots jittering around a little bit, but I wonder if they may be able to actually fix this with yet another patch...? Is this really something that is "fixed" by rma?
[Nexus 7 (2013) General] sfhub:
IMO best way to keep your sanity is by focusing on getting the touchscreen to the point where it is day-to-day usable. By that I mean you don't notice touchscreen issues in everyday usage.

If you try to focus on getting a perfect YAMTT test, you will get very frustrated. There are units that have no (or almost no) jitter, but they are very hard to find and IMO it just isn't worth the trouble.
[Nexus 7 (2013) General] uprightbass360:
Well thank you for spending your time on this issue and responding to all of our questions. I am not going to be another one complaining about how horrible asus is, but as far as bugs go, this one is definitely frustrating.

Well I have a 7-2013 model, and after reverting back to the ts-unlock, the screen seems about as good as it gets. Maybe I was just needing to see the issue in full glory before I understood the improvement. Is it so much to want your nexus to be perfect?
[Nexus 7 (2013) General] sfhub:
Just remember when you unlock, you are at the mercy of whatever software you run.

If you run TWRP, you'll get what touchscreen software twrp's kernel came with. If you take an OTA update, you'll get that one.

Personally I'd recommend you stay locked on the one you find works the best.
[Nexus 7 (2013) General] uprightbass360:
Well maybe you have a recommendation, when I run stock, it runs kinda glitchy. then it gets more severe with the locked ones 10 - kinda bad 20-worse 30-totally unusable. Coming back to the original seems to be about as stable as I can get it.
[Nexus 7 (2013) General] sfhub:
I recommend you run TS10 and then do a couple of reboots.
[Nexus 7 (2013) General] NekroWolfen:
[MENTION=1299673]sfhub[/MENTION] Hey, I know I said one day but it's been less than half day and I already notice the difference lol You were right, more reboots and keep using it works. I'm using the ts-10, by the way this also resolve the occasional freezing(2-3 seconds)? Because normally I'd have like 8-10 small freezes by now. But I haven't got a single one since I did this, it's related? This also fix that too?
[Nexus 7 (2013) General] uprightbass360:
K gonna give it a go, I'll let you know how it goes.
[Nexus 7 (2013) General] sfhub:
Short touchscreen freezes, yes, it will resolve those.

However, sometimes you get app freezes that may seem like touchscreen freezes. Those are issues with the app or with android so wouldn't be resolved.

The way to tell the difference is to turn on show taps and pointer location in developer options. If the screen is registering, but things are hanging, then it is the app. If the screen isn't registering, then it is probably the touchscreen (or android is in the process of crashing)
[Nexus 7 (2013) General] uprightbass360:
You were right :) been tinkering for a couple hours and the screen issues are livable, none of the glitches I was having before. I wish I could figure out whats giving me all my force-closes though ( I don't know the first thing about logcat )
[Nexus 7 (2013) General] eyeisdasteve:
Hey just wanted to share my experience.

My touchscreen was working fine out of the box. After about a day or 2 of use I noticed the keyboard sticking and it acting kind of laggy in some apps or scrolling on web pages. After using it for a while it sort of subsided. I started flashing mods and using root apps etc. I started noticing it again. So I came here because I had saw the thread before and thought to myself "Worst case...:D". So I flashed the t10.img and everything is working great.

Thank you for this!
[Nexus 7 (2013) General] jack1984:
Same here, Ts-10 fixed my issues completely (it seems). Really glad I held on to the tablet and didn't return it.
[Nexus 7 (2013) General] lch920619x:
Works like a charm, increased the touch responsiveness of my N7 a lot. I used the ts10 file, even didn't bother to check the other 2.

Thank you very much!
[Nexus 7 (2013) General] ksey3000:
Panel manufacturer: JDI/Japan Display

ROM: PA 3.99

Kernel: ElementalX 1.4

Ts-10 fixed my issues completely and increased the touch responsiveness.

Thank you very much!

Отправленно от моего Nexus 7 с помощью Tapatalk 4
[Nexus 7 (2013) General] trvbone:
Where did you find panel manufacturer?
[Nexus 7 (2013) General] ksey3000:
There's a beta app called Voodoo. Have to join the google+ community and then download it.

Отправленно от моего Nexus 7 с помощью Tapatalk 4
[Nexus 7 (2013) General] dgm9sf:
Fix for N7.2 Bluetooth Keyboards?

So, we have a fix for the multi-touch issues. Is there a fix for bluetooth keyboards' repeating and runaway keys issue?
[Nexus 7 (2013) General] Skinnysloth:
Lived with TS10 for awhile and the random dead bands got annoying. There was even one instance of ghost touches even while holding the tablet. Ghost touches weren't present if the usb was plugged in. Of course a reboot fixed the ghost touches. So, I decided to test the experimental builds, loaded up TS11 with the following results:

1. Ghost touches when using three or more fingers. This is a non-issue with day to day use, as at most, I use two fingers for zooming in and out.

2. No more dead bands/spots after triggering ghost touches! So far, I haven't seen any dead bands or spots after triggering ghost touches. Will see if this continues with extended use.

The other experimental builds gave similar or worse results compared to TS11, so I just sticking with TS11 unless the dead bands/spots show up. So, if you still have some issues with the one of the TS10, 20, or 30, make sure to test the experimental builds as well. I'm glad I did.