No debuggable processes in logcat when phone detected by Android studio

AndroidDebuggingAndroid StudioSamsung Mobile

Android Problem Overview


Everyone!

I got so confused by android studio. when I plug in my phone to debug apps, logcat can detect my phone, but I can not choose process. It said "no debuggable processes",not common "no debuggable applications".

My phone is samsung s5 (android 6.0),rooted.

Any ideas?

Thanks!

Android Solutions


Solution 1 - Android

I had a similar issue, when I was building an app, I could select the device in Logcat, but not the process. (same message, "No Debuggable Processes")

The reason: I was building my app in release, then, when I changed the build variants to debug, I was able to select the process.

Solution 2 - Android

You need to enable adb integration, just go to Tools-->Android-->Check Enable ADB Integration

It was a default feature a few versions ago but now it's disabled by default

Solution 3 - Android

In my case, using Android Studio 3.1.3, I had to enable "Use libusb backend" checkbox at File-->Settings-->Build, Execution, Deployment-->Debugger

Solution 4 - Android

This happens time to time, try these three options in any order:

  1. Restart Android Studio ( preferably with invalidated caches as well )
  2. Restart your phone
  3. Deactivate and reactivate usb debugging

Solution 5 - Android

one of the reasons is that your application is marked as not debuggable in the build.gradle file

buildTypes{
    release{
        debuggable false
    }
}

another reason maybe you did not allow ADB integration. You should have Tools->Android->Enable ADB Integration active

Solution 6 - Android

if you set minifyenabled to true you can be face with this error. So if you run your app release or debug then be sure that minifyenabled is false.

Solution 7 - Android

Open terminal window at botton ba.. type
adb kill-server adb start_server

Solution 8 - Android

  1. Android Studio -> Preferences -> Build, Exception, Deployment -> Debugger -> check "Use libusb backend" -> Apply -> OK
  2. Android Studio -> Preferences -> Build, Exception, Deployment -> Debugger -> uncheck "Use libusb backend" -> Apply -> OK
  3. oh, it's just work now ... (my android studio version is 4.1)

Solution 9 - Android

I finally found that I was running a release version of the App. So foolish...

Solution 10 - Android

Maybe you have recently launched Android Device Monitor which might have prompted you to disable ADB integration. Usually, when you exit the Android Device Monitor, ABD integration is automatically re-enabled. But sometimes it isn't, so please check Tools/Android/Enable ADB Integration

Solution 11 - Android

You wouldn't believe but this is really simple, took me long to find it out, but u don't need any solution here, actually there is nothing wrong, just:

  1. Right click your MainActivity class, (or whatever you name it)
  2. Click on Run "MainActivity"
  3. Solved!

I think this happens when updating the gradle, at least for me. Hope works for anyone looking around. (Sorry for my english)

Solution 12 - Android

Click the "Bug" icon and that did the trick.

Solution 13 - Android

Solution 14 - Android

1. Open Edit Configurations:

enter image description here

2. Check the boxes:

enter image description here

Solution 15 - Android

You need to download usb drivers for your phone (in this case as I see, it is a samsung s5). The link to its drivers is this one:

http://samsungusbdriver.com/download/samsung-driver-v1-5-61-0

When you are there, follow the steps when downloaded and your phone will be recognised. Hope I could help ;).

Solution 16 - Android

If all does not work then try checking your manifest file, set:

android:debuggable="true".

Solution 17 - Android

Maybe U can reboot your PC/Mac. It works for me.

Solution 18 - Android

This may be the case, when you change cable with new one, then Restart is required for Android Studio. It will prompt USB debugging again.

Solution 19 - Android

Unplugged the test device from USB and plugged it back in, that did it for me. Restarting Android Studio had no effect.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionkimichangView Question on Stackoverflow
Solution 1 - AndroidLoïc DumasView Answer on Stackoverflow
Solution 2 - AndroidZincView Answer on Stackoverflow
Solution 3 - Androiduser3138806View Answer on Stackoverflow
Solution 4 - AndroidkoperkoView Answer on Stackoverflow
Solution 5 - AndroidKhalid TahaView Answer on Stackoverflow
Solution 6 - AndroidaligurView Answer on Stackoverflow
Solution 7 - AndroidMarco Aurelio SilvaView Answer on Stackoverflow
Solution 8 - AndroidMichael MaoView Answer on Stackoverflow
Solution 9 - Androidcivic.LiListerView Answer on Stackoverflow
Solution 10 - AndroidMarkView Answer on Stackoverflow
Solution 11 - AndroidJuan Pedro GoicocheaView Answer on Stackoverflow
Solution 12 - AndroidthatzpremView Answer on Stackoverflow
Solution 13 - AndroidYasser JEView Answer on Stackoverflow
Solution 14 - AndroidВладислав ШестернинView Answer on Stackoverflow
Solution 15 - AndroidDzefersonSView Answer on Stackoverflow
Solution 16 - AndroidRahul JainView Answer on Stackoverflow
Solution 17 - AndroidScott WangView Answer on Stackoverflow
Solution 18 - AndroidAks4125View Answer on Stackoverflow
Solution 19 - Androidtariq101View Answer on Stackoverflow