connecting-to-devices

ADB commands fail with multiple devices when no transport is specified. Use adb devices -l to list transports, then target your intended device using -s SERIAL, -d for USB, -e for emulator, or -t TRANSPORT_ID to resolve the ambiguity.

To wait for a full Android boot, first use adb wait-for-device to block until the transport connects, then poll getprop sys.boot_completed until it returns 1, ensuring the OS is fully ready for test instrumentation.

Unauthorized or no permissions states in adb devices output indicate missing authorization or udev rules. Check adb devices -l output for these states and configure udev rules to grant the necessary USB permissions for the connected transport.

The canonical adb wait-for syntax is adb wait-for[-TRANSPORT]-STATE, where STATE corresponds to values like device, offline, or unauthorized. Specifying the transport and state ensures scripts block until the intended target reaches the required condition.

To select a specific emulator when multiple transports are active, run adb devices -l to identify available emulators, then use the -e flag for the emulator or -t TRANSPORT_ID to ensure commands route to the correct virtual device.

Yes, adb wait-for-device applies to wireless and TCP connections. List transports with adb devices, select the networked device using -s SERIAL or -t TRANSPORT_ID, and apply the canonical wait-for syntax to block until the wireless transport reaches the device state.