Summary:
Maps
ADB
Database

Debug KeyStore

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

• 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

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 

Complete information at http://developer.android.com/tools/help/monkey.html

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.

More info about this tool, here

DB Getter (Script) by Ignasi

#!/bin/bash
 
# Android 4.3+ changes app's internal directory permissions and you can not just pull your 
# databases to your computer, so this is a workaround to extract your databases.
# I only use it for debug, use it under YOUR responsability. IT REQUIRES ROOT
 
package=$1
db_name=$2
path="/data/data/$package/"
 
rm $db_name
adb shell "su -c 'cd $path; chmod -R 777 databases; exit'; exit"
adb pull $path/databases/$db_name
open $db_name