Thanks a-wjf. Switching device driver to USB Composite Device worked like a charm.
Kostya, I've never seen that menu and on both 2.1 and 2.2 the Droid only allows for mounting and unmounting from that menu. But, your screenshots are sweet and I'd like your menu instead of mine. On Aug 19, 1:28 pm, authorwjf <[email protected]> wrote: > Like you I had similar problems getting my Motroloa DROID to show up > as a device in Android Device Chooser dialog under Eclipse. I am > running the 32-bit version of Windows 7. I found a number of forums > that tried to address this issue, but no one seemed exactly sure what > was happening, and a number of the sites suggested re-installing > Windows. > > It just so happens that prior to doing Android development I wrote > device drivers for Windows. So I am at a bit of an advantage here. USB > drivers can be touchy, but you shouldn't have to re-install your OS > and the idea of a "driver boost" app from a third party makes me > shudder. More than likely what is happening is the OS has associated > your DROID with the generic driver that comes with the Windows Android > SDK. > > You can verify this by bringing up the Windows Device Manager. If in > your root node you see, ANDROID PHONE instead of ADB INTERFACE, this > post should solve your problem. Obviously, if you have not already > gone out to the Motorola website and downloaded the 32 or 64 bit > drivers for the DROID, this needs to be your first step. > > After you run the MSI you downloaded from Motorola, reboot your > machine, bring up your old friend the device manager again, and > reconnect your DROID. As mentioned in other posts on this thread, you > need to have the USB debugging turned on from the DROID's application > menu. > > Expand the ANDROID PHONE node, right click, and choose UPDATE DRIVER > SOFTWARE. You will be presented with two options, the one you want is > BROWSE MY COMPUTER FOR DRIVER SOFTWARE. When the next dialog comes up, > select LET ME PICK FROM A LIST OF DEVICE DRIVERS ON MY COMPUTER. > > As long as you have the SHOW COMPATIBLE HARDWARE box checked, you > should see a couple options. Ideally, you are looking for MOT > COMPOSITE ADB INTERFACE. However, in some cases only ANDROID COMPOSITE > ADB INTERFACE shows up. This *should* work as well. The one thing you > don't want is the generic ANDROID ADB INTERFACE, which seems to be the > default (thus the problem to begin with). > > Click NEXT and the driver will install. Its possible at this point (in > fact likely), Windows will force you to do a reboot. Once that is > complete you should be good to go. Hope this was helpful! -- 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
