yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
You might just have a unit like the 4th one I tested on which was bad from the start.

It seems TS10 did the best for you. I would try loading that one more time, rebooting, then do a factory reset.

Then plug it in and do a full charge.

Play with it overnight, sprinkling in some reboot fairy dust.

If it is still troublesome tomorrow, then return or exchange.

I have noticed some units change their behavior over time. It might be because they are on the edge to start and slight differences in battery/current behaviors push them over the edge. It may be because some calibration takes place.

You can see that your screen doesn't have a true dead spot because the different versions are shifting the spot around. It is just in the context of how it is being filtered, it may be farther from expected than the surrounding areas and can't be accounted for properly. Effectively as an end-user it is probably the same as a true dead spot, but there is at least hope it can improve if can still be detected in that area.

Also I have found with dead spots, sometimes it changes if you tap lighter, switch to your pinky or thumb, or switch to the other hand (I am not joking with these, even though it may seem I am)
[Nexus 7 (2013) General] Skinnysloth:
I was having grounding touch issue, ie, if I wasn't holding the tablet, some touches weren't getting registered. YAMTT confirmed this occurred at the top 1/5 of my tablet in portrait mode. Used boot-ts10-lock.img and so far so good. No grounding touch issue in any area of my screen. Had to register just to say thanks. Finally my tablet is working as it should be. :victory:
[Nexus 7 (2013) General] liorec:
i was playing around YAMTT after applying TS10 and found out there were grounding issues when using 9 or 10 multitouches, touches get stuck after removing my fingers for about 3-5 secs, sometimes longer. but i can live with this since i don't use more than 5 multitouches anyway. still many thanks for this fix!
[Nexus 7 (2013) General] sfhub:
Yeah, I got tired of doing 20 point multi-touches with my fingers and toes too. Figure I would never use the tablet in this way so I concentrated on just what I would use and said (like you) I'll live with the problems I'll probably never see :)
[Nexus 7 (2013) General] sfhub:
In your case, there's really only 2 to try. IMO it will take you longer to write and think about which one to try than to try them.
[Nexus 7 (2013) General] Ricowan:
Oh, ok cool. Which two should I try?
[Nexus 7 (2013) General] sfhub:
10 anbd 20
[Nexus 7 (2013) General] bandit_knight:
Yes I have tried the experimental ones. They were worse that the ts10 for me. It seems that all in all the ts10 was the best for me but also on it I was getting some ghost touches for example in games that use two finger gestures to pan/zoom. They were occuring only from time to time but when they happened to occure they could be quite persistent and reproducible. For instance I had a case when two fingers gesture in the upper right part of the screen in landscape was causing a ghost touch on the "task switcher" soft key. I had to reboot to get rid of it.

Thanks for help :) I decided to stay on stock for the time being. At least until the "sticky" touch bug gets annoying enough to try your fixes again :)
[Nexus 7 (2013) General] Yadao:
ts10 is doing the same thing on mine. It's not very frequent, but when it does happen, it's pretty bad.
[Nexus 7 (2013) General] blahb:
I was really ready to return this device until I flashed the ...10.IMG thanks for the fix this device now usable and awesome again!
[Nexus 7 (2013) General] Gordon Ramsay:
Just curious, if you flash one of these, and then decide you want to install a recovery and go with a custom rom like cyanogen, do you need to reflash the fix in the bootloader?
[Nexus 7 (2013) General] DowntownJeffBrown:
[MENTION=220042]gordan[/MENTION] ramsay

No it will stick through anything even updates from google till you use the boot-ts-unlock.Img

Sent from my HTC One using Xparent BlueTapatalk 2
[Nexus 7 (2013) General] jaredmorgs:
I'm running fedora 19 and decided to try this procedure using the android-tools package (we're lucky enough to have adb and fastboot packaged for us on fedora).

The only thing that stumped me about your excellent procedure set was the "fastboot boot <image_name>.img" step.

I was getting <waiting for device> errors and was wondering what I was doing wrong. Then I searched for a solution and http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro gave me the fix.

I need to run fastboot as superuser.

::facepalm::

So "sudo fastboot boot <image_name>.img" fixed my issue.

I'm running the "10" package now and will see how it performs over the course of today.

Thank you so much for posting this possible fix for us all, and thanks to [MENTION=1790051]TaintedByte[/MENTION] for compiling the awesome FAQ where this post was mentioned.
[Nexus 7 (2013) General] thecapsaicinkid:
Is it even possible for Google to fix this with an OTA update? My tablet works fine until I put it on my plastic tablet stand.
[Nexus 7 (2013) General] danvee:
Yes. They can - if they want to or care enough to.

IIRC, the first update (out of the box) loaded different firmware, and, for many, that's when the trouble really began.
[Nexus 7 (2013) General] thecapsaicinkid:
Even taking into account the variances in screen hardware between devices? Seems difficult to fix with a single one size fits all update.
[Nexus 7 (2013) General] danvee:
They use 3 different manufacturers.

The update can carry firmware for all 3.

The software just needs to identify the hardware and install the correct firmware.

Your PC does it all the time; it's called 'plug and play'.
[Nexus 7 (2013) General] player911:
Exactly. Shouldn't be hard to identify which hardware set you have and make adjustments accordingly.

Maybe it caught Google off guard. Maybe this is Asus's booboo. Perhaps why the fix fixed the bad ones but broke the good ones. Google will fix it. I've been around the block a while with Nexus devices and every single one of them seem to have touchscreen issues (drivers) out of the gate. They all get patched and forgotten. Didn't the OG N7 have some weird issues too?
[Nexus 7 (2013) General] ice20978:
Well I'm pretty confused:

I'm running the JSS15R stock rom, was getting pretty common breaking of gestures (swiping on the keyboard doesn't work very well for example) and rarely some sticking. As many have noted this pretty much only occurred while not plugged in, and seems when not being held. Everything would also usually be fine for the first ~minute after a reboot and then would start showing problems again.

I tried all three mods a couple of times:

ts-10 seemed to help a little with the breaking of the signal issues. still cant swype on the keyboard reliably.

ts-20 seemed either as bad or worse than stock

ts-30 seemed quite good for a good 10+ minutes, but then became as bad as before.

Not really sure what else to try :/
[Nexus 7 (2013) General] DowntownJeffBrown:
Not sure if they will help you but have you tried the experimental packages in the op?

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] sfhub:
From my experience looking at many units and looking at the source code, they only have 1 touchscreen manufacturer, elan.

The following is irrelevant for touchscreen. I know someone theorized there were 3 LCD vendors, but in current production, I don't believe that to be true. There is code to handle multiple LCD vendors, but I have only ever seen the JDI panels.

The identification for the hardware does not allow for different driver selection, ala plug-and-play, because it is the same, despite the hardware variances.
[Nexus 7 (2013) General] danvee:
Thanks for the clarification. :thumbup:

If that's the case, why is this such an elusive issue to nail down?

Are the parts that far out of spec?

3 updates later and yours is the only solution; producing 80%+ positive results if not a straight out cure.

15R not only made my touchscreen and freezing worse, but introduced waking rebooting which had only previously happened during sleep.
[Nexus 7 (2013) General] hyperspacey:
It's low-quality hardware, pure and simple- Asus are letting marginally-working units through QA to keep yields up, and odds are they're forwarding high-quality units to Google to keep them sweet.
[Nexus 7 (2013) General] danvee:
Possibly, but a friend bought 4 units from Google directly.

All 4 reboot, freeze and have touchscreen issues (to varying degrees, but all effected).

Google will be getting all 4 back and will be sending 4 new ones out.

ASUS must be slipping up....
[Nexus 7 (2013) General] rockingondrums:
You know you don't have to quote the ENTIRE OP.
[Nexus 7 (2013) General] ap4lifetn:
Is it possible to use a custom kernel with this fix? I flashed a custom kernel but upon reboot it reverts back to the stock kernel, not sure if the bootimg lock is responsible or not.
[Nexus 7 (2013) General] mi7chy:
Here's my dilemma. Stock R OTA, ts10 and ts30 cause random sticky touches (have show touches enabled in developer options). ts20 causes random complete freezes for about 10 secs where nothing responds. About to try ts25 unless someone has already been through this and can suggest a specific version to fix it.
[Nexus 7 (2013) General] thecapsaicinkid:
[YOUTUBE]https://www.youtube.com/watch?v=ZZFj_rby6WA&feature=youtube_gdata_player[/YOUTUBE]

Here's a video of my screen issues. Perfect on a table, terrible on a stand! Does anyone have a new N7 which works perfectly isolated on a stand? I'm not convinced if I return it I'll get one which does work perfectly on my stand.
[Nexus 7 (2013) General] toobers:
Fixed my screen

I've been so disappointed with my touchscreen since the day I received it, not reading my finger or my stylus unless I'm holding it a specific way, while crossing the fingers I'm not using, standing on one leg and praying to the gods. Your fix was amazing and VERY satisfying. Thank you for all your hard work!:victory:
[Nexus 7 (2013) General] iamnotkurtcobain:
+1

The ts10 file made my N7 usable!!

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) General] madphone:
mine seemed to be fixed with ts10 but i'm noticing other bugs now:

before fixing it had the prpblem not recognizing touches around the edges of the screen while not holding in my hands. Now thi is fixed. but now when you swype on your screen it interrupts the recognition for a millisecond. that causes apps to recognize a double tab.

and i can't install any custom kernel any more. it boots very slowly with graphic-glitches and freezes. on any kernel.
[Nexus 7 (2013) General] pablo130r:
Hi All

I bought my Nexus 7 in February 2013, so I assume it is 2012, right?

In the last couple of month it became unusable due to touchscreen issues. So google about it and arrived to this forum :good:

Before I try to install this packages, I´d like to know if they will work in my 2012 tablet.

Here you can see my Nexus 'working' :crying:

youtube.com/watch?v=QtUeZOsHWHg&feature=em-upload_owner
[Nexus 7 (2013) General] DowntownJeffBrown:
No they won't. This is for the n7 2013 only

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] player911:
Make sure that you are giving each fix ample time to calibrate itself and settle. I would use mine for a few days to let it iron out. A few reboots added in for good measure.

If you just flash and test, you will get all sorts of weird results.

And this is permanent [until you unlock it by flashing the unlocker.img]. This means that it will stick across custom kernels, roms, bootloaders, stock rom updates, full restores, etc. Once you flash this once, it is done. You don't have to reflash every time a rom update comes out. ONCE you find a working fix, just leave it alone and enjoy your tablet.

The ONLY reason you would need to mess with it again is if a new update came from GOOGLE that is a better fix. At this point you would have to Unlock then flash Google Update.
[Nexus 7 (2013) General] sfhub:
As mentioned by prior post, do a couple of reboots overnight.

If after 3 reboots you are still seeing glitches, it has nothing to do with this fix. Instead you should look at the custom kernel you are flashing and whether it works well with the ROM you have. Not all kernels can work with all ROMs.
[Nexus 7 (2013) General] ap4lifetn:
so it's possible to use a custom kernel and still have this fix applied? I ask because I flashed francokernel, and on the first reboot it seems to register the francokernel, but subsequent reboots puts it back to the stock kernel. I don't have any glitches or performance issues as I'm on the stock rom and its mostly a stock kernel.

My thinking was that the device either loads the francokernel, or the touchscreen fix, and not both... any info?
[Nexus 7 (2013) General] sfhub:
Problem is somewhere in your flashing procedure.

There is ABSOLUTELY NOTHING in this fix preventing you from running ANY kernel or ROM you want.

Did you actually flash francokernel to persistent memory using

fastboot flash boot franco.img

or did you just do a temporary boot using

fastboot boot franco.img
[Nexus 7 (2013) General] ap4lifetn:
thanks for the clarification, that makes total sense. I have only been doing fastboot boot. Both images were .img files so i feared that one overwrote the other.
[Nexus 7 (2013) General] ccrows:
So what's the latest with the touchscreen issues? I've been wanting to upgrade to this tablet from the original, but I've been hearing about touchscreen issues with the 2013 version.

Also anyone here have the original N7 and this one as well? Was it worth the upgrade? TIA!... :)
[Nexus 7 (2013) General] madphone:
ts-11 seems to work pretty good!

many people are having touchscreen issues when the device is not used with two hands. There are different issues, but no bug fix from google that helps everyone. but with this fixes over here many should find one that helps. but isn't a big deal anyway i think.

The performance is compared to the nexus 7 2012 edition way way better which suffered from bad storage and slow tegra cpu. build-quality is much better too, so are the speakers. the screen is good but alone it isn't a reason to switch. android 4.3 is almost the same, fast but boring and the tablet feels like ab big phone cause of the lacking tablet apps. but that should be no problem for you if you liked your old nexus 7.
[Nexus 7 (2013) General] ice20978:
Hm, is this actually true? Is the software actively re-calibrating itself? I'd be pretty surprised if it were, but if so, that may be a possible explanation for why people are seeing such varying performance...
[Nexus 7 (2013) General] mikeserv:
Ditto that, especially considering the touchscreen patch firmware developer seems to believe it should be good to go after reboot #2, or at least he did on page 1 of this thread. I managed to get 6 or so pages in before skipping to the end...

Any very helpful info between there and here you care to recommend?
[Nexus 7 (2013) General] ccrows:
Anyone else have the OG N7 and this tablet at one time?

With the touchscreen issues and all, do you still think that it was worth the upgrade?

The screen resolution really doesn't matter to me, it's more about the performance. (Since I thought the OG was kinda sluggish at times)

Actually I would have pulled the trigger a long time ago, but the touchscreen gave me second thoughts.

I sincerely appreciate any and all opinions on this matter. THANKS... :)
[Nexus 7 (2013) General] desmondso99:
part of my screen isnt responsive. i sent my nexus for repair and took it back after two weeks. he told me touchscreen hardware, or something i dont exactly know, has been replaced.

But i find my nexus still having the same issue: that part which is not responsive just moves to the right side. that's what he called "fixed"

now i have tried all of them again

touchscreen is extremely smooth with no glitches using ts10. Just works perfectly. But this wont last long ( just like before i sent it ).

after a few hours part of the screen becomes unresponsive and the issue is back again. and all the rest have different multi touching issues or other glitches

i am not convinced asus can fix my nexus anymore, just hoping Google will really release a fix for this:(
[Nexus 7 (2013) General] mikeserv:
I have them both.

I ordered the new one the day it was released on Amazon - I guess a couple days before Google's Play Store. I bought it specifically for video-out, but it is definitely noticeably faster and more capable in pretty much every way.

I didn't have any touch screen issues until recently, and though even these are not severe, long-touch for copy-paste has become a daily annoyance. I assume one of Google's more recent stop-gap PR firmware updates screwed it up, which leaves me hopeful that one of the images offered here or some other can undo it. Worst case Asus will have to replace it, I guess.

Again, the performance is noticeably better in evert aspect. Louder, truer, now stereo sound, front+rear cameras, bright, crisp, beautiful, display, better battery life, sleeker, lighter, package, and instantly responsive to any UI action except, lately goddammit, copy+paste.
[Nexus 7 (2013) General] curmudgeon56:
Less than ts10?

Are there files for less than ts10?
[Nexus 7 (2013) General] sfhub:
I have them but it is unlikely they would work any better so I haven't bothered posting.

If you really want to try, I added

boot-ts-exp2.7z

to the first post.
[Nexus 7 (2013) General] thecapsaicinkid:
I spoke to Google support recently and they absolutely will not even acknowledge there are issues with Nexus 7 touchscreens or they are investigating a fix.
[Nexus 7 (2013) General] DowntownJeffBrown:
Google support doesn't even work for google. After your phone call or email the may answer the phone for Robs Rugs or any other company. They are a 3rd party customer support company. They read from a manual and that's the only answers they can give.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] sfhub:
I might be extremely pie-in-the-sky optimistic here, but I would have expected after over 2 months, somebody at Google would have updated the manual :(
[Nexus 7 (2013) General] DowntownJeffBrown:
Everytime I've had to deal with them or others from what I've read they just deny any knowledge bro. It's ridiculous...

Now there is people who work on these issues but we can't talk to them. In fact when I dealing with the whole n4 limbo fiasco I was told by the floor manager that they can only email Google themselves. Meaning their own customer services service rep bosses don't even have a direct line to Google. Just emails like when they are having you deal with a specialist it's just all emails between you the csr and the supposed Google specialist.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] sfhub:
Thinking about it, I'm surprised they even pay people to answer the phones rather than just routing your call to Google Now or Siri. The customer will at least have a chance of getting a useful answer.
[Nexus 7 (2013) General] DowntownJeffBrown:
Lol that's so true.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] ice20978:
Anyone get the 4.3.1 update that was released today yet? Wonder if it has any digitizer improvements built in...
[Nexus 7 (2013) General] sfhub:
The kernel included in JLS36I (the LTE 4.3.1 update) is the same as JSS15R, therefore the touchscreen software is the same as JSS15R.
[Nexus 7 (2013) General] sfhub:
Ahhh, brings back memories... Sure, Apple charges more so they don't have basic issues like typing. Bringing back iPhone to exchange only to find replacement still has issues with sensors? check, already done that with nexus 7.

http://www.wired.com/gadgetlab/2013/10/iphone-5s-ios-7-issues/#slideid-214581

Typing Delays

Some users are experiencing typing delays on their iPhones and iPads after upgrading to iOS 7. If you're experiencing this, first try resetting the iPhone by going to Settings > General > Reset > Reset All Settings. If that doesn't do the trick, Twitter user [MENTION=1079242]deanc[/MENTION]orp suggests first toggling the iCloud setting Documents & Data to off, then back to on again, and then resetting the phone.

http://www.wired.com/gadgetlab/2013/10/iphone-5s-ios-7-issues/#slideid-213671

iPhone 5s Sensors Incorrectly Calibrated

If you plan to use your new iPhone 5s as a level, a compass, or to track your activities using its gyroscope or accelerometer, you may find things are a little...off. That's because those sensors aren't working properly on some iPhone 5s units.

This issue could be a big one. For now, it's unclear if it's a software or hardware problem. On top of that, the specific issues people are experiencing seem to vary quite a bit. If it is hardware related, it's going to be a challenge for Apple to issue a software-based fix. Some people who have affected units are already taking them back to the Apple Store and swapping them out for new ones. That seems to be the only fix for now. Even then, some customer's new units still have gyro, accelerometer, and compass abnormalities.
[Nexus 7 (2013) General] thecapsaicinkid:
Has anyone got anything useful talking to Google, like they are working on a software fix?

So if devices were largely fine before the update, does that mean the touchscreen firmware was originally adaptive in some way to account for variances in the hardware?
[Nexus 7 (2013) General] danvee:
Dead silence, as if they're completely unaware that there even is a problem.

The latest 'update' made mine worse, plus added waking RRs which hadn't been present previously.

Clueless, careless or indifferent: hard to tell which.. Also, note that in talking to Google tech, they're just outsourced support and limited to the script at hand. I don't blame these people - they're just doing what they're paid to do given the scripts they have been provided by Google.

More's the pity.
[Nexus 7 (2013) General] hyperspacey:
Google's product forum heid bummer has said they're still working on it. Given the delay between the Nexus 7 2012 storage issue being flagged and a fix being introduced I'd be patient.
[Nexus 7 (2013) General] danvee:
I must have missed that.

Do you have a link, please?
[Nexus 7 (2013) General] andyman_187:
using ts10, ghost touches have completely disappeared for me (they used to happen only when the tablet is on a surface/stand and is not in contact with any other parts of my body except for my fingers on the screen). i do notice now that instead of getting ghost touches, i'm getting inconsistent touch registration when using 2 fingers (using YAMMT, and simulating pinch to zoom, the touches would disappear and reappear sporadically, but no more ghost touches at all). this only really gets annoying when browsing the web with the tablet propped up on the table and trying to pinch zoom. other than that though, HUGE HUGE improvement over what i used to experience back on stock. THANK YOU for this!
[Nexus 7 (2013) General] sfhub:
heid bummer is a real person? Or is it slang for head honcho?

Where is this post BTW?
[Nexus 7 (2013) General] transekid:
how long did it take for that fix? any aproximate ETA on the touchscreen fix?
[Nexus 7 (2013) General] angry english:
Thanks for this, i tried the 1st image this morning and it seems to have instantly fixed my screen issues of laggy typing and hold to move icon presses
[Nexus 7 (2013) General] hyperspacey:
http://productforums.google.com/d/msg/nexus/W0Hfkq8hf-c/6jp8oXIPQZMJ

"Heid bummer" is West Coast Scottish slang for "person in charge", "heid" meaning "head" and "bummer" meaning "person who bumbles about".