yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] l2icky:
First off I want to state that I am not done attempting different things, but I would like the input and help of the community and others that know more and have more experience than myself...

I bought a Nexus 7 Flo 32 from Ebay. When I got it, it was awesome. Loved it, then the touchscreen issues started.... The touchscreen issue is crazy. The screen becomes completely unresponsive. Most the time I can just turn the screen on and off 1 to 50 times and it eventually works.. When it doesn't work, and I have to hold the power button for 30 seconds, the device will boot into fastboot, but it will not boot past the Google screen, neither for the OS or Recovery... I have to let it set while powered off for xx amount of time...I flashed ts10, it hung at in fastboot, fastboot reboot didn't work, I had to hold the power down... It did it's usual thing and wouldn't boot. It's been sitting for 20 minutes and it's finally booting.

This happens with EVERY ROM I have tried including flashing stock images.. Liquid, AOSP, etc. CleanROM is the one I have found that it doesn't occur as often as the other ROMs. I can not use a custom kernel whatsoever. It renders the device unusable. I am currently on Scott's 4.4.3 stock rooted de-odex. I wanted to try it to see if it fixed anything, it hasn't.

I am going to test ts10-30 over the next few days and I'll keep this thread posted on my results.

Any input would be awesome. Thanks gents.
[Nexus 7 (2013) General] mdamaged:
ts10, ts11 and ts20 seem to be the ones that helps the majority, so I would try them first.
[Nexus 7 (2013) General] l2icky:
Thanks. I'm trying 10 now, I'll try 11 next.
[Nexus 7 (2013) General] mdamaged:
No worries.

Sometimes one has to reboot several times, and it can take sometime for the fix to settle, give it a day or 2 along with several cold reboots.
[Nexus 7 (2013) General] godutch:
I would suggest opening up your tablet and reseating the display connector, if you are out of warranty. It takes less than 10 minutes and is pretty easy to to. See the thread below for a how to:

http://xdaforums.com/showthread.php?t=2535835
[Nexus 7 (2013) General] mdamaged:
If the issue is due to a faulty connection then yes, but not all ts issues are due to this.
[Nexus 7 (2013) General] l2icky:
I manage a computer and cell phone repair shop, I did that first thing.
[Nexus 7 (2013) General] godutch:
If you touchscreen is unresponsive try ts11. Mine is hypersensitive with a lot of ghost touch but ts11 made the tablet go crazy.....

I wished [MENTION=1299673]sfhub[/MENTION] could tell us the difference between the different ts files but he hasn't been online for over 6 months :(

---------- Post added at 08:56 PM ---------- Previous post was at 08:36 PM ----------

I think it's best to solve any easy to fix hardware problems first before you start trying to workaround them in software
[Nexus 7 (2013) General] l2icky:
I'm not getting a chance to test them for any length of time. I have tried ts10 and ts11 and both are rendering the device useless.

Looks like I'll just go down through the list and see if I can hit one that works.
[Nexus 7 (2013) General] mdamaged:
What do you mean? If you mean you boot into them and they bootloop at the balls, that's normal, because the kernel is a 4.3 kernel, but the fix is still applied, let it stay at that bootloop for at least 2 mins, then hold power until it shuts off, reboot and the fix will be applied, do not try and use the touchscreen while it boots, then once it boots, wait 2 min to let it settle, and reboot again.
[Nexus 7 (2013) General] l2icky:
I know that. I do that... Well, try. It boots, touchscreen is unresponsive, freezes, then won't go past the Google screen. I wait it with the device off. Power it on, it boots... I let it completely boot, 2-5 minutes, then reboot... It reboots... Then freezes, reboots itself, doesn't go past the google screen. Ts 10, 11, and 20 did the same thing. I would get it to finally boot, give it a few minutes, reboot, then it would freeze while using the touchscreen and when it would restart itself, it wouldn't go past the Google screen. When it did, it just did the same thing again.

Just now, I was trying to type this out on the tablet, the screen became unresponsive during texting and I had to reboot the devive via the power key. Once again, it will not go past the Google screen.
[Nexus 7 (2013) General] mdamaged:
That's...odd.
[Nexus 7 (2013) General] trvbone:
OK peeps here's my situation:

Nexus 7 currently on 15q not rooted or unlocked, my touchscreen works very well except for occasional dead touches/non-responsiveness.

From reading here I'm guessing ts10 will be my best bet unless someone can suggest something otherwise.

Where do I start? unlock root then ts10? Or flash back to previous build then ts10 then ota update... I'm super confused by the different routes people are taking to get to perfect touchscreen result.
[Nexus 7 (2013) General] danvee:
Simplest should be to unlock (no need to root) then perform the described install of ts10.
[Nexus 7 (2013) General] trvbone:
K thanks
[Nexus 7 (2013) General] sfhub:
Ahh, I thought he meant the new replacement unit he got looked sharper and the fix preserved the usability.
[Nexus 7 (2013) General] player911:
Yup, just unlock and flash.

All this does is flash over the existing touchscreen firmware. Shouldn't matter what rom you are on, since it will over write it anyway. Once you flash 15Q, you have 15Q firmware until you flash the fix.
[Nexus 7 (2013) General] astuermer:
Device: Nexus 7 32 GB WiFi

JSS15Q with HW Version "rev_e"

Stock has several ghost touches for me.

20 and 30 are completely unusable for me, flickers as soon as I move a finger on the screen.

10 ist best so far, but with the following issue:

When I put a second finger on the screen the first touchpoint starts to flicker as soon as I cross the axis of the other one.

This can be noticed best when playing eg. Dead Trigger:

When you move with the left thumb in a direction and somehow cross the horizontal axis with the look-thumb on the right side, you suddenly look straight up because of the flicker...

Good work so far, makes it more usable! :good:
[Nexus 7 (2013) General] lespaulman67:
your exactly right!!!!!!!! That's what I mean. For some reason I think the JSS15Q affects the video quality also. I remember going from the JWR66N on my last one. It was really crisp then after update it looked dull. I know my eyes aren't playing tricks with me. Even you tube videos look better.
[Nexus 7 (2013) General] afremont:
twrp is a recovery program so you would want to flash it into the recovery area using "fastboot flash recovery twrp.IMG". If you flashed into the boot area, that could lead to all kinds of weird stuff when it tried to boot. Sounds like you got of working now, have fun.
[Nexus 7 (2013) General] lespaulman67:
People if you are on JWR66N and are afraid to run the JSS15Q do not fear it.

Pick the boot-ts10-lock.img and load it up. Then install the JSS15Q it will keep it from messing up your display driver. Mine came out of the box perfect and I preserved it. Now running JSS15Q and it runs so freaken awesome you wouldn't believe it.

Try it out and post back.

If you have the JSS15Q installed and can take it back do it. Get your new one and do what I did and your good to go.:D

Big Thanks to sfhub for the great work he has did. Great help also. This guy needs to work for Big company's to help with the programming and drivers and OTA updates.
[Nexus 7 (2013) General] trvbone:
Why would you need to take it back doesn't the ts10 file reverse the problem caused by 15q?
[Nexus 7 (2013) General] sfhub:
One of them will, but when folks finally get something that works for something that seems so fickle, they tend to want to follow the same ritual so as not to upset the multi-touch gods :)
[Nexus 7 (2013) General] bossman013:
thank you!!

sfhub... dude. nice work. i just got my new nex7 and the touchscreen honestly wasnt all that bad. did have any ghost touches, but did notice some unresponsiveness while typing, and quite a bit of sticky touches. I just unlocked it to try this.. applied ts10 and boom. it seem perfect. im going to play with it some more tonight, but right now it looks alot better. thanks a ton!! hopefully this will keep working til google and get their stuff straight. you should be pretty proud. :good::good::good:
[Nexus 7 (2013) General] lespaulman67:
no it doesn't reverse the driver. if its on there before hand it keeps the new driver from overwriting it.
[Nexus 7 (2013) General] afremont:
Oh yes it will replace an updated firmware with the one supplied in the images that you booted. The order you do things makes no difference to the final outcome; either way you end up with the new system ROM and older firmware for the touchscreen. The only difference is that if you update the system first, before locking in your favorite firmware, you will have to tolerate poor touch performance while doing the firmware upgrade. Nobody needs to take their tablet back unless none of the firmware images that sfhub provides works for them. Pretty cool huh?
[Nexus 7 (2013) General] lespaulman67:
You take a perfect screen and install the JSS15Q and it screws it up there is no going back. I had a perfect screen prior to the JSS15Q my last Nexus 7 and none of the fixes fixed it.

This time I installed the #10 fix with my perfect screen just as shield from the JSS15Q. So when I installed the bad update it would not even effect my screen that was perfect. I f there was a screen fix from Google you would have to run the unlock fix and remove the fix you have or Google fix will not work.
[Nexus 7 (2013) General] Sud0lit3:
I tried the experimental 25 and it stabilized a lot of my jitter. near the axis however it feels as if there is a magnetic attraction between the points. Like if they are crossing x or y axis slowly. but that one for me has been the absolute best by far.

There is also this feeling/sensation as if the touch screen is like say 20 - 50 ish milliseconds behind from the input. Kind of doesnt feel instant but its pretty close to it.

I hope this helps you man. maybe you can come out with something like version 27 that'll kick ass and fix the problems xD

if there is anything i can help with do let me know.

thanks,
[Nexus 7 (2013) General] afremont:
That may be how it seemed to you, but I promise you that when you run sfhub's images it flashes (and locks in) firmware regardless of what was there previously. The problems with your previous tablet must have gone beyond what the firmware variations could cope with. It's not just a protective measure, it will also "repair" firmware that has already been updated.

Between OTA releases, there seems to be more than just the actual embedded firmware changing. Even though backing an update out (going from the Q release back to J for example) would not roll-back the embedded firmware, some people (such as my wife) would still experience various levels of improvement from going back to an older system release. That indicates that other software changes as well as the embedded touchscreen firmware when the OTA release changes. Your previous tablet was just a dud that couldn't be helped; it wouldn't have mattered if you locked in sfhub's firmware before the update. There were a couple of others like your previous tablet that just couldn't be helped, but a great many people that were already running JSS15Q were able to be helped.

I'm not trying to be argumentative, I just want to make sure that others don't skip trying sfhub's firmware because they already applied the system updates to JSS15Q. A good many of them can still benefit. Enjoy.
[Nexus 7 (2013) General] bossman013:
question...

Bear with me here...

So let's say I'm running "update A" that I got OTA from Google. Then I apply ts-10. Everything's fine, etc. A week from now Google pushes "update B" to my phone, I install it and its applied to my tablet. So I'm now on "update B" with the ts-10 firmware.

THEN I apply the ts-unlock you posted here. At that point would I them be running the firmware from "update B" from Google or would I be running update B with the touchscreen firmware from update A?

Sorry, I tried to make that as simple as possible. Just curious. Thanks again!!!
[Nexus 7 (2013) General] lespaulman67:
This is the point i'm trying to make. I think you will still be running update A drivers just on the screen. Because ts-10 blocks it from updating.

Unless you uninstalled the ts-10 before you do a Google update.

Here is what he says.

Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.

Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
[Nexus 7 (2013) General] afremont:
After you "unlock" his firmware, it (sfhub's) will still remain present until another update (C) pushes through. IOW, you would be running update B with sfhub's firmware after the unlock; the same as before the unlock.
[Nexus 7 (2013) General] l2icky:
I know, haha. That's what throws me off. I read a lot of other peoples touchscreen issues. Thread after thread, all over the place. Non of them match my problems. I've had it for a month or so now and I've just dealt with the complications. I flashed Ts01 and it seems to be doing better than 10, 11, or 20 so far. It had problems at first, not wanting to boot, etc. Now that it's booted, it seems to be functioning well. I'll keep everyone updated. I'm not sure what to do. I thought maybe it was power issues, I've taken the board out, checked every thing. I just don't know what else to try. I'm hoping that I can find a TS that will work. Only time will tell.
[Nexus 7 (2013) General] pjmarkert:
4.4.3

Just wiped and installed android 4.4.3 that just came out yesterday, seems to be fixed. This is without the 10 fix.
[Nexus 7 (2013) General] danaff37:
Weeping in recovery doesn't clear the fix; you have to flash the unlock zip. Wiping and flashing a new Rom leaves the fix in place.
[Nexus 7 (2013) General] mdamaged:
Weeping never does anyone any good. Instead, stay strong.
[Nexus 7 (2013) General] danaff37:
Damnit Swype. Lol
[Nexus 7 (2013) General] abemore:
4.4.3

I've been running ts11 on 4.4.2 happily.

Just updated to 4.4.3 (and also switched to ART) and now if I touch the screen with 2 fingers and hold them in place, 7-9 ghost touches will spazz vertically across the screen as long as I hold my fingers in place. Only my other hand fully palming the back of the tablet is enough grounding to stop the ghost touch spazzing and allow me to pinch zoom. Reboots don't help. So I'll try reverting back to the original ts.

EDIT: I switched back to Dalvik and the problem disappeared. Still on ts11.
[Nexus 7 (2013) General] Daniel2553:
Thanks i hope this work

hello i have been having multi touch problems and i test this o hope this work..
[Nexus 7 (2013) General] GatorsUF:
not sure if this has been mentioned, but I hope this fix resolves my issue. My multitouch seems to work ok for the most part, my biggest issue right now is that my touch screen becomes completely unresponsive at times. I have had it quite a few times where I turn the screen on but I cannot unlock the device and the screen just times out. If I keep trying it eventually works again.

I am hoping this fix resolves that, but I am not sure it is even aimed at that issue.
[Nexus 7 (2013) General] dieandromeda:
it help a lot. im using t10 and it work fine...
[Nexus 7 (2013) General] JazzieBoi:
thanks, worked for clash of clans zooming in and out and boom beach
[Nexus 7 (2013) General] sam298:
Updated to 4.4.4 stock with my ts-10 intact. has dead spots when not grounded same results when used unlock to remove the patch. if grounded, works fine. Planning to try ts11 or ts20.
[Nexus 7 (2013) General] sam298:
Looks like 4.4.4 wiped my ts-10 driver. Flashed ts-10 after 4.4.4 update (updated using wug's kit not thru ota) and now working fine with no issues.
[Nexus 7 (2013) General] hugosouto:
Anyone tried to install Android L developer preview to see if the touch issues are gone?
[Nexus 7 (2013) General] DeDanMU:
I'm running Android L on my Nexus 7 (2013) and I have no touchscreen problems anymore. Before I had dead spots when the tablet lies on the table. And sometimes ghost double touches. Everthing is gone. And the new keyboard is better. I make much less typos than before.
[Nexus 7 (2013) General] k3lcior:
Hard to believe as it's rather hardware than software problem. (grounding issue)
[Nexus 7 (2013) General] ahow628:
I've got a N7 2013 and in the bootloader it says hardware is rev_e. So far 20 is looking like it fixed the issue.
[Nexus 7 (2013) General] f0ssa:
omg.... my new nexus have touch issues wtf......?! where fix ground?

---------- Post added at 11:51 PM ---------- Previous post was at 11:34 PM ----------

GOOGLE DIE PLEASE! My touch is not worked
[Nexus 7 (2013) General] k3lcior:
Plug in USB, or headphones or hold it in hands.. only fixes I came around ;s

Tapnięte @ Nexus 7 II.
[Nexus 7 (2013) General] f0ssa:
I want to use it in bed is not holding, Well try these days to pick up the money from the store, took only a week
[Nexus 7 (2013) General] f0ssa:
How u flash ts driver with wug kit?
[Nexus 7 (2013) General] AndyYan:
I think he means he flashed Android L with Wug.

Sent from Google Nexus 4 @ CM11
[Nexus 7 (2013) General] niscrulez:
I've tried ts10,ts11,ts20 and ts30. Ts30 is the best here.

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 (2013) General] spartacus279:
After many test and running each ts for a couple of days I have concluded that ts-25 is the most stable for me and its working perfectly now on android L , thanks
[Nexus 7 (2013) General] sam298:
Yes. I flashed the google image thru Wug which erased my driver. So i flashed ts-10 per OP's instructions.
[Nexus 7 (2013) General] pjmarkert:
Working nicely with android L and no ts.
[Nexus 7 (2013) General] EduMonzter:
been using ts10 and working fine, after flashing 4.4.4 screen seems to work perfect
[Nexus 7 (2013) General] rob61280:
This also seems to be the case for me.

R
[Nexus 7 (2013) General] yoncy:
I have the problem with ghost touches only if i leave the tablet untouched a long period of time (over the day, when coming back home and start using it). A restart fix my problem, always it's ok after restart. It's just me with this pattern?
[Nexus 7 (2013) General] StarShoot97:
Version10 seems to work for me fine, right now. Have to see if it stays like this over the next couple of days.
[Nexus 7 (2013) General] rofore88:
A lot of thanks!

You've saved my nexus.:laugh:

Adorable, man!:good:
[Nexus 7 (2013) General] sakuhei:
Same. Tested a number of them and ts25 bring no more ghost touch or unresponsive screen like others!
[Nexus 7 (2013) General] myepicyear:
You guys realize that every touchscreen device gets these complaints, including the beloved iPhone...right? This issue is not unique to any one device. Check out this one of many scattered Apple support threads, currently active, that dates back to 2012:

https://discussions.apple.com/thread/4326234?start=210&tstart=0
[Nexus 7 (2013) General] WSZR:
How does it move through WugFresh?
[Nexus 7 (2013) General] mdamaged:
It doesn't, these are not meant to be flashed, you must use the method outlined in the OP.
[Nexus 7 (2013) General] rileylarche:
Use a toolkit?

Hey guys, I'm considering a tempting this I get buggy multi-touch and dropped touches on the right side of my device (where the camera is) now this is erratic to sometimes it will pick up touches and sometimes not, but when using multi touch it is always buggy

First off can I use this toolkit to skip using adb? http://xdaforums.com/showthread.php?t=2430708

Next based on my description of my issues what package would you recommend I start with? Or just cycle through them all?

I am also running the latest kit kat 4.4.4

Thanks!
[Nexus 7 (2013) General] mdamaged:
Read the post above yours...though option 11 might work, just make sure you BOOT the ts* images and NOT flash...I still don't recommend it.

Start with ts10, then ts20, some people had luck with ts11, some with ts30.
[Nexus 7 (2013) General] _jis_:
Do you own Nexus 7 (2013)?
[Nexus 7 (2013) General] myepicyear:
Yep, last year, I bought one the week they came out. Me and many others on this forum (and elsewhere) have never had a single problem with it, and overall, are incredibly happy with it.

There are actual defective units, (again...like any good brand can have) I am not trying to dispute that. I'm just saying there is no indication that Asus has a ratio of defective to non-defective units that is any higher than the next manufacturer. There are so many circumstances in which people can experience an issue like this--and true defects only make up a portion.. There are the actual defective units--and then there are people who lie about defects to get endless replacements because they are convinced that there must be something wrong with every unit but they're just not seeing it yet, (OCD), there are people who get this bug by suggestion (aka: placebo), and then there are people that just don't handle touchscreens "properly"/consistently, in the way they were calibrated to be used..(i.e.: some people put too much force on them--or are just overly aggressive in general, some people swipe too abruptly, some people swipe too long, etc..)

Basically, there are a multitude of reasons why some people experience this on touchscreen devices. I was just trying to make a point that this isn't everyone's experience, and it's one of the most common device complaints to fill any and every major flagship device's forum upon release. Again, every new iPhone gets this complaint...along with every Galaxy S release, every HTC release, blah, blah.

So, once more: yes, I do own this Nexus tablet (and the last one). I don't go around XDA pretending to own devices that I do not, just to fit in or something. Haven't been to the forums in a while, but I was curious to read other's impressions of Android L.
[Nexus 7 (2013) General] ahow628:
So are you saying this is a widespread problem or not? I'm confused about your point.

In any case, I own a Nexus 5 that I play Clash of Clans on and touching multiple spots on the screen quickly and rapidly has no issues. Doing the same on my Nexus 7 2013 results in about one out of every three touches not registering. Ts-10 didn't work, ts-20 reduced it to 1 in 6 or so, and I haven't used any others yet but plan on testing them out.

Also, I fix iPhones and test out their screens after the repair. Out of my 50 or so fixes, I've never experienced lack of touch responsiveness that the Nexus 7 2013 has.

Bottom line, this is an issue and it sucks it hasn't been addressed officially.
[Nexus 7 (2013) General] k3lcior:
And this is what i hate the most.
[Nexus 7 (2013) General] _jis_:
I am sorry to bother you, but I asked you just to be sure because you have My devices section empty.

Ok, so please test your touch screen if it is flawed as on any other N7II by Nexus 7 II Tester and tell us the result. I don't know any other device on the market with such a severe design defect and so horribly flawed touch panel which is so prone to EM interference. You can test with this app all your other Android touch screen devices, I am sure they will be ok.