yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] davefootball123:
Thank you so much for creating this fix. I purchased a Nexus 7 two days ago and returned it due to a bit of dust between the LCD and Glass Panel. The replacement had a bit of a jumpy screen so I custom rom'd/kernel'd it, and now added your touch fix and it is perfect now!

Thank you.
[Nexus 7 (2013) General] djph4ntom:
This isnt really a fix... Its just a work arround.. For ex for me. I dont have the problem with ghost touches ... Only with the sticking touch... Im waiting for 4.4 to see if there are any improvements if not im sending it back to waranty .. Cuz probably they arent going to give me another new tablet...
[Nexus 7 (2013) General] BrianDigital:
You can also try helium you will need to be plugged into your computer for no root.
[Nexus 7 (2013) General] sfhub:
Many folks with sticking touches no longer have them on TS10/TS20. Of course some touchscreens are just too far off and will still have issues.
[Nexus 7 (2013) General] norcalezk:
Hey sfhub, this is definitely a great fix and I would love to try it out. The only thing is I have a Mac and I currently don't have access to a windows PC :( is there any way I can load the boot files onto my nexus using my Mac? I really love my nexus and I want to fix it :(
[Nexus 7 (2013) General] iblues:
TS30 works for Nexus 7 LTE version

Thanks a lot for your fix!

I just bought a Nexus 7 LTE version last week only to find the touch screen. Even after updating to 4.3.1, I was seeing the issue.

Your TS30 resolves 95% of the touch issues! There are still some non-registering touch issues but can live with that till Google/Asus come clean on this!
[Nexus 7 (2013) General] bandit_knight:
You can do this with Mac just fine. You only need the Android SDK for Mac and Java installed on you Mac.

The SDK you can download from the following web page:

http://developer.android.com/sdk/index.html

All the command line tools (adb, fastboot) that are needed are inside the SDK zip file.
[Nexus 7 (2013) General] sfhub:
The files are in 7zip archive format.

The download link below:

http://www.7-zip.org/download.html

should have some 7zip archive versions for Mac or you can get 7zip for android here:

https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver

Other than that, adb, fastboot, etc. are available for mac as well.
[Nexus 7 (2013) General] bandit_knight:
Here's the platform-tools extracted from the Mac Android SDK.
[Nexus 7 (2013) General] satishenl:
Grouper 2012 wont boot after patch

I have a grouper 2012 version with [ROM] Buttered Grouper AOKP 4.3.1 [+Aroma] [2013-10-13] bootloader unlocked rooted

I have tried all the patches and when I do fastboot boot boot-ts10-lock.img or fastboot boot boot-ts20-lock.img or fastboot boot boot-ts30-lock.img the device is just stuck in bootloader for ever and I have to use the power button to reboot.

I have followed the next set of instructions to reboot twice before using the device and the device seems to be behaving better, but not completely. I think this is because the boot process did not complete.

Any ideas why the boot process is not completing?

Thanks in Advance :)
[Nexus 7 (2013) General] hyperspacey:
These files are designed for the 2013 Flo tablet, not the 2012 Grouper, so that's probably what your problem is.
[Nexus 7 (2013) General] Sensamic:
Tomorrow I will exchange my Nexus 7 for a new one. I don't really want to use a patch.

There are users out there that say they don't have this problem, so there must be Nexus 7 that work perfectly without patches.
[Nexus 7 (2013) General] embhorn:
Saved another return

Kudos! I was *this close* to returning my N7 2013. Thanks for saving me the hassle.
[Nexus 7 (2013) General] norcalezk:
I have already installed the android sdk for mac and I was able to unlock the bootloader on the n7 with no problem. i did download and install the 7zip archiver and i did unzip the boot-ts directory successfully. the problem is when i try to access the bootloader through the boot-ts directory like the instructions say, terminal gives me a error message: "./adb no such file or directory". is there something I am doing wrong on my end? this is the first time i try diving deeper into one of my android devices and I hope i can do this because I really dont want to return my n7
[Nexus 7 (2013) General] sfhub:
Grab the mac adb/fastboot from the post above and put the files in the boot-ts directory.
[Nexus 7 (2013) General] -Jesco-:
how long does one need to wait on boot animation after booting one of this ? been waiting for 4 mins oo ? pretty sure I've done nothing wrong but followed instructions :?

edit did a hard manual reset and it booted up fine
[Nexus 7 (2013) General] player911:
Yea I don't know. The possibility of a few working seems small or perhaps they aren't noticing them. I think the majority are weird just because it was a software bug introduced in an update.

So perhaps the ones that are working, rooted and flashed custom ROMs and never officially updated to install the bad driver. Once it installs you're boned.

Its a software problem and you are likely to end up in the same spot after it updates.
[Nexus 7 (2013) General] DymekPC:
Omg this problem is really annoying. Maybe not with multi-touch but touchscreen "grounding" issue - when i hold nexus in my hands - everything is working properly. I tried to apply patch from 1st post and neither improved my touchscreen...

Here is my video youtube.com/watch?v=3fcYFf5Tx7o&hd=1

Nexus 7 2013 16 GB - JSS15R
[Nexus 7 (2013) General] sfhub:
There should be a 20 second pause before you get the Google splash screen. Once that is done (ie you are on the Google screen) technically the touchscreen software is installed. If it takes more than 2 minutes to boot, just press and hold the power button until it reboots. The touchscreen software is already installed and it will go back to using your original kernel so everything should be fine.
[Nexus 7 (2013) General] DymekPC:
I apply first patch once again and... its really work! Thank you sfhub! :)
[Nexus 7 (2013) General] abs0lutezer0:
Greatly appreciated

ts-10 worked perfectly on my nexus 7... thank you
[Nexus 7 (2013) General] bandit_knight:
I've been on TS-10 for a few weeks already and in general it works all fine with decent performance with both "grounded" and "ungrounded". But every now and then my device seems to go nuts. Once it happened to me that the device developed a dead band at the bottom of the screen. It went away with a reboot. The other time it just started registering phantom touches in the screen corners. This again I was able to fix with a reboot. Any idea why does those happend and how come they can be fixed with just a reboot?
[Nexus 7 (2013) General] norcalezk:
Sfhub you truly rock!!!! I tried out ts10, it worked mostly good, tried out ts20 and it was a little more flawed, tried ts30 and it got worse, I tried ts11 and that made the tablet work flawlessly :) I am very happy with your great work and for helping me out with my noob questions lol if any discrepancies come up ill let you know :) thx again :)
[Nexus 7 (2013) General] sfhub:
Your screen probably accumulates some residual charge that throws off the algorithms.

In many cases you can make it reset by turning off for a few seconds and turning back on, as opposed to doing a full reboot.
[Nexus 7 (2013) General] hasenbein1966:
I have ts30 - works well. Thank you very much, sfhub!

Occasions where touch stucks are now at least very rare, albeit not really gone.

Yesterday I tried the "Swype" keyboard. When the tablet laid on the bed, inputting words by swiping first didn't work - the swipe was always interrupted several times, it wasn't possible to input even short words.

Then I took the tablet in one hand and swiped with the other - inputting text was possible flawlessly.

Next I put the tablet back onto the bed in order to see whether something had changed.

Using it while holding it had "healed the touch input!

Now swipe-inputting text worked!

So I suspect the theory that residual charge accumulates in the screen seems to be somehow valid!

Perhaps others could also test whether the problem "touches are sometimes stuck when the tablet is not held in the hands (=ungrounded)" can be (at least temporarily, of course) solved by executing the operation which is unreliable with tablet in hands and thus "draining away" residual charge.
[Nexus 7 (2013) General] furou:
So if despite any fix I've tried, the only time my tablet has no touchscreen issues is when it's charging, does that mean it's hardware and I should send it back to Asus to get fixed?

It's just that otherwise it's perfect - no dead pixels or light bleeding, no random reboots, etc and I'm worried the fixing or replacement unit will get those issues in addition to the touchscreen problem.
[Nexus 7 (2013) General] sfhub:
First, I would go with the best one and let it run overnight sprinkling in some reboot fairy dust.

If you are still seeing issue try the experimental ones close in number to the best one.

Finally consider whether you are seeing issues that will show up in real usage vs test tool.

If it is just unusable and you will often be placing the tab on a table rather than holding it, then you probably should get it repaired/replaced.
[Nexus 7 (2013) General] PouperPoups:
I gave thanks but really wanted to follow up with a post to say thank you for this. Mt touchscreen has become increasing frustrating and I was almost ready to give up on the Nexus 7. It now seems to be working fine.

Thank you so much!
[Nexus 7 (2013) General] navillos:
Ts25 worked the best for me.
[Nexus 7 (2013) General] Elting:
TS10 worked for my seemingly! THX a lot!

One question: when I will flash the KitKat-FactoryImage later this month :) this TS-lock is gone, right?

In other words: if I flash a Factory Image nobody can see what I have done in the past and I become a clean Android OS (I'm asking because of warranty claims).
[Nexus 7 (2013) General] sfhub:
Glad you found something that works for you.

As stated multiple times in the first post, the touchscreen software will stay in place until you run the unlock. Even if you flash kit Kat, the touchscreen software will still be in place. However it is very simple to go back to what came with the ROM. Just run the unlock and after reboot you will be back using the touchscreen software that came with the ROM.
[Nexus 7 (2013) General] Elting:
OK, I just thought the Factory Image resets everything, even this fix.

Again thanks a lot for your work!
[Nexus 7 (2013) General] phynix5800:
Would you mind telling a noob how this is possible? The driver has to be stored somewhere and when you reflash everything it would imply for me, that it will be replaced :confused:
[Nexus 7 (2013) General] MRobbo80:
Thank you so much my nexus 7 was built in august and had touch screen issues, after flashing ts10 I now have a super responsive touch screen. THANK YOU SO MUCH !
[Nexus 7 (2013) General] furou:
ts11 seems to be working very well when the tablet is in my hand. Thanks :)

However it goes nuts if I multi touch on the same axis ("crossing the streams") while the tablet is on certain surfaces like my bed. Do any of the fixes deal with this specific issue? I will sprinkle a good measure of reboot fairy dust and see if there is any improvement the following week, but would like to know if I would have more luck with the next fixes.
[Nexus 7 (2013) General] sfhub:
Yes, they do, but some screens are too far off spec to benefit.
[Nexus 7 (2013) General] furou:
The further up I went in number, the more wonky the screen got while multi touching on a bed / flat surface. I went back to ts-10 and it's a lot more stable, actually able to hold two fingers on the screen without it going all over the place (in real usage testing, not just YAMTT).

Seeing as how I have no idea what's inside the fixes and how they work, and assuming you assigned the numbers based on increased tinkering with the touchscreen software values, I'll use layman terms and ask if it's possible to have a ts fix that is even "less" than ts-10, like an experimental ts-09 ?
[Nexus 7 (2013) General] sfhub:
Those are in the exp2 package
[Nexus 7 (2013) General] player911:
Mine did that too using 10. Try TS20. It worked the same as 10 but doesn't freak out randomly.
[Nexus 7 (2013) General] furou:
lol, derp :D

Thank you so much for all the awesome work you've done!
[Nexus 7 (2013) General] BrianDigital:
Man oh man TS 09 has gotten rid of the fake touches. Thanks so much
[Nexus 7 (2013) General] Myro007:
TS10 solved touch screen issues

TS10 solved all problems with touch screen. I was having lost and ghost touches before. It was really annoying. When tested with Multitouch Test app it was really obvious that with 4 and more touches it had a lot of ghost touches. On the left side of screen (in portrait mode) it had some kind of dead zone - this part of screen always had the problem. Now everything works fine. I used a device for about 10 minutes and for now it works flawlessly. I hope it's gone forever! :)

Thanks a lot, sfhub! :victory:
[Nexus 7 (2013) General] Vagelis83:
Thank you very much TS10 was the right for me too. I was ready to sell my device but now everything looks to work OK. I can't believe Asus or Google hasn't made a patch fixing this terrible problem yet . Next time I would like to buy a tablet I will think it more than one times to buy by them.
[Nexus 7 (2013) General] lomonic:
After many days of testing various patches, I've concluded on TS-16. Below are my test summary if it helps anyone.

Problems I faced with

- stucked touches, rather frequent

- ghost touches, very seldom. Only noticeable in very touch intensive games.

- missed touches, seems to happen a lot with typing.

- all the above happened regardless hand held or on a non conducting surface. Happens a lot more on a non conducting surface. A reboot usually fixes things for a while before it starts again.

TS10

- Works well, but has very seldom 5sec freezes that recoveries and goes wonky at bottom of screen after extended uses.

- Fixes stucked touches.

- No noticeable ghost touches or missed touches.

TS20

- Works and feels better both single n multi touch compared to TS10.

- BUT has unexplainable random system freezes that requires hard reset. Happens very occasionally and only in touch intensive programs.

- Fixes stucked touches, ghost and most missed touches.

TS25 and TS30

- Fixes stucked touches.

- Ghost touches becomes more frequent near bottom of screen.

- Touch feels a lil wonky too.

TS18

- Fixes stucked touches.

- Ghost touches and missed touches are unnoticeable.

- Multi touch in Google maps is less responsive.

- Random freezes also encountered as per TS20

TS14

- Fixes stucked touches

- Ghost touches and missed touches are unnoticeable.

- good responsiveness in google maps.

- typing feels a little inaccurate.

TS8 TS6 AND TS9

- all feels very sensitive.

- feels random wonkyness

- fixes stucked touches

- no noticeable Ghost touches and missed touches.

- typing seems overly sensitive and results in many errors.

- random wonkyness happens after extended use and short self recovered freezes.

TS16 - my favourite

- Fixes stucked touches

- no noticeable ghost touches or missed touches

- no random freezes experienced, not even the self recoverable freezes.

- good balance of sensitivity and accuracy.

- good multi touch responses in Google maps and Google earth.

- no problems in most instances when using on a flat surface.

Just a note to everyone. I have given at least 3-4 reboots after each update, and run them for at least 24 hours playing touch sensitive and intensive games like Turbo racing using multitouch to slide and more around.

Hope this helps. Thank you sfhub for filling the gaps where Google and Asus have not. Great patches for everyone to suit your usage patterns.

This entire message is typed using my nexus 7 2013 in dolphin browser.
[Nexus 7 (2013) General] hasenbein1966:
First I had ts10.

Was much too sensitive.

Then I flashed ts30. Worked well, until I flashed some UI skins for TWRP; after that, I had stuck touches, even after rebooting.

Now I have ts11, and it seems to work really good *knock on wood*

Is it perhaps possible that a certain fix (e.g. ts10 or 11) works better after another fix (like ts30) was installed than if it would have been installed as 1st time fix?

Or do we enter voodoo territory here? :D
[Nexus 7 (2013) General] sfhub:
It is more likely the various reboots allowed the internal calibration to settle in.

Sometimes it takes a little bit of usage and reboots for things to settle in.
[Nexus 7 (2013) General] fuser-invent:
So my story is that I got my tablet with JSS15Q loaded and didn't notice any major issues at first. When I installed the OTA update my tablet stopped working, with noticeable "dead zones," erratic touch behavior, broken swipes and and ghost touches. This only happened when the tablet was on a surface, any surface really, whether it was my leg, the couch, a pillow or even suspended on a stand or clamp style stand. It worked normal if I held it in my hand though.

I tried these fixes and none of them worked so I sent the tablet in to the repair center, which was a crappy experience. They shipped it to the wrong address, it should have gone to my business address and went to my home instead and they refused to call FedEx and change the shipping address. FedEx then delivered it to the wrong address, retrieved it and finally tried delivering it to my home but it required a signature in person and of course I work all day, so it took three delivery attempts and lots of calls to find out the estimated deliver time to actually get the tablet back.

It came back loaded with JSS15Q again and no notes about what they did besides load the firmware. I contacted customer service again and they looked up the info and said that the techs opened the tablet and physically re-calibrated the touchscreen as well as "updated the touchscreen driver." I asked if I could now install the OTA update safely and they said that would definitely be okay to do. So I did install it and the tablet went right back to the same behavior. I got pretty mad at this point but then decided to come back to this thread. This time the ts10 fix worked for me! Perhaps their "physical re-calibration" made that possible if they did that at all. I'm not really sure but at least the tablet is functional now. There is still some very minor erratic behavior but it is almost not noticeable.

So thank you very much to sfhub! I'd love to be able to understand how this works. Is there a github with the code or can you offer a brief explanation of what is being changed?
[Nexus 7 (2013) General] Sensamic:
So many people sending their Nexus 7 to Asus is good because that way they'll see how big this problem is for many and will keep searching ways to fix it.
[Nexus 7 (2013) General] G2xer:
Is it working well now when on a surface?
[Nexus 7 (2013) General] fuser-invent:
Yes, and on stands. No more dead zone. Swype keyboard works great 99% of the time. Almost no problem with multi touch up to 5 or 6 fingers. After that it get a little glitchy though.
[Nexus 7 (2013) General] leonclement:
I had sticking touches on both Q & R, noticed it mainly when typing, installed ts10 and so far (1 full day) its been PERFECT, thanks alot!!
[Nexus 7 (2013) General] hamlam:
you send me your fle TS16 is not???

Mail: phuongbaohanh@gmail.com

Thanks.
[Nexus 7 (2013) General] lomonic:
You can download it. Its in one of the experimental packs for download. Let me know how it works for you.
[Nexus 7 (2013) General] trvbone:
Fuser hey man, I haven't been over to the ainol threads for awhile weird seeing your pic in here. How are Ya?
[Nexus 7 (2013) General] muyoso:
Only been using it for like 12 hours so far, but ts10 has completely fixed my tablet experience. Hopefully it keeps being perfect, because I was about to RMA the tablet.
[Nexus 7 (2013) General] Pfeffernuss:
Is there a file which has the *least* possible sensitivity or doesn't it work like that? Now using TS11 and it's "okay". What bothers me most (and almost so much as to wanting to sell the whole d*mn thing): when long-pressing an icon/option to move an icon on the homescreen, long-press to see options of something (rename/delete in a filemanager) and so on the screen/device usually sees this as a movement instead of a long-press.

So you long-press an icon but also move your fingers some pixels (which is really unavoidable) and whammo, long-press is gone and you end up a screen to the left or right. Trying to open an internet page in another tab is also quite an achievement. Eight out of ten times I only move the page up or down without getting the long-press pop-up.

This really really really winds me up so I would like the sensitivity to be wayyyyyy less. Tried a lot of TSxx files already but none so far offer me a reasonable alternative. Other than that: no ghost presses, no inadvertent long-presses and so on. The single most annoying aspect of the whole Nexus 7, for me, is the ludicrous sensitivity.
[Nexus 7 (2013) General] hasenbein1966:
That is true!

On my SGS2 with Dorimanx Kernel, you can adjust in "STweaks" how many pixel the finger can be moved until it's recognized as a "move command".

Would it be possible to edit this parameter on the N7 also?
[Nexus 7 (2013) General] fuser-invent:
Doing well :) Still trying to learn as much as I can about as many different aspects of Android as I can. Although I liked the Ainol Fire, I'm enjoying this Nexus 7 more now that the touch response is workable. I'm just wondering if any of the the code from these ts packages could potentially be used for those amlogic tablets or other tablets besides the Nexus 7, that's why I want to know more about how this works. Most of those foreign amlogic tabs have okay screens but definitely have touch sensitivity issues. Not as bad as the Nexus 7 before this fix but still annoying at times.
[Nexus 7 (2013) General] sfhub:
Does amlogic use an elan touchscreen? If not, 100% it won't work. If so, just highly unlikely.
[Nexus 7 (2013) General] L1lyksd@ddy:
TS10 is working great for me! Thank you so much for your time and expertise on this HUGE Nexus problem.:good:
[Nexus 7 (2013) General] Elsydeon:
I was practically ready to just give up and sell my Nexus 7, having read that this fix didn't do it for some people. BUT, decided to try TS10 anyways, and thank god I did. It's been about a month now and TS10 pretty much completely eliminated my double touch issues. I can actually use swype on keyboards without it doing ghost lifts. Thanks so much for the fix!!!
[Nexus 7 (2013) General] sfhub:
Glad you tried it and it worked out well for you.

For other folks reading this, as stated in the first post, I was able to make 3 out of 4 test units usable again with these fixes.

After monitoring this thread for almost 2 months, corresponding with people by PM, and helping folks locally, there is about an 80% success rate for making units usable again. Some units will have no signs of touchscreen issues at all. Some will have very minor issues that people won't notice in real usage. Basically these are all considered "usable"

About 20% (or 1 in 5) units will still not be usable even after trying all the different versions.

That means you WILL see people mention that the fix doesn't work for them. This is EXPECTED. 1 in 5 (20%) won't have a usable touchscreen. However 4 in 5 (80%) will have usable touchscreens, so your chances are pretty good. Considering your alternatives, you don't really have much to lose, especially since everything is reversable, including re-locking the tablet.

Also don't get discouraged if TS10 doesn't work for you. There's a reason TS20 and TS30 are included. If TS10 almost works for you, then you might want to try the experimental ones near in numbering to TS10.
[Nexus 7 (2013) General] Pfeffernuss:
But they will all have the same sensitivity, no?