Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4. For building and contributing to AOSP, we recommend utilizing android-latest-release instead of aosp-main. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. For more information, see Changes to AOSP.

Tools

In virtualized systems, the device can have multiple VMs with each running its own ADB daemon. In this case, the host VM can export an RNDIS Ethernet gadget, which can be used for the TCP/IP-based communications over the USB physical link. The development machine can then use ADB over TCP/IP to access multiple VMs on the device. The ADB daemon on the host side can announce the ADB presence on the guest VMs over mDNS by publishing ADB services. In addition, the development machine can browse these services with ADB tool, which supports mDNS device discovery (ADB version 31.0.2 or later) to get the IP address and the port number on which adb daemon is listening and then connect to the guest VMs.

The following commands can be used on the development machine to browse and connect to the ADB services.

To enable mDNS discovery, run:
Because ADB 31.0.2 disables mDNS discovery, you must enable mDNS discovery and then restart the ADB server.
```
export ADB_MDNS_OPENSCREEN=1
adb kill-server
adb start-server
```

To discover ADB services, run:

adb mdns services

List of discovered mdns services
driver_vm	_adb._tcp	192.168.1.49:4444
device_vm	_adb._tcp	192.168.1.49:3333

To connect to the device, run:
```
adb connect driver_vm._adb._tcp
```

To list the connected devices, run:

adb devices

List of devices attached
driver_vm._adb._tcp device

Tools Stay organized with collections Save and categorize content based on your preferences.

Tools