The following command kills the adb server:

adb kill-server 

This starts the adb server:

adb start-server

If you’re using penaltyLog(), the default, just run

$ adb logcat

and watch the terminal output. Any violations will be logged to your console, slightly rate-limited for duplicate elimination.

If you want to get fancier, turn on penaltyDropbox() and they’ll be written to the DropBoxManager, where you can extract them later with

$ adb shell dumpsys dropbox data_app_strictmode --print

$ adb devices

If multiple devices are attached, use adb -s DEVICE_ID to target a specific device

$ adb uninstall com.package.name

To uninstall the application using uninstall dialog:

$ adb shell am start -a android.intent.action.DELETE -d package:com.package.name

To keep the data in the cache directory, add -k

$ adb uninstall -k com.package.name

$ adb shell am start -n android.intent.action.VIEW -d "scheme://app/deep/linking"

or

$ adb shell am start -n android.intent.action.VIEW -d "https://name.app/user-settings/324" com.packaging.app

This command sends the power button event to turn the device ON/OFF.

$ adb shell input keyevent 26
$ adb shell inout text "KEYCODE_POWER"

This command sends the event that unlocks the lockscreen on the device. It can be combined with the power button command above to turn on and unlock the device

$ adb shell input keyevent 82
$ adb shell inout text "KEYCODE_MENU"

$ adb shell input keyevent 26 82
$ adb shell inout text "KEYCODE_POWER" "KEYCODE_MENU"

$ adb logcat "*:<priority>"
# Where <priority> can be V (Verbose), D (Debug), I (Info), W (Warning), E (Error), F (Fatal), S (Silent).

It can be combined with tagname command, to filter by tagname and priority

$ adb logcat -s TEST: W

$ adb shell setprop log.tag.SQLiteLog V
$ adb shell setprop log.tag.SQLiteStatements V
$ adb shell stop
$ adb shell start

That's it. Whenever any of the installed apps now accesses the database you should see the executed statement in the log output.

The Monkey is a program that runs on your emulator or device and generates pseudo-random streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.

$ adb shell monkey [options] <event-count>
# Basic, make 500 random actions.
$ adb shell monkey -p your.package.name -v 500

ABI (Application Binary Interface) is gonna tell us if an Android device support 64-bit. So using the next command the developer know if the device is 32-bit or 64-bit based.

$ adb shell getprop ro.product.cpu.abi\

# Get a backup of your application data.
$ adb backup --apk com.package.name
# Change the .ab in .tar.
$ dd if=backup.ab bs=24 skip=1 | openssl zlib -d > backup.tar
# Untar  backup.tar.
tar xfv backup.tar
# Go in you app private dir.
$ cd apps/com.package.name

You'll need :

• adb activated
• physical access to unlocked device
• works on Nexus 5 at least, might not work with other devices. allowBackup=false will break thos method

$ cd platform-tools/
# Before executing next command, go to Settings --> Developer Options --> Enable Profile GPU rendering option.
# And make sure to kill your application first or at least to kill the window that you want to profile, and then you run the command:
$ adb shell dumpsys gfxinfo

Purpose of Dumpsys is identifying frame rate issues and fix them.

What matter is the three columns shown. Copy paste results in a spreadsheet. And you will get a result like this one:

This is the data you can grab. You can create a stack graph, so every bar contains the sum of the three columns on the left in the data we output. Is the time it takes to update the display list on every frame.

• The middle column is called process display list. It's the time we take to draw the actual display list
• The last column is the time we take to swap the buffers, so to give the buffer back to surface flinger. Scrolling or doing any kind of actions should be below 16 millisecond limit. So this app is running at 60FPS, we're vsync'd, everything is going great. You can see that most of the time, you should spend most of the time in process display list, so drawing, executing the display list should be where you spend the bulk of the time.
• The blue part is your code. When you write your Java code, your onDraw() method, and this is where you can do most of the optimizations

There is a distinction between the GPU composition with frame buffers and overlays. So you can use a tool called dumpsys surface flinger to see the state of overlays and frame buffers in the system.

$ adb shell dumpsys SurfaceFlinger

You're going to get a list with all the windows currently visible on the screen.

Prerequisites Android device and computer should be connected in same network.

• Connect Android device with USB cable to computer
• Use following command in terminal to make sure adb is running in USB mode.

$ adb usb
# Restarting in USB mode.
# Connect to the device over USB.

• Execute following command in terminal to make sure adb identify/list gets connected with the device.

$ adb devices

• Change adb mode from USB to tcpip using following command.

$ adb tcpip 5555
# Restarting in TCP mode port: 5555.

• Now, adb is running over TCP/IP mode, Let’s find IP address of Android device. Go to Settings in Android device -> About -> Status -> IP address. note down the IP address of connected Android Device.
• Use following command to connect ADB with IP address

$ adb connect #.#.#.#
# Connected to #.#.#.#:5555.

• Now adb is working over Wi-fi, You can remove USB cable from Android device.
• To confirm adb is working over Wi-fi and your device is still connect. you can use following command

$ adb devices
*.*.*.*:5555 device

You’re now ready to go!, Enjoy ADB over Wi-fi. Use following command to change ADB mode to USB

$ adb usb

In order to test permissions targeting API 23+, we could use following commands to programatically grant and revoke permissions on the device:

$adb pm grant <package_name> <permission_name>

or

$adb pm revoke <package_name> <permission_name>