I am having a slight consequence when trying to debug and android app via usb to external device. I keep getting the fault "Warning: debug info tin be unavailable. Delight close other application using ADB: Monitor, DDMS, Eclipse Restart ADB integration and endeavor over again Waiting for process:"

I have tried stopping adb.exe in task manager , endmost 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

asked May 3, 2016 at 11:56

3

This is a trouble of ADB connections as sometimes ADB enshroud a expressionless connection on your existent/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.

answered December 20, 2018 at vi:43

half-dozen

Following steps resolved this issue to me:

  1. Disconnect the device.

  2. Restart android studio.

  3. Run the projection.

answered February 13, 2018 at xv:24

i

Just go to your Android phone developer settings, disable USB debugging, delete all authorizations for USB debugging and plow the debugging on once more.

answered Mar 22, 2019 at 10:36

0

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

answered Feb 12, 2018 at seven:05

First make certain y'all close whatsoever application utilise ADB , DDMS

similar if you open Eclipse with android studio

Second restart your ADB from terminal 

                  adb kill-server adb kickoff-server

answered May 3, 2016 at 12:01

6

  1. Open up USB preferences in your device. Like the prototype below.

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

  3. Click the no data transfer.

If information technology doesn't work,please endeavour again.

The operations on the android devices are like.

enter image description here

answered Jan 1, 2019 at 12:04

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

answered Jul 2, 2021 at 14:39

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

i as well employ aforementioned method and every time information technology works.

answered Feb 16, 2018 at vi:29

1

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

answered Sep 23, 2019 at 22:21

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

answered Jan 24 at 7:16

For me was Eclipse using DDMS and alien with Android Studio, I wasn't using, and then I simply uninstall it.

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

answered Mar three, 2021 at 17:37

At times ADB caches a dead connectedness on device(existent / virtual) due to which the port is busy and it is unable to plant a connectedness.

You tin try different means:

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

answered May 18, 2021 at xiii:24

Slightly dissimilar reply, but I'm including it for completeness.

For me Android Studio had frozen every bit well with the spinning beach brawl of decease.

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

After that everything was back to normal.

answered Aug twenty, 2021 at ane:41

if yous open ii Android Studio at the same time (android studio preview),Will exist like this

answered Nov 26, 2021 at three:20

IntelliJ Idea (Ultimate, probably also Community) comes with Android plugin. If IntelliJ is started and any projection is open and has been compiled (even without whatever Android code-base) and then IntelliJ (apparently) steals the adb-connexion 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 simply sporadic and brusque-time fixes of the problem as IntelliJ steals the adb connection again.

answered Jan 19 at 13:30

A possible temporary piece of 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 4, 2016 at 14:34

one

Non the reply y'all're looking for? Browse other questions tagged android debugging android-studio runtime or ask your own question.