yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] lespaulman67:
I think I will let it fully charge and keep it plugged in and restore the Nexus 7 then go right into doing the update before loading anything else. Not even play store updates. So when it boot in I will be going from JWR66N to JSS15Q. I don't have any miss keys or dead spots at all. I tested and never missed once. Mine is a 32g model 7/2013 Best Buy did not have any 8/2013 models. Mine has the 2 pieces of tape on bottom for seals.

Before I used to do the updates with YAMTT installed and everything in the Play store updated. I think I will try something different.
[Nexus 7 (2013) General] afremont:
Yeah, good point. I didn't even think about the recovery program being a threat as well. I was using CWM Recovery today on mine and I didn't notice any tell-tale 15 second delay upon booting my hacked kernel, so I just looked into it to verify why. Turns out that CWM Recovery 6.0.3.7 does indeed load the touch driver and it would flash any older firmware to version A038. That happens to be the version I'm running, so no delays occurred when I booted into Android afterwards.
[Nexus 7 (2013) General] lespaulman67:
I have a idea guys. What if I run the fix you have now and then did the JSS15Q update it would keep from messing up my screen driver.

---------- Post added at 08:33 PM ---------- Previous post was at 08:13 PM ----------

well I have #10 loaded right now. working great. I will update to the JSS15Q with #10 installed still. See if that blocks the JSS15Q from messing up my display driver.
[Nexus 7 (2013) General] afremont:
I think you'd be alright to do that since his goal was to prevent OTA updates from changing it, though sfhub is the "inventor" so wait for his reply to be sure. Since you already have his stuff installed, the OTA update to JSS15Q shouldn't change it. The end result should be the same as if you upgraded a fresh device to JSS15Q and then installed sfhub's stuff. Either way you end up with the Q system but with his firmware. I assume that T10 is the same as the JWR66N released version, but I don't know that for a fact.
[Nexus 7 (2013) General] sfhub:
Most things work fine in 4.4, so you are probably right, but sometimes people find some app they really like to use doesn't work well on a new OS version. For example I found that Dolphin doesn't do page zooms (both double-tap and pinch-zoom) anymore and Chrome seems kind of laggy. If you other browsers, you might not care.

So in the situation you described, you'd first be on KitKat using ts10. Once you run ts-unlock, upon first reboot, you'd be using the new touchscreen software that came with kitkat. Then, according to what you listed, you'd boot ts10 and it will hang on the bouncingballs animation (replaces X animation). ts10 is already installed at this point, so just wait 120 seconds for the boot to stabilize then press/hold the Power button 10-15 seconds until the tablet reboots and everything will continue as usual. Upon completion of boot, you'll be back to using ts10 with kitkat.
[Nexus 7 (2013) General] digiboy1:
Don't care for that weeks delay for app developers to fix, in case an app doesn't work properly.

And, love you man! Thanks! You wrote exactly what I had in mind. I've understood it, I think. Thanks for still clearing it up and taking out time! :)
[Nexus 7 (2013) General] lomonic:
Hi Sfhub, i use dolphin and it still does both page zooms and pinch zooms smoothly. Chrome is also running much better on 4.4. Only prob was with some select videos on youtube where video stutter is encountered.

I'm using ART and GEL, thought you might too. Not sure it that might contribute the difference in experiences.
[Nexus 7 (2013) General] sfhub:
Thanks for the data point. Dolphin might be because I'm running 10.0.4 because it crashed less for the sites I use and possibly 10.1.0 or 10.1.2beta would fix the zoom problem.

Chrome was ok (for me) on some pages, but on others it got laggy in that I would click on links and the response wouldn't show up for 2 seconds. I usually have 10-15 tabs open, so that might explain the difference.
[Nexus 7 (2013) General] doubleho:
then i m still running ts10,but the problrm.i had on 4.3 are now.all gone
[Nexus 7 (2013) General] lomonic:
I see. Just checked and i'm on 10.1.0 for Dolphin. Have not tried Chrome with so many tabs loaded! :D thought ART was suppose to make it faster anyways. sounds like you have a need for Nexus 7 2014! :D
[Nexus 7 (2013) General] doubleho:
im going to run the ts unlock now and see what happen
[Nexus 7 (2013) General] sfhub:
Just keep in mind that the 4.3 kernel the ts* files are using will not boot a 4.4 rom (it'll hang at the bouncing balls) but by that point the ts* software has already done its job. Simply wait 120 seconds for the boot to stabilize then press/hold the Power button for 10-15 seconds until the tablet reboots. Everything will work as normal after the reboot and you'll be running the touchscreen software that came with KitKat.

The instructions on the first page reflect this information, so if in doubt just follow those.
[Nexus 7 (2013) General] doubleho:
ok,ts unlocked,all the ghost touches,not recognized touch and slide came back,hv to flash the ts10 again,sorry if i mislead anyone

my experience is 4.3 without ts10 isnt usable, 4.4 without ts10, same as above

4.3 with ts10,95% of touch and slide are recognized, ghost touch sometimes come back and wont disappear unless i reboot

4.4 with ts10, work like a charm,everything is 100% working
[Nexus 7 (2013) General] Derjan23:
Hello,

Can someone please upload only boot-ts-unlock.img.

I can not unzip the 7z.

I always get an error.

THX
[Nexus 7 (2013) General] VRMozart:
how do I develop a boot.img for my device?

you cann't fix everyones' touchscreen,the ts10 one worked fine for me,but not perfectly!

1. can you tell me how I develop a boot.img for my device? such as Pack、unpack and modify kernel.

2 can you develop new packages for KRT16O (KitKat 4.4)?
[Nexus 7 (2013) General] sfhub:
Are you using 7zip to unpack?

http://www.7-zip.org/download.html
[Nexus 7 (2013) General] Derjan23:
Yes, Mac and Win7.
[Nexus 7 (2013) General] sfhub:
You can also use ZArchiver to unpack on Android:

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

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

I'll upload a zip packed ts-unlock in about 30 minutes unless you are able to get it unpacked.

BTW I'm wondering why you need ts-unlock if you weren't able to unpack the ts10, 20, 30 files?
[Nexus 7 (2013) General] sfhub:
Attached.
[Nexus 7 (2013) General] felix021:
thanks a lot. those files really worked!
[Nexus 7 (2013) General] Derjan23:
Thank you very much sfhub
[Nexus 7 (2013) General] manfio:
is this work with the new factory image 4.4? with the new bootloader and kernel i think?

or is better revert to 4.3 stock and the aply the imgs?

thanks

cumps
[Nexus 7 (2013) General] sfhub:
It works fine if you are on 4.4. I tested that a few days ago.

The only change is that a 4.3 kernel will not boot a 4.4 ROM, it will get stuck at the bouncing balls (replacement for X). However, by that time the touchscreen software is already installed, so simply wait 120 seconds for the boot to stabilize, then press/hold the power button for 10-15 seconds until the tablet reboots. The rest of the instructions stay the same.

The instructions in the first post reflect this information, so if in doubt just follow that.
[Nexus 7 (2013) General] manfio:
thanks for the reply

my screen goes insane after upgrade to 4.4

dont understand, with the 4.3 its ok
[Nexus 7 (2013) General] sfhub:
They are making changes to address hardware variances and so far when they fix for some, they break for others.

Eventually maybe they will be able to fix for all, but most likely they will fix for a certain amount of people, then let RMA handle the rest.

That is just my opinion.

I think in your case, you probably can get it working ok again with this thread, but no guarantees.
[Nexus 7 (2013) General] rumirand:
I have that case and I think it has to do something with magnets. I can't say for sure, but I have only issues when the magnets of the case are really near the device.

I haven't noticed this behaviour in Kit kat tough, give me some days to test it.
[Nexus 7 (2013) General] digiboy1:
No, trust me, it's not the case. Even I used to think so, untill I performed boot with ts10, using the instructions here.

Case or its magnet have no effect on the touchscreen whatsoever.

Mine works perfect, with the case on, for 24hours a day.
[Nexus 7 (2013) General] raschi78:
I OTA updated my Nexus 7v2 Wi-Fi from 4.3 to 4.4, and touch was working perfect with boot-ts10-lock.

Today I wanted to try a fresh install with factory 4.4, and none of the touch fixes work anymore. Touch is totally borked for me right now.
[Nexus 7 (2013) General] sfhub:
That is surprising as I was able to switch back and forth on 4.4 from the touchscreen software that came with it to ts10 w/o issues (and the behavior changed accordingly for each switch)

or are you saying it doesn't finish booting into android 4.4? That would be an expected behavior of a 4.3 kernel and a 4.4 ROM. Just wait 120 seconds at the bouncing balls and press/hold Power until the tablet reboots.

So you never ran ts-unlock or you did run it?
[Nexus 7 (2013) General] manfio:
When im leave the work i gone testing the ts10 to see
[Nexus 7 (2013) General] raschi78:
Everything worked fine when I OTA upgraded from 4.3 to 4.4. I even tried ts-unlock to test the new touch software, but had to go back to ts10.

I was just curious to try a totally fresh clean install from factory 4.4, and now I can't get the touch fix to work.

Did you OTA upgrade to 4.4, or did you do a fresh factory install?
[Nexus 7 (2013) General] sfhub:
I did both, but I will try again later today with the factory install and a full wipe.

I might not have done a full wipe on the factory install, I forget now.

Have you tried doing full 4.4 factory image, ts10, then wipe data / factory reset?

Worse case, I think you should be able to factory flash JSS15R, apply ts10, then OTA update back to 4.4 (recreating your first sequence), though I don't think you'll need to go through that much effort.
[Nexus 7 (2013) General] TheGoD:
Any chance getting the Kit Kat touchscreen software ported to 4.3?
[Nexus 7 (2013) General] Garret88:
I am really sad because I tried the ts10, 20 and 30 and no one worked after many rebooting. :crying:

Do you advice to try with the other experimentals or should be useless?
[Nexus 7 (2013) General] sfhub:
You noticed no change or you noticed change but not enough?

If there is one that performed better than the others, then try the experimental #s around that #.

If they are all really bad, then your screen is probably pretty off from most of them. You might try 4.4 and see if it helps.

Also are you judging based on real usage or just trying a touch tester? In the tester you might try sequences you don't normally use in every day usage.
[Nexus 7 (2013) General] sfhub:
I redid the factory image tests

flashed JSS15R factory image wiping user data

ran ts-unlock

verified touchscreen had dead spots for tapping

flashed KRT16O factory image wiping user data

verified touchscreen had dead spots for tapping

ran ts10-lock

verified dead spots for tapping gone

So to summarize, I've tested

JSS15R(ts-unlocked)->OTA->KRT16O->ts10-lock

JSS15R(ts10-lock)->OTA->KRT16O->ts-unlock->ts10-lock->ts-unlock

JSS15R(ts-unlocked)->factory image->KRT16O->ts10-lock

It all works as expected.

ts10 actually performs pretty good with 4.4 on my test unit. It feels like they implemented some type of bad touch info filtering at the Android level in 4.4 as a second layer to help alleviate the touchscreen issues.
[Nexus 7 (2013) General] Garret88:
I had improvements but still zones where the touch does not work as expected, like dead zones. For this reason, I do not know if to leave without or with your fixes because I have to leave the tablet to other people which do not understand how to do those things.

I tried some tester things but I think that also other people could try in everyday use those combinations.

I do not know what do to but I know that I am really sad.
[Nexus 7 (2013) General] sfhub:
In your case you might want to try the experimental ones, especially between ts10 and ts20 (in the exp1 pkg)
[Nexus 7 (2013) General] raschi78:
I have now tested:

factory JSS15R (wipe) -> ts10-lock -> OTA KRT16O -> ts-unlock -> ts10-lock -> restore factory/wipe -> ts10-lock

factory KRT16O (wipe) -> ts10-lock -> restore factory/wipe -> ts10-lock

And the results are the same. Multitouch goes bananas when crossing axes in YAMTT.

Things worked perfect before, but now I have no clue what has happened.

Have you released different versions of the ts10-lock image? If you have, I would like to try an older one.
[Nexus 7 (2013) General] sfhub:
Ts10 has not changed. Does multi touch go bananas on JSS15R or only on KRT16O?

Have you tried any other ts* files?

Also when you run the ts10 file, do you get the 20 second pause before it gets to the Google logo?

There is apparently, in your case, some state that changed and we can't figure out how to reset.
[Nexus 7 (2013) General] zSSeli:
finally perfect

After ts10, works great, cant make any dead touch, thanks a lot!
[Nexus 7 (2013) General] cocchiararo:
I have one of the first units that came without noticable issues,, and got borked with sticky touches after the updates.

I had been using TS-10 and it was like when it first came out.

I removed the lock and applied the ota to 4.4, and it seems to still be fine.
[Nexus 7 (2013) General] lg777:
I was on ts10 and it helped me out. I manually updated kitkat and my touch issues have improved. I unlocked ts10 prior to the upgrade so correct me if I am wrong but I should be on stock kit kat without any locks? I might apply ts10 just to see how it behaves.
[Nexus 7 (2013) General] sfhub:
Yes, once you unlock you are back to whatever Asus/Google gave you. In your case you are using the touchscreen software that came with kitkat.
[Nexus 7 (2013) General] lomonic:
Just curious, sfhub, did you get some random freezes like 5s where nothing is responsive at all with 4.3 and ts10? If yes, is that all gone now with ts10 under 4.4?
[Nexus 7 (2013) General] sfhub:
For my test tablet I never saw a freeze like you are describing under 4.3 using ts10.

For my touchscreen ts10 performs the same for 4.3 and 4.4.

When I was using the 4.4 touchscreen software I did notice areas of the screen would develop deadspots that would go away in a few seconds or if I tapped outside of that immediate area. That might be interpreted as a random freeze if one kept tapping the same spot.
[Nexus 7 (2013) General] sfhub:
Try ts09. If that doesn't help try ts11.
[Nexus 7 (2013) General] lomonic:
Interestong . Ive been going very well with the 4.4 stock touch software. With the tsxx series I tend to experiencing the same freezes some others have reported too. It happens mostly in kik when I do fast thumb typing. I suppose there's just lots o variation in the hw
[Nexus 7 (2013) General] cocchiararo:
i had those in my tablet

But i started seeing them long after ts-10 i believe (i had flashed a custom stock kernel for enabling touch control app).

After that, no amount of reflashig stuff made them go away completly (it was only while playing punchquest or time surfer)

4.4 is perfect now XD
[Nexus 7 (2013) General] May82:
I tried the 4.4 touchscreen software and while it was better it still didn't fix all my issues. I went back to ts10 and everything is fixed. Actually it seems like it's working even better than when I applied it on 4.3. I use remote admin tools for work (Bomgar and teamviewer) and it's much easier to be precise with the mouse when using these after the 4.4 update with ts10. Anyone know what changed? I know it's not placebo because I use these constantly and noticed a huge difference.
[Nexus 7 (2013) General] raschi78:
After some more testing ts10 on 4.4:

Multitouch goes wonky when I hold the tablet in just my hands.

If I lay the tablet down on my lap, multitouch is pretty much perfect.

If I lay the tablet flat on a table, the tablet goes wonky again.

So now I'm starting to have doubts if my tablet has ever had perfect touch, although I remember testing it OK on a hard flat surface before.

I'm sorry I have wasted your time, but it looks more like a hardware problem to me now.
[Nexus 7 (2013) General] danyboy008:
Thank you so much, I'm on stock 4.4 on my 16gb wifi model and had a looot of ghost, double and lost touches, using the ts10 I see a huge improvement! I'll be testing it these days and I'll report :)
[Nexus 7 (2013) General] player911:
I've experienced it with ts10 and flashing ts20 fixed that for me.

I havent used KitKat to say how it performs on stock but I had thee same issues with ts10. I run 20 now and can't find one thing wrong. So that that first before kitkat. Confirm its better or worse, then flash ts-unlock and update to kitkat. Compare.
[Nexus 7 (2013) General] lg777:
Thanks. I applied ts10 and whoa much more responsive and I thought I would be good on stock kitkat.

These touch patches have been great. Google owes you big time!
[Nexus 7 (2013) General] lg777:
Ooops meant to edit but ended up replying to my own post.
[Nexus 7 (2013) General] player911:
So 4.4 doesn't update the touchscreen drivers?

-sent from my LG G2 using XDA Premium 4
[Nexus 7 (2013) General] sfhub:
4.4 has updated touchscreen software.

Similar to previous releases, fixes for some, doesn't fix for others. On the positive side, not a whole lot of people saying things got worse.
[Nexus 7 (2013) General] desmondso99:
i'm on 4.4. dead areas are gone, but multi-touch persists. i will try ts-10 again

---------- Post added at 10:04 AM ---------- Previous post was at 09:14 AM ----------

help needed.

it's weird that it seems now i'm just getting the exactly same results as above no matter what packages i am using. I did have distinct results when i tried ts-10, 11, 20, 30, etc.

i'm guessing it's got sth to do with the additional step "press/hold the Power button 10-15 seconds until the tablet reboots" which seems a soft reset for nexus devices. by

doing so, i will just go back to ts-unlock and get the same results. or am i doing it wrong?

Thx in advance
[Nexus 7 (2013) General] SaberJ2X:
I applied the fix to my nexus, working perfectly... now... question... is this un-made by an OTA or installing CM or anything else? or only by running the TS-unlock one?

---------- Post added at 03:21 AM ---------- Previous post was at 03:17 AM ----------

I'd do TS-unlock... a nandroid/cwm/twrp backup... wipe everything and download an original image, install up and then apply again the ts fix, and restore apps...

I used to do that (except for the TSfix steps) on my optimus3D when it misbehaved
[Nexus 7 (2013) General] desmondso99:
thx, but is it because i sideloaded 4.4 with ts-11 lock? i'd forgotten to unlock it first :(
[Nexus 7 (2013) General] sfhub:
It shouldn't matter whether you ts-unlock'd before or after 4.4

I tested both scenarios many times.

That being said, after flashing back and forth between jss15r and krt16o about 20 times, my test unit suddenly became a touchscreen that behaved best under ts09 instead of ts10.

I don't really have a theory as to what happened and why it wasn't more deterministic at the moment. Maybe there is some Heisenberg uncertainty principle going on and if you poke the touchscreen too much in one area it ends up morphing in another.
[Nexus 7 (2013) General] SaberJ2X:
Which one is ts9? After a lot of playing around with mine it stills goof around :(
[Nexus 7 (2013) General] danvee:
In one of the experimentals in the OP.
[Nexus 7 (2013) General] Elting:
I used 4.3 with ts10 and all ts-bugs were gone. Then I flashed ts-unlock und updated to KitKat (flashed the factory image). Now all ts-bugs are back again (more worse than ever). RMA ist compelled... :(
[Nexus 7 (2013) General] thais14_03:
I don't know how to thank you, my new nexus 7 2013 LTE made me frustrated by its missed and freezed touches, having no option to return it back or even deliver it to Asus for maintainanc as I purchased it from UK and I do live in Egypt.

I used ts16 which was fine for keyboard typing but freeze a little bit in chrome browsing, ts14 is just perfect for every thing, works like a magic, as if I have bought another device.

I have just unlocked the device without rooting it, followed the instructions, reboot 3 times before each using those imgs. I recommende ts14 highly.

My build no. jsl36i

Thx again. Would update if any issues raised.
[Nexus 7 (2013) General] furou:
I wanted to share my experience.

My nexus touchscreen on 4.3 was faulty, I had missing touches, ghost taps and multi touch was bad - even while I was holding the tablet in my hand but it was completely unusable if it was resting on a flat surface.

I went through all the ts fixes until I found that ts9 was the only version that worked for me.

It made the touchscreen over sensitive at times but since it solved my ts problems at last, I could live with it.

Before side loading 4.4 I ts-unlocked. It seems that the touchscreen software that comes with kitkat is much more agreeable with my device. I was really surprised to see it working well, so well in fact that I thought that maybe I was still on ts9, but no it was the default 4.4 ts.

It feels very similar to how ts9 behaved, I can use the nexus like I could on ts9 and couldn't when I was on the default 4.3 touchscreen.

The best thing is that while it's almost working as well as ts9, it's not as sensitive.

The downside however is that sometimes it deteriorates and misses touches. That goes away for a while if I turn the screen off and on (kind of how hitting an old TV fixes the signal) but it's a temporary fix and I want to fix it permenantly since it's bugging me and it's the only issue stopping this touchscreen from being perfect.

sfhub, do any of the fixed help with that? Will I have different results with the ts fixes now that my baseline experience has improved?

I'm also wondering if the fixes will get ported to the 4.4 kernel.
[Nexus 7 (2013) General] sfhub:
IMO once you find something that makes the tablet reasonably usable you should just enjoy the tablet and not seek perfection unless there is a release from google where almost all people report their problems are fixed.

I've noticed on my test tablet that after many flashes from jss15r to krt16o (20+ now) it stopped being responsive to ts10 and I had to switch to ts09. I don't know the exact mechanism for how that happened. In my case I was fortunate that ts09 restored pretty good functionality but I can imagine worse case scenarios where no touchscreen software works well.

So my advice is if you can't get it to a usable state, return/exchange/RMA if possible. If you can get in usable state, just leave well enough alone, especially if you are in a situation where you can't return/exchange/RMA.

I could recompile everything using a 4.4 kernel as a delivery mechanism, but it will probably depend on whether a lot of people are seeing issues still on 4.4. I'd rather just keep one set of fixes optimized for the largest group rather than have people feel like they need to try yet another set of ts* files built on a 4.4 kernel which will have no difference in results from the 4.3 kernel, other than it will boot the 4.4 rom all the way.
[Nexus 7 (2013) General] hyperspacey:
Funnily enough I've ran into all manner of entertaining new multitouch quirks since updating to 4.4. The biggest issue is that, regardless of the patch I apply (or using stock), the multitouch points seem to drag toward each other when close on one axis. This makes Dead Trigger an entertaining if frustrating farce. Dammit Google, stop ruining my fun.
[Nexus 7 (2013) General] manfio:
ya RMA

but the problem is Google dont solve the bug

the only thing they do is factory reset

i speak the true...google dont care abbout this problem

i have a friend, he take the n7 to RMA and back with the same problem

with my n7 i upgrade to 4.4 and the screen goes insane

than i rooted, flash a custom 4.4 and the screen dont have any issue...how it is possible?

i dont know..