connecting-over-wifi

Manage wireless Android Debug Bridge pairing and mDNS discovery for Android 11+ devices.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill connecting-over-wifi-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connecting-over-wifi
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/adb/devices/connecting-over-wifi
Command: npx skills add https://github.com/trancee/MeshLink-template --skill connecting-over-wifi-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the friction of connecting Android devices to ADB without physical USB cables, handling the complexities of modern TLS-based pairing and legacy TCP/IP connections.

Core Features & Use Cases

  • Modern Pairing: Automates the Android 11+ wireless debugging flow using pairing codes and QR-based TLS authentication.
  • mDNS Discovery: Simplifies device identification using Openscreen or Bonjour backends to find available debug services on the local network.
  • Use Case: Use this skill when you need to debug an Android 13 device over a local Wi-Fi network without a USB cable, or when you need to troubleshoot connection failures caused by network restrictions or mDNS configuration issues.

Quick Start

Use the connecting-over-wifi skill to pair with my device at 192.168.1.42 using the pairing code 123456 and then connect to the debug port.

Frequently Asked Questions about connecting-over-wifi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect to ADB over Wi-Fi without a USB cable?

To connect to ADB over Wi-Fi without a USB cable, use the wireless debugging feature on Android 11+ devices. This involves pairing the device using a TLS-encrypted pairing code and then connecting to the discovered debug port over the local network.

What is mDNS discovery for wireless debugging?

mDNS discovery for wireless debugging is the process of finding available Android debug services on a local network. It simplifies device identification by using Openscreen or Bonjour backends to automatically locate active wireless debugging ports.

Do I need a specific ADB version for Android 11 wireless pairing?

Yes, you need ADB v34 or higher for optimal mDNS backend compatibility during Android 11 wireless pairing. Proper network configuration is also required to ensure the modern TLS-encrypted pairing process completes successfully.

Can I use legacy TCP/IP debugging instead of TLS pairing?

Yes, you can use legacy TCP/IP debugging instead of TLS pairing. This skill supports both modern TLS-encrypted pairing workflows and legacy TCP/IP debugging connections to accommodate various network environments and older device workflows.

Why is my wireless ADB connection failing to find the device?

Your wireless ADB connection may be failing due to network restrictions or mDNS configuration issues. Troubleshooting involves verifying local network settings, ensuring proper mDNS backend support, and checking that the device's wireless debugging is active.

How do I pair an Android device using a pairing code?

To pair an Android device using a pairing code, initiate the wireless debugging flow and input the generated code along with the device's IP address and port. This automates the Android 11+ TLS authentication process.