Frequently Asked Questions

Common issues

The application is very young, it is not unlikely that you encounter problems with it.

Here are the common reported problems and their status.

On Windows, I have no output in the console

When run in cmd.exe, the application does not print anything. Even scrcpy --help have no output. We don't know why yet.

However, if you run the very same scrcpy.exe from MSYS2 (mingw64), then it correctly prints output.

As a workaround, redirect outputs to files, so that you can read the files afterwards:

scrcpy >stdout 2>stderr
type stdout
type stderr

Note that all SDL logs are printed to stderr.

On Windows, when I start the application, nothing happens

The previous problem does not help to get a clue about the cause.

The most common is your device not being detected by adb, or is unauthorized. Check everything is ok by calling:

adb devices

Windows may need some drivers to detect your device.

If you still encounter problems, please see issue 9.

I get a black screen for some applications like Silence

This is expected, they requested to protect the screen.

In Silence, you can disable it in settings → Privacy → Screen security.

See issue 36.

Mouse clicks do not work

On some devices, you may need to enable an option to allow simulating input.

Mouse clicks at wrong location

On MacOS, with HiDPI support and multiple screens, input location are wrongly scaled. See issue 15.

A workaround is to build with HiDPI support disabled:

meson x --buildtype release -Dhidpi_support=false

However, the video will be displayed at lower resolution.

KWin compositor crashes

On Plasma Desktop, compositor is disabled while scrcpy is running.

As a workaround, disable "Block compositing".