yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
Sorry I wasn't clear, I meant does slow boot happen on stock Google rom and was suggesting using the factory restore to install the stock ROM.

I am thinking something in the ROM you are using doesn't like booting with a stock kernel (which this fix uses as a delivery mechanism)

There are 3 sections involved in the boot process

1) kernel

2) ROM (/system)

3) user data (/data)

#1 goes back to what you were using after reboot

#2 is unlikely to have changed since the kernel doesn't modify the ROM and the rom is mounted read-only

So that leaves #3. My best guess is the custom rom is reacting to a stock kernel causing some change to user data that results in long boots. If the boots go back to normal after factory reset, that kind of supports that theory.
[Nexus 7 (2013) General] mertzi:
Good morning! Kit Kat roll outs have begun. Is it necessary to flash ts-unlock prior to updating? And is it possible for you sfhub (or someone else with knowledge) to determine if google has included anything to address the touch problems just by studying code/kernel?
[Nexus 7 (2013) General] sfhub:
You can run ts-unlock before or after updating, doesn't matter.

Upon first reboot after ts-unlock you'll be back to running normal touchscreen software. If you were on JSS15R and ran ts-unlock, you would be back to running the touchscreen software from JSS15R, then when you update to kit kat, you'd get the touchscreen software from that release. If you were running ts10, then upgraded to kit kat, you'd still be running ts10, but after running ts-unlock, upon first reboot, you'd be running the touchscreen software from kit kat.

I can look at the code, but they haven't checked any source (for asus-flo) in to the public repository that I could find. I've only seen binary kernels checked in so far.
[Nexus 7 (2013) General] thecapsaicinkid:
Please tell me all 4.4 N7s have perfect touch response when not grounded.

Is there a way to force OTAs without cocking stuff up and requiring a reset?
[Nexus 7 (2013) General] bobafuzz:
Mine didn't :(. Did a firmware unlock and upgraded to 4.4. Multi-touch was okay in YAMTT. Pretty much broken in google maps, I can pinch zoom, but gesture turning was non-existent. Went back to ts10 everything is better.
[Nexus 7 (2013) General] andrewNY:
So far my Nexus 7 on 4.4 seems to have a better touchscreen response. For example, I don't have to try to enter my pattern for pattern unlock 3 or 4 times anymore!
[Nexus 7 (2013) General] frelnik:
I haven't experienced any real changes post-KitKat. Still experience minor difficulty when tablet is lying on a surface with multitouch in Maps and some reduced sensitivity to single touch in top right corner of screen. However, my screen has never been that terrible to begin with.
[Nexus 7 (2013) General] JackalJackalJackal:
I installed 4.4 KitKat and I would say that everything is fine. Multi-touch is fine. Wow. :good:
[Nexus 7 (2013) General] dehsA:
Not sure whether I should be surprised to see mixed reactions regarding the multi-touch yet again.
[Nexus 7 (2013) General] sfhub:
On one unit I tested with (these are all sitting on a table, not being held):

ghost taps with aligned fingers no longer happens

used to have dead spots for both tapping and sliding

now sliding is fine, but still have dead spots for taps

sometimes slides with fingers aligned will get jittery and broken

IMO it is an improvement and for some screens it will be a fix. For other screens they will still have lingering issues.

Went back to TS10 and the dead spots are gone.

BTW I updated the instructions on the first page because 4.4 ROMs won't boot with a 4.3 kernel (which all the TS* fixes are using). Not to worry, you'll get stuck on the bouncing balls (replaces glowing X), but by that time the TS* software is already installed. Just wait 120 seconds for the boot to stabilize, then press/hold Power for 10 seconds until the tablet reboots. Everything is installed as before.
[Nexus 7 (2013) General] Skinnysloth:
Updated to 4.4 but still had huge areas of missed touches. Went back to ts-11 and all is well again.
[Nexus 7 (2013) General] benjdm:
I did a ts-unlock and updated to 4.4 and my screen went back to misbehaving. I'll have to put ts-10 back on there.

ETA: I might be mis-diagnosing. When I try the multi-touch tester I don't see any errors. Hmmm....
[Nexus 7 (2013) General] lomonic:
Have used kitkat overnight now and touch is definitely improved. I've not experienced a single stuck touch as yet, and not a single micro (5secs or so) freeze up. I had a lot of the freeze up using various TS fixes in Kik. One other experience i noticed with the new touch software in kitkat is that touch/typing is more accurate. prior to kitkat, typing always seem a lil off center but now its good.

i still get very lil amount of missed touches when on the bed and multitouch gets wonky in google maps. funny thing is that it works perfect in google earth. cant help to think its app related :S

for me, im definitely sticking with ktkat for now to test it for extended periods as we know the touch situation downgraded after extended usage.

I've also switched to ART and everything seems to work faster and smoother. i have not encountered an App that could not run in ART yet. Not sure if ART would help with touch as well.

I like to think that it's great that we have unofficial options by sfhub and the official option by Google in Kitkat. at least they are addressing the problem. Wish they could have done better with communicating.
[Nexus 7 (2013) General] jjdoctor:
For me it did... No more dead areas on screen.. Infact I am using it with swype now to reply you and it's lying on my bed, before this patch it wasn't possible to type without holding in hands
[Nexus 7 (2013) General] Elting:
That gives me hope! :)

Yesterday I flashed back to stock and now I'm waiting for OTA. Hopefully I got the same benefit as you. :good:
[Nexus 7 (2013) General] doubleho:
hi there,i been using the ts10 since i bought the nexus7 cause of the ghost touch,some slide.not recongizing.

i reset my.device to update to kitkat,after the updatebi forgot to flash the ts10 again,and god,everything is working like a charm now.I will use it.for a few days to make sure google really fixed the issue.

will report to u guys in a few days

btw,thz ts10 for saving my.device for the laat few months
[Nexus 7 (2013) General] desmondso99:
Lets hope this really fixes mine as I still have the same issue even though I sent it for repair :'(
[Nexus 7 (2013) General] doubleho:
kitkat fixed.mine,worth a try
[Nexus 7 (2013) General] digiboy1:
Just asking. There is nothing wrong if I wish to stick with ts10 either, right? TsUnlock would again wipe my data, and I don't wish to do so at least for a month.

There's nothing I'm losing if i update kitkat and stay on ts10 only, right?
[Nexus 7 (2013) General] frelnik:
Someone can correct me if I'm wrong, but I thought that unless you run the ts-unlock file, you'd still be running the modified screen firmware despite resetting the device and installing the KitKat update.
[Nexus 7 (2013) General] doubleho:
im not sure, i factory reset my device, lose everything

i disabled.the bottom "back home task" bar and used pie control app, with ts10 i still had some unrecognized touch whick made the pie didnt pop up. After updating to kitkat it can recognize all my touches and slides. This is why i thought kitkat fixed it
[Nexus 7 (2013) General] wizard7926:
This is too general of terminology to search for, but does anyone have these issues while HOLDING the N7?

I get phantom touches and zooms while holding mine. I have a Poetic Slimline case on it, I don't know if the magnets in that have anything to do with it, but I doubt it..
[Nexus 7 (2013) General] sfhub:
Just to be clear what you did, when you "reset your device", does that mean you ran ts-unlock?

If you did not, then you still have ts10.

If you did, then you are running the new touchscreen software in 4.4/KRT16O
[Nexus 7 (2013) General] sfhub:
I am using ts10 and it works fine with 4.4 KitKat.

I ts-unlocked and used the new KitKat touchscreen software for about 12hrs and the multi-touch ghosting didn't appear, but it had dead spots for tapping. Didn't notice stuck taps, so it is an improvement. I believe for some screens it will be an effective fix and for other screens there will be some lingering issues.

For me, I went back to ts10.

BTW if you leave your tablet unlocked, you shouldn't lose your data when you boot ts-unlock (or ts10, 20, 30).

It isn't the process of installing these fixes that results in the data wipe.

It is the unlock process that requires the wipe for security reasons, so if you leave it unlocked, there is no reason to lose data again just for booting ts-unlock.
[Nexus 7 (2013) General] sfhub:
For me, once in a while (probably 2 weeks between occurences) there will be a .5" spot on the screen where any touch will cause a line of phantom touches. This is with the tablet held in hand.

I just close the smart cover and open it and the spot goes away.
[Nexus 7 (2013) General] sfhub:
Unless you actively ran the ts-unlock, you are still using ts10.
[Nexus 7 (2013) General] digiboy1:
Oh, thanks sfhub! :D didn't know that. :)

Then, I'll try ts-unlock once. Else, I'll get back to your ultimate solution ts-10 :)

Thank you so much! :) Had I been earning, I'd have donated a good amount for all the help that you've been doing around here.
[Nexus 7 (2013) General] sfhub:
I should warn you though that while you can upgrade to 4.4 without losing your data, if you try to downgrade and flash a 4.3 ROM back you'll need to wipe your data or the tablet will get stuck on X

So while ts-unlock, ts10, etc. wouldn't cause you to lose your data, going to 4.4 and trying to go back would.

Make a full backup of your 4.3 setup if you think you might need to go back.

Now if you are ok with 4.4 then you shouldn't need to worry about the stuff about going back to 4.3.

The ts* files will work fine with 4.4. The only change to the instructions is the boot will be stuck on the bouncingballs (replacement for X). This is because a 4.3 kernel cannot boot a 4.4 ROM. When it does that, just press/hold the power button for 10-15 seconds until the tablet reboots and the rest of the instructions stay the same.
[Nexus 7 (2013) General] mertzi:
Just did an adb sideload upgrade to kit kat with ts-unlock applied before and initially i have no grounding issues and touch seems to work great too. I write with swipe though and sometimes it's hard to tell if something miswritten is caused by yourself or hardware. This was written with my nexus lying flat on my desktop with no issues.
[Nexus 7 (2013) General] digiboy1:
Yeah, but why would I go from 4.4 to 4.3?

Is there anything wrong with 4.4? Even if there'd be, I'd be related top touchscreen, I suppose. And if some touchscreen issues are faced, i'd boot ts10 because that works, as you just told.

One doubt, if you could clarify.

I'm currently on ts10. Say I update using ota to kitkat. Then I boot ts-unlock. And I find touchscreen issues still present, and I boot ts10 again, then in this whole process, I'm not losing any of my data or ap data/settings, right?

I'm on stock only. Not gone for any custom rom. ( I guess, this is irrelevant)
[Nexus 7 (2013) General] Sud0lit3:
the version of software you are running: 10

what was/is broken: Multi touch on the axis because VERY jittery and jumpy.

whether any of the packages helped: None

the version of software you are running: 20

what was/is broken: Much better than the previous but still jumpy and jittery.

whether any of the packages helped: None

the version of software you are running: 30

what was/is broken: Probably most stable out of the 3 but the jitters and jumps were still there and occasionally it wouldnt detect my multi touch

whether any of the packages helped: None

Thanks for the help. I hope this helps you.
[Nexus 7 (2013) General] sfhub:
I have switched over the .idc and done a factory reset but it never seemed to make a noticeable difference or if there was any it was so little, I just chalked it up to normal variability. On the other hand the touchscreen software immediately made a noticeable difference.

The .idc file changed between JWR66N and JSS15J, and stayed the same between JSS15J and JSS15Q so it couldn't have accounted for what your wife saw (as I recall she downgraded from JSS15Q to JSS15J)

Again, I can certainly believe you and your wife saw a difference. It is just unknown what caused that difference. It wasn't the touchscreen software itself as that didn't change, but it could have been some instability in the upgrade process or some, as yet, unidentified part of the ROM. You may want to switch back to JSS15Q to reconfirm the problem and do some factory resets.

I have seen strange things where you can induce dead bands in the screen (I think someone on this thread had the same experience) if you force the multi-touch issues too many times.

At first I thought I had somehow broken my touchscreen, but eventually realized, after a reboot, things went back to normal. It feels like there is some state retention in the touchscreen software that gets triggered when you force the multi-touch issues, at least with some versions and some screens.

Anyway, the software is done as a semi-double-blind so people don't introduce their own biases.
[Nexus 7 (2013) General] afremont:
I'd really like to find where they store the scaling information for the X and Y coordinates and get the four corners a little better aligned. Since it is a capacitive sensor, there must be some kind of auto calibration going on where it tries to adjust to whatever the ambient conditions and the body capacitance variation of different people. I'm wondering if the wifi and other transmitters (NFC?) on and off is driving it a little batty with the sudden and steep changes in environment. I'm always expectant of RFI problems especially with something this tightly integrated.

If I recall correctly, the change log for the various versions of ektf3k.c keep mentioning "broken wire" which scares me a little that there is a missing jumper, grounding tab or some other manufacturing defect. Also, if there is dust/dirt under the glass that people can see with their naked eye, then there is likely dust/dirt big enough to cause issues with zebra pads or other pressure type electrical contacts. A missing ground for a shield could very well be impossible to entirely compensate for. I sure hope that's not the case here. I saw at least one poster claim to have disassembled his N7 and cleaned some contacts resulting in a perfectly functioning screen. I don't know if that's true, but it sounds plausible. I don't think I'll be disassembling mine to find out though. Have fun. ;)
[Nexus 7 (2013) General] sfhub:
I believe "broken line" (not "broken wire") refers to what we are calling dead bands where you do the paint test in YAMTT and there is just a black band where the paint doesn't register. The line becomes "broken" as you slide across that area.

I actually doubt there is a physical "grounding" issue the way folks are referring to it. These being battery-operated devices it doesn't make sense to design them so they only operate properly when connected to physical ground. Of course they will be connected to the ground plane relative to the battery, otherwise the screen would work even worse or not work at all.

IMO people are just confusing connecting the charger with grounding the unit. Lots of things happen when you connect the charger. Voltages and currents to components can change. Voltage regulators adjust. The touchscreen software specifically gets signals to tell it whether the unit is connected to usb/ac, slimport, or battery. Presumably it needs to behave differently in each of these conditions.

Actually prior to this unit, most of my experience with misbehaving touchscreens was only when connecting the charger. The touchscreen on some previous devices (Samsung, HTC) would behave similar to how ours are behaving, except those devices would exhibit them when connected to charger (what people are calling grounded) while we are seeing the behavior when connected to battery. So for those other devices, the problem clearly couldn't be "grounding" issues because it would have been connected to ground when plugged into the charger, but the symptoms were the same or very similar.
[Nexus 7 (2013) General] afremont:
Ok, I should have checked it out before saying anything. Broken line then it is. Oops. Yeah, when I refer to grounding, I mean things like shielding with respect to the circuit electrical ground inside the tablet. I know what you're saying about people (mis)using the term though. Even when plugged into the charger, it's not connected to Earth ground or even the neutral wire of the AC circuit, that would be dangerous. I could still see where a bad/missing "ground" from a metal shield could result in this. I've seen older, non-touch LCD displays freak out when you remove the surrounding metal shield and touch the screen.

I can touch the metal shield of the USB connector and the problems cease on mine, but just picking it up or putting my hand behind the display (even when in the leather case) makes the problems so much less severe that they are livable. I'm going to try and go back to the original released firmware on mine and see if that doesn't pretty much eliminate the issues.

I forgot to mention earlier that I tend to agree with you in that I think the firmware/driver or upper software tries to learn, and it may be picking up a few bad habits doing so. There definitely seems to be a short term memory on mine if I consistently tap the same area, it will gradually start to ignore it. It was terrible on my wife's. That makes me think that there have been more changes than just the firmware throughout the releases. I used it a lot with the show touches turned on and would swear that there were many occasions that the touch showed on the screen, but wasn't registered by the application. I'm thinking that somewhere in the higher level code they're trying to identify and ignore "noise" and this might be part of the reason that people seem to experience relief from just rolling back the ROM image, even though the firmware stays the same.
[Nexus 7 (2013) General] lespaulman67:
Well guys I got my new Nexus 7 made on 7/2013 this one didn't have 4.3 out of the box like my last one.So it loaded with JWR66N. I was wondering You guys think I should hold off on the JSS15Q update.I did a good test of this screen and its working 100% perfect.

Let me know what you think. My GPS is not working.
[Nexus 7 (2013) General] afremont:
If you don't mind a little hacking and wiping your device once, there is a way to put the GPS firmware update on without upgrading the ROM. You have to "unlock" the bootloader, install a recovery program such as ClockWorkMod Recovery using fastboot and then "push" the GPS Update file to the tablet using adb. Finally, you will reboot and go into the recovery program and install the zip file and then wipe the cache. This will put the firmware on the device without making any other changes to it. Does this sound like your idea of fun, or does it scare the pants off you? :laugh:

That said, it might be worth it to you to let it upgrade to Q (especially if you are experiencing any stability problems, reboots etc) and then "fix" your firmware using the contribution from sfhub.
[Nexus 7 (2013) General] lespaulman67:
Well I know how to do the unlock bootloader, I know how to install fastboot boot *******.img. I just don't know how to restore it from the Clockworkmod. If I want to take it back.

I do know how to lock the bootloader. Fastboot oem lock

Help me out I will give it a try and not load the JSS15Q.

My Nexus is perfect not a problem with the screen at all on dead spots.
[Nexus 7 (2013) General] sfhub:
If you just want the GPS fix for your current OS version, it is available here:

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

It is also in my signature for future reference.
[Nexus 7 (2013) General] afremont:
The first thing is to make sure that you have adb and fastboot device drivers for windows and the associated executable commands.

Hook up your tablet to the PC

Enable Developer Options in Settings/About Tablet by pressing on the last item about 8 times

Go into Developer Options and enable USB debugging

Run "adb devices" to make sure that it sees it.

Issue the command "adb reboot-bootloader" and your tablet will reboot into the bootloader with android on his back with doors open

(at this point fastboot becomes the method to communicate)

Send "fastboot devices" to make sure windows sees it.

Send "fastboot oem unlock" to unlock the bootloader, acknowledge the threat and wave goodbye to your apps/data/etc

Select "Restart Bootloader" and verify the unlocked status.

Restart the tablet and go into Settings/About Tablet and reenable Developer Options and then turn on Debugging again since the wipe cleared all that

Run "adb devices" to make sure you have it connected ok

Now "push" the update to the tablet with "adb push GPS_Update.zip /sdcard/"

Now issue "adb reboot-bootloader" to get into the fastboot loader.

Then use the power/vol up/vol down to select Restart Bootloader to verify that the bootloader is unlocked

Now burn in the recovery program with "fastboot flash recovery CWM_Image_Name.img

Pick up your tablet and using the volume as up/down and power as select, select Boot Recovery and boot into the recovery program. You'll see Google in the middle of the screen and an unlocked lock at the bottom while it boots up the clockworkmod recovery program.

Now select "choose zip from SDCARD"

Select the "0" directory if you don't see the list of folders like Downloads, Pictures, etc.

You should see your GPS update zip file, so select it

Confirm the action and then you'll see the install messages scroll at the bottom of the screen

Now select "wipe cache partition"

Now reboot and hopefully enjoy a functional GPS

Good luck and don't hesitate to ask questions if you get stuck. As long as you don't "fastboot flash bootloader xxxx", you shouldn't be able to brick the tablet no matter how bad you mess up. Never flash the bootloader.

And yes, it can all be put back to where the people at the store can't tell what you did. The images are available and relocking the bootloader is a piece of cake.
[Nexus 7 (2013) General] sfhub:
I should warn you though, about the GPS fix, in the process you'll end up running TWRP (or some custom recovery).

TWRP 2.6.0.0 will implicitly upgrade your touchscreen software to JSS15J levels.

TWRP 2.6.1.0 will implicitly upgrade your touchscreen software to JSS15Q levels.

This is because of the bundled kernels in those releases.

If it were me, I would install TS10, then just have no fear of upgrading to anything because your touchscreen software will be locked in place, but I understand if you don't want to mess with a working system. The thing is, there are so many ways to inadvertently upgrade your touchscreen software by accident, so IMO locking something that works in place is a better option that will relieve some anxiety.
[Nexus 7 (2013) General] cocchiararo:
How did you load JWR66N on it ?

:/
[Nexus 7 (2013) General] Chadneu:
JSS15Q

Had the typing issues after the last update, didn't have any issues before the update.

Ts10

Thank you very much!!
[Nexus 7 (2013) General] cocchiararo:
there is no "typing issue" :P
[Nexus 7 (2013) General] Chadneu:
That's the only way I could ever describe it. I didn't have any of the other issues. I got freezing and sticking on typing, that was it, maybe 5-15% of the time. I flashed ts10 and it's gone.

Not sure what else to say.
[Nexus 7 (2013) General] cocchiararo:
i was just kidding :p

I call it "sticky touch" issue.

It is not only when typing, touches "stick", and the next touch "unstickies" them.

It is easier to notice while typing.

TS-10 fixed it for me too.