GUIscrcpy is a graphical front end for scrcpy, but its upstream repository is archived and its Flathub listing marks the app and its KDE runtime end of life. If you need to mirror and control an Android phone from Linux, use the maintained scrcpy release instead. It gives you the same USB or network connection model without an unmaintained desktop layer.
GUIscrcpy is end of life. Mirror your Android screen on Linux with scrcpy
scrcpy displays and controls an Android device over USB or TCP/IP. It does not need root access or an app installed on the phone. I downloaded the official Linux x86_64 release in this refresh, verified its published SHA-256 checksum, and ran its version command successfully.
Why GUIscrcpy is no longer the safe default
The GUIscrcpy GitHub repository was archived on December 29, 2023, and Flathub identifies in.srev.guiscrcpy version 4.11.3 as no longer maintained with an end-of-life KDE runtime.
A previously installed copy may continue to work, but a fresh setup should use scrcpy, which has an actively maintained release and documented Linux builds.
Prepare the Android device
scrcpy connects through Android Debug Bridge, also called ADB. On the phone, enable Developer options and USB debugging, then connect a data-capable USB cable and accept the computer authorization prompt.
Android places these controls in different Settings locations across manufacturers. Google’s Developer options documentation is the dependable reference when the label or path differs on your device.
Install the maintained scrcpy release
The upstream Linux page offers a static x86_64 archive for the latest release. This avoids a distribution package that upstream labels obsolete on Debian and Ubuntu.
curl -fL -o scrcpy.tar.gz https://github.com/Genymobile/scrcpy/releases/download/v4.1/scrcpy-linux-x86_64-v4.1.tar.gz
sha256sum scrcpy.tar.gz
tar -xzf scrcpy.tar.gz
cd scrcpy-linux-x86_64-v4.1
./scrcpy --version
The checksum printed during my verification was ad56ae8bfeedf41e824945c11dbf55fcb092b3e615b9b486f48a50e30d389635, which matches the checksum published in the upstream Linux instructions for scrcpy 4.1. Download the archive from the latest release page when a newer release is available, then compare it with that release’s published checksum.
Mirror and control the phone
With USB debugging authorized and the phone attached, start scrcpy from the extracted directory. A desktop window opens with the Android display, and your keyboard and mouse control the device.
./scrcpy
I could verify the binary on this Linux server, but I could not complete a device-mirroring session because this server has no attached Android device or graphical desktop. The upstream project documents USB and TCP/IP connections, recording, audio controls, and device options in its README.
Record the Android screen
scrcpy can write the mirrored stream to a file while it runs, so choose a media filename and keep the terminal open until the session ends.
./scrcpy --no-audio --record=phone-demo.mkv
Remove no-audio when you want device sound in the captured file and your setup supports audio forwarding.
Use wireless debugging only on a network you trust
Android’s wireless debugging feature can remove the USB cable after pairing. Keep the phone and computer on a network you control, and revoke debugging authorizations from Developer options when you no longer need remote access.
USB debugging gives the authorized computer substantial control over the device. Confirm the authorization dialog on the phone, avoid unknown computers, and turn debugging off when the task is complete.
If you already installed GUIscrcpy
You can keep it for a short-lived workflow, but do not expect security or compatibility maintenance from an archived project. Move to scrcpy before a desktop, Android, or runtime update breaks the old GUI.
Start with the official scrcpy release, confirm USB debugging, and run the version check before connecting your phone. That gives you a maintained baseline and an immediate way to diagnose whether the desktop tool is installed correctly.