Discofork
Repository brief

Genymobile/scrcpy

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:08:50.730Z
3mo ago

Genymobile/scrcpy

scrcpy is the official, actively maintained open source tool for mirroring and controlling Android devices from Linux, Windows, and macOS. It emphasizes low latency, native performance, no device-side app installation, and support for USB or TCP/IP connections.

GitHub
Loading tags...
Stars137,744
Forks12,830
Default branchmaster
Last pushed2026-03-24T19:57:52Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Adopt this fork only if you specifically need its legacy Android 4.4 support or hierarchy-dump behavior. For general scrcpy use, upstream is the better choice because this fork is very stale and far behind current features, fixes, and maintenance.

Choose this fork if websocket streaming is the main requirement and you accept substantial upstream lag. If you want the most reliable, broadly maintained scrcpy experience, upstream is the safer default.

Prefer upstream unless you explicitly need this older, lightly patched behavior. This fork is best for legacy use or niche compatibility work, not as a general-purpose replacement.

Prefer upstream unless you specifically need this exact listener-removal patch and are prepared to carry the missing upstream changes yourself.

Prefer this fork only if the Latvian localization or macOS-specific distribution fits your needs and you accept being far behind upstream. For most users, the official scrcpy repo is the better choice because it is actively maintained and much closer to current upstream functionality.

Choose this fork only if the `FLAG_SECURE` black-screen issue is your blocking problem and you can accept root. If you want the latest scrcpy behavior, fewer compatibility risks, and the standard no-root workflow, upstream is the better default.