srevinsaju/guiscrcpy

[BUG] GUI connected, but can't see phone screen

andytorres opened this issue · 12 comments

Downloaded guiscrcpy-PyQt5-x64.exe from here and installed it.
GUI opens just fine, phone connected

image

But when I click START SCRCPY, this happens:

image

Connection is established and toolbar buttons work, I can see the effect in my phone screen when I click them, but there's no phone screen.

I tried to execute scrcpy binary manually, and it shows my phone screen. The GUI is the one that isn't working

Windows 11 21H2 (OS Build 22000.1281)

Thanks in advance

Same problem.

Can you please run guiscrcpy-xxxxx.exe from a powershell window and copy the logs on chat when you try to "START SCRCPY" so that I can take a look?

@srevinsaju

guiscrcpy v2022.6.1
by @srevinsaju
https://github.com/srevinsaju/guiscrcpy


connected to 192.168.0.101:43258

WARNING:guiscrcpy.adb:Command '['C:\\ProgramData\\chocolatey\\bin\\adb.EXE', '-s', '192.168.0.101:38816', 'shell', 'wm', 'size']' exited with '1'
E: guiscrcpy has crashed because of a failure in the execution of `adb shell wm size`. This might be because of an improper connection of adb. Please reconnect your device (disconnect from WiFi / Reconnect USB) or try

guiscrcpy --killserver

as a command line to restart adb server

Thank you @soredake , Can you please try running

C:\ProgramData\chocolatey\bin\adb.EXE -s 192.168.0.101:38816 shell wm size

from the powershel window and let me know what happens / what is the output?

@srevinsaju

❯ C:\ProgramData\chocolatey\bin\adb.EXE -s 192.168.0.101:38816 shell wm size
adb.exe: device '192.168.0.101:38816' not found

I don't know why this adb command was used with old port.

On subsequent runs i get no errors, but still, can't see phone screen.

Can I see the contents of C:/Users/<username>/AppData/Local/guiscrcpy/...config.json?

@soredake does C:/Users/user/Downloads/scrcpy-win64-v1.25/scrcpy-server and C:\ProgramData\chocolatey\bin\scrcpy.EXE exist? If yes, when running it using guiscrcpy, does it create any weird output on the poweshell / terminal window?

@srevinsaju yes, they exist, and no weird output when running them.

I've reset my config, and pointed scrcpy-server location to scrcpy-server bundled with scrcpy, not the newer version like earlier, now it shows my screen.

It would be nice if guiscrcpy can automatically find scrcpy-server if scrcpy is on PATH as scrcpy-server is located in the same folder.

On Arch Linux using guiscrcpy-appimage package from AUR I get this error (and another one related to PyQt5):

With USB, it detects the device but doesn't show the screen, just the panels. This error happens a lot with different sequence numbers:

qt.qpa.xcb: QXcbConnection: XCB error: 6 (BadCursor), sequence: 1373, resource id: 100663307, major code: 2 (ChangeWindowAttributes), minor code: 0

Also, when searching the device via local wifi, I get this on the terminal, and doesn't detect it:

Traceback (most recent call last):
  File "guiscrcpy/launcher.py", line 252, in settings_mgr
  File "/tmp/embedded.z6kj5qeg.zip/shibokensupport/__feature__.py", line 142, in _import
  File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
  File "guiscrcpy/ux/settings.py", line 20, in <module>
  File "/tmp/embedded.z6kj5qeg.zip/shibokensupport/__feature__.py", line 142, in _import
ModuleNotFoundError: No module named 'PyQt5'

I'm adding this here due to the PyQt5 mention above, although I don't think this is related, since this error only appears when searching the device.