我在这里找到了答案:

Connect Android device and adb host computer to a common Wi-Fi network accessible to both. We have found that not all access points are suitable; you may need to use an access point whose firewall is configured properly to support adb. Connect the device with USB cable to host. Make sure adb is running in USB mode on host. $ adb usb restarting in USB mode Connect to the device over USB. $ adb devices List of devices attached ######## device Restart host adb in tcpip mode. $ adb tcpip 5555 restarting in TCP mode port: 5555 Find out the IP address of the Android device: Settings -> About tablet -> Status -> IP address. Remember the IP address, of the form #.#.#.#. sometimes its not possible to find the IP-address of the android device, as in my case. so u can get it using adb as the following: $ adb shell netcfg and the should be in the last line of the result. Connect adb host to device: $ adb connect #.#.#.# connected to #.#.#.#:5555 Remove USB cable from device, and confirm you can still access device: $ adb devices List of devices attached #.#.#.#:5555 device

现在可以开始了!

如果adb连接丢失:

确保你的主机仍然连接到你的Android设备所在的Wi-Fi网络。 再次执行“adb connect”步骤重新连接。 或者如果这不起作用，重置你的adb主机: 亚行kill-server

然后从头再来。

拉杜·西米内斯库的回答对我很管用。谢谢你！对于无法看到android设备ip地址的用户，请转到 >无线> Wi-Fi 然后长按已连接的wifi。然后选择“显示高级选项”上的“修改网络配置检查”，并滚动到IP地址部分。

在系统中安装adb后，请运行 Killadd adb和adb start-server 刷新adb。有时我们会遇到这样的问题

adb实用程序能够通过TCP/IP连接到设备。但是，adbd通常不会监听TCP连接。

如果您想让它运行，您需要一个工程设备(换句话说，您需要root)。然后按照这篇文章中的指导去做:

如何通过TCP连接到ADB的Android ?

由于这只适用于eng设备，所以它不受官方支持。使用风险自负，包括bug等。

最好和超级简单的方法是:-

制作批处理文件:-

亚洲开发银行设备 Adb tcpip 5555 adb connect 192.168.9.120:5555(您的电话ip xxx.xxx.x. com)。xxx: 5555)

将此文件放入android sdk platform-tool文件夹。 例子:C:\Users\当地的user_name \ AppData \ \ Android \ Sdk \平台工具 右键单击文件>发送到>桌面(创建快捷方式) 就是这样……

现在你只需要通过USB连接你的手机，然后打开桌面快捷方式，断开你的手机…

android无线调试(MAC)

步骤1:进入sdk文件夹(常用路径“/Users/macname/Library/Android/sdk/platform-tools”) 打开CMD，运行"adb devices" output -附加设备列表

如果在CMD类型中没有找到adb命令 。/亚洲开发银行——的帮助 OS X / macOS:典型的~/。Profile或~/.bash_profile 在这里添加以下一行，并将其替换为安装platform-tools的路径:

步骤2: $PATH ="/Users/macname/Library/Android/sdk/platform-tools"

步骤3: $ adb设备 所附设备清单 ZH99FF7FTY设备

步骤4: $ adb tcpip 5555 以TCP模式重新启动端口:5555

步骤5: $ adb connect 10.124.32.18:5555 已连接到10.124.32.18:5555

下次重复步骤4和5重新连接 或者如果设备重新启动但没有连接，请再次执行步骤 祝你好运

更新:

从Android Studio Bumblebee(2021.1.1)稳定版开始，你可以通过扫描二维码对设备进行Wifi调试。

引用博客文章:

通过Wi-Fi的ADB: Bumblebee包括一个简化的连接流程 你的Android 11和更高版本的设备通过Wi-Fi进行部署 使用ADB调试。在你的 的“物理”选项卡中选择“使用Wi-Fi动作的对” 新建设备管理器打开配对向导。然后按照下面的步骤 提供用于与通过同一网络连接的设备配对。学习 更多。

老帖:

有了新的Android 11，你可以在WiFi上调试你的应用程序，而完全不需要使用USB线。

引用自Android Studio用户指南

Connect to a device over Wi-Fi (Android 11+) Android 11 and higher support deploying and debugging your app wirelessly from your workstation using Android Debug Bridge (adb). For example, you can deploy your debuggable app to multiple remote devices without physically connecting your device via USB. This eliminates the need to deal with common USB connection issues, such as driver installation. To use wireless debugging, you need to pair your device to your workstation using a pairing code. Your workstation and device must be connected to the same wireless network. To connect to your device, follow these steps: On your workstation, update to the latest version of the SDK Platform-Tools. On the device, enable developer options. Enable the Wireless debugging option. On the dialog that asks Allow wireless debugging on this network?, click Allow. Select Pair device with pairing code. Take note of the pairing code, IP address, and port number displayed on the device (see image). On your workstation, open a terminal and navigate to android_sdk/platform-tools. Run adb pair ipaddr:port. Use the IP address and port number from step 5. When prompted, enter the pairing code that you received in step 5. A message indicates that your device has been successfully paired. none Enter pairing code: 482924 Successfully paired to 192.168.1.130:37099 [guid=adb-235XY] (For Linux or Microsoft Windows only) Run adb connect ipaddr:port. Use the IP address and port under Wireless debugging.