The Android Debug Bridge (ADB) is a versatile command-line tool that lets you communicate with your device. Adb commands facilitate various device operations, such as installing and debugging applications, and provide access to the Unix shell, which can be used to run various commands on the device. It is a client-server program consisting of the following three components:
- Client: Used to send commands. The client runs on the development machine. You can invoke the client from the command line terminal by issuing adb commands.
- Daemon (ADBD) : Runs commands on the device. Daemons run as background processes on each device.
- Server: Manages communication between clients and daemons. The server runs as a background process on the development machine.
But the common problem is that ADB can’t connect, or other ADB driver issues, etc..
In fact, there is no such problem in Mac and Linux, but it is always easy for ADB to be disconnected in WIN. This article is mainly aimed at this problem. It is clear that the driver has been installed, but ADB can not find the device:
ADB can not find the device in AndroidStudio. Install the Google USB Driver
Next install the driver:
Find ADB Interface on other devices in Computer Management – Device Manager – because not only do you need to install Google USB Driver, but the ADB Driver should also have the ADB Driver download address
After downloading, unpack and click exe to install
Once installed, you’re done
Finally, due to the slow download of ADB driver, I also download over the wall, attached to the download link (this is the object storage repository of seven Niuyun) : adbdriver.zip