-
-
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
ERROR: Could not open video stream #565
Comments
Could you build the app in debug mode (to get more logs)? (this is the meson default, just do not pass |
Logcat still empty. |
OK, so there is a deadlock somewhere. Maybe related to the "Meizu fix" you mentioned. To find where it is blocked on the client-side, execute: SCRCPY_SERVER_PATH=x/server/scrcpy-server.jar gdb scrcpy -ex run Then when it is blocked, press Ctrl+Z. You get a Type |
I am probably doing something wrong, because
|
Did you build scrcpy in debug?
You should start the one from your builddir ( |
I noticed that too, but I did build it in debug; Or should I not use the prebuilt server for that? Update
Update 2
Apparently starting the program from the builddir causes some other problem. |
Hi @rom1v so gdb shows next (I have the same issue with Meizu after Flyme >= 7.0 upgrade)
|
So in general - very stupid workaround to show scrcpy window - press on the icon , go to scrcpy - About - after dialog opened - close it - Gray window will be shown - when you can click - so touches works as expected. |
OK, so the client is waiting for video stream from the server:
Therefore, the server (on the device) seems deadlocked. Nothing special in |
Btw, absolutely same bt from unpatched version. Thread 2 received signal SIGTSTP, Stopped (user). Thread 10 (Thread 0x2703 of process 56918): Thread 9 (Thread 0x171b of process 56918): Thread 8 (Thread 0x164b of process 56918): Thread 7 (Thread 0x2803 of process 56918): Thread 6 (Thread 0xe2f of process 56918): #6 0x0000000100127b96 in av_probe_input_buffer2 () from /usr/local/opt/ffmpeg/lib/libavformat.58.dylib Thread 4 (Thread 0xc0b of process 56918): Thread 2 (Thread 0xb03 of process 56918): |
in logcat absolutely nothing useful (
|
It seems that it's after reboot logs only - and never updated. Will try with |
So logcat connected with the issue
|
OK, so it's #151. |
Even after enabling Night mode via Flyme Lab apk + quick shortcut apk (non-China firmware) - the issue still persists ( |
ERROR: Could not open video streamDevices : development board, no screen OS : Mac 10.14.5 Log:
|
In addition, I just picked up an HDMI screen, still the same error message. |
@lhzlg3368 Any relevant logs in the output of |
I've got a workaround: |
This worked for me as well. |
Yup. That helps
Getting this error on 1 and 2. 3 works fine |
It just depends on what the hardware encoder in the device is able to encode. |
Sounds reasonable. Thanks |
Works for Umidigi F2, I also experienced the same initial error. |
Device: Meizu Pro 7
Logcat info: None
OS: macOS 10.14.5
I have a Meizu Pro 7 device with a broken screen. Tried the prebuilt version and a custom build using a Meizu fix (#1).
After running the program nothing happens. Until I terminate the process, then an errors appears about the video stream. I checked logcat, but there is no activity whatsoever.
The text was updated successfully, but these errors were encountered: