Touch screen unresponsive froyo?

[Guest dragon2611]

Just had the problem where the touchscreen stops responding and you have to pull the battery and reboot the phone to get it working again.

Running MCR Alpha4 from the kitchen,

I'm wondering if it's caused by a notification, such as the one handcent triggers since that causes the display to power up to display the quick preview of the sms.

Since this is a different trigger to a normal wake (i.e not related to me pressing a button) I wondered if that what's causing the touchscreen not to respond.

[Guest jurrasstoil]

Just had the problem where the touchscreen stops responding and you have to pull the battery and reboot the phone to get it working again.

Running MCR Alpha4 from the kitchen,

I'm wondering if it's caused by a notification, such as the one handcent triggers since that causes the display to power up to display the quick preview of the sms.

Since this is a different trigger to a normal wake (i.e not related to me pressing a button) I wondered if that what's causing the touchscreen not to respond.

no one figured it out yet iirc.

http://android.modaco.com/content/zte-blad...kscreen-freeze/

its the one thing that does stop me from going from fillyjonk to froyo.

[Guest NightSt@lk3r]

I've had my San Fran a week and put Alpha 3 on it the day i got it and im yet to have this issue.

[Guest dragon2611]

I've had my San Fran a week and put Alpha 3 on it the day i got it and im yet to have this issue.

It happens a lot less frequently on the later builds, and actually I'm trying to remember a time when it's happened on the later builds apart from when an notification has triggered a wakeup.

[Guest eLJay]

It happens a lot less frequently on the later builds, and actually I'm trying to remember a time when it's happened on the later builds apart from when an notification has triggered a wakeup.

I had this happen but only when trying to get a 32gb class 4 sdhc card to work, doesn't happen with the 8gb class 4 sdhc card.

[Guest isambard]

i've had touch screen freezes on 2.1

what happens is that first the touchscreen seems to register the x axis incorrectly, e.g. i tap bottom middle of the screen and it registers bottom right. then it doesn't register any taps at all.

reboot fixes

[Guest Donkey Oaty]

Just had the problem where the touchscreen stops responding and you have to pull the battery and reboot the phone to get it working again.

Running MCR Alpha4 from the kitchen,

I'm wondering if it's caused by a notification, such as the one handcent triggers since that causes the display to power up to display the quick preview of the sms.

Since this is a different trigger to a normal wake (i.e not related to me pressing a button) I wondered if that what's causing the touchscreen not to respond.

I think you might be on to something here. I'm running the same rom and have recently gone 3 days without a lock, but today (Xmas day) I've had 3 lock ups. Thinking about it, each time there was some type of notification alert in the status bar, be it a text or calendar alert which I hadn't responded to at the exact time it was recieved.

[Guest targetbsp]

This would presumably be fairly easy to test by phoning or texting yourself from another phone? Would be good to have a definitive way to reproduce the problem. :(

Edited December 25, 2010 by targetbsp

[Guest dragon2611]

This would presumably be fairly easy to test by phoning or texting yourself from another phone? Would be good to have a definitive way to reproduce the problem. :(

It seems that it won't happen every-time, but most of the times I experience it seem to be when something else (I.e not me pressing the power button) woke the phone.

[Guest wbaw]

I bought a new (tft) Orange San Francisco less than a week ago. My touchscreen stopped responding yesterday on alpha3. At first it'd respond if I removed the battery cover, then that stopped working, then it'd work after a reboot (taking battery out), now it wont work at all. I went back to the stock Orange rom which I backed up before flashing & it still wont work, at all.

I'm going to take it back tomorrow.

I think it's a hardware problem, possibly something overheating. The back of the phone near the top got pretty warm, when I removed the battery cover there was some warm electronics smell.

My phone seems to be dead, unless anybody has any ideas?

Edited December 26, 2010 by wbaw

[Guest wbaw]

I've done some reading, it looks like it's a manufacturing defect that affects a small percentage of all phones with capacitive touch screens, maybe a slightly higher percentage in the blade due to it's lower cost.

Mine was fine for a few days, started to become unresponsive as people describe in this thread (fixed after a reset, then happened again after a random time), then totally died. I flashed back to stock firmware & the touch screen is still dead.

It seems to be a hardware problem.

Edited December 27, 2010 by wbaw

[Guest samjam]

I find that opera-mobile is very prone to jiggering touch-screen for itself only. Other apps will work, but opera mobile needs task-killing and restarting.

I've also had one wake-up with busted touch-screen and reboot is fine.

On my previous SF touchscreen was totally dead even after stock firmware and erase.

I think these were different problems with similar symptoms.

[Guest jurrasstoil]

If it would be in fact a hardware problem, why are there so few (none?) 2.1 lockscreen freeze reports and so many from people on 2.2?

[Guest Matty-p]

If it would be in fact a hardware problem, why are there so few (none?) 2.1 lockscreen freeze reports and so many from people on 2.2?

[/quo

yea i get it a couple of times a day on froyo but never on 2.1 or 2.3 its soft for sure maybe. 32 ?

[Guest isambard]

i have 2 phones, one on 2.2 and one on 2.1

i just got a freeze on the 2.2 after leaving a gmail notification untouched for a couple of hours. not sure if this is related.

also had a freeze on 2.1. which could have been triggered by overheating.

also noticed a freeze on 2.1 after switching between orientation lock several times.

[Guest wbaw]

If it would be in fact a hardware problem, why are there so few (none?) 2.1 lockscreen freeze reports and so many from people on 2.2?

Maybe more people on this forum have installed 2.2 rather than 2.1, I think it's what a lot of people came to this forum for, me included. I'd flashed to modaco 2.2 alpha3, but I flashed it back to the stock 2.1 once the touchscreen stopped working & it still didn't work.

It wasn't just the lockscreen that froze on mine, the touchscreen started acting weird while I was using it. Turning the screen off & on worked at first, then popping the battery cover off, then nothing would fix it.

I did a bit of searching on the net, it isn't just the blade that has these problems, a lot of nexus 1 users were reporting similar problems & users of other phones with capacitive touch screens too. Apparently the manufacturing tolerances need to be very tight for that kind of screen & sometimes there are defects that affect the accuracy of the screen, or whether it works at all.

Anyway, I just got an exchange at the Orange shop, my new phone works so far, I'm hoping it's just a few with problems.

If squeezing in certain places, popping the battery cover off & things like that have an effect & they seem to, I'd say it isn't a software problem.

Edited December 28, 2010 by wbaw