>.\scrcpy.exe -V verbose
scrcpy 2.7 <https://github.com/Genymobile/scrcpy>
INFO: ADB device found:
INFO: --> (tcpip) 10.42.40.226:5555 device CTP08_V3
DEBUG: Device serial: 10.42.40.226:5555
DEBUG: Using server (portable): C:\FlashTools\scrcpy-win64-v2.7\scrcpy-server
C:\FlashTools\scrcpy-win64-v2.7\scrcpy-server: 1 file pushed, 0 skipped. 52.8 MB/s (71200 bytes in 0.001s)
[server] INFO: Device: [DIVUS] DIVUS CTP08_V3 (Android 10)
[server] WARN: Audio disabled: it is not supported before Android 11
[server] DEBUG: Audio encoder stopped
[server] DEBUG: Using video encoder: 'OMX.rk.video_encoder.avc'
DEBUG: Server connected
DEBUG: Starting controller thread
DEBUG: Starting receiver thread
[server] DEBUG: Display: using SurfaceControl API
DEBUG: Using icon (portable): C:\FlashTools\scrcpy-win64-v2.7\icon.png
INFO: Renderer: direct3d
DEBUG: Trilinear filtering disabled (not an OpenGL renderer)
DEBUG: Demuxer 'video': starting thread
DEBUG: Demuxer 'audio': starting thread
INFO: Texture: 1280x800
WARN: Demuxer 'audio': stream explicitly disabled by the device
VERBOSE: input: touch [id=mouse] hover-move position=533,402 pressure=1.000000 action_button=000000 buttons=000000
[...]
VERBOSE: input: touch [id=mouse] hover-move position=1175,521 pressure=1.000000 action_button=000000 buttons=000000
DEBUG: Demuxer 'video': end of frames
DEBUG: Receiver stopped
DEBUG: Server disconnected
WARN: Device disconnected
DEBUG: Server terminated
DEBUG: quit...
DEBUG: Controller stopped
Notes
The issue is NOT present using the c2.android.avc.encoder or the OMX.google.h264.encoder video encoders, instead of the default OMX.rk.video_encoder.avc. The display mirroring is however quite slow, using those two codecs.
Another option to avoid the issue is to use the --stay-awake options.
Hope this helps; let me know if there are more information that can be useful to debug the problem.
Environment
Describe the bug
The device crashes when the screen is turned off. Sometimes it will reboot, sometimes it will freeze.
It seems similar to #5121 but the log is not quite the same.
Logcat on the device:
dmesg output on the device:
scrpy on Windows (verbose logging enabled):
Notes
The issue is NOT present using the
c2.android.avc.encoder
or theOMX.google.h264.encoder
video encoders, instead of the defaultOMX.rk.video_encoder.avc
. The display mirroring is however quite slow, using those two codecs.Another option to avoid the issue is to use the
--stay-awake
options.Hope this helps; let me know if there are more information that can be useful to debug the problem.