yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
Unfortunately Paul Wilcox is not really the person in charge and we are quite aware of his past communications.

Basically he said they are aware of the problem, came out with a fix that made things worse for more than a few folks, then said they know it is still an issue, but then no communication for 6 weeks despite him responding to other posts. Since the acknowledgment that the touchscreen is still an issue after their attempted fix, they have come out with another update that did nothing to address the touchscreen because it included the same touchscreen DSP software as before.

BTW the thread you pointed to is no longer active and it is continued on another thread of the same title.

Multi-touch - reports of improvement, no improvement, and some worse

Multi-touch (continued) - more reports of fixed / not fixed for JSS15R

Multi-touch (alternate) - more discussion
[Nexus 7 (2013) General] MohamedYousri:
is it safe to use it with the latest update Stock Android 4.3 (JSS15R)

also is there a way to determine which file i shall use or i have to try one by one ?!

Thanks for this great effort :good:
[Nexus 7 (2013) General] sfhub:
It is safe with any ROM. It may or may not provide improvement depending on how much variance is in your screen. If you need to revert, just run the ts-unlock.

You just need to try the different files. They are ordered in most to least likely to help.
[Nexus 7 (2013) General] hyperspacey:
It'll take a lot longer than six weeks to find a resolution and I'd rather Paul just got back when he had something new to report. Nothing happens fast in development, especially when it comes to hardware. You take a **** and it's a month before you're given authorisation to wipe your ass.

My theory is that Asus got a load of defective touchscreen-digitiser panels from their supplier (if you balls up adhering the digitiser to the display panel you're going to get a lot of issues with touch detection) that went into production units, they cut QA standards to meet launch yields, and now they're trying to patch out a hardware defect via software, which is going to have a negative effect on working units.

There's not really anything Google can do except attempt to force Asus to do a product recall for defective units (embarrassing but good for consumers who get their machines replaced) or wait for Asus to try and patch around it. Given Asus took 8 solid months to get a fix to the storage issues around the 2012 N7 I'd suggest this could take a while.
[Nexus 7 (2013) General] MohamedYousri:
Thanks , applied boot-ts10-lock and will try it later , i know the problem and can feel it while chatting and using keyboard so i will try and give you my feedback

i used boot-ts10-lock for now

when shall i use the files in boot-ts-exp1 and boot-ts-exp2 ?!!

and if i flashed the device with factory image this will remove this file effect ?!
[Nexus 7 (2013) General] sfhub:
Everyone is welcome to their own opinion.

There was confusion introduced by your use of the slang term which some people in the US interpreted to mean some new person named heid bummer at Google was corresponding with us.

Now that it is clear you were referring to Paul Wilcox's original posts, there is no more confusion.
[Nexus 7 (2013) General] hyperspacey:
I would dearly love it if there was someone who worked at Google called Heid Bummer.
[Nexus 7 (2013) General] SchrodingersCatSK:
As requested...

I installed all three.

The first one significantly improved the edge jitters. It didn't remove them completely, but at least they're only changing in the last decimal place instead of all of them. I haven't field-tested this version well enough to know if it eliminated all the typing issues but I'm optimistic.

The second and third didn't appear to behave any differently than the stock software.

I'll use this for a few days and see if it solves the problem. Otherwise, I'll wait a few weeks and swap it under warranty. The issues I'm having aren't serious enough to rush it back right away, so I'm optimistic it will get solved under some software update or another.
[Nexus 7 (2013) General] hyperspacey:
I just blat blatted these into my somewhat okay, but occasionally sticky-touched Nexus 7. 10 totally gubbed the touchscreen if you weren't holding it- one bloody great touch-insensitive area along the middle of the screen- but 20 seems to be working fine. More info as it happens.

On the plus side, knowing 10 breaks the touchscreen quite a bit means I can probably flash it and wave it angrily at the staff of PC World if a "definitely not ****" batch arises.
[Nexus 7 (2013) General] SchrodingersCatSK:
Update after a few hours

I uninstalled the fix, thinking "It wasn't really that bad." I noticed the difference right away. Hold-clicks weren't working, sporatic touches were happening... I had forgotten to unplug the USB during comparative testing which is why it "wasn't that bad."

I've re-installed (v10) and it's definitely different. The hold-clicks are working flawlessly, I'm not getting any weird things with drag... Definitely keeping the fix.
[Nexus 7 (2013) General] Gareee:
I'm not sure I'm having any issues at all, but am considering this.

The only issue I see occasionally is the keyboard freeze some people have mentioned. rotation and pinch zoom seem fine even is flat on a table.

Is it worth seeing if this will fix that keyboard freeze?

Also, does the unlocker go back to stock, or once unlocked do you have to install the stock touch again?
[Nexus 7 (2013) General] graffixnyc:
Last night I flashed the unlock img on the LTE N7 and got stuck in a bootloop. I had to flash the stock boot.img to get it to boot.
[Nexus 7 (2013) General] DowntownJeffBrown:
Only you know if it's worth running the fix on your tablet. The unlocker will take you back to whatever rom or version of stock u are usings touch settings again.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] Gareee:
Cool. I'm running the kang CM with its kernel.
[Nexus 7 (2013) General] graffixnyc:
I just got off the phone with play support.. I honestly didn't think I had an issue until I ran some display testing apps. I made a video of my LTE version runnint 4.3.1 and it's Ghost touches in Gamma detection.. I showed the video to support and he couldn't believe it. After some troubleshooting he said they will submit a replacement request and he saw the video after I explained the issue and he said "wow, when you explained it, I didn't think it was that bad"

[YOUTUBE]DSjhFjDauK8[/YOUTUBE]
[Nexus 7 (2013) General] tni.andro:
Interesting. My flo does exactly the same in the gamma test, although it's normally fine. It looks like the gamma test creates an interference/noise pattern that the touch screen controller doesn't properly filter out.

Can anyone actually do the gamma test on a N7 without the ghost touches?
[Nexus 7 (2013) General] graffixnyc:
Also happened with the "screen tester" app right before the non solid color patterns..

[YOUTUBE]kbZ0l0sYaGI[/YOUTUBE]
[Nexus 7 (2013) General] sfhub:
After unlocking, upon first reboot (keeping in mind rebooting is part of the install process) you will be on whichever touchscreen software came with the ROM/kernel you have installed.

Basically, unlock, reboot, and you will be reverted.
[Nexus 7 (2013) General] sfhub:
fastboot boot boot-ts-unlock.img

NEVER overwrites or touches your installed boot.img

At worst all you would need to do is press and hold the power button for 30 seconds until the tablet rebooted, at which point it would be running the boot.img you've always been running. Now if you did "fastboot flash boot boot-ts-unlock.img" by mistake, then you might need to reflash the stock boot.img, but that is why the instructions specifically are written the way they are.

Regarding the gamma pattern, every N7 2013 screen I've come across has that behavior irrespective of how touchscreen behaves under normal operations. IMO it isn't really a significant issue unless you must have that pattern as your background image.
[Nexus 7 (2013) General] graffixnyc:
I tried rebooting after flashing the unlock and I just kept hanging at the bootanimation screen. It wouldn't boot until I flashed the boot.img from the system restore images from google. I had even tried reflashing the unlock img and it wouldn't boot :( Odd..
[Nexus 7 (2013) General] sfhub:
I am at a loss to explain what happened in your situation then.

Are you on stock ROM? (kernel, I assume you are stock)

I'm a little bit curious how what you described occurred. I've literally ran these a couple hundred times on different units people asked me to look at and never had a boot issue that couldn't be resolved with a reboot.

Certainly never had a situation where a stock boot.img had to be reflashed.
[Nexus 7 (2013) General] rockingondrums:
sfhub, sorry to beat a dead horse but I have a question: Do these changes get swept up in nandroid backups? I'm assuming not, but I got my warranty replacement today and since I cannot skip the setup wizard (sans SIM card AND wifi connection), I'm going to push a backup and restore it via TWRP. I don't want to inadvertently carry over any touch improvements when I test this new unit.

Also: whenver I flash with fastboot boot ___.img, the tablet NEVER reboots to android on it's own. I've left it for more than 10 minutes. I will just restart with the power button. It seems to change things, but I just want to make sure it's not a placebo.
[Nexus 7 (2013) General] sfhub:
The touchscreen software in the boot-ts*-lock.img would not carry over with a nandroid backup.

It probably doesn't boot because these were built using a wifi kernel or you are using a custom ROM.

It doesn't matter as far loading the touchscreen software is concerned. As long as you get that 20 second pause before the Google logo comes up, everything was installed.

So basically, if you do fastboot boot and Google logo comes up in a few seconds, then no touchscreen software was loaded. If it takes 20 seconds before Google logo comes up, touchscreen software was loaded and it is not relevant whether it completes the full boot. Just wait a few minutes for stuff to stabilize and press/hold Power for however many seconds it takes to reboot. It'll then go back to using your existing kernel, but the touchscreen software is already loaded.
[Nexus 7 (2013) General] angry english:
Call me crazy but ever since Installed ts10 my battery life has been fantastic, can this really make it better? Im not imagining it neither lol
[Nexus 7 (2013) General] player911:
I had that with ts10. It worked well but ts20 worked even better. I had a hard time playing games with ts10. It wasn't all the time but it would occasionally spaz out. Ts20 doesn't do that for me. Really no issues I can think of. Ts20 also increased my sensitivity some.
[Nexus 7 (2013) General] player911:
Sure makes sense if the touchscreen was in overdrive before and getting all confused, eating more CPU cycles and drowning. Could be a placebo effect though but makes sense.
[Nexus 7 (2013) General] lomonic:
Oddly enough but not surprisingly i've been running into "more" touch related problems (stucked touches, missed touches, some fake/ghost touches) lately with heavier usage. A reboot usually fixes it for a while. Tried TS-10 before and didnt feel like there was much diff. Decided to give it a try and use TS-20. Results so far have been fantastic. I will report back in a few days.
[Nexus 7 (2013) General] andyman_187:
do you get unregistered touches on ts20? i tried both ts20 and ts30, and i will often get unregistered single or multi touches whenever the tablet is on a flat surface/stand/pillow/has no body contact. ts10 was the only one that worked better for me (except for that issue with unregistered pinching i mentioned)
[Nexus 7 (2013) General] rondera:
I bet Google will fix that with 4.4, so they don't make an update for 4.3, because 4.4 is coming in a few days :) my theory :P
[Nexus 7 (2013) General] MohamedYousri:
after testing the device for almost a week now i can definitely say that the problem is almost fixed :good:

very huge improvement comparing to original status

many thanks for this excellent work :laugh:
[Nexus 7 (2013) General] lomonic:
I read your post and tried the ts20. Didn't have a great experience with ts10 before and didn't bother with other versions.

Have run for a few hours now, and intensively testing it in games and typing this message. I've not encountered any of the problems at all, not even a single stucked touch, ghost touch or missed touch so far.

Gee sfhub, what is the special sauce in ts20?

I'm gonna use it for more days to weeks and will report back again. It sure fixes everything for me now.
[Nexus 7 (2013) General] netespl:
Just tested ts10 on my stock JSS15R and finally I have no problem with touches when not holding device :) Thanks a lot for this fix.
[Nexus 7 (2013) General] transekid:
I would realy love if this were true, but i realy doubt that, if the storage problem in nexus 7 versionn 1 took 7 months to repair, one can doubt a quick fix for this new version... But hey maybe i'm being a pessimist.
[Nexus 7 (2013) General] Rymafyr:
Thanks to sfhub!

I just want to give my thanks to sfhub on this work. I was about to return my Nexus 7 2013 until I grew a pair and decided to try his fixes. I tried ts10 and while it helped I still had the issue of losing a touch and it coming back in the same swipe. Normally not a big issue but when swiping it could cause lots of fun. I then tried ts20 and I now have no issue with the touch screen. I see no reason to try the ts30 patch.

For the record, I get no ghost touching when I test through the Developer options showing the touches or paths. YAMTT seems to be too sensitive by comparison and I don't have any confidence in the app. I can get ghost touches to happen, but it seems to occur only when you have touch points too close together. So fingers touching and then registering two touches on the screen can cause a ghosting to happen but only in that case. I'm not sure that is a hardware or software fault; it makes sense to me, with two touches so close together, the display would get confused.

I also wonder how useful it is to have 10 point touch locations on a 7 inch tablet. A piano app is too small on a 7" screen for two hands and I have smaller hands. I can't even imagine another app where you would need more than 3 simultaneous touches.

My only real question, since I have refused to install the update JSS15R sitting in my notification bar; is it absolutely true the update will not overwrite the ts20 patch? Stupid to ask I know but I'm still a bit 'gun shy' on this fiddling around.
[Nexus 7 (2013) General] lomonic:
I'm on ts20 with jss15r. If ur r unsure, u can always reflash ts20 again anytime. Easy thing to do but it should stick. Ur situation is very similar if not identical to mine and ts20 totally resolved many of my problems. Intensive game plays over the past 12 hrs with no reboots HV not caused major problems. I still stay away from chrome thou.
[Nexus 7 (2013) General] sfhub:
Yes
[Nexus 7 (2013) General] DowntownJeffBrown:
Yea that's correct. You will stay on ts20 till you run the unlock. Sfhubs fix is a great solution to a problem that we shouldn't have.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] Rymafyr:
updated to JSS15R and running smooth. Thanks again.
[Nexus 7 (2013) General] sfhub:
The core problem is caused by hardware variances. There is always variance within the specs. Sometimes that variance is outside specs. Not clear where this variance falls. Software usually takes into account expected variance. Sometimes it can handle unexpected as well.

If they can, they will adjust the software to compensate for the variance. It might or might not ever get fixed. There might be a partial fix. Google isn't communicating anything regarding this issue any more. Now that many folks have a workaround, perhaps not enough people are complaining so they don't feel the pressure any more.

Upon first reboot (which is part of the process of applying the unlock) you will be using the original touchscreen software that came with your OS/ROM/kernel
[Nexus 7 (2013) General] sfhub:
Nothing was ever written to the flash memory you are thinking of. After the reboot, everything is gone, no traces.
[Nexus 7 (2013) General] lomonic:
after a day with ts20 its all working well except i encountered an instance when the system just froze and requires a reboot.

im just gonna try ts 30 and see how it works
[Nexus 7 (2013) General] sfhub:
That freeze is a different issue with your tablet unrelated to ts20.

If I had to guess, it is probably an intermittent CPU or memory issue.
[Nexus 7 (2013) General] Sensamic:
I think I've got the issue.

Just tried playing Asphalt 8 again and on some moments of the gage, when racing, when I turn the car slightly to one side (left or right) and then pull my finger away the car still goes to that side and crashes. This never happened to me on the Nexus 10.

Will exchange next week probably and see how that goes.

If this touchscreen issue is so widespread and so many people are having it then it could be more software related, or it could be a hardware problem from early on.
[Nexus 7 (2013) General] jarrodstrachan:
So after having my nexus for about two weeks, the only problem I've had with it is a few touches sticking, for example when using the keyboard a key would stick, particularly annoying when the key that sticks is the backspace key. Anyway the ts10 fixed this for me. Cheers
[Nexus 7 (2013) General] lomonic:
I dunno. I've never had such an issue before. It froze with a touch showing on the screen..like a permanent touch. Actually it happened twice. First time it recovered after 5-10secs. Not the second.

Anyways I have new news to update. Decided to try something after the crash...tried ts30 and stuck touches comes back almost immediately after 2nd reboot. Then I tot of trying something between ts10 and ts20, so I picked ts16. Was having some erratic behaviour after 2nd boot, 3rd reboot was bliss and have been very reliable since. Tried it on intense racing game, web browsers and all. Just perfect now.

Question here really would be what's the diff between ts20 and ts16? 16 seems a keeper for me. I typed this entire post with no problems.
[Nexus 7 (2013) General] SimFox3:
Tried all three versions (ts10, ts20, and ts30) for about 10 minutes each in YAMTT. Ts20 and Ts30 feel about the same as stock--a tap or two is missed every ~20 taps.

With ts10 I counted 200 consecutive registered taps with no gaps. Thank you! Thank you! Thank you! With three or more fingers, the pointers still get a little crazy, but so far I haven't been able to reproduce any problems with just two fingers (though I didn't have any ghost pointer issues with two fingers on stock either).
[Nexus 7 (2013) General] lomonic:
So ur on ts20 too? I'm trying ts16 at the moment, give it up to 3 reboots. Its working very well like ts20 but has no odd crashes, at least for now

Let's compare notes after a few days
[Nexus 7 (2013) General] Pfeffernuss:
Flashing this mod will not increase the chances of crashes, whatsoever. If the tab is unstable it's because of something else.
[Nexus 7 (2013) General] Cedwebx:
You're a god !!

Thx for your help bud !!

3 nexus 7 2013 on my hands and YOU solves this screen issue.

Before : Quite impossible to put a shortcut on my desktop. Ghost touch, or no response.

After TS10 : 99% perfect shortcut, no ghost at all but few no reaction from the nexus... have to touch again to have something.

Thx again !
[Nexus 7 (2013) General] MAJED.y:
I have LTE version with touch problem, and it was very obvious when using keyboard.

Flashed boot-ts10-lock.img and my problem has fixed. :good:

Thank you.
[Nexus 7 (2013) General] SimFox3:
Darn--after about 12 hours ts10 is having lots of issues. Even dragging a single finger across the screen results in the pointer intermittently not recognized. After a tablet reboot, ts10 starts behaving fine--but same issue if I try again after 10 minutes. Has anyone else experienced this?
[Nexus 7 (2013) General] sfhub:
Try letting your tab charge or discharge depending on when it was working best.

Sometimes the voltage sent to the screen varies slightly with different battery levels and that can affect the screen.
[Nexus 7 (2013) General] lomonic:
Technically no, but well I'm not alone experiencing it with ts20. But touch works with other parts of the CPU/GPU too. Touchmark covers a lot on these details. Nevertheless ts16 is working a charm no lags, no freezes just perfect even after a full day of intense usage typing gaming etc.

http://appleinsider.com/articles/13...fast-screen-response-to-laggy-android-tablets

Awesome work by sfhub

---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------

I experienced this and a few others in this thread too. A few of us found ts20 working very well after a few reboots. I get some odd freezesnwith ts20 and so far ts16 is working perfect. Feel free to try them and give them at least 3 reboots if u can. Juz personal hands on experience.
[Nexus 7 (2013) General] Matrix_19:
Take a look at this thread :

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

I think all nexus 7 have this issue.

However it is happening only with this specific test/display : the problem occurs when a 1x1 pixel checkerboard is displayed.

My guess is that you will have the same issue after the replacement.

But you shouldn't get this bug with a standard tablet usage.
[Nexus 7 (2013) General] digiboy1:
Hey, thanks for all the hard work you've done in making these for us.

Nexus 7 2013 is my first android device. I had symbian before :silly: and did a lot of flashing and stuff there.

Now, I'm not quite sure how to do what is told on the front page.

I have few questions too :

1. Any pages/tutorials I should read before proceeding on with the instructions on first page?

2. Would installing these bootloaders/img files also delete all my apps, and data? Is there any way(without rooting) to have backup of them and restore them, if they get deleted?

3. Could anyone just help this newbie with links/instructions through which I'd be able to (hopefully) make my touch better as well.

Returning isn't possible for me, since I imported my tablet from US.

The touch problems have greatly increased with recent updates. I remember, when I had got it, it didn't have much of the issues.

Thanks :)
[Nexus 7 (2013) General] sfhub:
Just read about unlocking bootloader in sticky thread at top.

These updates are very safe. Nothing is written to the regular flash memory so the chances of losing your data is extremely low. It is always best to backup, but IMO you'll be fine even if you don't.
[Nexus 7 (2013) General] player911:
Flash TS-20

I was getting that too with 10.
[Nexus 7 (2013) General] digiboy1:
How do I backup my apps and their data then? Without rooting?
[Nexus 7 (2013) General] sfhub:
I use titanium which requires root, but I have heard people mention mybackup for non-root
[Nexus 7 (2013) General] deewad:
I would recomment you to root your device to make a full nandroid backup via custom recovery. But I also think you dont really need a backup. It's always gold to have but I did those touch caused flashings a thousand times without any troubleshootings. The process is very clear and takes a short time. Just follow the instructions in the first page.

For root and CR i would recomment you the wug-toolkit which you can find somewhere in this forum ;)
[Nexus 7 (2013) General] Cedwebx:
I tried and finnaly get back to TS10.

BTW the difference with stock is impressive and TS10 or TS20 give me better result than stock.

Thx :)
[Nexus 7 (2013) General] M3thos:
Thank you!

I made this account to personally thank you, sfhub, for making my nexus 7 useable again. I live in Bangkok, Thailand and had a friend bring me one, so return was not an option. I can't thank you enough for taking the time to make these fixes for the community. Cheers!