Google’s ADB Wi-Fi 2.0 boosts wireless debugging speeds by 66%

ADB Wi-Fi lets developers connect an Android device to a computer without keeping a USB cable plugged in. The convenience is obvious, but wireless debugging has had an annoying weakness where connections could disappear when the device changed networks, went offline or the underlying discovery service stopped working correctly.

Google is addressing those problems by rebuilding three parts of the system: the adb server, the adbd daemon running on the Android device, and Android Studio.

ADB Wi-Fi gets a new discovery stack

The most technical change happens in the device discovery layer. Google has introduced a new mDNS stack, replacing the older Bonjour and legacy mDNS components. mDNS is what allows devices and services on a local network to find each other. If that discovery process fails, a phone can effectively vanish from the developer's workstation even though both devices are still connected to Wi-Fi.

ADB Wi-Fi 2.0 also gets smarter network handling through adbd. When Android detects that the device has moved onto an untrusted network, wireless ADB can automatically switch itself off. Once the device returns to a network that the user has allowed, the feature can automatically become available again.

That should be useful for developers who regularly move between home, office and other networks. Instead of manually managing the wireless debugging state after every network change, Android can now react to the connection environment itself.

Android Studio makes wireless devices easier to find

Google has also made pairing easier to find inside Android Studio. Once wireless debugging is enabled on an Android device, the device name can appear directly in Android Studio's Device Manager. Developers can therefore discover the handset from the same interface they use for other connected devices.

The update is not restricted to phones. Google says ADB Wi-Fi 2.0 works with Android phones and tablets, Wear OS watches and Android TV devices.

The 66% speed improvement is the headline figure, but reliability may be the more useful change during everyday development. Google reports a 32% improvement in automatic connection success, potentially reducing the number of times developers have to reconnect or re-pair a device during testing.

The actual performance will depend on the device and network, so the maximum figures should not be expected on every setup. Still, Google has tackled the problem at several layers instead of simply changing the pairing interface.

What users need to do

Developers should update to compatible Android Studio and ADB versions, enable Wireless debugging on the Android device and look for the device in Android Studio's Device Manager. The computer and Android device should also be connected to a trusted network.