yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] PJ Clifford:
Ok, to clarify for the logic challenged among us, ie. me, running the unlock program (with subsequent reboots, if I understand correctly) will return to whatever touch screen software that is included as part of whatever update one is currently running. Is this correct? I have some very minor touch problems with 15Q, but not enough that I have been willing to risk making things worse with no way to get back to whatever TS software is part of 15Q (or later versions). So, if I apply ts10, find it really screws things up, I can go back to stock by unlocking and rebooting a couple of times?

BTW, thanks for all the work on this. Regardless whether I am a wuss or not, it is amazing to see someone put this much work into this for the benefit of us all.
[Nexus 7 (2013) General] afremont:
Yes, you got it.

FACTS:

It might help to explain how the process normally works. Currently, the kernel driver compares the version number of the firmware compiled into the driver with the version actually flashed into the hardware touchscreen controller. If the kernel supplied version number is higher, then the kernel driver flashes the new version into the hardware controller. If it is not, then nothing happens. This process occurs every time the kernel boots and loads the ektf3k driver.

SPECULATION:

I believe that sfhub uses a modified kernel driver to burn in whatever he wants when you boot the TSxx image. I suspect that he "locks" it by setting the version number fairly high preventing the kernel from updating it. I believe that he probably "unlocks" it by lowering the version number stored in the flash, or he simply erases it, I don't know for sure. In either case, the kernel will overwrite it on the next boot.
[Nexus 7 (2013) General] PJ Clifford:
Thanks! I may go ahead and give it a try. I've been hesitant because I never saw it explicitly stated that unlocking would restore the stock TS software. I didn't want to get backed into a corner where the only way out was a total wipe and reinstall. My touch problems ate not bad enough to consider having to do that.
[Nexus 7 (2013) General] sfhub:
That's what the company that got your money does to you.

Here we dug a tunnel underneath the corner for you to escape.
[Nexus 7 (2013) General] atb1183:
Please confirm, this is ONLY for stock 4.3?

bootloop if 4.4 or later? I was planning to install this either now on 4.4.4 or after 5.0 update.

---------- Post added at 04:13 PM ---------- Previous post was at 04:10 PM ----------

Does this work for 4.4 and later?
[Nexus 7 (2013) General] mdamaged:
Yes, what it means by boot loop is when you boot the image on 4.4.x (DO NOT FLASH IT, you BOOT it) as per the instructions, is it'll just boot loop as it installs the TS firmware, if you wait for a couple minutes then force a reboot, it will then boot your normal boot.img and it won't be looped, because if done the way the OP outlines, it does not replace your kernel.

Read the first post carefully, it goes over it in extremely clear detail.
[Nexus 7 (2013) General] mertzi:
In lollipop you can now send your thoughts about your nexus device straight to google via settings > about

http://www.androidpolice.com/2014/1...-to-tell-google-what-you-think-of-the-device/

I just sent a report about our infamous touchscreen, you should too.
[Nexus 7 (2013) General] Jamin_1:
This fix works great with 5.0!

After updating to 5.0 I faced serious touchscreen issues (1 touch point caused 3 ghost points). TS25 seems to have fixed it totally for me. Thanks :good:
[Nexus 7 (2013) General] jfriend33:
Great news. I'm on 4.4.4 and ts11. Wish more people on 5.0 would chime in about ghost touches.
[Nexus 7 (2013) General] Cobra11Murderer:
im on 5.0 with the nexus 2013, no probs with touch screen?, I might have the first model/early batch that came out (its refub) in any case dont these all ghost a little on the image no matter what? touches for me are perfect never i had a issue
[Nexus 7 (2013) General] osm0sis:
Things remain just fine for me on L as well! :good:
[Nexus 7 (2013) General] poofyhairguy:
Upgraded to L and its actually better for me. I used to have bad bad bad ghost touches (like couldn't type without getting frustrated) in KitKat. But now I am typing all this in the stock keyboard and it is working fine.

So far my random reboots also seem to be gone. Until I get one of those, I think 5.0 fixed my Nexus!
[Nexus 7 (2013) General] sam298:
Android L is worse. For those who say L is good, please check flow in keyboard or yamtt app. Lots of ghost touches.

TS25 - no ghost touches or dead spots when holding in hand. Few dead spots if placed on table.

TSunlock (android L) - some dead spots when holding and when placed on floor

TS10 - more ghost touches than unlock

Those with android L, please post your results when not grounded. Any ghost touches, multi touch performance, dead spots, etc.

Most ROMs, versions seem to work fine when held by hand and tested using yamtt or similar apps.
[Nexus 7 (2013) General] poofyhairguy:
Just installed Yamtt to check and it seems better.
[Nexus 7 (2013) General] osm0sis:
Obviously you can't make blanket statements.
[Nexus 7 (2013) General] n3wDaddy77:
Did you have a TS img installed when you flashed L? If so, which one?

I'm also curious as to whether these TS images will affect OTA updates to 5.0. I know OP mentioned that these shouldn't; but, I heard that there is more strict verification which checks for modification and may prevent OTA updates to L.
[Nexus 7 (2013) General] poofyhairguy:
Ts10
[Nexus 7 (2013) General] naylamp:
It seems better with Lollipop

Hello everyone, first post on XDA but I have been following this thread since I bought my Nexus 7 and found about this touchscreen problem (mine had severe ghost touches and plenty of dead spots). It definitely went better with the controllers (in particular with TS10). Ghost touches were almost eliminated but there were still several dead spots.

Prior to updating to Android 5.0 I returned to the stock controller. After updating to Lollipop with the factory image from Google, I test the touchscreen and ghost touches and dead spots were still present. Finally, I reinstalled the TS10 controller and so far ghost touches and dead spots are gone. I have enable the "show touches" option to see the behavior of the touchscreen but until now it looks OK. Sometimes I believe there are some dead spots or inaccuracies but maybe its just me not believing that this tablet is finally working well.
[Nexus 7 (2013) General] Mausas:
Oh... f**k those touch problems, i tried all 3 files.. for some time screen works normally, then it goes mad again.. i took the nexus to service as quarantee, gonna see what they say :cowboy:
[Nexus 7 (2013) General] abemore:
I've also tested with 5.0 Lollipop and touch issues seem to be the same as always.

That is, I was running ts18 before flashing the Lollipop update, and after updating (still locked on ts18 according to OP) I can still produce touch issues in a multitouch testing app while the tablet is not grounded.

EDIT: There is definitely a patch for the boot image in the Lollipop OTA update, but we can't be certain this patch addresses the touchscreen. I also can't be certain that my boot image didn't get patched by the OTA. All I have is the OP's word that his modified boot image is unpatchable (locked).

What we really need is for someone smarter than me to figure out how to keep this damn thing grounded.
[Nexus 7 (2013) General] mdamaged:
Did you unlock the ts18 fix using the unlock image in the OP? If not, then you never undid ts18.
[Nexus 7 (2013) General] Fanta3y:
Touch problems

Hello People!

For 1st excuse me for my english if that ).

(i'm trying to fix it by myself until I took it to a repair, maybe here i can find an answer.)

Well... i have the same touchscreen problems, as phantom clicks, touch lags and etc. on my nexus. I have read and done all of these instructions, all was alright, but the problem was in next. After last command in fastboot mode (fastboot boot boot-ts10-lock.img (for example this)) my device starts rebooting how it should be, it hanging for ~20 seconds, then restarting, then there is a google logo, and after what there is an android with a red exclamation mark (the picture below) and all... while i will not turn it off with button and reboot it. Anyway i tried all of those "boot-ts" with 2-3 times device rebooting and it was hopeless. So the question is in next, maybe these commands (boot-ts10,20,30) isn't prescribing in system because of that bug with dead android, when he should normaly reboot, so what i'm doing wrong, or it's a problem with my tablet?

Android 5.0, no root, bootloader unlcoked.

Any way thank you for listening! Hope i will get answers
[Nexus 7 (2013) General] n3wDaddy77:
I'd be very interested in cracking this tablet open and performing my own modification on it if someone with knowledge of electronics and EMI posted "how-to" instructions.

The touch issues get so bad sometimes that I get tempted to sacrifice the portability of the N7 and buy an N9. [emoji26]
[Nexus 7 (2013) General] navcar:
Upgraded to L, and thought I'd try the new stock touch screen firmware (ts unlock). New stock firmware was probably just as bad on mine, so going back to try a few of these DIY's in OP. (It was 'ok' for the first few days, but not today... maybe the hot Aussie weather!)

I am just a little upset that my tab was pretty much working well except for the gyroscope, so when I thought I'd go and get that repaired... it took 3 times for ASUS service centre to get it fixed (first time they hadn't fixed anything, second time was for the broken glass screen they put in), and now I have this crazy touch screen problem - and the warranty's out!
[Nexus 7 (2013) General] Mausas:
finally, i got my nexus 7 from service. They said that they reconnected screen cable, mounted it correctly, then reinstalled (stupid ones, nexus 7 LTE image to WIFI model). Then i manually reinstalled to WiFI model firmware, now after service, tablet seems ok to run
[Nexus 7 (2013) General] redwings8888:
I dunno guys I tried to like this device but I have to open it up and fix the grounding issues before it can work correctly?

wow....i thought nexus=solid this was an eye opener. and what options are left? these android tablets all look like suck :eek:
[Nexus 7 (2013) General] osm0sis:
Mine's basically fine. It's just a lottery really.
[Nexus 7 (2013) General] sam298:
In Lollipop, after flashing either ts locks or ts unlock, the nexus reboots to recovery. It looks like you have no custom recovery installed. If you reboot by pressing power button, it should boot to system.
[Nexus 7 (2013) General] Mausas:
too bad, after service my nexus behaves the same... f**k... gonna bring it to them again, bastards
[Nexus 7 (2013) General] squeeish:
Ah I experienced the same thing. I shall try it now since I've flashed TWRP.

EDIT: Just flashed ts-10. What happens is it reboots to TWRP instead of to system. Is that normal? I can just reboot to system after TWRP comes up right?

Yea Asus really screwed this up.
[Nexus 7 (2013) General] Mausas:
got my nexus fro RMA service, now they have changed all LCD screen, gonna see how it works now.
[Nexus 7 (2013) General] rationaldreamer:
Android 4.4.4 KTU84P does not boot after applying ts-unlock.img

Hello everyone,

since testing ts10-Ts30 for some months now solved issues with single touches but brought also problems with swipes (I just deleted 10 products in my amazon cart, I ordered by swiping the offer pages :( ), I thought, I will try the original controller again.

But when I apply ts-unlock.img, my nexus doesn't boot anymore and stucks at the very first screen (the white google logo and the bootloader-unlocked symbol). The only solution is to go to boot loader and apply one of the ts10-ts30-unlock.img files again.

I also would like to test original 5.0 screen controller, when it is officially available, at least then I would be glad to unlock ts10-ts30.

Does anyone have the same problem?

When I first applied the imgs, I was still on 4.4.3 and now I have 4.4.4. Is it possible that we need a different ts-unlock.img for 4.4.4?
[Nexus 7 (2013) General] mdamaged:
Hrm, well something you can try, do a full nandroid, just in case, then boot the ts-unlock.img then immediately reflash the 4.4.4 rom (don't wipe), then see if it boots.
[Nexus 7 (2013) General] rationaldreamer:
Thanks for your fast reply.

Do you know, if a nandroid backup is also possible without a custom recovery installed, just by using the temporary TWRP of Nexus Root Toolkit? Just, if you know that already, otherwise, I will search by myself.
[Nexus 7 (2013) General] mdamaged:
Yes, you should be able to make a full nandroid with just a booted (not flashed ) twrp. In fact, IIRC, NRT has a section for that backup type as well.
[Nexus 7 (2013) General] rationaldreamer:
OK, Thank you!
[Nexus 7 (2013) General] bgiesing:
Miracle!

This is a life saver! Two days ago, my device started to become so unusable that I was getting really mad. I remembered about this and tried t10 and my problem is solved!!
[Nexus 7 (2013) General] islammanjurul:
does this patch work on android 5.0 or 5.0.1 lollipop? I am having ghost touch problem even on android 5.0
[Nexus 7 (2013) General] mdamaged:
It's rom agnostic.
[Nexus 7 (2013) General] godutch:
i don' t think this works on lollipop, it doesn' t boot but goes straight to recovery (yes I did fastboot boot, not fastboot flash)

edit: or maybe it does still lock
[Nexus 7 (2013) General] AndyYan:
Maybe lock it in KitKat then jump to Lollipop using recovery? That way the lock shouldn't be overwritten.

Sent from Google Nexus 4 @ CM11

[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
[Nexus 7 (2013) General] Raphael VR6:
after this procedure, my n7 has been formated. why?﻿

how I will make sure that the procedure was successful?
[Nexus 7 (2013) General] yosmokinman:
^No idea why it formated your ****. Never had that happen. Edit: If you unlocked the bootloader thats why. Always make a nandroid and copy it and any files to your pc before doing anything.

To check go to /sys/devices/i2c-3/3-0010/vendor the last part is the firmware version. Stock is xa044. Ts11 for instance is xa061.

Works fine. Just tested. At least with twrp flashed. It boots to recovery then I hit reboot. Don't know about stock recovery.
[Nexus 7 (2013) General] godutch:
Do you know what the differences are between these ts versions?
[Nexus 7 (2013) General] mdamaged:
Calibration values I'd imagine.
[Nexus 7 (2013) General] godutch:
I sort of figured this too but i wanted to know what changed so i could the package that most suited my problem
[Nexus 7 (2013) General] mdamaged:
Trial and error is the only way. OP is MIA, and he's probably the only one who knows in this thread what's changed enough to do you any good.
[Nexus 7 (2013) General] DoNuT_1985:
Thanks a lot... just bought an used N7 because Lollipop sucked on my first-gen device, but after a couple of hours of usage I figured out that it is quite unresponsive in the bottom right corner. Sometimes it was nearly impossible to open a dock folder or hit the return key in SwiftKey.

Tried the ts10 and 20 versions - twenty first - and finally the ts10 adjustments made a big difference and I think it's gone now... it booted into (TWRP) recovery instead of doing a system boot, I just hit "reboot" and did a second reboot via adb.

Interestingly: I had the odd behavior that it only had this issue when its in a fixed position, e.g. mounted in my kickstand cover or lying flat on the table - as soon as I picked it up using it in my hands -> all fine. :confused: :confused: :confused:
[Nexus 7 (2013) General] mdamaged:
Yeah, it's a grounding thing. The ts patches can only mitigate some of that if one is lucky, not completely solve it.
[Nexus 7 (2013) General] godutch:
He's lucky. I finally tested them all with the nexus 7 ii test app, i get a lot of ghost touches, only ts03, 04 and 09 are without ghost touches but get unresponsive on pattern 1, ts20 gets ghost touches after touch. I really wished i could tweak these settings myself a vit
[Nexus 7 (2013) General] DoNuT_1985:
Well, in my case it totally fixed it - I was playing around for the last 15 minutes and had no issues whatsoever - quite a short period, but the fact that I didn't have to repeat a single gesture makes me confident it's not just a placebo.

Before the ts lock, it was totally random... I just had to pick it up and moving/shaking it a bit already made it a lot better. So, the question is: is it not just about screen sensitivity and are other parameters like motion sensor input also taken into account? I really don't get it, it was just annoying to use it on the breakfast table... :D ;)
[Nexus 7 (2013) General] serik21:
I have recently flashed to L 5.0 then did an OTA sideload to 5.0.1 and verified i am still locked to ts10 ( xa059 ). However i am getting a lot of phantom touches now when before on 4.4.4 i had minimal issues. I plan to try other versions of the ts images and stock L after work and will report back with my findings.

Wish me luck!
[Nexus 7 (2013) General] serik21:
Alright, after testing Stock L, 7, 10, 16, 20 , 25 and 30. I have found that in all of the setting aside from 7 there was a dead vertical strip in my screen right over the back button. Now in YAMTT i can swipe around the entire screen without getting a dead spot. Much appreciated with all the work that went in to this fix.

So 7 works best for me but it seems that everyone is different. In Lollipop all the fixes apply very easy and takes little time to boot, and reboot to get a solid test.
[Nexus 7 (2013) General] metalhead131:
The first one worked for me. Tablet is once again a pleasure to use
[Nexus 7 (2013) General] blackbi:
its better but sometimes its still lag.

I have used a nexus 7 2013 runs 5.0.1 for a week, and have a lag of touching when using long time. Its not responding when i tap on the screen, and i have to turn off the screen then turn on, and everything turns to normal.

Then yesterday i used the ts10 for my nexus. Everything seems to be better but sometimes its till not respond my touching and i have to repeat the turn off-turn on screen action. I dont know if other versions will work in my situation.

Can anyone have the same problem with mine and can you tell me what version that fixes the problem?
[Nexus 7 (2013) General] mdamaged:
Even though they are the same model, every device is different. You will have to trial and error, there is no way around it. That being said, common ts versions that seem to pop up the most, are ts10 and ts20.
[Nexus 7 (2013) General] player911:
Yea. I just took my case off of my nexus because it needs to be held directly to prevent grounding issues. Gaming on this thing is annoying. Been back and forth on my nexus and fire tablet, big difference in Terraria
[Nexus 7 (2013) General] Hnk1:
Take a look at my experience

http://xdaforums.com/showpost.php?p=53410257&postcount=1389

[MENTION=5490227]mdamaged[/MENTION]

Kindly refer anyone with touch issues to my post in hope they might find it useful but once again, remember for everyone something different works!
[Nexus 7 (2013) General] jfriend33:
I have been using stock rooted 5.0.1 all day today. Was on 4.4.4 for some time with TS11 fix.

Using display tester, I have excellent performance with multitouch and no ghost touches whatsoever.

I was very happy with this performance. I guess the creator of this was right. Even flashing a different firmware will not erase the TS fix!

That being said, I did encounter one time where the rotation was locked. That made me sad. In the back of my head I figured lollipop might cure this. But yes, I use a moko ultra slim smart cover. I am too paranoid to push really hard on the back of my tablet. For some reason a soft reboot doesn't always fix the issue. Sometimes have to fully reboot. But again, the frequency of the autorotate problem is maybe once a month if that.

You guys really should get on lollipop. The battery life is great!
[Nexus 7 (2013) General] bossman013:
Does anyone know when the last touchscreen update came from google? I was using ts-10 for a while as it seemed to work better than the others for me but then my screen started to become unresponsive to single touch. I ran the ts-unlock before applying the next ota in hopes that maybe google updated the touchscreen firmware.

No luck, it still locks up randomly. Ive wiped the cache partition and the device multiple times. Upgraded to 5.0.1. The issue remains.

Im dying for any help with this.
[Nexus 7 (2013) General] yosmokinman:
^ From this thread you can see the changelog in the op: http://xdaforums.com/showthread.php?t=2800308

Don't know how it relates to these ts firmwares. Sfhub was asked in the beginning of this thread what they are or how they differ but I don't think he ever answered.

A044 is googles latest. Came out at least 6 months ago.
[Nexus 7 (2013) General] bossman013:
Thanks for the info.

Forgive me if this has been answered, but is there a way i can see what firmware im currently running? A044 etc.
[Nexus 7 (2013) General] yosmokinman:
^ Because I have nothing better to do I'll copy and paste; you should read it's in the op of that thread..

/sys/devices/i2c-3/3-0010/vendor
[Nexus 7 (2013) General] squeeish:
Just for reference, this is what I got.

127|shell@flo:/ $ cat /sys/devices/i2c-3/3-0010/vendor

cat /sys/devices/i2c-3/3-0010/vendor

ELAN_KTF3K_xa044

shell@flo:/ $
[Nexus 7 (2013) General] brittonberkan:
Hey guys, just wanted to chime in with my personal n7 "grounding bug" story because it might be helpful for others:

So i ordered a used n7 a little over a month ago, and of course: it was from an early batch, and it had grounding issues: multitouch problems, ghost touches and all the other nasty stuff.

So i did what i always do: check xda. Found this thread, found another thread, tried all the software/tape fixes could find but nothing worked, and I was on the brink of throwing that thing away.

BUT the fact that i bought a used tablet might have saved me, because it came with a broken camera glass on the back. I knew about it and ordered a secon back cover for the device that arrived right when i was about to throw the thing away. Immediatly after opening the package i realized that this back cover was different to the old one.

I proceeded by removing the old back cover one more time, removing the tape i had applied earlier that didn't fix my issues, and applied the new back cover.

Since then, I didn't have a single issue with my device. So to all of those who don't get their tablet to work they way it should with all the other fixes, i recommend getting the back cover replaced by a new one.

I'd love to open the device to show you guys what's different (so maybe we can see the difference that fixes the issue) but before that i want to thoroughly test it on different surfaces and for more than the 24 hours i've used it now etc. Also, I'm afraid to break or damage that beautiful new back cover. Maybe there are pics online of different back cover versions?!
[Nexus 7 (2013) General] n3wDaddy77:
How did you go about ordering the new back cover? From Asus, or another parts distributor?

Thanks!
[Nexus 7 (2013) General] ddurandd:
First of all - I know this is ugly so please don't laugh. I've tried all the downloads in the OP, reseated all the connectors and even RMA'd my tablet. All with no luck. I decided to treat the grounding issue the way we used to treat a poor TV signal when I was a kid... With aluminum foil of course! I removed the Qi charger in an earlier attempt so that is why you will not see it in the pictures. The foil makes contact with the metal case of the battery and also with my hand when I hold it. So far, this is the best solution I have found to the ghost touches. I know it is cheesy, but I was at my wits end and about to buy a new tablet.
[Nexus 7 (2013) General] Persechini:
Not going to do it, but giving thanks for the spirit

Enviado do meu Nexus 7