Repository: mzlogin/awesome-adb
Branch: master
Commit: c99848d362eb
Files: 10
Total size: 188.2 KB
Directory structure:
gitextract_71oj42wk/
├── .github/
│ └── FUNDING.yml
├── .gitignore
├── LICENSE
├── README.en.md
├── README.md
└── related/
├── aapt.md
├── am.md
├── dumpsys.md
├── pm.md
└── uiautomator.md
================================================
FILE CONTENTS
================================================
================================================
FILE: .github/FUNDING.yml
================================================
# These are supported funding model platforms
github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
patreon: # Replace with a single Patreon username
open_collective: # Replace with a single Open Collective username
ko_fi: # Replace with a single Ko-fi username
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
liberapay: # Replace with a single Liberapay username
issuehunt: # Replace with a single IssueHunt username
otechie: # Replace with a single Otechie username
lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
custom: https://mazhuang.org/donate/
================================================
FILE: .gitignore
================================================
*.swp
.DS_Store
================================================
FILE: LICENSE
================================================
The MIT License (MIT)
Copyright (c) 2016 Zhuang Ma
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
================================================
FILE: README.en.md
================================================
# 
The [Android Debug Bridge](https://developer.android.com/studio/command-line/adb.html) (ADB) is a toolkit included in the Android SDK package, it is not only a powerful tool for Android developers and testers, but also a good toy for Android fans.
This repository renews continually, Pull Requests and Issues are welcomed. If you found [this](https://github.com/mzlogin/awesome-adb) is useful, you can star it and conveniently back here to view when necessary.
**Note:** Some commands may depending on the version of Android system or ROM.
Other languages: [:cn: Chinese](./README.md)
# 
<!-- vim-markdown-toc GFM -->
* [Basic Usage](#basic-usage)
* [Command syntax](#command-syntax)
* [Targeting equipment for command](#targeting-equipment-for-command)
* [Start/Stop](#startstop)
* [View adb version](#view-adb-version)
* [Run adbd as root](#run-adbd-as-root)
* [Designated adb server network port](#designated-adb-server-network-port)
* [Device connection management](#device-connection-management)
* [Inquiries connected device / simulator](#inquiries-connected-device--simulator)
* [USB connection](#usb-connection)
* [Wireless connection (Android11+)](#wireless-connection-android11)
* [Wireless connection (need to use the USB cable)](#wireless-connection-need-to-use-the-usb-cable)
* [Wireless connection (without using the USB cable)](#wireless-connection-without-using-the-usb-cable)
* [Application Management](#application-management)
* [Check the list of](#check-the-list-of)
* [All applications](#all-applications)
* [system applications](#system-applications)
* [third-party usage](#third-party-usage)
* [Application package name contains a string](#application-package-name-contains-a-string)
* [Install APK](#install-apk)
* [Uninstalling](#uninstalling)
* [Disable or enable apps](#disable-or-enable-apps)
* [Disable apps](#disable-apps)
* [Enable apps](#enable-apps)
* [Clear app cache data](#clear-app-cache-data)
* [View Reception Activity](#view-reception-activity)
* [View Running Services](#view-running-services)
* [Query package detail information](#query-package-detail-information)
* [Query application installation path](#query-application-installation-path)
* [Interact with Applications](#interact-with-applications)
* [Launch app / Start an Activity](#launch-app--start-an-activity)
* [Start a Service](#start-a-service)
* [Stop service](#stop-service)
* [Send a broadcast](#send-a-broadcast)
* [Force stop an application](#force-stop-an-application)
* [Trim memory](#trim-memory)
* [File Management](#file-management)
* [Copy files from a device to a computer](#copy-files-from-a-device-to-a-computer)
* [Copy files from a computer to a device](#copy-files-from-a-computer-to-a-device)
* [Analog Keys / inputs](#analog-keys--inputs)
* [Power button](#power-button)
* [menu](#menu)
* [HOME key](#home-key)
* [return key](#return-key)
* [volume control](#volume-control)
* [Media Control](#media-control)
* [On / Off screen](#on--off-screen)
* [Slide to unlock](#slide-to-unlock)
* [Enter text](#enter-text)
* [View Log](#view-log)
* [Android log](#android-log)
* [Filter the log by level](#filter-the-log-by-level)
* [Filter by tag and log level](#filter-by-tag-and-log-level)
* [Log format](#log-format)
* [Clear log](#clear-log)
* [Kernel log](#kernel-log)
* [View device information](#view-device-information)
* [Model](#model)
* [Battery Status](#battery-status)
* [Screen Resolution](#screen-resolution)
* [Screen density](#screen-density)
* [Display Parameters](#display-parameters)
* [android\_id](#android_id)
* [IMEI](#imei)
* [Android system version](#android-system-version)
* [IP address](#ip-address)
* [Mac Address](#mac-address)
* [CPU Information](#cpu-information)
* [Memory Information](#memory-information)
* [More hardware and system properties](#more-hardware-and-system-properties)
* [Modify Settings](#modify-settings)
* [Resolution](#resolution)
* [Screen density](#screen-density-1)
* [Overscan](#overscan)
* [Turn off Android Debug](#turn-off-android-debug)
* [allow/forbidden access non SDK API](#allowforbidden-access-non-sdk-api)
* [Show/hide status bar or navigation bar](#showhide-status-bar-or-navigation-bar)
* [Utility functions](#utility-functions)
* [Screenshots](#screenshots)
* [Recording Screen](#recording-screen)
* [Remount system partition as writable](#remount-system-partition-as-writable)
* [Check connection over WiFi password](#check-connection-over-wifi-password)
* [To set the system date and time](#to-set-the-system-date-and-time)
* [restart cellphone](#restart-cellphone)
* [Detect whether the device is root](#detect-whether-the-device-is-root)
* [Monkey use stress testing](#monkey-use-stress-testing)
* [On / off WiFi](#on--off-wifi)
* [Flashing-Phone related commands](#flashing-phone-related-commands)
* [Restart to Recovery mode](#restart-to-recovery-mode)
* [To restart from the Recovery Android](#to-restart-from-the-recovery-android)
* [Restart to Fastboot mode](#restart-to-fastboot-mode)
* [Through sideload system update](#through-sideload-system-update)
* [Security-related commands](#security-related-commands)
* [Enable / Disable SELinux](#enable--disable-selinux)
* [Enable / Disable dm_verity](#enable--disable-dm_verity)
* [More adb shell command](#more-adb-shell-command)
* [See process](#see-process)
* [View real-time resource consumption](#view-real-time-resource-consumption)
* [query process uid](#query-process-uid)
* [Other](#other)
* [common problem](#common-problem)
* [Start adb server failure](#start-adb-server-failure)
* [com.android.ddmlib.AdbCommandRejectedException](#comandroidddmlibadbcommandrejectedexception)
* [adb unofficial implementation](#adb-unofficial-implementation)
* [related commands](#related-commands)
* [Acknowledgements](#acknowledgements)
* [Reference Links](#reference-links)
<!-- vim-markdown-toc -->
## Basic Usage
### Command syntax
adb basic syntax of the command is as follows:
```sh
adb [-d|-e|-s <serialNumber>] <command>
```
If only one device / emulator connection, you can omit the `[-d | -e | -s <serialNumber>]` this part, the direct use `adb <command>`.
### Targeting equipment for command
If you have more than one device / emulator connection, you need to specify the target device for the command.
| Parameter | Meaning |
|---------------------|-----------------------------------------------------------------------------------|
| -d | Specifies currently the only Android device USB connector as the command target |
| -e | Specify currently the only goal for the command to run the simulator |
| `-s <SerialNumber>` | Specifies the device number corresponding serialNumber / simulator command target |
In the case of multiple devices / simulators are connected to the more common `-s <serialNumber>` parameters, serialNumber can be obtained through `adb devices` command. Such as:
```sh
$ adb devices
List of devices attached
cf264b8f device
emulator-5554 device
```
Output in the `cf264b8f` and` emulator-5554` is serialNumber. For example, this time I want to specify `cf264b8f` this equipment to run the adb command to take a screen resolution:
```sh
adb -s cf264b8f shell wm size
```
Encountered multiple devices / simulators use the case of these parameters for the command to specify the target device, hereinafter to simplify the description will not be repeated.
### Start/Stop
Start adb server command:
```sh
adb start-server
```
(Generally no need to manually execute this command, when you run the command adb adb server if found does not start automatically from the transfer.)
Stop adb server command:
```sh
adb kill-server
```
### View adb version
command:
```sh
adb version
```
Sample output:
```sh
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android
```
### Run adbd as root
The operating principle is adb adb server daemon and the phone side PC side adbd establish a connection, then the PC side adb client via adb server forward command parsing after running adbd receive commands.
So if adbd ordinary rights to perform some require root privileges to execute the command can not be directly used `adb xxx` execution. Then you can then execute the command `adb shell` after` su`, but also allows adbd root privileges to perform this high privilege can execute arbitrary commands.
command:
```sh
adb root
```
Normal output:
```sh
restarting adbd as root
```
Now run `adb shell`, take a look at the command line prompt is not turned into a` `#?
After some phone root can not let adbd by `adb root` execute commands with root privileges, some models such as Samsung, will be prompted to` adbd can not run as root in production builds`, then you can install adbd Insecure, then `adb root` try.
Accordingly, if you want to restore adbd non-root privileges, you can use `adb unroot` command.
### Designated adb server network port
command:
```sh
adb -P <port> start-server
```
The default port is 5037.
## Device connection management
### Inquiries connected device / simulator
command:
```sh
adb devices
```
Example output:
```sh
List of devices attached
cf264b8f device
emulator-5554 device
```
Output format is `[serialNumber] [state]`, serialNumber that is, we often say that the SN, state the following categories:
* `Offline` - indicates that the device is not connected to the success or unresponsive.
* `Device` - device is connected. Note that this state does not identify the Android system has been fully activated and operational in the device during startup device instance can be connected to the adb, but after boot the system before it becomes operational.
* `No device` - no device / emulator connection.
The output shows the current connected the two devices / simulators, `cf264b8f` and` emulator-5554` are they SN. As can be seen from the `emulator-5554` name it is an Android emulator.
Common alarm output:
1. No device / emulator connection is successful.
```sh
List of devices attached
```
2. The device / emulator is not connected to adb or unresponsive.
```sh
List of devices attached
cf264b8f offline
```
### USB connection
USB connection normal use adb by the need to ensure that:
1. Hardware status is normal.
Including Android devices in the normal power state, USB cable and interface intact.
Developer Options 2. Android devices and USB debugging mode is on.
You can go to the "Settings" - "Developer options" - "Android Debug" view.
If you can not find the developer options in the settings, it needs to make it through an egg is displayed: In the "Settings" - "About phone" continuous click "version number" 7 times.
3. The device driver is normal.
It seems to worry about the Linux and Mac OS X, the Windows likely to be encountered in the case of the need to install drivers, this can be confirmed right "Computer" - "Properties", the "Device Manager" in view on related equipment Is there a yellow exclamation point or question mark, if not explain the driving state has been good. Otherwise, you can download a mobile assistant class program to install the driver first.
4. Status after confirmation via USB cable connected computers and devices.
```sh
adb devices
```
If you can see
```sh
xxxxxx device
```
Description Connection successful.
### Wireless connection (Android11+)
[Doc in Android developers](https://developer.android.com/studio/command-line/adb#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:
1. Update to the latest version of the [SDK Platform-Tools](https://developer.android.com/studio/releases/platform-tools).
2. Connect Android device to run adb computer connected to the same local area network, such as connected to the same WiFi.
3. Enable the **Wireless debugging** option.
4. On the dialog that asks **Allow wireless debugging on this network?**, click **Allow**.
5. Select **Pair device with pairing code**. Take note of the pairing code, IP address, and port number displayed on the device.
6. On your workstation, open a terminal and navigate to `android_sdk/platform-tools`.
7. Run `adb pair ipaddr:port`. Use the IP address and port number from step 5.
8. When prompted, enter the pairing code that you received in step 5. A message indicates that your device has been successfully paired.
```sh
none
Enter pairing code: xxxxxx
Successfully paired to ...
```
9. (For Linux or Microsoft Windows only) Run `adb connect ipaddr:port`. Use the IP address and port under **Wireless debugging**.
### Wireless connection (need to use the USB cable)
In addition to the USB connection to the computer to use adb, can also be a wireless connection - although the connection process is also step using USB needs, but after a successful connection to your device can get rid of the limit of the USB cable within a certain range it !
Steps:
1. Connect Android device to run adb computer connected to the same local area network, such as connected to the same WiFi.
2. The device connected to the computer via a USB cable.
Make sure the connection is successful (you can run `adb devices` see if you can list the device).
3. Allow the device listens on port 5555 TCP / IP connections:
```sh
adb tcpip 5555
```
4. Disconnect the USB connection.
5. Find the IP address of the device.
Generally the 'Settings' in - "About phone" - "state information" - "IP address" is found, you can also use the following in the [View device information - IP address][1] a Lane method adb command.
6. Connect the device via IP address.
```sh
adb connect <device-ip-address>
```
Here `<device-ip-address>` is the IP address of the device found in the previous step.
7. Confirm the connection status.
```sh
adb devices
```
If you can see
```sh
<device-ip-address>:5555 device
```
Description Connection successful.
If you can not connect, verify that Android devices and the computer is connected to the same WiFi, then execute `adb connect <device-ip-address>` that step again;
If that does not work, by `adb kill-server` restart the adb and then try it all over again.
**The wireless connection**
command:
```sh
adb disconnect <device-ip-address>
```
### Wireless connection (without using the USB cable)
**Note: You need root privileges.**
On a "wireless connection (need to use USB cable)" method is described in official documents, need the help of a USB cable to enable the wireless connection.
Since we want to achieve a wireless connection, it can all step down are wireless it? The answer is energy.
1. Install a terminal emulator on the Android device.
Equipment already installed you can skip this step. Terminal emulator download address I use is: [Terminal Emulator for Android Downloads](https://jackpal.github.io/Android-Terminal-Emulator/)
2. To run the Android device and computer adb is connected to the same local area network, such as connected to the same WiFi.
3. Open a terminal emulator on your Android device, in which run the command sequence:
```sh
su
setprop service.adb.tcp.port 5555
```
4. Find the IP address of the Android device.
Generally the 'Settings' in - "About phone" - "state information" - "IP address" is found, you can also use the following in the [View device information - IP address][1] a Lane method adb command.
5. Connect Android device on a computer via adb and IP addresses.
```sh
adb connect <device-ip-address>
```
Here `<device-ip-address>` is the IP address of the device found in the previous step.
If you can see `connected to <device-ip-address>: 5555` such output indicates a successful connection.
* Notice: *
Some device may not working unless you restart adbd service, so you need to run command on the device's terminal as below
```sh
restart adbd
```
if `restart` is not working, try following command:
```sh
stop adbd
start adbd
```
## Application Management
### Check the list of
Check the list of basic commands format
```sh
adb shell pm list packages [-f] [-d] [-e] [-s] [-3] [-i] [-u] [--user USER_ID] [FILTER]
```
That is the basis of `adb shell pm list packages` can add some parameters on the filter to view different lists, supports filtering parameters are as follows:
| Parameter | display list |
|------------|------------------------------------------|
| No | all applications |
| -f | Display apk file application association |
| -d | Show only applications disabled |
| -e | Show only enabled applications |
| -s | Display only System |
| -3 | Show only third-party application |
| -i | Display applications installer |
| -u | Contains uninstall applications |
| `<FILTER>` | package name contains `<FILTER>` strings |
#### All applications
command:
```sh
adb shell pm list packages
```
Example output:
```sh
package:com.android.smoketest
package:com.example.android.livecubes
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.providers.calendar
package:com.android.providers.media
package:com.android.protips
package:com.android.documentsui
package:com.android.gallery
package:com.android.externalstorage
...
// other packages here
...
```
#### system applications
command:
```sh
adb shell pm list packages -s
```
#### third-party usage
command:
```sh
adb shell pm list packages -3
```
#### Application package name contains a string
For example, to view a list of package names that contain the string `mazhuang` applications, order:
```sh
adb shell pm list packages mazhuang
```
Of course, you can also use grep to filter:
```sh
adb shell pm list packages | grep mazhuang
```
### Install APK
Format:
```sh
adb install [-lrtsdg] <path_to_apk>
```
parameter:
`Adb install` may be followed by some optional parameters to control the behavior of the installation APK, available parameters and their meanings are as follows:
| Parameter | Meaning |
|----------------------|------------------------------------------------------------------------------------------------------------|
| -l | Will be applied to protect the installation directory / mnt / asec |
| -r | Allowed to cover the installation |
| -t | Allowed to install application specified in AndroidManifest.xml `android: testOnly =" true "` Application |
| -s | Install apps to sdcard |
| -d | Downgrade coverage allows installation |
| -g | Grant all runtime permissions |
| --abi abi-identifier | Force install an apk for a specific ABI, abi-identifier could be armeabi-v7a、arm64-v8a、v86、x86_64, etc. |
After you run the command to see if similar to the following output (status is `Success`) represents the installation was successful:
```sh
[100%] /data/local/tmp/1.apk
pkg: /data/local/tmp/1.apk
Success
```
The above is the output of adb current latest version v1.0.36, it will push apk file to display the progress of the percentage of mobile phones.
Using older versions of adb output is this:
```sh
12040 KB/s (22205609 bytes in 1.801s)
pkg: /data/local/tmp/SogouInput_android_v8.3_sweb.apk
Success
```
If the status is `Failure` said installation failure, such as:
```sh
[100%] /data/local/tmp/map-20160831.apk
pkg: /data/local/tmp/map-20160831.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
```
Common Installation failed output code, the meaning and possible solutions are as follows:
| Output | Meaning | solutions |
|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
| INSTALL\_FAILED\_ALREADY\_EXISTS | application already exists | use `-r` parameters |
| INSTALL\_FAILED\_INVALID\_APK | invalid APK file | |
| INSTALL\_FAILED\_INVALID\_URI | invalid filename APK | APK file names to ensure no Chinese |
| INSTALL\_FAILED\_INSUFFICIENT\_STORAGE | lack of space | cleanup space |
| INSTALL\_FAILED\_DUPLICATE\_PACKAGE | program of the same name already exists | |
| INSTALL\_FAILED\_NO\_SHARED\_USER | shared user requested does not exist | |
| INSTALL\_FAILED\_UPDATE\_INCOMPATIBLE | already installed the app, but signature is not the same; or uninstalled, but data is not removed. | |
| INSTALL\_FAILED\_SHARED\_USER\_INCOMPATIBLE | shared user request exists but the signatures do not match | |
| INSTALL\_FAILED\_MISSING\_SHARED\_LIBRARY | installation package used on the device unusable shared library | |
| INSTALL\_FAILED\_REPLACE\_COULDNT\_DELETE | can not be deleted when replacing | |
| INSTALL\_FAILED\_DEXOPT | dex optimization validation failure or lack of space | |
| INSTALL\_FAILED\_OLDER\_SDK | equipment system version is lower than the application requirements | |
| INSTALL\_FAILED\_CONFLICTING\_PROVIDER | equipment already exists with the same name in application content provider | |
| INSTALL\_FAILED\_NEWER\_SDK | equipment system version higher than the application requirements | |
| INSTALL\_FAILED\_TEST\_ONLY | test-only applications, but when you install `-t` parameter is not specified | |
| INSTALL\_FAILED\_CPU\_ABI\_INCOMPATIBLE | contains incompatible device CPU Application Binary Interface for native code | |
| INSTALL\_FAILED\_MISSING\_FEATURE | application uses device features that are unavailable | |
| INSTALL\_FAILED\_CONTAINER\_ERROR | sdcard access failure | confirm sdcard is available, or to install built-in storage |
| INSTALL\_FAILED\_INVALID\_INSTALL\_LOCATION | can not be installed to the specified location | switch mounting position, add or delete `-s` parameters |
| INSTALL\_FAILED\_MEDIA\_UNAVAILABLE | installation location is unavailable | generally sdcard, confirm sdcard is available or to install built-in storage |
| INSTALL\_FAILED\_VERIFICATION\_TIMEOUT | Installation Timeout verify | |
| INSTALL\_FAILED\_VERIFICATION\_FAILURE | verify the installation package fails | |
| INSTALL\_FAILED\_PACKAGE\_CHANGED | calling application program expects inconsistent | |
| INSTALL\_FAILED\_UID\_CHANGED | previously installed the app, and this assignment UID inconsistent | remove residual files previously installed |
| INSTALL\_FAILED\_VERSION\_DOWNGRADE | already installed the application later | use `-d` parameters |
| INSTALL\_FAILED\_PERMISSION\_MODEL\_DOWNGRADE | installed target SDK runtime support for application permissions of the same name, to install the runtime version does not support permission | |
| INSTALL\_PARSE\_FAILED\_NOT\_APK | specified path is not a file or not to `.apk` end | |
| INSTALL\_PARSE\_FAILED\_BAD\_MANIFEST | unresolved AndroidManifest.xml file | |
| INSTALL\_PARSE\_FAILED\_UNEXPECTED\_EXCEPTION | parser encounters an exception | |
| INSTALL\_PARSE\_FAILED\_NO\_CERTIFICATES | installation package is not signed | |
| INSTALL\_PARSE\_FAILED\_INCONSISTENT\_CERTIFICATES | already installed the app, and signed with the APK files are inconsistent | first uninstall the application on the device, then install |
| INSTALL\_PARSE\_FAILED\_CERTIFICATE\_ENCODING | encountered while parsing APK file `CertificateEncodingException` | |
| INSTALL\_PARSE\_FAILED\_BAD\_PACKAGE\_NAME | manifest file no or an invalid package name | |
| INSTALL\_PARSE\_FAILED\_BAD\_SHARED\_USER\_ID | manifest file specifies an invalid shared user ID | |
| INSTALL\_PARSE\_FAILED\_MANIFEST\_MALFORMED | encountered while parsing file manifest error structural | |
| INSTALL\_PARSE\_FAILED\_MANIFEST\_EMPTY | in the manifest file can not be found to find operable label (instrumentation or application) | |
| INSTALL\_FAILED\_INTERNAL\_ERROR | installation fails because of system problems | |
| INSTALL\_FAILED\_USER\_RESTRICTED | Users are limited to installing applications | open options 'install app via USB' in developer options, if it was opened, close and reopen it |
| INSTALL\_FAILED\_DUPLICATE\_PERMISSION | application attempts to define an existing permission name | |
| INSTALL\_FAILED\_NO\_MATCHING\_ABIS | applications include device application binary interface does not support the native code | |
| INSTALL\_CANCELED\_BY\_USER | applications installed on the device needs confirmation, but not operate the device or the point of cancellation | agree to install on the device |
| INSTALL\_FAILED\_ACWF\_INCOMPATIBLE | applications are not compatible with the device | |
| INSTALL_FAILED_TEST_ONLY | APK file is build via Android Studio 'RUN' | Rebuild via Gradle assembleDebug or assembleRelease, or Generate Signed APK |
| INSTALL_FAILED_ABORTED: User rejected permissions | applications installed on the device has risk tips, needs confimation, but no operate or canceled | agree to install on the device |
| Does not contain AndroidManifest.xml | invalid APK file | |
| Is not a valid zip file | invalid APK file | |
| Offline | device is not connected successfully | first device with adb successful connection |
| Unauthorized | unauthorized device allows debugging | |
| Error: device not found | not successfully connected equipment | equipment and adb first successful connection |
| Protocol failure | device is disconnected | first device with adb successful connection |
| Unknown option: -s | Android 2.2 does not support the following installation to sdcard | do not use `-s` parameters |
| No space left on device | lack of space | cleanup space |
| Permission denied ... sdcard ... | sdcard unavailable | |
| signatures do not match the previously installed version; ignoring! | already installed this app, but signatures do not match | uninstall previous installed, then install this one |
Reference: [PackageManager.java](https://github.com/android/platform_frameworks_base/blob/master/core%2Fjava%2Fandroid%2Fcontent%2Fpm%2FPackageManager.java)
*`Adb install` internal principle Introduction*
`Adb install` actually three steps:
1. push apk files to / data / local / tmp.
2. Call pm install installation.
3. Delete the corresponding apk file / data / local / tmp under.
Therefore, when necessary, according to this step, manually step through the installation process.
### Uninstalling
command:
```sh
adb uninstall [-k] <packagename>
```
`<Packagename>` represents the application package name, `-k` optional parameter indicates uninstall the application but keep the data and cache directories.
Command Example:
```sh
adb uninstall com.qihoo360.mobilesafe
```
Uninstall represents 360 mobile guards.
### Disable or enable apps
List all apps enabled:
```sh
adb shell pm list packages -e
```
#### Disable apps
command:
```sh
adb shell pm disable-user <packagename>
```
Command Example:
```sh
adb shell pm disable-user com.qihoo360.mobilesafe
```
#### Enable apps
command:
```sh
adb shell pm enable <packagename>
```
Command Example:
```sh
adb shell pm enable com.qihoo360.mobilesafe
```
### Clear app cache data
command:
```sh
adb shell pm clear <packagename>
```
`<Packagename>` represents the name of the application package, the effect of this command is equivalent to the application information in the settings screen, click the "Clear Cache" and "Clear data."
Command Example:
```sh
adb shell pm clear com.qihoo360.mobilesafe
```
360 mobile guards to clear the data and cache.
### View Reception Activity
command:
```sh
adb shell dumpsys activity activities | grep mResumedActivity
```
Example output:
```sh
mResumedActivity: ActivityRecord{8079d7e u0 com.cyanogenmod.trebuchet/com.android.launcher3.Launcher t42}
```
Where `com.cyanogenmod.trebuchet / com.android.launcher3.Launcher` is currently in the foreground Activity.
*The command above may not valid in Windows, you can try `adb shell dumpsys activity activities | findstr mResumedActivity` or `adb shell "dumpsys activity activities | grep mResumedActivity"`.
### View Running Services
command:
```sh
adb shell dumpsys activity services [<packagename>]
```
`<packagename>` parameter is optional, command with `<packagename>` will output services related with that packagename, and command without `<packagename>` will output all services.
Complete packagename is unnecessary. For example, `adb shell dumpsys activity services org.mazhuang` will output services related with `org.mazhuang.demo1`, `org.mazhuang.demo2` and `org.mazhuang123`, etc.
### Query package detail information
command:
```sh
adb shell dumpsys package <packagename>
```
There are many infos in output, include Activity Resolver Table, Registered ContentProviders, package name, userId, files/resources/codes path after install, version name and code, permissions info and their granted status, signing version, etc.
`<packagename>` is package name of an application.
Example output:
```sh
Activity Resolver Table:
Non-Data Actions:
android.intent.action.MAIN:
5b4cba8 org.mazhuang.guanggoo/.SplashActivity filter 5ec9dcc
Action: "android.intent.action.MAIN"
Category: "android.intent.category.LAUNCHER"
AutoVerify=false
Registered ContentProviders:
org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider:
Provider{7a3c394 org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider}
ContentProvider Authorities:
[org.mazhuang.guanggoo.fileProvider]:
Provider{7a3c394 org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider}
applicationInfo=ApplicationInfo{7754242 org.mazhuang.guanggoo}
Key Set Manager:
[org.mazhuang.guanggoo]
Signing KeySets: 501
Packages:
Package [org.mazhuang.guanggoo] (c1d7f):
userId=10394
pkg=Package{55f714c org.mazhuang.guanggoo}
codePath=/data/app/org.mazhuang.guanggoo-2
resourcePath=/data/app/org.mazhuang.guanggoo-2
legacyNativeLibraryDir=/data/app/org.mazhuang.guanggoo-2/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=74 minSdk=15 targetSdk=25
versionName=1.1.74
splits=[base]
apkSigningVersion=2
applicationInfo=ApplicationInfo{7754242 org.mazhuang.guanggoo}
flags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
privateFlags=[ RESIZEABLE_ACTIVITIES ]
dataDir=/data/user/0/org.mazhuang.guanggoo
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
timeStamp=2017-10-22 23:50:53
firstInstallTime=2017-10-22 23:50:25
lastUpdateTime=2017-10-22 23:50:55
installerPackageName=com.miui.packageinstaller
signatures=PackageSignatures{af09595 [53c7caa2]}
installPermissionsFixed=true installStatus=1
pkgFlags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
requested permissions:
android.permission.READ_PHONE_STATE
android.permission.INTERNET
android.permission.ACCESS_NETWORK_STATE
android.permission.ACCESS_WIFI_STATE
android.permission.READ_LOGS
android.permission.WRITE_EXTERNAL_STORAGE
android.permission.READ_EXTERNAL_STORAGE
install permissions:
android.permission.INTERNET: granted=true
android.permission.ACCESS_NETWORK_STATE: granted=true
android.permission.ACCESS_WIFI_STATE: granted=true
User 0: ceDataInode=1155675 installed=true hidden=false suspended=false stopped=true notLaunched=false enabled=0
gids=[3003]
runtime permissions:
android.permission.READ_EXTERNAL_STORAGE: granted=true
android.permission.READ_PHONE_STATE: granted=true
android.permission.WRITE_EXTERNAL_STORAGE: granted=true
User 999: ceDataInode=0 installed=false hidden=false suspended=false stopped=true notLaunched=true enabled=0
gids=[3003]
runtime permissions:
Dexopt state:
[org.mazhuang.guanggoo]
Instruction Set: arm64
path: /data/app/org.mazhuang.guanggoo-2/base.apk
status: /data/app/org.mazhuang.guanggoo-2/oat/arm64/base.odex [compilation_filter=speed-profile, status=kOatUpToDa
te]
```
### Query application installation path
command:
```
adb shell pm path <PACKAGE>
```
Output shows application installation path.
Example output:
```
adb shell pm path ecarx.weather
package:/data/app/ecarx.weather-1.apk
```
## Interact with Applications
The most used syntax for interacting with applications is :
```sh
am <command>
```
The common commands for `<command>` are as follow:
| Command | Use |
|-----------------------------------|------------------------------------------------------|
| `start [options] <INTENT>` | Start an Activity specified by `<INTENT>` |
| `startservice [options] <INTENT>` | Start the Service specified by `<INTENT>` |
| `broadcast [options] <INTENT>` | Send a broadcast `<INTENT>` |
| `force-stop <packagename>` | Force stop everything associated with `<packagename>`|
The `<INTENT>` is a flexible parameter which is corresponding to the Intent writing in the application.
The options for `<INTENT>` are as follows:
| Parameter | Meaning |
|------------------|---------------------------------------------------------------------------------------------------------------------------------------|
| `-a <ACTION>` | Specify the intent action, such as `android.intent.action.VIEW`. You can declare this only once. |
| `-c <CATEGORY>` | Specify an intent category, such as `android.intent.category.APP_CONTACTS` |
| `-n <COMPONENT>` | Specify the component name with package name prefix to create an explicit intent, such as `com.example.app/.ExampleActivity` |
There are some options addting data for `<INTENT>`, similar to `extra` for Bundle:
| Parameter | Meaning |
|------------------------------------------------------------------|----------------------------------------|
| `--esn <EXTRA_KEY>` | null value (only key name) |
| `-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE>` | string value |
| `--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>` | boolean value |
| `--ei <EXTRA_KEY> <EXTRA_INT_VALUE>` | integer value |
| `--el <EXTRA_KEY> <EXTRA_LONG_VALUE>` | long value |
| `--ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE>` | float value |
| `--eu <EXTRA_KEY> <EXTRA_URI_VALUE>` | URI |
| `--ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>` | component name |
| `--eia <EXTRA_KEY> <EXTRA_INT_VALUE> [, <EXTRA_INT_VALUE ...]` | integer array |
| `--ela <EXTRA_KEY> <EXTRA_LONG_VALUE> [, <EXTRA_LONG_VALUE ...]` | long array |
### Launch app / Start an Activity
> start with Activity's name
The syntax is:
```sh
adb shell am start [options] <INTENT>
```
For example:
```sh
adb shell am start -n com.tencent.mm/.ui.LauncherUI
```
The command above means starting the launch activity of WeChat.
```sh
adb shell am start -n org.mazhuang.boottimemeasure/.MainActivity --es "toast" "hello, world"
```
The command above means starting MainActivity of the application with the package name `org.mazhuang.boottimemeasure` with an extra string information (key is 'toast' and value is 'hello, world').
> start without Activity's name
The syntax is:
```sh
adb shell monkey -p <packagename> -c android.intent.category.LAUNCHER 1
```
For example:
```sh
adb shell monkey -p com.tencent.mm -c android.intent.category.LAUNCHER 1
```
The command above means starting the launch activity of WeChat.
### Start a Service
The syntax is:
```sh
adb shell am startservice [options] <INTENT>
```
For example:
```sh
adb shell am startservice -n com.tencent.mm/.plugin.accountsync.model.AccountAuthenticatorService
```
The command above means starting a service from WeChat.
Another typical useage is that if devices has bottom virtual keys but not show, you can try this:
```sh
adb shell am startservice -n com.android.systemui/.SystemUIService
```
### Stop service
The syntax is:
```sh
adb shell am stopservice [options] <INTENT>
```
### Send a broadcast
The syntax is:
```sh
adb shell am broadcast [options] <INTENT>
```
Broadcast intent can be sent to all components or a specified component.
For example, the command of issuing a broadcast intent with `BOOT_COMPLETED` to all of the components is as following:
```sh
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED
```
As another example of issuing a broadcast intent with `BOOT_COMPLETED` only to `org.mazhuang.boottimemeasure / .BootCompletedReceiver` is as following:
```sh
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n org.mazhuang.boottimemeasure/.BootCompletedReceiver
```
The command of issuing a broadcast intent is very useful in the test, especially when a broatcast intent is hard to generate normally, it would be of great use to send the broadcast intent by the command.
Both system predefined and custom broadcast intent are able to be sent. The following is part of the system predefined broadcast intents and the triggers:
| Action | Trigger |
|-------------------------------------------------|-----------------------------------------------------------------------|
| android.net.conn.CONNECTIVITY_CHANGE | network connectivity changes |
| android.intent.action.SCREEN_ON | screen on |
| android.intent.action.SCREEN_OFF | screen off |
| android.intent.action.BATTERY_LOW | low battery, corresponding to the "Low battery warning" system dialog |
| android.intent.action.BATTERY_OKAY | the battery is now okay after being low |
| android.intent.action.BOOT_COMPLETED | device boot finished |
| android.intent.action.DEVICE_STORAGE_LOW | low memory condition on the device |
| android.intent.action.DEVICE_STORAGE_OK | low memory condition on the device no longer exists |
| android.intent.action.PACKAGE_ADDED | a new application has been installed |
| android.net.wifi.STATE_CHANGE | WiFi connection status changed |
| android.net.wifi.WIFI_STATE_CHANGED | Wi-Fi has been enabled, disabled, enabling, disabling, or unknown |
| android.intent.action.BATTERY_CHANGED | battery level changed |
| android.intent.action.INPUT_METHOD_CHANGED | system input method changed |
| android.intent.action.ACTION_POWER_CONNECTED | external power connected to the device |
| android.intent.action.ACTION_POWER_DISCONNECTED | external power removed from the device |
| android.intent.action.DREAMING_STARTED | system starts dreaming |
| android.intent.action.DREAMING_STOPPED | system stops dreaming |
| android.intent.action.WALLPAPER_CHANGED | wallpaper changeed |
| android.intent.action.HEADSET_PLUG | wired headset plugged in or unplugged |
| android.intent.action.MEDIA_UNMOUNTED | external media is present, but not mounted at its mount point |
| android.intent.action.MEDIA_MOUNTED | external media is present and mounted at its mount point |
| android.os.action.POWER_SAVE_MODE_CHANGED | power-saving mode changed |
*(Above broadcast intents are all available to be sent via adb commands)*
### Force stop an application
The syntax is:
```sh
adb shell am force-stop <packagename>
```
For example:
```sh
adb shell am force-stop com.qihoo360.mobilesafe
```
The command above means stopping all processes and services related to the package name `com.qihoo360.mobilesafe`.
### Trim memory
command:
```sh
adb shell am send-trim-memory <pid> <level>
```
pid: process id
level: HIDDEN、RUNNING_MODERATE、BACKGROUND、RUNNING_LOW、MODERATE、RUNNING_CRITICAL、COMPLETE
For example:
```sh
adb shell am send-trim-memory 12345 RUNNING_LOW
```
means send command to process 12345, notify it to set level to RUNNING.
## File Management
### Copy files from a device to a computer
command:
```sh
adb pull <remote> [local]
```
> - `remote`: file path on device
> - `local`: directory on computer
The `local` parameter is optional, the default value is current directory.
For example:
```sh
adb pull /sdcard/sr.mp4 ~/tmp/
```
- *Tips*: The file from device may be not readable without root permission, you need to make sure your device is rooted and then use `adb shell` and `su` commands to gain the root permission in the `adb shell` environment, after that you can use `cp /path/on/device /sdcard/filename` to copy the target file from those directories which require root permission to a public directory, and finaly you can use `adb pull /sdcard/filename /path/on/pc` normally as mentioned above after exiting the `adb shell` environment.
### Copy files from a computer to a device
command:
```sh
adb push <local> <remote>
```
> - `local`: file path on computer
> - `remote`: directory on device
For example:
```sh
adb push ~/sr.mp4 /sdcard/
```
- *Tips*: The directory on device may be not writable without root permission, you need to make sure your device is rooted and then use `adb push /path/on/pc /sdcard/filename` firstly, and use `adb shell` and `su` to gain the root permission in the `adb shell` environment, and finaly use `cp /sdcard/filename /path/on/device` to copy the file to the target directory.
## Analog Keys / inputs
In `adb shell` there is a very useful command called` input`, through which you can do some interesting things.
`Complete help information input` command is as follows:
```sh
Usage: input [<source>] <command> [<arg>...]
The sources are:
mouse
keyboard
joystick
touchnavigation
touchpad
trackball
stylus
dpad
gesture
touchscreen
gamepad
The commands and default sources are:
text <string> (Default: touchscreen)
keyevent [--longpress] <key code number or name> ... (Default: keyboard)
tap <x> <y> (Default: touchscreen)
swipe <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
press (Default: trackball)
roll <dx> <dy> (Default: trackball)
```
Such as using `adb shell input keyevent <keycode>` command, different keycode to achieve different functions, keycode complete list see [KeyEvent](https://developer.android.com/reference/android/view/KeyEvent.html), I think the interesting part of the quote is as follows:
| Keycode | Meaning |
|---------|--------------------------------------------------------------|
| 3 | HOME button |
| 4 | return key |
| 5 | open dialing application |
| 6 | hang up |
| 24 | increase volume |
| 25 | Volume Down |
| 26 | Power button |
| 27 | taking pictures (in the camera application needs in) |
| 64 | Open Browser |
| 82 | menu button |
| 85 | Play / Pause |
| 86 | stop playing |
| 87 | play the next |
| 88 | played on a |
| 122 | Move the cursor to the beginning or top of the list |
| 123 | Move the cursor to the end of the line or bottom of the list |
| 126 | resume playing |
| 127 | pause play |
| 164 | Mute |
| 176 | Open the System Setup |
| 187 | switching applications |
| 207 | Open Contacts |
| 208 | Open calendar |
| 209 | Open Music |
| 210 | Open Calculator |
| 220 | Decrease screen brightness |
| 221 | Increase screen brightness |
| 223 | System Sleep |
| 224 | light up the screen |
| 231 | Open the voice assistant |
| 276 | If no wakelock allow the system to sleep |
Here are some examples of the use of `input` command.
### Power button
command:
```sh
adb shell input keyevent 26
```
Executive effect equivalent to pressing the power button.
### menu
command:
```sh
adb shell input keyevent 82
```
### HOME key
command:
```sh
adb shell input keyevent 3
```
### return key
command:
```sh
adb shell input keyevent 4
```
### volume control
Increase the volume:
```sh
adb shell input keyevent 24
```
lower the volume:
```sh
adb shell input keyevent 25
```
Mute:
```sh
adb shell input keyevent 164
```
### Media Control
play / Pause:
```sh
adb shell input keyevent 85
```
Stop play:
```sh
adb shell input keyevent 86
```
Play the next song:
```sh
adb shell input keyevent 87
```
Played on one:
```sh
adb shell input keyevent 88
```
Resume playback:
```sh
adb shell input keyevent 126
```
Pause playback:
```sh
adb shell input keyevent 127
```
### On / Off screen
It can be switched on and off by telling off the screen above the analog power button, but if you want to light up or clear off the screen, then you can use the following method.
Light up the screen:
```sh
adb shell input keyevent 224
```
Off screen:
```sh
adb shell input keyevent 223
```
### Slide to unlock
If no password lock screen is unlocked by sliding gestures, so you can `input swipe` to unlock.
Command (parameter models Nexus 5, swipe up to unlock, for example):
```sh
adb shell input swipe 300 1000 300 500
```
`3001000300 parameters represent` 500` starting x coordinate of the start point y coordinate of the end point x coordinate y coordinate of the end point '.
### Enter text
When the focus is in a text box, you can enter text by `input` command.
command:
```sh
adb shell input text hello
```
`hello` now appear in the text box.
If you want to input Chinese, you can install [ADBKeyBoard.apk](https://github.com/senzhk/ADBKeyBoard), detailed documentation refer to [here](https://github.com/senzhk/ADBKeyBoard).
Then execute the commands:
```sh
# 1. Set the current input method to ADBKeyBoard
adb shell ime set com.android.adbkeyboard/.AdbIME
# 2. Input Chinese
adb shell am broadcast -a ADB_INPUT_TEXT --es msg '你好'
```
## View Log
Log Android system is divided into two parts, the underlying Linux kernel log output to / proc / kmsg, Android's log output to / dev / log.
### Android log
Format:
```sh
[adb] logcat [<option>] ... [<filter-spec>] ...
```
Common usage are listed below:
### Filter the log by level
Android log divided into the following levels:
* V - Verbose (lowest output most)
* D - Debug
* I - Info
* W - Warning
* E - Error
* F - Fatal
* S - Silent (highest, what is not output)
Press a grade level and above filter log is the log output.
For example, the command:
```sh
adb logcat *:W
```
Will Warning, Error, Fatal and Silent log output.
(**Notice:** tag `*` must surrounded with double quotation, like `adb logcat "*:W"`, otherwise an error `no matches found *:W` would throws.)
#### Filter by tag and log level
filterspecs are a series of `<tag>[:priority]`.
For example, the command:
```sh
adb logcat ActivityManager:I MyApp:D *:S
```
Represents an output tag `ActivityManager` above the level of Info logs, Debug log output above the level of the tag` MyApp`, and other tag Silent level of log (ie, shield other tag logging).
#### Log format
You can use `adb logcat -v <format>` option specifies log output format.
Log supported by the following `<format>`:
* brief
The default format. The format is:
```sh
<priority>/<tag>(<pid>): <message>
```
Example:
```sh
D/HeadsetStateMachine( 1785): Disconnected process message: 10, size: 0
```
* process
The format is:
```sh
<priority>(<pid>) <message>
```
Example:
```sh
D( 1785) Disconnected process message: 10, size: 0 (HeadsetStateMachine)
```
* tag
The format is:
```sh
<priority>/<tag>: <message>
```
Example:
```sh
D/HeadsetStateMachine: Disconnected process message: 10, size: 0
```
* raw
The format is:
```sh
<message>
```
Example:
```sh
Disconnected process message: 10, size: 0
```
* time
The format is:
```sh
<datetime> <priority>/<tag>(<pid>): <message>
```
Example:
```sh
08-28 22:39:39.974 D/HeadsetStateMachine( 1785): Disconnected process message: 10, size: 0
```
* threadtime
The format is:
```sh
<datetime> <pid> <tid> <priority> <tag>: <message>
```
Example:
```sh
08-28 22:39:39.974 1785 1832 D HeadsetStateMachine: Disconnected process message: 10, size: 0
```
* long
The format is:
```sh
[ <datetime> <pid>:<tid> <priority>/<tag> ]
<message>
```
Example:
```sh
[ 08-28 22:39:39.974 1785: 1832 D/HeadsetStateMachine ]
Disconnected process message: 10, size: 0
```
Specified format can be used simultaneously with the above filter. such as:
```sh
adb logcat -v long ActivityManager:I *:S
```
#### Clear log
```sh
adb logcat -c
```
### Kernel log
command:
```sh
adb shell dmesg
```
Example output:
```sh
<6>[14201.684016] PM: noirq resume of devices complete after 0.982 msecs
<6>[14201.685525] PM: early resume of devices complete after 0.838 msecs
<6>[14201.753642] PM: resume of devices complete after 68.106 msecs
<4>[14201.755954] Restarting tasks ... done.
<6>[14201.771229] PM: suspend exit 2016-08-28 13:31:32.679217193 UTC
<6>[14201.872373] PM: suspend entry 2016-08-28 13:31:32.780363596 UTC
<6>[14201.872498] PM: Syncing filesystems ... done.
```
In brackets `[14201.684016]` time represents the core begins to start in seconds.
By kernel log, we can do some things, such as a measure of the kernel boot time, `Freeing init memory` find that time is in front of the line after system startup, the kernel log.
## View device information
### Model
Command:
```sh
adb shell getprop ro.product.model
```
Sample output:
```sh
Nexus 5
```
### Battery Status
Command:
```sh
adb shell dumpsys battery
```
Sample output:
```sh
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
status: 2
health: 2
present: true
level: 44
scale: 100
voltage: 3872
temperature: 280
technology: Li-poly
```
`Scale` means the maximum value of `level`, and `level` means the current battery level. The output above means there is 44% of battery left of the device.
### Screen Resolution
Command:
```sh
adb shell wm size
```
Sample output:
```sh
Physical size: 1080x1920
```
The above output means the device's screen resolution is 1080px * 1920px.
If resolution has been changed by command, the output would be like this:
```sh
Physical size: 1080x1920
Override size: 480x1024
```
It means the original resolution of the screen is 1080px * 1920px, and currently it is 480px * 1024px.
### Screen density
Command:
```sh
adb shell wm density
```
Sample output:
```sh
Physical density: 420
```
The output shows the density of the device is 420dpi.
If screen density has been changed by command, the output would be like this:
```sh
Physical density: 480
Override density: 160
```
It means the original density of the screen is 480dpi, and currently it is 160dpi.
### Display Parameters
Command:
```sh
adb shell dumpsys window displays
```
Sample output:
```sh
WINDOW MANAGER DISPLAY CONTENTS (dumpsys window displays)
Display: mDisplayId=0
init=1080x1920 420dpi cur=1080x1920 app=1080x1794 rng=1080x1017-1810x1731
deferred=false layoutNeeded=false
```
The `mDisplayId` stands for the number of the display screen, `init` shows the initial resolution and density of the screen, the height in `app` is smaller than that in `init`, which means the device has a virtual navigation bar with a height: `1920 - 1794 = 126px (42dp)`.
### android\_id
Command:
```sh
adb shell settings get secure android_id
```
Sample output:
```sh
51b6be48bac8c569
```
### IMEI
For Android 4.4 and the belows, the IMEI viewing command is like this:
```sh
adb shell dumpsys iphonesubinfo
```
Sample output:
```sh
Phone Subscriber Info:
Phone Type = GSM
Device ID = 860955027785041
```
`Device ID` stands for IMEI.
For Android 5.0 and the aboves, the command used to view IMEI above is not working which always comes out nothing, the alternative is like this(requires root privileges):
```sh
adb shell
su
service call iphonesubinfo 1
```
Sample output:
```sh
Result: Parcel(
0x00000000: 00000000 0000000f 00360038 00390030 '........8.6.0.9.'
0x00000010: 00350035 00320030 00370037 00350038 '5.5.0.2.7.7.8.5.'
0x00000020: 00340030 00000031 '0.4.1... ')
```
After extracting the data the normal IMEI will show, such as the IMEI above is `860955027785041`.
Reference: [adb shell dumpsys iphonesubinfo not working since Android 5.0 Lollipop](http://stackoverflow.com/questions/27002663/adb-shell-dumpsys-iphonesubinfo-not-working-since-android-5-0-lollipop)
### Android system version
Command:
```sh
adb shell getprop ro.build.version.release
```
Sample output:
```sh
5.0.2
```
### IP address
Are you getting bored for pressing "Setting" - "About phone" - "state information" - "IP address" to get the IP address of the device? You can make it easily via adb command:
Command:
```sh
adb shell ifconfig | grep Mask
```
Sample output:
```sh
inet addr:10.130.245.230 Mask:255.255.255.252
inet addr:127.0.0.1 Mask:255.0.0.0
```
The IP address of the device is `10.130.245.230`.
The above command may result in an empty result on some devices if they are connected via WIFI, then you can use the following command to view the LAN IP:
```sh
adb shell ifconfig wlan0
```
Sample output:
```sh
wlan0: ip 10.129.160.99 mask 255.255.240.0 flags [up broadcast running multicast]
```
or
```sh
wlan0 Link encap:UNSPEC
inet addr:10.129.168.57 Bcast:10.129.175.255 Mask:255.255.240.0
inet6 addr: fe80::66cc:2eff:fe68:b6b6/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:496520 errors:0 dropped:0 overruns:0 frame:0
TX packets:68215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:116266821 TX bytes:8311736
```
If the two commands above still don't get the desired information, then you can try the following command (available in some system):
```sh
adb shell netcfg
```
Sample output:
```sh
wlan0 UP 10.129.160.99/20 0x00001043 f8:a9:d0:17:42:4d
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
p2p0 UP 0.0.0.0/0 0x00001003 fa:a9:d0:17:42:4d
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
rmnet0 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet3 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet4 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet6 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet5 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet7 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rev_rmnet3 DOWN 0.0.0.0/0 0x00001002 4e:b7:e4:2e:17:58
rev_rmnet2 DOWN 0.0.0.0/0 0x00001002 4e:f0:c8:bf:7a:cf
rev_rmnet4 DOWN 0.0.0.0/0 0x00001002 a6:c0:3b:6b:c4:1f
rev_rmnet6 DOWN 0.0.0.0/0 0x00001002 66:bb:5d:64:2e:e9
rev_rmnet5 DOWN 0.0.0.0/0 0x00001002 0e:1b:eb:b9:23:a0
rev_rmnet7 DOWN 0.0.0.0/0 0x00001002 7a:d9:f6:81:40:5a
rev_rmnet8 DOWN 0.0.0.0/0 0x00001002 4e:e2:a9:bb:d0:1b
rev_rmnet0 DOWN 0.0.0.0/0 0x00001002 fe:65:d0:ca:82:a9
rev_rmnet1 DOWN 0.0.0.0/0 0x00001002 da:d8:e8:4f:2e:fe
```
It shows the network connection name, connection enable status, IP address, Mac address and etc.
### Mac Address
Command:
```sh
adb shell cat /sys/class/net/wlan0/address
```
Sample output:
```sh
f8:a9:d0:17:42:4d
```
The output above is the Mac address of LAN, if you want other infomation of connection, the command `adb shell netcfg` mentioned in the section **IP address** would be helpful.
### CPU Information
Command:
```sh
adb shell cat /proc/cpuinfo
```
Sample output:
```sh
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 38.40
processor : 1
BogoMIPS : 38.40
processor : 2
BogoMIPS : 38.40
processor : 3
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x06f
CPU revision : 0
Hardware : Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
Revision : 000b
Serial : 0000000000000000
```
This is the CPU information of Nexus 5, we can find from the output that the hardware is `Qualcomm MSM 8974`, and the processor number is from 0 to 3, which means the cpu is a quad-core, then from the `Processor` we can find the architecture of the cpu is` ARMv7 Processor rev 0 ( v71) `.
### Memory Information
Command:
```sh
adb shell cat /proc/meminfo
```
Sample output:
```sh
MemTotal: 1027424 kB
MemFree: 486564 kB
Buffers: 15224 kB
Cached: 72464 kB
SwapCached: 24152 kB
Active: 110572 kB
Inactive: 259060 kB
Active(anon): 79176 kB
Inactive(anon): 207736 kB
Active(file): 31396 kB
Inactive(file): 51324 kB
Unevictable: 3948 kB
Mlocked: 0 kB
HighTotal: 409600 kB
HighFree: 132612 kB
LowTotal: 617824 kB
LowFree: 353952 kB
SwapTotal: 262140 kB
SwapFree: 207572 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 265324 kB
Mapped: 47072 kB
Shmem: 1020 kB
Slab: 57372 kB
SReclaimable: 7692 kB
SUnreclaim: 49680 kB
KernelStack: 4512 kB
PageTables: 5912 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 775852 kB
Committed_AS: 13520632 kB
VmallocTotal: 385024 kB
VmallocUsed: 61004 kB
VmallocChunk: 209668 kB
```
`MemTotal` means the total memory of the device, and `MemFree` means the current free memory.
### More hardware and system properties
More hardware devices and system properties can be obtained by the following command:
```sh
adb shell cat /system/build.prop
```
This will output a lot of information, including "model" and "Android system version" and other infomation which are mentioned in previous several sections.
In output also includes some other useful information, which can also be obtained individually via the command `adb shell getprop <attribute name>`:
| Attribute name | Meaning |
|---------------------------------|-------------------------------|
| ro.build.version.sdk | SDK version |
| ro.build.version.release | Android system version |
| ro.build.version.security_patch | Android security patch level |
| ro.product.model | Type |
| ro.product.brand | Brands |
| ro.product.name | device name |
| ro.product.board | Processor Model |
| ro.product.cpu.abilist | CPU supported abi list[Ref 1] |
| persist.sys.isUsbOtgEnabled | OTG supports |
| dalvik.vm.heapsize | limit on heap size for each app |
| ro.sf.lcd_density | screen density |
*Ref 1*:
The property of abi list may be changed in some custom ROMs, if it can't be obtained via `ro.product.cpu.abilist`, you can try this command:
```
adb shell cat /system/build.prop | grep ro.product.cpu.abi
```
Sample output:
```
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
```
## Modify Settings
**Notice:** Display may not normal after reset settings, you can use command `adb reboot` to reboot device, or reboot it maually.
### Resolution
command:
```sh
adb shell wm size 480x1024
```
It means change the resolution to 480px * 1024px.
Reset to original resolution:
```sh
adb shell wm size reset
```
### Screen density
command:
```sh
adb shell wm density 160
```
It means change the screen density to 160dpi.
Reset to original screen density:
```sh
adb shell wm density reset
```
### Overscan
command:
```sh
adb shell wm overscan 0,0,0,200
```
Four parameters are left, top, right and bottom margin pixels to the edge, command above means leave 200px in screen bottom clean.
Reset to original overscan:
```sh
adb shell wm overscan reset
```
### Turn off Android Debug
command:
```sh
adb shell settings put global adb_enabled 0
```
To reset:
We can't do this via command now, because without "Android Debug" on, adb cannot communicate with Devices.
So just do it on device manually:
"Settings" - "Developer options" - "Android Debug".
### allow/forbidden access non SDK API
allow access non SDK API:
```sh
adb shell settings put global hidden_api_policy_pre_p_apps 1
adb shell settings put global hidden_api_policy_p_apps 1
```
forbidden access non SDK API:
```sh
adb shell settings delete global hidden_api_policy_pre_p_apps
adb shell settings delete global hidden_api_policy_p_apps
```
*Note: Commands above don't need root privileges.*
meaning for number in command tail:
| value | meaning |
|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 0 | disable detect for non SDK API call. In this situation, there is no call log in logcat, and make strict mode API, detectNonSdkApiUsage() invalid. Not recommended. |
| 1 | Just warning -- allow access all non SDK API, but retain warning in logcat. You can continue to use strick mode API. |
| 2 | It is forbidden to invoke interfaces in dark grey lists and black lists. |
| 3 | It is forbidden to invoke the interface in the black list, but it is allowed to call the interface in the dark grey list. |
### Show/hide status bar or navigation bar
Settings in this section correspond with "Expanded desktop" in Cyanogenmod.
command:
```sh
adb shell settings put global policy_control <key-values>
```
`<key-values>` composite by keys and their values below, format is `<key1>=<value1>:<key2>=<value2>`.
| key | meaning |
|-----------------------|---------------------|
| immersive.full | Hide both |
| immersive.status | Hide status bar |
| immersive.navigation | Hide navigation bar |
| immersive.preconfirms | ? |
Values for these keys are comma-delimited list of tokens, where tokens:
| value | 含义 |
|----------------|------------------|
| `apps` | All applications |
| `*` | Everywhere |
| `packagename` | Include package |
| `-packagename` | Exclude package |
For example:
```sh
adb shell settings put global policy_control immersive.full=*
```
Means set hide both status bar and navigation bar everywhere.
```sh
adb shell settings put global policy_control immersive.status=com.package1,com.package2:immersive.navigation=apps,-com.package3
```
Means set hide status bar in applications whoes package name is `com.package1` or `com.package2`, hide navigation bar in all applications, exclude whoes package name is `com.package3`.
## Utility functions
### Screenshots
Take screenshot and save to computer:
```sh
adb exec-out screencap -p > sc.png
```
If your adb is old version, doesn't have `exec-out` command, then your can take screenshot like below:
First, take screenshot and save to device:
```sh
adb shell screencap -p /sdcard/sc.png
```
And then export the png file to your computer:
```sh
adb pull /sdcard/sc.png
```
You can use the `adb shell screencap -h` See` help screencap` command, here are two significant parameters and their meanings:
| Parameter | Meaning |
|---------------|------------------------------------------------------------------------------|
| -p | Save the file in png format specified |
| -d Display-id | screenshots display the specified number (multiple screen display case next) |
Found If you specify a file name can be omitted when the -p parameter to `.png` ending; otherwise you need to use the -p parameter. If you do not specify a file name, file contents screenshot will be directly output to stdout.
Another method to save screenshot file to computer with a single line command:
```sh
adb shell screencap -p | sed "s/\r$//" > sc.png
```
This depends on `sed` command, it's avaliable in Linux and Mac OS X by default. In Windows, you may find it in bin directory in Git installation place. Otherwise, you may need to download [sed for Windows](http://gnuwin32.sourceforge.net/packages/sed.htm) and add the directory where sed.exe is to PATH environment variable.
### Recording Screen
Record screen are saved in mp4 format to / sdcard:
```sh
adb shell screenrecord /sdcard/filename.mp4
```
When you need to stop press <kbd> Ctrl-C </ kbd>, the default recording time and maximum recording time is 180 seconds.
If you need to export to your computer:
```sh
adb pull /sdcard/filename.mp4
```
You can use the `adb shell screenrecord --help` See` help screenrecord` command, the following are common parameters and their meanings:
| Parameter | Meaning |
|---------------------|-------------------------------------------------------------------------|
| --size WIDTHxHEIGHT | dimensions of the video, such as `1280x720`, default screen resolution. |
| --bit-Rate RATE | bit-rate video, the default is 4Mbps. |
| --time-Limit TIME | recording length, in seconds. |
| --verbose | Print more information. |
### Remount system partition as writable
**Note: You need root privileges.**
/system partitions are mounted read-only, but some operating systems such as Android to add commands to remove the need to bring their own application / system write operation, it is necessary to remount it read-write.
step:
1. Enter the shell and switch to the root user privileges.
command:
```sh
adb shell
su
```
2. View the current partition mounted case.
command:
```sh
mount
```
Example output:
```sh
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /var tmpfs rw,seclabel,relatime,mode=770,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
none /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
```
Find one of our concerns with the / system of the line:
```sh
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
```
3. remount.
command:
```sh
mount -o remount,rw -t yaffs2 /dev/block/platform/msm_sdcc.1/by-name/system /system
```
Here `/ dev / block / platform / msm_sdcc.1 / by-name / system` is we get the file path from the output in the previous step.
If the output is not an error, then the operation is successful, you can file / system under wanted.
### Check connection over WiFi password
**Note: You need root privileges.**
command:
```sh
adb shell
su
cat /data/misc/wifi/*.conf
```
Example output:
```sh
network={
ssid="TP-LINK_9DFC"
scan_ssid=1
psk="123456789"
key_mgmt=WPA-PSK
group=CCMP TKIP
auth_alg=OPEN
sim_num=1
priority=13893
}
network={
ssid="TP-LINK_F11E"
psk="987654321"
key_mgmt=WPA-PSK
sim_num=1
priority=17293
}
```
`Ssid` we shall see in the WLAN settings in the name,` psk` the password, `key_mgmt` security encryption.
If android version is above O, the path of config file should be in `WifiConfigStore.xml`.
```sh
adb shell
su
cat /data/misc/wifi/WifiConfigStore.xml
```
Example output:
> because of too many items in the file, it can be focused on `ConfigKey`-- WiFi name and `PreSharedKey` -- WiFi password.
```xml
<string name="ConfigKey">"Wi-Fi"WPA_PSK</string>
<string name="PreSharedKey">"931907334"</string>
```
### To set the system date and time
** Note: You need root privileges. **
command:
```sh
adb shell
su
date -s 20160823.131500
```
It said it would change the system date and time at 13:15:00 on August 23, 2016.
### restart cellphone
command:
```sh
adb reboot
```
### Detect whether the device is root
command:
```sh
adb shell
su
```
In this case the command line prompt is `` $ indicates no root privileges, is `` the # indicates root.
### Monkey use stress testing
Monkey can generate pseudo-random event to simulate a user click, touch, gesture and other operations, you can program being developed random stress test.
Usage is simple:
```sh
adb shell monkey -p <packagename> -v 500
```
He told `<packagename>` specific application to send 500 pseudo-random events.
Monkey in detail with reference to the use of [official document](https://developer.android.com/studio/test/monkey.html).
### On / off WiFi
** Note: You need root privileges. **
Sometimes the need to control the device WiFi mode, you can use the following command to complete.
Open WiFi:
```sh
adb root
adb shell svc wifi enable
```
Close WiFi:
```sh
adb root
adb shell svc wifi disable
```
If successfully implemented, the output is empty; if not get root privileges to execute this command will fail, output `Killed`.
## Flashing-Phone related commands
### Restart to Recovery mode
command:
```sh
adb reboot recovery
```
### To restart from the Recovery Android
command:
```sh
adb reboot
```
### Restart to Fastboot mode
command:
```sh
adb reboot bootloader
```
### Through sideload system update
If we downloaded the Android system update package corresponds to the device to your computer, you can also adb to complete the update.
Case in Recovery Mode Update:
1. Restart to Recovery mode.
command:
```sh
adb reboot recovery
```
2. Recovery operations on the interface device into the `Apply update`-`Apply from ADB`.
Note: Different Recovery menu may differ from this, there is some level menu `Apply update from ADB`.
3. adb upload and update the system.
command:
```sh
adb sideload <path-to-update.zip>
```
## Security-related commands
### Enable / Disable SELinux
Enable SELinux
```sh
adb root
adb shell setenforce 1
```
Disable SELinux
```sh
adb root
adb shell setenforce 0
```
### Enable / Disable dm_verity
Enable dm_verity
```sh
adb root
adb enable-verity
```
Disable dm_verity
```sh
adb root
adb disable-verity
```
## More adb shell command
Android system is based on Linux kernel, so Linux where many commands in Android also has the same or similar implement, in `adb shell` where you can call. Part earlier in this document have been used in the `adb shell` command.
### See process
command:
```sh
adb shell ps
```
Example output:
```sh
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 8904 788 ffffffff 00000000 S /init
root 2 0 0 0 ffffffff 00000000 S kthreadd
...
u0_a71 7779 5926 1538748 48896 ffffffff 00000000 S com.sohu.inputmethod.sogou:classic
u0_a58 7963 5926 1561916 59568 ffffffff 00000000 S org.mazhuang.boottimemeasure
...
shell 8750 217 10640 740 00000000 b6f28340 R ps
```
Meaning of each column:
| Listing | Meaning |
|---------|-------------------|
| USER | their user |
| PID | Process ID |
| PPID | parent process ID |
| NAME | process name |
### View real-time resource consumption
command:
```sh
adb shell top
```
Example output:
```sh
User 0%, System 6%, IOW 0%, IRQ 0%
User 3 + Nice 0 + Sys 21 + Idle 280 + IOW 0 + IRQ 0 + SIRQ 3 = 307
PID PR CPU% S #THR VSS RSS PCY UID Name
8763 0 3% R 1 10640K 1064K fg shell top
131 0 3% S 1 0K 0K fg root dhd_dpc
6144 0 0% S 115 1682004K 115916K fg system system_server
132 0 0% S 1 0K 0K fg root dhd_rxf
1731 0 0% S 6 20288K 788K fg root /system/bin/mpdecision
217 0 0% S 6 18008K 356K fg shell /sbin/adbd
...
7779 2 0% S 19 1538748K 48896K bg u0_a71 com.sohu.inputmethod.sogou:classic
7963 0 0% S 18 1561916K 59568K fg u0_a58 org.mazhuang.boottimemeasure
...
```
Meaning of each column:
| Listing | Meaning |
|---------|-------------------------------------------------------------------------------------------|
| PID | Process ID |
| PR | Priority |
| CPU% | instantaneous current occupancy percentage of CPU |
| S | process state (R = run, S = sleep, T = trace / stop, Z = zombie process) |
| #THR | Threads |
| VSS | Virtual Set Size of virtual memory consumption (including shared libraries occupy memory) |
| RSS | Resident Set Size actual physical memory (including shared libraries occupy memory) |
| PCY | scheduling policy priority, SP_BACKGROUND / SPFOREGROUND |
| UID | process owner user ID |
| NAME | process name |
`Top` command also supports a number of command-line parameters, detailed usage is as follows:
```sh
Usage: top [ -m max_procs ] [ -n iterations ] [ -d delay ] [ -s sort_column ] [ -t ] [ -h ]
-m num How many processes displays up
-n num refresh how many times
-d num refresh interval (in seconds, default value of 5)
-s col sorted by a column (available col value: cpu, vss, rss, thr)
-t display thread information
-h displays help documentation
```
### query process uid
There are two methods:
1. `adb shell dumpsys package <packagename> | grep userId=`
For example:
```sh
$ adb shell dumpsys package org.mazhuang.guanggoo | grep userId=
userId=10394
```
2. Get pid by `ps` first, then `adb shell cat /proc/<pid>/status | grep Uid`
For example:
```sh
$ adb shell
gemini:/ $ ps | grep org.mazhuang.guanggoo
u0_a394 28635 770 1795812 78736 SyS_epoll_ 0000000000 S org.mazhuang.guanggoo
gemini:/ $ cat /proc/28635/status | grep Uid
Uid: 10394 10394 10394 10394
gemini:/ $
```
### Other
The following is a brief description of other commonly used commands, has previously spoken commands no special additional explanation:
| Command | function |
|---------|------------------------------------|
| cat | display file contents |
| cd | change directory |
| chmod | change file access mode / access |
| df | view disk space usage |
| grep | output filter |
| kill | kill the specified process PID |
| ls | list directory contents |
| mount | Mount View and manage directory |
| mv | move or rename a file |
| ps | view running processes |
| rm | delete files |
| top | Check process resource consumption |
## common problem
### Start adb server failure
**Error message**
```sh
error: protocol fault (couldn't read status): No error
```
**Possible Causes**
adb server process wants to use 5037 port is occupied.
**solution**
Found consumes process 5037 port, and then terminate it. In Windows, for example:
```sh
netstat -ano | findstr LISTENING
...
TCP 0.0.0.0:5037 0.0.0.0:0 LISTENING 1548
...
```
1548 Here is the process ID, the process ends with the command:
```sh
taskkill /PID 1548
```
Then start adb no problem.
### com.android.ddmlib.AdbCommandRejectedException
Create a new emulator in Android Studio, but cannot connect with adb, output is:
```
com.android.ddmlib.AdbCommandRejectedException: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
```
After install a terminal app in emulator and run `su` command, it shows no su program, that is not normal.
So just delete the emulator and re-download, reinstall, all is well now.
## adb unofficial implementation
* [fb-adb](https://github.com/facebook/fb-adb) - A better shell for Android devices (for Mac).
## related commands
* [aapt](./related/aapt.md)
* [am](./related/am.md)
* [dumpsys](./related/dumpsys.md)
* [pm](./related/pm.md)
* [uiautomator](./related/uiautomator.md)
## Acknowledgements
Thanks friends for theirs selfless sharing and supplement. Names listed in no particular order.
[zxning](https://github.com/zxning), [linhua55](https://github.com/linhua55), [codeskyblue](https://github.com/codeskyblue), [seasonyuu](https://github.com/seasonyuu), [fan123199](https://github.com/fan123199), [zhEdward](https://github.com/zhEdward), [0x8BADFOOD](https://github.com/0x8BADFOOD), [keith666666](https://github.com/keith666666), [shawnlinboy](https://github.com/shawnlinboy), [s-xq](https://github.com/s-xq),
[lucky9322](https://github.com/lucky9322).
## Reference Links
* [Android Debug Bridge](https://developer.android.com/studio/command-line/adb.html)
* [ADB Shell Commands](https://developer.android.com/studio/command-line/shell.html)
* [logcat Command-line Tool](https://developer.android.com/studio/command-line/logcat.html)
* [Android ADB命令大全](http://zmywly8866.github.io/2015/01/24/all-adb-command.html)
* [adb 命令行的使用记录](https://github.com/ZQiang94/StudyRecords/blob/master/other/src/main/java/com/other/adb%20%E5%91%BD%E4%BB%A4%E8%A1%8C%E7%9A%84%E4%BD%BF%E7%94%A8%E8%AE%B0%E5%BD%95.md)
* [Android ADB命令大全(通过ADB命令查看wifi密码、MAC地址、设备信息、操作文件、查看文件、日志信息、卸载、启动和安装APK等)](http://www.jianshu.com/p/860bc2bf1a6a)
* [那些做Android开发必须知道的ADB命令](http://yifeiyuan.me/2016/06/30/ADB%E5%91%BD%E4%BB%A4%E6%95%B4%E7%90%86/)
* [adb shell top](http://blog.csdn.net/kittyboy0001/article/details/38562515)
* [像高手一样使用ADB命令行（2）](http://cabins.github.io/2016/03/25/UseAdbLikeAPro-2/)
[1]: #ip-address
================================================
FILE: README.md
================================================
# 
ADB，即 [Android Debug Bridge](https://developer.android.com/studio/command-line/adb.html)，它是 Android 开发/测试人员不可替代的强大工具，也是 Android 设备玩家的好玩具。
持续更新中，欢迎提 PR 和 Issue 补充指正，觉得有用的可以将 [此 GitHub 仓库](https://github.com/mzlogin/awesome-adb) Star 收藏备用。
给本项目提建议和意见，或想与我交流，可关注微信公众号「闷骚的程序员」：
<img src="https://cdn.jsdelivr.net/gh/mzlogin/mzlogin.github.io/assets/images/qrcode.jpg" style="width:120px;height:120px;" >
**注：** 文中有部分命令的支持情况可能与 Android 系统版本及定制 ROM 的实现有关。
Other languages: [:gb: English](./README.en.md)
# 
<!-- vim-markdown-toc GFM -->
* [基本用法](#基本用法)
* [命令语法](#命令语法)
* [为命令指定目标设备](#为命令指定目标设备)
* [启动/停止](#启动停止)
* [查看 adb 版本](#查看-adb-版本)
* [以 root 权限运行 adbd](#以-root-权限运行-adbd)
* [指定 adb server 的网络端口](#指定-adb-server-的网络端口)
* [设备连接管理](#设备连接管理)
* [查询已连接设备/模拟器](#查询已连接设备模拟器)
* [USB 连接](#usb-连接)
* [无线连接（Android11 及以上）](#无线连接android11-及以上)
* [无线连接（需要借助 USB 线）](#无线连接需要借助-usb-线)
* [无线连接（无需借助 USB 线）](#无线连接无需借助-usb-线)
* [应用管理](#应用管理)
* [查看应用列表](#查看应用列表)
* [所有应用](#所有应用)
* [系统应用](#系统应用)
* [第三方应用](#第三方应用)
* [包名包含某字符串的应用](#包名包含某字符串的应用)
* [安装 APK](#安装-apk)
* [卸载应用](#卸载应用)
* [停用/启用应用](#停用启用应用)
* [停用应用](#停用应用)
* [启用应用](#启用应用)
* [清除应用数据与缓存](#清除应用数据与缓存)
* [查看前台 Activity](#查看前台-activity)
* [查看正在运行的 Services](#查看正在运行的-services)
* [查看应用详细信息](#查看应用详细信息)
* [查看应用安装路径](#查看应用安装路径)
* [与应用交互](#与应用交互)
* [启动应用/ 调起 Activity](#启动应用-调起-activity)
* [调起 Service](#调起-service)
* [停止 Service](#停止-service)
* [发送广播](#发送广播)
* [强制停止应用](#强制停止应用)
* [收紧内存](#收紧内存)
* [文件管理](#文件管理)
* [复制设备里的文件到电脑](#复制设备里的文件到电脑)
* [复制电脑里的文件到设备](#复制电脑里的文件到设备)
* [模拟按键/输入](#模拟按键输入)
* [电源键](#电源键)
* [菜单键](#菜单键)
* [HOME 键](#home-键)
* [返回键](#返回键)
* [音量控制](#音量控制)
* [媒体控制](#媒体控制)
* [点亮/熄灭屏幕](#点亮熄灭屏幕)
* [滑动解锁](#滑动解锁)
* [输入文本](#输入文本)
* [查看日志](#查看日志)
* [Android 日志](#android-日志)
* [按级别过滤日志](#按级别过滤日志)
* [按 tag 和级别过滤日志](#按-tag-和级别过滤日志)
* [日志格式](#日志格式)
* [清空日志](#清空日志)
* [内核日志](#内核日志)
* [查看设备信息](#查看设备信息)
* [型号](#型号)
* [电池状况](#电池状况)
* [屏幕分辨率](#屏幕分辨率)
* [屏幕密度](#屏幕密度)
* [显示屏参数](#显示屏参数)
* [android\_id](#android_id)
* [IMEI](#imei)
* [Android 系统版本](#android-系统版本)
* [IP 地址](#ip-地址)
* [Mac 地址](#mac-地址)
* [CPU 信息](#cpu-信息)
* [内存信息](#内存信息)
* [更多硬件与系统属性](#更多硬件与系统属性)
* [修改设置](#修改设置)
* [分辨率](#分辨率)
* [屏幕密度](#屏幕密度-1)
* [显示区域](#显示区域)
* [关闭 USB 调试模式](#关闭-usb-调试模式)
* [允许/禁止访问非 SDK API](#允许禁止访问非-sdk-api)
* [状态栏和导航栏的显示隐藏](#状态栏和导航栏的显示隐藏)
* [实用功能](#实用功能)
* [屏幕截图](#屏幕截图)
* [录制屏幕](#录制屏幕)
* [重新挂载 system 分区为可写](#重新挂载-system-分区为可写)
* [查看连接过的 WiFi 密码](#查看连接过的-wifi-密码)
* [设置系统日期和时间](#设置系统日期和时间)
* [重启手机](#重启手机)
* [检测设备是否已 root](#检测设备是否已-root)
* [使用 Monkey 进行压力测试](#使用-monkey-进行压力测试)
* [开启/关闭 WiFi](#开启关闭-wifi)
* [刷机相关命令](#刷机相关命令)
* [重启到 Recovery 模式](#重启到-recovery-模式)
* [从 Recovery 重启到 Android](#从-recovery-重启到-android)
* [重启到 Fastboot 模式](#重启到-fastboot-模式)
* [通过 sideload 更新系统](#通过-sideload-更新系统)
* [安全相关命令](#安全相关命令)
* [启用/禁用 SELinux](#启用禁用-selinux)
* [启用/禁用 dm_verity](#启用禁用-dm_verity)
* [更多 adb shell 命令](#更多-adb-shell-命令)
* [查看进程](#查看进程)
* [查看实时资源占用情况](#查看实时资源占用情况)
* [查看进程 UID](#查看进程-uid)
* [其它](#其它)
* [常见问题](#常见问题)
* [启动 adb server 失败](#启动-adb-server-失败)
* [com.android.ddmlib.AdbCommandRejectedException](#comandroidddmlibadbcommandrejectedexception)
* [adb 的非官方实现](#adb-的非官方实现)
* [相关命令](#相关命令)
* [致谢](#致谢)
* [参考链接](#参考链接)
<!-- vim-markdown-toc -->
## 基本用法
### 命令语法
adb 命令的基本语法如下：
```sh
adb [-d|-e|-s <serialNumber>] <command>
```
如果只有一个设备/模拟器连接时，可以省略掉 `[-d|-e|-s <serialNumber>]` 这一部分，直接使用 `adb <command>`。
### 为命令指定目标设备
如果有多个设备/模拟器连接，则需要为命令指定目标设备。
| 参数 | 含义 |
|---------------------|----------------------------------------------------|
| -d | 指定当前唯一通过 USB 连接的 Android 设备为命令目标 |
| -e | 指定当前唯一运行的模拟器为命令目标 |
| `-s <serialNumber>` | 指定相应 serialNumber 号的设备/模拟器为命令目标 |
在多个设备/模拟器连接的情况下较常用的是 `-s <serialNumber>` 参数，serialNumber 可以通过 `adb devices` 命令获取。如：
```sh
$ adb devices
List of devices attached
cf264b8f device
emulator-5554 device
10.129.164.6:5555 device
```
输出里的 `cf264b8f`、`emulator-5554` 和 `10.129.164.6:5555` 即为 serialNumber。
比如这时想指定 `cf264b8f` 这个设备来运行 adb 命令获取屏幕分辨率：
```sh
adb -s cf264b8f shell wm size
```
又如想给 `10.129.164.6:5555` 这个设备安装应用（*这种形式的 serialNumber 格式为 `<IP>:<Port>`，一般为无线连接的设备或 Genymotion 等第三方 Android 模拟器*）：
```sh
adb -s 10.129.164.6:5555 install test.apk
```
**遇到多设备/模拟器的情况均使用这几个参数为命令指定目标设备，下文中为简化描述，不再重复。**
### 启动/停止
启动 adb server 命令：
```sh
adb start-server
```
（一般无需手动执行此命令，在运行 adb 命令时若发现 adb server 没有启动会自动调起。）
停止 adb server 命令：
```sh
adb kill-server
```
### 查看 adb 版本
命令：
```sh
adb version
```
示例输出：
```sh
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android
```
### 以 root 权限运行 adbd
adb 的运行原理是 PC 端的 adb server 与手机端的守护进程 adbd 建立连接，然后 PC 端的 adb client 通过 adb server 转发命令，adbd 接收命令后解析运行。
所以如果 adbd 以普通权限执行，有些需要 root 权限才能执行的命令无法直接用 `adb xxx` 执行。这时可以 `adb shell` 然后 `su` 后执行命令，也可以让 adbd 以 root 权限执行，这个就能随意执行高权限命令了。
命令：
```sh
adb root
```
正常输出：
```sh
restarting adbd as root
```
现在再运行 `adb shell`，看看命令行提示符是不是变成 `#` 了？
有些手机 root 后也无法通过 `adb root` 命令让 adbd 以 root 权限执行，比如三星的部分机型，会提示 `adbd cannot run as root in production builds`，此时可以先安装 adbd Insecure，然后 `adb root` 试试。
相应地，如果要恢复 adbd 为非 root 权限的话，可以使用 `adb unroot` 命令。
### 指定 adb server 的网络端口
命令：
```sh
adb -P <port> start-server
```
默认端口为 5037。
## 设备连接管理
### 查询已连接设备/模拟器
命令：
```sh
adb devices
```
输出示例：
```sh
List of devices attached
cf264b8f device
emulator-5554 device
10.129.164.6:5555 device
```
输出格式为 `[serialNumber] [state]`，serialNumber 即我们常说的 SN，state 有如下几种：
* `offline` —— 表示设备未连接成功或无响应。
* `device` —— 设备已连接。注意这个状态并不能标识 Android 系统已经完全启动和可操作，在设备启动过程中设备实例就可连接到 adb，但启动完毕后系统才处于可操作状态。
* `no device` —— 没有设备/模拟器连接。
以上输出显示当前已经连接了三台设备/模拟器，`cf264b8f`、`emulator-5554` 和 `10.129.164.6:5555` 分别是它们的 SN。从 `emulator-5554` 这个名字可以看出它是一个 Android 模拟器，而 `10.129.164.6:5555` 这种形为 `<IP>:<Port>` 的 serialNumber 一般是无线连接的设备或 Genymotion 等第三方 Android 模拟器。
常见异常输出：
1. 没有设备/模拟器连接成功。
```sh
List of devices attached
```
2. 设备/模拟器未连接到 adb 或无响应。
```sh
List of devices attached
cf264b8f offline
```
### USB 连接
通过 USB 连接来正常使用 adb 需要保证几点：
1. 硬件状态正常。
包括 Android 设备处于正常开机状态，USB 连接线和各种接口完好。
2. Android 设备的开发者选项和 USB 调试模式已开启。
可以到「设置」-「开发者选项」-「Android 调试」查看。
如果在设置里找不到开发者选项，那需要通过一个彩蛋来让它显示出来：在「设置」-「关于手机」连续点击「版本号」7 次。
3. 设备驱动状态正常。
这一点貌似在 Linux 和 Mac OS X 下不用操心，在 Windows 下有可能遇到需要安装驱动的情况，确认这一点可以右键「计算机」-「属性」，到「设备管理器」里查看相关设备上是否有黄色感叹号或问号，如果没有就说明驱动状态已经好了。否则可以下载一个手机助手类程序来安装驱动先。
4. 通过 USB 线连接好电脑和设备后确认状态。
```sh
adb devices
```
如果能看到
```sh
xxxxxx device
```
说明连接成功。
### 无线连接（Android11 及以上）
Android 11 及更高版本支持使用 Android 调试桥 (adb) 从工作站以无线方式部署和调试应用。例如，您可以将可调试应用部署到多台远程设备，而无需通过 USB 实际连接设备。这样就可以避免常见的 USB 连接问题，例如驱动程序安装方面的问题。
[官方文档](https://developer.android.com/studio/command-line/adb?hl=zh_cn#connect-to-a-device-over-wi-fi-android-11+)
操作步骤：
1. 更新到最新版本的 [SDK 平台工具](https://developer.android.com/studio/releases/platform-tools?hl=zh_cn)(至少30.0.0)。
2. 将 Android 设备与要运行 adb 的电脑连接到同一个局域网，比如连到同一个 WiFi。
3. 在开发者选项中启用**无线调试**。
4. 在询问要允许在此网络上进行无线调试吗？的对话框中，点击允许。
5. 选择使用配对码配对设备，使用弹窗中的 IP 地址和端口号。
```sh
adb pair ipaddr:port
```
6. 提示`Enter pairing code: `时输入弹窗中的配对码，成功后会显示`Successfully paired to ...`。
7. 使用无线调试下的 **IP 地址和端口**。
```sh
adb connect ipaddr:port
```
8. 确认连接状态。
```sh
adb devices
```
如果能看到
```sh
ipaddr:port device
```
说明连接成功。
### 无线连接（需要借助 USB 线）
除了可以通过 USB 连接设备与电脑来使用 adb，也可以通过无线连接——虽然连接过程中也有需要使用 USB 的步骤，但是连接成功之后你的设备就可以在一定范围内摆脱 USB 连接线的限制啦！
操作步骤：
1. 将 Android 设备与要运行 adb 的电脑连接到同一个局域网，比如连到同一个 WiFi。
2. 将设备与电脑通过 USB 线连接。
应确保连接成功（可运行 `adb devices` 看是否能列出该设备）。
3. 让设备在 5555 端口监听 TCP/IP 连接：
```sh
adb tcpip 5555
```
4. 断开 USB 连接。
5. 找到设备的 IP 地址。
一般能在「设置」-「关于手机」-「状态信息」-「IP地址」找到，也可以使用下文里 [查看设备信息 - IP 地址][1] 一节里的方法用 adb 命令来查看。
6. 通过 IP 地址连接设备。
```sh
adb connect <device-ip-address>
```
这里的 `<device-ip-address>` 就是上一步中找到的设备 IP 地址。
7. 确认连接状态。
```sh
adb devices
```
如果能看到
```sh
<device-ip-address>:5555 device
```
说明连接成功。
如果连接不了，请确认 Android 设备与电脑是连接到了同一个 WiFi，然后再次执行 `adb connect <device-ip-address>` 那一步；
如果还是不行的话，通过 `adb kill-server` 重新启动 adb 然后从头再来一次试试。
**断开无线连接**
命令：
```sh
adb disconnect <device-ip-address>
```
### 无线连接（无需借助 USB 线）
**注：需要 root 权限。**
上一节「无线连接（需要借助 USB 线）」是官方文档里介绍的方法，需要借助于 USB 数据线来实现无线连接。
既然我们想要实现无线连接，那能不能所有步骤下来都是无线的呢？答案是能的。
1. 在 Android 设备上安装一个终端模拟器。
已经安装过的设备可以跳过此步。我使用的终端模拟器下载地址是：[Terminal Emulator for Android Downloads](https://jackpal.github.io/Android-Terminal-Emulator/)
2. 将 Android 设备与要运行 adb 的电脑连接到同一个局域网，比如连到同一个 WiFi。
3. 打开 Android 设备上的终端模拟器，在里面依次运行命令：
```sh
su
setprop service.adb.tcp.port 5555
```
4. 找到 Android 设备的 IP 地址。
一般能在「设置」-「关于手机」-「状态信息」-「IP地址」找到，也可以使用下文里 [查看设备信息 - IP 地址][1] 一节里的方法用 adb 命令来查看。
5. 在电脑上通过 adb 和 IP 地址连接 Android 设备。
```sh
adb connect <device-ip-address>
```
这里的 `<device-ip-address>` 就是上一步中找到的设备 IP 地址。
如果能看到 `connected to <device-ip-address>:5555` 这样的输出则表示连接成功。
*节注一：*
有的设备，比如小米 5S + MIUI 8.0 + Android 6.0.1 MXB48T，可能在第 5 步之前需要重启 adbd 服务，在设备的终端模拟器上运行：
```sh
restart adbd
```
如果 restart 无效，尝试以下命令：
```sh
stop adbd
start adbd
```
## 应用管理
### 查看应用列表
查看应用列表的基本命令格式是
```sh
adb shell pm list packages [-f] [-d] [-e] [-s] [-3] [-i] [-u] [--user USER_ID] [FILTER]
```
即在 `adb shell pm list packages` 的基础上可以加一些参数进行过滤查看不同的列表，支持的过滤参数如下：
| 参数 | 显示列表 |
|------------|----------------------------|
| 无 | 所有应用 |
| -f | 显示应用关联的 apk 文件 |
| -d | 只显示 disabled 的应用 |
| -e | 只显示 enabled 的应用 |
| -s | 只显示系统应用 |
| -3 | 只显示第三方应用 |
| -i | 显示应用的 installer |
| -u | 包含已卸载应用 |
| `<FILTER>` | 包名包含 `<FILTER>` 字符串 |
#### 所有应用
命令：
```sh
adb shell pm list packages
```
输出示例：
```sh
package:com.android.smoketest
package:com.example.android.livecubes
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.providers.calendar
package:com.android.providers.media
package:com.android.protips
package:com.android.documentsui
package:com.android.gallery
package:com.android.externalstorage
...
// other packages here
...
```
#### 系统应用
命令：
```sh
adb shell pm list packages -s
```
#### 第三方应用
命令：
```sh
adb shell pm list packages -3
```
#### 包名包含某字符串的应用
比如要查看包名包含字符串 `mazhuang` 的应用列表，命令：
```sh
adb shell pm list packages mazhuang
```
当然也可以使用 grep 来过滤：
```sh
adb shell pm list packages | grep mazhuang
```
### 安装 APK
命令格式：
```sh
adb install [-lrtsdg] <path_to_apk>
```
参数：
`adb install` 后面可以跟一些可选参数来控制安装 APK 的行为，可用参数及含义如下：
| 参数 | 含义 |
|----------------------|---------------------------------------------------------------------------------------|
| -l | 将应用安装到保护目录 /mnt/asec |
| -r | 允许覆盖安装 |
| -t | 允许安装 AndroidManifest.xml 里 application 指定 `android:testOnly="true"` 的应用 |
| -s | 将应用安装到 sdcard |
| -d | 允许降级覆盖安装 |
| -g | 授予所有运行时权限 |
| --abi abi-identifier | 为特定 ABI 强制安装 apk，abi-identifier 可以是 armeabi-v7a、arm64-v8a、v86、x86_64 等 |
运行命令后如果见到类似如下输出（状态为 `Success`）代表安装成功：
```sh
[100%] /data/local/tmp/1.apk
pkg: /data/local/tmp/1.apk
Success
```
上面是当前最新版 v1.0.36 的 adb 的输出，会显示 push apk 文件到手机的进度百分比。
使用旧版本 adb 的输出则是这样的：
```sh
12040 KB/s (22205609 bytes in 1.801s)
pkg: /data/local/tmp/SogouInput_android_v8.3_sweb.apk
Success
```
而如果状态为 `Failure` 则表示安装失败，比如：
```sh
[100%] /data/local/tmp/map-20160831.apk
pkg: /data/local/tmp/map-20160831.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
```
常见安装失败输出代码、含义及可能的解决办法如下：
| 输出 | 含义 | 解决办法 |
|---------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------|
| INSTALL\_FAILED\_ALREADY\_EXISTS | 应用已经存在，或卸载了但没卸载干净 | `adb install` 时使用 `-r` 参数，或者先 `adb uninstall <packagename>` 再安装 |
| INSTALL\_FAILED\_INVALID\_APK | 无效的 APK 文件 | |
| INSTALL\_FAILED\_INVALID\_URI | 无效的 APK 文件名 | 确保 APK 文件名里无中文 |
| INSTALL\_FAILED\_INSUFFICIENT\_STORAGE | 空间不足 | 清理空间 |
| INSTALL\_FAILED\_DUPLICATE\_PACKAGE | 已经存在同名程序 | |
| INSTALL\_FAILED\_NO\_SHARED\_USER | 请求的共享用户不存在 | |
| INSTALL\_FAILED\_UPDATE\_INCOMPATIBLE | 以前安装过同名应用，但卸载时数据没有移除；或者已安装该应用，但签名不一致 | 先 `adb uninstall <packagename>` 再安装 |
| INSTALL\_FAILED\_SHARED\_USER\_INCOMPATIBLE | 请求的共享用户存在但签名不一致 | |
| INSTALL\_FAILED\_MISSING\_SHARED\_LIBRARY | 安装包使用了设备上不可用的共享库 | |
| INSTALL\_FAILED\_REPLACE\_COULDNT\_DELETE | 替换时无法删除 | |
| INSTALL\_FAILED\_DEXOPT | dex 优化验证失败或空间不足 | |
| INSTALL\_FAILED\_OLDER\_SDK | 设备系统版本低于应用要求 | |
| INSTALL\_FAILED\_CONFLICTING\_PROVIDER | 设备里已经存在与应用里同名的 content provider | |
| INSTALL\_FAILED\_NEWER\_SDK | 设备系统版本高于应用要求 | |
| INSTALL\_FAILED\_TEST\_ONLY | 应用是 test-only 的，但安装时没有指定 `-t` 参数 | |
| INSTALL\_FAILED\_CPU\_ABI\_INCOMPATIBLE | 包含不兼容设备 CPU 应用程序二进制接口的 native code | |
| INSTALL\_FAILED\_MISSING\_FEATURE | 应用使用了设备不可用的功能 | |
| INSTALL\_FAILED\_CONTAINER\_ERROR | 1. sdcard 访问失败;<br />2. 应用签名与 ROM 签名一致，被当作内置应用。 | 1. 确认 sdcard 可用，或者安装到内置存储;<br />2. 打包时不与 ROM 使用相同签名。 |
| INSTALL\_FAILED\_INVALID\_INSTALL\_LOCATION | 1. 不能安装到指定位置;<br />2. 应用签名与 ROM 签名一致，被当作内置应用。 | 1. 切换安装位置，添加或删除 `-s` 参数;<br />2. 打包时不与 ROM 使用相同签名。 |
| INSTALL\_FAILED\_MEDIA\_UNAVAILABLE | 安装位置不可用 | 一般为 sdcard，确认 sdcard 可用或安装到内置存储 |
| INSTALL\_FAILED\_VERIFICATION\_TIMEOUT | 验证安装包超时 | |
| INSTALL\_FAILED\_VERIFICATION\_FAILURE | 验证安装包失败 | |
| INSTALL\_FAILED\_PACKAGE\_CHANGED | 应用与调用程序期望的不一致 | |
| INSTALL\_FAILED\_UID\_CHANGED | 以前安装过该应用，与本次分配的 UID 不一致 | 清除以前安装过的残留文件 |
| INSTALL\_FAILED\_VERSION\_DOWNGRADE | 已经安装了该应用更高版本 | 使用 `-d` 参数 |
| INSTALL\_FAILED\_PERMISSION\_MODEL\_DOWNGRADE | 已安装 target SDK 支持运行时权限的同名应用，要安装的版本不支持运行时权限 | |
| INSTALL\_PARSE\_FAILED\_NOT\_APK | 指定路径不是文件，或不是以 `.apk` 结尾 | |
| INSTALL\_PARSE\_FAILED\_BAD\_MANIFEST | 无法解析的 AndroidManifest.xml 文件 | |
| INSTALL\_PARSE\_FAILED\_UNEXPECTED\_EXCEPTION | 解析器遇到异常 | |
| INSTALL\_PARSE\_FAILED\_NO\_CERTIFICATES | 安装包没有签名 | |
| INSTALL\_PARSE\_FAILED\_INCONSISTENT\_CERTIFICATES | 已安装该应用，且签名与 APK 文件不一致 | 先卸载设备上的该应用，再安装 |
| INSTALL\_PARSE\_FAILED\_CERTIFICATE\_ENCODING | 解析 APK 文件时遇到 `CertificateEncodingException` | |
| INSTALL\_PARSE\_FAILED\_BAD\_PACKAGE\_NAME | manifest 文件里没有或者使用了无效的包名 | |
| INSTALL\_PARSE\_FAILED\_BAD\_SHARED\_USER\_ID | manifest 文件里指定了无效的共享用户 ID | |
| INSTALL\_PARSE\_FAILED\_MANIFEST\_MALFORMED | 解析 manifest 文件时遇到结构性错误 | |
| INSTALL\_PARSE\_FAILED\_MANIFEST\_EMPTY | 在 manifest 文件里找不到找可操作标签（instrumentation 或 application） | |
| INSTALL\_FAILED\_INTERNAL\_ERROR | 因系统问题安装失败 | |
| INSTALL\_FAILED\_USER\_RESTRICTED | 用户被限制安装应用 | 在开发者选项里将「USB安装」打开，如果已经打开了，那先关闭再打开。 |
| INSTALL\_FAILED\_DUPLICATE\_PERMISSION | 应用尝试定义一个已经存在的权限名称 | |
| INSTALL\_FAILED\_NO\_MATCHING\_ABIS | 应用包含设备的应用程序二进制接口不支持的 native code | |
| INSTALL\_CANCELED\_BY\_USER | 应用安装需要在设备上确认，但未操作设备或点了取消 | 在设备上同意安装 |
| INSTALL\_FAILED\_ACWF\_INCOMPATIBLE | 应用程序与设备不兼容 | |
| INSTALL_FAILED_TEST_ONLY | APK 文件是使用 Android Studio 直接 RUN 编译出来的文件 | 通过 Gradle 的 assembleDebug 或 assembleRelease 重新编译，或者 Generate Signed APK |
| INSTALL_FAILED_ABORTED: User rejected permissions | 应用安装有风险提示需要用户在设备上确认，但用户未操作设备或点了取消 | 在设备上同意安装 |
| does not contain AndroidManifest.xml | 无效的 APK 文件 | |
| is not a valid zip file | 无效的 APK 文件 | |
| Offline | 设备未连接成功 | 先将设备与 adb 连接成功 |
| unauthorized | 设备未授权允许调试 | |
| error: device not found | 没有连接成功的设备 | 先将设备与 adb 连接成功 |
| protocol failure | 设备已断开连接 | 先将设备与 adb 连接成功 |
| Unknown option: -s | Android 2.2 以下不支持安装到 sdcard | 不使用 `-s` 参数 |
| No space left on device | 空间不足 | 清理空间 |
| Permission denied ... sdcard ... | sdcard 不可用 | |
| signatures do not match the previously installed version; ignoring! | 已安装该应用且签名不一致 | 先卸载设备上的该应用，再安装 |
参考：[PackageManager.java](https://github.com/android/platform_frameworks_base/blob/master/core%2Fjava%2Fandroid%2Fcontent%2Fpm%2FPackageManager.java)
*`adb install` 内部原理简介*
`adb install` 实际是分三步完成：
1. push apk 文件到 /data/local/tmp。
2. 调用 pm install 安装。
3. 删除 /data/local/tmp 下的对应 apk 文件。
所以，必要的时候也可以根据这个步骤，手动分步执行安装过程。
### 卸载应用
命令：
```sh
adb uninstall [-k] <packagename>
```
`<packagename>` 表示应用的包名，`-k` 参数可选，表示卸载应用但保留数据和缓存目录。
命令示例：
```sh
adb uninstall com.qihoo360.mobilesafe
```
表示卸载 360 手机卫士。
### 停用/启用应用
查看启用的应用列表：
```sh
adb shell pm list packages -e
```
#### 停用应用
命令：
```sh
adb shell pm disable-user <packagename>
```
命令示例：
```sh
adb shell pm disable-user com.qihoo360.mobilesafe
```
#### 启用应用
命令：
```sh
adb shell pm enable <packagename>
```
命令示例：
```sh
adb shell pm enable com.qihoo360.mobilesafe
```
### 清除应用数据与缓存
命令：
```sh
adb shell pm clear <packagename>
```
`<packagename>` 表示应用名包，这条命令的效果相当于在设置里的应用信息界面点击了「清除缓存」和「清除数据」。
命令示例：
```sh
adb shell pm clear com.qihoo360.mobilesafe
```
表示清除 360 手机卫士的数据和缓存。
### 查看前台 Activity
命令：
```sh
adb shell dumpsys activity activities | grep mResumedActivity
```
输出示例：
```sh
mResumedActivity: ActivityRecord{8079d7e u0 com.cyanogenmod.trebuchet/com.android.launcher3.Launcher t42}
```
其中的 `com.cyanogenmod.trebuchet/com.android.launcher3.Launcher` 就是当前处于前台的 Activity。
*在 Windows 下以上命令可能不可用，可以尝试 `adb shell dumpsys activity activities | findstr mResumedActivity` 或 `adb shell "dumpsys activity activities | grep mResumedActivity"`。*
### 查看正在运行的 Services
命令：
```sh
adb shell dumpsys activity services [<packagename>]
```
`<packagename>` 参数不是必须的，指定 `<packagename>` 表示查看与某个包名相关的 Services，不指定表示查看所有 Services。
`<packagename>` 不一定要给出完整的包名，比如运行 `adb shell dumpsys activity services org.mazhuang`，那么包名 `org.mazhuang.demo1`、`org.mazhuang.demo2` 和 `org.mazhuang123` 等相关的 Services 都会列出来。
### 查看应用详细信息
命令：
```sh
adb shell dumpsys package <packagename>
```
输出中包含很多信息，包括 Activity Resolver Table、Registered ContentProviders、包名、userId、安装后的文件资源代码等路径、版本信息、权限信息和授予状态、签名版本信息等。
`<packagename>` 表示应用包名。
输出示例：
```sh
Activity Resolver Table:
Non-Data Actions:
android.intent.action.MAIN:
5b4cba8 org.mazhuang.guanggoo/.SplashActivity filter 5ec9dcc
Action: "android.intent.action.MAIN"
Category: "android.intent.category.LAUNCHER"
AutoVerify=false
Registered ContentProviders:
org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider:
Provider{7a3c394 org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider}
ContentProvider Authorities:
[org.mazhuang.guanggoo.fileProvider]:
Provider{7a3c394 org.mazhuang.guanggoo/com.tencent.bugly.beta.utils.BuglyFileProvider}
applicationInfo=ApplicationInfo{7754242 org.mazhuang.guanggoo}
Key Set Manager:
[org.mazhuang.guanggoo]
Signing KeySets: 501
Packages:
Package [org.mazhuang.guanggoo] (c1d7f):
userId=10394
pkg=Package{55f714c org.mazhuang.guanggoo}
codePath=/data/app/org.mazhuang.guanggoo-2
resourcePath=/data/app/org.mazhuang.guanggoo-2
legacyNativeLibraryDir=/data/app/org.mazhuang.guanggoo-2/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=74 minSdk=15 targetSdk=25
versionName=1.1.74
splits=[base]
apkSigningVersion=2
applicationInfo=ApplicationInfo{7754242 org.mazhuang.guanggoo}
flags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
privateFlags=[ RESIZEABLE_ACTIVITIES ]
dataDir=/data/user/0/org.mazhuang.guanggoo
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
timeStamp=2017-10-22 23:50:53
firstInstallTime=2017-10-22 23:50:25
lastUpdateTime=2017-10-22 23:50:55
installerPackageName=com.miui.packageinstaller
signatures=PackageSignatures{af09595 [53c7caa2]}
installPermissionsFixed=true installStatus=1
pkgFlags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
requested permissions:
android.permission.READ_PHONE_STATE
android.permission.INTERNET
android.permission.ACCESS_NETWORK_STATE
android.permission.ACCESS_WIFI_STATE
android.permission.READ_LOGS
android.permission.WRITE_EXTERNAL_STORAGE
android.permission.READ_EXTERNAL_STORAGE
install permissions:
android.permission.INTERNET: granted=true
android.permission.ACCESS_NETWORK_STATE: granted=true
android.permission.ACCESS_WIFI_STATE: granted=true
User 0: ceDataInode=1155675 installed=true hidden=false suspended=false stopped=true notLaunched=false enabled=0
gids=[3003]
runtime permissions:
android.permission.READ_EXTERNAL_STORAGE: granted=true
android.permission.READ_PHONE_STATE: granted=true
android.permission.WRITE_EXTERNAL_STORAGE: granted=true
User 999: ceDataInode=0 installed=false hidden=false suspended=false stopped=true notLaunched=true enabled=0
gids=[3003]
runtime permissions:
Dexopt state:
[org.mazhuang.guanggoo]
Instruction Set: arm64
path: /data/app/org.mazhuang.guanggoo-2/base.apk
status: /data/app/org.mazhuang.guanggoo-2/oat/arm64/base.odex [compilation_filter=speed-profile, status=kOatUpToDa
te]
```
### 查看应用安装路径
命令:
```
adb shell pm path <PACKAGE>
```
输出应用安装路径
输出示例:
```
adb shell pm path ecarx.weather
package:/data/app/ecarx.weather-1.apk
```
## 与应用交互
主要是使用 `am <command>` 命令，常用的 `<command>` 如下：
| command | 用途 |
|-----------------------------------|---------------------------------|
| `start [options] <INTENT>` | 启动 `<INTENT>` 指定的 Activity |
| `startservice [options] <INTENT>` | 启动 `<INTENT>` 指定的 Service |
| `broadcast [options] <INTENT>` | 发送 `<INTENT>` 指定的广播 |
| `force-stop <packagename>` | 停止 `<packagename>` 相关的进程 |
`<INTENT>` 参数很灵活，和写 Android 程序时代码里的 Intent 相对应。
用于决定 intent 对象的选项如下：
| 参数 | 含义 |
|------------------|---------------------------------------------------------------------------------------------|
| `-a <ACTION>` | 指定 action，比如 `android.intent.action.VIEW` |
| `-c <CATEGORY>` | 指定 category，比如 `android.intent.category.APP_CONTACTS` |
| `-n <COMPONENT>` | 指定完整 component 名，用于明确指定启动哪个 Activity，如 `com.example.app/.ExampleActivity` |
`<INTENT>` 里还能带数据，就像写代码时的 Bundle 一样：
| 参数 | 含义 |
|---------------------------------------------------------------|----------------------------------------|
| `--esn <EXTRA_KEY>` | null 值（只有 key 名） |
| `-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE>` | string 值 |
| `--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>` | boolean 值 |
| `--ei <EXTRA_KEY> <EXTRA_INT_VALUE>` | integer 值 |
| `--el <EXTRA_KEY> <EXTRA_LONG_VALUE>` | long 值 |
| `--ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE>` | float 值 |
| `--eu <EXTRA_KEY> <EXTRA_URI_VALUE>` | URI |
| `--ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>` | component name |
| `--eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]` | integer 数组 |
| `--ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]` | long 数组 |
### 启动应用/ 调起 Activity
> 指定Activity名称启动
命令格式：
```sh
adb shell am start [options] <INTENT>
```
例如：
```sh
adb shell am start -n com.tencent.mm/.ui.LauncherUI
```
表示调起微信主界面。
```sh
adb shell am start -n org.mazhuang.boottimemeasure/.MainActivity --es "toast" "hello, world"
```
表示调起 `org.mazhuang.boottimemeasure/.MainActivity` 并传给它 string 数据键值对 `toast - hello, world`。
> 不指定Activity名称启动（启动主Activity）
命令格式：
```sh
adb shell monkey -p <packagename> -c android.intent.category.LAUNCHER 1
```
例如：
```sh
adb shell monkey -p com.tencent.mm -c android.intent.category.LAUNCHER 1
```
表示调起微信主界面。
### 调起 Service
命令格式：
```sh
adb shell am startservice [options] <INTENT>
```
例如：
```sh
adb shell am startservice -n com.tencent.mm/.plugin.accountsync.model.AccountAuthenticatorService
```
表示调起微信的某 Service。
另外一个典型的用例是如果设备上原本应该显示虚拟按键但是没有显示，可以试试这个：
```sh
adb shell am startservice -n com.android.systemui/.SystemUIService
```
### 停止 Service
命令格式：
```sh
adb shell am stopservice [options] <INTENT>
```
### 发送广播
命令格式：
```sh
adb shell am broadcast [options] <INTENT>
```
可以向所有组件广播，也可以只向指定组件广播。
例如，向所有组件广播 `BOOT_COMPLETED`：
```sh
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED
```
又例如，只向 `org.mazhuang.boottimemeasure/.BootCompletedReceiver` 广播 `BOOT_COMPLETED`：
```sh
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n org.mazhuang.boottimemeasure/.BootCompletedReceiver
```
这类用法在测试的时候很实用，比如某个广播的场景很难制造，可以考虑通过这种方式来发送广播。
既能发送系统预定义的广播，也能发送自定义广播。如下是部分系统预定义广播及正常触发时机：
| action | 触发时机 |
|-------------------------------------------------|-----------------------------------------------|
| android.net.conn.CONNECTIVITY_CHANGE | 网络连接发生变化 |
| android.intent.action.SCREEN_ON | 屏幕点亮 |
| android.intent.action.SCREEN_OFF | 屏幕熄灭 |
| android.intent.action.BATTERY_LOW | 电量低，会弹出电量低提示框 |
| android.intent.action.BATTERY_OKAY | 电量恢复了 |
| android.intent.action.BOOT_COMPLETED | 设备启动完毕 |
| android.intent.action.DEVICE_STORAGE_LOW | 存储空间过低 |
| android.intent.action.DEVICE_STORAGE_OK | 存储空间恢复 |
| android.intent.action.PACKAGE_ADDED | 安装了新的应用 |
| android.net.wifi.STATE_CHANGE | WiFi 连接状态发生变化 |
| android.net.wifi.WIFI_STATE_CHANGED | WiFi 状态变为启用/关闭/正在启动/正在关闭/未知 |
| android.intent.action.BATTERY_CHANGED | 电池电量发生变化 |
| android.intent.action.INPUT_METHOD_CHANGED | 系统输入法发生变化 |
| android.intent.action.ACTION_POWER_CONNECTED | 外部电源连接 |
| android.intent.action.ACTION_POWER_DISCONNECTED | 外部电源断开连接 |
| android.intent.action.DREAMING_STARTED | 系统开始休眠 |
| android.intent.action.DREAMING_STOPPED | 系统停止休眠 |
| android.intent.action.WALLPAPER_CHANGED | 壁纸发生变化 |
| android.intent.action.HEADSET_PLUG | 插入耳机 |
| android.intent.action.MEDIA_UNMOUNTED | 卸载外部介质 |
| android.intent.action.MEDIA_MOUNTED | 挂载外部介质 |
| android.os.action.POWER_SAVE_MODE_CHANGED | 省电模式开启 |
*（以上广播均可使用 adb 触发）*
### 强制停止应用
命令：
```sh
adb shell am force-stop <packagename>
```
命令示例：
```sh
adb shell am force-stop com.qihoo360.mobilesafe
```
表示停止 360 安全卫士的一切进程与服务。
### 收紧内存
命令：
```sh
adb shell am send-trim-memory <pid> <level>
```
pid: 进程 ID
level:
HIDDEN、RUNNING_MODERATE、BACKGROUND、
RUNNING_LOW、MODERATE、RUNNING_CRITICAL、COMPLETE
命令示例：
```sh
adb shell am send-trim-memory 12345 RUNNING_LOW
```
表示向 pid=12345 的进程，发出 level=RUNNING_LOW 的收紧内存命令。
## 文件管理
### 复制设备里的文件到电脑
命令：
```sh
adb pull <设备里的文件路径> [电脑上的目录]
```
其中 `电脑上的目录` 参数可以省略，默认复制到当前目录。
例：
```sh
adb pull /sdcard/sr.mp4 ~/tmp/
```
*小技巧：*设备上的文件路径可能需要 root 权限才能访问，如果你的设备已经 root 过，可以先使用 `adb shell` 和 `su` 命令在 adb shell 里获取 root 权限后，先 `cp /path/on/device /sdcard/filename` 将文件复制到 sdcard，然后 `adb pull /sdcard/filename /path/on/pc`。
### 复制电脑里的文件到设备
命令：
```sh
adb push <电脑上的文件路径> <设备里的目录>
```
例：
```sh
adb push ~/sr.mp4 /sdcard/
```
*小技巧：*设备上的文件路径普通权限可能无法直接写入，如果你的设备已经 root 过，可以先 `adb push /path/on/pc /sdcard/filename`，然后 `adb shell` 和 `su` 在 adb shell 里获取 root 权限后，`cp /sdcard/filename /path/on/device`。
## 模拟按键/输入
在 `adb shell` 里有个很实用的命令叫 `input`，通过它可以做一些有趣的事情。
`input` 命令的完整 help 信息如下：
```sh
Usage: input [<source>] <command> [<arg>...]
The sources are:
mouse
keyboard
joystick
touchnavigation
touchpad
trackball
stylus
dpad
gesture
touchscreen
gamepad
The commands and default sources are:
text <string> (Default: touchscreen)
keyevent [--longpress] <key code number or name> ... (Default: keyboard)
tap <x> <y> (Default: touchscreen)
swipe <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
press (Default: trackball)
roll <dx> <dy> (Default: trackball)
```
比如使用 `adb shell input keyevent <keycode>` 命令，不同的 keycode 能实现不同的功能，完整的 keycode 列表详见 [KeyEvent](https://developer.android.com/reference/android/view/KeyEvent.html)，摘引部分我觉得有意思的如下：
| keycode | 含义 |
|---------|--------------------------------|
| 3 | HOME 键 |
| 4 | 返回键 |
| 5 | 打开拨号应用 |
| 6 | 挂断电话 |
| 24 | 增加音量 |
| 25 | 降低音量 |
| 26 | 电源键 |
| 27 | 拍照（需要在相机应用里） |
| 64 | 打开浏览器 |
| 82 | 菜单键 |
| 85 | 播放/暂停 |
| 86 | 停止播放 |
| 87 | 播放下一首 |
| 88 | 播放上一首 |
| 122 | 移动光标到行首或列表顶部 |
| 123 | 移动光标到行末或列表底部 |
| 126 | 恢复播放 |
| 127 | 暂停播放 |
| 164 | 静音 |
| 176 | 打开系统设置 |
| 187 | 切换应用 |
| 207 | 打开联系人 |
| 208 | 打开日历 |
| 209 | 打开音乐 |
| 210 | 打开计算器 |
| 220 | 降低屏幕亮度 |
| 221 | 提高屏幕亮度 |
| 223 | 系统休眠 |
| 224 | 点亮屏幕 |
| 231 | 打开语音助手 |
| 276 | 如果没有 wakelock 则让系统休眠 |
下面是 `input` 命令的一些用法举例。
### 电源键
命令：
```sh
adb shell input keyevent 26
```
执行效果相当于按电源键。
### 菜单键
命令：
```sh
adb shell input keyevent 82
```
### HOME 键
命令：
```sh
adb shell input keyevent 3
```
### 返回键
命令：
```sh
adb shell input keyevent 4
```
### 音量控制
增加音量：
```sh
adb shell input keyevent 24
```
降低音量：
```sh
adb shell input keyevent 25
```
静音：
```sh
adb shell input keyevent 164
```
### 媒体控制
播放/暂停：
```sh
adb shell input keyevent 85
```
停止播放：
```sh
adb shell input keyevent 86
```
播放下一首：
```sh
adb shell input keyevent 87
```
播放上一首：
```sh
adb shell input keyevent 88
```
恢复播放：
```sh
adb shell input keyevent 126
```
暂停播放：
```sh
adb shell input keyevent 127
```
### 点亮/熄灭屏幕
可以通过上文讲述过的模拟电源键来切换点亮和熄灭屏幕，但如果明确地想要点亮或者熄灭屏幕，那可以使用如下方法。
点亮屏幕：
```sh
adb shell input keyevent 224
```
熄灭屏幕：
```sh
adb shell input keyevent 223
```
### 滑动解锁
如果锁屏没有密码，是通过滑动手势解锁，那么可以通过 `input swipe` 来解锁。
命令（参数以机型 Nexus 5，向上滑动手势解锁举例）：
```sh
adb shell input swipe 300 1000 300 500
```
参数 `300 1000 300 500` 分别表示`起始点x坐标 起始点y坐标 结束点x坐标 结束点y坐标`。
### 输入文本
在焦点处于某文本框时，可以通过 `input` 命令来输入文本。
命令：
```sh
adb shell input text hello
```
现在 `hello` 出现在文本框了。
如果想输入中文，可以在设备上安装 [ADBKeyBoard.apk](https://github.com/senzhk/ADBKeyBoard)，详细文档参考 [这里](https://github.com/senzhk/ADBKeyBoard)。
然后执行命令:
```sh
# 1. 设置当前输入法为 ADBKeyBoard
adb shell ime set com.android.adbkeyboard/.AdbIME
# 2. 输入中文
adb shell am broadcast -a ADB_INPUT_TEXT --es msg '你好'
```
## 查看日志
Android 系统的日志分为两部分，底层的 Linux 内核日志输出到 /proc/kmsg，Android 的日志输出到 /dev/log。
### Android 日志
命令格式：
```sh
[adb] logcat [<option>] ... [<filter-spec>] ...
```
常用用法列举如下：
#### 按级别过滤日志
Android 的日志分为如下几个优先级（priority）：
* V —— Verbose（最低，输出得最多）
* D —— Debug
* I —— Info
* W —— Warning
* E —— Error
* F —— Fatal
* S —— Silent（最高，啥也不输出）
按某级别过滤日志则会将该级别及以上的日志输出。
比如，命令：
```sh
adb logcat *:W
```
会将 Warning、Error、Fatal 和 Silent 日志输出。
（**注：** 在 macOS 下需要给 `*:W` 这样以 `*` 作为 tag 的参数加双引号，如 `adb logcat "*:W"`，不然会报错 `no matches found: *:W`。）
#### 按 tag 和级别过滤日志
`<filter-spec>` 可以由多个 `<tag>[:priority]` 组成。
比如，命令：
```sh
adb logcat ActivityManager:I MyApp:D *:S
```
表示输出 tag `ActivityManager` 的 Info 以上级别日志，输出 tag `MyApp` 的 Debug 以上级别日志，及其它 tag 的 Silent 级别日志（即屏蔽其它 tag 日志）。
#### 日志格式
可以用 `adb logcat -v <format>` 选项指定日志输出格式。
日志支持按以下几种 `<format>`：
* brief
默认格式。格式为：
```sh
<priority>/<tag>(<pid>): <message>
```
示例：
```sh
D/HeadsetStateMachine( 1785): Disconnected process message: 10, size: 0
```
* process
格式为：
```sh
<priority>(<pid>) <message>
```
示例：
```sh
D( 1785) Disconnected process message: 10, size: 0 (HeadsetStateMachine)
```
* tag
格式为：
```sh
<priority>/<tag>: <message>
```
示例：
```sh
D/HeadsetStateMachine: Disconnected process message: 10, size: 0
```
* raw
格式为：
```sh
<message>
```
示例：
```sh
Disconnected process message: 10, size: 0
```
* time
格式为：
```sh
<datetime> <priority>/<tag>(<pid>): <message>
```
示例：
```sh
08-28 22:39:39.974 D/HeadsetStateMachine( 1785): Disconnected process message: 10, size: 0
```
* threadtime
格式为：
```sh
<datetime> <pid> <tid> <priority> <tag>: <message>
```
示例：
```sh
08-28 22:39:39.974 1785 1832 D HeadsetStateMachine: Disconnected process message: 10, size: 0
```
* long
格式为：
```sh
[ <datetime> <pid>:<tid> <priority>/<tag> ]
<message>
```
示例：
```sh
[ 08-28 22:39:39.974 1785: 1832 D/HeadsetStateMachine ]
Disconnected process message: 10, size: 0
```
指定格式可与上面的过滤同时使用。比如：
```sh
adb logcat -v long ActivityManager:I *:S
```
#### 清空日志
```sh
adb logcat -c
```
### 内核日志
命令：
```sh
adb shell dmesg
```
输出示例：
```sh
<6>[14201.684016] PM: noirq resume of devices complete after 0.982 msecs
<6>[14201.685525] PM: early resume of devices complete after 0.838 msecs
<6>[14201.753642] PM: resume of devices complete after 68.106 msecs
<4>[14201.755954] Restarting tasks ... done.
<6>[14201.771229] PM: suspend exit 2016-08-28 13:31:32.679217193 UTC
<6>[14201.872373] PM: suspend entry 2016-08-28 13:31:32.780363596 UTC
<6>[14201.872498] PM: Syncing filesystems ... done.
```
中括号里的 `[14201.684016]` 代表内核开始启动后的时间，单位为秒。
通过内核日志我们可以做一些事情，比如衡量内核启动时间，在系统启动完毕后的内核日志里找到 `Freeing init memory` 那一行前面的时间就是。
## 查看设备信息
### 型号
命令：
```sh
adb shell getprop ro.product.model
```
输出示例：
```sh
Nexus 5
```
### 电池状况
命令：
```sh
adb shell dumpsys battery
```
输入示例：
```sh
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
status: 2
health: 2
present: true
level: 44
scale: 100
voltage: 3872
temperature: 280
technology: Li-poly
```
其中 `scale` 代表最大电量，`level` 代表当前电量。上面的输出表示还剩下 44% 的电量。
### 屏幕分辨率
命令：
```sh
adb shell wm size
```
输出示例：
```sh
Physical size: 1080x1920
```
该设备屏幕分辨率为 1080px * 1920px。
如果使用命令修改过，那输出可能是：
```sh
Physical size: 1080x1920
Override size: 480x1024
```
表明设备的屏幕分辨率原本是 1080px * 1920px，当前被修改为 480px * 1024px。
### 屏幕密度
命令：
```sh
adb shell wm density
```
输出示例：
```sh
Physical density: 420
```
该设备屏幕密度为 420dpi。
如果使用命令修改过，那输出可能是：
```sh
Physical density: 480
Override density: 160
```
表明设备的屏幕密度原来是 480dpi，当前被修改为 160dpi。
### 显示屏参数
命令：
```sh
adb shell dumpsys window displays
```
输出示例：
```sh
WINDOW MANAGER DISPLAY CONTENTS (dumpsys window displays)
Display: mDisplayId=0
init=1080x1920 420dpi cur=1080x1920 app=1080x1794 rng=1080x1017-1810x1731
deferred=false layoutNeeded=false
```
其中 `mDisplayId` 为 显示屏编号，`init` 是初始分辨率和屏幕密度，`app` 的高度比 `init` 里的要小，表示屏幕底部有虚拟按键，高度为 1920 - 1794 = 126px 合 42dp。
### android\_id
命令：
```sh
adb shell settings get secure android_id
```
输出示例：
```sh
51b6be48bac8c569
```
### IMEI
在 Android 4.4 及以下版本可通过如下命令获取 IMEI：
```sh
adb shell dumpsys iphonesubinfo
```
输出示例：
```sh
Phone Subscriber Info:
Phone Type = GSM
Device ID = 860955027785041
```
其中的 `Device ID` 就是 IMEI。
而在 Android 5.0 及以上版本里这个命令输出为空，得通过其它方式获取了（需要 root 权限）：
```sh
adb shell
su
service call iphonesubinfo 1
```
输出示例：
```sh
Result: Parcel(
0x00000000: 00000000 0000000f 00360038 00390030 '........8.6.0.9.'
0x00000010: 00350035 00320030 00370037 00350038 '5.5.0.2.7.7.8.5.'
0x00000020: 00340030 00000031 '0.4.1... ')
```
把里面的有效内容提取出来就是 IMEI 了，比如这里的是 `860955027785041`。
参考：[adb shell dumpsys iphonesubinfo not working since Android 5.0 Lollipop](http://stackoverflow.com/questions/27002663/adb-shell-dumpsys-iphonesubinfo-not-working-since-android-5-0-lollipop)
### Android 系统版本
命令：
```sh
adb shell getprop ro.build.version.release
```
输出示例：
```sh
5.0.2
```
### IP 地址
每次想知道设备的 IP 地址的时候都得「设置」-「关于手机」-「状态信息」-「IP地址」很烦对不对？通过 adb 可以方便地查看。
命令：
```sh
adb shell ifconfig | grep Mask
```
输出示例：
```sh
inet addr:10.130.245.230 Mask:255.255.255.252
inet addr:127.0.0.1 Mask:255.0.0.0
```
那么 `10.130.245.230` 就是设备 IP 地址。
在有的设备上这个命令没有输出，如果设备连着 WiFi，可以使用如下命令来查看局域网 IP：
```sh
adb shell ifconfig wlan0
```
输出示例：
```sh
wlan0: ip 10.129.160.99 mask 255.255.240.0 flags [up broadcast running multicast]
```
或
```sh
wlan0 Link encap:UNSPEC
inet addr:10.129.168.57 Bcast:10.129.175.255 Mask:255.255.240.0
inet6 addr: fe80::66cc:2eff:fe68:b6b6/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:496520 errors:0 dropped:0 overruns:0 frame:0
TX packets:68215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:116266821 TX bytes:8311736
```
如果以上命令仍然不能得到期望的信息，那可以试试以下命令（部分系统版本里可用）：
```sh
adb shell netcfg
```
输出示例：
```sh
wlan0 UP 10.129.160.99/20 0x00001043 f8:a9:d0:17:42:4d
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
p2p0 UP 0.0.0.0/0 0x00001003 fa:a9:d0:17:42:4d
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
rmnet0 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet3 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet4 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet6 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet5 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rmnet7 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
rev_rmnet3 DOWN 0.0.0.0/0 0x00001002 4e:b7:e4:2e:17:58
rev_rmnet2 DOWN 0.0.0.0/0 0x00001002 4e:f0:c8:bf:7a:cf
rev_rmnet4 DOWN 0.0.0.0/0 0x00001002 a6:c0:3b:6b:c4:1f
rev_rmnet6 DOWN 0.0.0.0/0 0x00001002 66:bb:5d:64:2e:e9
rev_rmnet5 DOWN 0.0.0.0/0 0x00001002 0e:1b:eb:b9:23:a0
rev_rmnet7 DOWN 0.0.0.0/0 0x00001002 7a:d9:f6:81:40:5a
rev_rmnet8 DOWN 0.0.0.0/0 0x00001002 4e:e2:a9:bb:d0:1b
rev_rmnet0 DOWN 0.0.0.0/0 0x00001002 fe:65:d0:ca:82:a9
rev_rmnet1 DOWN 0.0.0.0/0 0x00001002 da:d8:e8:4f:2e:fe
```
可以看到网络连接名称、启用状态、IP 地址和 Mac 地址等信息。
### Mac 地址
命令：
```sh
adb shell cat /sys/class/net/wlan0/address
```
输出示例：
```sh
f8:a9:d0:17:42:4d
```
这查看的是局域网 Mac 地址，移动网络或其它连接的信息可以通过前面的小节「IP 地址」里提到的 `adb shell netcfg` 命令来查看。
### CPU 信息
命令：
```sh
adb shell cat /proc/cpuinfo
```
输出示例：
```sh
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 38.40
processor : 1
BogoMIPS : 38.40
processor : 2
BogoMIPS : 38.40
processor : 3
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x06f
CPU revision : 0
Hardware : Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
Revision : 000b
Serial : 0000000000000000
```
这是 Nexus 5 的 CPU 信息，我们从输出里可以看到使用的硬件是 `Qualcomm MSM 8974`，processor 的编号是 0 到 3，所以它是四核的，采用的架构是 `ARMv7 Processor rev 0 (v71)`。
### 内存信息
命令：
```sh
adb shell cat /proc/meminfo
```
输出示例：
```sh
MemTotal: 1027424 kB
MemFree: 486564 kB
Buffers: 15224 kB
Cached: 72464 kB
SwapCached: 24152 kB
Active: 110572 kB
Inactive: 259060 kB
Active(anon): 79176 kB
Inactive(anon): 207736 kB
Active(file): 31396 kB
Inactive(file): 51324 kB
Unevictable: 3948 kB
Mlocked: 0 kB
HighTotal: 409600 kB
HighFree: 132612 kB
LowTotal: 617824 kB
LowFree: 353952 kB
SwapTotal: 262140 kB
SwapFree: 207572 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 265324 kB
Mapped: 47072 kB
Shmem: 1020 kB
Slab: 57372 kB
SReclaimable: 7692 kB
SUnreclaim: 49680 kB
KernelStack: 4512 kB
PageTables: 5912 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 775852 kB
Committed_AS: 13520632 kB
VmallocTotal: 385024 kB
VmallocUsed: 61004 kB
VmallocChunk: 209668 kB
```
其中，`MemTotal` 就是设备的总内存，`MemFree` 是当前空闲内存。
### 更多硬件与系统属性
设备的更多硬件与系统属性可以通过如下命令查看：
```sh
adb shell cat /system/build.prop
```
这会输出很多信息，包括前面几个小节提到的「型号」和「Android 系统版本」等。
输出里还包括一些其它有用的信息，它们也可通过 `adb shell getprop <属性名>` 命令单独查看，列举一部分属性如下：
| 属性名 | 含义 |
|---------------------------------|-------------------------------|
| ro.build.version.sdk | SDK 版本 |
| ro.build.version.release | Android 系统版本 |
| ro.build.version.security_patch | Android 安全补丁程序级别 |
| ro.product.model | 型号 |
| ro.product.brand | 品牌 |
| ro.product.name | 设备名 |
| ro.product.board | 处理器型号 |
| ro.product.cpu.abilist | CPU 支持的 abi 列表[*节注一*] |
| persist.sys.isUsbOtgEnabled | 是否支持 OTG |
| dalvik.vm.heapsize | 每个应用程序的内存上限 |
| ro.sf.lcd_density | 屏幕密度 |
*节注一：*
一些小厂定制的 ROM 可能修改过 CPU 支持的 abi 列表的属性名，如果用 `ro.product.cpu.abilist` 属性名查找不到，可以这样试试：
```sh
adb shell cat /system/build.prop | grep ro.product.cpu.abi
```
示例输出：
```sh
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
```
## 修改设置
**注：** 修改设置之后，运行恢复命令有可能显示仍然不太正常，可以运行 `adb reboot` 重启设备，或手动重启。
修改设置的原理主要是通过 settings 命令修改 /data/data/com.android.providers.settings/databases/settings.db 里存放的设置值。
### 分辨率
命令：
```sh
adb shell wm size 480x1024
```
表示将分辨率修改为 480px * 1024px。
恢复原分辨率命令：
```sh
adb shell wm size reset
```
### 屏幕密度
命令：
```sh
adb shell wm density 160
```
表示将屏幕密度修改为 160dpi。
恢复原屏幕密度命令：
```sh
adb shell wm density reset
```
### 显示区域
命令：
```sh
adb shell wm overscan 0,0,0,200
```
四个数字分别表示距离左、上、右、下边缘的留白像素，以上命令表示将屏幕底部 200px 留白。
恢复原显示区域命令：
```sh
adb shell wm overscan reset
```
### 关闭 USB 调试模式
命令：
```sh
adb shell settings put global adb_enabled 0
```
恢复：
用命令恢复不了了，毕竟关闭了 USB 调试 adb 就连接不上 Android 设备了。
去设备上手动恢复吧：「设置」-「开发者选项」-「Android 调试」。
### 允许/禁止访问非 SDK API
允许访问非 SDK API：
```sh
adb shell settings put global hidden_api_policy_pre_p_apps 1
adb shell settings put global hidden_api_policy_p_apps 1
```
禁止访问非 SDK API：
```sh
adb shell settings delete global hidden_api_policy_pre_p_apps
adb shell settings delete global hidden_api_policy_p_apps
```
不需要设备获得 Root 权限。
命令最后的数字的含义：
| 值 | 含义 |
|----|---------------------------------------------------------------------------------------------------------------------------|
| 0 | 禁止检测非 SDK 接口的调用。该情况下，日志记录功能被禁用，并且令 strict mode API，即 detectNonSdkApiUsage() 无效。不推荐。 |
| 1 | 仅警告——允许访问所有非 SDK 接口，但保留日志中的警告信息，可继续使用 strick mode API。 |
| 2 | 禁止调用深灰名单和黑名单中的接口。 |
| 3 | 禁止调用黑名单中的接口，但允许调用深灰名单中的接口。 |
### 状态栏和导航栏的显示隐藏
本节所说的相关设置对应 Cyanogenmod 里的「扩展桌面」。
命令：
```sh
adb shell settings put global policy_control <key-values>
```
`<key-values>` 可由如下几种键及其对应的值组成，格式为 `<key1>=<value1>:<key2>=<value2>`。
| key | 含义 |
|-----------------------|------------|
| immersive.full | 同时隐藏 |
| immersive.status | 隐藏状态栏 |
| immersive.navigation | 隐藏导航栏 |
| immersive.preconfirms | ? |
这些键对应的值可则如下值用逗号组合：
| value | 含义 |
|----------------|--------------|
| `apps` | 所有应用 |
| `*` | 所有界面 |
| `packagename` | 指定应用 |
| `-packagename` | 排除指定应用 |
例如：
```sh
adb shell settings put global policy_control immersive.full=*
```
表示设置在所有界面下都同时隐藏状态栏和导航栏。
```sh
adb shell settings put global policy_control immersive.status=com.package1,com.package2:immersive.navigation=apps,-com.package3
```
表示设置在包名为 `com.package1` 和 `com.package2` 的应用里隐藏状态栏，在除了包名为 `com.package3` 的所有应用里隐藏导航栏。
## 实用功能
### 屏幕截图
截图保存到电脑：
```sh
adb exec-out screencap -p > sc.png
```
如果 adb 版本较老，无法使用 `exec-out` 命令，这时候建议更新 adb 版本。无法更新的话可以使用以下麻烦点的办法：
先截图保存到设备里：
```sh
adb shell screencap -p /sdcard/sc.png
```
然后将 png 文件导出到电脑：
```sh
adb pull /sdcard/sc.png
```
可以使用 `adb shell screencap -h` 查看 `screencap` 命令的帮助信息，下面是两个有意义的参数及含义：
| 参数 | 含义 |
|---------------|--------------------------------------------|
| -p | 指定保存文件为 png 格式 |
| -d display-id | 指定截图的显示屏编号（有多显示屏的情况下） |
实测如果指定文件名以 `.png` 结尾时可以省略 -p 参数；否则需要使用 -p 参数。如果不指定文件名，截图文件的内容将直接输出到 stdout。
另外一种一行命令截图并保存到电脑的方法：
*Linux 和 Windows*
```sh
adb shell screencap -p | sed "s/\r$//" > sc.png
```
*Mac OS X*
```sh
adb shell screencap -p | gsed "s/\r$//" > sc.png
```
这个方法需要用到 gnu sed 命令，在 Linux 下直接就有，在 Windows 下 Git 安装目录的 bin 文件夹下也有。如果确实找不到该命令，可以下载 [sed for Windows](http://gnuwin32.sourceforge.net/packages/sed.htm) 并将 sed.exe 所在文件夹添加到 PATH 环境变量里。
而在 Mac 下使用系统自带的 sed 命令会报错：
```sh
sed: RE error: illegal byte sequence
```
需要安装 gnu-sed，然后使用 gsed 命令：
```sh
brew install gnu-sed
```
### 录制屏幕
录制屏幕以 mp4 格式保存到 /sdcard：
```sh
adb shell screenrecord /sdcard/filename.mp4
```
需要停止时按 <kbd>Ctrl-C</kbd>，默认录制时间和最长录制时间都是 180 秒。
如果需要导出到电脑：
```sh
adb pull /sdcard/filename.mp4
```
可以使用 `adb shell screenrecord --help` 查看 `screenrecord` 命令的帮助信息，下面是常见参数及含义：
| 参数 | 含义 |
|---------------------|-------------------------------------------------|
| --size WIDTHxHEIGHT | 视频的尺寸，比如 `1280x720`，默认是屏幕分辨率。 |
| --bit-rate RATE | 视频的比特率，默认是 4Mbps。 |
| --time-limit TIME | 录制时长，单位秒。 |
| --verbose | 输出更多信息。 |
### 重新挂载 system 分区为可写
**注：需要 root 权限。**
/system 分区默认挂载为只读，但有些操作比如给 Android 系统添加命令、删除自带应用等需要对 /system 进行写操作，所以需要重新挂载它为可读写。
步骤：
1. 进入 shell 并切换到 root 用户权限。
命令：
```sh
adb shell
su
```
2. 查看当前分区挂载情况。
命令：
```sh
mount
```
输出示例：
```sh
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /var tmpfs rw,seclabel,relatime,mode=770,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
none /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
```
找到其中我们关注的带 /system 的那一行：
```sh
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
```
3. 重新挂载。
命令：
```sh
mount -o remount,rw -t yaffs2 /dev/block/platform/msm_sdcc.1/by-name/system /system
```
这里的 `/dev/block/platform/msm_sdcc.1/by-name/system` 就是我们从上一步的输出里得到的文件路径。
如果输出没有提示错误的话，操作就成功了，可以对 /system 下的文件为所欲为了。
### 查看连接过的 WiFi 密码
**注：需要 root 权限。**
命令：
```sh
adb shell
su
cat /data/misc/wifi/*.conf
```
输出示例：
```sh
network={
ssid="TP-LINK_9DFC"
scan_ssid=1
psk="123456789"
key_mgmt=WPA-PSK
group=CCMP TKIP
auth_alg=OPEN
sim_num=1
priority=13893
}
network={
ssid="TP-LINK_F11E"
psk="987654321"
key_mgmt=WPA-PSK
sim_num=1
priority=17293
}
```
`ssid` 即为我们在 WLAN 设置里看到的名称，`psk` 为密码，`key_mgmt` 为安全加密方式。
如果 Android O 或以后，WiFi 密码保存的地址有变化，是在 `WifiConfigStore.xml` 里面
```sh
adb shell
su
cat /data/misc/wifi/WifiConfigStore.xml
```
输出格式：
数据项较多，只需关注 `ConfigKey`（WiFi 名字）和 `PreSharedKey`（WiFi 密码）即可
```xml
<string name="ConfigKey">"Wi-Fi"WPA_PSK</string>
<string name="PreSharedKey">"931907334"</string>
```
### 设置系统日期和时间
**注：需要 root 权限。**
命令：
```sh
adb shell
su
date -s 20160823.131500
```
表示将系统日期和时间更改为 2016 年 08 月 23 日 13 点 15 分 00 秒。
### 重启手机
命令：
```sh
adb reboot
```
### 检测设备是否已 root
命令：
```sh
adb shell
su
```
此时命令行提示符是 `$` 则表示没有 root 权限，是 `#` 则表示已 root。
### 使用 Monkey 进行压力测试
Monkey 可以生成伪随机用户事件来模拟单击、触摸、手势等操作，可以对正在开发中的程序进行随机压力测试。
简单用法：
```sh
adb shell monkey -p <packagename> -v 500
```
表示向 `<packagename>` 指定的应用程序发送 500 个伪随机事件。
Monkey 的详细用法参考 [官方文档](https://developer.android.com/studio/test/monkey.html)。
### 开启/关闭 WiFi
**注：需要 root 权限。**
有时需要控制设备的 WiFi 状态，可以用以下指令完成。
开启 WiFi：
```sh
adb root
adb shell svc wifi enable
```
关闭 WiFi：
```sh
adb root
adb shell svc wifi disable
```
若执行成功，输出为空；若未取得 root 权限执行此命令，将执行失败，输出 `Killed`。
## 刷机相关命令
### 重启到 Recovery 模式
命令：
```sh
adb reboot recovery
```
### 从 Recovery 重启到 Android
命令：
```sh
adb reboot
```
### 重启到 Fastboot 模式
命令：
```sh
adb reboot bootloader
```
### 通过 sideload 更新系统
如果我们下载了 Android 设备对应的系统更新包到电脑上，那么也可以通过 adb 来完成更新。
以 Recovery 模式下更新为例：
1. 重启到 Recovery 模式。
命令：
```sh
adb reboot recovery
```
2. 在设备的 Recovery 界面上操作进入 `Apply update`-`Apply from ADB`。
注：不同的 Recovery 菜单可能与此有差异，有的是一级菜单就有 `Apply update from ADB`。
3. 通过 adb 上传和更新系统。
命令：
```sh
adb sideload <path-to-update.zip>
```
## 安全相关命令
### 启用/禁用 SELinux
启用 SELinux
```sh
adb root
adb shell setenforce 1
```
禁用 SELinux
```sh
adb root
adb shell setenforce 0
```
### 启用/禁用 dm_verity
启用 dm_verity
```sh
adb root
adb enable-verity
```
禁用 dm_verity
```sh
adb root
adb disable-verity
```
## 更多 adb shell 命令
Android 系统是基于 Linux 内核的，所以 Linux 里的很多命令在 Android 里也有相同或类似的实现，在 `adb shell` 里可以调用。本文档前面的部分内容已经用到了 `adb shell` 命令。
### 查看进程
命令：
```sh
adb shell ps
```
输出示例：
```sh
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 8904 788 ffffffff 00000000 S /init
root 2 0 0 0 ffffffff 00000000 S kthreadd
...
u0_a71 7779 5926 1538748 48896 ffffffff 00000000 S com.sohu.inputmethod.sogou:classic
u0_a58 7963 5926 1561916 59568 ffffffff 00000000 S org.mazhuang.boottimemeasure
...
shell 8750 217 10640 740 00000000 b6f28340 R ps
```
各列含义：
| 列名 | 含义 |
|------|-----------|
| USER | 所属用户 |
| PID | 进程 ID |
| PPID | 父进程 ID |
| NAME | 进程名 |
### 查看实时资源占用情况
命令：
```sh
adb shell top
```
输出示例：
```sh
User 0%, System 6%, IOW 0%, IRQ 0%
User 3 + Nice 0 + Sys 21 + Idle 280 + IOW 0 + IRQ 0 + SIRQ 3 = 307
PID PR CPU% S #THR VSS RSS PCY UID Name
8763 0 3% R 1 10640K 1064K fg shell top
131 0 3% S 1 0K 0K fg root dhd_dpc
6144 0 0% S 115 1682004K 115916K fg system system_server
132 0 0% S 1 0K 0K fg root dhd_rxf
1731 0 0% S 6 20288K 788K fg root /system/bin/mpdecision
217 0 0% S 6 18008K 356K fg shell /sbin/adbd
...
7779 2 0% S 19 1538748K 48896K bg u0_a71 com.sohu.inputmethod.sogou:classic
7963 0 0% S 18 1561916K 59568K fg u0_a58 org.mazhuang.boottimemeasure
...
```
各列含义：
| 列名 | 含义 |
|------|------------------------------------------------------------|
| PID | 进程 ID |
| PR | 优先级 |
| CPU% | 当前瞬间占用 CPU 百分比 |
| S | 进程状态（R=运行，S=睡眠，T=跟踪/停止，Z=僵尸进程） |
| #THR | 线程数 |
| VSS | Virtual Set Size 虚拟耗用内存（包含共享库占用的内存） |
| RSS | Resident Set Size 实际使用物理内存（包含共享库占用的内存） |
| PCY | 调度策略优先级，SP_BACKGROUND/SPFOREGROUND |
| UID | 进程所有者的用户 ID |
| NAME | 进程名 |
`top` 命令还支持一些命令行参数，详细用法如下：
```sh
Usage: top [ -m max_procs ] [ -n iterations ] [ -d delay ] [ -s sort_column ] [ -t ] [ -h ]
-m num 最多显示多少个进程
-n num 刷新多少次后退出
-d num 刷新时间间隔（单位秒，默认值 5）
-s col 按某列排序（可用 col 值：cpu, vss, rss, thr）
-t 显示线程信息
-h 显示帮助文档
```
### 查看进程 UID
有两种方案：
1. `adb shell dumpsys package <packagename> | grep userId=`
如：
```sh
$ adb shell dumpsys package org.mazhuang.guanggoo | grep userId=
userId=10394
```
2. 通过 ps 命令找到对应进程的 pid 之后 `adb shell cat /proc/<pid>/status | grep Uid`
如：
```sh
$ adb shell
gemini:/ $ ps | grep org.mazhuang.guanggoo
u0_a394 28635 770 1795812 78736 SyS_epoll_ 0000000000 S org.mazhuang.guanggoo
gemini:/ $ cat /proc/28635/status | grep Uid
Uid: 10394 10394 10394 10394
gemini:/ $
```
### 其它
如下是其它常用命令的简单描述，前文已经专门讲过的命令不再额外说明：
| 命令 | 功能 |
|-------|-----------------------------|
| cat | 显示文件内容 |
| cd | 切换目录 |
| chmod | 改变文件的存取模式/访问权限 |
| df | 查看磁盘空间使用情况 |
| grep | 过滤输出 |
| kill | 杀死指定 PID 的进程 |
| ls | 列举目录内容 |
| mount | 挂载目录的查看和管理 |
| mv | 移动或重命名文件 |
| ps | 查看正在运行的进程 |
| rm | 删除文件 |
| top | 查看进程的资源占用情况 |
## 常见问题
### 启动 adb server 失败
**出错提示**
```sh
error: protocol fault (couldn't read status): No error
```
**可能原因**
adb server 进程想使用的 5037 端口被占用。
**解决方案**
找到占用 5037 端口的进程，然后终止它。以 Windows 下为例：
```sh
netstat -ano | findstr LISTENING
...
TCP 0.0.0.0:5037 0.0.0.0:0 LISTENING 1548
...
```
这里 1548 即为进程 ID，用命令结束该进程：
```sh
taskkill /PID 1548
```
然后再启动 adb 就没问题了。
### com.android.ddmlib.AdbCommandRejectedException
在 Android Studio 里新建一个模拟器，但是用 adb 一直连接不上，提示：
```
com.android.ddmlib.AdbCommandRejectedException: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
```
在手机上安装一个终端然后执行 su 提示没有该命令，这不正常。
于是删除该模拟器后重新下载安装一次，这次就正常了。
## adb 的非官方实现
* [fb-adb](https://github.com/facebook/fb-adb) - A better shell for Android devices (for Mac).
## 相关命令
* [aapt](./related/aapt.md)
* [am](./related/am.md)
* [dumpsys](./related/dumpsys.md)
* [pm](./related/pm.md)
* [uiautomator](./related/uiautomator.md)
## 致谢
感谢朋友们无私的分享与补充（排名不分先后）。
[zxning](https://github.com/zxning)，[linhua55](https://github.com/linhua55)，[codeskyblue](https://github.com/codeskyblue)，[seasonyuu](https://github.com/seasonyuu)，[fan123199](https://github.com/fan123199)，[zhEdward](https://github.com/zhEdward)，[0x8BADFOOD](https://github.com/0x8BADFOOD)，[keith666666](https://github.com/keith666666)，[shawnlinboy](https://github.com/shawnlinboy)，[s-xq](https://github.com/s-xq)，
[lucky9322](https://github.com/lucky9322)。
## 参考链接
* [Android Debug Bridge](https://developer.android.com/studio/command-line/adb.html)
* [ADB Shell Commands](https://developer.android.com/studio/command-line/shell.html)
* [logcat Command-line Tool](https://developer.android.com/studio/command-line/logcat.html)
* [Android ADB命令大全](http://zmywly8866.github.io/2015/01/24/all-adb-command.html)
* [adb 命令行的使用记录](https://github.com/ZQiang94/StudyRecords/blob/master/other/src/main/java/com/other/adb%20%E5%91%BD%E4%BB%A4%E8%A1%8C%E7%9A%84%E4%BD%BF%E7%94%A8%E8%AE%B0%E5%BD%95.md)
* [Android ADB命令大全(通过ADB命令查看wifi密码、MAC地址、设备信息、操作文件、查看文件、日志信息、卸载、启动和安装APK等)](http://www.jianshu.com/p/860bc2bf1a6a)
* [那些做Android开发必须知道的ADB命令](http://yifeiyuan.me/2016/06/30/ADB%E5%91%BD%E4%BB%A4%E6%95%B4%E7%90%86/)
* [adb shell top](http://blog.csdn.net/kittyboy0001/article/details/38562515)
* [像高手一样使用ADB命令行（2）](http://cabins.github.io/2016/03/25/UseAdbLikeAPro-2/)
[1]: #ip-地址
================================================
FILE: related/aapt.md
================================================
# aapt 相关命令
```sh
Android Asset Packaging Tool
Usage:
aapt l[ist] [-v] [-a] file.{zip,jar,apk}
List contents of Zip-compatible archive.
aapt d[ump] [--values] [--include-meta-data] WHAT file.{apk} [asset [asset ...]]
strings Print the contents of the resource table string pool in the APK.
badging Print the label and icon for the app declared in APK.
permissions Print the permissions from the APK.
resources Print the resource table from the APK.
configurations Print the configurations in the APK.
xmltree Print the compiled xmls in the given assets.
xmlstrings Print the strings of the given compiled xml assets.
aapt p[ackage] [-d][-f][-m][-u][-v][-x][-z][-M AndroidManifest.xml] \
[-0 extension [-0 extension ...]] [-g tolerance] [-j jarfile] \
[--debug-mode] [--min-sdk-version VAL] [--target-sdk-version VAL] \
[--app-version VAL] [--app-version-name TEXT] [--custom-package VAL] \
[--rename-manifest-package PACKAGE] \
[--rename-instrumentation-target-package PACKAGE] \
[--utf16] [--auto-add-overlay] \
[--max-res-version VAL] \
[-I base-package [-I base-package ...]] \
[-A asset-source-dir] [-G class-list-file] [-P public-definitions-file] \
[-D main-dex-class-list-file] \
[-S resource-sources [-S resource-sources ...]] \
[-F apk-file] [-J R-file-dir] \
[--product product1,product2,...] \
[-c CONFIGS] [--preferred-density DENSITY] \
[--split CONFIGS [--split CONFIGS]] \
[--feature-of package [--feature-after package]] \
[raw-files-dir [raw-files-dir] ...] \
[--output-text-symbols DIR]
Package the android resources. It will read assets and resources that are
supplied with the -M -A -S or raw-files-dir arguments. The -J -P -F and -R
options control which files are output.
aapt r[emove] [-v] file.{zip,jar,apk} file1 [file2 ...]
Delete specified files from Zip-compatible archive.
aapt a[dd] [-v] file.{zip,jar,apk} file1 [file2 ...]
Add specified files to Zip-compatible archive.
aapt c[runch] [-v] -S resource-sources ... -C output-folder ...
Do PNG preprocessing on one or several resource folders
and store the results in the output folder.
aapt s[ingleCrunch] [-v] -i input-file -o outputfile
Do PNG preprocessing on a single file.
aapt v[ersion]
Print program version.
Modifiers:
-a print Android-specific data (resources, manifest) when listing
-c specify which configurations to include. The default is all
configurations. The value of the parameter should be a comma
separated list of configuration values. Locales should be specified
as either a language or language-region pair. Some examples:
en
port,en
port,land,en_US
-d one or more device assets to include, separated by commas
-f force overwrite of existing files
-g specify a pixel tolerance to force images to grayscale, default 0
-j specify a jar or zip file containing classes to include
-k junk path of file(s) added
-m make package directories under location specified by -J
-u update existing packages (add new, replace older, remove deleted files)
-v verbose output
-x create extending (non-application) resource IDs
-z require localization of resource attributes marked with
localization="suggested"
-A additional directory in which to find raw asset files
-G A file to output proguard options into.
-D A file to output proguard options for the main dex into.
-F specify the apk file to output
-I add an existing package to base include set
-J specify where to output R.java resource constant definitions
-M specify full path to AndroidManifest.xml to include in zip
-P specify where to output public resource definitions
-S directory in which to find resources. Multiple directories will be scanned
and the first match found (left to right) will take precedence.
-0 specifies an additional extension for which such files will not
be stored compressed in the .apk. An empty string means to not
compress any files at all.
--debug-mode
inserts android:debuggable="true" in to the application node of the
manifest, making the application debuggable even on production devices.
--include-meta-data
when used with "dump badging" also includes meta-data tags.
--pseudo-localize
generate resources for pseudo-locales (en-XA and ar-XB).
--min-sdk-version
inserts android:minSdkVersion in to manifest. If the version is 7 or
higher, the default encoding for resources will be in UTF-8.
--target-sdk-version
inserts android:targetSdkVersion in to manifest.
--max-res-version
ignores versioned resource directories above the given value.
--values
when used with "dump resources" also includes resource values.
--version-code
inserts android:versionCode in to manifest.
--version-name
inserts android:versionName in to manifest.
--replace-version
If --version-code and/or --version-name are specified, these
values will replace any value already in the manifest. By
default, nothing is changed if the manifest already defines
these attributes.
--custom-package
generates R.java into a different package.
--extra-packages
generate R.java for libraries. Separate libraries with ':'.
--generate-dependencies
generate dependency files in the same directories for R.java and resource package
--auto-add-overlay
Automatically add resources that are only in overlays.
--preferred-density
Specifies a preference for a particular density. Resources that do not
match this density and have variants that are a closer match are removed.
--split
Builds a separate split APK for the configurations listed. This can
be loaded alongside the base APK at runtime.
--feature-of
Builds a split APK that is a feature of the apk specified here. Resources
in the base APK can be referenced from the the feature APK.
--feature-after
An app can have multiple Feature Split APKs which must be totally ordered.
If --feature-of is specified, this flag specifies which Feature Split APK
comes before this one. The first Feature Split APK should not define
anything here.
--rename-manifest-package
Rewrite the manifest so that its package name is the package name
given here. Relative class names (for example .Foo) will be
changed to absolute names with the old package so that the code
does not need to change.
--rename-instrumentation-target-package
Rewrite the manifest so that all of its instrumentation
components target the given package. Useful when used in
conjunction with --rename-manifest-package to fix tests against
a package that has been renamed.
--product
Specifies which variant to choose for strings that have
product variants
--utf16
changes default encoding for resources to UTF-16. Only useful when API
level is set to 7 or higher where the default encoding is UTF-8.
--non-constant-id
Make the resources ID non constant. This is required to make an R java class
that does not contain the final value but is used to make reusable compiled
libraries that need to access resources.
--shared-lib
Make a shared library resource package that can be loaded by an application
at runtime to access the libraries resources. Implies --non-constant-id.
--app-as-shared-lib
Make an app resource package that also can be loaded as shared library at runtime.
Implies --non-constant-id.
--error-on-failed-insert
Forces aapt to return an error if it fails to insert values into the manifest
with --debug-mode, --min-sdk-version, --target-sdk-version --version-code
and --version-name.
Insertion typically fails if the manifest already defines the attribute.
--error-on-missing-config-entry
Forces aapt to return an error if it fails to find an entry for a configuration.
--output-text-symbols
Generates a text file containing the resource symbols of the R class in the
specified folder.
--ignore-assets
Assets to be ignored. Default pattern is:
!.svn:!.git:!.ds_store:!*.scc:.*:<dir>_*:!CVS:!thumbs.db:!picasa.ini:!*~
--skip-symbols-without-default-localization
Prevents symbols from being generated for strings that do not have a default
localization
--no-version-vectors
Do not automatically generate versioned copies of vector XML resources.
--no-version-transitions
Do not automatically generate versioned copies of transition XML resources.
--private-symbols
Java package name to use when generating R.java for private resources.
```
================================================
FILE: related/am.md
================================================
# am 相关命令
```sh
usage: am [subcommand] [options]
usage: am start [-D] [-W] [-P <FILE>] [--start-profiler <FILE>]
[--sampling INTERVAL] [-R COUNT] [-S] [--opengl-trace]
[--user <USER_ID> | current] <INTENT>
am startservice [--user <USER_ID> | current] <INTENT>
am stopservice [--user <USER_ID> | current] <INTENT>
am force-stop [--user <USER_ID> | all | current] <PACKAGE>
am kill [--user <USER_ID> | all | current] <PACKAGE>
am kill-all
am broadcast [--user <USER_ID> | all | current] <INTENT>
am instrument [-r] [-e <NAME> <VALUE>] [-p <FILE>] [-w]
[--user <USER_ID> | current]
[--no-window-animation] [--abi <ABI>] <COMPONENT>
am profile start [--user <USER_ID> current] [--sampling INTERVAL] <PROCESS> <FILE>
am profile stop [--user <USER_ID> current] [<PROCESS>]
am dumpheap [--user <USER_ID> current] [-n] <PROCESS> <FILE>
am set-debug-app [-w] [--persistent] <PACKAGE>
am clear-debug-app
am set-watch-heap <PROCESS> <MEM-LIMIT>
am clear-watch-heap
am monitor [--gdb <port>]
am hang [--allow-restart]
am restart
am idle-maintenance
am screen-compat [on|off] <PACKAGE>
am package-importance <PACKAGE>
am to-uri [INTENT]
am to-intent-uri [INTENT]
am to-app-uri [INTENT]
am switch-user <USER_ID>
am start-user <USER_ID>
am stop-user [-w] <USER_ID>
am stack start <DISPLAY_ID> <INTENT>
am stack movetask <TASK_ID> <STACK_ID> [true|false]
am stack resize <STACK_ID> <LEFT,TOP,RIGHT,BOTTOM>
am stack split <STACK_ID> <v|h> [INTENT]
am stack list
am stack info <STACK_ID>
am task lock <TASK_ID>
am task lock stop
am task resizeable <TASK_ID> [true|false]
am task resize <TASK_ID> <LEFT,TOP,RIGHT,BOTTOM>
am get-config
am set-inactive [--user <USER_ID>] <PACKAGE> true|false
am get-inactive [--user <USER_ID>] <PACKAGE>
am send-trim-memory [--user <USER_ID>] <PROCESS>
[HIDDEN|RUNNING_MODERATE|BACKGROUND|RUNNING_LOW|MODERATE|RUNNING_CRITICAL|COMPLETE]
am start: start an Activity. Options are:
-D: enable debugging
-W: wait for launch to complete
--start-profiler <FILE>: start profiler and send results to <FILE>
--sampling INTERVAL: use sample profiling with INTERVAL microseconds
between samples (use with --start-profiler)
-P <FILE>: like above, but profiling stops when app goes idle
-R: repeat the activity launch <COUNT> times. Prior to each repeat,
the top activity will be finished.
-S: force stop the target app before starting the activity
--opengl-trace: enable tracing of OpenGL functions
--user <USER_ID> | current: Specify which user to run as; if not
specified then run as the current user.
am startservice: start a Service. Options are:
--user <USER_ID> | current: Specify which user to run as; if not
specified then run as the current user.
am stopservice: stop a Service. Options are:
--user <USER_ID> | current: Specify which user to run as; if not
specified then run as the current user.
am force-stop: force stop everything associated with <PACKAGE>.
--user <USER_ID> | all | current: Specify user to force stop;
all users if not specified.
am kill: Kill all processes associated with <PACKAGE>. Only kills.
processes that are safe to kill -- that is, will not impact the user
experience.
--user <USER_ID> | all | current: Specify user whose processes to kill;
all users if not specified.
am kill-all: Kill all background processes.
am broadcast: send a broadcast Intent. Options are:
--user <USER_ID> | all | current: Specify which user to send to; if not
specified then send to all users.
--receiver-permission <PERMISSION>: Require receiver to hold permission.
am instrument: start an Instrumentation. Typically this target <COMPONENT>
is the form <TEST_PACKAGE>/<RUNNER_CLASS>. Options are:
-r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with
[-e perf true] to generate raw output for performance measurements.
-e <NAME> <VALUE>: set argument <NAME> to <VALUE>. For test runners a
common form is [-e <testrunner_flag> <value>[,<value>...]].
-p <FILE>: write profiling data to <FILE>
-w: wait for instrumentation to finish before returning. Required for
test runners.
--user <USER_ID> | current: Specify user instrumentation runs in;
current user if not specified.
--no-window-animation: turn off window animations while running.
--abi <ABI>: Launch the instrumented process with the selected ABI.
This assumes that the process supports the selected ABI.
am profile: start and stop profiler on a process. The given <PROCESS> argument
may be either a process name or pid. Options are:
--user <USER_ID> | current: When supplying a process name,
specify user of process to profile; uses current user if not specified.
am dumpheap: dump the heap of a process. The given <PROCESS> argument may
be either a process name or pid. Options are:
-n: dump native heap instead of managed heap
--user <USER_ID> | current: When supplying a process name,
specify user of process to dump; uses current user if not specified.
am set-debug-app: set application <PACKAGE> to debug. Options are:
-w: wait for debugger when application starts
--persistent: retain this value
am clear-debug-app: clear the previously set-debug-app.
am set-watch-heap: start monitoring pss size of <PROCESS>, if it is at or
above <HEAP-LIMIT> then a heap dump is collected for the user to report
am clear-watch-heap: clear the previously set-watch-heap.
am bug-report: request bug report generation; will launch UI
when done to select where it should be delivered.
am monitor: start monitoring for crashes or ANRs.
--gdb: start gdbserv on the given port at crash/ANR
am hang: hang the system.
--allow-restart: allow watchdog to perform normal system restart
am restart: restart the user-space system.
am idle-maintenance: perform idle maintenance now.
am screen-compat: control screen compatibility mode of <PACKAGE>.
am package-importance: print current importance of <PACKAGE>.
am to-uri: print the given Intent specification as a URI.
am to-intent-uri: print the given Intent specification as an intent: URI.
am to-app-uri: print the given Intent specification as an android-app: URI.
am switch-user: switch to put USER_ID in the foreground, starting
execution of that user if it is currently stopped.
am start-user: start USER_ID in background if it is currently stopped,
use switch-user if you want to start the user in foreground.
am stop-user: stop execution of USER_ID, not allowing it to run any
code until a later explicit start or switch to it.
-w: wait for stop-user to complete.
am stack start: start a new activity on <DISPLAY_ID> using <INTENT>.
am stack movetask: move <TASK_ID> from its current stack to the top (true) or bottom (false) of <STACK_ID>.
am stack resize: change <STACK_ID> size and position to <LEFT,TOP,RIGHT,BOTTOM>.
am stack split: split <STACK_ID> into 2 stacks <v>ertically or <h>orizontally
starting the new stack with [INTENT] if specified. If [INTENT] isn't
specified and the current stack has more than one task, then the top task
of the current task will be moved to the new stack. Command will also force
all current tasks in both stacks to be resizeable.
am stack list: list all of the activity stacks and their sizes.
am stack info: display the information about activity stack <STACK_ID>.
am task lock: bring <TASK_ID> to the front and don't allow other tasks to run.
am task lock stop: end the current task lock.
am task resizeable: change if <TASK_ID> is resizeable (true) or not (false).
am task resize: makes sure <TASK_ID> is in a stack with the specified bounds.
Forces the task to be resizeable and creates a stack if no existing stack
has the specified bounds.
am get-config: retrieve the configuration and any recent configurations
of the device.
am set-inactive: sets the inactive state of an app.
am get-inactive: returns the inactive state of an app.
am send-trim-memory: Send a memory trim event to a <PROCESS>.
<INTENT> specifications include these flags and arguments:
[-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>]
[-c <CATEGORY> [-c <CATEGORY>] ...]
[-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE> ...]
[--esn <EXTRA_KEY> ...]
[--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> ...]
[--ei <EXTRA_KEY> <EXTRA_INT_VALUE> ...]
[--el <EXTRA_KEY> <EXTRA_LONG_VALUE> ...]
[--ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE> ...]
[--eu <EXTRA_KEY> <EXTRA_URI_VALUE> ...]
[--ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>]
[--eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]]
(mutiple extras passed as Integer[])
[--eial <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]]
(mutiple extras passed as List<Integer>)
[--ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]]
(mutiple extras passed as Long[])
[--elal <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]]
(mutiple extras passed as List<Long>)
[--efa <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE...]]
(mutiple extras passed as Float[])
[--efal <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE...]]
(mutiple extras passed as List<Float>)
[--esa <EXTRA_KEY> <EXTRA_STRING_VALUE>[,<EXTRA_STRING_VALUE...]]
(mutiple extras passed as String[]; to embed a comma into a string,
escape it using "\,")
[--esal <EXTRA_KEY> <EXTRA_STRING_VALUE>[,<EXTRA_STRING_VALUE...]]
(mutiple extras passed as List<String>; to embed a comma into a string,
escape it using "\,")
[--grant-read-uri-permission] [--grant-write-uri-permission]
[--grant-persistable-uri-permission] [--grant-prefix-uri-permission]
[--debug-log-resolution] [--exclude-stopped-packages]
[--include-stopped-packages]
[--activity-brought-to-front] [--activity-clear-top]
[--activity-clear-when-task-reset] [--activity-exclude-from-recents]
[--activity-launched-from-history] [--activity-multiple-task]
[--activity-no-animation] [--activity-no-history]
[--activity-no-user-action] [--activity-previous-is-top]
[--activity-reorder-to-front] [--activity-reset-task-if-needed]
[--activity-single-top] [--activity-clear-task]
[--activity-task-on-home]
[--receiver-registered-only] [--receiver-replace-pending]
[--selector]
[<URI> | <PACKAGE> | <COMPONENT>]
```
================================================
FILE: related/dumpsys.md
================================================
# dumpsys 相关命令
<!-- vim-markdown-toc GFM -->
* [获取当前Activity](#获取当前activity)
* [获取当前Window](#获取当前window)
<!-- vim-markdown-toc -->
### 获取当前Activity
Linux:
```sh
adb shell dumpsys activity | grep "mFocusedActivity"
```
Windows:
```sh
adb shell dumpsys activity | findstr "mFocusedActicity"
```
### 获取当前Window
```sh
adb shell dumpsys window w | grep \/ | grep name=
```
================================================
FILE: related/pm.md
================================================
# pm 相关命令
<!-- vim-markdown-toc GFM -->
* [pm --help](#pm---help)
* [查看手机中APK的存放位置](#查看手机中apk的存放位置)
<!-- vim-markdown-toc -->
## pm --help
```sh
usage: pm list packages [-f] [-d] [-e] [-s] [-3] [-i] [-u] [--user USER_ID] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm list users
pm path PACKAGE
pm dump PACKAGE
pm install [-lrtsfd] [-i PACKAGE] [--user USER_ID] [PATH]
pm install-create [-lrtsfdp] [-i PACKAGE] [-S BYTES]
[--install-location 0/1/2]
[--force-uuid internal|UUID]
pm install-write [-S BYTES] SESSION_ID SPLIT_NAME [PATH]
pm install-commit SESSION_ID
pm install-abandon SESSION_ID
pm uninstall [-k] [--user USER_ID] PACKAGE
pm set-installer PACKAGE INSTALLER
pm move-package PACKAGE [internal|UUID]
pm move-primary-storage [internal|UUID]
pm clear [--user USER_ID] PACKAGE
pm enable [--user USER_ID] PACKAGE_OR_COMPONENT
pm disable [--user USER_ID] PACKAGE_OR_COMPONENT
pm disable-user [--user USER_ID] PACKAGE_OR_COMPONENT
pm disable-until-used [--user USER_ID] PACKAGE_OR_COMPONENT
pm hide [--user USER_ID] PACKAGE_OR_COMPONENT
pm unhide [--user USER_ID] PACKAGE_OR_COMPONENT
pm grant [--user USER_ID] PACKAGE PERMISSION
pm revoke [--user USER_ID] PACKAGE PERMISSION
pm reset-permissions
pm set-app-link [--user USER_ID] PACKAGE {always|ask|never|undefined}
pm get-app-link [--user USER_ID] PACKAGE
pm set-install-location [0/auto] [1/internal] [2/external]
pm get-install-location
pm set-permission-enforced PERMISSION [true|false]
pm trim-caches DESIRED_FREE_SPACE [internal|UUID]
pm create-user [--profileOf USER_ID] [--managed] USER_NAME
pm remove-user USER_ID
pm get-max-users
pm list packages: prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to only show disbled packages.
-e: filter to only show enabled packages.
-s: filter to only show system packages.
-3: filter to only show third party packages.
-i: see the installer for the packages.
-u: also include uninstalled packages.
pm list permission-groups: prints all known permission groups.
pm list permissions: prints all known permissions, optionally only
those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
pm list instrumentation: use to list all test packages; optionally
supply <TARGET-PACKAGE> to list the test packages for a particular
application. Options:
-f: list the .apk file for the test package.
pm list features: prints all features of the system.
pm list users: prints all users on the system.
pm path: print the path to the .apk of the given PACKAGE.
pm dump: print system state associated with the given PACKAGE.
pm install: install a single legacy package
pm install-create: create an install session
-l: forward lock application
-r: replace existing application
-t: allow test packages
-i: specify the installer package name
-s: install application on sdcard
-f: install application on internal flash
-d: allow version code downgrade
-p: partial application install
-g: grant all runtime permissions
-S: size in bytes of entire session
pm install-write: write a package into existing session; path may
be '-' to read from stdin
-S: size in bytes of package, required for stdin
pm install-commit: perform install of fully staged session
pm install-abandon: abandon session
pm set-installer: set installer package name
pm uninstall: removes a package from the system. Options:
-k: keep the data and cache directories around after package removal.
pm clear: deletes all data associated with a package.
pm enable, disable, disable-user, disable-until-used: these commands
change the enabled state of a given package or component (written
as "package/class").
pm grant, revoke: these commands either grant or revoke permissions
to apps. The permissions must be declared as used in the app's
manifest, be runtime permissions (protection level dangerous),
and the app targeting SDK greater than Lollipop MR1.
pm reset-permissions: revert all runtime permissions to their default state.
pm get-install-location: returns the current install location.
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
pm set-install-location: changes the default install location.
NOTE: this is only intended for debugging; using this can cause
applications to break and other undersireable behavior.
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
pm trim-caches: trim cache files to reach the given free space.
pm create-user: create a new user with the given USER_NAME,
printing the new user identifier of the user.
pm remove-user: remove the user with the given USER_IDENTIFIER,
deleting all data associated with that user
```
## 查看手机中APK的存放位置
```sh
adb shell pm list packages -f
```
示例：
```sh
adb shell pm list packages -f | grep vivo
output:
package:/system/app/BBKWeatherProvider/BBKWeatherProvider.apk=com.vivo.weather.provider
package:/system/app/VivoSmartMultiWindow/VivoSmartMultiWindow.apk=com.vivo.smartmultiwindow
package:/system/app/CoffeeTime/CoffeeTime.apk=com.vivo.livewallpaper.coffeetime
package:/system/app/SetupWizard/SetupWizard.apk=com.vivo.setupwizard
...
```
================================================
FILE: related/uiautomator.md
================================================
# uiautomator 相关命令
<!-- vim-markdown-toc GFM -->
* [获取当前页面布局](#获取当前页面布局)
<!-- vim-markdown-toc -->
### 获取当前页面布局
```sh
adb shell uiautomator dump /data/local/tmp/uidump.xml && adb pull /data/local/tmp/uidump.xml uidump.xml
```
gitextract_71oj42wk/
├── .github/
│ └── FUNDING.yml
├── .gitignore
├── LICENSE
├── README.en.md
├── README.md
└── related/
├── aapt.md
├── am.md
├── dumpsys.md
├── pm.md
└── uiautomator.md
Condensed preview — 10 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (200K chars).
[
{
"path": ".github/FUNDING.yml",
"chars": 760,
"preview": "# These are supported funding model platforms\n\ngithub: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [u"
},
{
"path": ".gitignore",
"chars": 16,
"preview": "*.swp\n.DS_Store\n"
},
{
"path": "LICENSE",
"chars": 1076,
"preview": "The MIT License (MIT)\n\nCopyright (c) 2016 Zhuang Ma\n\nPermission is hereby granted, free of charge, to any person obtaini"
},
{
"path": "README.en.md",
"chars": 96858,
"preview": "# \n\nThe [Android Debug Bridge](https://developer.android.com/studio/command-line/adb.h"
},
{
"path": "README.md",
"chars": 67555,
"preview": "# \n\nADB，即 [Android Debug Bridge](https://developer.android.com/studio/command-line/adb"
},
{
"path": "related/aapt.md",
"chars": 9081,
"preview": "# aapt 相关命令\n\n```sh\nAndroid Asset Packaging Tool\n\nUsage:\n aapt l[ist] [-v] [-a] file.{zip,jar,apk}\n List contents of Zi"
},
{
"path": "related/am.md",
"chars": 10828,
"preview": "# am 相关命令\n\n```sh\nusage: am [subcommand] [options]\nusage: am start [-D] [-W] [-P <FILE>] [--start-profiler <FILE>]\n "
},
{
"path": "related/dumpsys.md",
"chars": 379,
"preview": "# dumpsys 相关命令\n\n<!-- vim-markdown-toc GFM -->\n* [获取当前Activity](#获取当前activity)\n* [获取当前Window](#获取当前window)\n<!-- vim-markd"
},
{
"path": "related/pm.md",
"chars": 5939,
"preview": "# pm 相关命令\n\n\n<!-- vim-markdown-toc GFM -->\n\n* [pm --help](#pm---help)\n* [查看手机中APK的存放位置](#查看手机中apk的存放位置)\n\n<!-- vim-markdow"
},
{
"path": "related/uiautomator.md",
"chars": 230,
"preview": "# uiautomator 相关命令\n\n<!-- vim-markdown-toc GFM -->\n* [获取当前页面布局](#获取当前页面布局)\n<!-- vim-markdown-toc -->\n\n\n### 获取当前页面布局\n```sh"
}
]
About this extraction
This page contains the full source code of the mzlogin/awesome-adb GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 10 files (188.2 KB), approximately 51.2k tokens. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.