Android gamepad for Windows, over Wi-Fi
No Bluetooth pairing, no USB cable, no adapter. The phone and the PC talk over the network you already have.
Why Wi-Fi and not Bluetooth or USB
Bluetooth is not available to you. Presenting a phone as a Bluetooth HID gamepad requires the HID device role, which Android does not expose to ordinary apps. This is a platform restriction, not an oversight, and no amount of app-side cleverness gets around it without root.
USB works but tethers you to a cable long enough to reach the sofa, and puts the phone in a mode that fights with charging and file transfer.
Wi-Fi is already there, needs no pairing ritual, and on a normal home network is genuinely fast. Measured on a Galaxy S24 Ultra and a Windows 11 PC: 4.9–8.0 ms round trip, 249 packets per second, 0.0% loss across 42,805 consecutive packets.
How it presents to Windows
Windows never learns a phone is involved. A small program on the PC
creates a virtual Xbox 360 controller through the ViGEmBus driver, and
drives it from what the phone sends. The result appears in
joy.cpl, on an XInput slot, indistinguishable from a wired
pad — which is why there is nothing to configure per game.
That covers XInput, DirectInput, GameInput and the browser Gamepad API, which between them is essentially everything on Windows.
How it compares
| Approach | Latency | Catch |
|---|---|---|
| PhonePad over Wi-Fi | 4.9–8.0 ms | Needs a program running on the PC |
| A real Xbox controller (USB) | ~1–4 ms | Costs money, and is not in your pocket |
| A real controller (Bluetooth) | ~10 ms and up | Costs money; pairing is its own adventure |
| Key-mapping apps | Varies | Sends keystrokes, not controller input — analogue sticks and triggers do not survive the translation |
The PhonePad figures are from our own measurements, on our own hardware, with the method written down. The comparison figures are typical published values, not measurements we made.
What the 40 bytes contain
Sixteen button bits, four 16-bit stick axes, two 8-bit triggers, a session id, a sequence number, a timestamp and an authentication tag. Sent on every change plus an unconditional repeat, so a dropped packet is corrected within a few milliseconds by the next one rather than retransmitted — a re-sent stale input would be worse than a lost one.
That is about 10 KB/s at full rate, which is nothing on any network built this century.
What you need
- Windows 10 or 11
- Android 7 or newer, arm64
- Both on the same Wi-Fi network
- The ViGEmBus driver, installed once
A 5 GHz network is worth preferring, but 2.4 GHz works — the traffic is tiny, and what matters is congestion rather than bandwidth.
See also: using your phone as an Xbox controller, or Xbox Cloud Gaming.