Work out which mode you’re in first
The official manual’s connection troubleshooting is mode-specific — most “app is broken” reports are just the wrong checklist for the mode in use:
- AP mode (direct connection): your phone must be joined to the Go2’s own hotspot, not your home network. Check your phone’s Wi-Fi list for the robot’s AP and join it.
- Wi-Fi (router) mode: the network the robot is on must actually have internet access — a router with a dead upstream connection breaks the app even though Wi-Fi “looks” connected.
- 4G mode: verify the IoT card has data. In the app: Settings → Mobile Network.
Bluetooth binding fails
If the initial binding won’t complete: grant the Unitree Go app Bluetooth permission in your phone’s settings, make sure Bluetooth is on, and keep the phone physically close to the robot during binding.
The “connected but nothing responds” trap
The companion remote control and the app cannot control the robot at the same time. If the robot ignores every app command, exit side-follow mode and hold the remote’s power button for two seconds to switch the remote off — the app takes over immediately. This one masquerades as a connection failure constantly and costs owners hours.
After a firmware update
If the app crashes instantly when connecting right after a firmware update, that’s a different, documented problem — see our dedicated guide on post-update service settings.