yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] swisstourist:
it simulates a bad nexus 7.

nothing else.
[Nexus 7 (2013) General] NexusRunner:
wow! weird

I thought my Nexus 7 II generally has no touch related issue besides random freeze for a few seconds once in 2-3 days

...until I start this test

the screen goes nuts with so many stars of white dots mainly on the right half of the screen. It's always the "bottom" half (with ASUS logo on the back side) no matter the screen is flipped or not.

I see OP is also the author of "Display Test". So I ran similar pattern picture in that app and get similar result.

So the situation is clear: by just showing static picture on the screen, the multitouch somehow get fake triggered. weird but convinced.

PS:JSS15Q on PA
[Nexus 7 (2013) General] Jester Minute:
Just checking (for my sanity more than anything else).

Is this App showing the ghost touches on the nexus 7 (i.e. the touches a 'faulty' nexus makes)

OR

Is this App _simulating_ ghost touches on the nexus 7 (i.e. if you run this on a 'fine' Nexus It will still show ghost touches because it's just showing what it _would_ be like).

Does that make sense?

I'm just scratching my head as to why it wouldn't do that 'scattergun' effect of touches outside of this app (unless of course it's just a sim).

Just swapped out my Nexus for a replacement one regardless.

All the best,

Ant
[Nexus 7 (2013) General] nihil0:
Once again:

* The app simulates nothing!

* The app only shows one static image

That's all.

Everything else happens because the Nexus 7 II has this fake Touch bug.

If you don't trust me, then just make a screenshot, and open the screenshot in a viewer app without any zooming. You must see the very same result!
[Nexus 7 (2013) General] church:
Post up the image
[Nexus 7 (2013) General] nihil0:
Int he very first post.

As I said, you must view them without any zooming!
[Nexus 7 (2013) General] Ecartman12:
My thoughts

That is very interesting.
[Nexus 7 (2013) General] church:
Tried it out. No zooming. No issue. I don't get it
[Nexus 7 (2013) General] nihil0:
Are you sure, that you had no zooming?! You had the picture 1:1 on your display? I mean 1 pixel in the picture 1 pixel on the display?

If you can't show the picture in that way, because your viewer program does some minor scaling, then you don't get the effect!

Please be 100% sure, that you don't scale or zoom the picture!
[Nexus 7 (2013) General] bandit_knight:
If you view it in the gallery app it will be scaled down. It's because the tester app hides the status bar while the galery app only dims it out.
[Nexus 7 (2013) General] geocine:
This is weird , my nexus indeed has a bug confirmed with this test. On what specific screens does this occur aside from an image that hasn't been scaled? because I don't experience this behavior on other screens I frequent to.
[Nexus 7 (2013) General] sss2sssss:
OK, after testing ur apps and ur picture without any zooming, I should say that it's sure u are doing something in ur apps....

Here's the picture test , in ur apps got problem only ,so is sure u doing something , just admit it
[Nexus 7 (2013) General] sss2sssss:
edited
[Nexus 7 (2013) General] geocine:
There is nothing wrong with his app if you are a dev you would know it LOL. And please study what is scaling and what are pixels :)
[Nexus 7 (2013) General] sss2sssss:
But also in normal use also no touchscreen issue
[Nexus 7 (2013) General] nihil0:
The app does only this:

Layout:

...
<ImageView
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_centerInParent="true"
android:scaleType="center"
android:src="@drawable/img_test" />
...

Src:

...
[MENTION=439709]override[/MENTION]
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
requestWindowFeature(Window.FEATURE_NO_TITLE);
getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN);
setContentView(R.layout.activity_main);
....

Everything else in the app is just to handle the button pushes.

Write your app self, and stop with this kind of accusation!

I already said everything what is worth to say. So you believe what you want.
[Nexus 7 (2013) General] geocine:
Bugs need to be reproduced in order for it to be reported and fixed appropriately and this is the way to reproduce it. A non scaled static image is not the same as going through your menu and opening your applications or viewing an image on the gallery app. Even though the OP or me show you a code, I don't think you would really get what is happening.
[Nexus 7 (2013) General] bandit_knight:
Something triggers it. Apart from this app and the Display Tester I once observed similar ghost touch weirdness in Worms 2 Armageddon. It just started to randomly "tap" itself. I had to quit the game to stop it.
[Nexus 7 (2013) General] geocine:
I tried this using centerCrop, same behavior. I didn't realize this bug until now.

android:scaleType="centerCrop"
[Nexus 7 (2013) General] bandit_knight:
The image is shown scaled down on your screenshot. Please note that the status bar is all black but it is still there.
[Nexus 7 (2013) General] LoVeRice:
This is the same bug that happens in display tester app if you test gamma detection, much worse and you can screenshot whats happening lol
[Nexus 7 (2013) General] bokoy:
I restored the tablet with the one click method from the forum, I am thinking on sending it back to Asus. Since that is performing better than never, on the 15Q without update to 15R just because it can find it. As usual works better in your hand than over a table, but I have never had such a fake touching as your app does, or at least I can't notice. Still testing but maps works better than before, writing is also much better... It will go to Asus anyway.
[Nexus 7 (2013) General] geocine:
I create another app using half of the image used by [MENTION=394278]nihil0[/MENTION]. This is much less aggressive and your device won't go crazy as long as you don't touch it too much.

In this picture I am just using 1 FINGER
[Nexus 7 (2013) General] bandit_knight:
I guess the reason may be the 1px x 1px checkerboard pattern on the original image. For some reason it drives the touchscreen crazy.
[Nexus 7 (2013) General] geocine:
Yes I thought so because If I use an image without the 1px x 1px checkerboard pattern it works fine.
[Nexus 7 (2013) General] FlamingAngel82:
How weird. I don't get any issues at all on the multi touch screen tests, but on this.. my screen goes mental. Proper all over the place. How could this be?

Sent from my shiny Nexus 7 (2013)
[Nexus 7 (2013) General] freeza:
Mine appears to work fine with this app (just received my 3rd Nexus 7 (32GB) Tuesday for an unbelievable price of $200)
[Nexus 7 (2013) General] bandit_knight:
My device freaks out pretty much the same way in this app. I do not need to even touch the screen :) I think I'll send it for repair. I just checked and my warranty is valid here in Poland even though the device has been imported from US.
[Nexus 7 (2013) General] bokoy:
I'm sure that my problem is with the grounding of the device, in my hands is nearly no problem with it, but when I put it over the table or the sofa it goes really nuts. I had it rooted from 15Q to 15R, just with a custom kernel no roms or any other stuff, just bulletproof and now franco, and I use to have more problems with the multitouch than now that I just restored to 15Q. It has just updated a moment ago and I guess I can fell it even a bit better, but as I said a soon it is not touching you begins to fail. So mine is going to Asus for sure
[Nexus 7 (2013) General] bandit_knight:
Ok, more experimenting. I just flashed my device with sfhub's boot-ts20-lock.img. And guess what? In the tester app it only exhibits ghost touches when I start tapping the screen. It can even survive the Display Tester's Gamma Test screen. It only goes nuts if I start to touch and swipe. And also it can register 4 fingers multitouch with fingers located on 4 edges of a rectangle. Before it was getting jumpy already with 3 fingers multitouch. That all when it is grounded (held in a hand or placed on the lap).
[Nexus 7 (2013) General] Muikkuman:
So the multi touch problem is software fault right?
[Nexus 7 (2013) General] Richieboy67:
Have you guys tried the latest stock updates?
[Nexus 7 (2013) General] swisstourist:
so what does it mean?

my tablet is f... up? and need repair or what.?

and without this application, it works fine...

what would say nexus?
[Nexus 7 (2013) General] player911:
Perhaps this program is just showing all the touches the screen thinks its seeing but are so low they don't register as actual taps. I can look at the image in gallery and no problems.

I tested on my Galaxy Nexus and I don't see this behavior. Mucho sucko.

I am using ts10 custom touchscreen driver.

Surprised we haven't officially heard more big site news site report this. Seems to happen to most people.

Curious is ANY N7 can do this. If its a 100% fail then Asus may have a serious problem. Or if only us unlucky few?
[Nexus 7 (2013) General] swisstourist:
it just show static which are not recorded usually as they are too short.

you got static everywhere, hair, hands, shoes... doesn't mean you are a failure....!
[Nexus 7 (2013) General] Jester Minute:
Possibly true - but using the same program on my Tab 7.7 (the last decent samsung tab in my opinion ;) ) and my HTC ONE and they record zero ghost touches.

What would really be of use would be if someone with a "perfect" Nexus tested this app and recorded if it was showing ghost touches (or at least only a limited number of ghost touches compared to 'faulty' tablets).

That way people can determine whether 'zero ghost touches' is a possibility or if we have to accept a certain number on this piece of hardware.

Good work on the app regardless sir!

Ant
[Nexus 7 (2013) General] bandit_knight:
Does it really? In my case it really "touches" the UI. And once triggered it never stops until eventually these ghost touches would tap on the home button and quit the app. It may be touch sensitivity setting. I was on the ts10 touchscreen fix from sfhub's thread on this forum and I was getting ghost touches immediately after loading the app. I moved to ts20 and now I have to touch the screen to get ghost touches. Nothing happens if I just open the "tester" app unless the screen is actually touched.
[Nexus 7 (2013) General] nextelbuddy:
well my LTE model shows FAKE touches using this app with SHOW TOUCH enabled in development options.

what i DONT understand is why when I am in this app, i get so many ghost touches that eventually the app closes or i get kicked back to the home screen because the GHOST touches eventually touch the home/back or recent apps button yet when i'm at my normal home screen or in any other app i have 0 issues with touches.

that makes no sense, according to this fake touch app i have at least 100 fake touches in 10 min or less yet when not in this app i have 0 issues, no touches, no apps exiting them selves nothing...
[Nexus 7 (2013) General] daijizai:
Dude, I can't replicate this bug outside your "tester." Please release the source of the app.
[Nexus 7 (2013) General] nihil0:
I did it already. Here

In the latest version of the app, the app generates the checker board background. The gray strips are included in the layout. This was necessary, because I cant include as many pictures as many devices exists. This means that the latest app calculates one static view and doesn't uses any PNGs.

But the principle is the same, that one static image is enough and the Nexus7 II starts to generate the fake touches.

By the way, I think, that the nexus 7 II display driver tries to analyse somehow the image on the display and does some actions depending on the display content and this mechanism could be faulty and could cause the fake touches.

An app which has no root permissions can do nothing outside of the app self. This means also that cant push any button. I also don't know, how to generate fake touches for testing purposes. I only found out that this kind of picture causes fake touches on the Nexus 7 II, because my other app (Display Tester) has the same effect in the Gamma Test.
[Nexus 7 (2013) General] adit9989:
n interesting article: http://www.eetimes.com/document.asp?doc_id=1259704. Nexus 7 may use some new type of integrated touchscreen controller. Maybe the specific pattern generates a lot of noise which is not handled properly by touchscreen controller.
[Nexus 7 (2013) General] deezid:
Wow, this is weird. Can reproduce this problem when I load the Screenshot in Photoshop Touch (50% scaling)...

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) General] Tim4:
Lot of modern smartphones, like optimus g or iphone 5 got screens with built-in touch controller.

And about the bug, i think its somehow related to the fact new nexus works in book reading mode up to 24 hours.
[Nexus 7 (2013) General] Gorgtech:
I´ve also tried this app and my device goes ape****..Well, in normal use I don´t notice any problems, I still hope that Google will be able to fix this issues soon enough since I want to keep this device :eek:
[Nexus 7 (2013) General] [TSON]:
My nexus consistently locks the screen when I run this test and there's not even a lock button on-screen... Something fishy's going on.
[Nexus 7 (2013) General] DowntownJeffBrown:
Mine freaks out while using the app just like everyone else's. Though while not running the app I don't have any problems like this at all. So I'm not quite sure what the big problem is. Seems like everyone's n7 does this no matter if they have touchscreen issues during normal use or not. So my take is just don't run the app and I will never see this behavior.

>^.^< Sent from meow HTC One

---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------

Interesting :sly:

>^.^< Sent from meow HTC One
[Nexus 7 (2013) General] GreatTide:
Wow impressive. It reproduces massive wave of multi touches in the bottom half of the screen wild enough to press home button to turn app off. Tested in both app and just image file and got same result.

Now it makes me wonder if it is really the source of the current multi touch problem or just totaly new finding that complex image data can overload touch controller with LCD panel noise.

Cause current problem is not acting this much crazy. If it is the source alone, it could been just hi-rez wall paper people using... or color gradation on key board. Which is too wild to believe at the moment... to me at least.

However great finding sir.

I wonder if google during all this time talk with its touch controller manufacture, ELAN Microelectronics, to this issue. Or they believe it is just caused by poor touch firmware calibration.
[Nexus 7 (2013) General] yuyeung.wong:
Are you using touch control?
[Nexus 7 (2013) General] DowntownJeffBrown:
No... But again my take is that I don't have any issues when not using this app. I play games alot on my n7 without any problems and no problems while typing. So the best fix to not see this behavior is to not run this app ;)

>^.^< Sent from meow HTC One
[Nexus 7 (2013) General] Richieboy67:
Who gives a crap what a stupid app says. I cannot believe some guys are having no issues but an app says they have an issue so they are rma'ing.

If you notice touchscreen issues during use than by all means replace but who cares what an app shows?
[Nexus 7 (2013) General] Khendrix:
Same thoughts as Richieboy67, why would I try this app if i don't have any problems with my touchscreen? I can use it fine for typing, navigation and gaming. Never noticed any problem at all
[Nexus 7 (2013) General] hyperspacey:
How magnificently weird. I think the checkboard pixel pattern must be inducing a capacitance difference in the screen that, because of the proximity of the touch membrane, gets detected as a series of touch events.
[Nexus 7 (2013) General] supercurio:
Brilliant demonstration

The app need me to touch the display and it generates touch events all over the place (looks like noise)

The images themselves displayed at 100% trigger similar touch events even without actually touching anything at all.

I love my Nexus 7 but get annoyed as while typing the keyboard gets wild sometimes. Now I know why and how ^^
[Nexus 7 (2013) General] Guhrasoh:
Well my 2012 Nexus 7 shows similar fake touches with this app, and I never had (and still don't have) any touch problems with it.
[Nexus 7 (2013) General] player911:
Yea I never had any problems on my Original N7.

I tried the app on my Amoled Galaxy Nexus and I don't see the same behavior.

I couldn't duplicate the issue with just an image file. The only way it would skitz out is with that app.
[Nexus 7 (2013) General] swisstourist:
Best solution : trash it....
[Nexus 7 (2013) General] x4sper:
Are all of them defective like this? I bought one two days ago and it freaks out on this test should I return in hopes for a good one or are they all bad?
[Nexus 7 (2013) General] bokoy:
Forget about this test if you don't have any problem
[Nexus 7 (2013) General] Kizune:
I just tested this app (well, actually eocine's variant) and I got fake touches as well. When I wasn't touching the screen, they only occurred occasionally, but as soon as I put my finger on the screen, hell broke loose. I don't have any problems when I use my N7 as usual, though, so I won't RMA it because of this test result.

Anyway, I also noticed that the navigation bar had some weird stripes when I used the app in landscape mode. I also noticed these stripes when I accidentally hit a volume button and the volume indicator appeared. (See photographs)

Do you folks have the same problem, or is it just me?
[Nexus 7 (2013) General] x4sper:
Hmm so is there any n7 that pass this test? Anyone
[Nexus 7 (2013) General] player911:
I don't think so.
[Nexus 7 (2013) General] DowntownJeffBrown:
Nope that's why I completely discount anything this app tells me. Personally I think it's complete bull.

>^.^< Sent from meow HTC One
[Nexus 7 (2013) General] swisstourist:
Un installed...

Don't worry. Nexus 7 works well without this software..
[Nexus 7 (2013) General] Jimmy2u:
Simply no need to go for test...its a bull
[Nexus 7 (2013) General] geocine:
it's no bs , if you know how to read code and create this yourself (like i did) you will see it is really an issue. one day , after leaving my n7 and picked it up to check my mail, it went crazy showing all those fake touches . i was able to reproduce this without the app as well. it happened only once but yeah this happens
[Nexus 7 (2013) General] nihil0:
I don't know, why so many people are so mad about this app. There are people who built a similar app with the picture I included in the first app, and they just proved what I found.

I got today 8 one star reviews in the play store, and people are telling in the reviews that the app is a prank app, which is definitely not true. There is also one who goes so far, that he tells in a review he proved, that the app generates the fake touches:

"Fake	This app is fake. It checks your build.prop file and fakes a defective unit if it reads you're on a N7 2013. Source: Used on S3, no problem. Changed build.prop on S3 to N7 entry and got faked touch signatures. Flagged."

I start to think, that all this people are from a firm which is interested in covering up the whole story.

I never said that the N7 II is a bad device nor that it is not usable. I personally own one and I use it on daily basis.

But this problem exist regardless of the negative criticism against the tester app.
[Nexus 7 (2013) General] tzalay:
OMG people, are you really this nuts? It has been clearly stated that the problem occurs when a 1x1 pixel checkerboard is displayed. That is a pattern that won't show up in your game or on your home screen. So yes, in everyday use it won't cause you trouble. This does not mean it is not a problem, just read others that do report failures in normal use.

And for the genius testing this app on an old n7 and a galaxy nexus, this problem occurs on the NEW nexus 7 only (seems to be an oversensing capacitive digitizer that records the capacitive difference produced by neighboring pixels (one black one white, checkerboard, remember?) hence the software solution works by lowering sensitivity of the digitizer.
[Nexus 7 (2013) General] player911:
I couldn't reproduce the 1to1 test. Not saying it is false but it was also confirmed it was doing this on the OG N7.

I think this test is more of a "overloading the touchscreen driver" than showing how crazy the screen is.

With touchscreen touches enabled, no other app or image freaks out the touchscreen. So its like touching the stove. Yea its hot and it burns but you don't do it again and you live your life.

Its a good find, and hopefully Google can fix the reason it freaks out when viewing the image, but it doesn't really matter if only this app/image is the cause.

Just don't use it and you'll be fine.

Great find though. I'm not knocking your app or work. But rather saying it is an isolated problem that won't affect day to day use.
[Nexus 7 (2013) General] Richieboy67:
My point earlier in the thread was that if someone uses their device and never notices any issues then what difference does it make what any app says?

Personally I haven't experienced any touchscreen issues and I play tons of games. I don't know, maybe I'm not touching the screen in a way that messes things up but regardless. I'm not going to trust an app if my device is working fine.

Sent from my shiny new(bought last Nov), scratch less Nexus 4!
[Nexus 7 (2013) General] nihil0:
The app has been updated to V2.0.

I included 20 test patterns.

Here is how you can test:

Start the test by selecting a pattern. The pattern is visualized in the left upper corner. Not all patterns cause fake touches. One pattern can cause fake touches in landscape mode but not in portrait mode or vice versa.

Look for fake touches

Touch the display with one finger (one touch point)

Touch the display with two or more fingers (multiple touch points)

Try the same pattern in landscape/portrait mode

Select other pattern (by changing portrait/landscape mode)
[Nexus 7 (2013) General] timehat:
This certainly demonstrates something inherently wrong with the hardware of these devices. More along the "design flaw" sort of line, rather than "some faulty units" in my opinion. The natural presence of images with this sort of stark checkerboard pattern (or other patterns that might trigger this) is probably rare (why most people don't have day to day trouble/no trouble outside this app), but it certainly shows what's possible. It could be exploited by nefarious parties to make your tablet unusable.

In fact, I've created a web page that also demos this issue. It uses a 1x1 checkerboard pattern. It'll turn that pattern off after 10 seconds so things are usable again. On my wife's tablet, the digitizer completely stops responding with this pattern. Occasionally, one of the software buttons is pressed and the device goes to the home screen. Other times it's the window switcher. nihil0's app isn't fake, but for those who think that it's suspicious, then this page should help.

timothyehat.com/

m/checkerboard.html

(can't post links yet, so put that all on one line to see it... sigh.)

Warning: I wouldn't use that page too much. My wife's digitizer acts a bit funny for a while if that's on for too long... Don't blame me if it somehow manages to brick your device. :p
[Nexus 7 (2013) General] Matrix_19:
Very interesting thread.... Thank you nihil0 for the demo
[Nexus 7 (2013) General] Ashin:
Change your build.prop and it passes fine:good:
[Nexus 7 (2013) General] _jis_:
You didn't read previous posts in this thread probably, there was one user who has perfect touchscreen in his new N7:
[Nexus 7 (2013) General] _jis_:
I am sorry for such a late reply, but have found and have read this thread today. I can confirm observed weird behaviour with ghosted stripes, so it is another common problem of our beloved Nexuses 7 II.

---------- Post added at 04:38 PM ---------- Previous post was at 04:05 PM ----------

:confused: Did you try it yourself? How can you say it, this is not true!