Genymobile / Genymobile/scrcpy
scrcpy device
- Dominant language
- C
- Stars
- 150k
- Forks
- 13.7k
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
Description
- [x] I have checked that a similar [feature request](https://github.com/Genymobile/scrcpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22feature+request%22) does not already exist.
**Is your feature request related to a problem? Please describe.**
Not a problem of scrcpy but a limitation to some devices that does not have DP alt mode and users does not want to use a desktop or laptop just to mirror device (not wireless, cause wired one is better)
**Describe the solution you'd like**
---
# Standalone "Scrcpy-Box" Appliance Mode (Hardware Mirroring & Control Bridge)
### Summary
Instead of running `scrcpy` inside a heavy desktop OS (like Windows, macOS, or full Linux desktop environments), I propose exploring a **standalone, dedicated hardware appliance concept**—essentially a pocket-sized "Scrcpy Receiver Box."
This device would allow any user to plug an Android phone into a tiny, custom-flashed single-board computer (like a Raspberry Pi Zero 2 W, Compute Module, or Radxa Zero) via USB, instantly mirroring and controlling the phone on *any* standard HDMI monitor, TV, or portable display with ultra-low latency, completely bypassing the need for a PC.
---
### How It Works (The User Experience)
1. **Power Up:** Plug the small box into a standard USB-C power source or power bank.
2. **Connect Display:** Plug a standard HDMI cable from the box into any monitor, TV, or portable touch display.
3. **Connect Phone:** Plug an Android phone (with USB Debugging enabled) into the box’s **USB Data Input** port.
4. **Instant Mirroring:** The device boots directly into a headless minimalist Linux environment (like Alpine Linux) that auto-starts `scrcpy`. The phone screen instantly appears full-screen on the external display with zero configuration needed.
5. **Control:** If connected to a touch monitor or via a USB/Bluetooth mouse and keyboard plugged into the box, touch and cursor inputs map natively back to the phone via ADB.
---
### Physical Form Factor & Port Layout
Imagine a small, deck-of-cards-sized enclosure (3D-printed or custom-molded) with 3 ports:
* **Port 1 (Power Input):** USB Type-C (Female) — Supplies dedicated power to the board and ensures stability for the connected phone.
* **Port 2 (Device Input):** USB Type-C (Female) — Connects to the Android phone (running in USB Host Mode to handle the ADB/scrcpy data bridge).
* **Port 3 (Video Output):** Standard HDMI (Female) — Connects straight to any standard monitor or display via an ordinary HDMI cable.
---
### Technical Blueprint (How to Build It Today)
For developers or enthusiasts wanting to prototype this right now, the architecture relies on existing components:
* **The Hardware Brain:** A Raspberry Pi 4/5 or a compact board like the Radxa Zero (chosen for its small footprint and native hardware video decoding support for H.264/H.265 streams).
* **The OS Layer:** Alpine Linux or Raspberry Pi OS Lite stripped of any heavy desktop environment (no GNOME/KDE) to keep boot times under 3–5 seconds.
* **The Software Autostart:** A lightweight X11/Wayland window server (like Weston) configured via a `systemd` service to launch `scrcpy` in fullscreen immediately upon detecting an ADB handshake on the USB port:
```bash
#!/bin/bash
adb wait-for-device
scrcpy --fullscreen --no-audio-playback
```
---
### Why This Benefits the Scrcpy Ecosystem
While `scrcpy` is traditionally a desktop tool, formalizing or packaging an "Appliance / Embedded Build Profile" opens up massive use cases for the community:
* **Automotive Head Units:** Turning a cheap screen and a single-board computer into a high-performance Android car infotainment dashboard.
* **Portable Gaming Rigs:** Connecting a phone to a portable gaming monitor on the go without hauling a laptop.
* **Field Work & Bench Techs:** Technicians projecting phone screens onto large workbench monitors instantly.
I’d love to hear the core maintainers' thoughts on whether a lightweight, appliance-style embedded target for `scrcpy` is something that aligns with the project's future roadmap!
**Describe alternatives you've considered**
Or, instead of just 3 ports, make it like hub or docking station look, this will make a huge amount in the market, specially for the mobile gamers that uses phone that does not support DP alt mode. I know a lot from the Philippines
**Additional context**
Make the best out of android device with scrcpy-box. I'd like to try the prototype and also i want to invest in it.
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository files, tests, or implementation entry points are named. Start by reviewing scrcpy's supported platforms and runtime architecture, then determine whether an embedded appliance target fits the project scope. Done would require a defined target, supported hardware and OS, integration boundaries, and maintainer agreement rather than a small isolated code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, linux, raspberry-pi
- Domain
- desktop-dev, embedded-iot, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100