This occasionally happens to me on both my G1 and my Ion. I think its related to the data pins not contacting competely. Usually the old NES trick (blow in the cartridge) works for me. A quick little blow in both the USB connectors and it works like new. Unfortunately, I think there is a chance that constantly plugging in and removing the USB can rather quickly damage the port.
On Jul 13, 6:56 pm, Richard Schilling <[email protected]> wrote: > I'm doing a lot of G1 development these days, and I'm seeing a problem > others have talked about but there seems to be no consistent answer. > > I have multiple G1 phones. Same model, manufacturer, etc... > > One of them connects to the computer, is recognized by adb, etc. just > fine. Works like a charm. > > The second phone isn't recognized by adb at all. > > The two phones are setup identically. > > In fact, I have an application running on both phones that detects > changes in battery state. The phone that connects to the computer > just fine also captures the battery states for being plugged in and > unplugged just fine. > > The phone that doesn't get recognized doesn't get the battery events > at all - not when it's plugged in to the USB port, nor when it's > plugged into the wall charger. > > Any help on troubleshooting the phone that won't connect would be > appreciated. > > A factory reset seems to not help. > > Thanks. > > Richard Schilling > Root Wireless --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
