Dropped or missed inputs on Wi-Fi: causes and fixes

Lag and lost inputs are two different problems. Lag means every press is a little late. A lost input means a press never reaches the game at all: a gear shift that does nothing, a jump that does not happen, a held trigger that lets go for a moment. Wi-Fi is a shared radio channel, and it can produce both. This guide explains the typical causes of missed inputs and what you can do about each.

What a missed input looks like

• A quick tap on a button does nothing, while a longer press works.
• Everything freezes for a fraction of a second and then catches up.
• A held trigger or stick briefly drops to zero.
• Inputs arrive in a burst after a pause, so a double-tap becomes a single press.

If these happen on Wi-Fi but never over USB, the link is the cause. Try the same game on a cable first. See how to connect over USB.

Cause 1: the PC's Wi-Fi card looks away

Windows periodically scans for other wireless networks, roughly once a minute. While it scans, the Wi-Fi card is tuned to other channels, and your controller's packets can wait 100 to 300 milliseconds. A card in power-saving mode has a similar habit: it sleeps between packets and wakes only when the router tells it to.

The GamepadOS PC server from version 2.1.4 addresses this directly. While at least one phone is connected over Wi-Fi it turns the background scan off and asks Windows for a streaming-friendly mode. It remembers your original settings, restores them when the phone disconnects or the server closes, and restores them on the next start if the server was stopped unexpectedly. No administrator rights are needed. Some wireless drivers ignore the streaming hint, but switching off the background scan is the part that removes the once-a-minute stall.

If you are on an older version, update the PC server. Even better, connect the PC to the router with an Ethernet cable and take its Wi-Fi card out of the picture.

Cause 2: packets arrive in a pile

After a pause, a router often delivers the packets it was holding all at once. If a program only keeps the last packet in a pile, a quick press and release that were both in the pile leave only the release behind, and the game sees nothing. The server now reads every packet in the pile, picks the newest by its timestamp rather than by arrival order, and still registers a button that was pressed somewhere inside the pile.

Cause 3: a press that is too short for the game

A game that reads the controller once per frame cannot see a button that went down and up between two reads. At 60 frames per second those reads are about 16 milliseconds apart. To avoid losing quick taps, the server keeps a pressed button down for at least 20 milliseconds, and the app on the phone sends a pressed button for at least 30 milliseconds. Sticks and triggers are never held back, so analog motion stays instant.

Cause 4: too little repetition for Wi-Fi

Because Wi-Fi can drop a packet, the app repeats each change a few times. In app version 1.4.8 it also resends the full controller state every 8 milliseconds while any input is active, and for a short while after a change, instead of every 33 milliseconds. A held trigger therefore keeps being refreshed and recovers quickly from a lost packet.

Cause 5: the phone is busy or throttled

A phone that is hot, low on battery or running heavy apps in the background can delay touch handling. Close other apps, keep the phone cool and charge it. A cable fixes this too, because it charges while you play.

Cause 6: interference and distance

A weak or crowded signal causes retries, and retries cause delays and drops. Sit closer to the router and use the 5 GHz or 6 GHz band. The ranking and the reasons are in how to reduce input lag.

Special case: the PC joined the phone's hotspot

Some people share their phone's mobile hotspot and connect the PC to it, so both devices sit on the phone's own network. This can work and keeps the radio traffic local, but the phone is then running both the hotspot and the controller, which makes it warm and busy. If you see missed inputs in this arrangement, move both devices onto a normal router, or use USB.

Special case: coming back from the recents screen

Android freezes an app that sits in the background. If you leave GamepadOS in recents for a while and return, the PC may have already dropped the pad. Newer versions of the server keep the secure session information for ten minutes, and the app now reconnects by itself if the Wi-Fi link goes quiet for several seconds. If it does not recover, tap the connection screen to reconnect, or scan the QR code again.

A checklist when inputs go missing

1. Update the PC server and the Android app to the latest versions.
2. Test on USB. If the problem disappears, the cause is the Wi-Fi link.
3. Put the PC on Ethernet if you can.
4. Use 5 GHz or 6 GHz and sit closer to the router.
5. Close background downloads on every device on the network.
6. Keep the phone cool, charged and free of heavy background apps.

If it still happens after all of this, send us a note through the contact form with your phone model, router model and what happens. Details like that let us find patterns.