Touchscreen doesn't work

[Guest i am not a hacker]

Ok, this was the fist time i installed a custom ROM on the Blade. It was CM7 N35. When it booted up, it showed touch the Android to start. The thing was that the touchscreen didn't work. The buttons worked, menu would show wireless settings, but the touchscreen doesn't work.

What went wrong? Should i try N36?

[Guest i am not a hacker]

I have no idea what to do!

[Guest ronc2000]

You need to give more details.

If you searched the forums you would have found hundreds of messages regarding this issue.

[Guest lixcab]

if (md5sum == [correct variable]) { 

Reflash rom; 

}

Else {

Download CM7;

Load in OSF;

Reflash rom;

}

[Guest worto03]

I got this last week when I replaced the stock ROM with modaco r12 and panicked a bit but then I removed the battery and started it up again it's been fine since - have you tried that already?

[Guest i am not a hacker]

yes

[Guest i am not a hacker]

can someone tell me how to fix this

[Guest sambartle]

Currently no. Its a known issue with some phones.

[Guest i am not a hacker]

could other ROMs work with it, or the stock ROMs from Modaco? or is my phone broken?

[Guest agreenjesus]

My touch screen died after having the blue tint issue. I returned it to Orange & bought another one.

[Guest AndroThomas]

Hello!

I have a very similar problem with a gray ZTE device from austrian dealer Hofer.

I bought two devices from the same stack last week and one works perfectly with custom ROMs, the other one doesnt.

On both the firmware is build b02 from provider yesss.

Both have exactly the same chipinfo output. Needless to say that the IMEI is slightly different.

I flashed one first with sdb and fastboot to clockwork 3.0.1.4. This worked, I did a backup and flashed Cyanogen rc4

The touchscreen doesnt react. Did displace the abttery for some hours, rebooted, wiped everything. Still no function.

The Touchscreen is dead from all on and ever was. No possibility to enter a PIN for example.

Neither works a nightly build, or another custom ROM. The restore of the stock ROM brings the Touchscreen back to life.

The other device, I flashed with ROM Manager, to exactly the same clockwork and did a flash to a nightly (35) and it worked, it wors with other nightlies and rc4, too.

Never had the problem.

So I tried to install an old version of clockwork via ROM Manager, back to the same new version (so I had clockwork installed the same way as on the other device).

Still the same problem.

Whatever I do, wipe, no wipe, flash back, install with or without google apps, anyway. One (always the same) device is working with no issues, the other wont until the stock rom is reinstalled.

Touchscreens are from Synaptics, Glass is TRULY, i can provider more in depth information on request. But the thing is, that nothing differs.

It was a slightly different way I first time installed clockwork, and it has another IMEI, of course.

So from my point of view I can say: ITS NOT THE BUILD B02.

Any ideas welcome.

[Guest i am not a hacker]

how did you get the stock ROM? Did you get one from the list on Modaco?

[Guest AndroThomas]

how did you get the stock ROM? Did you get one from the list on Modaco?

As i said, I did a backup.

Maybe this is useful for you:

http://forum.cyanogenmod.com/topic/19640-n...orking-touches/

[Guest sambartle]

Hello!

I have a very similar problem with a gray ZTE device from austrian dealer Hofer.

I bought two devices from the same stack last week and one works perfectly with custom ROMs, the other one doesnt.

On both the firmware is build b02 from provider yesss.

Hi,

Have a look at the last page of this thread: http://android.modaco.com/content-page/331...w-rom/page/100/

It appears that if you do a logcat you get some weird messages about missing touchscreen config on phones that dont work.. on my phone that works reliably I dont get the messages..

Would be interesting to see if you get that message on one and not the other.

That thread is a good place to look as well as although it says Orange... it probably is the same problem (im almost certain in fact)

Sam

[Guest AndroThomas]

Hi,

Have a look at the last page of this thread: http://android.modaco.com/content-page/331...w-rom/page/100/

It appears that if you do a logcat you get some weird messages about missing touchscreen config on phones that dont work.. on my phone that works reliably I dont get the messages..

Would be interesting to see if you get that message on one and not the other.

That thread is a good place to look as well as although it says Orange... it probably is the same problem (im almost certain in fact)

Sam

The working device on Cyanogen lists some info, I don't have the other one with me now, it'S my girlfriends, and at the moment on stock ROM.

So mine, which works:

# logcat |grep touch

logcat |grep touch

I/InputManager-Callbacks( 175): No input device calibration properties found for device synaptics-rmi-touchscreen.

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=0/0 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=0 seq=1 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=0/0 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=2 themeResource=null}

I/InputManager-Callbacks( 175): No virtual keys found for device synaptics-rmi-touchscreen.

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=3 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=4 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=5 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=6 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=7 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=8 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=9 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=10 themeResource=null}

I/ActivityManager( 175): Config changed: { scale=1.0 imsi=232/3 loc=de_AT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=11 themeResource=null}

Hope that helps someone. Or can anyone merge the posts. I read both, but postet to the one that describes the problem best.

Can also post a full log but it's quite long.

[Guest i am not a hacker]

im going to return it. When i get another, should i try and flash a custom ROM again? Or are the chances increasing because it will be newer?