No debuggable processes in logcat when phone detected by Android studio
AndroidDebuggingAndroid StudioSamsung MobileAndroid 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:
- Restart Android Studio ( preferably with invalidated caches as well )
- Restart your phone
- 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
- 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)
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:
- 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)
Solution 12 - Android
Click the "Bug" icon and that did the trick.
Solution 13 - Android
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
Solution 14 - Android
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.