Android SDK does not recognize debug device

Question

I am new to Android development and I am trying to run a test application on my device itself. I followed the instructions http://developer.android.com/guide/developing/device.html (and related links), but Android Debug Bridge (adb) does not recognize the connected device.

Some quick reference information, I am running WinXP, developing with Eclipse, with a Motorola Droid with Android 2.1 as a physical device.

Overview of the steps I took:

• Installed the Android SDK by downloading all the necessary packages.
• USB debugging is enabled on my device.
• Connected device via USB, installing the driver from the SDK folder.

I will stop here (although I continued to configure the debugging application in Eclipse) because at that moment I noticed a problem.

Running "sdk \ tools \ adb devices" at this stage (at least in my opinion) should contain my device as connected. However, executing this value only gives:

A list of connected devices

My device recognizes that it is connected to the computer in debug mode, and my computer recognizes the device. However, I cannot get sdk to recognize it. I will leave all the steps that I used to configure Eclipse to debug on the device, as this does not seem to be a problem. I will turn them on if necessary.

If anyone has any ideas, I would really appreciate help. Thank you in advance for your time.

Answer 1

I am using HTC OneS. Eclipse on Ubuntu 12.04. I have USB debugging enabled. But after connecting it does not allow me to deploy. It was recognized as a device: ... no permissions

What I decided to solve was the resolution of the USB device. I found the answer here .

What I've done:

$ sudo vi /etc/udev/rules.d/51-android.rules 

I added these 2 lines to the rule file:

 SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0cec", MODE="0666" SUBSYSTEMS=="usb", SYSFS{product}=="Android Phone", MODE="0666" 

My device USB device: product "0bb4: 0cec". To find out, use the command> lsusb. Then I disconnect / reconnect the phone. It has been recognized.

Answer 2

When I had this problem, I realized that my USB connection for the phone was set to multimedia synchronization mode. When I switched it to mass storage, the hello world program loaded straight up. I did this by dragging the USB icon to the top toolbar of the phone’s home page.

Answer 3

What usually works for me:

• Disconnect device
• Run ./adb wait-for-device in terminal in your android-sdk platform tools
• Connect device
• Turn on device

Every time one of my devices doesn’t read, this seems to fix the problem.
An alternative is to repeat all of the above steps, but do not turn off the device (i.e., turn it off, run the command, turn it on).

If this does not work, another thing I found for older devices that I use (2.1 update 1 and 2.3) is to disconnect USB, disable USB debugging, return to usb debugging and reconnect.

Answer 4

I tried to get this to work on the Acer A500 with Eclipse on Windows 8 Pro. In the end, I found a solution through this link . I also had to follow the instructions on this link to allow the installation of an unsigned driver in Windows 8.

Answer 5

I use HTC, so it may be different, but for me I need to sync the device with a PC before it recognizes the phone. When it is ready, a message appears stating that the device is connected for debugging.

In addition, you need to mark your application as debugging, if you have not done so already, as described here

Answer 6

Assuming that the correct driver has been successfully installed (there is no exclamation mark on the driver icon in the device manager), check if the device provider identifier is specified in User \ .android \ adb_usb.ini.

Device Provider ID can be found at http://developer.android.com/tools/device.html

After adding a new provider ID, reconnect the device and restart adb

For more details see this adb topic without finding my device / phone (MacOS X)

Answer 7

Kal I had the same situation a few months ago, my device was recognized for my computer, but adb did not know that my device was connected, I had to update it from the device manager ... I hope this helps you!

Adb driver is notalling error

Answer 8

Make sure you have the Motorola USB driver as described in this thread .

Answer 9

Have you tried to kill the adb process and run it again? This has worked for me before.

Answer 10

I just purchased a new Android phone (LG) and also had some difficulties. It seems that my phone would disable debugging myself when I plugged it into a USB port.

My solution is to connect the phone and THEN enable debugging.

Answer 11

When adb stops recognizing my device on Windows, it is usually fixed using the adb kill-server / start-server trick. But this time nothing made it work, each time I repeated every answer to this stream (restart, reconnect, reinstall, everything) ... Then I tried to connect the device to another USB port, and everything worked again.

Answer 12

sometimes kills and restarts adb to fix this:

in console:

 adb kill-server adb start-server 

(Remember to add the sdk platform-tools folder in PATH )

Answer 13

I followed the steps suggested by Neil Khan, but adb still could not recognize my tablet (a cheap Chinese device - Freelander PD10).

to solve this problem for me was restarting adb as root:

 adb kill-server sudo adb start-server 

Answer 14

Put the phone in mass storage mode. It took me a day and a half.

Answer 15

You can try to install USB drivers for devices from the official website:

• Google usb
• OEM USB

Answer 16

That's right if I'm wrong, but clearing the lint from the USB port seems to work for some people. Here is a video on how to do this.

http://www.youtube.com/watch?v=R6p0Eg-yq3A

edit: Connection performance seems to be improved. A device is recognized using the -devices command if it swings up and is supported in this position. So far, the connection to the charger works great.

Answer 17

I have this problem with my Sony Experia L , the problem was in my Windows firewall, I just change some Inbound and Outbound parameters (setting up the preliminary firewall) for abd.exe (emulator) and the problem was fixed. Do this and reset your emulator. Hope this helps you.

Answer 18

None of these solutions worked for me!

The device driver did not install properly, and I had to restart the computer while holding F8 and disabling forced device signatures.

Answer 19

type in chrome:

 chrome://inspect 

All your connected devices will be listed. If the debugging session was not enabled, a confirmation dialog should appear on your device. Accept it.

It worked for me.