-
Notifications
You must be signed in to change notification settings - Fork 0
Command Reference
Babul Raj Singh edited this page Jul 26, 2026
·
1 revision
While the daemon is running (dart run bin\daemon.dart), its terminal window accepts single-letter commands. Type the letter and press Enter — there's no other interface yet.
| Command | Name | What it does |
|---|---|---|
w |
Go Wireless | Switches a USB-connected phone to Wi-Fi, guides you through hotspot/same-Wi-Fi setup, then connects automatically. Leaves the window alone otherwise — doesn't close the old USB window or recognize it's the same device. |
h |
Handoff | Same underlying wireless connection as w, but requires a mirror to already be running over USB, and automatically closes that USB window once the wireless one opens — feels like one continuous window, not two. |
u |
USB mode | Reverts every currently-ready device back to USB-only: disconnects any wireless address, or closes the TCP port on a device still attached over USB. |
l |
List | Prints every device the daemon currently knows about, its connection state, and whether it's mirroring. Check this before deciding what to do next. |
q |
Quit | Closes every scrcpy window and shuts the daemon down entirely. |
Both do the exact same underlying work — switch the phone to TCP mode, then connect over Wi-Fi. They only differ in what happens to the mirror window:
-
Already have a mirror running over USB, and just want it to keep going wirelessly without you doing anything else? Use
h(Handoff). -
Don't have a mirror open yet, or you'd rather manage the USB and wireless windows yourself? Use
w(Go Wireless).
Rule of thumb: mirror already running → h. No mirror yet, or you want manual control → w.
For w or h to succeed, one of two things has to be true when the daemon tries to connect:
- The phone's own hotspot is on, and this PC has joined it, or
- The phone and PC are already on the same Wi-Fi network.
There's no third option — adb has no way to discover a device on the network by itself. If neither of these is true, the daemon will keep retrying quietly and never succeed; check your Wi-Fi/hotspot connection if w or h seem stuck.