Android Device Chooser - My Device Seems Offline

Android device chooser - My device seems offline

I've seen this happen a few times on my HTC Desire. I've never figured out whether the problem is in adb or the device but I usually do the following:

• Restart adb by issuing 'adb kill-server' followed by 'adb start-server' at a cmd prompt
• Disable and re-enable USB debugging on the phone
• Rebooting the phone if it still doesn't work.

99% of my issues have been resolved with these steps.

Android device chooser - My device seems offline

I've seen this happen a few times on my HTC Desire. I've never figured out whether the problem is in adb or the device but I usually do the following:

• Restart adb by issuing 'adb kill-server' followed by 'adb start-server' at a cmd prompt
• Disable and re-enable USB debugging on the phone
• Rebooting the phone if it still doesn't work.

99% of my issues have been resolved with these steps.

Android device does not show up in Android Device Chooser, but is listed in adb

Eerily similar to what I just spent the last hour figuring out. OS X, Nexus 5, shows up in adb devices, tried everything under the sun.

In my case, it turned out that even though the device wasn't listed, I was able to press the OK button and it launched just fine. (seen below)

I'm not sure if it also helped, but before I stumbled upon that solution, I edited my Launch config options to change from "Always prompt to pick device" to "Launch on all compatible devices/AVS'S" and selected the "Active Devices" options. I ran that and it worked! I expected the device to start showing up in the above menu afterwards, but it didn't. Then I realized it didn't matter and I could hit OK and it would build. Go figure.

Android ADB device offline, can't issue commands

I just got the same problem today after my Nexus 7 and Galaxy Nexus were updated to Android 4.2.2.

The thing that fixed it for me was to upgrade the SDK platform-tools to r16.0.1. For me, this version was not displayed in my SDK Manager, so I pulled it down from http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip directly.

You then need to rename the platform-tools directory and unzip it to android-sdk-windows/platform-tools. Using the SDK Manager, I had also updated to the latest sdk-tools before this.

If your whole Eclipse and ADT are ancient, you may need to update them as well, but I didn't need to.

Note: you may need to run SDK Manager twice (once to update itself) before you will see the latest packages.

Why is Eclipse's Android Device Chooser not showing my Android device?

I just had the same issue with the Motorola Droid. I had 3 devices and only 1 was detected in the ADB. The one that worked showed up in device manager as "android adb composite interface" and the 2 that did not work showed up as "android adb interface". In Windows 7 I did the following.

1. Right Click Computer then Manage
2. Expand Android phone at the top of the list
3. Right click Android ADB Interface then Update Driver Software
4. Browse my computer for driver software
5. Let me pick from a list of device drivers on my computer
6. Choose USB Composite Device then next

If USB Composite Device doesn't show up then try browsing to the usb_driver folder in your android sdk directory for step 5 then try step 5 and 6 again.

Note : If Android does not appear at the top of this list as described in #2 and/or you find a device ADB with no drivers then you probably need to install the device driver, which in my case (HTC Glacier) was located right on my phone.

Android Device Window Chooser not working after updating device

Ok open sdk manager /sdk/tools/android now download the sdk for your new android version. In my case it was API 17. Once its done you should be ready.

If you still got some issue be sure that you have the last version of the ADT installed. Installing it again http://developer.android.com/sdk/installing/installing-adt.html

Now you should be ready to go.

---

Related Topics