Segmentation fault

[eku]

Compiled and running scrcpy on Fedora 28 against an M3 SM10 device. scrcpy crashes with

$ ninja run
[0/1] Running external command run.
/home/.../scrcpy/x/server/scrcpy-server.jar: 1 file pushed. 1.2 MB/s (19342 bytes in 0.016s)
error: closed
ERROR: "adb reverse" returned with value 1
WARN: 'adb reverse' failed, fallback to 'adb forward'
Segmentation fault 

I did not find any coredump, even Fedora's coredumpctl did not list any.

[rom1v]

What is your Android version? Is it at least Android 5?

[eku]

It's running Android 4.3. I know scrcpy's device component requires at least Lollipop. Anyway, a hint instead of a segmentation fault would be helpful. Feel free to close this issue.

[rom1v]

Anyway, a hint instead of a segmentation fault would be helpful.

The segmentation fault occurs on the device, not in scrcpy (the client).

Avoiding it would require to check the Android version before starting the server… Why not, but don't know if it is worth it.

[eku]

Min API 21 - what requires it? Is lowering the API possible?

[rom1v]

See discussion for API 19: #98

[eku]

ty

[Lokawn]

My device is running Android 7.0 and still scrcpy crashed 2 times back to back.
Device is Moto G5 Plus 4GB variant.

 $ scrcpy -m 1280 -b 6M
 321 KB/s (18570 bytes in 0.056s)
 INFO: Initial texture: 720x1280
 INFO: FPS counter started
 INFO: 13 fps
 INFO: 44 fps
 Segmentation fault

[rom1v]

My device is running Android 7.0 and still scrcpy crashed 2 times back to back.

Interesting. How did it crash (which error messages)?

Segmentation fault? Error logs in adb logcat?