How to resolve “Warning: debug info can be unavailable. Please close other application using ADB: Restart...

Multi tool use
Multi tool use












3















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










share|improve this question























  • I am not using eclipse on my machine at all

    – Zidane
    May 3 '16 at 11:56






  • 1





    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 3 '16 at 12:01











  • @Zidane did you solve it or not ?

    – user5248371
    May 3 '16 at 12:42
















3















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










share|improve this question























  • I am not using eclipse on my machine at all

    – Zidane
    May 3 '16 at 11:56






  • 1





    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 3 '16 at 12:01











  • @Zidane did you solve it or not ?

    – user5248371
    May 3 '16 at 12:42














3












3








3








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










share|improve this 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







android debugging android-studio runtime






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 3 '16 at 11:56









ZidaneZidane

4442721




4442721













  • I am not using eclipse on my machine at all

    – Zidane
    May 3 '16 at 11:56






  • 1





    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 3 '16 at 12:01











  • @Zidane did you solve it or not ?

    – user5248371
    May 3 '16 at 12:42



















  • I am not using eclipse on my machine at all

    – Zidane
    May 3 '16 at 11:56






  • 1





    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 3 '16 at 12:01











  • @Zidane did you solve it or not ?

    – user5248371
    May 3 '16 at 12:42

















I am not using eclipse on my machine at all

– Zidane
May 3 '16 at 11:56





I am not using eclipse on my machine at all

– Zidane
May 3 '16 at 11:56




1




1





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 3 '16 at 12:01





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 3 '16 at 12:01













@Zidane did you solve it or not ?

– user5248371
May 3 '16 at 12:42





@Zidane did you solve it or not ?

– user5248371
May 3 '16 at 12:42












7 Answers
7






active

oldest

votes


















1














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.






share|improve this answer

































    7














    It's an old question but I faced the same issue now. Following steps resolved my issue:




    1. Disconnect the device.


    2. Restart android studio.


    3. Run the project.








    share|improve this answer


























    • Even restarting system did not worked... but, this trick worked ;)

      – jeet.chanchawat
      Apr 20 '18 at 7:16



















    2














    I think OP may have already moved past this, but nonetheless what worked for me was to disable and re-enable usb debugging on the device.






    share|improve this answer































      0














      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





      share|improve this answer
























      • 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 3 '16 at 12:10











      • @Zidane in the terminal.

        – user5248371
        May 3 '16 at 12:10











      • yes that is the error I get in the terminal

        – Zidane
        May 3 '16 at 12:16











      • @Zidane if you run this two command then starting adb with no error.

        – user5248371
        May 3 '16 at 12:18











      • I get that same error in the terminal do you have any other suggestions

        – Zidane
        May 3 '16 at 14:11



















      0














      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






      share|improve this answer































        0














        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.






        share|improve this answer































          0















          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.



          enter image description here






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f37003481%2fhow-to-resolve-warning-debug-info-can-be-unavailable-please-close-other-appli%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            7 Answers
            7






            active

            oldest

            votes








            7 Answers
            7






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            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.






            share|improve this answer






























              1














              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.






              share|improve this answer




























                1












                1








                1







                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.






                share|improve this answer















                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.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 20 '18 at 8:42

























                answered Dec 20 '18 at 6:43









                sakshamsaksham

                914914




                914914

























                    7














                    It's an old question but I faced the same issue now. Following steps resolved my issue:




                    1. Disconnect the device.


                    2. Restart android studio.


                    3. Run the project.








                    share|improve this answer


























                    • Even restarting system did not worked... but, this trick worked ;)

                      – jeet.chanchawat
                      Apr 20 '18 at 7:16
















                    7














                    It's an old question but I faced the same issue now. Following steps resolved my issue:




                    1. Disconnect the device.


                    2. Restart android studio.


                    3. Run the project.








                    share|improve this answer


























                    • Even restarting system did not worked... but, this trick worked ;)

                      – jeet.chanchawat
                      Apr 20 '18 at 7:16














                    7












                    7








                    7







                    It's an old question but I faced the same issue now. Following steps resolved my issue:




                    1. Disconnect the device.


                    2. Restart android studio.


                    3. Run the project.








                    share|improve this answer















                    It's an old question but I faced the same issue now. Following steps resolved my issue:




                    1. Disconnect the device.


                    2. Restart android studio.


                    3. Run the project.









                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Feb 13 '18 at 17:52









                    Rick

                    75411322




                    75411322










                    answered Feb 13 '18 at 15:24









                    Sachin TomarSachin Tomar

                    7114




                    7114













                    • Even restarting system did not worked... but, this trick worked ;)

                      – jeet.chanchawat
                      Apr 20 '18 at 7:16



















                    • Even restarting system did not worked... but, this trick worked ;)

                      – jeet.chanchawat
                      Apr 20 '18 at 7:16

















                    Even restarting system did not worked... but, this trick worked ;)

                    – jeet.chanchawat
                    Apr 20 '18 at 7:16





                    Even restarting system did not worked... but, this trick worked ;)

                    – jeet.chanchawat
                    Apr 20 '18 at 7:16











                    2














                    I think OP may have already moved past this, but nonetheless what worked for me was to disable and re-enable usb debugging on the device.






                    share|improve this answer




























                      2














                      I think OP may have already moved past this, but nonetheless what worked for me was to disable and re-enable usb debugging on the device.






                      share|improve this answer


























                        2












                        2








                        2







                        I think OP may have already moved past this, but nonetheless what worked for me was to disable and re-enable usb debugging on the device.






                        share|improve this answer













                        I think OP may have already moved past this, but nonetheless what worked for me was to disable and re-enable usb debugging on the device.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Feb 12 '18 at 7:05









                        humblerookiehumblerookie

                        2,95621334




                        2,95621334























                            0














                            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





                            share|improve this answer
























                            • 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 3 '16 at 12:10











                            • @Zidane in the terminal.

                              – user5248371
                              May 3 '16 at 12:10











                            • yes that is the error I get in the terminal

                              – Zidane
                              May 3 '16 at 12:16











                            • @Zidane if you run this two command then starting adb with no error.

                              – user5248371
                              May 3 '16 at 12:18











                            • I get that same error in the terminal do you have any other suggestions

                              – Zidane
                              May 3 '16 at 14:11
















                            0














                            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





                            share|improve this answer
























                            • 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 3 '16 at 12:10











                            • @Zidane in the terminal.

                              – user5248371
                              May 3 '16 at 12:10











                            • yes that is the error I get in the terminal

                              – Zidane
                              May 3 '16 at 12:16











                            • @Zidane if you run this two command then starting adb with no error.

                              – user5248371
                              May 3 '16 at 12:18











                            • I get that same error in the terminal do you have any other suggestions

                              – Zidane
                              May 3 '16 at 14:11














                            0












                            0








                            0







                            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





                            share|improve this answer













                            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






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered May 3 '16 at 12:01







                            user5248371




















                            • 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 3 '16 at 12:10











                            • @Zidane in the terminal.

                              – user5248371
                              May 3 '16 at 12:10











                            • yes that is the error I get in the terminal

                              – Zidane
                              May 3 '16 at 12:16











                            • @Zidane if you run this two command then starting adb with no error.

                              – user5248371
                              May 3 '16 at 12:18











                            • I get that same error in the terminal do you have any other suggestions

                              – Zidane
                              May 3 '16 at 14:11



















                            • 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 3 '16 at 12:10











                            • @Zidane in the terminal.

                              – user5248371
                              May 3 '16 at 12:10











                            • yes that is the error I get in the terminal

                              – Zidane
                              May 3 '16 at 12:16











                            • @Zidane if you run this two command then starting adb with no error.

                              – user5248371
                              May 3 '16 at 12:18











                            • I get that same error in the terminal do you have any other suggestions

                              – Zidane
                              May 3 '16 at 14:11

















                            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 3 '16 at 12:10





                            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 3 '16 at 12:10













                            @Zidane in the terminal.

                            – user5248371
                            May 3 '16 at 12:10





                            @Zidane in the terminal.

                            – user5248371
                            May 3 '16 at 12:10













                            yes that is the error I get in the terminal

                            – Zidane
                            May 3 '16 at 12:16





                            yes that is the error I get in the terminal

                            – Zidane
                            May 3 '16 at 12:16













                            @Zidane if you run this two command then starting adb with no error.

                            – user5248371
                            May 3 '16 at 12:18





                            @Zidane if you run this two command then starting adb with no error.

                            – user5248371
                            May 3 '16 at 12:18













                            I get that same error in the terminal do you have any other suggestions

                            – Zidane
                            May 3 '16 at 14:11





                            I get that same error in the terminal do you have any other suggestions

                            – Zidane
                            May 3 '16 at 14:11











                            0














                            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






                            share|improve this answer




























                              0














                              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






                              share|improve this answer


























                                0












                                0








                                0







                                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






                                share|improve this answer













                                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







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered May 4 '16 at 14:34









                                ZidaneZidane

                                4442721




                                4442721























                                    0














                                    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.






                                    share|improve this answer




























                                      0














                                      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.






                                      share|improve this answer


























                                        0












                                        0








                                        0







                                        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.






                                        share|improve this answer













                                        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.







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Feb 16 '18 at 6:29









                                        VaibhavBhosaleVaibhavBhosale

                                        7914




                                        7914























                                            0















                                            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.



                                            enter image description here






                                            share|improve this answer




























                                              0















                                              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.



                                              enter image description here






                                              share|improve this answer


























                                                0












                                                0








                                                0








                                                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.



                                                enter image description here






                                                share|improve this answer














                                                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.



                                                enter image description here







                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered Jan 1 at 12:04









                                                Jin WangJin Wang

                                                8113




                                                8113






























                                                    draft saved

                                                    draft discarded




















































                                                    Thanks for contributing an answer to Stack Overflow!


                                                    • Please be sure to answer the question. Provide details and share your research!

                                                    But avoid



                                                    • Asking for help, clarification, or responding to other answers.

                                                    • Making statements based on opinion; back them up with references or personal experience.


                                                    To learn more, see our tips on writing great answers.




                                                    draft saved


                                                    draft discarded














                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f37003481%2fhow-to-resolve-warning-debug-info-can-be-unavailable-please-close-other-appli%23new-answer', 'question_page');
                                                    }
                                                    );

                                                    Post as a guest















                                                    Required, but never shown





















































                                                    Required, but never shown














                                                    Required, but never shown












                                                    Required, but never shown







                                                    Required, but never shown

































                                                    Required, but never shown














                                                    Required, but never shown












                                                    Required, but never shown







                                                    Required, but never shown







                                                    EG,5uMi4Bcxc,m,vj0ZWvvIE6yGm7qOY7gfTWVVUXHoVl6Nd0B lp GeP8p
                                                    SXYDrTviFiKNzyABznD,I3SlXXC,9kSafeTHh9vnT40mlOu

                                                    Popular posts from this blog

                                                    Monofisismo

                                                    Angular Downloading a file using contenturl with Basic Authentication

                                                    Olmecas