yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] mhannigan:
Made my tablet explode

I used the ts10 file, and after the reboots it seemed slightly better.

I used the ts20 file, and it was not working well.

I used the ts30 file, went through the first reboot and then on the second reboot, I saw signs of smoke coming out from between the screen and the bezel and I heard a *pop*. I shut it off using the power button and turned it back on, saw the Google logo and then my tablet burst into flames. I quickly poured my coffee on it to put out the fire, dried it off, and now I can't get it to boot at all.

Also, my dog was too curious and it shot a smoldering piece of Nexus 7 plastic into his left eye and he keeps blinking.

We evacuated down the back fire escape as a precaution. My dog couldn't see very well, so he opted to take the stairs. He tripped half way and basically bounced the rest of the way. Nobody was seriously hurt. Is this the expected behavior of ts30?

Not sure what I should do next. Thanks.

Mike
[Nexus 7 (2013) General] jfriend33:
I have a moko ultra slim smart case with the auto wake and magnets for closure. Also a screen protector. I tried removing these before adopting the TS fixes. No changes. Seems like most success is with Ts11 except for a select few people.

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] abemore:
ts10 UPDATE:

2 weeks running ts10, I started seeing some occasional multitouch issues. So I grabbed a multitouch test app from the Play store and was able to clearly reproduce my issues in the test app.

I just applied the ts20 file and could not produce any issues in the test app. Will see how it turns out after some time.

ts20 UPDATE:

After 1 day of running ts20, I noticed if the tablet was sitting on carpet or bed and I touched it with just one finger the touchscreen would not respond. I had to hold the tablet in my hand (or plug it in) for a normal touch response. What the hell is going on with this capacitive screen!? Seems like a grounding issue. A reboot seems to have almost entirely alleviated this issue... but for how long? Most people in this thread seem to recommend ts11. Giving that a try right now. So far... it seems slightly worse than ts20.
[Nexus 7 (2013) General] jfriend33:
There's a Nexus 7 display app that shows ghost touches for me even when it works fine otherwise on Ts11.

Now on the actual "display tester" app, all is well.

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] abemore:
I don't understand how this app (Nexus 7 II Tester) works. The first pattern causes random touches all over the screen whether I'm touching it or not. Like it's possessed. How is this supposed to help anything?
[Nexus 7 (2013) General] abemore:
THIS ULTIMATELY APPEARS TO BE A GROUNDING ISSUE

Using a multitouch testing app (like this one), lay your tablet on different materials and try to reproduce your touchscreen issues by touching your tablet with just your fingertip(s). I've tried all of the following...

Good Grounds (Laying your tablet on these materials seem to solve the issue):

my hand

my laptop (even though it's unplugged and plastic)

a metal frying pan

a thin metal box

a big flimsy disposable aluminum serving tray

Bad Grounds (Laying your tablet on these materials either does nothing to fix, or causes the issue):

Wood

carpet

bedding

dvd case

plastic bin

granite counter

a book

leather couch

a stack of anti-static bags (used to ship computer components)

aluminum foil

Try this:

With the tablet placed on a couch, bed, or pillow, visualize your touchscreen issue using a multitouch test app, and while the touchscreen is spazzing (or not registering a touch), with your fingers held in place on the screen, simply slide your other hand under the tablet and notice how the screen suddenly works correctly.

So the question is:

Is there some way we can permanently ground this damn screen? Can we tape one of the good ground materials to the back of the tablet? Or inside the cover?
[Nexus 7 (2013) General] jfriend33:
I don't understand either. I'll email the dev and post the response.

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] basily:
This is a really weird issue. Probably made even weirder by the fact that it's likely several different issues, as evidenced by the fact that different solutions work or don't work for different people.

I first tried out the "loose connector" solution posted here:

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

At first I thought it worked, but alas, no. I re-opened my tablet several times trying to re-seat the connectors "better" each time. I tried grounding my device. I tried pushing on different points on the back of the case and squeezing the case more tightly shut. All produced random results. My touchscreen is messing up so badly to make the tablet completely unusable.

I finally decided this issue, at least for me, cannot possibly have to do with the hardware. The reason is that I have multirom installed and I can boot stock, CM, and Ubuntu Touch. With stock it's unusable. With CM, there are slight issues, but still not good. With Ubuntu it works flawlessly.

So, I tried TS10, and it worked better, but I found that I had to push pretty hard for touch to work - still it worked. I'm trying TS20 now to see if it's any better.

Thanks for providing this!

edit: while there were definite improvements with each of TS10, 20 and 30, it's still not perfect. My guess is that there must be multiple issues at play here. This really sucks google/asus...

edit: ok, went back to TS10, after trying all 3, and after a couple of reboots, and waiting for it to fully boot up, it seems good now. Still makes me feel like I can't rely on this thing...
[Nexus 7 (2013) General] jfriend33:
Did you try the experimentals?

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] basily:
I'm back to thinking that my problem is hardware related as it's just insanely sporadic.
[Nexus 7 (2013) General] jfriend33:
Try ts11

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] basily:
Tried it, and now ts12,,, working so far, but I expect it will start getting weird again.

This is why I don't think it has to do with software for me, because the problem appeared out of nowhere, no new updates no nothing. I'm back to a clean factory image now, for testing. Previous tsXX's that I tried all seemed to work at first, then I would get weirdness again. Sometimes my touchscreen won't respond at all, sometimes it will get erratic touches, and sometimes it will work fine. I just don't see how this (in my case anyway) can be anything except a flaky connector, part or noise interference due to poor grounding.
[Nexus 7 (2013) General] ddurandd:
I just got my unit back from ASUS. The serial number is the same. It looks like they replaced the LCD...

New Part No: 90NK0081-R20020

New Part No Desc: ME571K TFT LCD+FRONT+GPS MODULE (NEW)

They did not appear to do a factory reset - unless they made a backup first and restored.

I've only had it about an hour so I will report back to let everyone know if the problem is fixed.
[Nexus 7 (2013) General] basily:
Well, in the end I gave in and contacted Asus via online chat. I described my problem and they asked some details including what I had done to troubleshoot. I told them everything *except* for my warranty voiding actions.

They gave me an RMA.

Luckily I know of an authorised repair facility nearby, and they accepted my device as a walk in. The tech noted a cracked bit on the top left corner (I only ever used my mail to open it!!!) so I admitted to opening it to reseat the connectors (but NOT to removing and replacing the battery and micro-usb board). He asked me to make a note to that effect, and noted that the crack wouldn't be repaired). I told him I was in a rush as I'm leaving the country tomorrow, and he said he'd see what he could do. He consulted with Asus about me being able to pick it up after repair (rather than them mailing it back to me), and the answer came back positive.

So, I get a call about 2 hours later (I'm not kidding!) - tablet is repaired, please come and get it. I did. It's fine now. No charge, under warranty. The tech told me that he replaced the lower circuit board (the one with the micro usb port on it), and that's a common failure on these tablets.

Overall, I could only be happier if I hadn't tried to fu¢q around with the tablet previously and cracked a tiny piece off the corner. It really is minor though, and I'll probably fill it in with something at some point.

So.... YAY ASUS!!!!!!!!!!!
[Nexus 7 (2013) General] TheMaskedHamburger:
[MENTION=4769686]abemore[/MENTION]

I just wanted to mention that the grounding issue CAN remarkably be solved by one of the touchscreen variations, at least that's what me and a handful of others have noticed. I had the grounding issue bad, but upon loading "TS-11" it has been permanently fixed (its been a few months since then). I guess the touchscreen drivers must also affect the voltages... So even though it appears to be a hardware grounding issue, it is fixable for some (like my brother and myself) with this touchscreen software. TS-11 did the trick for the both of us.
[Nexus 7 (2013) General] nitrous²:
Looks like CAF is not supported. Any words on that?
[Nexus 7 (2013) General] kingston73:
??? what do you mean by this??? The ts files work independent of your rom, if that's what you're asking.

Ts11 has now been working flawlessly for me for several wells.
[Nexus 7 (2013) General] nitrous²:
I may have missed something in the thread. Since i flashed ts20, I can't boot non-CAF ROM's at all even after using boot-ts-unlock.img. Isn't this command supposed to bring back the stock touchscreen kernel?
[Nexus 7 (2013) General] mdamaged:
You flashed ts20? As in, "fastboot flash boot-ts20-lock.img"?
[Nexus 7 (2013) General] nitrous²:
Of course not. Sorry. I mean fastboot boot boot-ts20-lock.img :laugh:

Flashed Factory Image several times after CyanogenMod wouldn't boot up properly or with graphical artifacts.
[Nexus 7 (2013) General] mdamaged:
Ok, just making sure.

You said, "I can't boot non-CAF ROM's at all" yet your initial complaint is that it does not support CAF ROMs, perhaps you meant to say, "I can't boot CAF ROM's at all"?

Either way, the touchscreen firmware is separate from the kernel or ROM, so your issue is not common, you should know that when you boot to one of these on something at or newer than 4.4, the first time it will get stuck on bouncing balls, just wait 120s and reboot and it should be fine, if that isn't your issue, if it were I, I might start over with a complete wipe, because something isn't right...or just forget about these fixes and keep what you have.
[Nexus 7 (2013) General] nitrous²:
Damnit! Yes, that's what I was trying to say. Again, sorry. So my complaint was that I couldn't boot CAF-kernel based ROM's.

Thank you for your help =) You can count me to the rare species of those who actually study OP's but aren't able to compile a logical sentence :laugh:

But I get the point. I should be more precise. The problem was that after booting Ts20, CyanogenMod would show graphical artifacts as seen when you accidetally flash an AOSP kernel onto a CAF ROM. This let me believe that the touchscreen firmware actually interferes with the ROMs kernel. Right now, after flashing the factory image for the ~6th time and booting Ts11, I finally could boot CyanogenMod.

Thank you again for your help.
[Nexus 7 (2013) General] mdamaged:
No problem.

Yes, the kernel that boots with the ts files are 4.3, and as you guessed are non-CAF, but once the ts firmware is updated and it reboots (perhaps more than once) it should use your kernel (in your case your CAF kernel) and should be fine as you see.
[Nexus 7 (2013) General] outlawmodzz:
flashify??

Can I flash with flashify?
[Nexus 7 (2013) General] mdamaged:
No, these are not to be flashed.
[Nexus 7 (2013) General] AndyYan:
Just one shot at TS11 seemed to have solved the problem on my N7, awesomesauce :D

FYI, my combination is N7 2013 + CM11 Nightly + ElementalX.
[Nexus 7 (2013) General] digitalbot:
Removed.
[Nexus 7 (2013) General] nacho:
Still not working for me...

Whenever I try to boot any of these images the bootloader just shows "booting downloaded image" but then nothing happens. It is not responsive and never reboots, I've tried TS10, 11, 20, and 30 with all the same results.

I have bootloader v4.2 on my Wifi Nexus 7, I've tried using krt16s stock rom but nothing seems to effect it.

My touchscreen is completely not working.

Any advice?

Thank you.
[Nexus 7 (2013) General] rajeshachanta:
Thanks a ton mate!!

Thank you very much dear pal! I've spent many disappointing days after buying my NX7 2013 in a good deal. Later thought I've unnecessarily bought it in the cheap deal as I thought I was given a damaged product for less price. No guarantee or warranty also! But after searching about the touch screen issue I luckily found this thread!! I'm a geek myself and as I'm already having Nexus 4 and know rooting and tweaking it I've rooted my NX7 too the first day I bought it. Then after few searches and finding this thread I resolved the touch screen issue pretty easily and quickly. Thank you very very much mate! I'm very happy now!

boot-ts10-lock.img worked for me!!:laugh::good::cowboy::D

*ts10* isn't working after few boots. *ts20* also not working satisfactorily. Now trying *ts30*. Hopefully wish it works!!

**********

Unfortunately *ts30* also isn't working!! There are few places on right side edge where the screen isn't showing the lines when I draw a line. But, initially it was worse than this. Now I feel it's a bit fine.:fingers-crossed::mad:
[Nexus 7 (2013) General] jfriend33:
Is there any way to donate to the person who created this?

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] graphdarnell:
I have a serious touchscreen problem that differs from all reported through 134 pages of this thread, so bear with me. I replaced a digitizer on this thing. More than half of the right screen is unresponsive. Barring the possibility of a defective dig - which I doubt, as I tried flashing TS14, and got the whole screen working for a short 3 minutes before ghost touches appeared all over the screen - I'd like to know if there's a way to extract the touch firmware and flash it again independently.

The reason for this is we (XDA members) have had unresponsiveness troubles with replacement digs on another Asus model, and re-flashing the touch firmware independently seemed to solve it without fail. The problem then was to identify the correct firmware that would work with ALL versions of the digs. But that, I can do on my own so long as I know where the firmware(s) in question are hidden.

Thanks in advance for any help.
[Nexus 7 (2013) General] osm0sis:
You could try dumping the ramdisks of the .imgs using my Android Image Kitchen and seeing what scripts or commands are in the .rc files or elsewhere. They are just boot.imgs after all. :good:

Let us know what you find! :)
[Nexus 7 (2013) General] player911:
Very sad that this is still an issue.

My original Nexus 7 was dropped in the toilet and then put on a charger for 5 days. The replacement is just as picky about touches. I haven't flashed any of these touchscreen patches on the new one yet. I don't plan on it either. I'm so used to it now that I just accept it for what it is, keeping hopeful that an update will one day fix this dreadful issue and return it back to it's glorious self.
[Nexus 7 (2013) General] Arturo777:
Thanks a lot for this. My problem was really nasty and i was mad at the seller... but i tried this and i'm very grateful. this is the perfect solution! ts10 worked for me on 4.4.2. Thank you.
[Nexus 7 (2013) General] spartacus279:
I have tried almost all the ts files and none of them seem to be working , I still have tons of ghost touches and on some when I use a multi touch app my screen goes all over the place and is unusable. For a while I was using ts11 and it was working decently but latley I have been having more and more issues. Should I try to flash another experimental file or wait for 4.4.3 which I heard might resolve everyones issues. If I helps , my device was manufactured in july 2013 and I bought it at launch so that could possibly be why im having all these problems?
[Nexus 7 (2013) General] El Nino1977:
I was suffering from the non touch issue when my tablet was flat on the table or sofa etc. I just came customed to it until i stumbled across this beauty of a thread. I was skeptical to say the least but damn, the first attempt with ts10 worked a f##king treat!!!

Very happy now, thank OP :)
[Nexus 7 (2013) General] amroman2006:
what about factory reset ?

Hello

I just have question , if I made factory reset from toolkit , will I lose that fix ? Shall I apply the fix every time I make factory reset from toolkit ?

Bgrds,

Amr
[Nexus 7 (2013) General] mdamaged:
No you will not lose the fix. No need to reapply.
[Nexus 7 (2013) General] godutch:
[MENTION=1299673]sfhub[/MENTION]?

Btw what's the difference between the different ts packages? Which would be the best to try against ghost touches? I tried 11, 10, 20 and 30, 11 was the worst 30 was like stock 10 and 20 seemed a bit better than stock...

I used the following app to test:

https://play.google.com/store/apps/details?id=com.gombosdev.nexus7tester
[Nexus 7 (2013) General] godutch:
Not registering touches was easy to fix by opening the back and reattaching the display connector, these ghost touches I experience are more difficult to fix :(

see this thread for fixing the connector: http://xdaforums.com/showthread.php?t=2535835
[Nexus 7 (2013) General] jfriend33:
That app is crazy.

I have no issues whatsoever after applying ts11 but if I run that app it goes crazy.

I'm gonna try running that app on other devices and see what happens.

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
[Nexus 7 (2013) General] graphdarnell:
Don't get what you said, my man. What holes on the ribbons? Are you talking about a tilapia? It's a 2012 model. Why are we talking about it here? If possible, post some pictures so at least we know about this GND thing. I took the back cover off my unit, and in my case at least,

1. If I put a finger on the connectors, it would sometimes make the ghost touches go away;

2. Same thing happened when I slightly bent the mid-frame;

3. Dead bands switched from one area to another when I moved the components within their locations; or tightened some screws more than others;

Which tells me that either the daughter card acted up, or the mid-frame with plastic contour exerted undue pressure on the touchscreen: Defective design or shoddy material. Anyone knows differently?

Dead bands would switch from one area to another when you move
[Nexus 7 (2013) General] godutch:
Does anyone know what happened with [MENTION=1299673]sfhub[/MENTION], he was very active but hasn't posted in half a year...
[Nexus 7 (2013) General] graphdarnell:
Most probable: got married, a situation where one person commits a victimless crime by claiming ownership to another person, time and money - voluntary servitude, in short.:laugh::laugh::laugh:
[Nexus 7 (2013) General] godutch:
I hope he's okay, usually when people are getting married they announce, he just disappeared...

---------- Post added at 10:20 PM ---------- Previous post was at 09:24 PM ----------

Ts25 seems very good against ghost touch, best so far

Edit: ts25 is a bit unresponsive at times though....
[Nexus 7 (2013) General] graphdarnell:
Of course you know I'm joking, right? BTW, I don't remember its being addressed in the thread, but when you flash one image after another to test, do you need to flash the unlock image after each first to erase the former image completely?
[Nexus 7 (2013) General] karandevilocs:
i tried almost EVERY one of them ! casual / exp1 / and half of exp2 files ! and none worked properly i had a perfect touch screen before installing the TOUCH CONTROL after that and even by reverting back to stock and formatting everything it was still there then i headed to this forum and at first try the TS10 Worked perfectly but after 2-3 hours it started to show it's laggy side ! and after that none worked nothing like ts 10 i'm on ts20 right now it's less laggy than the rest but i'm living with it !

so what should i do now ? how can this be happend i had everything right at first weeks so that couldn't be a touch panel thingy should i test anything more experimental [cause im willing to take the risk ] ! and do any of you guys have any idea that 4.4.3 may fix this thing once and for all ?

THANKS!
[Nexus 7 (2013) General] yukkio:
4.4.3 doesn't fix anything :S I flashed it to test if the touchscreen was fixed... wtf google!
[Nexus 7 (2013) General] godutch:
What is your problem, unresponsiveness or ghost touches?
[Nexus 7 (2013) General] yukkio:
Without the the boot ts fix, unresponsiveness at the top of the screen. With the fix, no unresponsiveness but i have ghost touches...
[Nexus 7 (2013) General] godutch:
Did you try reseating the connector? It's not very hard, though be careful around the volume and power button and usb port because the back cover can break there easily
[Nexus 7 (2013) General] niscrulez:
I've given up. I would recommend not buying a Nexus 7

Asus is probably the only one who did not comment this issue yet.
[Nexus 7 (2013) General] osm0sis:
This is a really good question. Does anyone know definitively?
[Nexus 7 (2013) General] mdamaged:
I figure the OPs directions make it pretty clear. I'm sure he would have stated to use unlock as part of the steps if required to try a new TS. He also explicitly states the unlock is only if you want to go back to the way it was, or receive an update from the manufacturer (which would deliver them in a different way than the ts files do).

i.e. I strongly suspect the unlock is part of the ts files boot process...unlock, apply fixes, relock. Whilst the manufacturers' would not have the unlock process.
[Nexus 7 (2013) General] digitalbot:
Before i took the 4.4.3 update i ran ts-unlock, then formatted to take update but screen still exactly same as any other update so i flashed back my ts-of choice.
[Nexus 7 (2013) General] vinzer.x:
Logged-in to say thanks a bunch for this. You saved me from having to wait weeks for a warranty repair (that may open up other issues in it's place - it happens).

Details from my own unit, if it helps:

- build is KOT49H

- I was having problems with drag gestures, actually, and not multi-touch (which worked/still works okay for me). My tablet thinks I've already released my finger midway through the drag motion even when I haven't.

- ts10 fixed the issue for me
[Nexus 7 (2013) General] danaff37:
My experience pretty much mirrors yours. It feels like a new tablet again.
[Nexus 7 (2013) General] 318sugarhill:
Has anyone unlocked ts and tried the new 4.4.3 update to see if it fixes anything? I applied this fix long ago and I forget which one I applied 10, 20, and 30 had varying degress of success, but I think it was 16 or 18. I was wondering how the update was before I play around. Was considering unlocking ts and then trying the 4.4.3 update. Pretty sure it will not change anything and cost me time. But my tablet is unusable without this fix. It's pretty embarrasing and makes me wish I bought a galaxy Note 8 instead.....locked bootloader and all.
[Nexus 7 (2013) General] frelnik:
I unlocked and updated and didn't notice a significant change. Went back to ts-11.