androiddebuggingandroid-studiosamsung-mobile

Reputation: 961

No debuggable processes in logcat when phone detected by Android studio

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!

Upvotes: 85

Answers (23)

Victor Choy

Reputation: 4246

My case is not like other's answers.

I just click Remove from sidebar on tab by right click.

Then enable it in View -> Tool window -> Profiler.

Upvotes: 0

Rakesh Jha

Reputation: 379

To Solve this issue.

Restart you Android Studio.
Your Application should be in debug mode.
Device should be connected.

Upvotes: 0

Mahmoud Aly

Reputation: 751

In case of a debuggable app that has stopped logging accidentally restarting android studio is the only helpful solution 🤷‍♀️

Upvotes: 0

frankelot

Reputation: 14409

The following worked for me:

adb kill-server
adb devices // restart in case it doesn't do it by itself

Upvotes: 0

Владислав Шестернин

Reputation: 1367

1. Open Edit Configurations:

2. Check the boxes:

Upvotes: 4

Yasser JE

Reputation: 61

This is the same of my problem and I solve it by install android studio 4.1.3 from this link : https://developer.android.com/studio/archive

or this directly

https://redirector.gvt1.com/edgedl/android/studio/install/4.1.3.0/android-studio-ide-201.7199119-windows.exe for windows

for MAC https://redirector.gvt1.com/edgedl/android/studio/install/4.1.3.0/android-studio-ide-201.7199119-mac.dmg

Upvotes: 1

Juan Pedro Goicochea

Reputation: 69

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:

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

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

Upvotes: 2

Michael Mao

Reputation: 463

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

Upvotes: 8

tariq101

Reputation: 157

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

Upvotes: 0

Marco Aurelio Silva

Reputation: 1534

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

Upvotes: 7

Aks4125

Reputation: 5720

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.

Upvotes: 0

kokoko

Reputation: 3964

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.

Upvotes: 6

Scott Wang

Reputation: 498

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

Upvotes: 0

user3138806

Reputation: 535

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

Upvotes: 41

Khalid Taha

Reputation: 3313

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

Upvotes: 20

Rahul Jain

Reputation: 276

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

android:debuggable="true".

Upvotes: 0

civic.LiLister

Reputation: 2197

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

Upvotes: 5

Loïc Dumas

Reputation: 1084

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.

Upvotes: 77

thatzprem

Reputation: 4767

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

Upvotes: 1

Mark

Reputation: 7718

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

Upvotes: 4