search

younglo / cyanogenmod4milestone

Automatically exported from code.google.com/p/cyanogenmod4milestone
0 stars 0 forks source link

Touch screen unusable #324

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Unknown

What is the expected output? What do you see instead?

N/A

What version of the product are you using?

0.04-10.12.22

Please provide any additional information below.

I updated my Milestone and for 5 days all has worked fine. This morning when 
using an app, my Milestone started "receiving" random touches and moving about 
randomly in the app. Switching to the hardward keyboard let me exit the 
application and get to the home screen. After a few seconds, an application was 
opened and it started receiving random touches also. I've rebooted the phone a 
couple of times and each time this behaviour reappears after a few seconds. 
Maybe it has something to do with the multitouch fixes. My phone is basically 
unusable at the moment.

Original issue reported on code.google.com by wtm...@gmail.com on 27 Dec 2010 at 12:23

GoogleCodeExporter commented 8 years ago 
USB/power adapter connected when the touch screen went crazy? If yes, then it's 
a long time known hardware issue (caused by unstable current/voltage provided 
to the Milestone's usb port). It has nothing to do with CM ROM nor the recent 
changes in it.

Original comment by kabal...@gmail.com on 27 Dec 2010 at 12:45

GoogleCodeExporter commented 8 years ago 
No, the power cord was not connected. I went back to the previous version but 
I'm still getting the same behaviour (I just tried writing an SMS but it 
suddenly started "ghost" touching random keys very fast - I have to put the 
phone in and out of standby to regain control temporarily). I guess maybe my 
Milestone is becoming defective. I'm going to wipe the system completely and 
retry it again.

Original comment by wtm...@gmail.com on 27 Dec 2010 at 1:03

GoogleCodeExporter commented 8 years ago 
OK, I've excluded the ROMs as the problem and have decided it's a hardware 
problem. Today I took the phone to the support center and they're sending it 
back to Motorola. So this non-issue is closed.

Original comment by wtm...@gmail.com on 28 Dec 2010 at 11:13

GoogleCodeExporter commented 8 years ago 
Thanks for the status update and sorry for your phone issues.

Original comment by kabal...@gmail.com on 29 Dec 2010 at 1:23