yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] MohamedYousri:
Dear sfhub ,

i have a quick question

lets say that when Google will release the KitKat 4.4 the update will contain files to solve the touch screen problem , so how can i revert back safely to the original state that was before using your files to make sure that the device will receive the update fully from Google with the fix that Google did

or if Google released the fix with 4.4 it will automatically overwrite your file we already updated the device with ?!

Thanks :good:
[Nexus 7 (2013) General] Pfeffernuss:
Then I'm one of the twenty percent as all variations I've tried have the same (ridiculously high) sensitivity. Unable to long-press anything securely without moving the screen.
[Nexus 7 (2013) General] sfhub:
Your experience of super sensitivity with all versions is actually very rare, I have probably only heard it once or twice.

There is something different about your unit.

Do you have a screen protector on your unit?

Are you over/under clocking or over/under volting?

Have you factory reset and gone back to stock ROM/kernel?

Anything you might be doing different than a regular stock user is an area to look at.

Also when you say all versions, do you mean 10, 20, 30 or have you tried all the experimental ones also?
[Nexus 7 (2013) General] furou:
I want to +1 how grateful I am for sfhub's fix. I was about to RMA my nexus. None of the fixes between 10 and 30 worked. I tried 9 and it's amazing, the touchscreen works almost perfectly, even on the flat surfaces it had failed on before. I was sure I had a defective hardware since nothing helped but ts9 was the cure. Weird how binary it is - any other ts fix in any direction makes my ts totally unusable.
[Nexus 7 (2013) General] sfhub:
If all you did was install the ts fix that will not negatively affect your ability to get an ota or update from Google. No files on your ROM were changed nor modified so it can't break the ota.

If you rooted and then ran some root apps that modified/deleted files or installed some tweaks, then that could break a future ota.

Installing a future update whether by ota or factory restore will not change the ts fix. The only way for it to change is if you run ts-unlock.

You can run it before or after you update to kit kat, doesn't matter. Upon first reboot after running ts-unlock (ie part of the install instructions) you'll be back to using the touchscreen software that came with the ROM you have installed. If you do it before kit kat then that'll be the jss15* jls36* versions. If you do it after kit kat, then it'll be the one that came with kit kat.
[Nexus 7 (2013) General] Roger Boden:
sfhub is a genius!! Thank you!! TS10 worked 100% for me. Had my N7 2013 for three weeks and as soon as it updated to JSS15R most of the LHS of the keyboard in landscape mode stopped working unless I either grabbed the top LH corner of the bezel or plugged it in. Playing around with bootloaders etc is all new to me but I used the SkipSoft Toolkit to backup my apps and unlock the bootloader. It all worked first time except for my email settings. Asus obviously haven't got anyone of sfhubs calibre on their payroll!!

Pretty unimpressed with how difficult it was to get the N7 2013 working properly with Win7 X64. I'm quite savvy with the ins and outs of Windows but I can understand why less technical people have given up with their N7's and just got a refund. Nice peace of kit seriously flawed by various software issues that Google and Asus don't seem to want to know about....

BTW, can I now re-lock my bootloader??

Thanks again for all the hard word done by you guys....
[Nexus 7 (2013) General] sfhub:
adb reboot bootloader

fastboot oem lock

It takes seconds and doesn't result in erasing the data like the unlock.

However I don't suggest it unless you have a compelling reason other than you don't like seeing the unlock symbol at boot. The reason being if you ever need to do some more repair work, need to run factory restores, need to root, etc. you'll need to unlock again forcing you to do the backup, unlock, lose data, restore data cycle again.
[Nexus 7 (2013) General] wanfeilwong:
Just unlocked bootloader and tried ts10 and it fixed my "grounding issues" for good.

Before this fix I barely got any recognized touches in the top 1/3 area of the screen whenever it was set down on a table or something.

My nex7 came form the June 2013 batch with JDI screen.
[Nexus 7 (2013) General] sfhub:
Even though the source code handles multiple LCDs, I've only ever seen JDI screens. The touchscreen is made by Elan though.
[Nexus 7 (2013) General] wanfeilwong:
Sweet, thanks for the info and for the fix!
[Nexus 7 (2013) General] fuser-invent:
No they don't use elan, I'm wondering what's in the package to see if any of it can be adapted to other tablets.
[Nexus 7 (2013) General] nexai:
I ran numerous test but still nothing seems to fix the sticky touch issue. Even though ts14 has the least issue with ghost touches but nothing seems to be able to fix the sticky touch problem. Day to day use is still bearable because sticky touches only happen intermittently. I'll wait for KitKat update before sending to Asus to claim my warranty.
[Nexus 7 (2013) General] lespaulman67:
Here is the scoop. The 1st file 10 was the best it fixed the dead screen after I did a full restore of the Nexus 7. The problem with that fix #10 is that when you scroll up or down it would cause my page to zoom out or in and jump to other things. If you can fix that issue it would be fixed. I have tried everyone of them installed a fully restore and 10 is the best .

Fix #10 and we are golden.

I was browsing the XDA forums and went to swipe up with the fix #10 and some porn site poped up on my tablet. Has anyone had that happen.

I'm serious too.
[Nexus 7 (2013) General] Skinnysloth:
Update after further testing:

Grounded: holding the tablet or using it with the usb cable plugged into the computer.

Ungrounded: using the tablet on a nonconductive surface, not plugged in with the usb cable, not holding the device.

The touch issues/dead spots are only present when the device is not grounded as defined above. The following is a report when used in the ungrounded state.

TS10- No dead spots until triggered by using three or more simultaneous multitouch, which produced phantom touches. Then there was a narrow band of dead space which seems to not be in the same area all the time. Multitouch when using two fingers was still present, but not a readily apparent.

The dead band goes away after a reboot. As long as the phantom touches aren’t triggered, there are no dead areas.

TS20- Inconsistent touch response at bottom 2/3 of screen in portrait mode. Largely unresponsive at the top 1/3 of the screen with single finger input. When using multiple fingers, the screen is responsive regardless of the area touched. There are still some multitouch issues, but not as obvious as in TS10.

TS30- The device acted similarly to TS20 in regards to touch input.

TSunlock- Similar to TS20 and TS30. May be slightly more responsive in the top 1/3 of the screen.

Bottom line, TS10 didn't completely solved all my issues, but worked a lot better than stock.
[Nexus 7 (2013) General] cocchiararo:
My tablet seemed fine on JWR66N, and started having "sticky touches" on JSS15Q.

TS10 seems to have fixed it.
[Nexus 7 (2013) General] mi7chy:
My stock N7 2013 was issue free before the latest JSS15Q OTA update. Now, the virtual keyboard randomly gets stuck and, worse, Great Big War Game now freezes almost every game and the only way to unfreeze it is to switch to home screen then back to game. Or, sometimes it'll unfreeze on its on if you wait long enough and present the 'app not responding' window and prompts you to ok to close or wait.

Was tempted to try this but decided to boot to recovery to clear cache first. Sure, enough. Doing so seem to have resolved the keyboard stick and freeze issues. To clear cache, power off, hold volume down+power, select recovery, hold power+volume up then select clear cache.

Also, change your 'key long press delay' under Google keyboard advanced settings to 500ms to minimize the false positive pop-up menu.
[Nexus 7 (2013) General] sfhub:
Just for you I added some experimental stuff to the first post.
[Nexus 7 (2013) General] :
I have a July 32gb, my light touch issues were fix with ts10. I tried up to 5 finger touches even if I don't use more then two and all is great so far.:good:
[Nexus 7 (2013) General] will25u:
Thanks for this! I had the grounding issue on top of my screen and ts10 completely fixed it as far as I can tell. I will be testing this for a couple days to see if anything unusual arises and post back.
[Nexus 7 (2013) General] cnims:
It is possible to get these in flashable zip format so we flash with TWRP or another custom recovery?
[Nexus 7 (2013) General] lespaulman67:
I am exchanging mine today for sure. I still have tons of problems with mine.

When I get the new one and fire it up and if it has JWR66N or JSS15J or what ever the other ones would be. Should I not update it to the JSS15Q.

I think I should hold off with the JSS15Q OTA till Google comes up with a fix again.

I will let you guys know what date I get and how it runs.
[Nexus 7 (2013) General] sfhub:
Did you get a chance to try the experimental ones I added to the first post?
[Nexus 7 (2013) General] trvbone:
What's exp about them?
[Nexus 7 (2013) General] lespaulman67:
You talking about the 10,20,30 ?

I did everyone of them and restored the Nexus 7 between fixes and still had issues.

The best one was 10, It took the dead screen away for good. I was left with really bad swiping problems. Swipe up and it would open a new web page. Or swipe up and it would zoom out if I was zoomed in. It was really bad. Other than the swiping problem it would of been perfect.

I even was on the XDA forums here and I was swiping up as I was reading and boom some porn page popped up on its own. This was with the #10 fix.lol
[Nexus 7 (2013) General] sfhub:
No, I'm talking about 11, 12, 14, 16, 18, and 25

boot-ts-exp1.7z

I built them just for you :)
[Nexus 7 (2013) General] lespaulman67:
I am trying it right now. TY

---------- Post added at 11:00 AM ---------- Previous post was at 10:40 AM ----------

starting with #11 Dead screen fixed, 2 finger touches was all over the place. Tried it in Google Earth and it just started to jump all over.

#12 dead spots fixed. 2 fingers real bad. When you put fingers straight with each other it drops the connection under your finger and shows touch screen. Very bad on multi touch. Swiping left to right and up and down did not cause any problems with #11 or #12. So swiping is better.

#14 just the same as #12 with some swiping issues. Very bad 2 finger touching.

the dead screen touch is good on #14 also.

Well I ended on #16 ran out of time. Going to take back Nexus 7.

#16 had great touch response, but the multi finger was still bad, The swiping was good.

I hope I get a good one this time. Going on 6th tablet.lol
[Nexus 7 (2013) General] cyberprodigy:
sfhub, I love you with all the virtual love I have. You fixed my device's touch-screen problems and finally gave me a perfect device. Thank you so much.
[Nexus 7 (2013) General] sfhub:
They haven't been tested by me as thoroughly. I left them in a separate package because most people should be ok with just 10, 20, 30. Only if you have real issues after trying those would I suggest trying the experimental ones.
[Nexus 7 (2013) General] SubMatrix:
Great work sfhub, nice to see a dev step up to right the wrongs Google made.

For me, my experience on JSS15J was perfect multitouch, with single touches sometimes not being registered (not holding tablet, and not plugged in). On JSS15Q, the touch experience remained largely the same. Here is my experience with the 3 files:

ts10: Immediately noticed better single touch response. In fact, all single touches were registered. However, when testing double touch, and imitating a pinch to zoom/shrink action, often the connection will be lost and no touches will be registered at all (YAMTT will ask you to touch the screen). As I continue with the pinch action, the connection will be picked up again. Effectively this is like a "skip" in the pinch action.

ts20: Single touches were not being picked up, similar to my experience before trying these files. Multitouch seemed fine, though I didn't do extensive testing since for me, single touch performance is the main thing I'm looking to improve.

ts30: Similar to ts20, single touches were not being picked up sometimes.

All tests were performed at 95%-100% battery. I think I'll go with ts10 for now, unless sfhub has a better idea of why ts10 might not be perfect and maybe a suggested tweak (perhaps one of the experimentals?). I'd rather have perfect single touch and some slightly dysfunctional multitouch than the other way around. I will also note that for ts10, if I'm holding the tablet, the pinch action works fine.
[Nexus 7 (2013) General] sfhub:
I have tested one unit where pinch zoom behaves like you described.

I found that I could keep my fingers 1" apart during pinch/zoom instead of touching each other (so start 1" apart during zoom in, and stop 1" apart during zoom out) then I could avoid the multi-touch issue. Also helps if you start them diagonal from each other rather than aligned vertically or horizontally.

I found that to be a more workable solution than dealing with dead spots, which I could not avoid as easily, especially when typing on the keyboard.
[Nexus 7 (2013) General] viralbug:
Thank you very much! You are very dedicated in following up with the touchscreen issues and have helped a lot of us.

I have a 32GB made in July. 10 was good but had a little multi touch. 20 had both multi touch and single issues much like what I'm facing. 30 seemed to be best for me, there was very slight multi touch problem.

My main problem of missed touches has been well eradicated with this. Thanks a lot. Hope Google pushes an official update very soon.
[Nexus 7 (2013) General] afremont:
Cool stuff. Are the 10, 20 and 30 versions equivalent to the JWR66N, JSS15J and JSS15Q released versions? Have you done any experimenting with the "calibration" file in /system/usr/idc/elan-touchscreen.idc? Perhaps that has something to do with people (like my wife) experiencing better performance with older releases even though the digitizer retains the newest firmware.

Even after downgrading my firmware, to the JSS15J version (A038), I get some ghost touches on my tablet when it isn't being held (laying down flat on couch). If I use three fingers to make a sort of right triangle and rotate them, it will create phantom taps and touches at what would be the fourth corner of a rectangle. They appear when the axis cross.
[Nexus 7 (2013) General] coolsilver:
More I use my Nexus 7 deb (LTE) with JLS36I seems like when unlocking my swipes have been more broken than before. It still seems to register taps as before but sometimes will fail depending on how I tap with my finger. I am just wondering why and if I should try some the fixes here.
[Nexus 7 (2013) General] sfhub:
IMO it is worth trying. There's a reasonable chance you'll see improvement and even if not, everything is reversible.
[Nexus 7 (2013) General] wanfeilwong:
Manu date: June 2013

Original problem: intermittent dead spot at top 1/3 of the screen when not grounded

After messing around with ts-10 fix for a while I found that it introduced ghost touches, but it recognized every tap I did. Tried ts-20 and 30 but they had same issue as my original problem. Then tried ts-11 and it registered every tap with fewer ghost touches than ts-10.

ts-12 seems like the keeper for me. registers every touch and haven't had a ghost touch yet.

Thanks again sfhub, I can start playing games and typing on my 7 again
[Nexus 7 (2013) General] WoozyBE:
[MENTION=1299673]sfhub[/MENTION] Thank you so much! First one I flashed solved all my screen issues! :laugh: My nexus 7 is absolutely perfect now! Thanks again! :good:
[Nexus 7 (2013) General] ralexand:
TS10 Worked for my sticky touch

I just got a replacement 2013 N7 after I sent the first one back for touchscreen issues. The first thing I did with the new one was unlock the bootloader so that if it had issues I could easily try your fixes.

Using the Multitouch app on the Store I was getting a "Sticky" touch after anywhere from 50-150 touches, pretty consistently. I tried TS10 and made it nearly 400 touches with no issues. It seems my problem is fixed.

Thanks!
[Nexus 7 (2013) General] Xirix12:
WOW. I haven't had enough time to do this until tonight. The screen has been driving me crazy. ts10 worked perfectly for me. The screen and the buttons were pretty horrible from the beginning for me. This has fixed the touchscreen!

Thanks!
[Nexus 7 (2013) General] mi7chy:
The combination that fixed sticky touches for me and made it usable is ts10 plus reimaging with factory image (remove -w from batch file so it doesn't wipe data) and wipe cache. Happy with the N7 2013 now.
[Nexus 7 (2013) General] DarkusC:
NS20 works for a little bit.

My N7 worked perfectly fine until recently, I did a System Update and got some touch screen issues.

I didn't notice it too much until I started playing Dead Trigger 2 though.

It works fine with a single touch, but when trying to play with a dual-touch control set, the right touch jerks around.

It makes in very hard to aim in FPS games, as you can imagine, when my characters viewpoint constantly shakes around.

I tried several of the TS files, and the closest it came to being like it was before the update is TS20.

TS20 works fine, only having very few "jerks" every so often.

The odd thing is, it works fine for a little while then goes back to jerking badly.

It persists after reboots too.

But flashing a different TS file, then going back to TS20 makes the same thing happen, it works for a little bit then just stops helping.

I have no idea what to do at this point.

Is there any kind of system update "rollback"?
[Nexus 7 (2013) General] sfhub:
Had you played Dead Trigger 2 prior to the System Update? (so that you have a baseline to compare to) or only after you had done the update?
[Nexus 7 (2013) General] DarkusC:
I had not, I did the system update just before downloading DT2.

However, I also played MC4 before the update, and used the Multi-Touch Test app several times beforehand.

Now the problem persists in those, and all other apps.
[Nexus 7 (2013) General] sfhub:
The reason I ask is I've played dead trigger and it can sometimes get jerky independent of the touch screen.

What os version were you on prior to system update?
[Nexus 7 (2013) General] DarkusC:
I'm not entirely sure, I was just doing the OTA updates as they were offered.

I'm on build number JSS15J, Kernel version 3.4.0-g365a6e0, Android 4.3
[Nexus 7 (2013) General] sfhub:
If it were me, I'd install ts10, then factory restore to jss15r.
[Nexus 7 (2013) General] Caelrie:
Thank you!

Thank you for this!

I love my nexus 7. It's my go-to internet device on the road (tethered to my phone), but the touch screen was so squirrelly it was actually unpleasant to use. It always thought I was tapping things in the middle of scrolling, which made using it miserable.

I flashed ts.10 and after 2 reboots it's like a whole new tablet. I hope it sticks.
[Nexus 7 (2013) General] mishko:
Same issue here with DT2 when using ts10. Flashed ts12 and it's an improvement but still not perfect.
[Nexus 7 (2013) General] InfX:
First of all, sfhub, thanks for your efforts.

I've stumbled upon this thread after experiencing a nasty, erratic, touch screen behavior on a completely new N7, kinda feels like uncalibrated (offset) and not filtered enough for tiny motions, but also dependent on HW factors, such as the surface the device is on. Couldn't say it is totally unusable, but is way, WAY more finicky than any capacitive touch screen i've ever used.

The first thing i've tried is your ts10 bootloader. It seemed ok first, but under some conditions it sensed an entire column getting random touches on some surfaces, in some screen areas, during a single touch, so it was a no-go.

Seeing the amount of the bootloaders to try, yet not having much time to mess with it, while not being completely illiterate neither HW nor code-wise, could you please describe, technically, what did you patch in those bootloaders and what do the numbers mean, so one could try it in a more sensible way? What is it? Some kind of sensitivity? Recognition threshold? Filtering enabling/disabling? Bits from both? Which ones?

Also, why do you have to do this from bootloader? Can't you put it in kernel, controllable from proc, or something?

PS: Don't take this post as a complain, by any means.

PPS: Thanks again for the effort.
[Nexus 7 (2013) General] thecapsaicinkid:
Has anyone here seen a stock N7 on the latest update with a perfect touchscreen? (when not grounded) Do they exist?

Is a single, adaptive software fix to cover the variances in screen hardware even possible?

Is anyone using the official Asus screen protector and did you try removing it?
[Nexus 7 (2013) General] sfhub:
Every screen is slightly different so you are just going to have to try them out. Start with 10, 20, 30. Make sure you do a couple of reboots for each one so the calibration can settle in.

If you find one that is close but still could improve, try the experimental #s near the one that works best for your screen.

It is being done in the kernel, not the bootloader. You are just using the bootloader to load the kernel.
[Nexus 7 (2013) General] DowntownJeffBrown:
This^^^

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] LittleConfucy:
Undetected random touches

Has anyone ever had some random undetected touches every once in a while? Because I have never had many multitouch problems, but I have always had this problem (regardless of the ROM or kernel).:(

Edit: just tried ts10, and it fixed it all. Thank you so much sfhub
[Nexus 7 (2013) General] DarkusC:
I'm kind of new to Android devices still, since my device is rooted and flashed with a custom recovery (TWRP) can I still just "factory reset" back to stock that easily? Should I back up my save data and all that?
[Nexus 7 (2013) General] sfhub:
Do a backup in twrp *and* copy the twrp directory onto your PC for safe keeping.

Then do the factory restore.

You mentioned you are on jss15j, for WiFi version, that means the previous version you had (jwr66n) isn't available as a factory restore.

I would try jss15q factory restore nowipe option here

http://xdaforums.com/showthread.php?p=44888268#post44888268
[Nexus 7 (2013) General] creeve4:
Occasionally when I tap an option on a pop-up dialog box the tap is only half registered. E.g. I tap "Yes" and the yes button is highlighted, but the tap is not fully registered because the pop-up dialog remains.

Could this be related to the multi-touch issue? Anyone else experience this?
[Nexus 7 (2013) General] DarkusC:
I see, thanks for all your help. I just realized you're the same guy that started this threat to begin with.

It may not have worked as well for me, but seeing all the posts here and the definite changes each ts# does, I just want to say excellent work and thanks.
[Nexus 7 (2013) General] sfhub:
BTW try jss15q first and if that doesn't help try jss15r. Have ts10 installed before hand.
[Nexus 7 (2013) General] LittleConfucy:
I have one problem that persists regardless of the fix, it's when I put 3 fingers vertically aligned: more touches appear an they juamp all over the place. But when I align my fingers horizontaly, it works like a charm.:mad:
[Nexus 7 (2013) General] DowntownJeffBrown:
Is this real world usage or just what an app shows?

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] NekroWolfen:
Ok after spending some time with ts10 and ts20, the problem still happens, but today I decided to try those others from ts03 to ts18... After awhile with ts12 I couldn't believe, for the first time with this tablet I can use photoshop pointer feature(multi-touch) and not having the pointer go crazy. I'm about to cry, I'm finally able to draw with my Nexus 7... also no ghost touches with the keyboard.

I seriously hope it stays that way!