connecting-over-wifi

Wireless ADB connection refused errors on Android 11+ usually happen when trying to connect to the pairing port instead of the separate post-pairing debug port. You must first run adb pair on the pairing IP:port, then connect to the debug port discovered via _adb-tls-connect._tcp mDNS services.

ADB v34+ defaults to Openscreen, causing mDNS backend mismatches if Bonjour is expected. Setting ADB_MDNS_OPENSCREEN resolves these wireless debugging discovery conflicts by enforcing the correct backend for adb mdns services to find _adb-tls-pairing._tcp entries.

To use wireless debugging, run adb pair with the IP and port shown on your device's Wireless debugging screen. Once paired, run adb connect using the separate connect IP:port listed under _adb-tls-connect._tcp from adb mdns services, not the pairing port.

Yes, wireless ADB supports legacy devices using the adb tcpip 5555 fallback followed by adb connect to the device IP. This bypasses the TLS-based pairing required for Android 11+ devices and does not rely on mDNS discovery.

mDNS discovery fails for Android TV or Wear OS if the platform requirements like API 33+ are unmet or corporate Wi-Fi restricts peer-to-peer traffic. Ensure ADB_MDNS_AUTO_CONNECT is configured and your network permits _adb-tls-connect._tcp traffic.

You should use adb disconnect to cleanly tear down the TLS connection and release the post-pairing debug port. Simply closing the terminal leaves the mDNS service hanging, which can cause port conflicts or connection refused errors on your next adb connect attempt.