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

Back when I used eclipse, it happened for me all the time. the only solution for me was restarting computer, put cable in, start eclipse, in that exact order. — Mohammad Zarei, May 03 '16 at 12:01

saksham · Accepted Answer · 2018-12-20T08:42:26.850

136

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.

edited Dec 20 '18 at 08:42

answered Dec 20 '18 at 06:43

saksham

3,173
1
21
23

15

Disconnecting the phone from the cable worked as well. – sud007 Feb 27 '20 at 12:09
sud007 Not needed. May have worked for you but different people face this problem under different circumstances. Some phones stop their ports in use when cable is detached but not all. – saksham Mar 02 '20 at 08:39
1

I do not understand "not needed" as your forced opinion. However, different people have different problems is a correct one. And for the record, there is no specific problem hence, this is just a workaround and not a Solution. – sud007 Mar 02 '20 at 09:01
sud007 not needed means no need to disconnect the cable if you work according the above way around. It will work for all phones – saksham Mar 02 '20 at 09:41
1

i had my device connected over the wifi and adb tcpip 5555 < restarted the connection for me and it worked – Bawa Dec 17 '20 at 18:36
Device restart solution workded. Thanks @Saksham – umesh Jun 17 '22 at 11:53
Thanks, Bawa! I'm also debugging over wifi, and this is much nicer than restarting the phone or the IDE. – ctd Oct 25 '22 at 21:53
I restarted my device and it did not work – John Glen Jan 15 '23 at 00:36
Device restart is too much. Disable and re-enable USB debugging on the device is enough – santilod Jul 06 '23 at 00:11
1

@sud007 Thanks! I have two PC. One notebook was already connected to the Android phone by USB cable. When trying to connect the phone on another PC via WiFi, the warning appears. Finally unplugged cable works. – Weekend Aug 16 '23 at 09:11

score 47 · Answer 2 · edited Nov 10 '21 at 18:54

47

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

edited Nov 10 '21 at 18:54

Phil Dukhov

67,741
15
184
220

answered Feb 12 '18 at 07:05

humblerookie

4,717
4
25
40

4

Yes it worked by turn it OFF and turn it ON back in `Settings -> Developer Options -> USB Debugging` – Shailendra Madda May 17 '22 at 18:24
Tried this; did not work – John Glen Jan 15 '23 at 00:36

score 19 · Answer 3 · edited Nov 10 '21 at 18:55

19

Following steps resolved this issue to me:

Disconnect the device.
Restart android studio.
Run the project.

edited Nov 10 '21 at 18:55

Phil Dukhov

67,741
15
184
220

answered Feb 13 '18 at 15:24

Sachin Tomar

215
2
5

Even restarting system did not worked... but, this trick worked ;) – jeet.chanchawat Apr 20 '18 at 07:16
This worked. Step 2.1: connect your device while android studio restarts :) – Kishan Solanki Dec 26 '22 at 08:23

score 18 · Answer 4 · answered Mar 22 '19 at 10:36

18

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

answered Mar 22 '19 at 10:36

arenaq

2,304
2
24
31

Yes it worked by turn it OFF and turn it ON back in `Settings -> Developer Options -> USB Debugging` – Shailendra Madda May 17 '22 at 18:24

score 15 · Answer 5 · answered May 03 '16 at 12:01

15

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

answered May 03 '16 at 12:01

in my cmd and in my terminal I typed adb kill-server and I get 'adb' is not recognized as an internal or external command, operable program or batch file. – Zidane May 03 '16 at 12:10
@Zidane in the terminal. – May 03 '16 at 12:10
@Zidane if you run this two command then starting `adb` with no error. – May 03 '16 at 12:18
I get that same error in the terminal do you have any other suggestions – Zidane May 03 '16 at 14:11
@Zidane in /platform-tools try './adb kill-server' and './adb start-server' – peresisUser Jan 10 '17 at 09:16
@Zidane You must add adb to your environment variables path Check online for how to add environment variable based on your operating system – Bahaa KA Jun 20 '21 at 20:33

Francis Bacon · Answer 6 · 2022-09-19T03:46:35.370

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.

score 12 · Answer 7 · answered Jul 02 '21 at 14:39

12

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

answered Jul 02 '21 at 14:39

Wesley Campagna

131
1
3

After trying all other options, this was it. Closed IntelliJ IDEA CE and the problem was solved. Thanks! – Nino van Hooff Apr 08 '22 at 16:26

score 9 · Answer 8 · answered Jan 01 '19 at 12:04

9

Open USB preferences in your device. Like the image below.
Click another option. (eg:File Transfer)
Click the no data transfer.

If it doesn't work,please try again.

The operations on the android devices are similar.

answered Jan 01 '19 at 12:04

Jin Wang

671
6
8

score 9 · Answer 9 · answered Mar 10 '23 at 14:15

9

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

answered Mar 10 '23 at 14:15

Kapil Soni

119
1
8

score 6 · Answer 10 · answered Feb 16 '18 at 06:29

6

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.

answered Feb 16 '18 at 06:29

VaibhavBhosale

275
4
6

2

You're right, I have this problem while running Android Studio Canary along side the stable version. – AnT Dec 24 '20 at 05:59

score 6 · Answer 11 · answered Jan 19 '22 at 13:30

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.

That's brilliant of you to discover this!! This was my problem! Very helpful! — Oz Shabat, Mar 29 '22 at 14:38

score 4 · Answer 12 · answered Apr 20 '22 at 08:43

4

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

answered Apr 20 '22 at 08:43

bharat udasi

133
7

Worked for Android 12 by changing USB for File Transfer. – Pradeep Kumar May 02 '22 at 05:43

score 2 · Answer 13 · answered Jan 24 '22 at 07:16

2

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

answered Jan 24 '22 at 07:16

Hemant Bharti

116
6

score 2 · Answer 14 · answered May 24 '23 at 17:56

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

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

When problem still not resolved, consider restarting your device

score 1 · Answer 15 · answered Sep 23 '19 at 22:21

1

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

answered Sep 23 '19 at 22:21

Alain1405

2,259
2
21
40

score 1 · Answer 16 · answered Jan 23 '23 at 13:43

1

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

answered Jan 23 '23 at 13:43

Radzik

244
2
16

score 0 · Answer 17 · answered Mar 03 '21 at 17:37

0

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..

answered Mar 03 '21 at 17:37

Ronaldo

1
2

score 0 · Answer 18 · answered May 18 '21 at 13:24

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:

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).

score 0 · Answer 19 · answered Aug 20 '21 at 01:41

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.

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

After that everything was back to normal.

score 0 · Answer 20 · answered Nov 26 '21 at 03:20

0

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

answered Nov 26 '21 at 03:20

f2A

27
4

score 0 · Answer 21 · answered Mar 13 '23 at 10:09

0

For me, it works when rebooting the macOS.

answered Mar 13 '23 at 10:09

Francis Bacon

4,080
1
37
48

Eric · Answer 22 · 2023-03-29T15:02:12.003

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

enter command in terminal: adb kill-server
don't run any other commands
click on "Attach Debugger to Android Process button"
wait for "Waiting for ADB" dialog to finish
done!

if the issue persists:

unplug all devices and terminate all emulators
plug devices back in, and turn on emulators from the "cold boot now" option
and then try again from the beginning (adb kill-server)

score -1 · Answer 23 · answered May 04 '16 at 14:34

-1

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

answered May 04 '16 at 14:34

Zidane

1,696
3
21
35

The scenario you describe is where I encountered this problem. (It wasn't me who downvoted btw) – Chris Sep 16 '21 at 09:59

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

23 Answers23