18637
18637
I also have the same issue. mine is running i2c 32 also. Running on a Rp4 Compute module. is there any way to fix this?
> Steps to figure out what went wrong: > > 1. Ensure I2C is enabled `sudo raspi-config` > 2. Remove PiSugar, then run `i2cdetect -y 1 0x75`. If there is...
@fengyc The latest version 1.5.0 has fixed this issue for me. Thank you.
Yes. You should be able to control the audio from Scrcpy independently. Go to windows audio control and you should be able to adjust the scrcpy audio without changing the...
Sorry Forgot to include that doing the following ``` adb kill-server, or adb disconnect or both, then restarting adb and re connecting. ``` Makes no difference. Still fails to push...
For starters, I appreciate your help. I can't reproduce the problem without involving "scrcpy-server". That is the only file that fails to push when it gets in this state. If...
Ok I tested the commands above when it is in a broken state ``` C:\Users\User\Shadow>adb push devices.txt /data/local/tmp/scrcpy-server.jar devices.txt: 1 file pushed, 0 skipped. 0.0 MB/s (89 bytes in 0.019s)...
After reboot. I tested new version. Took about 3 hrs to stop working. ``` C:\Users\User\Shadow_new>scrcpy scrcpy 2.3.1 INFO: ADB device found: INFO: --> (tcpip) 192.168.193.202:5555 device SM_A146P C:\Users\User\Shadow_new\scrcpy-server: 1 file...
Is there anything else I can try?
@rom1v I want to be able to prove the fault is only related to adb. To test this, When this error happens i will push the server to the phone...