-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote debug app #62
Comments
Check if it works if you use your phone with the regular |
My phone is not rooted, so adb tcpip will be a little complicated to me. Could you try to debug like mine? |
I don't have the luxury of spending time debugging random issues for free.
You need to provide enough information so that I don't waste my time. Once
we have a clear idea whether it's Studio's or adbkit's fault, I can maybe
take a look.
adb tcpip does not require root, it works on any device (not that it's
extremely slow, though). Try it out and report back with results.
…On Wed, Feb 15, 2017 at 4:17 PM, like ***@***.***> wrote:
My phone is not rooted, so adb tcpip will be a little complicated to me.
Could you try to debug like mine?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#62 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_W0Snz2QnSOZNqj_UUJi2dj1rrzGks5rcqZ-gaJpZM4MBXEu>
.
|
I have tried 5 times, the adb tcpip is ok. |
When you connect the device via adbkit, is the device also connected locally to the same machine with a usb cable? |
The adbkit runs on the computer which is connected by the phone via usb. And the android studio is another computer, connected the phone by the command adb connect 10.18.131.59:6174 |
And the as debug logs as below: 02/15 16:00:24: Launching app $ adb shell am start -n "com.example.administrator.myapplication/com.example.administrator.myapplication.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D |
Ok looks like I'll have to run some packet captures later 😞 |
Thanks a lot! Waiting for you response. |
We met the same problem, and it seems that we cannot solve it.
The reason is android studio sends a disconnection message to adb server to
and then reconnect again. If the mobile is connected by usb, there is no
problem. But for remote connection, it is a big problem
2017-02-15 14:48 GMT+08:00 like <[email protected]>:
… I came with the problem as the picture below when I used android studio
2.2.3 to debug an app. But the eclipse is ok with the same app. I am
confused. Could you give me some advice. Thanks.
[image: cc80d250-f2d2-11e6-99c8-6f1bb16f115d]
<https://cloud.githubusercontent.com/assets/12730220/22963367/bb026096-f38d-11e6-9ff6-d54f2b04d5a0.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#62>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABqrXnTm0BvYUM2HgwF2TH9a7gzA6npPks5rcp-ggaJpZM4MBXEu>
.
|
I just tried it with a simple hello world app and it was fine. After pressing the "debug app" icon in Android Studio, the "waiting for debugger" appeared on the device for a moment but quickly went away, and the app appeared. I did not experience any disconnections with Android Studio, either. My computer:
STF host:
Device:
Seems to work fine. I need more details from you if you want me to look into this. Full details of your computer, the STF host computer, and the device are needed. You may even need to send me the APK file. |
Thanks a lot! |
I came with the problem as the picture below when I used android studio 2.2.3 to debug an app. But the eclipse is ok with the same app. I am confused. Could you give me some advice. Thanks.

The text was updated successfully, but these errors were encountered: