-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
i got an error when i run scrcpy v1.5 #337
Comments
|
hi rom1v
|
If you installed it (with
|
|
|
OK, so it seems good. From |
hi rom1v |
This is clearly due to a change in the way the crop parameters are passed (to pass an additional parameter) in What is the result of:
? |
my android is rk3288 , it's working at android v6.0 |
OK, then:
How many spaces does it print between |
|
The client passes parameters to the server via "adb shell" arguments. Use "-" instead of "" when no crop is specified to avoid empty arguments, which are not handled the same way on all devices. Fixed <#337>.
@puface Thank you for the details. Please checkout the |
Hi rom1v, |
@mgienal Did you recompile the server? (you must not use the prebuilt server, since the fix updates it) |
I see, I'm using the prebuilt server now. So do I need to build my own server to avoid the problem? |
I'm also running into this. Can we get an updated prebuilt server 🙏 ? |
@sshock Sorry, didn't have time. But now there is v1.6 😉 |
hi all
i update scrcpy v1.5 today .
i can build success by scrcpy server v1.5.jar file but i got an error when i run scrcpy -m 1024
the error :
397 KB/s (19291 bytes in 0.047s)
ERROR: Exception on thread Thread[main,5,main]
java.lang.IllegalArgumentException: Crop must contains 4 values separated by colons: "''"
at com.genymobile.scrcpy.Server.parseCrop(Server.java:91)
at com.genymobile.scrcpy.Server.createOptions(Server.java:72)
at com.genymobile.scrcpy.Server.main(Server.java:108)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
The text was updated successfully, but these errors were encountered: