I am developing an Android app on Windows, and have successfully loaded it on probably 10-12 different phone models now. Each time I have used the Android win-usb driver supplied with the SDK<http://developer.android.com/sdk/win-usb.html>. In fact, I have had great success using it even with phones that are not listed as applicable devices.
For the first time, I have run into trouble, and strangely, it is with the T-Moblie myTouch -- which *is* listed as one of the supported devices. Windows installs the diver fine -- just as with the other phones I have used -- but something is not right. ADB does not recognize the device when connected -- "adb devices" returns nothing (no devices connected). One bit of information that is probably useful is that Device Manager lists the myTouch as "Android Phone >> Android ADB Interface", whereas with the phones that work, they instead list as "ADB Interface >> Mot Composite ADB Interface" (Motorola Droid, for example). The driver install process appeared to go exactly the same as with all other phones. I guess I can try going and getting the myTouch custom driver from T-Mobile, but I hate just trying things without some understanding of what is going on -- especially since in this case, as I said, documentation says the myTouch is supposed to work with the Google driver in the SDK. I've done quite a bit of searching for this issue, and found many posts that seem closely related to what I'm experiencing, but nothing that recommends something I haven't tried already. Anyone know how to fix this? Thanks, Andrew -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
