adb logcat hangs with "waiting for device" message

When I type adb devices command on terminal, it shows device is connected

List of devices attached

0123456789ABCDEF device

But when I type adb logcat command, it hangs with below message

waiting for device

Can anybody tell me what is the problem behind this? I test the device on cts.

Answers


I am not pretty much sure if this works for you but can you please try the steps below:

# Kill and restart      
$ adb kill-server      
$ adb start-server     
 daemon not running. starting it now *      
 daemon started successfully *         

# Device appears, but is listed as offline

$ adb devices      
$ adb logcat

I have also experienced similar problems I think I solved it by having the USB debugging option switched on within Developer Options in Settings.

REPEAT The following steps above, it should work!


I had this same problem on Ubuntu 12.04. Thankfully MickeyMicro had the solution that worked for me:

  1. Run the command: gksudo gedit /etc/udev/rules.d/51-android.rules

  2. Add the following line to the blank file

SUBSYSTEM=="usb", ATTR{idVendor}="2080", MODE="0666" (I used this one on 12.04)

SUBSYSTEM=="usb", SYSFS{idVendor}="2080", MODE="0666" (Another recommended for 10.04)

  1. Save and close gedit.

  2. Run the command: sudo chmod a+rx /etc/udev/rules.d/51-android.rules

  3. Restart the system.

  4. Run the command: sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"

  5. Verify that you have permissions to access the device. adb devices should return normal response, rather than a "???????????? no permissions" message.

http://forum.cyanogenmod.com/topic/23163-need-help-for-adb-connection-on-ubuntu/


When I have experienced this infinite "waiting for device" on Windows I had simply forgotten to enable usb-debugging in the developer options of my device.


Here is yet another potential method to solve this -- in the past, the above solutions will work, but in my case, this time, this was the thing that fixed it:

  1. Plug device into USB
  2. Settings -> Developer Options
  3. Revoke USB Debugging Authorization
  4. Unplug Device
  5. Repeat Step 1
  6. Authorize Device
  7. Repeat Steps 4&5

adb devices should now show device

adb logcat should now output logs from device


What OS are you using? It can be a variety of different reasons. Did you make sure you only have either the emulator running or a device attached? If so, you can direct your adb command by using the -d or the -e flag.


I got Nexus tab today and I had to go to Settings -> About Tablet -> (tap 7 or 8 times) on Build Number.

Then 'Developer Options' showed up above 'About Tablet'.

Next in Developer Options, after enabling USB Debugging I was able to get the logs

For Mac Users:

cd /Applications/Android/sdk/platform-tools

./adb logcat


I had similar problem on Galaxy S3, with adb running on Ubuntu 11.10 OS. In my case, If I reconnect the device (pull the USB connection and reconnect it), the log cat starts working. This happens only for the first time I connect the device after powering it up. Once logcat starts working, then it continues to work smoothly, without needing to reconnect.


This happend to me on OS X mountain lion. To fix it I had to open Activity Monitor, filter all processes named "adb" and force quit them (I had 3 running). Then reconnect the device and everything was working again.


On my Samsung Galaxy S4 I had the same problem but after 10-20 seconds a dialog pops up on the phone where I have to accept the debug request


I had a similar problem, but for different reasons. My issue came from programing usb accessory on android, which changes the vid/pid when in accessory mode. The solution for me that worked was the following:

  1. Connect the phone
  2. Run the usb host side accessory mode commands (Example website: http://android.serverbox.ch/?p=262 )
  3. Phone should have reconnected in accessory mode (Ensure the PID has adb: 0x2D01)
  4. adb kill-server
  5. sudo adb start-server (This caused the phone to re-ask auth permission)
  6. adb logcat (In my case I wanted to watch the logs, this now worked in accessory mode)

In my case, I was using an old version of adb, make sure you have the latest version of adb. You can download here, extract and run straight within the folder ./adb.


Please go to the developer options on the phone and click "Revoke USB debugging authorization"

Enable it again and try to get the logs. This is basically waiting for the device to get connected. Make sure to authorize USB access from device as well.


Need Your Help

Mocking in Swift

unit-testing mocking swift

How do you mock an object in Swift?

ERROR: 'rake/rdoctask' is obsolete and no longer supported. Use 'rdoc/task' (available in RDoc 2.4.2+) instead

ruby-on-rails ruby-on-rails-3.2

Seems the last post for this problem was closed for one reason or another so I'll try my luck...