yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] HearMeWhisper:
I'm on 4.4 stock with the glitch kernel and I can't seem to get it to boot at all. Keeps hanging on the boot animation. I've even tried flashing the kernel after the ts
[Nexus 7 (2013) General] sfhub:
The boot-ts* files are 4.3 kernels. They are expected to hang at the BouncingBalls animation. By that time the job is already done and the touchscreen software is installed. Simply wait 120 seconds for the boot to stabilize, then press/hold the Power button for 10-15 seconds until the unit reboots.

If you are saying it won't boot after you've rebooted, can you try the stock 4.4 kernel?
[Nexus 7 (2013) General] HearMeWhisper:
Yeah, even after multiple reboots, I'll try the stock right now though. I even waited about 5 minutes between everything too. I'll report back in a few minutes when I try it

Sent from my Nexus 7
[Nexus 7 (2013) General] sfhub:
I guess the Dolphin 4.4 zoom problem affected more than me:

https://play.google.com/store/apps/details?id=mobi.mgeek.TunnyBrowser

What's New

...

★ Fix the pinch zoom compatibility issue on Android 4.4 kitkat
[Nexus 7 (2013) General] anubisb:
[MENTION=1299673]sfhub[/MENTION], just wondering if it'll be possible to create a calibration application which could feed/configure the TS kernel module? ...this could resolve the issues device-by-device... :cowboy:
[Nexus 7 (2013) General] sfhub:
It would probably be possible to give calibration info to the ROM's touchscreen input modules.

However the fixes in this thread are not in the kernel. They are in the touchscreen DSP.

IMO for some of these problems, the data is already bad before it reaches the kernel. For others calibration within the kernel or runtime might help.

Google has the data on what is going wrong so I'm sure they would have considered more advanced calibration options if they felt it would help.

Either it is more work than they are willing to put in right now or they don't feel it would help.
[Nexus 7 (2013) General] anubisb:
...fine then a calibration for the DSP? ...instead of trying different variances... :D

I don't think Google is going to address these issues; I'm pretty sure than they are working on the next device cycle so no point of fixing the current production!
[Nexus 7 (2013) General] sfhub:
You can try playing with

/system/usr/idc/elan-touchscreen.idc

I haven't found it to affect the symptoms in the past, but I haven't touched it since JSS15Q.

The only thing they changed in KRT16O (for this file) was to add:

touch.coverage.calibration = box
[Nexus 7 (2013) General] FernandoMiguel:
i own a 2013 LTE version

the 1st one i had, showed no issues. but it cracked the cover within 2 weeks, and i had it traded.

the new one does show many ghost touches, especially on the keyboard and the side lines.

kitkat did improve it a bit, but it's still showing.

i've been reading over this thread but 90+ pages is getting confusing with all the experimental builds.

1st question: is this a patch for LTE version too?

2nd: which is the best version for KK?

3rd: how can i know which kind of sensor i own?

thank in advance for your work
[Nexus 7 (2013) General] lomonic:
Guess it happens inconsistently then. Is it fixed on yours now?
[Nexus 7 (2013) General] sfhub:
Yes, the zoom is fixed in 10.1.2, but dolphin starts lagging after I hit certain sites (or maybe after I've visited too many sites). I think that is related to 10.1.2 rather than 4.4 because it wasn't happening with 10.0.4 on 4.4 (just didn't zoom right)
[Nexus 7 (2013) General] sfhub:
The touchscreen software in this thread will work on LTE also.

There is no best version for KK. It is dependent on your touchscreen hardware which performs best.

All the touchscreen IDs come up the same so it is difficult to algortihmically decide which touchscreen software to apply.

So basically there are 3 to try, ts10, ts20, ts30.

You should at least notice some change in behavior (make sure to reboot a few times after each change so the internal calibration can settle in)

If one of the 3 main ones works well then just be happy and enjoy your tablet.

If none are good enough, then pick the best one and try the experimental ones near in number to the best one.

Though these are low-risk operations, it is always best to back up important data and copy off your tablet.
[Nexus 7 (2013) General] FernandoMiguel:
are the TS based on 4.3 kernel or 4.4?

any impact on using kernel 4.3 based images on KK?
[Nexus 7 (2013) General] sfhub:
They are based on 4.3 kernel, however the 4.3 kernel is only used as a delivery mechanism, you aren't running your setup on this kernel.

stock 4.3 kernel will not boot a stock 4.4 ROM. It will hang on the bouncing balls animation (replacement for X animation). However by that point the touchscreen software is already installed. Just wait 120 seconds for the boot to stabilize and press/hold the Power button 10-15 seconds until the tablet reboots. You'll be back to using the original 4.4 kernel but with the chosen touchscreen software installed.

This information is also in the instructions of the first post.

If a lot of people are still seeing the touchscreen issues on 4.4, once google checks in the source for the kernel, I'll look at recompiling these using a 4.4 kernel. It won't result in any difference in touchscreen software, it'll just boot all the way into the ROM instead of hanging on the bouncing balls animation.
[Nexus 7 (2013) General] astuermer:
For me with KitKat/ Android 4.4 all touchscreen bugs are gone.
[Nexus 7 (2013) General] JMS74:
What were your issues?
[Nexus 7 (2013) General] astuermer:
Ghost touches sometimes.

When not grounded the N7 sometimes didn't response.

Those two are gone now with Android 4.4 for me.
[Nexus 7 (2013) General] HearMeWhisper:
Just tried with the stock kernel, no bones. I'm not sure why. I've got a few more things I want to try once I get home.
[Nexus 7 (2013) General] adrianis:
Yes, if not a problem, please recompile. Thank you!
[Nexus 7 (2013) General] sfhub:
If possible I would try factory reset from recovery.
[Nexus 7 (2013) General] sfhub:
So after 2 months of no issues, I had a second unit start wigging out on ts10.

By wigging out I mean a .5" point would form on the screen where just a single finger touch would cause totally random ghosting along the Y axis (normally people experience this with 2 fingers overlapping)

This unit has never been flashed to anything else (other than installing ts10). It is a baseline unit still running 3.05 bootloader and JWR66N. Reboot didn't help. I then flashed ts09, used it for about 30min, confirming it worked ok, then flashed ts10 back and everything is normal again.

The first unit referenced above was my test unit and it was working fine for 2 months also but after KRT16O came out I flashed back and forth between JSS15R and KRT16O over 20 times to test various scenarios and then it started showing issues. My theory at the time was the flashes were related to the problem popping up, but now that my baseline unit showed the same symptoms, the flashes as a cause are out of the picture.

Anyway, I went back and reflashed ts10 on the test unit that had been running ts09 for a day now, and ts10 works fine again.

My new theory is with the weather getting colder it is easier to build up static charge in these screens, just like you are more often zapped when you touch a doorknob in the cold/dry winter weather. This charge should theoretically have been dissipated when I connected the tablet to the PC via USB, but I didn't think of this theory at that time. I can't tell right now whether flashing ts09 and back to ts10 was the fix or just connecting the usb to ground would have fixed it on its own. Will try to figure out which one if it happens again.
[Nexus 7 (2013) General] airmaxx23:
Does anyone have any insight as to why this seems to help for a few days and then the touch issues come back again?
[Nexus 7 (2013) General] mertzi:
Is it possible that low battery can cause touch misbehaviour? It's probably just in my imagination but i think i have had more issues when the battery is getting low, from 15% and below.

I went back to using ts10 with kit kat, i don't know if the few issues i get is caused by Swype keyboard not being compatible with kit kat or something else. I'm using Google keyboard now and few issues but i think it is inferior for gesture typing.
[Nexus 7 (2013) General] sfhub:
Yes, it is possible. When batteries get lower the power can fluctuate. The voltage regulators are supposed to keep the voltage constant, but there is always some range.
[Nexus 7 (2013) General] :
After installing KK my touch problems got better albeit not disappearing at all. Now with ts03 everything seems to be OK, both 3 touches in a line and missed touches are gone, will report later after some stress-tests :thumbup::thumbup:
[Nexus 7 (2013) General] bobafuzz:
Got new KitKat OTA just now, KRT16S. Multitouches been working well with ts10. Figure I'll try to see if the new OTA fixes anything touchscreen related. Ran unlock, YAMTT looks promising, no axis problem, no ghost touches, fired up google maps, can't turn or zoom, what a POS, back to ts10 for me :(.
[Nexus 7 (2013) General] sfhub:
BTW both the kernel and touchscreen software in KRT16S are the same as KRT16O.

KRT16O did have newer touchscreen software than JSS15R.
[Nexus 7 (2013) General] hyperspacey:
After complaining about ts10 wigging out on a previously-fine N7 when I moved over to KitKat-O, I decided to unlock the touchscreen before flashing the KitKat-S update. Seems to be completely fine now I'm on KitKat-S.
[Nexus 7 (2013) General] canhazpixels:
Interesting. I had a bone-stock rooted KitKat-O with a perfectly-functioning touchscreen, and updating it to S made the touchscreen nigh unusable. I guess I'll be trying out these files :(
[Nexus 7 (2013) General] hyperspacey:
An update on this, it seems that while it's no longer dragging touch events around with other events, it is dropping parts of touch events. So back to fastboot I go.

I said this last year, but I really hope Google find someone less inept to make the next Nexus 7.
[Nexus 7 (2013) General] WillPoz:
TS10 worked for me running KRT16S. I have been holding off on doing this to see if KitKat would fix the problem. It was not a good decision on my part. Thanks for fixing something that Google and ASUS couldn't. :thumbup:
[Nexus 7 (2013) General] mi7chy:
Google Maps rotate issue I'm pretty sure is an Android 4.3 and 4.4 issue because it's happening on both N7 2013 (Android 4.4 and 4.3) and Note 3 (Android 4.3) but not Note 2 (Android 4.1.2) with same Google Maps version.

I unlocked before flashing 4.4 factory image and the touches are improved like ts10 but slightly better in that I can hold press open links in Chrome easier.
[Nexus 7 (2013) General] lomonic:
I'm curious to know if those users having problems rotating in Google Maps, also have the same problems in Google Earth. Can anyone please try it out? On my system, Google Earth works perfectly - same gestures as in google maps but google maps pales in comparison with smoothness.
[Nexus 7 (2013) General] bandit_knight:
I can confirm your observation. In Google Earth rotation gesture works almost perfectly. In Google Maps I hardly can rotate the map. Pinch to zoom gesture works pretty well. Since Kitkat I've been on stock OS without the sfhub's fix.
[Nexus 7 (2013) General] mi7chy:
I was able to replicate it at a Verizon store Note 3 demo tonight so I'm pretty sure yours is probably affected too. Use two fingers to slowly rotate back and forth along the x-axis until it stops rotating or goes wonky (you should see something within 10 secs or so). Doesn't matter if it's plugged in and/or holding it with the other hand.

I don't have Google Earth on Note 3 but just tried it on Nexus 7 2013 and it's kind of wonky too.

If you're able to replicate it remember to report it to Google so they can fix the oversight.
[Nexus 7 (2013) General] rodrigodiazdevivar:
That is exactly what I was experiencing with ts10 (using 4.3 with JSS15R). At first, after installing ts10 everything seemed to be ok but I found that some of those .5" points where randomly appearing at different locations of the screen (one each time). After rebooting the point disappeared, but after several minutes of use, it appeared again at a different location.

After reading your post, I decided to try your advice and moved to ts09. Now these points seem to be gone. (although some missing touchs still remain when pressing the home button at the bottom). I will continue with ts09 and see if these annoying points come back. Let me ask you: if ts09 seemed to be also ok for you, why did you decide to move back to ts10 again?
[Nexus 7 (2013) General] Wrngway:
Yes, I've seen the same issue in Google Maps. The rotation gesture doesn't always work and when it does it hesitates and isn't precise. I've seen this on three Nexus 7 models that I've had. One of those had other touch issues. Plugging the device in helps. Rotation in Google Earth is much better on all of them.

My Galaxy S3 doesn't have any issues with Google Maps. I can rotate and zoom without lifting my fingers.

I'm assuming this problem has something to do with how Google Maps interfaces with the touchscreen controller? It seems to be a problem specific to Nexus 7.
[Nexus 7 (2013) General] astuermer:
I can confirm that too!

With O I had a perfect touch-experience.

Yesterday I updated to S and with 5-fingers on the screen it flickers between 4 and 5.

Also on two areas of the screen I have to press very strong so that the screen recognizes my input.

Is there any option to change back to the O-touchscreen firmware? (I've read it's the same, but obviously something's different)
[Nexus 7 (2013) General] Anderson2:
shub : I would love to hear your thoughts on

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

Because you know more about this problem than most of us.
[Nexus 7 (2013) General] sfhub:
I don't dispute what you are seeing, but it can't be because of the touchscreen DSP software. It has to be somewhere else in the system. I know you don't really care where and just want it fixed, but I point this out so you can focus your efforts on areas that did change.

The touchscreen software is embedded in the kernel. The kernel did not change between KRT16S and KRT16O. You can prove this by looking at the ota which doesn't include the kernel because nothing changed. Further, if you flash the factory image, the kernel version # and build date will be exactly the same as KRT16O.

So where does that leave you? Something on the android system side may have changed. Flash KRT16O factory image using the nowipe option to undo that.

Some settings in user data might have gotten messed up, factory reset to undo that.

Some as yet unknown hardware issue popped up. If this is what happened it is unclear how to undo.

You could try flashing back and forth between different factory images and sprinkling in otas and try to see if what originally caused your issue undoes itself. It feels like flailing, but if nothing else works...

When you've exhausted the possibilities above, you might want to try different ts files. You might want to do that right away, but I suggested in the order above so you can isolate what may have caused what you are seeing in a more systematic sequence.
[Nexus 7 (2013) General] sfhub:
I switched back to ts10 because

1) I wanted to see if it went back to the working state that had been in place for 2 months

2) because ts09 had a small section of screen that would only respond to light taps. Heavier taps would be missed. It wasn't really bad and I could live with it, but if I could get ts10 working again, I figured I'd try
[Nexus 7 (2013) General] sosagf:
after not even 7 days the top inch of my screen stopped responding to touch. was fine in the evening turnt on in the morning and couldnt expand the tool bar etc

no matter what way you rotatated the screen whatever was on that 1 inch strip at the top just didnt work.

downloaded a touch app an it confirmed the whole top was dead.

sent back to amazon today, if i get another one how likely is the same problem or was I just very unlucky?
[Nexus 7 (2013) General] sfhub:
How likely to get some amount of touchscreen issues? Don't know, number is in dispute, more likely than normal manufacturing issues but whether that is 2%, 5%, 10%, etc. only Google knows.

How likely is it for an entire area of the screen to be dead, unlikely.
[Nexus 7 (2013) General] thecapsaicinkid:
Got the 4.4 OTA tonight. I think my touchscreen is actually worse. Large dead spots all over. I'm sending this thing back. What with all the bluetooth problems and this, the 2013 N7 is a lemon imo.
[Nexus 7 (2013) General] sosagf:
well i think im going to repurchase from john lewis, although its 30 quid more then amazon it has a 2 year john lewis guarantee as standard so any more problems i can just take it back to the store
[Nexus 7 (2013) General] wintermute000:
Thanks for the effort mate but no good for me.

My touchscreen was acceptable through 4.3, but 4.4 has introduced noticeable jitter/ghost touches.

TS10, 20, 30, 02, 03 all failed to improve the situation (yeah did multiple reboots). Can't be bothered going through the rest of them, will wait to see what comes up next official update. Stupid google.

My only saving grace is that it was fine so theoretically should be able to get back to fine!!!!
[Nexus 7 (2013) General] danvee:
16S (4.4) seems to, for now, have made things a bit better. Not seeing additional dead areas, and touch is more consistent, and feels a bit "damped"

We'll see what happens over time.
[Nexus 7 (2013) General] doubleho:
mine got worse on 16s,16o was better to me

16s cannot.recognize some slide near the bottom on my device

it is so sad tbat i m complaining here and.google did nth to improve
[Nexus 7 (2013) General] desairs:
So I just got my Nexus 7 2013 today and it's pretty awesome other than the touchscreen. I am thinking about doing this but I have 4.4. That should matter right? Also, I see that some people mentioned that they have other TS versions than the 4 on the first post. Am I missing something here? Is this really a trial and error type deal or can you attribute your touchscreen type to a certain img?

I know these are total noob question.
[Nexus 7 (2013) General] sfhub:
10, 20, 30 are in the first attachment, the rest are in the exp* attachments to the first post.

Screens are all the same ID but have variances so it is just trial and error. Most will probably do best with ts10 but some do better with the others.

Some screens won't work well with any.
[Nexus 7 (2013) General] desairs:
Dude you are awesome! It's not everyday that you have someone that's so responsive. Thanks!
[Nexus 7 (2013) General] bobafuzz:
I'm not sure if it's 4.4/4.3 issues or not all I know is ts10 fixed it. On stock it won't even rotate. Also it works great on my nexus 4 and 5. I'll just chalk it up to crappy asus touch controller.
[Nexus 7 (2013) General] lomonic:
Sfhub did u get a chance to look at the other thread talking Abt the fix by reinforcing the digitiser cable at the back of the device. Love to get your thoughts Abt it.

I might give it a try when the video is out

---------- Post added at 10:37 AM ---------- Previous post was at 09:54 AM ----------

You have the exact identical symptoms as mine. Rotation gesture works a little iffy,but pinch zoom in out is perfect. In Google earth all gestures are smooth and perfect moving from pinching to rotating and doing both simultaneously as a rotating zoom in out. This is what bugs me. Is it software or hardware yet again. Why does it behave differently in 2 different app with similar gestures. Is it because there's more processing in Google maps? Or does Google earth has different code dpfor gestures which is more tolerant somehow?

I have been on KitKat touchscreen so far and other than some rare typing problems I'm very satisfied overall. Both krt releases works the same for me.

Thx for testing it and sharing your feedback. Love to gather more and subsequently send something thru to Google's support

---------- Post added at 10:39 AM ---------- Previous post was at 10:37 AM ----------

So based on what you've just shared here it seems to be app related. Prob the performance of Google maps creates lag and the touch sensing gets messed up. So the nexus 7 is not alone with regards to problems in maps.

Can anyone else validate this?
[Nexus 7 (2013) General] sfhub:
It is certainly possible some touchscreen issues are caused by the connection cable. I've seen this type of problem with other devices.

However I don't know how many are being caused by the connection issue. It would be hard to believe it is the sole cause of the touchscreen issues as people who are getting their tablet back from RMA with the screen replaced (where they presumably would need to disconnect and connect the touchscreen) are still seeing touchscreen issues and also it is very hard to compensate for the type of issues you get with loose connections using software.

So I would say worth a try, especially if you are out of options. Otherwise wait for more feedback.

Personally I don't have problems with zooms or rotations in google maps for 4.4 or 4.3 using ts10.

In the past, it was easy to spot whether rotation problems in google maps were due to touchscreen or not by turning on show taps and show pointer location in developer options. If the rotation problem was caused by touchscreen, the show pointer location would show a broken line.
[Nexus 7 (2013) General] jjdoctor:
At first when I updated to 4.4 , the problem was OK for 4 to 5 days, now I got the same grounding issue and I don't think it's related to some software I installed.. It just gradually got worse and now lots of dead areas in screens

I will give a try to ts10 again later which had solved my touch issues on 4.3... Will report back once its done

And this thread should be in development section, what's it doing in General?
[Nexus 7 (2013) General] kinetic758:
After updating to 4.4, the grounding issue seems A LOT worse than 4.3 (I'm running completely stock). There are occasions where it works flawlessly which always gives me hope to hang on to this thing, but once it starts acting up, I want to pack it up and return it. I have one day left to decide to keep it. What do you guys think? The dead spot (when lying on a table) runs vertically at the center of the screen (in portrait) and is about the width of an icon.
[Nexus 7 (2013) General] sfhub:
Are you saying you are on the stock touchscreen software or are you saying you tried some set of these alternate touchscreen software in this thread?

If the former, you don't really have much to lose to try some alternate touchscreen software.

If the latter, you probably just want to return and be done with it or exchange the unit.
[Nexus 7 (2013) General] kinetic758:
Sorry, I was completely on stock and didn't try the fixes in this thread. I'm going back and forth on trying to do this fix, but I don't have much experience rooting and only have until tomorrow to return it.
[Nexus 7 (2013) General] sfhub:
You don't need to root.

You only need to unlock the bootloader.

Up to you, if you already have the USB drivers installed it probably takes less than 5 minutes to do, add 15-20 minutes if you are starting from scratch or this is your first time.
[Nexus 7 (2013) General] OJ in Compton:
I'm having a very similar issue after months of few to no touchscreen problems, maybe it's for the same reason. I didn't have any significant issues with TS10 on 4.3 but after flashing 4.4 and the 16S update I've encountered (in separate instances) totally random ghosting on the x-axis on the first row of my keyboard and similar ghosting on the y-axis twice, all 3 times holding the device with one hand in bed. Going to test the device with the ts-unlock and ts-10 again and see if the issue pops up again.

Is there a way to dissipate charge accumulated in the tablet aside from connecting it to a PC or wall outlet via USB?