Many apps do this by asking the user to enable developer modeĪnd USB debugging, but this is an extra step than can be inconvenient for the user. So we had to get a bit creative to pull it off. The Android system does not provide any official method for USB communication between an app and a Windows computer, This will allow transferring files while SuperDisplay is running, but requires a little more setup.įor an explanation of why this is necessary, keep reading. Enable USB connections via ADB and uncheck Enable AOAP under Advanced settings from SuperDisplay Settings on your PC.This is the easiest method, but you'll have to remove and plug your device back in before you can use SuperDisplay again. Select Transfer files as the USB mode from the system notification that pops up after plugging in your device (see image).The ADB log is telling: 8568-8568/it.myapp:myprocess W/ActivityThread﹕ Application it.myapp is waiting for the debugger on port 8100.Ĩ568-8568/it.myapp:myprocess I/System.out﹕ Sending WAIT chunkĪlso, I can't find an easy way to disconnect nor reset ADB connection in Android Studio.If you wish to transfer files with between your device after installing SuperDisplay, you have two options:

Even re-installing the app doesn't solve. Update: Opened a bounty since this issue is so annoying. I can't be the only one encountering this issue :-/ Update: The same thing happens when debugging on Nexus 7 (2013) running Android 5.0 and testing on another machine rendered the same result. So the question is what can I do to make Android Studio debugging work? And on the same computer I can perform debugging using Eclipse on the same device without any issues. This has being the case from Android Studio 0.8.8 all the way to 1.0. While the device (Samsung Galaxy S3 Android 4.3) I'm debugging would display Whenever I try to use Android Studio's Debug function, the Run status would always stuck at: Launching application: /.ĭEVICE SHELL COMMAND: am start -n '/' -a -c The supposed duplicate is a question on being stucking in ' Waiting For Debugger' when executing Run, while this question is on being stucking in ' Waiting For Debugger' when executing Debug, the steps to produce the problem is different, and the solution(s) are different as well.

Bluestacks 2 please wait