yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] DarkusC:
Will do, when I get off work tomorrow it's the first thing on my to-do list. lol

thanks
[Nexus 7 (2013) General] Kvil:
After i did all step by step every time i boot my Nexus 7 it always asks what launcher do i prefer to use. And it doesn`t matter if i choose "always", for example for nova launcher, or not.

Btw, it seems that t12 helped.

Nexus 7 wi-fi 32gb

Stock 4.3 JSS15R
[Nexus 7 (2013) General] Pfeffernuss:
Yup, same here. What I find mostly amazing is that you can clearly see the button being enabled (highlighted) yet the touch is still not being recognized as such. You do really have to re-press it. Odd.
[Nexus 7 (2013) General] sfhub:
That's not something related to this fix. It may have coincidentally occurred around the time you tried this, but the fix doesn't touch your filesystem at all so it can't be causing that.

What happens if you uninstall nova launcher?
[Nexus 7 (2013) General] sfhub:
If you want to tell whether that is a touchscreen or app issue, turn on show taps in developer options.

If it is a touchscreen issue, the tap indicator will behave differently from normal recognized taps.
[Nexus 7 (2013) General] Pfeffernuss:
First thing I did obviously. Mainly because I was mi****ting stuff. Thought I pointed correctly but the Nexus decided otherwise. Every tap is being registered on the screen but not always in a way to be expected. Long pressing remains an adventurous task. Some screen taps not leading to an action even though it is being registered as can clearly be seen by aforementioned developer option setting.
[Nexus 7 (2013) General] sfhub:
If the tap indicator is showing up, then going away, then the touchscreen DSP has done its job and communicated the tap. Something on the android or app side is not processing the tap properly. If the tap indicator is stuck on, then the issue is probably on the DSP side (ie what these fixes are addressing)

A while back I thought the taps not registering in my Dolphin browser session were because of the touchscreen issues, but I eventually realized it was Dolphin not processing taps until the page was more fully loaded.
[Nexus 7 (2013) General] iamnotkurtcobain:
I think I smash my n7 against the wall. Touch issues since I got it. Then I flashed the ts10 file and it was awesome... But then again after some time it went horsesh*t and worse than ever before. I tried ls20, ls30 and one more (9?). All bad...

FU Google.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) General] Kvil:
It boots normally without any quesions about what launcher do i want to use. But if i install any other launcher instead of nova the same thing occurs.
[Nexus 7 (2013) General] sfhub:
I've seen android ask which launcher to use if you have multiple launchers but usually it saves your choice and doesn't ask you again. In any event this has nothing to do with the fix in this thread.
[Nexus 7 (2013) General] sfhub:
Try using ts10 for 24hrs sprinkling in some reboots. If that doesn't help try the ones between ts10 and ts20 in the exp1 package.
[Nexus 7 (2013) General] iamnotkurtcobain:
But why should I reboot a couple times? I did that and still the same. Guess that's why people like apple devices. They WORK. Don't get me wrong I hate iOS and apple products but why isn't Google/Asus capable of making working devices?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) General] DowntownJeffBrown:
Lol ummm ok. You obviously don't follow blogs.

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] LittleConfucy:
I tried with multitouch testers and also Google Maps. Now when I align 2 fingers vertically it also happens. When I reboot it goes back to normal and progressively gets worse
[Nexus 7 (2013) General] NekroWolfen:
Try ts12... Mine didn't go well with ts10,20 or 30 neither... and I was about to smash the Nexus as well lol so I know how you feel.
[Nexus 7 (2013) General] iamnotkurtcobain:
I'll try but I'm losing hope. I shouldn't have to do us. I paid for a working device not a ****. Damn Google. And release 4.4! The teasing is getting boring.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) General] LittleConfucy:
Which one is ts12?
[Nexus 7 (2013) General] NekroWolfen:
I know, whe shoudn't have to do stuff like this to to get our device working, it's a shame for Google and Asus.

At least we have people like sfhub and other users trying to help and fixing what Google and Asus should have done right.

I hope Kit Kat lives to it's hype.

[MENTION=5124177]LittleConfucy[/MENTION] In the OP at the bottom with the attached files, is the one that says "boot-ts-exp1.7z".
[Nexus 7 (2013) General] LittleConfucy:
Mine works fine when it's connected to the computer, but when I disconnect it, it starts failing
[Nexus 7 (2013) General] DowntownJeffBrown:
That's 90% or more of the units

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] sfhub:
What happens if you don't purposely try to align and hold (ie you just briefly cross the fingers)

I think the question about real world was whether there were operations with apps that really require 3 simultaneous fingers. If not, just don't do it.

Also, next time if it degrades, try turning the screen off for a few seconds, then back on. This will often cause it to behave normally again and you won't lose context like a reboot.
[Nexus 7 (2013) General] sfhub:
The reason I suggest multiple reboots is it sometimes takes a couple of reboots for the calibration to settle in initially.

Do the packages behave differently for you? You should at least notice differences. Pick the one that works best and spend more time with that one and do some extra reboots. Then if it still isn't working well enough, try the experimental ones near in #.
[Nexus 7 (2013) General] DowntownJeffBrown:
Yup that's exactly what I meant by real world use :thumbup:

>^.^< Sent From Meow HTC One
[Nexus 7 (2013) General] bama78792000:
Any chance we could get these as a flashable file through cwm?
[Nexus 7 (2013) General] sfhub:
While it would be trivial to provide a flashable file for the kernel, it wouldn't make sense for how this is designed. The goal is not to have you run a special kernel to make your touchscreen usable. It is to use a kernel to load the touchscreen software, then have you go back to using your existing kernel.

Done in this way, you don't need to change every kernel out there to work with your touchscreen, once you find one of the ts variances that works well, it'll continue to work regardless of what software you install. Also new updates wouldn't overwrite your installed kernel.

This process is a intended to be a one time procedure you do in the beginning to figure which variance works best with your screen, not something that you'll be constantly doing over time, so needing to use fastboot command line shouldn't be an ongoing inconveniwnce .

So yes it could be done, but I won't be doing it because it doesn't make sense to do it in this situation.
[Nexus 7 (2013) General] creeve4:
The OP says that the drivers are "locked" but does not specify under what conditions.

Will flashing a new or different kernel overwrite the touchscreen drivers?

Some details concerning how exactly the drivers are "locked" would be helpful.
[Nexus 7 (2013) General] muyoso:
Ts-10 was way too sensitive for me, but was an improvement.

Ts-20 was absolutely perfect, but after a couple of reboots it started going crazy, especially with pinch to zoom and whenever two fingers were aligned vertically.

Trying out ts-30 now. Hopefully this one will be better.
[Nexus 7 (2013) General] sfhub:
You can flash different kernels, roms, install otas, factory images, perform factory resets, etc. Your touchscreen software will not change unless you run the unlock.
[Nexus 7 (2013) General] Sensamic:
Would flashing JSS15R work if Im now on JSS15Q?

I didnt have problems on R, so maybe downloading the stock factory image and flashing it would work? Or would the touchscreen driver still be the same as in Q?

Also, if we dont use the TS files and stay stock, could 4.4 fix this issue or another update from Google in the future? Or maybe theres no hope for more changes?

Thanks.
[Nexus 7 (2013) General] creeve4:
I'm curious if there is a correlation between the build date (month) of the device and the touchscreen driver that works best with that build date. Has anyone collected any data to test this theory? If not, I may start a new thread with a poll.
[Nexus 7 (2013) General] sfhub:
Touchscreen software on both q and r (from Asus/Google) is the same.

Some people do experience differences between q and r (worse for some, better for others) but most will see no difference, either no problems or problems persist.
[Nexus 7 (2013) General] sfhub:
In my experience there is no noticeable correlation.

Maybe that will change after September builds which is the latest I've helped people with.
[Nexus 7 (2013) General] LittleConfucy:
If I flash a ROM, will the firmware stay?
[Nexus 7 (2013) General] Sensamic:
Should I wait for 4.4 to see if it fixes this problem or should I return the tablet?

Tomorrow is my last day to return so I must decide now.
[Nexus 7 (2013) General] sfhub:
The touchscreen software in this post will remain after flashing a rom. If you'd like to go back to what came with the ROM just flash the unlock either before or after flashing the ROM.
[Nexus 7 (2013) General] Sensamic:
In theory, if the TS files make the touchscreen better for many then this is a software problem that can be fix by Google.

If it was a hardware problem then the TS files wouldnt be able to help anyone.

Just a theory.
[Nexus 7 (2013) General] sfhub:
If it were me and none of the TS files helped, I would return it.

No reason you should get stuck with a unit with a touchscreen issue hoping for a fix when you are being provided a return period to in part address these types of situations.

This is irrespective of whether kit kat does really fix this or not. It is just about risk management and whether you should assume the risk of not getting a fix when currently you have the option to not take on that risk.
[Nexus 7 (2013) General] sfhub:
I think your definition of "hardware problem" is too binary.

In a more nuanced definition there are hardware differences or variances which can be accounted for, up to a point, in software. However some of the variances may be too far off from the baseline to be accounted for.

Software often has to make accomodations for hardware variances, but not all hardware variances can be compensated for in software.
[Nexus 7 (2013) General] GTMoraes:
omg omg omg you made it

it seems to be working FLAWLESSLY

I've fast typed a text and it was CORRECT!

I've played multitouch games and it didn't SCRAMBLE THE HELL OUT!

YEAAAAHHH
[Nexus 7 (2013) General] c3k:
Didn't work for me (same results on all packages) :(

http://www.youtube.com/watch?v=qGMVmb0pVl0

Product: Nexus 7 2013 WiFI only (flo) 32GB

Hw revision: rev_e

Bootloader: FLO-03.15
[Nexus 7 (2013) General] DymekPC:
I sent my N7 to Asus... I tried all patches and each was something wrong.

Now im waiting for repair..
[Nexus 7 (2013) General] hasenbein1966:
Even after 1 1/2 weeks, my tablet works perfectly with ts11. Thumbs up!
[Nexus 7 (2013) General] sfhub:
If you are saying it behaved exactly the same way with all packages, then maybe something went wrong with the installation. If you are saying it behaved differently but there were still problems, then that is possible. If you haven't done so already, you might want to try the experimental ones.

I looked at your video and your screen behavior looks pretty bad. Most screens you need some amount of time (maybe a second or two) aligning your fingers before you see the ghost touches. Yours is almost instantaneous. It may be that yours is one that is too far off to be corrected.
[Nexus 7 (2013) General] eberaldo:
I just wanted to ask, whether the process of flashing the different ts firmwares can be done directly on the tablet. I go to work for the rest of the night, but don't have the ability to use the PC there to flash the drivers.

What would the commands be?

Besides, ts10 used to work quite well, but then started to act weird, so I tried ts11, got slighty better, but to no long avail.

Now tried ts20, but it acts very badly.

My benchmarks are multi touch test apps, shadowgun, dead trigger 2 and a PDF file in adobe reader.

Aiming jerks around heavily in the shooters, as well as scrolling in a document, when moving the finger diagonally from top to bottom. Two fingers crossing on a parallel line makes the test app go crazy.
[Nexus 7 (2013) General] DarkusC:
I managed to get some time to update my tablet to JSS15Q and it still has the exact same issue.

I even tried redoing the update to JSS15R.

I've just finished going back and trying the initial TS10, 20 and 30.

They all still make things significantly worse.

I've also noticed from using more multi-touch testing apps, that the problem ONLY occurs when using 2 or more fingers, and the vertical lines cross.

It's still a perfectly useable device, aside from some games.

It just irritates me to no end that it worked absolutely fine up until recently.
[Nexus 7 (2013) General] sfhub:
You can flash the kernel on the tablet rather than boot temporarily but I wouldn't really suggest it as the kernel might not be a good match for your ROM. The main purpose is to load the touchscreen software only, then step out of the way and go back to your existing ROM/kernel combination.

One way you could accomplish loading the touchscreen software then going back to your original kernel is using the following:

su

dd if=/dev/block/mmcblk0p14 of=/sdcard/img/boot-backup.img

dd if=/sdcard/img/boot-ts10-lock.img of=/dev/block/mmcblk0p14

reboot

su

dd if=/sdcard/img/boot-backup.img of=/dev/block/mmcblk0p14

reboot

I don't have time to give exact step-by-step instructions so only do this if you know what you are doing. It is easy to make typos and be left with a non-bootable system.

You could also stick the boot image in a TWRP flashable zip file, flash the ts image, reboot, then reflash your existing kernel, and reboot all from twrp.

It is just too much of a hassle to suggest the general public do this when using the fastboot command line is the least risky of the options and automatically falls back to a working system if something goes wrong.

As to multi-touch and FPS, your requirements for a usable system are probably the most stringent of all users as your thumbs will often be crossing as you move around and aim. What is usable for most people may not be usable for you. I do play Dead Trigger and have both a unit that works fine on it and another that occasionally has some jerking, which I can resolve by turning the display on/off.

Many people are coming from devices where just sliding results in broken touches or they have dead spots where the keyboard doesn't work or even dead bands running down the screen where touches don't register or touches that get stuck. For them, their multi-touch exposure might be just a 1/4 second overlap of fingers during pinch zooming or rotation in google maps where a small amount of jerkiness isn't that big a deal. This class of users finds good success with the different versions making their tablet "usable" rather than something they are banging their head on.

If you need perfect multi-touch for gaming, then the occurrence of physical touchscreens with those characteristics are rarer, but still possible to find. I have one unit like that and another that is mostly usable for gaming but occasionally I need to turn the screen on/off to reset the calibration.

I have found with one of my units if you overlap your fingers and hold long periods of time, like when you are trying to force multi-touch issues in the tester or playing FPS games, then it seems to increase the frequency of getting to the misbehaving state. If I don't play FPS games nor use the tester and just have incidental overlap in every day usage, like Google Maps, then the touchscreen is fine for many days at a time.
[Nexus 7 (2013) General] c3k:
My problem is very odd, I buy my unit 2 months ago, I don't usually play games and I was pretty happy until now.

During normal use there aren't big issues, since there's not a big use of multitouch gestures, what you see in the video is the very worst moment and not easy to reproduce.

I flash the 3 main version (10-20-30) and as soon that I see a ghost touch (more frequents) I've change to the next one. You think I have to try the other "steps"anyway? Is the ts a kind of "sensibility value"?
[Nexus 7 (2013) General] sfhub:
These are different DSP programming to address different issues.

You might get better results trying the ones from TS10 to TS20.

Don't assume if you get some multi-touch ghosting you should move on. Sometimes they are temporary and if you turn the screen off/on they go away. If you find one that has them infrequent enough, you might consider that usable but not perfect.

If your goal is to have a perfect multi-touch under the most stringent FPS game usage, you need to be lucky enough to have one of the better variances of screens.
[Nexus 7 (2013) General] Sensamic:
So most of the Nexus 7 aren't perfect for gaming? One of the main reasons I returned mine today was because in some games like Asphalt 8 I had problems with the multi-touch.

So if I want a good tablet to play all types of games flawlessly (and I do mean flawlessly. I don't want any kind of problems with multi-touch in games) should I forget about the Nexus 7 and look somewhere else?
[Nexus 7 (2013) General] sfhub:
I didn't say most Nexus 7 aren't perfect for gaming.

Of all the units that have touchscreen issues, the ones that will have perfect multitouch, for an FPS gamer, after applying these touchscreen software variations will be a smaller subset of the one where most people would consider the tablet usable (outside of gaming)

On the other hand, there are some units that are perfect out of the box and never have touchscreen issues regardless of what updates google puts out. I don't have the data to tell you what percentage of units these make up.

My advice, try another unit, if it still has issues, move on to a different tablet.
[Nexus 7 (2013) General] starxgamingx:
well i was skeptical when I first was going to try this, I was having trouble with keys sticking when I was typing and other small glitches, I have owned the tablet for about 5 days or so and after reading a review where I saw that this had been a common problem I actually saw it on my screen. I followed the well layed out instructions that OP posted, and installed the first one (number 10 I believe) and low and behold it fixed the issue! It might be sticking a little bit I cant tell 100% but its about 90 times better then it was.

In short, thanks for taking the time to do this, im very impressed that this problem had been addressed by a member of the community so soon after the tablet has been released. I hope very much that with the next update (Kitkat) that all these problems will be addressed by google and everyone especially the ones still having troubles.

Thanks for your help
[Nexus 7 (2013) General] DymekPC:
My N7 back from asus service and... still same problems -.-

Again multi-touch problem, again sensitive problem (maybe little more sensitive)...

Here is what they do:

i.imgur.com/ui4WtWu.jpg

I don't know what can i do...
[Nexus 7 (2013) General] danvee:
Try sfhub's fix, or call ASUS and request that they pick it up and repair it again. Repeat until they fix it for real or send you a new one (that, hopefully, will be ok).
[Nexus 7 (2013) General] creeve4:
Ts10 is working great on my N7 with manufacture date 2013.08! I'm running stock JSS15R with Franco kernel. Thank you thank you for the work you out into these fixes!
[Nexus 7 (2013) General] sfhub:
If it is too sensitive, sometimes adding a screen protector can help.
[Nexus 7 (2013) General] DymekPC:
No, sensitive now is ok, main problem is multi-touch.

Edit: I have no words for this.... asus service.

Look: imgur.com/ILD7OYj.jpg

This little hair is not on screen but... under it. And i can't clean it.
[Nexus 7 (2013) General] digiboy1:
Thank you so much man! I'm finally able to use swipe gesture in keyboard. Thank you so much!

Used ts10 and so far it's been great! :)
[Nexus 7 (2013) General] Sensamic:
Has anyone tried installing one of the new 4.4 ROMS like Paranoid?

Try installing one and see if there's any update to the touchscreen issue and if it now works better.
[Nexus 7 (2013) General] Wrngway:
I was wondering if anyone that used this fix successfully, tested it using the Nexus 7 II Tester app on the play store.

https://play.google.com/store/apps/details?id=com.gombosdev.nexus7tester&hl=en

I've yet to try this fix. I still have a week for exchanges though. My tablet isn't too bad for day to day use, but I still get stuck touches, unresponsive touches and drags. Multi touch seems to work ok outside google maps, which is barely responsive.

I tried the tester app and my screen goes bonkers with dozens of touch inputs within a few seconds on pattern 1. My Galaxy S3 tests fine.

[UPDATE] I tried this fix today after rooting. I had stuck touches and unresponsive touches before. GMaps multi-touch commands also were a little erratic. The TS-10 setting seems to have cleared this up. I tried all 3. The multi-touch test still has issues when I line up 3 touch points but outside of that, my N7 works just fine now. My issues were possibly related to EMI as holding the front glass with a 2nd hand or plugging to a charger also improved response.

As for the app I mentioned. All it does is display a picture. This seems to be some other issue.
[Nexus 7 (2013) General] gr8twhite:
Not sure what that app is doing but I have absolutely NO touchscreen issues running ts10. No ghost touches, no stuck or missed touches and I can open a graphic program and draw a continuous line everywhere on the screen. Landscape or portrait.

I can also get all ten fingers to register touches on the multi-touch test app and drag them across the screen with no issues.

Pretty sure a simple graphic picture (as the developer states) is not going to change that.

However, I opened the first screen and my nexus lost its mind. I had to power out of the app to get it to stop. I deleted it right away and my touch screen started working badly everywhere.

i had to powered off reset an couple times to get everything working perfectly again.

I'd advise avoiding that app. If this were a PC, I'd call it virus ware or something.

Pretty sure a "simple background picture" is not all that app is doing.

I loaded up a similar graphic from the net and it did nothing to the touchscreen.

Yeah, I'd call it a malicious app. Possibly some one with a bad touchscreen trying to get even more people to send thier's back and start a flood to force his issue with Asus or Google.

I'd avoid installing that one.....seriously. Don't install it.
[Nexus 7 (2013) General] c3k:
I tried the app too.

Pattern 1 make my device go crazy like nothing before.

All other paths make it less responsive and show ghost touches.

But after closing (just rotate the screen) everything as usual again.

I don't think this is a malicious app, it has no permission, but seems true that apps can simulate touches (need confirmation).

I wrote to the dev (that have others testing app on the store and reply to all store comments), I'll send him a link to this thread just now.

Seems possible to me that what you see on the screen generate the touch issues, I'm curious about what [MENTION=1299673]sfhub[/MENTION] think of it.
[Nexus 7 (2013) General] Pfeffernuss:
Yes. No. :p
[Nexus 7 (2013) General] Sensamic:
So no improvements in multi-touch?

That's a shame.
[Nexus 7 (2013) General] NekroWolfen:
Wait till the official 4.4 for the Nexus 7 is release.
[Nexus 7 (2013) General] hasenbein1966:
Yes, of course only the customized version of 4.4 for the N7 can bring the specific touchscreen fixes (because they are hardware-specific). This should be obvious, dudes.