No debuggable processes in logcat when phone detected by Android studio

Question

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!

for me I had to run an emulator with Oreo... not what I want but the only thing that worked — CrandellWS, Oct 10 '18 at 04:21
first of all, make sure that this is not a release version ) — Andrew Glukhoff, Sep 15 '21 at 08:33

score 77 · Answer 1 · answered Jun 28 '17 at 08:45

77

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.

answered Jun 28 '17 at 08:45

Loïc Dumas

1,036
10
18

2

This was exactly my issue. Thanks! – haggy May 12 '19 at 23:11
1

Note that debuggable may be set to true in release as well. Optional but maybe not recommended depending on you application. – JohnyTex Oct 23 '19 at 06:55
that's the right answer! Thanks, i did not know that! – Don Diego Nov 17 '22 at 14:55

score 54 · Answer 2 · answered Apr 26 '17 at 14:31

54

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

answered Apr 26 '17 at 14:31

Zinc

1,002
12
18

this should be the answer. +1 – E J Chathuranga Nov 06 '17 at 06:58
12

Yes, they removed it in last Android Studio version. Go to `File`-->`Settings`-->`Build, Execution, Deployment`-->`Debugger` and ensure that the `Logcat output` options are checked – Zinc Apr 05 '18 at 10:06

score 42 · Answer 3 · answered Dec 08 '16 at 07:21

42

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

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

answered Dec 08 '16 at 07:21

koperko

2,447
13
19

What about the cable ? There are cables out there, that have only power transfer capability.. – koperko Dec 08 '16 at 08:19
I can use adb in cmd console with the same cable,it works well.so.... I don't know the root cause about this phenomenon. – kimichang Dec 08 '16 at 08:24
11

"Restart Android Studio" worked like a charm for me. – Bram Jul 31 '17 at 18:22
2

after tried all these solutions its not working for me. – Aman Goyal May 15 '19 at 05:57

score 40 · Answer 4 · answered Jul 23 '18 at 09:59

40

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

answered Jul 23 '18 at 09:59

user3138806

525
5
5

Worked for me using a Google Pixel 2. Thanks! – DevOpsSauce Jan 10 '19 at 02:07
This setting is not where it is specified above. I have 3.1.3 installed and the setting does not exist in that window. – Adam Feb 12 '19 at 16:36
1

You saved my life! A little update to this answer, on newer versions of Android Studio, you should go to: Android Studio -> Preferences -> Build, Execution, Deployment -> Debugger – Miller Go Dev Mar 26 '20 at 00:16
1

Doesn't work on mac though. Will give you an error when you try to debug the app. https://stackoverflow.com/questions/57770464/installation-did-not-succeed-the-application-could-not-be-installed-installati – aB9 Apr 21 '20 at 03:40
Sweet! Thank you – FerDensetsu Nov 30 '21 at 22:37

score 18 · Answer 5 · answered Oct 09 '17 at 23:25

18

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

answered Oct 09 '17 at 23:25

Khalid Taha

3,183
5
27
43

After reading this answer I set "debuggable true" in a custom signed debug variant and it worked. Thanks! – Antonio Papalillo Mar 30 '19 at 08:13

score 7 · Answer 6 · answered Oct 21 '20 at 08:34

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)

aligur · Answer 7 · 2019-01-12T18:44:59.977

6

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.

edited Jan 12 '19 at 18:44

answered May 17 '18 at 13:47

aligur

3,387
3
34
51

score 6 · Answer 8 · answered May 26 '20 at 13:17

6

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

answered May 26 '20 at 13:17

Marco Aurelio Silva

1,524
1
12
6

Best answer. It works for me. Thanks – Cedriga Nov 22 '21 at 19:45

score 5 · Answer 9 · answered Sep 04 '17 at 08:33

5

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

answered Sep 04 '17 at 08:33

civic.LiLister

2,087
16
13

Great! I didn't know I have to set `debuggable true` explicitly in the `build.gradle` file. – JCarlosR Nov 10 '20 at 18:46

score 4 · Answer 10 · answered Apr 28 '17 at 05:52

4

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

answered Apr 28 '17 at 05:52

Mark

7,446
5
55
75

Indeed this was not re-enabled by default for me as well – Louis Feb 21 '18 at 14:10
Great tip. I found that I had to use Task Manager to kill process monitor.exe running in the background to restore the normality. – Hong Mar 24 '18 at 17:12

score 4 · Answer 11 · edited May 24 '22 at 20:50

4

1. Open Edit Configurations:

2. Check the boxes:

edited May 24 '22 at 20:50

Dharman

30,962
25
85
135

answered Feb 09 '22 at 15:44

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

1,125
8
14

I'm trying to use the App Inspection Tab to check my app's database and I am seeing this "No debuggable process" when selecting my device. How do I go about this? Because this did not work – Daniel Iroka Jul 24 '23 at 15:49

score 2 · Answer 12 · answered Mar 30 '21 at 21:11

2

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)

answered Mar 30 '21 at 21:11

Juan Pedro Goicochea

59
3

wooooow this worked for me, after One week search :x – abbasalim Jan 01 '22 at 13:43

score 1 · Answer 13 · answered Apr 28 '17 at 05:54

1

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

answered Apr 28 '17 at 05:54

thatzprem

4,697
1
33
41

score 1 · Answer 14 · answered May 19 '21 at 00:01

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

score 0 · Answer 15 · edited Sep 25 '17 at 12:38

0

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

android:debuggable="true".

edited Sep 25 '17 at 12:38

Paul Roub

36,322
27
84
93

answered Sep 25 '17 at 12:32

Rahul Jain

276
2
11

score 0 · Answer 16 · answered Sep 04 '18 at 03:54

0

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

answered Sep 04 '18 at 03:54

Scott Wang

489
1
7
9

score 0 · Answer 17 · answered Mar 05 '19 at 07:06

0

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.

answered Mar 05 '19 at 07:06

Aks4125

4,522
4
32
48

score 0 · Answer 18 · answered Oct 04 '20 at 11:20

0

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

answered Oct 04 '20 at 11:20

tariq101

127
2
6

score 0 · Answer 19 · answered Jan 29 '23 at 03:59

0

The following worked for me:

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

answered Jan 29 '23 at 03:59

frankelot

13,666
16
54
89

score 0 · Answer 20 · answered May 30 '23 at 11:21

0

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

answered May 30 '23 at 11:21

Mahmoud Aly

578
3
10

score 0 · Answer 21 · answered Jul 01 '23 at 11:42

0

To Solve this issue.

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

answered Jul 01 '23 at 11:42

Rakesh Jha

279
2
7

score 0 · Answer 22 · answered Aug 18 '23 at 06:42

0

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.

answered Aug 18 '23 at 06:42

Victor Choy

4,006
28
35

score -1 · Answer 23 · answered Dec 08 '16 at 08:47

-1

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

answered Dec 08 '16 at 08:47

DzefersonS

28
8

I don't know then. Maybe you didn't do 1 important thing - when you plug your phone in, when you pull down that little menu in it you should see usb file transfer. If not yet done, select "transferring media files" so it works. – DzefersonS Dec 08 '16 at 09:12
I can transfer file correctly.because of my reputation on this web,i can not upload picture. or you can see the phenomenon. – kimichang Dec 08 '16 at 09:17
That is pretty sad. If you could explain what you did overall I could try helping you a bit more. – DzefersonS Dec 08 '16 at 09:22
I got the answer,maybe it can only debug the app that in your project.i want to debug others' app via attache process. Thanks a lot! you are so kind! – kimichang Dec 08 '16 at 10:45

No debuggable processes in logcat when phone detected by Android studio

23 Answers23

Linked