How to resolve "Warning: debug info can be unavailable. Please close other application using ADB: Restart ADB integration and try again"

Question

I am having a slight issue when trying to debug and android app via usb to external device. I keep getting the error "Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse Restart ADB integration and try again Waiting for process:"

I have tried stopping adb.exe in task manager , closing android studio and restarting , taking out the cable and putting it back and going to tools => android uncheck adb intergration then recheck it . All to no avail

Answer 1

adb kill-server

adb start-server

Reconnect your device

Rebluid the app on it

Answer 2

In Android Studio Version Electric Eel, I get this error. What worked for me:

1. enter command in terminal: adb kill-server

2. don't run any other commands

3. click on "Attach Debugger to Android Process button"

   

4. wait for "Waiting for ADB" dialog to finish

5. done! (but sometimes i have to repeat above steps 2-3 times)

---

1. if the issue still persists, unplug all devices and terminate all emulators

2. plug devices back in, and turn on emulators from the "cold boot now" option

   

3. and then try again from the beginning (adb kill-server)

Answer 3

There are few ways to recover adb debugging without restarting android device or machine,

1. try to restart adb connection (adb kill-server && start-server)
2. try to restart your modem device (Ethernet or Wifi)
3. try Disable and Enable again Developer option in your android device

When problem still not resolved, consider restarting your device

Answer 4

For me, it works when rebooting the macOS.

Answer 5

Just run command adb usb with connected device and try to debug again.

Answer 6

Quite awkward issue, I think none of the solutions mentioned above worked for me. Ultimately, I had to invalidate caches and restart.

File -> Invalidate caches... -> Select both options -> Invalidate and restart

Answer 7

The issue occurs when I open the Android Studio and IDEA together.

Restart the Android Studio does NOT fix the issue

Re-plugin the cable either does NOT fix the issue

Restart the Mac either does NOT fix the issue

Restart the ADB from terminal FIX the issue

adb kill-server 
adb start-server

In this way, you do not need to close the IDEA.

Updated: 2022-09-19

Restart the Android Studio does NOT fix the issue

Invalidate and Restart the Android Studio does NOT fix the issue

Re-plugin the cable either does NOT fix the issue

Restart the Mac either does NOT fix the issue

Restart the ADB from terminal either does NOT fix the issue

Restart the Android device fix the issue.

Answer 8

I resolved this issue by changing the Use USB for settings Go to setting select transfer settings in my case MIDI was selected.

Answer 9

Go to Airplane mode ON and OFF , After that everything back to normal.

Answer 10

IntelliJ IDEA (Ultimate, probably also Community) comes with Android plugin. If IntelliJ is started and any project is open and has been compiled (even without any Android code-base) then IntelliJ (apparently) steals the adb-connection from Android Studio. Either close IntelliJ or disable the Android plugin in IntelliJ.

If IntelliJ is open with android plugin, rebooting phone, killing adb etc. are only sporadic and short-time fixes of the problem as IntelliJ steals the adb connection again.

Answer 11

if you open two Android Studio at the same time (android studio preview),Will be like this

Answer 12

Following steps resolved this issue to me:

1. Disconnect the device.

2. Restart android studio.

3. Run the project.

Answer 13

What worked for me was to disable and re-enable USB debugging on the device.

Answer 14

Slightly different answer, but I'm including it for completeness.

For me Android Studio had frozen as well with the spinning beach ball of death.

1. I rebooted the emulator (by having it emulate a power-off/restart cycle)
2. Killed Android Studio (on a Mac by using ⌘⌥esc)
3. Restarted Android Studio.

After that everything was back to normal.

Answer 15

This problem sometimes occur when Android Studio is opened with another IntelliJ Editor. Just close the other IntelliJ Editor.

Answer 16

At times ADB caches a dead connection on device(real / virtual) due to which the port is busy and it is unable to establish a connection.

You can try different ways:

1. You can kill and restart the server:

   adb kill-server adb start-server

2). Try disconnecting the device(phone) and reconnecting it.

3). Restart your device (phone).

Answer 17

For me was Eclipse using DDMS and conflicting with Android Studio, I wasn't using, so I just uninstall it.

If is your case, go to Eclipse > Help > About Eclipse IDE > Installation Details > Select DDMS and Uninstall..

Answer 18

In my case, I had my device connected both via WiFi (with adb tcpip) and USB cable. Disconnecting the USB cable solved the issue.

Answer 19

Simply go to your Android phone developer settings, disable USB debugging, delete all authorizations for USB debugging and turn the debugging on again.

Answer 20

1. Open USB preferences in your device. Like the image below.

2. Click another option. (eg:File Transfer)

3. Click the no data transfer.

If it doesn't work,please try again.

The operations on the android devices are similar.

Answer 21

This is a problem of ADB connections as sometimes ADB cache a dead connection on your real/virtual device and due to which the port is busy and u cannot connect to it.

The simplest solution to this is RESTART your ANDROID phone that's it.

Answer 22

this may happen when you created two instances of android studio, or else you are using same device in multiple ADB programs, so simply disconnect you device and then open your desired android studio instance and then connect again. now it will work fine.

i also use same method and every time it works.

Answer 23

A possible temporary work around that may work prove useful for progress sake when intending to debug is to run the app in android studio , then immediately click on run => attach to debugger

Answer 24

First make sure you close any application use ADB , DDMS

like if you open Eclipse with android studio

Second restart your ADB from terminal

adb kill-server
adb start-server