Support

Minimal setup path for ADB and Wi-Fi debugging

Start wired, confirm the device is visible, then switch to wireless debugging if that is part of your workflow. The goal here is speed and repeatability.

Buy the cable

Command flow

Local wired verification

adb start-server
adb devices
adb shell getprop ro.product.model
adb shell

Run the above first. If the device is not visible over cable, do not jump straight to wireless debugging assumptions.

Wireless handoff

Switch to Wi-Fi after the first wired session

adb tcpip 5555
adb shell ip addr show wlan0
adb connect <device-ip>:5555
adb devices

Replace `<device-ip>` with the address shown on the device network interface. Keep the device and workstation on the same network while testing.

Troubleshooting

If `adb devices` is empty

Re-seat the magnetic connector and confirm the USB port is providing a stable connection.
Restart the ADB server with `adb kill-server && adb start-server`.
Try a different port or hub if the host is underpowering the connection.
Confirm any device-side debug authorization prompt has been accepted.

Example projects

Repo links can be dropped in later without changing the page structure

Bench diagnostics examples
Wireless debugging quickstart repo
Automation scripts for repeated setup

No public repo links are wired in yet. This section is reserved so the storefront can grow without redesigning the information architecture.