yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] fuser-invent:
I have never had this bad of an issue on a device before and ts11 fixed it but I work with some Ainol tablets and all of them have had similar issues, just not nearly as bad.

My Hero, Fire and 3 Crystals all had ghost touch and swipes that would break in the middle. The Crystals also had a 20 pixel border issue near some edges of the screen that didn't register touches. There were also lots of reports of the Elf2 and Aurora2 having some touchscreen and border issues. My Cube Mini-ms has very minor issues.

I don't have any experience with more popular brands/models though. I asked a long time ago for details on what these TS files are doing just incase they could help other tablets but didn't get a response of anything that might be applied to other tablets.
[Nexus 7 (2013) General] _jis_:
Exactly, even the cheapest one and total noname behave better than N7 second generation in this regard which is a big shame for Asus.

Could you please test touch screen on any of above mentioned models with Nexus 7 II Tester and compare with results on N7II?
[Nexus 7 (2013) General] fuser-invent:
Yeah, I tested them as soon as I discovered my Nexus had issues because it reminded me of the other tablets. What I found was that the Crystal tabs, if you dragged your finger to the edge of the screen, would stop registering 20pixels from the edge. I can't remember which edges but I think it was right and bottom because I remember having to extend the registered area for LMT's PIE. The dead pixel zone also rotated with the tablet, which was weird.

All the Ainol tablets had occasional broken swipes but the difference was that it wasn't as often. You could swipe totally fine for a while and then one of them might break up to multi points (starting the swipe, breaking a large gap and then starting a new swipe in the same path) perhaps due to a lot of touch commands being placed in a row and the devices not being able to keep up?

For my foreign tablets, the ghost touches happened and still occasionally happen when the devices are plugged in and charging but not when they are on battery. There were reports from people of ghost touches both plugged in and unplugged but I didn't experience that.

All of the tablets freaked out when you did the multi-touch pinch thing and brought all your fingers together. When you get close enough the touch points would just jump all around. With the Nexus though, when lifting your fingers, they would continue to do that for a while like they were locked in place for a bit. With the foreign tablets, it would stop registering the multi-touches very quickly. Hope that answers your questions.
[Nexus 7 (2013) General] ahow628:
Alright, the final for me was that stock was terrible. ts-10 was just as bad. ts-20 was better, but not great. Just flashed ts-03 and so far, I am able to essentially touch type in landscape (or my version of multifinger touch typing for that small of a keyboard). I think it is almost as good as my Nexus 5, but I'll continue to try it out.

Also, is there a way to know what version is currently installed? I'm sure in a week I'll forget which version I used.
[Nexus 7 (2013) General] mdamaged:
No, no way to know, you'll just have to make as note of it, put it in Google Keep. :P
[Nexus 7 (2013) General] _jis_:
I am sorry, but not at all. You probably never try Nexus 7 II Tester don't you? It is completely different test. With this test you don't test multitouches, swipes or such a thing but you test if your touch panel is prone to EM interference from LCD panel itself.
[Nexus 7 (2013) General] mdamaged:
I've read too many negative things about that app, it seems to be a bit unreliable, some go as far as to call it a fake.
[Nexus 7 (2013) General] Porobu:
Its not a fake , i thought the same, so I took a screen capture, opened it in quickpic and the screen freaked out
[Nexus 7 (2013) General] mdamaged:
It has far too many negative statements which say the same thing about it, so pardon me if I dismiss your claim as quickly as you dismissed mine.
[Nexus 7 (2013) General] _jis_:
Just don't trust to everything what you have read on the internet and use your own brain and knowledge ;). As an example, even in this thread, there are many posts from ignorant people who denied this problem or are unable to proceed simple steps from OP. I am sorry, I'll post more about Nexus 7 II Tester later, I have no time just now. In the mean time try to read Google Play reviews of Nexus 7 II Tester if you didn't do it so far.
[Nexus 7 (2013) General] mdamaged:
I know there is a touch issue, I fixed mine with this very thread, my issue is with that particular app. There are other apps which are far more accurate and do not generate fake touches like that app you mentioned does, there are far too many reporting issues with that app to be a mere anomaly. Perhaps you should take some of your own advice, read the reviews, you will find many which corroborate my statements.
[Nexus 7 (2013) General] fuser-invent:
No I hadn't tried Nexus 7 II Tester, like mdamaged I read a lot of people's complaints and negative reviews. If there is a github with the code posted I would read it, see what the app is really doing and then trust it more. Either way, what is it really showing you? You're never going to encounter those screenshots in real life use. You can just enable "show touches" and "pointer location" in the developer settings and use the tablet as you normally would to see how the screen behaves, or use an app that does the same thing but visualized it better.

With that said, I installed it on my Ainol Fire and get nothing in the app from the static images and the usual behaviour when touching the screen. Again, I'd need to read the code because I don't see how an app like this can "test if your touch panel is prone to EM interference from LCD panel itself."
[Nexus 7 (2013) General] osm0sis:
What testing app(s) would you recommend?
[Nexus 7 (2013) General] mdamaged:
Mostly the apps I use every day, I discovered my problems by using apps which depend on touches, such as drawing apps, games which use touch, (swipe and flow based) keyboards, etc. I used Yet Another MultiTouch Test also to confirm my issue.
[Nexus 7 (2013) General] _jis_:
It is logical, because there are only a few apps which can demonstrate reaction of every N7II touch panel to EMI.

You completely miss the point. You compare apples and oranges. It is not about accuracy, Nexus 7 II Tester is not multitouch tester, it is a tester for EMI susceptibility.

Yes, it is a fate for apps where you must study their manual and their thread on XDA before you first run it and not every Android user is a bright and thinking man. Some of them are even small children ;)

I am sorry, but I use my own brain so I am immune to urban legends and mass hysteria.
[Nexus 7 (2013) General] mdamaged:
To each his own, I've said my peace. Good luck to you.
[Nexus 7 (2013) General] _jis_:
Oh boy :crying:, my English is so bad, so I have a hard time to discuss with all of you and explain it as a not native speaker, but I see that there is a right place and right time to do it. I am sorry but I don't get arguments like "I read a lot of people's complaints and negative reviews". So let see the facts:

Yes, it is just a proof that other devices behave normally, because they doesn't use the same flawed LCD/touch panel combo.

http://www.youtube.com/watch?v=A8qdkgTClgU more later...

That's probably true, but problem is that no other device is prone to EMI from displayed moire patterns.

This is your false idea how this tester works, because you hadn't tried Nexus 7 II Tester so far, but it is not true.

:) Ok, there is a plenty relevant information from author itself and other XDA users:

This is the first post where is mentioned problem with Ghost touches in Gamma detection in Display Tester app (video):

http://xdaforums.com/showpost.php?p=46292627&postcount=456

Here is the original thread from the author of Nexus 7 II Tester app:

Fake touch tester - xda-developers

Author even attached two pictures (landscape a portrait) for suspicious users so they can show them yourself in a program they trust and publish code excerpt which is showing those pictures.

In reply to the post above is a video from another Screen Test app:

http://xdaforums.com/showpost.php?p=46293931&postcount=458

Here is a reaction from our god sfhub to above mentioned posts:

http://xdaforums.com/showpost.php?p=46294194&postcount=460

But who know sfhub, he is a very decent person, who isn't so much critical to flawed N7II too, it is a sad reality that no other Android device with touch panel hasn't such a design flaw.

Another testing program:

In this picture I am just using 1 FINGER

http://xdaforums.com/showpost.php?p=45735399&postcount=30

One XDA newcomer create simple web page for demonstration this bug:

http://xdaforums.com/showpost.php?p=46395774&postcount=78

http://timothyehat.com/m/checkerboard.html

Touchscreens being integrated inside LCDs | EE Times

Old, but very interesting article.

Possible HW solution to our problem:

Potential Nexus 7 Touch Screen Fix? - xda-developers

How Nexus 7 II Tester was born in the next post, but maybe tomorrow, it is near midnight here.
[Nexus 7 (2013) General] tsimitsangaz:
is it working on CM 4.4.4 to flash the ts files? I am getting softbrick.
[Nexus 7 (2013) General] mdamaged:
You don't flash the files, you boot them. And since they are from older kenels it is normal for them to get stuck booting, just wait 2 minutes, hold down power till it powers down, etc, etc, it's all in the OP.
[Nexus 7 (2013) General] tsimitsangaz:
I mean when I am at fastboot mode and doing the proccess to boot the ts in CM m8 I am getting green screen ,settling down for 2 mins holding power to close and after that it doesn't boot ,did it with clean rom and was ok before but with cm something is wrong.
[Nexus 7 (2013) General] mdamaged:
CM uses some CAF sources, one of them is the display driver, so maybe CM screwed with some other stuff. Sorry, that's why I stay away from CM sourced stuff myself.
[Nexus 7 (2013) General] tsimitsangaz:
I thought about it! revert to slim or clean or stock rom to patch the 11ts. damm!!
[Nexus 7 (2013) General] AndyYan:
Well, I think you didn't do exactly according to the steps in OP... It doesn't matter if you're on CM and it doesn't boot, just make sure you "boot" the kernel, wait for long enough, and proceed as the OP says. I have CM11 as well and despite getting that green screen and bootloop, I still successfully installed TS11.

Sent from Google Nexus 4 @ CM11
[Nexus 7 (2013) General] tsimitsangaz:
it worked! I left it for 5 mins with the green screen and did the process as normal.thanks guys!!
[Nexus 7 (2013) General] BobbaLouie:
I just bought a Nexus 7 from the Play Store and it arrived yesterday, 7/10/14. The manufacture date was Jan 2014 and it was completely unusable out of the box because of the touchscreen. Sent it back right away for a replacement.

How is it possible they are still making and selling these units with defective hardware? It was a black 16gig wifi only unit. I have read all the noise over the last 6 months about these issues and foolishly thought there was no way they still existed.

Silly me.
[Nexus 7 (2013) General] 318sugarhill:
I don't care how many devices have "complaints". I own probably 20 different touch screen devices...and NONE are this bad. Some it's lag and lack of processing power, some it's cheap hardware/software or both. This is really a problem. WIthout the fix, I refuse to use it. It just doesn't work right. NEVER had any issue with a screen like this on any other android device. Just because I don't put it in my signature, doesn't mean I don't have other devices. I've had complaints about my ipad 2 for years....but nothing like the Nexus 7. The fact that there is a fix on XDA that makes it 95% better for me tells me there is a real issue.
[Nexus 7 (2013) General] fuser-invent:
I feel the same way. Most un-usable device I've ever had out of the box. It's also really irritating that TS11 completely fixed the problem for me but anytime I unlock it and try a new stock release the problem is still there. If the fix is here, why can't they work it into the stock releases? I'm also really surprised there wasn't more press coverage about this. When the iPhone had that whole antenna thing where you needed a bumper or case to make a call and use it as an actual phone the story was all over the place.
[Nexus 7 (2013) General] _jis_:
Here is promised story about how Nexus 7 II Tester was born.

06.06.2013 I have buy Display Tester Pro Unlocker and use it on all of my Android devices to my satisfaction without any problems for nearly half an year.

15.11.2013 I have buy N7II. I did know about touch panel problems before from this thread, but one colleague at work tell me that he has N7II a few weeks already and that he has never have such a problem, so that all this is not about all N7IIs but only about some bad batch probably. So I went to buy my N7II, but immediately out of box realize that this thread was valid. Next day I instructed by phone my colleague at work (he is from another town) how to do some tests and he realized the same as me despite the fact that he thinked that his unit is touch panel fault free.

18.11.2013 I sent this letter to Display Tester Pro developer

The developer tell me in his answer that he didn't had an N7II till August 2013, so he had no chance to play with the device. But he got some complaints from users against the Gamma detection test picture in his Display Tester app on Google Play. After he got 4 or 5 negative reports because of this he bought an N7II and tried it for yourself. So this is story how he discovered the fake touch problem on N7II. But despite this problem he regard the N7II a great device otherwise and he use his N7II every day and never had fake touch problem elsewhere, just with the Gamma detection test picture in Display Tester and Nexus 7 II Tester. So he think, nobody should be frustrated and even he would buy the device again. But to be honest I couldn't say the same :(.

One could think that the negative reviews for the N7 II Tester are written by people who try to disqualify the app and the problem itself in this way. Some of them are just lying in their reviews so clever that it seems that they are organized somehow (see the second worst example above and read all the facts from my previous post). Another interesting thing is, that no big website or blog has mentioned Nexus 7 II Tester, or that the N7II has this kind of problem with the display. I am not alone noticing this, others noticed this too:

---------- Post added at 09:54 AM ---------- Previous post was at 09:39 AM ----------

MultiTouch Tester | AppBrain Android Market

Yet Another MultiTouch Test | AppBrain Android Market

MultiTouch Visualizer 2 | AppBrain Android Market

Multitouch Test | AppBrain Android Market

Nexus 7 II Tester | AppBrain Android Market

Display Tester | AppBrain Android Market

Test Screen | AppBrain Android Market

Screen test | AppBrain Android Market

Screen Test | AppBrain Android Market
[Nexus 7 (2013) General] osm0sis:
_jis_, that's just an email.. Doesn't really prove it works. Especially shows that less effected units (like your friend's, and mine) still show just as badly in N7IIT, which is what makes it suspect. One would expect them to be at least a bit better. Have you tried to recreate the build.prop thing? That would be pretty damning.
[Nexus 7 (2013) General] ahow628:
I'm going to try to do this later unless someone beats me to it.

I have major doubts about that tester app. Seems very shady. An app that supposedly just projects patterns on the screen should not have a disclaimer about wrecking your device unless something else is going on.

EDIT: Set the build prop to the same as my Nexus 5 and it was still doing it so that makes me feel slightly better. Hopefully someone else tried it since I may or may not know what I'm doing.
[Nexus 7 (2013) General] _jis_:
I am sorry, but I am starting to think that I only wasted my time here, because no one read my previous post with facts, which is full of various proofs of evidence that N7II is prone to EMI from displayed moire pattern because its LCD/touch panel combo has fatal design flaw.

You miss the point. Nexus 7 II Tester is not multitouch tester, it is a tester for EMI susceptibility and all N7II units are affected by EMI.

But yes, because of small HW assembly differences (cabling, connectors, shielding foils, ...) some units has less problems than other with multitouches etc, but it is different story.

Oh, you read this:

Yes I have tried it. I made N7II from my Samsung Galaxy Note II (I still have this faked device in Google Play) and guess what happened when I completely goes through Nexus 7 II Tester - nothing, because this review is pure lie.

I really don't know why majority here are so against Nexus 7 II Tester, when you can easily demonstrate the same effect with displaing plain web page, as is described in my post with facts:

Or you can try another app...

Author of Nexus 7 II Tester even attached two pictures (landscape a portrait) for suspicious users so they can show them yourself in a program they trust and he publish code excerpt which is showing those pictures so anyone can prepare his/her own app to do the same.

That's all, as had Mr. mdamaged said

and to all gombosdev haters.

PS: Did you know that he is an author of Display Tester - the best app of its kind in Google Play and that he have small but pretty decent app portfolio?
[Nexus 7 (2013) General] fuser-invent:
I'm not "against" the app. I just want REAL facts, like what the code is so I can see what the app is doing and how it measures EMI (if that is what it is doing). I just want to know how it works and what is happening. Its obvious that displaying the image causes touch issues but the question is WHY does it do that? What if the touch issues are a reaction to something else, how do we know its measuring EMI? I was unable to find any technical information saying that you can measure EMI with a gamma image.

On another note, my Nexus 7 does have issues when viewing the image in the app and through the web page. It also still has issues when I change the build.prop to other fingerprints, even non-nexus devices. However, there are absolutely no touch issues outside of displaying the gamma image on my device since using ts11. The tablet is 100% functional and never gets ghost touches or any other multi-touch issues with ts11. So why does it matter that a gamma image that I would never view otherwise causes ghost touches? I think that is the primary point here.
[Nexus 7 (2013) General] ahow628:
[MENTION=4478620]_jis_[/MENTION] No offense, but you sound like you are a friend of the dev or the dev himself based on your defenses and shilling and whatnot.

As others have mentioned, if the dev wants to post the code so it can be reviewed, that would be optimal since no one really knows what is going on at this point.
[Nexus 7 (2013) General] _jis_:
Please first read this short article about integration LCD and touch panels into sandwich combo:

And thats all. In N7II is used flawed LCD/touch panel combo. EMI is produced by LCD panel itself, in less degree by other components and by the user hands and fingers, ... Quality touchscreen controller should be able to eliminate all EMI but it is not our case unfortunately.

As I wrote, some users of Display Tester tested their N7II with this app and in that way purely incidentally realize that the Gamma detection test picture trigger EMI generated by LCD in such amount that touchscreen controller cannot eliminate it. I was one of those users:

So, here are answers to your questions:

Nexus 7 II Tester just show static moire picture in a precise way 1:1 without any picture resizing / resampling to boost EMI generated by LCD (picture resizing destroy moire pattern and lower EMI generated by LCD). That was invented purely incidentally, but problem is that no other Android touch screen device has its touchscreen controller so susceptible to EMI from LCD panel itself. Nexus 7 II Tester doesn't measure level of this susceptibility, with this tool you can just test / demonstrate the flawed touchscreen controller of your N7II device.

Primary point is that that no other Android touch screen device has its touchscreen controller so susceptible to EMI from LCD panel itself. You can lower some issues as dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. by using custom touchscreen controller software from this thread. But there is no need for custom touchscreen controller software on any other Android touch screen device, or at least on so horribly high level.

---------- Post added at 02:20 AM ---------- Previous post was at 02:03 AM ----------

I have no connection with developer as you can see for example from this post in his old thread: http://xdaforums.com/showthread.php?p=53100270

I am just angry when people doesn't listen, doesn't read, doesn't think and only further boost mass hysteria about one innocent app and some people are even lying (see mentioned second worst review example).

There is no need for this when you can easily yourself demonstrate the same effect with displaying plain web page, as is described in my post with facts.
[Nexus 7 (2013) General] CTCaer:
Why you complain about this app, I can't under stand. Just use Pointer Location in dev options if you don't believe it.

Or create an image from that pattern and view it at your favorite gallery at 100% size. Or just decompile it like I did.

Or make an app, I can post you the source.

The device has clearly problems from EMI emitted from the LCD/Led backlighting.

Some people are lucky with low EMI, others not.

My case:

Biggest problem when I'm reading mangas and news (text based news app) with one hand. And 3 games.

So if your device behaves good don't complain (and bush apps) and just enjoy it.

I enjoy it, even with the above small problems.
[Nexus 7 (2013) General] fuser-invent:
Yes please, post the source code.
[Nexus 7 (2013) General] hoangtungst:
Sorry noob question , can I use this for 4.4.4 rom ?

neXus 7
[Nexus 7 (2013) General] sam298:
I am using ts10 with stock 4.4.4 and it is perfect.
[Nexus 7 (2013) General] CTCaer:
here's a simple app using pattern 1.

Compiled apk and source code
[Nexus 7 (2013) General] WSZR:
Boot is a component of the kernel? After using the boot-ts-unlock.img standing on Google.
[Nexus 7 (2013) General] _delice_doluca_:
So what are the ways to eliminate EMI? Maybe a case with a hidden Faraday Cage inside? So that it can suck some extra electromagnetic field thus causing less EMI goes upper side of the screen where the touch panel lies..
[Nexus 7 (2013) General] danaff37:
Then you wouldn't any wifi of bluetooth or lte or signal of any kind.
[Nexus 7 (2013) General] Karlmadur:
I started with ts-10 and it seems alot better.
[Nexus 7 (2013) General] demol3:
I tried the app in my Nook HD and it produces no ghost touch.

I tried the app in my Nexus 7 with different ts image and get mixed result: all tested with pattern 1

ts10: many ghost touches in the bottom area

ts20 ts30: no ghost touch when I select the pattern, when I touched the screen myself, the ghost touch appears

It looks like the devices does suffer from EMI issues as different calibration does not help.

Sometime when i get ghost touch, I just rub it in my shirt and it's ok again.
[Nexus 7 (2013) General] Bezeq:
After updating to 4.4.4 i had a lot issue with touch, couldn't play, its all ways clicked other places, after flashing "boot-ts10-lock"

Its working perfectly, thanks you very much!!
[Nexus 7 (2013) General] ahmedsalah83:
Thanks for the fix ... I followed the instructions and it worked flawlessly using ts10. I didn't try the others. I had just bought this tablet for half price. It was used but in excellent condition. Now I know how I got it for this price, probably the seller wanted to get rid of it because of the touchscreen issues.

Thanks again