Wireless debugging troubleshooting

Why Android wireless debugging pairing fails

Most pairing failures happen because the temporary pairing dialog closed, the wrong port was entered, the code expired, or the network changed during pairing.

Check the pairing dialog first

  • Reopen “Pair device with pairing code” and leave the dialog visible.
  • Use the new six-digit code; an older code is no longer valid.
  • Enter the pairing port from that dialog, not the connection port shown on the main wireless debugging screen.
  • Use split-screen so Settings and Teralivo Setup remain open together.

Check the Wi-Fi connection

  • Keep the phone on the same Wi-Fi network throughout pairing.
  • Temporarily disable a VPN if it prevents local network communication.
  • Avoid guest Wi-Fi networks that isolate devices from each other.
  • Turn wireless debugging off and back on after changing networks.

Reset stale debugging state

  • Remove old paired devices from the wireless debugging screen when the list is cluttered.
  • Turn wireless debugging off, wait a few seconds, and enable it again.
  • Force close and reopen Teralivo Setup before generating a fresh code.
  • Restart the phone if Android continues returning connection-aborted or timeout errors.

Pairing succeeded but binding did not finish

Pairing and binding are separate stages. After pairing, keep Wi-Fi enabled while Teralivo connects, writes the device package, obtains a token, and starts the service. A timeout during this stage may require reconnecting, but it does not always mean the pairing itself failed.

Official references

Android documentation used for this guide