I'm using Eclipse + ADT, and my physical device (listed below) is unlisted on Android Device Chooser. I have updated Eclipse and all of the Android packages. My phone is running Android OS 1.6, which corresponds to the target version listed in the Eclipse Project.
Also, the reason I decided to try testing on a real device is because the emulator doesn't seem to be working right anymore when I run my project. The emulator launches, but the program never does. Any ideas?
(using windows 7/t-mobile mytouch 3g)
If you have a samsung device you need to install a special driver for development:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Another alternative: on modern Apple iMac's, the USB port closest to the outside edge of the machine never works with ADB, whereas all others work fine. I've seen this on two different iMacs, possibly those are USB 1.0 ports (or something equally stupid) - or it's a general manufacturing defect.
Plugging USB cables (new, old, high quality or cheap) into all other USB ports works fine, but plugging into that one fails ADB
NB: plugging into that port works for file-transfer, etc - it's only ADB that breaks.
Okay... so I could never get my PENDO pad to show up.. until I encountered this..
Yeah.. nothing to do with this issue right? Ah ah but it lead me to MOBILEGO. It's a desk application that lets you admin your device.. Guess how.. by connecting via USB. Yep and it does.. It installed everything on my windows box, and now Eclipse has no problem seeing my PENDO.
I'm very late here, but if it helps someone... be sure you don´t have a conflict with your USB mode when attaching the cable. I pick "Only charge" (sorry if it's not exact, I have an Spanish terminal) but sometimes it changes to share net and the device dissapears from the list when running an app.
My problem was with an old ZTE phone, I was ignoring the autorun.exe that kept popping up when I plugged in the phone. I finally ran the autorun software it installed ZTE drivers and the phone started showing up in adb devices.
I had a similar problem...and my issue was related to using too high of an sdk....
I changed:
to
and my problem was solved.