Use Your Android Phone as a Switch Monitor (SysDVR)

Yes — your Android phone can be the screen. Install the official SysDVR-Client app on the phone (or point an RTSP player at the console) and the Switch plays on the phone display while the console sits in your lap, your bag, or across the room. It’s the travel setup SysDVR is quietly best at: no dock, no TV, no capture hardware — just the console, a phone, and a decent connection.

What you need

• A hacked Switch running Atmosphère with SysDVR installed — start with the install guide if needed.
• For the client app: a phone running Android 10 or later on a 64-bit device (32-bit support was added in SysDVR v6.2, which widens the net a little).
• Console and phone on the same Wi-Fi network for the wireless routes, or a USB cable for the wired route.
• A streaming-compatible game — long-press the capture button in it; if a clip records, it will stream.

Route A — The SysDVR-Client app (recommended)

1. Install the official SysDVR-Client APK on your phone (safe procedure in the APK guide).
2. On the console, open SysDVR Settings and set the streaming mode to TCP Bridge — the low-latency network mode with automatic discovery.
3. Launch your game on the console.
4. Open the SysDVR-Client app on the phone, on the same Wi-Fi. Your console should appear via auto-discovery — tap it (or enter the console’s IP manually if it doesn’t).
5. Prop the phone up, pick up your controller — Joy-Con or Pro Controller, paired to the Switch as always — and play. Game audio plays through the phone.

Route B — An RTSP player (nothing to install from GitHub)

If you’d rather not install the client, any RTSP-capable player turns the phone into a viewer:

1. On the console, set the streaming mode to Simple Network in SysDVR Settings.
2. Open mpv for Android or VLC on the phone and open the network stream rtsp://<console IP>:6666/.
3. Launch the game and watch it on the phone.

Expect more buffering and latency on this route — RTSP players cache for smoothness, which is the opposite of what live play wants. It’s fine for turn-based games, RPGs and spectating; for action games, use the client app. The RTSP mode guide covers latency settings on the player side.

Route C — USB to the phone (lowest latency)

The Android client can also receive over USB, and Android receivers need no driver setup at all. A cable makes this the lowest-latency portable setup — the phone becomes a true wired monitor. One known weak point, straight from the official guide: USB-C-to-C cables can be unreliable for SysDVR’s USB mode, so if the connection drops or never appears, try a different, shorter, good-quality cable before troubleshooting anything else.

Latency and battery honesty

• Wi-Fi quality decides smoothness. Same strong network for both devices, close to the router or hotspot. Your internet speed is irrelevant; the stream is local.
• The feed is 720p30. On a phone-sized screen that looks sharp — this is the one display where SysDVR’s hardware cap barely matters.
• Turn the console screen off. Since SysDVR 6.1 the console’s screen can stay off while it streams. Use it: the Switch doesn’t need to glow inside your bag, and you’ll save real battery. (More switches like this live in the advanced tips.)
• A small phone stand changes everything. Propping the phone at eye level, controller in hand, is the difference between a gimmick and a setup you’ll actually use on a train.

Rather go bigger — or smaller?

The same app-and-player logic scales up to the TV with an Android TV box (with real caveats about cheap hardware — see SysDVR on Android TV) and sideways to a laptop screen with the laptop-as-monitor setup. The phone remains the sweet spot for travel: it’s the screen you already carry.

Troubleshooting the phone setup

• The console doesn’t appear in the app: confirm both devices are on the same network, then check the router for AP/client isolation — many routers, and nearly all public hotspots, block devices from seeing each other, which silently kills auto-discovery. If discovery stays blocked, connect by entering the console’s IP address manually.
• The app won’t install: check the phone against the real limits — the client needs Android 10+ on a 64-bit device (32-bit support arrived in v6.2). The official guide is blunt that older devices, smart TVs and similar hardware may simply not install it; that’s a platform limit, not a broken APK. Re-download from the official GitHub release before concluding anything.
• The picture freezes on venue or hotel Wi-Fi: that’s AP isolation plus congestion, the worst combination for local streaming. Your own travel router or a phone-hosted network you control will beat it every time — the stream is local, so it never needed the venue’s internet in the first place.
• USB connection drops: swap the cable before touching settings. Cable quality is the documented weak point of USB mode.

Next steps

• Install the Android client safely — GitHub-only, hash-checked.
• TCP Bridge mode — the mode Route A is built on.
• Lag and desync fixes — if the picture stutters on hotel Wi-Fi.