Performance optimization of common ADB commands

Commonly used adb Command summary ( Absolutely dry )

wanderingGuy
0.365
2018.02.10 22:02:54
Number of words 673
read 4,408
This article summarizes the commonly used adb command , Familiarity with these commands can greatly improve development efficiency in some scenarios , Absolutely dry . All parameters in this paper are as follows $ start , In actual use, it can be replaced with real parameters .

One 、 start-up / Close class
start-up activity
Implicit action The way ：

adb shell am start -a ${your_action_name}
Show activity The way ：

adb shell am start -n $you{r}_{p}ackag{e}_{n}ame/${your_activity_name}
Explicit (-n) And implicit (-a) The instructions of are also applicable to services and broadcasting .

Add startup parameters
If you want to add startup parameters, continue to add the following configuration after the above command :

string type : --es ${paramterkey} ${value}
int type : --ei ${paramterkey} ${value}
boolean type : --ez ${paramter_key} ${value}
Multiple parameters are separated by spaces , Other parameter types can be used by themselves google Look up , This method also applies to service And broadcast , Take a chestnut
adb shell am start -a com.xxxx.business.action --es name ‘zhangsan’ --ei age 18
Send a broadcast
adb shell am broadcast -a ${broad_action_name}
Start the service
adb shell am startservice -n $you{r}_{p}ackag{e}_{n}ame/${your_service_name}
// Out of Service
adb shell am stopservice -n $you{r}_{p}ackag{e}_{n}ame/${your_service_name}
Launch the install application dialog
adb shell am start -a android.intent.action.VIEW -d ${your_apk_file_absolute_path} -t application/vnd.android.package-archive
For example, the path is sdcard Then the parameter can be file:///sdcard/test.apk
Force exit process
adb shell am force-stop KaTeX parse error: Expected 'EOF', got '#' at position 368: … So let's just have a script , Quite a powerful . #̲!/bin/sh # Screenshot ls…{ls_date}.png
# from SD The card is exported to the current directory of the machine
adb pull /sdcard/screenshot_${ls_date}.png .
Catch log
This is a routine operation , Basically, I can , My common configuration is as follows
// Threads 、 The process name is a key information when it comes to debugging between multiple applications
adb logcat -v threadtime > log_xxxx.txt
Check the service activity
Needless to say , A line of command prints service It's not much easier for debugging to survive
add |grep Fuzzy query can be supported
adb shell dumpsys activity services |grep ${your_service_name}
Print activity stack situation
With this order , You're worried about transparency activity Well , The printed information already covers all stack And its task And among them activity All status information for . in addition dumpsys The instructions are quite powerful , It can also print cpu、battery Wait for hardware information .
adb shell dumpsys activity activities
With this command and a parameter, the top layer can be printed directly activity name

adb shell dumpsys activity | grep mFocusedActivity
Print window situation
Same as activity similar
adb shell dumpsys window -w
With this command and a parameter, the top layer can be printed directly activity name

adb shell dumpsys activity | grep mFocusedActivity
Clear all application data
adb shell pm clear ${your_package_name}
Print apk Package information
If apk Not installed
aapt dump badging ${your_apk_file_path}
If installed

adb shell dumpsys package ${your_package_name}
Print manifest Content
aapt dump xmltree ${your_apk_file_path} AndroidManifest.xml
Kill the process executing the package name
adb shell am force-stop ${your_package_name}
Print all property information , The information is in system/build.prop In file
adb shell getprop
3、 ... and 、 performance optimization
GPU Presentation mode , An important indicator of frame rate
adb shell setprop debug.hwui.profile visual_bars ( Bar charts )
adb shell setprop debug.hwui.profile visual_lines ( Broken line diagram )
Transition drawing
// After execution, kill the process and restart
adb shell setprop debug.hwui.overdraw show
// Turn off over painting Reopen the interface to take effect
adb shell setprop debug.hwui.overdraw false
Print memory information
adb shell procrank|grep ${your_package_name}
adb shell dumpsys meminfo ${your_package_name}（ More details ）
activty Starting time
adb shell am start -W $you{r}_{p}ackag{e}_{n}ame/${your_activity_name