yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
If you've noticed no change in behavior at all (good or bad) between ts10, 20, 30, then the touchscreen software might not have been loaded properly.

However, if you've noticed some change in behavior, but still have issues, then you might want to try the experimental ones in the 2nd download.
[Nexus 7 (2013) General] sfhub:
You should be able to get back to previous behavior. Have you tried downgrading to JSS15Q and then loading ts20?
[Nexus 7 (2013) General] brashmadcap:
Noticed some change for sure and have tried them all I think I may have a defective unit :(
[Nexus 7 (2013) General] gizmik:
Not yet, I have nandroid backup right before upgrade to 15R, will restore when I get home :)
[Nexus 7 (2013) General] player911:
Sfhub, Can you confirm the 15R doesn't have any touchscreen updates? I don't think it did but haven't actually seen a yes or not. Most people are saying it isn't changing anything even if it did.

Also is your fixed based off of 15J? I'm just curious if they are. If they aren't, is it possible to get a zip of the stock 15J driver?

Both 10 and 20 are working great but it seems like 10 would get buggy in landscape after a while. Toggle screen fixes it. 20 seems it disconnect/freezes after a while. Both are just for a short time, maybe 5 seconds.

Its not noticeable in normal use other then gaming. 20 seems best so far over using 10 for a while.
[Nexus 7 (2013) General] sfhub:
The touchscreen firmware that runs on the DSP was unchanged between 15Q and 15R.

That is not to say there were no changes that could affect the touchscreen as there could be areas on the Android-side that affect touchscreen processing, just that those changes are not in the touchscreen firmware.

Most people will probably see no difference, but some might.
[Nexus 7 (2013) General] threepwood960:
I have Q, and initially I had every reported problem with the screen (tablet made on June). The tech support exchanges the screen (http://xdaforums.com/show....php?t=2452064), and everything was ok during 2 days. Then, next to the first charge, started the problems again, though more subtles: maps doesn't rotate, and ghost touches sometimes (the trace in Swype keyboard is sometimes broken).

I am trying the ts10, but obtain this one:

X:\boot-ts>fastboot boot boot-ts10-lock.img

downloading 'boot.img'...

OKAY [ 0.280s]

booting...

FAILED (status malformed (0 bytes))

finished. total time: 0.320s

Any idea?
[Nexus 7 (2013) General] sfhub:
Check the MD5 of the boot-ts10-lock.img

It should be

boot-ts10-lock.img

f140097acaf323b0ed08cba43b303f1e

If the file isn't corrupted, either there is a problem with the usb connection or this is some one-time hiccup.
[Nexus 7 (2013) General] threepwood960:
The MD5 is ok and also the USB connection, I think. I use also the "Nexus Root Toolkit" in the same computer, and it works rigth.

I don't know what more I could try.
[Nexus 7 (2013) General] sfhub:
Are you on WiFi N7.2?

does

fastboot boot twrp.img

work?

Download TWRP and rename it to twrp.img for convenience.
[Nexus 7 (2013) General] threepwood960:
I have TWRP recovery now. I flashed with Nexus Root Toolkit, because I am a newbye.
[Nexus 7 (2013) General] sfhub:
I think it is probably something relatively simple but it isn't coming to my head right now. Did you happen to wipe/erase /cache?
[Nexus 7 (2013) General] milan_gondor:
ota

quick question.. i want to try this fix for my touch issue and i will have to unlock my bootloader which will wipe my data..

so if i keep my bootloader unlocked, will i get any future OTA updates? i dont want to stop OTA updates on my nexus.. so should i keep my bootloader locker or unlocked?
[Nexus 7 (2013) General] DowntownJeffBrown:
You will still get the ota updates as long as you stay completely stock. So your answer is yes you will be fine if you leave your bootloader unlocked.

>^.^< Sent from meow HTC One
[Nexus 7 (2013) General] threepwood960:
Yes. In fact I now am wipe reset and testing J compilation, which I had when I received the tablet from tech support and it worked right.
[Nexus 7 (2013) General] Josh98:
Thanks a bunch! TS-10 seems to have worked great!

Running PA, Franco r3.

PROBLEM: Single touches not being responsive when tablet was lying flat and not charging ('grounded' apparently is the term).
[Nexus 7 (2013) General] maple4star:
JSS15R

Updated to JSS15R, left TS-10 locked as touchscreen generally works fine with it. Can report no noticeable problems with anything so people should be good to go. I didn't try unlocking TS-10 and updating though, so I can't speak about if you're stock and unlocked.
[Nexus 7 (2013) General] sfhub:
I don't remember what fastboot does with a temporary boot and whether it needs to store stuff or loads directly to memory.

Try again after you've booted into Android.
[Nexus 7 (2013) General] threepwood960:
Thanks, but no way.

I now am trying "Flash Stock & Unroot" and it hangs up in:

Writing bootloader
[Nexus 7 (2013) General] GrillMouster:
ts10 worked for me.
[Nexus 7 (2013) General] Nbsss:
ts-20 is looking better
[Nexus 7 (2013) General] bandit_knight:
What the real difference between t10, ts20 and ts30? Is it so that the higher the number the more sensitive the touchscreen will be?

My device seems to perform better with ts20 when it comes to supporting multi-finger multitouch and fingers placed on a single axis but it also have tendency to generate ghost touches.

With ts10 ghost touches are non existent but multitouch seems to be quite jumpy when I use multiple fingers placed on a single axis, crosing axis (3 fingers) or when I make a rectange with 4 fingers on its corners.

Also with any fix the sensitivity seems to fluctuate. For instance sometimes the screen can register "touches" when I place my finger a few milimiters above the screen and sometimes I need to really touch it. I guess that may depend on how much statically charged my body is.
[Nexus 7 (2013) General] threepwood960:
Problem fixed but none file is useful for me.
[Nexus 7 (2013) General] sfhub:
what was the problem causing the fastboot boot to fail?
[Nexus 7 (2013) General] threepwood960:
Well, I use Linux but I use a virtual machine with WindowsXP for modifying my mobiles and tablet. But the hard drive of the virtual machine got full and I put the image files in a shared drive, where seems that it wasn't rightly accessed.

This morning, I tried again on my work computer and everything was ok.
[Nexus 7 (2013) General] Roman2K:
@sfhub

boot-ts10-lock.img fixed the erratic touchscreen bug for me (after following the OP to the letter).

What I used to do to reproduce the bug was to:

Drag icons around in Nova Launcher. The icon would be dropped somewhere unexpected even though I wasn't done dragging. Sometimes there would even be ghost taps on the icon, launching the app... very frustrating.

On a web page (default browser or Chrome), long article, double tap to zoom on a paragraph and scroll down sliding a single finger toward the top. While dragging the page up, double ghost taps would zoom out... even more frustrating.

All solved now. I can't thank you enough.

UPDATE: Playing in YAMTT for a few minutes, no glitches from 1 to 5 fingers.
[Nexus 7 (2013) General] Floraflora:
Is turning on USB debugging absolutely essential to making the process work? The upgrade made my touchscreen so bad that I don't think I'll be able to do that. I did the reset to factory defaults as my first troubleshooting step and I could just barely get back on the network. It takes a bunch of fiddling to get the screen unlocked; I was able to get back on the wireless network only by turning off all security (entering a password just wasn't happening).
[Nexus 7 (2013) General] bandit_knight:
You may boot your device into bootloader by starting it up with Power + Volume Down. Once in bootloader you should be able to use fastboot command from your PC.
[Nexus 7 (2013) General] gizmik:
OK, at least I went back to 15Q (had crazy week) but strange thing is that I still had issues in YAMTT, nothing special but some strange movement of lines (like negative magnetic field) when 3rd or 4th finger crossed them, finger unregistering when crossing the lines etc.

But I know that is out of logic, right? Maybe I just changed testing method with YAMTT and before just don't observe this issues.

None of your images removes them completely, still ts20 was closest, better than ts10 in some scenarios, but worse in others.

Then I tried experimental one, ts14, because I thought I need something between ts10 and ts20 :D If you designed them that way )))

And you know what, right now ts14 is working like a charm, I can't reproduce any of the issues mentioned above, played with YAMTT about 5 minutes......yet I'm afraid to try harder, I don't want to see problems anymore :D

Thank you one more time sfhub
[Nexus 7 (2013) General] sfhub:
Once you get something working, my advice is you just move along and enjoy the tablet.

If you spend too much time with the touchscreen under a microscope it will just give you more anxiety.
[Nexus 7 (2013) General] gizmik:
yep, agree with you completely.

uninstalling YAMTT right NOW :D
[Nexus 7 (2013) General] bandit_knight:
[MENTION=1299673]sfhub[/MENTION]

Is there any way that any of your fixes may help with "grounding issues"? I mean my device is all ok with ts10 and ts20 when held in a hand but when placed on a table it freaks out. It fails to properly register pinch to zoom or roation gestures. YAMTT shows jumpiness and ghost touches appearing between two fingers when trying to rotate or scale map or image. That all only when "not grounded".
[Nexus 7 (2013) General] sfhub:
Depends on your screen severity.

On many units you can eliminate, or minimize to the point you won't notice in regular usage, what you are referring to as "grounding" issues.

Most of the feedback you seen on this thread is for the tablet on a table, not held.
[Nexus 7 (2013) General] Jeerath:
Thanks so much! ts10 works perfectly on my JSS15R Stock with franco3 kernel! Now I can finally highlight text in pdf without having the screen "explode" on me.
[Nexus 7 (2013) General] x4sper:
You sir are a magician! Thank you! You saved Google a return!
[Nexus 7 (2013) General] maidangisme:
amazing Job, Ts10 work flawlessly on mine, mine just had minor response touch, after flash this it look like problem almost gone.

ps: I'm on Custom AOKP JLS36G FLO.

Do we have to flash TSxx every time we update new Rom?
[Nexus 7 (2013) General] sfhub:
Nope, what you have is locked in (will stay in place) until you voluntarily choose to go back to what came with the ROM by using ts-unlock.
[Nexus 7 (2013) General] player911:
Try some of the others to see if one works best.

I just tested mine on a table and no problems. I also tested using a stylus and same result. I'm using TS20. I DID have those problems before.
[Nexus 7 (2013) General] cj10488:
Thank you soo much ts30 seemed to fix my perfectly. I was having random issues with mine since I got it 2 days ago. But after trying out ts10-20&30 it seems as though 30 is the best. They all seemed better than what was originally on there.

thanks again its been more than appreciated.

James
[Nexus 7 (2013) General] maidangisme:
I never able to draw (test) perfect line with some touch screen test, before i flash TS10 the line as image below always breaking up not perfectly joint.

-So TS10 work perfect for me.
[Nexus 7 (2013) General] bandit_knight:
I did some more testing also with the experimental builds. On all of them I experience ghost touches when using two or more finger gestures.

It starts from pretty rare random ghost touches (on ts10) to more frequent ghost touches on ts20 and ts30. Pretty much the same on the experimental builds.

I would pretty much ignore it but at some point it started to occur in apps and games. For example in Worms 2 Armageddon that uses pinch to zoom and two fingers pan gestures when I was trying to zoom or pan it was "generating" a ghost touch on the task switcher soft key. Sometimes even when "grounded".

Then I reverted to the stock with ts-unlock and it seems that all the ghost touches seem to be gone. There's one case when I can observer some ghost touches. It's when I zoom out all the way and my fingers meet. But that has no visible effect in actual apps. All zooming and panning with two fingers seems to be ok when both "grounded" and "not grounded".

It would be all great if I weren't experiencing the "stuck touches" that were non existent with [MENTION=1299673]sfhub[/MENTION] fixes. They occur every maybe 5-10 minutes when typing on the onscreen keyboard. I haven't experienced any touchscreen freezes yet but I guess they may come in time.

Now the question to [MENTION=1299673]sfhub[/MENTION] comes. Can a fix be made this way it only eliminates the stuck touches without introducing the ghost touches? Maybe my interpretation of what the fixes actually do is wrong but it seems to me that my touchscreen becomes a little too sensitive with ts10 and way to sensitive with ts20/ts30.
[Nexus 7 (2013) General] jogu73:
My issue is as follows. In YAMMT, if I touch the screen with two fingers and then release one finger (red) while holding the first (blue) still, the (red) touch gets stuck. This is noticable on stock and all the images, except for ts10. With ts10 I get frequent ghost touches when crossing lines though and sometimes dead spots, so it's less than optimal. I'm on JSS15R.
[Nexus 7 (2013) General] rockingondrums:
I was experiencing what people are describing as the grounding problem. Went all the way up to 30 and it seems to be fixed. LTE (deb) version.
[Nexus 7 (2013) General] Yadao:
I don't fully understand how this did it, but it fixed my "grounding" issues it seems. I had the problem where single touches would rarely register when the tablet was laying on my desk without being plugged in.

I used ts10 on a stock JSS15R build and it's working perfectly now. :victory:

Update: Ok it's not 100% perfect. There's still some very slight "dropping" of touches when sliding. I noticed it when re-sizing widgets. Overall, the responsiveness is still much better than stock.

I tried ts20 and ts30 but they made the touch issues worse. Even worse than stock it seemed. Went back to ts10.
[Nexus 7 (2013) General] sfhub:
Use TS10 overnight and sprinkle in a couple of doses of reboot fairy dust. It sometimes takes a little time to stabilize.
[Nexus 7 (2013) General] bandit_knight:
Hi sfhub. What do you recommend if I do not have any issue with sensitivity on stock. Pretty much no missed touches or dead spots. The only issue is that sometimes it registers long press instead of a single touch. With your fixes I am experiencing less or more severe ghost touches but the "long press" issue is gone.
[Nexus 7 (2013) General] sfhub:
I haven't read back far enough to see if you have tried the experimental ones.

Also in case you haven't, consider whether the ghost touches are present in normal operations or only in extreme forced testing in YAMTT. Sometimes if you are focusing on reproducing the ghost touches, you lose track of whether you'd see them in every day operations.
[Nexus 7 (2013) General] Ricowan:
Hey guys. I'm one of those that hasn't had any problems with the touch on my tablet. But all that changed with JSS15R. Now I'm seeing lots of ghost touches when using the on screen keyboard, clicking links on web pages, etc. I really don't want to have to try each of these fixes to see which one works the best, is there really no way we can discover which hardware we have so we know which patch to use?

Would the various hardware configurations correspond to serial number blocks?
[Nexus 7 (2013) General] destroyer2usa:
After the ADB REBOOT command I get a device not found error and my nexus 7 now hangs at the turn of screen with a message:

NFC service stopped

proces.com.android.phone stopped

and I cann't get any further.

How to proceed?

Bootloader was unlocked before applying the .img but in the background i see now a locked lock on screen.

Phew...Got it finally to shutdown and restart again.

Looks to be working just fine again...

Not good for my blood pressure with my 1-day old nexus.

When I visit this website with my nexus 7 the page keeps on refreshing all the time... Only website I have that problem with.

Thought I flash this touchscreen software to see if it fixes that but nope.

Must be due to something else...AOSP browser also keeps on refreshing...the same like Opera my main browser.
[Nexus 7 (2013) General] rafa3L:
sfhub: Could you provide a description of each of the files so we understand what we are loading and the differences between them?
[Nexus 7 (2013) General] Caldair:
:D Thanks for all your work on this [MENTION=1299673]sfhub[/MENTION]!!

I have a July manufactured device (for what it's worth) and updated to and have been running on JSS15Q since day one with this, so I had nothing to compare my screen behaviour to, before this.

On 15Q I was experiencing sticking touches and one finger slide sometimes being perceived as open-pinch gesture (probably because initial touch stuck and moving away was seen as 2 points)

I tried all 3 files, for comparison, and put the tablet through some touch exercises with each. Thanks for providing all 3 versions so they can be easily compared! Here are my results for each version:

boot-ts10-lock.img

-Fixed my sticking touch issue.

-Multi-touch was very erratic. (With show pointer enabled, slow pinching motion makes the 2 touch points seem to move around under each thumb, the pointer trails left look like 2 sine waves, rather than 2 straight lines)

-Touches were sometimes not registering when the device was not being held in my hands.

boot-ts20-lock.img

-Fixed sticking touch issue.

-Multi-touch was much smoother (Maybe a little jumpy, but I had it under a microscope, so to speak, and was moving my fingers slower than anyone ever would in practice. Pointer trails when pinching were nice straight lines)

-Some lost touches when not actually holding device, but seems better than above.

boot-ts30-lock.img

-Sticking touch issue present.

-Multi-touch is smooth as silk.

-Still some lost touches when not physically holding the device. (But this is the least of my concerns by far. I never use the device this way, and only knew about this and tested for it because others here had reported it.)

Thanks again for providing all the versions like this. It is neat to be able to track the work through the fixes to see what attempts have been made to alleviate the issue.

For me ts20 is a keeper for now. I think that there is still some room to fine tune things, and I look forward to Asus/Google's next try, but at least I can use this now, without wanting to throw it across the room!

Thanks again sfhub! Google owes you at least $200 Canadian, 'cause this thing was going back defective next Thursday, before my 14 days was up, if a fix hadn't come out by then!

I really, really appreciate this work. :highfive::good:
[Nexus 7 (2013) General] sfhub:
No, as stated in the first post, there is no need. You are ruining my hard work of simplifying, planning ahead, and anticipating issues :)
[Nexus 7 (2013) General] sfhub:
I usually leave the bootloader unlocked because it makes recovering from mistakes easier.

You can easily lock it back up using

fastboot oem lock

it takes literally 1 second and doesn't wipe your tablet when you relock

I would however suggest you do this PRIOR to locking it up
[Nexus 7 (2013) General] jakelights:
Fixed for me! But my touchscreen issue is only ghost touch. I have a question sir. if my my issue fixed on ts10, do i have proceed to ts20? Thanks
[Nexus 7 (2013) General] sfhub:
This is a clue that it is the website, not the browser, no?

Try choosing one of the other themes in the lower left popup.
[Nexus 7 (2013) General] sfhub:
Thanks for the detailed report. It helps understanding what variances are out there and you can finally start to see patterns.
[Nexus 7 (2013) General] sfhub:
From the first post:
[Nexus 7 (2013) General] destroyer2usa:
Ok..found my mistake with attempt 1..I was to quick with adb reboot.

Just flashed 20 and went smooth.

10 gave erratic behavior for me when zooming in on websites.

Gonna test 20 now.
[Nexus 7 (2013) General] sfhub:
Thanks, clarified this in the OP.
[Nexus 7 (2013) General] player911:
Well your just so sweet. Thanks again.

Also after flashing I had to hard reboot it by holding power until it shuts down because you lose ADB access until you reboot.
[Nexus 7 (2013) General] crazyyyk:
Is it OK if I turn off and on my device instead of adb reboot?
[Nexus 7 (2013) General] sfhub:
That is fine. Just need to reboot somehow. If things are not stable, reboot at least one more time before judging.
[Nexus 7 (2013) General] sfhub:
Thanks I clarified the first post. I think you are probably not running stock ROM (which is OK), but normally you can still use adb reboot. Either that or it is a one-off problem.
[Nexus 7 (2013) General] lespaulman67:
Well great job on this fix for now. I have the 7/2013 Nexus 7 came with JWR66N and I updated it from OTA to JSS15Q and it made it so bad I couldn't even stand it. So I did a side load of the factory JSS15Q running around here. I also reset my tablet 10 times. It go way better. I was still having a lot of missing keys and ghosting and sticking keys.

Well I just unlocked my boot loader for the first time and ran this boot-ts10-lock.img for the first run. Wow what a difference I don't have the missing and dead screen around the QAWS keys. I had that deadness all the time. I did run the YAMTT and I am still getting a few ghost touches. Here is the thing with the ghost touches. They are not causing any issue with Google Earth at all meaning its not shaking the screen real bad and causing it to zoom out or jump around. Nothing wrong with some ghosting.

I am very happy with the results and I never did try the other two.

So do I need to unload this fix for any reason to do a Google update when they finally send one out. Google look at this fix its working for dead screen taps.

Good Job guys!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:good:

Doing some more testing as we speak and ran into issues again with dead screen hits around the A key in landscape with camera up to left. It is weird I am still thinking mine is a hardware problem.

---------- Post added at 03:37 PM ---------- Previous post was at 03:08 PM ----------

I just loaded up the 2nd file boot-ts20-lock.img.

What its doing is moving my dead screen area down. I had very bad dead spot on Q,W,A,S

With the first fix boot-ts10 it still was missing keys but it moved it down a hair. So the keys around A started to miss but Q key was fine.

With the second fix boot-ts20 it pushed the bad screen area down further. Now I am having dead area around the UP arrow and the ?123 KEY.

This is all in landscape with camera in upper left.

So the fix is not really taking it away its moving it around on my device. hmmm

Anyone else notice that.

I will try number 3 here in a few minutes.

Well here is the scoop the 3 fixes 10,20,30 didn't fix any of the dead screen problems. The last one made it like it was from the beginning .

This really sucks.

So do you think I should exchange this one for a new one. Best Buy