cocoonstack/scrcpy-rfb — explained in plain English
Analysis updated 2026-05-18
View and remotely control an Android device's screen using a standard VNC viewer.
Get low-latency, unmodified H.264 video from scrcpy through VNC-compatible clients like TigerVNC or noVNC.
Run a containerized bridge in a Docker or Kubernetes environment for remote Android access.
Integrate Android screen control into tools like Apache Guacamole that already speak VNC.
| cocoonstack/scrcpy-rfb | busung-dev/cve-2026-43499-s25u | lemire/fastconstmap | |
|---|---|---|---|
| Stars | 28 | 28 | 28 |
| Language | C | C | C |
| Setup difficulty | hard | hard | easy |
| Complexity | 4/5 | 5/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires compiling C dependencies or Docker, plus a running scrcpy server and VNC client to test end to end.
scrcpy-rfb is a bridge program that lets you view and control an Android phone or tablet screen using ordinary VNC remote desktop viewers. Scrcpy is an existing tool that streams an Android device's screen to a computer as compressed video, but it does not normally speak the standard VNC protocol that most remote desktop clients understand. This project sits between scrcpy and a VNC client and translates one into the other, exposing everything through a single network port. If a client supports a special H.264 video mode, such as the TigerVNC or noVNC viewers, it receives the original Android video stream directly with no extra processing on the server, keeping quality high and load low. Any other regular VNC client instead automatically receives a more universally compatible video format that the bridge converts on the fly, so nothing needs to be reconfigured on the viewer side beyond normal VNC settings. Building it requires a C toolchain along with the cmake build system, git, and a few supporting libraries including FFmpeg and libjpeg-turbo, plus a patched version of an existing VNC server library that the project fetches automatically during setup. The project also publishes ready-made Linux binaries and a container image automatically whenever changes are pushed, so most users will not need to compile it themselves. Once scrcpy is running with video and control enabled, you start this bridge pointing at it and connect any VNC viewer to the resulting port. The README documents specific settings that make the popular TigerVNC and Apache Guacamole clients behave better with the bridge, and describes internal details like how it detects and works around slow or unresponsive network clients so one bad connection does not affect others. By default the bridge listens on all network interfaces without a password, meaning anyone able to reach the port can control the connected Android device, so the README recommends either restricting it to the local machine and tunneling access, or setting a VNC password. Rotating the device or changing its screen resolution requires restarting the bridge, since the session size is fixed once it starts.
A bridge tool that translates an Android screen stream from scrcpy into the standard VNC protocol so ordinary remote desktop viewers can view and control the device.
Mainly C. The stack also includes C, CMake, FFmpeg.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.