-
-
Notifications
You must be signed in to change notification settings - Fork 11k
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
Unable to connect via ADB over TCPIP #213
Comments
Thank you for your report. You can increase the number of attempts to confirm the problem. See #5 (comment) Basically, change this line and recompile. |
I can't compile it though, I don't know enough to compile it properly I keep messing it up and I ended up giving up on trying to compile a test version myself. I'm running windows and have no idea what I'm doing. |
Would you be willing to give an exact step-by-step procedure of what you're doing, from the very beginning all the way to the error? Maybe we can pinpoint what's going on with such further detail. |
5 seconds might not be sufficient: <#213> Increase to 10 seconds (it does not harm).
Please retry with v1.3. |
- Fix missing initialization that leaded to kill the whole process - group on quit (Genymobile#182, Genymobile#183) - Support holding Ctrl+Key shortcuts (Genymobile#166) - Forward repeated volume events - Increase "adb forward" connections attempts to 10 seconds (Genymobile#213) - Add crop feature
@ZizzyDizzyMC Could you try with v1.3, please? |
I can complete a connection to my android device over ADB including opening a shell. I cannot get scrcpy to work over wifi however.
I believe it might be related to the retry attempts. I know it's 50 retries at a 100ms wait time as per the code, and was wondering if there would be a way to test and see if a higher retry count would fix my issue.
Basically a carbon copy of #121 but with the no connection of #5 's issue of timing out before the phone server starts.
Edit: The phone I was orginally trying the adb over wifi connection was a ZTE ZFive 2, that didn't work. It has Android 6.0.1
I tried it with my Samsung S7 which is also running Android 6.0.1. This worked quickly and has worked a few more times after closing and reopening again.
I highly suspect now that the slower ZTE just couldn't start the server fast enough. Perhaps change this into a feature request to make a start-up flag that allows us to set the connection attempts to a higher value in the case that our devices can't connect fast enough.
The text was updated successfully, but these errors were encountered: