Skip to content
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

Windows: adb over tcp/ip dose not work, command prompt dosen't show log #123

Closed
parthibx24 opened this issue Apr 16, 2018 · 5 comments
Closed

Comments

@parthibx24
Copy link

parthibx24 commented Apr 16, 2018

it dosen't work with ADB over wifi in windows. Its working on linux but its not working on windows.
i get this output when i execute scrcpy.exe from Mingw with adb over wifi.

screenshot 309

$ ./scrcpy
ERROR: "adb reverse" returned with value 1
WARN: 'adb reverse' failed, fallback to 'adb forward'

And when i execute scrcpy.exe from command prompt or powershell it dosen't show any output in the terminal(scrcpy works though) even when i add --help flag. but it shows output when i execute it from Mingw.

Command prompt
screenshot 314

Mingw
screenshot 315

scrcpy version :

$ ./scrcpy --version
scrcpy v1.1

dependencies:
 - SDL 2.0.7
 - libavcodec 57.107.100
 - libavformat 57.83.100
 - libavutil 55.78.100`

OS : Windows 10 - 1703

@rom1v
Copy link
Collaborator

rom1v commented Apr 16, 2018

Thank you for your report.

The missing output on Windows is a known problem (but unknown solution).

The failure over adb connect is probably due to a small number of attempts. Cf #121 (comment).

@parthibx24
Copy link
Author

@rom1v Okay.
But can you make the app to show logs on a new window? just a for a temporary solution?

@rom1v
Copy link
Collaborator

rom1v commented Apr 17, 2018

But can you make the app to show logs on a new window?

SDL does not provide widgets (e.g. a TextBox), so it would require too much work for this. The current workaround consists in redirecting the output and error streams to files, and read the files.

@parthibx24
Copy link
Author

Oh ok.

@rom1v
Copy link
Collaborator

rom1v commented May 28, 2018

Should be fixed by v1.2. Please reopen otherwise.

@rom1v rom1v closed this as completed May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants