Solved scrcpy success stories sought

[DonK]

This is as far as I get. adb seems satisfied:

$ adb shell​

a13x:/ $ ls​

acct etc prism​

apex init proc​

audit_filter_table init.container.rc product​

bin init.environ.rc sdcard​

bugreports linkerconfig second_stage_resources​

cache lost+found sepolicy_version​

config metadata spu​

d mnt storage​

data odm sys​

data_mirror odm_dlkm system​

debug_ramdisk oem system_dlkm​

dev omr system_ext​

dpolicy_system optics vendor​

efs postinstall vendor_dlkm​

a13x:/ $ exit​

$​

OpenGL opens OK:

$ glxgears​

​

Yet scrcpy stalls until ^C is hit:

$ scrcpy --render-driver opengl​

scrcpy 3.0.2 <https://github.com/Genymobile/scrcpy>​

INFO: ADB device found:​

INFO: --> (usb) R*********L device SM_A136U1​

/usr/local/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 104.3 MB/s (90396 bytes in 0.001s)​

^C​

ERROR: "adb push" exited unexpectedly​

What's missing?

 

[nxjoseph]

Try workaround in PR 278264. Adb Sideload and adb push/pull is seem to be problematic for now on FreeBSD.

If you want to use scrcpy for webcam purposes, try multimedia/droidcam but i cant get it to work at HD resolution.

 

[DonK]

Try workaround in PR 278264. Adb Sideload and adb push/pull is seem to be problematic for now on FreeBSD.

The easiest solution at your link worked for me. Thank you.

scrcpy instantaneously appears after adb shell ls is invoked from a second session about a minute after scrcpy is invoked. Users must wait a minute or two foradb push to complete (without notification). If adb shell ls from a second session also hangs then give it a little more time, open a third session, and invoke adb shell ls from the third session.

 

[rewest]

The easiest solution at your link worked for me. Thank you.

scrcpy instantaneously appears after adb shell ls is invoked from a second session about a minute after scrcpy is invoked. Users must wait a minute or two foradb push to complete (without notification). If adb shell ls from a second session also hangs then give it a little more time, open a third session, and invoke adb shell ls from the third session.

Yep, I use this technics too, from the script (any command in shell works, not only ls):

#!/usr/bin/env sh
/usr/local/bin/adb devices && /usr/local/bin/scrcpy -d -m 960 --max-fps=25 -w --no-audio --mouse=uhid --keyboard=uhid &
sleep 0.1
adb shell cd
wait

 

[DonK]

This reliable recipe works well, without a wait, on 13.4-STABLE FreeBSD:

1. Ensure adb is stopped:

sudo killall -9 adb​

or

adb kill-server​

2. Activate the phone's GUI through its touchscreen. (Enter the optional four digit security code, if need be). Connect the phone to the PC with a USB cable. Invoke these commands from a terminal session.

adb devices​

scrcpy &​

adb shell ls​

adb shell ls​

The android display now inevitably appears for me. Whenever the scrcpy window goes dark, my twmxwindows session allows me to wake it up with a right mouse click.