Survey for unresponsive touchscreens

[Guest i am not a hacker]

Please take part in this survery if you phone had an unresponsive touchscreen. This excludes the bug on CM7 where you have to turn the screen off then on again for it to work. Please answer honestly so we can find out what the root of the problem is.

Please reply with your answers too so that we can be more specific and solve the problem a lot quicker.

Thank you for taking part and helping the Android Community!

Edited April 30, 2011 by i am not a hacker

[Guest i am not a hacker]

Let's vote and vote and fix this bug!

[Guest wbaw]

Not a bug, it's a bad connection. Take your phone back, it's broken.

[Guest iKrautDroid]

Not a bug, it's a bad connection. Take your phone back, it's broken.

I thought it was a bug on newer san frans...

[Guest wbaw]

I thought it was a bug on newer san frans...

CM7 & SS5 should work on new san frans.

[Guest KACE_231]

This issue for me can simply be fixed by turning the screen off and on, I got my san fran just over a month ago (mid march) so is very new

[Guest iKrautDroid]

This issue for me can simply be fixed by turning the screen off and on, I got my san fran just over a month ago (mid march) so is very new

I just tried the screen of thingy while playing pew pew on my fairly new blade, that does have some multitouch errors...

And yes, after locking and unlocking the screen the errors were gone.

About ten seconds (while playing pew pew) I got a nasty hiccup.

Then I could play for fifty seconds without any errors. Then I died...

Ill try a multitouch tester later...

[Guest iKrautDroid]

I just tried the screen of thingy while playing pew pew on my fairly new blade, that does have some multitouch errors...

And yes, after locking and unlocking the screen the errors were gone.

About ten seconds (while playing pew pew) I got a nasty hiccup.

Then I could play for fifty seconds without any errors. Then I died...

Ill try a multitouch tester later...

Multitouchtesters arent working for me.

But I played some more pew pew.

It seem that the errors are fixed for about 40-50 seconds after locking and unlocking the blade.