Erratic touch screen?

Quote:

---

Originally Posted by BuckyN8

I have the same problem but only when it is plugged in. I am assuming you have yours plugged in since it only happens at night.

---

same here.....actually tried a generic charger from walmart to use at work and it flat out locked up my phone, though it would charge the phone. I returned the walmart charger and bought an "extra" charger from verizon with the 9 ft cord to use at home, so I can talk while charging and keep the factory charger at the fire station to use at night. Sometimes the keys get erratic while using the verizon charger, but I've found that if I unplug the phone and plug it back in, it resolves the erratic key behavior.

I am having a similar issue to yours except It happens at random times during the day none of which are when it is charging, I have had the bionic for three days now and it had started happening the morning after I bought it, I charged it the night before using the charging dock that comes with the extra battery. Most of the time what happens is the notification bar at the top will start to pull down on its own and the screen will be unresponsive to any touching. I had the same issue with my previous droid which was the original but that was much more extreme as it would go to webpages, download files, make calls, store contacts, and even send texts all on its own. Never saw anything like it that is why I ended up buying a new phone and now im scared the same thing is happening. Is this a common problem droids?

I have the same issue with my DROID3. It only acts up when its plugged into the charger, and only on the lock screen....
I'm using the charger that came with the phone.
Is it a Moto issue? Doesn't bother me too much....just adding my 2 pennies...

Edit: It only does it when fully charged and plugged in.

Sent from my DROID3 using DroidForums

Must be a Moto issue. This was the entire reason I got a new Bionic. I had to unplug my phone from the charger if I ever wanted to text. And it still happens so this must be a software issue on Motorola's part.