Appium automation test foundation ADB common commands (I)

Use adb The premise of the command is to ensure that the mobile phone or simulator is connected to the computer .
Use adb connect 127.0.0.1:+ Port number command , Link .

1、 Startup and shutdown adb service

In some cases , You may need to terminate and then start the server process , for example ADB When you don't respond to commands , You can solve the problem by restarting .
Start the command line terminal and execute the command ：
（1） start-up adb service ,adb command ： adb start-server.
（2） close adb service ,adb command ： adb kill-server.
demonstration ：

• start-up adb service

C:\Users\L>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Users\L>

Tips ： The daemon is not turned on , Now through 5037 Port open daemon service .
Be careful

• adb The default binding port of the command is 5037 , If the port is bound by another application, it cannot be started adb service .
• Generally, it is not necessary to execute this command manually , Running adb If you find adb server No startup will automatically start up .
• close adb service
  close adb The service doesn't have any tips .

2、 see adb edition

adb command ：adb version

C:\Users\L>adb version
Android Debug Bridge version 1.0.41
Version 29.0.6-6198805
Installed as F:\***\android-sdk-windows\platform-tools\adb.exe
C:\Users\L>

3、 Appoint adb server The network port of

adb command ：adb -P <port> start-server（ Temporarily change a port number to open adb service ）
The default port is 5037.

C:\Users\L>adb -P 5039 start-server
* daemon not running; starting now at tcp:5039
* daemon started successfully

C:\Users\L>

Tips ：

• netstat -ano Query process ID.
• taskkill /f /t /im Process name Kill the process .
  Such as ：taskkill /f /t /im nginx.exe

4、 Query connected devices / Simulator

adb command ：adb devices
Premise ：Android Simulator turned on .
demonstration ：
（1） Direct execution adb devices command

C:\Users\L>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

C:\Users\L>

You can see from above , If we don't start adb service , And directly execute adb devices command , Will automatically help us turn on adb service , In execution adb devices command , As a result, no linked simulators were queried .
（2） Use adb Service link Android Simulator
Carry out orders adb connect 127.0.0.1:21503（ notes ： Different simulators have different port numbers ）.

C:\Users\L> adb connect 127.0.0.1:21503
connected to 127.0.0.1:21503

C:\Users\L>

（3） Re execution adb devices command , Query connected devices

C:\Users\L>adb devices
List of devices attached
127.0.0.1:21503 device
C:\Users\L>

We can see adb The service has linked devices
explain ：
The output format is  [serialNumber] [state].
serialNumber That's what we call it SN code ,state There are the following ：

• offline —— Indicates that the device is not connected successfully or is not responding .
• device —— The device is connected . Note that this state does not identify Android The system is fully up and operational , During device startup, the device instance can be connected to adb, But the system can only be operated after startup .
• no device —— No equipment / Simulator connection .
  Common abnormal output ：

1. No equipment / The simulator is connected successfully .
   List of devices attached
2. equipment / Simulator is not connected to adb Or no response .
   List of devices attached cf264b8f offline

5、 Get Android version
adb command ：adb shell getprop ro.build.version.release
demonstration ：

C:\Users\L>adb shell getprop ro.build.version.release
7.1.2

C:\Users\L>

6、 Specify the target device for the command
If there are multiple devices / Simulator connection , You need to specify the target device for the command .

Parameters	meaning
-d	Specifies the current unique pass USB Connected Android The device is the command target
-e	Specify the currently unique running simulator as the command target
-s <serialNumber>	Specify the corresponding serialNumber Equipment No / The simulator is the command target

On multiple devices / When the simulator is connected, it is more commonly used to  -s <serialNumber>  Parameters ,serialNumber Can pass  adb devices  Command acquisition . Such as ：

$ adb devices

List of devices attached
cf264b8f    device
emulator-5554   device
10.129.164.6:5555   device

In the output  cf264b8f、emulator-5554  and  10.129.164.6:5555  That is to say serialNumber.
For example, I want to specify  cf264b8f  This device to run adb Command get screen resolution ：
adb -s cf264b8f shell wm size
If you want to give  10.129.164.6:5555  This device installs applications （ In this form serialNumber The format is <IP>:<Port>, It's usually a wireless device or Genymotion Wait for the third party Android Simulator ）：
adb -s 10.129.164.6:5555 install test.apk
Encounter multiple devices / The simulator uses these parameters to specify the target device for the command

a key ： Supporting learning materials and video teaching

So here I have carefully prepared the detailed information of the above outline in The link below is as follows