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 your device is not correctly detected in RAD Studio or in the system Device Manager, check the following: Ensure that your Android device is unlocked and not sleeping while connected via USB. Set the appropriate option in Settings or Developer Options. Make sure your Android device is enabled for USB debugging.
First, make sure that the Android ADB can "talk to" your device.
cd
) where ADB.exe is in, e.g, C:\Android\android-sdk\platform-tools.adb devices
If your device is listed (serial number is displayed), go to the second check. Otherwise, this means ADB currently can't talk to your device. There're many reasons which can cause the problem, try:
Second, make sure you set the "Deployment target selection mode" to manual:
Your device still can't display? Ok. Third, make sure your "Project Build Target" Android version is supported in your Device.
Also remember to set the 'Deployment target selection mode' to manual (Debug configurations -> target tab)
After following some of the steps in other answers here, as well as what is found here: ADB Driver for HTC Incredible, I had to issue two commands before my phone would show up.
adb kill-server
adb start-server
Finally, after those two commands would my device show up when I ran
adb devices
From time to time, the ADB process may get stuck (technical term there). When that happens, the above commands will not work. I have found that killing the ADB process (look in for adb.exe
in the Processes tab in Task Manager on Windows, or kill the PID for adb under linux), and then use
adb start-server
generally fixes that problem.
I think this was because the option for USB debugging wasn't checked on the device
This note from the Android Developer site is what worked for me:
Enable USB debugging on your device. On most devices running Android 3.2 or older, you can find the option under Settings > Applications > Development. On Android 4.0 and newer, it's in Settings > Developer options. Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
Using the Android SDK Manager may or may not actually install the Google USB Driver.
Following the steps here: http://developer.android.com/sdk/oem-usb.html#InstallingDriver allowed Eclipse to display the device.
If you select Android Application in the Debug As dialog, you should be able to attach the debugger to the device directly. Make sure you run adb devices on your shell and see your device listed. If not, you will need to re-install the driver for the device. You can uninstall the drivers you have using USBdeview and then download and re-install the drivers until you see the serial number for the device listed when you run adb devices. - Arunabh Das
None of the other answers worked for me. For me the device registered with eclipse after I rebooted the phone. Process for that is going to vary by phone model.
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
Windows 7
To install the Android USB driver on Windows 7 for the first time:
Connect your Android-powered device to your computer's USB port. Right-click on Computer from your desktop or Windows Explorer, and select Manage. Select Devices in the left pane. Locate and expand Other device in the right pane. Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard. Select Browse my computer for driver software and click Next. Click Browse and locate the USB driver folder. (The Google USB Driver is located in \extras\google\usb_driver.) Click Next to install the driver.
I had a similar problem...and my issue was related to using too high of an sdk....
I changed:
uses-sdk android:minSdkVersion="17" android:targetSdkVersion="17"/
to
uses-sdk android:minSdkVersion="8" android:targetSdkVersion="17"
and my problem was solved.
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.
I was facing the android device not showing in "device chooser" so I try my best but no avail, at least I found that ADB drivers should update, for this I did following steps 1. download driver from"http://forum.xda-developers.com/showthread.php?t=1161769" 2. Device Manager->> right click on ADB ->> update driver ->>browse path of downloaded drivers then OK update successful. and I found my android device in "Device Chooser" try and getting relax
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
Okay... so I could never get my PENDO pad to show up.. until I encountered this..
process android.process.acore has stopped..
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.
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.
In galaxy note 3 you need to enable the developer option. Access the "About Device" and click on the Build number multiple time until a message appear which telling you that the developer option has been enabled. Go back to general and there your go..the developer option has been enabled and select USB debugging option. This is for Galaxy note 3 N9005 Andriod 4.3.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With