Android Tech on control and test

Using Shell Script on Android

2014-05-22T00:04:00.000-07:00

Preface

Shell Script is a good tool to control Android device. You can run the script either by connecting PC or by disconnecting.PC. In order to enter Android's console mode, the ADB is required. Therefore, you can start to use Shell Script on Android. Shell Script is well known on Linux PC to do some scenario control. The kernel of Android is Linux Based. Hence, you can use similar script to control your Android device.

Introduction

Let's learn how to run a Shell Script on Android at first. I'll give an example.
In begging, you need a edit tool for shell script on PC. GEdit is a good choice for you. Note that you need to save your shell script on Linux Format rather than Windows.

Let's get start on writing shell script to run on your Android.
=================================================
#!/bin/sh
#The comments you can write here follows #
#Assign Value 1 to variable named val
val=1
#Assign a String "Hello World" to a variable str1 by export command
export str1="Hello World"
echo "$str1"
#Append a String to its variable by ":"
export str1=$str1:" Hello World again"

#The Screen will show you "Hello World Hello World again"
echo "$str1"

#The Screen will show you "Hello World Hello World again" by infinite loop
while [ true ]
do
echo "$str1"
done
=================================================

Save this file as Linux format and push this file to Android device by following command.
adb push filename /data/local/tmp/
Execute this shell by following command.
adb shell sh /data/local/tmp/filenmae

The output would be as follows,
Hello World
Hello World: Hello World again
Hello World: Hello World again
Hello World: Hello World again
...

Note
It's unnecessary to have root permission to run the shell script if you place files in the folder of /data/local/tmp/ and don't use the none permitted command.

Keyword: Shell Script, Android

在Android做LTP (Linux Test Project)測試

2014-05-06T18:31:00.001-07:00

在Android做LTP (Linux Test Project)測試

序:

LTP是一個測試Linux核心的開源(Open Source)測試套件, 一開始由SGI發起, 由 IBM, Cisco, Fujitsu, SUSE, Red Hat 等公司開發與維護. 目前能持續的進版中. LTP針對Linux系統做可靠度, 強健度, 與穩定度做系統測試, 內涵許多的Test Case可供測試. 測試Linux伺服器時, 也可以採用這樣的測試套件來為你購買的硬體設備做燒機(Burn/Run in)測試.

Android的底層核心是Linux系統, 可透過Android ADB的連線進到大家熟悉的Linux Console環境. LTP套件基本上的設計是基於PC的系統架構與權限條件. 但Android的架構與X86是不一樣的, 因此要把LTP佈署在Android的裝置上, 必須採用可在X86環境上編譯Android架構可用的編譯器(Compiler), 稱作跨平台編譯器(Cross Compiler). 由於LTP的源碼(Source Code)的架構與參數設定, 是給X86架構使用的, 因此在編譯前, 還必須做些參數上的調整.當中有相當多的觀念可以學習.

介紹:

環境建置: 在開始編譯一個合適你的Android系統測試用的LTP前, 環境建置是必須的. 以下分別介紹要安裝那些套件.

1. 安裝Ubuntu64 bit在你的電腦上, 我是用12版.
2. 到 sourcery.mentor.com 下載Cross Compiler. 也可以用新版的Cross Compiler.
3. 於Ubuntu上安裝以下套件.

sudo apt-get install git-core flex bison gperf libesd0-dev libwxgtk2.6-dev zlib1g-dev build-essential libstdc++5 tofrodos
sudo apt-get install x-dev
sudo apt-get install libx11-dev
sudo apt-get install libncurses5-dev
sudo apt-get install libreadline-dev
sudo apt-get install g++-multilib (build kernel用)
Ubuntu 64bit
apt-get install ia32-libs ia32-libs-gtk
sudo dpkg-reconfigure dash  Selection 'NO‘
./arm-2012.09-64-arm-none-linux-gnueabi.bin

3. 於sourceforge.net下載LTP原始碼

http://sourceforge.net/projects/ltp/?source=dlp

4. 編譯環境設定.

設定Cross Compiler的路徑到環境變數中. 以下路徑需要修改為你放置與安裝Cross Compiler的正確資料夾. 注意這些環境設定是適用於ARM平台.

export PATH=$PATH:/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/

export CC=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-gcc

export LD=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ld

export AR=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ar

export LIB_DIR=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/lib

export AS=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-as

export RANLIB=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ranlib

export STRIP=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-strip

編譯與安裝LTP
1. 設定你的LTP.
./configure AR=arm-none-linux-gnueabi-ar CC=arm-none-linux-gnueabi-gcc RANLIB=arm-none-linux-gnueabi-ranlib STRIP=arm-none-linux-gnueabi-strip --host=arm-linux --target=arm-linux CFLAGS="-static" LDFLAGS="-static -pthread“

2. 為了要讓LTP能順利在ARM平台下的Linux執行, 需要做一些參數上的調整. 這邊參考了網路一些零碎的資料, 實做了, 是可行的. 以下以20120104的LTP版本為例. 實驗過2013版本也是可行的.

在 ltp-full-20120104/testcases/kernel/controllers/libcontrollers/libcontrollers.h 裡增加 LINE_MAX 的 define, 這邊是設定為 255.
將 ltp-full-20120104/testcases/kernel/fs/fs-bench 裡 random-access.c, random-del-create.c & random-access-del-create.c 這三個檔案裡的 openlog[] 陣列名稱修改成其他的名稱, 避免衝突.
在 ltp-full-20120104/testcases/kernel/sched/sched_stress/sched_driver.c 和 ltp-full-20120104/testcases/kernel/fs/ftest/libftest.c 這兩個檔案裡, 增加 PATH_MAX 的 define 值, 這裡是設定成 1024.
在 ltp-full-20120104/testcases/kernel/sched/cfs-scheduler/hackbench.c 裡加上 PTHREAD_STACK_MIN 的 define, 這兒是設成 1024.
make
make install prefix=/[Install Folder]

3. 開始編譯與安裝在指定的資料夾. 這會需要一段很長的時間, 視電腦速度而異. 編譯出來約1GByte的大小. 若只有100M上下的檔案大小, 就是沒有編譯成功.

make
make install prefix=/[Install Folder]

佈署LTP到你的Android裝置

1. 下載Busybox, 並且推到你的Android中. 因為Android裝置內的Linux指令已經精簡過了, 因此少了很多Shell Command. 你需要補強幾個LTP會用到的Linux Shell Command.
adb push busybox /data/local/tmp
2. 把編譯出的LTP整個資料夾推送到Android裝置內的/data/local/tmp/資料夾.
3. 讓你的Busybox內的command可以實體化. 以下只舉幾個例子, 最好可以把busybox內的所有command都做一次以下動作.

busybox ln -f busybox readlink
busybox ln -f busybox basename
busybox ln -f busybox mktemp
busybox ln -f busybox dirname
busybox ln -f busybox grep
busybox ln -f busybox sed
busybox ln -f busybox awk
busybox ln -f busybox head
busybox ln -f busybox free
busybox ln -f busybox uname

4. 於Android ADB命令列下設定執行LTP環境. 例如我編譯出的LTP都推到Android內的 /data/local/tmp/LTP13/資料夾內.

export PATH=/data/local/tmp/busyboxdir:$PATH
export PATH=/data/local/tmp/LTP13:$PATH
export PATH=/data/local/tmp/LTP13/testcases/bin:$PATH
export PATH=/data/local/tmp/LTP13/runtest:$PATH

開始執行LTP
sh ./runltp -p -l 130326report1ipc.log -o 130326output1ipc.log -d /data/local/tmp/LTP13/tmp -f ipc

後記

由於LTP的Source Code中有些程式碼不符合Android的一些限制, 需要做修改後方可正常執行. 若有興趣的人, 在留言板上留言, 我們再來討論吧.

至於LTP的Soruce Code是用甚麼語言寫的, 主要分為兩種, 一種是C語言, 另外一種是Shell Script配合Shell Command執行.

參考資料:

Internet Q&A

關鍵字: LTP, Android, Linux Test Project, Stress Test, Android Reliability, Automation Test. 分享到Line

Linux Test Project (LTP) on Android

2014-05-06T18:07:00.000-07:00

Perform LTP on Android

Preface

LTP WiKi said, "The Linux Test Project is a joint project started by SGI, developed and maintained by IBM, Cisco, Fujitsu, SUSE, Red Hat and others, that has a goal to deliver test suites to the open source community that validate the reliability, robustness, and stability of Linux. The LTP testsuite contains a collection of tools for testing the Linux kernel and related features."

The kernel layer of Android is based on Linux. User can connect to Linux Console by Android ADB. Download the LTP from official website, it can run on Linux PC. However, it can not run on ARM platform such as Android because of its original design on X86. Therefore, if you would like to use LTP on Android, the Cross Compiler is required.

Introduction

Configuration Environment
1. Prepare a PC and install Ubuntu64 bit on it. (version 12 is applicable.)
2. Download the Cross Compiler from sourcery.mentor.com. (Newer version is applicable.)
3. Install following program on Ubuntu

sudo apt-get install git-core flex bison gperf libesd0-dev libwxgtk2.6-dev zlib1g-dev build-essential libstdc++5 tofrodos
sudo apt-get install x-dev
sudo apt-get install libx11-dev
sudo apt-get install libncurses5-dev
sudo apt-get install libreadline-dev
sudo apt-get install g++-multilib (For build kernel)
Ubuntu 64bit
apt-get install ia32-libs ia32-libs-gtk
sudo dpkg-reconfigure dash  Selection 'NO‘
./arm-2012.09-64-arm-none-linux-gnueabi.bin

3. Download LTP source code from sourceforge.net

http://sourceforge.net/projects/ltp/?source=dlp

4. Environment settings for Cross Compiler

You need to modify the file path for your own. Note that settings here is for ARM platform.

export PATH=$PATH:/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/

export CC=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-gcc

export LD=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ld

export AR=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ar

export LIB_DIR=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/lib

export AS=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-as

export RANLIB=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-ranlib

export STRIP=/home/carl/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-strip

Compile and install LTP
1. Configuration
./configure AR=arm-none-linux-gnueabi-ar CC=arm-none-linux-gnueabi-gcc RANLIB=arm-none-linux-gnueabi-ranlib STRIP=arm-none-linux-gnueabi-strip --host=arm-linux --target=arm-linux CFLAGS="-static" LDFLAGS="-static -pthread“

2. Some values of parameter should be changed for ARM platform. Here I illustrate what should be changed by the version in 2012. (The version of 2013 is applicable)

Find and edit the file ltp-full-20120104/testcases/kernel/controllers/libcontrollers/libcontrollers.h and add one line for LINE_MAX and define its value as 255.
Change the varialbe name of array in random-access.c, random-del-create.c and random-access-del-create.c which files are located at ltp-full-20120104/testcases/kernel/fs/fs-bench/
Find and edit the files named ltp-full-20120104/testcases/kernel/sched/sched_stress/sched_driver.c and ltp-full-20120104/testcases/kernel/fs/ftest/libftest.c and add one line for PATH_MAX and define its value as1024.
Find and edit the file ltp-full-20120104/testcases/kernel/sched/cfs-scheduler/hackbench.c and add one line for PTHREAD_STACK_MIN and define its value as 1024.
make
make install prefix=/[Install Folder]

3. After the install, there are some files in your Install Folder and the total file size is about 1GByte. It takes long time to perform compiling work.

Deploy LTP into your Android device

1. Download Busybox and push it to your Android in order to have necessary shell command on Android. adb push busybox /data/local/tmp
2. Push all the installed LTP folder (Install Folder) to Android. I always push the files to /data/local/tmp.
3. Ln all the command from busybox. Following examples only shows you some pieces, you need to ln all the commands that busybox have.

busybox ln -f busybox readlink
busybox ln -f busybox basename
busybox ln -f busybox mktemp
busybox ln -f busybox dirname
busybox ln -f busybox grep
busybox ln -f busybox sed
busybox ln -f busybox awk
busybox ln -f busybox head
busybox ln -f busybox free
busybox ln -f busybox uname

4. Setting the LTP variable environment in Adroid. You need to change the path to where your file located in Android.

export PATH=/data/local/tmp/busyboxdir:$PATH
export PATH=/data/local/tmp/LTP13:$PATH
export PATH=/data/local/tmp/LTP13/testcases/bin:$PATH
export PATH=/data/local/tmp/LTP13/runtest:$PATH

Run LTP on Android
sh ./runltp -p -l 130326report1ipc.log -o 130326output1ipc.log -d /data/local/tmp/LTP13/tmp -f ipc

Reference

Internet Q&A

Keyword: LTP, Android, Linux Test Project, Stress Test, Android Reliability, Automation Test. Share to Line

Android Power State Information Acquired

2013-01-02T00:39:00.000-08:00

Introduction

Android Power state can be found by using console/ADB command - adb shell dumpsys power, then the message would be printed as follows,

Power Manager State:

mIsPowered=true mPowerState=3 mScreenOffTime=958909 ms

mPartialCount=1

mWakeLockState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT

mUserState=

mPowerState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT

mLocks.gather=SCREEN_BRIGHT_BIT SCREEN_ON_BIT

mNextTimeout=66689 now=1022321 -955s from now

mDimScreen=true mStayOnConditions=3 mPreparingForScreenOn=false mSkippedScreenOn=false

mScreenOffReason=2 mUserState=0

mBroadcastQueue={-1,-1,-1}

mBroadcastWhy={0,0,0}

mPokey=0 mPokeAwakeonSet=false

mKeyboardVisible=false mUserActivityAllowed=false

mKeylightDelay=6000 mDimDelay=47000 mScreenOffDelay=7000

mPreventScreenOn=false mScreenBrightnessOverride=-1 mButtonBrightnessOverride=-1

mScreenOffTimeoutSetting=60000 mMaximumScreenOffTimeout=2147483647

mLastScreenOnTime=1019715

mBroadcastWakeLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)

mStayOnWhilePluggedInScreenDimLock=UnsynchronizedWakeLock(mFlags=0x6 mCount=0 mHeld=true)

mStayOnWhilePluggedInPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=true)

mPreventScreenOnPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)

mProximityPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)

mProximityWakeLockCount=0

mProximitySensorEnabled=false

mProximitySensorActive=false

mProximityPendingValue=-1

mLastProximityEventTime=0

mLightSensorEnabled=false mLightSensorAdjustSetting=0.0

mLightSensorValue=-1.0 mLightSensorPendingValue=-1.0

mHighestLightSensorValue=-1 mWaitingForFirstLightSensor=false

mLightSensorPendingDecrease=false mLightSensorPendingIncrease=false

mLightSensorScreenBrightness=-1 mLightSensorButtonBrightness=-1 mLightSensorKeyboardBrightness=-1

mUseSoftwareAutoBrightness=true

mAutoBrightessEnabled=false

mScreenBrightnessAnimator:

animating: start:0, end:102, duration:960, current:102

startSensorValue:-1 endSensorValue:-1

startTimeMillis:1019791 now:1022324

currentMask:SCREEN_BRIGHT_BIT

mLocks.size=3:

SCREEN_DIM_WAKE_LOCK 'StayOnWhilePluggedIn Screen Dim' activated (minState=1, uid=1000, pid=622)

PARTIAL_WAKE_LOCK 'StayOnWhilePluggedIn Partial' activated (minState=0, uid=1000, pid=622)

FULL_WAKE_LOCK 'keyguard'ACQUIRE_CAUSES_WAKEUP activated (minState=3, uid=1000, pid=622)

mPokeLocks.size=0:

The power state is listed by parameter mPowerState which has the flag value as follows,

// flags for setPowerState
private static final int ALL_LIGHTS_OFF = 0x00000000;
private static final int SCREEN_ON_BIT = 0x00000001;
private static final int SCREEN_BRIGHT_BIT = 0x00000002;
private static final int BUTTON_BRIGHT_BIT = 0x00000004;
private static final int KEYBOARD_BRIGHT_BIT = 0x00000008;
private static final int BATTERY_LOW_BIT = 0x00000010;

If device is on suspend mode, it would print 0 for mPowerState parameter.

When device is on screen on mode, the value 3 is shown for parameter mPowerState because of following reason.

// SCREEN_BRIGHT == screen on, screen backlight bright
private static final int SCREEN_BRIGHT = SCREEN_ON_BIT | SCREEN_BRIGHT_BIT;

where SCREEN_ON_BIT and SCREEN_BRIGHT_BIT are performed or operation.

References

https://android.googlesource.com/platform/frameworks/base/+/android-4.1.2_r1/services/java/com/android/server/PowerManagerService.java

Extending monkeyrunner with Plugins - Jar File

2012-11-19T00:53:00.001-08:00

Preface
As you can see the description on Android Developer Site, you can extend MonkeyRunner by writing java programming language and integrate to an Jar file and create more capacities for your control purpose. In following section, using 21 steps to guide you how to create a monkeyrunner extension JAR file.

How to create a Jar component for MonkeyRunner?

Before we start to know how to create a Jar Component for MonkeyRunner, there're something you need to do in advance. The J2SDK installation on your computer is required and you need to know how to program Java based program. Eclipse is an option, however it's very useful. Android SDK installation is required.

Here I'll show you an example by using Eclipse to create a Jar component for MonkeyRunner Extension.

1. Using Eclipse to create a Java Project through File->New->Java Project. Fill the project name.
2. Press Next button.

3. Tap Libraries.

4. Tap "Add External JARs..." button.

5. Add Jar files - Pick chimpchat.jar, guavalib.jar, jython.jar, and monkeyrunner.jar in the folder - /android_sdk_folder/tools/lib/.
6. Press Finish button.

7. Fill the package name - com.android.monkeyrunner.
8. Fill the class name.
9. Press Finish button.

10. If you need to initial some variable for monkeyrunner runtime environment, you can implement a interface named Predicate and write the initial thing in apply method.
11. In this example, I create three static methods for interacting with Android device. They're tap, PressButton, and saveScreenToFile respectively. These functions are to trigger a touch event, and a button event, and to save run-time screen to a file. In order to implement these function to communicate with Android device, we need to import MonkyDevice and MonkeyImage classes. The usage is similar with what you wrote on monkeyrunner console to control Android devices. The difference is that you need to use Python Object class for given parameters. For instance, to invoke a touch event, you can use touch method in MonkeyDevice class. But you need to give a value which is belong to the type of PyObject. Hence, we declare a PyObject variable and assign two integer and one string as their values that is needed by declared PyObject variable. For given parameters, the two integer values are used to assign where to touch and the string value is used to assign which action we're going to use for touch event (E.g. DOWN, UP, or DOWN_AND_UP). Note that, you can not use int as integer's type in PyObject's initialization. To assign an integer value to PyObject class, the type of PyInteger Object is needed. To assign a string value to PyObject class, the type of PyString Object is needed.

12. The Eclipse is very useful for developing MonkeyRunner Extension Jar file, because you can see the tip when your mouse move cursor to the method. Hence, you can know what type and you should use and how many parameters you should provide for particular method.

13. Start to export your wrote files to a Jar file for MonkeyRunner after you finish the coding work.
14. Move mouse to project name on Eclipse and right click the mouse.
15. Click Export option.

16. Select JAR file and press Next button.

17. Select the files which are going to be exported and press Next button.

18. Press Next Button.

19. If you don't have a MANIFEST file existed already, you can select option of "Generate the manifest file" and press Browser button to select where to store the MANIFEST file. You can give a name like MANIFEST.MF and place in root folder of project. If you have a MANIFEST file already, you can select option - Use existing manifest from workspace and select your own file.
20. Press Finish button.

21. Edit the MANIFEST file you used at last step and add a command - MonkeyRunnerStartupRunner: com.android.monkeyrunner.monkeyrunnerExt to MANIFEST file. The string of MonkeyRunnerStartupRunner: is followed by full package name of your class. Finally, save your modified MANIFEST file to your JAR file.

How to import your own Jar file for MonkeyRunner?

Copy your Jar file to /android-sdk_folder/tools/lib before running monkeyrunner.bat. Double click monkeyrunner.bat at the folder of android-sdk/tools/ to bring up a MonkeyRunner console as follows. And import the necessary class and your own class as follows. Then you can use your own class to do something on MonkeyRunner run-time environment.

Reference
http://developer.android.com/tools/help/monkeyrunner_concepts.html#Plugins

Build an Android SDK

2012-11-08T23:49:00.001-08:00

Preface

To build a customized Android SDK is a option to develop your SDK tools. In following section will talk about how to build a Android SDK. Before you read this paragraph, you need to know how to build a Android Build Environment in advance.

Description

Android SDK is very easy to build up. After you finish both the Android Build Environment setup and a particular version of Android Source Code downloaded, you can do it by following command.

1. Go to root folder of Android Source Code.
2. Execute Console Command to build a Linix Android SDK -

$ . build/envsetup.sh
$ lunch sdk-eng
$ make sdk

The Android SDK on Linux is started to build. Note that in case you want to build a Windows Android SDK, to perform the above actions in advance. Or the build process of Windows Android SDK would fail because of lack of something it needs from Linux Android SDK.

3. In case you want to build a Windows Android SDK, perform the following commands.

$ sudo apt-get install mingw32 tofrodos

$ . build/envsetup.sh
$ lunch sdk-eng
$ make win_sdk

The build process will finish after a long time. It depends on the performance of your build machine. You will see the following screen once the build process is successfully.

Reference
http://tools.android.com/build

Android Build Environment Setup

2012-11-07T20:31:00.002-08:00

Preface

Following Instructions will lead you to know how to build a Android build Environment.

Setup Your Ubuntu

In case you'd like to have both of Windows and Ubuntu can work on a computer concurrently, you can install Oracle VM VirtualBox in your Computer/Notebook and then install Ubuntu on VirtualBox. You can follow the instruction below to setup your Android Build Environment. If you want to install Ubutun on a computer only, you can ignore installation of VirtualBox.

1. Download Oracle VirtualBox from https://www.virtualbox.org/.
2. Download Ubuntu 10.04 LTE from http://releases.ubuntu.com/lucid/ and choose the file named ubuntu-10.04.4-desktop-amd64.iso.
3. Install VirtualBox and Create a Virtual Ubuntu System on VirtualBox.
4. Install Ubuntu on VirtualBox.

Configure Your Ubuntu

1. Launch a terminal on Ubuntu.
2. Follow the instructions that Google said at http://source.android.com/source/initializing.html to install the required tools.

Detailed instructions for Ubuntu and MacOS follow. In general you will need:

Python 2.5 -- 2.7, which you can download from python.org.
GNU Make 3.81 -- 3.82, which you can download from gnu.org,
JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from java.sun.com.
Git 1.7 or newer. You can find it at git-scm.com.

Install the following tools by executing console command below.

sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc

Because Canonical is no longer to support Oracle Java, you need to install the Oracle JDK6 manually. It means you cannot use apt-get tool to install Oracle JDK6. Follow the instruct at following section - Installation Instruction of Oracle J2SDK 6 on Ubuntu 10.04 64 bit to install the Oracle J2SDK6.

3. Download and install repo tool from Google - http://source.android.com/source/downloading.html.

Make sure you have a bin/ directory in your home directory, and that it is included in your path:

$ mkdir ~/bin
$ PATH=~/bin:$PATH
Download the Repo script and ensure it is executable:

$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

4. Initializing a Repo client

After installing Repo, set up your client to access the android source repository:

Create an empty directory to hold your working files. If you're using MacOS, this has to be on a case-sensitive filesystem. Give it any name you like:

$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY

Run repo init to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest, which specifies where the various repositories included in the Android source will be placed within your working directory.

$ repo init -u https://android.googlesource.com/platform/manifest
To check out a branch other than "master", specify it with -b:

$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r1

Note that the parameter -b is followed by Android version. The Android version can be assigned to the latest version or previous version that Google released.

When prompted, please configure Repo with your real name and email address. To use the Gerrit code-review tool, you will need an email address that is connected with a registered Google account. Make sure this is a live address at which you can receive messages. The name that you provide here will show up in attributions for your code submissions.

A successful initialization will end with a message stating that Repo is initialized in your working directory. Your client directory should now contain a .repo directory where files such as the manifest will be kept.

5. Get the source code by repo
$ repo sync

6. After several hours, you may receive 6 to 8 GByte file in your storage.

Installation Instruction of Oracle J2SDK 6 on Ubuntu 10.04 64 bit

1. Download binary file from http://www.oracle.com/technetwork/java/javase/downloads/jdk6u37-downloads-1859587.html and click jdk-6u37-linux-x64.bin to download

2. Root permission is required to install J2SDK.
3. Copy the file jdk-6u37-linux-x64.bin to /usr/lib/jvm folder.
# cp /Download_Folder_Path/jdk-6u37-linux-x64.bin /usr/lib/jvm/jdk-6u37-linux-x64.bin
# cd usr/lib/jvm/
# sh jdk-6u37-linux-x64.bin

4. After folder jdk1.6.0_37 is extracted, install it by using update-alternatives as follows,

update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_37/bin/java 1000
update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_37/bin/javac 1000
update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_37/bin/javaws 1000
update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk1.6.0_37/bin/jar 1000

The command of update-alternatives is a tool which can select particular tool version to be run on Linux. To view the manual by executing console command - "man update-alternatives" on Ubuntu.

5. Choose the option of Oracle Java by following command in case your Ubuntu has installed other Java VM (E.g. OpenJava).

#update-alternatives --config java

6. Check the Java version you used on your Ubuntu by following command.
# java -version
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

Reference:

http://source.android.com/source/initializing.html

http://source.android.com/source/downloading.html

http://tools.android.com/build

https://www.virtualbox.org/

http://yltechblog.blogspot.tw/2012/10/install-jdk6-on-ubuntu-1204.html

Dumpsys Information - Android Open Source

2012-10-24T02:14:00.002-07:00

Preface

Dumpsys is a tool to gather various information from Android device and tell you its system status. All you have to do is to execute a command - "adb shell dumpsys" on your computer with J2SDK and Android SDK. Let's take a look on it.

Description

After executing the command of "adb shell dumpsys", there're various service messages are outputted as follows. (In this case, I used an Android device to depict how to get the information and what they stand for.)

Currently running services:
accessibility
account
activity
alarm
apn_settings_policy
application_policy
appwidget
audio
backup
battery
batteryinfo
bluetooth
bluetooth_a2dp
bluetooth_avrcp
bluetooth_policy
browser_policy
clipboard
clipboardEx
connectivity
content
country_detector
cpuinfo
CustomFrequencyManagerService
date_time_policy
device_info
device_policy
devicestoragemonitor
DirEncryptService
diskstats
drm.drmManager
dropbox
eas_account_policy
email_account_policy
enterprise_policy
enterprise_vpn_policy
entropy
firewall_policy
FMPlayer
gfxinfo
hardware
input_method
iphonesubinfo
isms
location
location_policy
mdm.remotedesktop
media.audio_flinger
media.audio_policy
media.camera
media.player
media.yamahaplayer
meminfo
mini_mode_app_manager
misc_policy
motion_recognition
mount
netpolicy
netstats
network_management
notification
package
password_policy
permission
phone
phone_restriction_policy
phoneext
power
remoteinjection
restriction_policy
roaming_policy
samplingprofiler
search
SecTVOutService
security_policy
sensorservice
shutdownlogger
simphonebook
statusbar
SurfaceFlinger
telephony.registry
textservices
throttle
tvoutservice
TvoutService_C
uimode
usagestats
usb
vibrator
voip
vpn_policy
wallpaper
wifi
wifi_policy
wifip2p
window

In above list, we see that there're various functional services are running on Android device. When debug engineering is necessary, we could get a lot of useful information from dumpsys for debugging purpose.

We've discussed the MonkeyRunner Control with Jython script in separate article. We can check the testing result by comparing image. However, we always hope to acquire more clues to point out the root cause of problem.

Typically, I illustrate two situations. First one is when the problem is caused by up layer (Framework layer or UI representation), but it's work normally at lower layer ( E.g. driver). For instance, when trying to switch Bluetooth On, you may observe the icon on UI which remains Off state. But the driver of Bluetooth has been powered on. In another situation we can think about is oppositive to last case

Now we have another choice to make result more accurately. Fortunately, we can monitor both system status by using parameter inspection from outputted information of dumpsys on Android device and UI comparison by using MonkeyRunner manner as the necessary testing criteria.

Usage

dumpsys [running_service_name]

In case nothing is followed by dumpsys, the dumpsys will output all the information of running services.

What information can be found in Dumpsys ?

Dumpsys outputs various message to depict system status of an Android device. Let's talk about some frequent used messages.

When you need power relative information, you can get them by following information.

Battery Information from Dumpsys

Execute the command of "adb shell dumpsys battery", you may see the following information.

Current Battery Service state:

AC powered: false

USB powered: true

status: 2

health: 2

present: true

level: 100

scale: 100

voltage:4191

temperature: 350

technology: Li-ion

From above information, you can get the information, including type of power source, battery capacity, measured battery voltage, measured temperature and so on.

The definitions of each parameter from battery information are as follows,

AC powered:false (Power source)

USB powered:true (Power source)

status:5 (see next section)

health:2 (see next section)

present:true (indicating whether a battery is present.)

level:100 (returns battery level as a percentage)

scale:100 (maximum battery level)

voltage: 4195 (an integer containing the current battery voltage level)

temperature: 380 (an integer containing the current battery temperature)

technology: Li-ion (technology of the current battery)

With respect to status in battery information, the definition of value is as follows,

Defined in android.os.BatteryManager

BATTERY_STATUS_UNKNOWN (0x00000001)

BATTERY_STATUS_CHARGING (0x00000002)

BATTERY_STATUS_DISCHARGING (0x00000003)

BATTERY_STATUS_NOT_CHARGING (0x00000004)

BATTERY_STATUS_FULL (0x00000005)

With respect to health in battery information, the definition of value is as follows,

Defined in android.os.BatteryManager

BATTERY_HEALTH_UNKNOWN (0x00000001)

BATTERY_HEALTH_GOOD (0x00000002)

BATTERY_HEALTH_OVERHEAT (0x00000003)

BATTERY_HEALTH_DEAD (0x00000004)

BATTERY_HEALTH_OVER_VOLTAGE (0x00000005)

BATTERY_HEALTH_UNSPECIFIED_FAILURE(0x00000006)

BATTERY_HEALTH_COLD (0x00000007)

When you need to get the information from Bluetooth you can use following information.

Bluetooth Information from Dumpsys

Execute the command of "adb shell dumpsys bluetooth", you may see the following information.

DUMP OF SERVICE bluetooth:

mIsAirplaneSensitive = true

mIsAirplaneToggleable = true

Local address = 00:07:0B:16:23:AC

Local name = MyBTPhone

isDiscovering() = false

The definitions of Bluetooth information for each parameter are as follows,

Parameter	Value	Definition
mIsAirplaneSensitive	true \| false	Airplane mode can prevent Bluetooth radio from being turned on
mIsAirplaneToggleable	true \| false	Airplane mode can prevent Bluetooth radio from being turned on
Local name		Bluetooth device name
Local address		Bluetooth Address
isDiscovering	true\|false	Discoverable for Bluetooth

The following information will tell you what the status for telecom is.

telephony.registry Information from Dumpsys

Execute the command of "adb shell dumpsys telephony.registry", you may see the following information.

DUMP OF SERVICE telephony.registry:
last known state:
mCallState=0
mCallIncomingNumber=
mServiceState=0 home TTT TTT 46999 HSDPA:9 CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false
mSignalStrength=SignalStrength: 19 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 gsm|lte 4
mMessageWaiting=false
mCallForwarding=false
mDataActivity=0
mDataConnectionState=0
mDataConnectionPossible=true
mDataConnectionReason=dataDisabled
mDataConnectionApn=
mDataConnectionLinkProperties=null
mDataConnectionLinkCapabilities=null
mCellLocation=Bundle[mParcelledData.dataSize=76]
registrations: count=8

Note, the information telephony.registry provided is the last know state. It means it may not the state that device is running.

The definitions of telephony.registry information for each parameter are as follows,

Parameter	Definition/Value
mCallState	Call State 0 - CALL_STATE_IDLE(No activity.) 1 - CALL_STATE_RINGING 2 - CALL_STATE_OFFHOOK
mCallIncomingNumber	Last incoming call number
mServiceState	Radio service State 0 - STATE_IN_SERVICE(Normal operation condition, the phone is registered with an operator either in home network or in roaming. ) 1 - STATE_OUT_OF_SERVICE (Phone is not registered with any operator, the phone can be currently searching a new operator to register to, or not searching to registration at all, or registration is denied, or radio signal is not available. ) 2 - STATE_EMERGENCY_ONLY (The phone is registered and locked. Only emergency numbers are allowed. ) 3 - STATE_POWER_OFF(Radio of telephony is explicitly powered off.)
SignalStrength	Radio Signal Strength (RSSI)
mMessageWaiting	Radio Message Waiting true \| false
mCallForwarding	Radio Call Forwarding true \| false
mDataActivity	0 - Radio Data Call Activity: DATA_ACTIVITY_NONE(No traffic.) 1- DATA_ACTIVITY_IN(Currently receiving IP PPP traffic.) 2 - DATA_ACTIVITY_OUT(Currently sending IP PPP traffic.) 3 - DATA_ACTIVITY_INOUT(Currently both sending and receiving IP
mDataConnectionState	Radio Data Connection State 0 - DATA_DISCONNECTED (Disconnected. IP traffic not available. ) 1- DATA_CONNECTING(Currently setting up a data connection.) 2 - DATA_CONNECTED (Connected. IP traffic should be available.) 3 - DATA_SUSPENDED (Suspended. The connection is up, but IP traffic is temporarily unavailable. For example, in a 2G network, data activity may be suspended when a voice call arrives.)
mActiveDataConnectionState	Radio Data Connection State 0 - DATA_DISCONNECTED (Disconnected. IP traffic not available. ) 1- DATA_CONNECTING(Currently setting up a data connection.) 2 - DATA_CONNECTED (Connected. IP traffic should be available.) 3 - DATA_SUSPENDED (Suspended. The connection is up, but IP traffic is temporarily unavailable. For example, in a 2G network, data activity may be suspended when a voice call arrives.)
mDataConnectionPossible	Active Radio Data Connection true \| false
mDataConnectionReason	Reason for data Connection
mDataConnectionApn	APN Name
mDataConnectionInterfaceName	Name of data connection interface
mCellLocation	Information of Cell Location
registrations: count	Recording count of registration

When you want to know the status of WiFi, you can refer to following information.

WiFi Information from Dumpsys

Execute the command of "adb shell dumpsys wifi", you may see the following information.

DUMP OF SERVICE wifi:
Wi-Fi is enabled
Stay-awake conditions: 0
Internal state:
current HSM state: ConnectedState
mLinkProperties InterfaceName: wlan0 LinkAddresses: [1.1.2.3/24 ] Routes: [0.0.0.0/0 -> 1.1.2.6,] DnsAddresses: [1.1.2.1,] HttpProxy: [ProxyProperties.mHost == null]
mWifiInfo SSID: Google, BSSID: 00:08:0a:02:03:08, MAC: 00:00:00:00:00:80, Supplicant state: COMPLETED, RSSI: -63, Link speed: 13, Net ID: 1, Explicit connect: true
mDhcpInfoInternal addr: 1.1.2.3/24 mRoutes: 0.0.0.0/0 -> 1.1.2.6 | dns: 1.1.2.6, dhcpServer: 1.1.2.6 leaseDuration: 7200
mNetworkInfo NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason:(unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
mLastSignalLevel 3
mLastBssid 00:00:00:00:00:00
mLastNetworkId 1
mReconnectCount 0
mIsScanMode false
Supplicant status
bssid=00:00:00:00:00:00
ssid=Google
id=1
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=1.1.2.3
address=00:00:00:00:00:00

The definitions of wifi information for each parameter are as follows,

Parameter	Value	Definition
Wi-Fi is	disabled\|connected enabled\|disconnected	Wi-Fi Radio State
Stay-awake conditions		Stay-awake conditions value
Internal state		Internal state
interface		Netowrk Interface
runState		Run State
SSID		Wi-Fi AP's SSID
BSSID		BSSID of Wi-Fi AP
MAC		MAC Address for Wi-Fi
Supplicant state		Supplicant state for Wi-Fi
RSSI		RSSI for Wi-Fi
Link speed		Link speed for Wi-Fi
Net ID		Net ID for Wi-Fi
ipaddr		Obtained IP Address for Wi-Fi
gateway		Gateway for Wi-Fi
netmask		Netmask for Wi-Fi
dns1		Primary DNS for WiFi
dns2		Secondary DNS for WiFi
DHCP server		DHCP address for WiFi
scanModeActive	true \| false	Scan Mode Active for Wi-Fi
haveIpAddress	true \| false	Have IP Address for Wi-Fi
obtainingIpAddress	true \| false	Obtaining Ip Address for Wi-Fi
lastSignalLevel		Last Signal Level for Wi-Fi
explicitlyDisabled		Explicitly Disabled for Wi-Fi

There're more information you can get from dumpsys for your purpose. Aforementioned has provided you a good start on how to get them. Now, it's your turn.

When you want to know what network interface you are using, you can look at following information.

Connectivity Information from Dumpsys

Execute the command of "adb shell dumpsys connectivity", you may see the following information.

DUMP OF SERVICE connectivity:
NetworkInfo: type: mobile[UMTS], state: DISCONNECTED/DISCONNECTED, reason: dataDisabled, extra: vivi, roaming: false, failover: false, isAvailable: true
Mobile data state: DISCONNECTED
Data enabled: user=true, policy=true

Active network: WIFI
NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
android.net.wifi.WifiStateTracker@00000000
...

The definitions of connectivity information for each parameter are as follows,

Parameter	Value	Definition
Active network	WiFi \| UMTS	Check if Active Network is transmitted by WiFi or UMTS
NetworkInfo: type: mobile		NetworkInfo: type for mobile: HSDPA\|UMTS
state	UNKNOW / IDEL	Radio State
	CONNECTED\|CONNECTED
	DISCONNECTED\|DISCONNECTED
Extra		NetworkInfo: Carrier Name
roaming	true \| false	Roaming state
failover	true \| false
isAvailable	true \| false	Check if Mobile network is available

How Jython and MonkeyRunner use these information to do automated testings ?

Using shell command in MonkeyRunner and executing dumpsys service_name, you can get the particular information from it and parse/filter those information by Jython Script. Hence, you can use these information for your testing or control purpose.

Reference

Dumpsys, http://source.android.com/tech/input/dumpsys.html

A guide to Activity, Service, and Content Provider Testing by JUnit

2012-10-23T00:17:00.000-07:00

Android Develop Team has well introduction on Activity Test by JUnit. Here is the link leads you to explore the testing skill.

http://developer.android.com/tools/testing/activity_test.html

For Service Testing by JUnit, take a look WEB sit - http://developer.android.com/tools/testing/service_testing.html.

For Content provider testing by JUnit, take a look WEB sit - http://developer.android.com/tools/testing/contentprovider_testing.html.

The limitation for this method to do test is that you need to have the source code of Activity you want to test. And you need to compile test case with source code of Activity.

One of strength of using JUnit to test Activity is you can control the particular UI component such as a button, or a textarea. Another good standpoint is that you can use JUnit to manage your test case and test result. There's another testing tool to test Android Framework called CTS. The CTS uses JUnit for its testing framework as well. With respect to CTS, take a look following WEB Site for more information. http://source.android.com/compatibility/cts-development.html

Android / Linux Shell Command List

2012-10-18T20:35:00.002-07:00

Preface

We've discussed about the Android / Linux Command in separate article. Here, we want to talk about what we can use and where to find the useful commands in Android device. Connect your Android device and launch a command line window in advance. Then you can try to use all these commands by executing command adb shell command_name.

The following commands can be found in the folder "/system/bin/ on Nexus 7.

Commands	Desc.
adb	Android Debug Bridge
am	Activity Manager
app_process	Execute a runtime environment for a dalvik class/Jar file.
applypatch	Apply patches to android files. usage: applypatch [: ...] or applypatch -c [ ...] or applypatch -s or applypatch -l Filenames may be of the form MTD::::::... to specify reading from or writing to an MTD partition.
atrace	Trace information captured in the folder of /sys/kernel/debug/tracing/ usage: atrace [options]. Measure the system performance and do the analysis. Systrace tool provides more parameters to measure the performance than atrace. options include: -b N use a trace buffer size of N KB -c trace into a circular buffer -d trace disk I/O -f trace CPU frequency changes -l trace CPU frequency governor load -s trace the kernel scheduler switches -t N trace for N seconds [defualt 5] -w trace the kernel workqueue -z compress the trace dump
bluetoothd	Bluetooth Debuging Utility Usage: bluetoothd [OPTION...] Help Options: -?, --help Show help options Application Options: -d, --debug=DEBUG Specify debug options to enable -p, --plugin=NAME,.., Specify plugins to load -P, --noplugin=NAME,... Specify plugins not to load -n, --nodetach Don't run as daemon in background -v, --version Show version information and exit -u, --udev Run from udev mode of operation
bmgr	bmgr is a shell tool you can use to interact with the Backup Manager on Android devices. usage: bmgr [backup\|restore\|list\|transport\|run] bmgr backup PACKAGE bmgr enable BOOL bmgr enabled bmgr list transports bmgr list sets bmgr transport WHICH bmgr restore TOKEN bmgr restore TOKEN PACKAGE... bmgr restore PACKAGE bmgr run bmgr wipe PACKAGE
bootanimation	Show the boot animation.
brcm_patchram_plus	This program downloads a patchram files in the HCD format to Broadcom Bluetooth based silicon and combo chips and and other utility functions. It can be invoked from the command line in the form <-d> to print a debug log <--patchram patchram_file="patchram_file"> <--baudrate baud_rate="baud_rate"> <--bd_addr bd_address="bd_address"> <--enable_lpm> <--enable_hci> uart_device_name
btmacreader	Bluetooth MAC Reader.
bu	Backup Options: -apk, Save APK -noapk, Save no APK -shared, Save Shared -noshared, Save no Shared -system, All Includes System -nosystem, Not all Includes System -all, Everything
bugmailer.sh	Send Bug Report to Vendor.
bugreport	Export all the debug message from Android and Linux layer.
cat -> toolbox	Concatenate, a tool to print out the content of a file continually. It's the same usage with Linux.
chmod -> toolbox	Change the mode of file. Usage is the same with Linux.
chown -> toolbox	Change the owner of a file/folder. Usage is the same with Linux.
cmp -> toolbox	Compare the file. Usage is the same with Linux.
content	Perform operations on particular content usage: adb shell content [subcommand] [options] usage: adb shell content insert --uri --bind [--bind ...] a content provider URI. binds a typed value to a column and is formatted: :: where: specifies data type such as: b - boolean, s - string, i - integer, l - long, f - float, d - double Note: Omit the value for passing an empty string, e.g column:s: Example: # Add "new_setting" secure setting with value "new_value". adb shell content insert --uri content://settings/secure --bind name:s:new_setting --bind value:s:new_value usage: adb shell content update --uri [--where ] is a SQL style where clause in quotes (You have to escape single quotes - see example below). Example: # Change "new_setting" secure setting to "newer_value". adb shell content update --uri content://settings/secure --bind value:s:newer_value --where "name='new_setting'" usage: adb shell content delete --uri --bind [--bind ...] [--where ] Example: # Remove "new_setting" secure setting. adb shell content delete --uri content://settings/secure --where "name='new_setting'" usage: adb shell content query --uri [--projection ] [--where ] [--sort ] is a list of colon separated column names and is formatted: [:...] is the order in which rows in the result should be sorted. Example: # Select "name" and "value" columns from secure settings where "name" is equal to "new_setting" and sort the result by name in ascending order. adb shell content query --uri content://settings/secure --projection name:value --where "name='new_setting'" --sort "name ASC"
dalvikvm	Launch the Dalvik VM to run a Java class in DEX format. dalvikvm: [options] class [argument ...] dalvikvm: [options] -jar file.jar [argument ...] The following standard options are recognized: -classpath classpath -Dproperty=value -verbose:tag ('gc', 'jni', or 'class') -ea[:... \|:] -da[:... \|:] (-enableassertions, -disableassertions) -esa -dsa (-enablesystemassertions, -disablesystemassertions) -showversion -help The following extended options are recognized: -Xrunjdwp: -Xbootclasspath:bootclasspath -Xcheck:tag (e.g. 'jni') -XmsN (min heap, must be multiple of 1K, >= 1MB) -XmxN (max heap, must be multiple of 1K, >= 2MB) -XssN (stack size, >= 1KB, <= 256KB) -Xverify:{none,remote,all} -Xrs -Xint (extended to accept ':portable', ':fast' and ':jit') These are unique to Dalvik: -Xzygote -Xdexopt:{none,verified,all,full} -Xnoquithandler -Xjnigreflimit:N (must be multiple of 100, >= 200) -Xjniopts:{warnonly,forcecopy} -Xjnitrace:substring (eg NativeClass or nativeMethod) -Xstacktracefile: -Xgc:[no]precise -Xgc:[no]preverify -Xgc:[no]postverify -Xgc:[no]concurrent -Xgc:[no]verifycardtable -XX:+DisableExplicitGC -X[no]genregmap -Xverifyopt:[no]checkmon -Xcheckdexsum -Xincludeselectedop -Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]* -Xincludeselectedmethod -Xjitthreshold:decimalvalue -Xjitblocking -Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace) -Xjitcheckcg -Xjitverbose -Xjitprofile -Xjitdisableopt -Xjitsuspendpoll Configured with: debugger profiler hprof jit(armv7-a) show_exception=1 Dalvik VM init failed (check log file)
date -> toolbox	Set date value. date -s yyyymmdd, set date on Android
dd -> toolbox	Copy, Convert, and Format a file. Usage: dd [options] bs=BYTES [block size] cbs=BYTES [conversion record size] conv=KEYWORDS [conv option disabled] count=BLOCKS [block count] ibs=BYTES [input block size] if=FILE [read file] obs=BYTES [output block size] of=FILE [write file] seek=BLOCKS [seek blocks] skip=BLOCKS [skip blocks] Ex: dd if=/data/local/tmp/1gb bs=64k \| dd of=/sdcard/1gb
df -> toolbox	List free space on disk
dmesg -> toolbox	Output linux debug message
dumpstate	Dump system status usage: dumpstate [-b soundfile] [-e soundfile] [-o file [-d] [-p] [-z]] [-s] -o: write to file (instead of stdout) -d: append date to filename (requires -o) -z: gzip output (requires -o) -p: capture screenshot to filename.png (requires -o) -s: write output to control socket (for init) -b: play sound file instead of vibrate, at beginning of job -e: play sound file instead of vibrate, at end of job
dumpsys	Dump functional state dumpsys [options] Execute dumpsys will output all the message in case there's no option specified. option: accessibility account activity alarm appwidget audio backup battery batteryinfo bluetooth bluetooth_a2dp clipboard commontime_management connectivity content country_detector cpuinfo dbinfo device_policy devicestoragemonitor diskstats drm.drmManager dropbox entropy gfxinfo hardware input input_method iphonesubinfo isms location lock_settings media.audio_flinger media.audio_policy media.camera media.player meminfo mount netpolicy netstats network_management nfc notification package permission phone power samplingprofiler scheduling_policy search sensorservice serial servicediscovery simphonebook sip statusbar SurfaceFlinger telephony.registry textservices throttle uimode updatelock usagestats usb vibrator wallpaper wifi wifip2p window
getevent -> toolbox	The getevent tool runs on the device and provides information about input devices and a live dump of kernel input events. Usage: getevent [-t] [-n] [-s switchmask] [-S] [-v [mask]] [-d] [-p] [-i] [-l] [-q] [-c count] [-r] [device] -t: show time stamps -n: don't print newlines -s: print switch states for given bits -S: print all switch states -v: verbosity mask (errs=1, dev=2, name=4, info=8, vers=16, pos. events=32, props=64) -d: show HID descriptor, if available -p: show possible events (errs, dev, name, pos. events) -i: show all device info and possible events -l: label event types and names in plain text -q: quiet (clear verbosity mask) -c: print given number of events then exit -r: print rate events are received http://source.android.com/tech/input/getevent.html
getprop -> toolbox	List some property of Android
hd -> toolbox	To sum up each character in specified file and result the summation. To do hd command repeatedly and to set delay interval between each execution if -r is designated. Usage: hd [-b base] [-c count] [-r delay] file
id -> toolbox	Print uid, gid, and context
ifconfig -> toolbox	TCP/IP command. Assign an address to a network interface and/or configure network interface parameters. ifconfig is typically used at boot time to define the network address of each interface on a machine.
iftop -> toolbox	Show the packet flow for each network interface Usage: iftop [ -r repeats] [ -d delay ]
input	Send string or key event to device usage: input [text\|keyevent] input text input keyevent
insmod -> toolbox	Load a module into the kernel at runtime. The module cannot be used after reboot. Usage: insmod
ioctl -> toolbox	IO Control Command between Up and lower layer. ioctl [-l ] [-a ] [-rdh] -l Length of io buffer -a Size of each argument (1-8) -r Open device in read only mode -d Direct argument (no iobuffer) -h Print help
ionice -> toolbox	Configure the Process. Usage: ionice [none\|rt\|be\|idle] [prio]
kill -> toolbox	Kill the process usage: kill [-s signame \| -signum \| -signame] { job \| pid \| pgrp } kill -l [exit_status ...]
ln -> toolbox	Create pseudonyms (links) for files, allowing them to be accessed by different names. ln [-s]
log -> toolbox	Display specified log information. USAGE: log [-p priorityChar] [-t tag] message priorityChar should be one of: v,d,i,w,e
logcat	Real time Log for all application running on Android System. options include: -s Set default filter to silent. Like specifying filterspec ':s' -f Log to file. Default to stdout -r [] Rotate log every kbytes. (16 if unspecified). Requires -f -n Sets max number of rotated logs to , default 4 -v Sets the log print format, where is one of: brief process tag thread raw time threadtime long -c clear (flush) the entire log and exit -d dump the log and then exit (don't block) -t print only the most recent lines (implies -d) -g get the size of the log's ring buffer and exit -b Request alternate ring buffer, 'main', 'system', 'radio' or 'events'. Multiple -b parameters are allowed and the results are interleaved. The default is -b main -b system. -B output the log in binary filterspecs are a series of [:priority] where is a log component tag (or for all) and priority is: V Verbose D Debug I Info W Warn E Error F Fatal S Silent (supress all output) '' means ':d' and by itself means :v If not specified on the commandline, filterspec is set from ANDROID_LOG_TAGS. If no filterspec is found, filter defaults to '*:I' If not specified with -v, format is set from ANDROID_PRINTF_LOG or defaults to "brief"
ls -> toolbox	List the file and directory at current or specified path. Usage: ls -l: LIST_LONG; break; -n:LIST_LONG \| LIST_LONG_NUMERIC; break; -s: LIST_SIZE; break; -R:LIST_RECURSIVE; break; -d: LIST_DIRECTORIES; break; -Z: LIST_MACLABEL; break; -a: LIST_ALL; break; -F: LIST_CLASSIFY; break;
lsmod -> toolbox	List the module in Android device.
lsof -> toolbox	List information in /Proc folder which contains all the process information.
md5 -> toolbox	MD5 encription tool
mkdir -> toolbox	Create a folder.
monkey	A automation stress test tool which generates random event for Android device.
mount -> toolbox	Mount a file structure. Usage: mount [-r] [-w] [-o options] [-t type] device directory
mv -> toolbox	Remove a file. USAGE: mv
nandread -> toolbox	nandread [-d ] [-f file] [-s sparesize] [-vh] -d Read from -f Write to -s Number of spare bytes in file (default 64) -R Raw mode -S Start offset (default 0) -L Length (default 0) -v Print info -h Print help
netcfg	Configure network interface usage: netcfg [ {dhcp\|up\|down}]
netstat -> toolbox	Print net state
newfs_msdos -> toolbox	New a file System with specified format usage: newfs_msdos [ -options ] special [disktype] where the options are: -@ create file system at specified offset -B get bootstrap from file -C create image file with specified size -F FAT type (12, 16, or 32) -I volume ID -L volume label -N don't create file system: just print out parameters -O OEM string -S bytes/sector -a sectors/FAT -b block size -c sectors/cluster -e root directory entries -f standard format -h drive heads -i file system info sector -k backup boot sector -m media descriptor -n number of FATs -o hidden sectors -r reserved sectors -s file system size (sectors) -u sectors/track
ping	Check if the specified host address is online.
pm	Package Manager for running Dalvik Class file.
printenv -> toolbox	Print Environment Variables and their Values for Android Device
ps -> toolbox	Print the running process with its state. Usage: ps [options] -t Show threads -x Show time -Z Show MAC Label -P Show Policy -p Show Priority -c Show CPU
reboot -> toolbox	Reboot Android Device
renice -> toolbox	Change the priority of a process. USAGE: renice [[-r] priority pids ...] [-g pid]
rm -> toolbox	Remove a file or folder. Usage: rm file_name or rm -r folder_name
rmdir -> toolbox	Remove the folder. Usage: rmdir
rmmod -> toolbox	Remove a module usage: rmmod
route -> toolbox	Add or Remove route Ex: route add -net 192.168.1.2 netmask 255.255.255.0 gw 192.168.1.1
screencap	Output Android screen usage: screencap [-hp] [FILENAME] -h: this message -p: save the file as a png. If FILENAME ends with .png it will be saved as a png. If FILENAME is not given, the results will be printed to stdout.
screenshot	Output Android screen usage: screenshot [-s soundfile] filename.png -s: play a sound effect to signal success -i: autoincrement to avoid overwriting filename.png
sendevent -> toolbox	Send a event trigger to specified device with type, code, and value. E.g. Touch, or Key. Usage: sendevent [device] [type] [code] [value].
service	Service operation Usage: service [-h\|-?] service list service check SERVICE service call SERVICE CODE [i32 INT \| s16 STR] ... Options: i32: Write the integer INT into the send parcel. s16: Write the UTF-16 string STR into the send parcel.
setconsole -> toolbox	setconsole [-d ] [-v ] [-gtncpoh] -d Use instead of /dev/tty0 -v Switch to virtual console -g Switch to graphics mode -t Switch to text mode -n Create and switch to new virtual console -c Close unused virtual consoles -p Print new virtual console -o Print old virtual console -h Print help
setprop -> toolbox	Set the Android property. Usage: setprop
sh -> mksh	Execute a shell script.
sleep -> toolbox	Interval of next action/command (seconds)
start -> toolbox	Start a specified service
stop -> toolbox	Stop a specified service
sync -> toolbox	Copy host->device only if changed. adb sync is a tool which may be used to copy files from the computer to the device if the files has been changed. By default the command will synchronize /data and /system unless one option is specified. For the command to operate properly a system variable must be created and defined. ANDROID_PRODUCT_OUT must designate the full actual path to the directory containing a file structure with system and/or data subfolders containing the files and folders changed. Usage: sync [ ]
toolbox	Check if the specified command existed. Usage: toolbox command_name
top -> toolbox	Display usage of thread or process. Usage: top [ -m max_procs ] [ -n iterations ] [ -d delay ] [ -s sort_column ] [ -t ] [ -h ] -m num Maximum number of processes to display. -n num Updates to show before exiting. -d num Seconds to wait between updates. -s col Column to sort by (cpu,vss,rss,thr). -t Show threads instead of processes. -h Display this help screen.
umount -> toolbox	Unmount the device Usage: umount device_path
uptime -> toolbox	The up time since last boot. The information includes up, idle, and sleep time.
vmstat -> toolbox	Virtual Meomory Statistics Usage: vmstat [ -h ] [ -n iterations ] [ -d delay ] [ -r header_repeat ] -n iterations How many rows of data to print. -d delay How long to sleep between rows. -r header_repeat How many rows to print before repeating the header. Zero means never repeat. -h Displays this help screen.
vold	Manage the device on Android. The function is similar with udev in Linux.
watchprops -> toolbox	Monitor the change of property and list them. The properties can be viewed by executing getprop and set by executing setprop.
wipe -> toolbox	Erase the system or data Usage: wipe system means '/system' data means '/data'
wpa_supplicant	Configure WLAN usage: wpa_supplicant [-BddhKLqqstuvW] [-P] [-g] \ -i -c [-C] [-D] [-p] \ [-b] [-f] [-e] \ [-o] [-O] \ [-N -i -c [-C] [-D] \ [-p] [-b] ...] drivers: nl80211 = Linux nl80211/cfg80211 options: -b = optional bridge interface name -B = run daemon in the background -c = Configuration file -C = ctrl_interface parameter (only used if -c is not) -i = interface name -d = increase debugging verbosity (-dd even more) -D = driver name (can be multiple drivers: nl80211,wext) -e = entropy file -g = global ctrl_interface -K = include keys (passwords, etc.) in debug output -t = include timestamp in debug messages -h = show this help text -L = show license (GPL and BSD) -o = override driver parameter for new interfaces -O = override ctrl_interface parameter for new interfaces -p = driver parameters -P = PID file -q = decrease debugging verbosity (-qq even less) -v = show version -W = wait for a control interface monitor before starting -N = start describing new interface example: wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

基於開放原始碼精神，Carl決定來這分享由開放原始碼所成就的Android技術。

知道再多的技術不如要知道如何善加利用他。才能物盡其利，事半功倍。大部分的企業開發產品都想要Pull in Schedule and Cost Down。

一個非常複雜尖端科技與技術所完成的產品，並不一定受到市場的歡迎。而要看見與創造市場願意接受的需求，才能創造新的社群。

Android測試工程
Android 自動化操作與測試 - monkeyrunner
Android MonkeyRunner 和 Jythan - 從一個簡單的範例開始
Android Automation Test for Stability by Monkey 中文版

Android控制工程

Android Activity Manager - shell command am中文版
Android 與 Linux 的執行命令

Android訊息紀錄
Android Log 訊息 - Bugreport

另類相關
Upgrade your Nexus 7 to 4.1.2 Manually

Android MonkeyRunner 和 Jythan - 從一個簡單的範例開始

2012-10-17T20:54:00.001-07:00

English Version
序

MonkeyRunner是由Google Android開發團隊所提出的控制Android的工具，放置於Android SDK。
MonkeyRunner 是由一組控制命令並使用Jython的語法來做控制程序的撰寫。Jython是由Java虛擬機器來執行，有別於Python是用C/C++來做執行。利用Jython來作邏輯控制將會更有彈性的控制Android裝置。

在閱讀本篇文章前，你需要對MonkeyRunner的設定環境先行了解。若尚不知怎麼作，可以先閱讀此篇文章 http://android-test-tw.blogspot.com/2012/10/android-automation-test-by-monkeyrunner.html。

Jython簡介

在開始介紹如何用Jython來撰寫MonkeyRunner的Script前，我們先來介紹基本的Jython語法。

Jython可使用的變數類別有數字、字串和串列。使用變數不需要宣告，主要是依據指定的值的型態來確認變數的類別。

接下來先來看幾個簡單的範例方便快速了解Jython的使用。你可以複製以下範例到一個文字檔。例如example.py。打開一個cmd的視窗並執行命令 - monkeyrunner.bat example.py 再按下確定(Enter)按鈕。

設定數字給變數
num = 1
設定字串給變數
str = "Hello"
str = 'Hello2'
設定一個串列給變數
list = ['mail','inbox',100,200]

以下來簡單探討邏輯判斷與迴圈控制

使用if的方式如下所示
if_stmt ::= "if" expression ":" suite
( "elif" expression ":" suite )*
["else" ":" suite]

範例:
if num < 0:
num = 0
   print('Negative changed to zero')
  elif num == 0:
   print('Zero')
  elif num == 1:
   print('Single')
  else:
   print('More')

使用while的方式如下所示
while_stmt ::= "while" expression ":" suite
["else" ":" suite]

範例:
num = 100
go = True

while go:
getNum = int(raw_input('Input a number : '))
if getNum == num:
print 'That is right.'
go = False
else:
print 'Oh No~'
else:
print 'Game over.'
print 'Done'

使用for的方式如下所示
for_stmt ::= "for" target_list "in" expression_list ":" suite

["else" ":" suite]

範例:
for i in range(9):
print(i)
else:
print 'done'

一個簡單的加入Jython控制的MonkeyRunner範例介紹:

這個範例中，我們想要驗證執行中的畫面與我們事先設定好的畫面是否一致，以做為測試判斷的結果。在這個範例中，我們會利用Jython增加邏輯敘述到MonkeyRunner。Jython的語法基本上和Python大致相同。因此可以參考Python的語法來做為新添加的元素。

在以下的範例我們會判斷藍牙的開啟狀況，利用使用者介面來做測試結果的判斷。反覆的開關藍芽的電源。當中會需要一個API是官網未提出的。但經實驗證實可以使用。該API為MonkeyRunner.loadImageFromFile(Full_File_Path)。

首先必須先取得預設希望得到的預期測試結果的圖像，可利用以下的Script來取得。以下為片段程式碼。使用前還是需要先預載MonkeyRunner相關的類別與設定變數。

result = device1.takeSnapshot()
result.getSubImage ((133,85,85,28))
result.writeToFile('./capture1.png','PNG')

執行前請先把Android裝置的畫面選到設定，並開啟藍芽電源。這個範例使用Android JB模擬器，螢幕解析度為240X432的大小。執行上述Script後會得到以下的圖檔。

capture1.png

完整範例：
from com.android.monkeyrunner import MonkeyRunner, MonkeyDevice, MonkeyImage
#Import class of MonkeyRunner, MonkeyDevice, and MonkeyImage.
device1 = MonkeyRunner.waitForConnection(10000,"emulator-5554")
print 'connected'
#Connect Android device from computer and assign handler to variable -device1.
monkeyimage1 = MonkeyRunner.loadImageFromFile('./capture1.png')
print 'capture1.png loaded'
#Load a existing image file by load image API and assign handler to variable - monkeyimage1;
device1.press('KEYCODE_HOME','DOWN_AND_UP',' ')
print 'home key are triggered'
#Send home key event to bring up Launcher
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
device1.press('KEYCODE_MENU','DOWN_AND_UP',' ')
#Send menu key event
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
device1.touch ( 95, 417, "DOWN_AND_UP")
#Touch system settings in menu list
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
for i in range(1000):
device1.touch ( 197, 96, "DOWN_AND_UP")
#Touch bluetooth On
MonkeyRunner.sleep(2);
monkeyimage2 = device1.takeSnapshot()
#Take a screenshot on Android device and assign handler to variable monkeyimage2
monkeyimage2 = monkeyimage2.getSubImage ((133,85,85,28))
#Get specified rectangle from screenshot got by last step for the result we want to check and assign handler to variable monkeyimage2 again.
if monkeyimage2.sameAs ( monkeyimage1, 1 ):
print str(i+1)+':pass'
else:
print str(i+1)+':fail'
#Compare the result if both images of pre-loaded and run-time screenshot are the same.
device1.touch ( 155, 95, "DOWN_AND_UP")
#Touch bluetooth Off
else:
print 'done'

測試結果若都通過，命令列視窗會顯示第幾次測試，結果為何。

參考資料:

Python Script Language Tutorial, http://docs.python.org/tutorial/
Jython Script Lanuage Tutorial, http://www.jython.org/docs/index.html
MonkeyRunner, http://developer.android.com/tools/help/monkeyrunner_concepts.html
Android KeyCode, http://developer.android.com/reference/android/view/KeyEvent.html

Android 與 Linux 的執行命令

2012-10-17T19:58:00.001-07:00

序:

Android的系統架構在Linux上，是一個Java基礎的作業系統。如同以下的圖示，Google提出的架構可了解。

http://source.android.com/tech/security/#android-platform-security-architecture

Android的工作區域是在上方圖的淡藍色(Applications&Application Framework)與深綠色(Android Runtime) 的部分。Java所設計的程式必須利用深綠色的Android Runtime裡的Dalvik虛擬機器來執行，若需要與Linux這層做溝通，由Android Runtime這部份來做國境遷移(Native Code)的技術來做訊息交遞。Linux的工作區域是位於上方架構圖的淡綠色 (Libraries) 與粉紅色 (Linux Kernel)。

這樣的架構可以用在Android系統做參考，但實際的產品會因產品功能不同而有不同的架構物件的增減或是修改。

介紹

Android提供一個工具，稱作ADB. ADB的全名是Android Debug Bridge，就是Android除錯橋樑。在Android的裝置內有ADB的伺服端，以供放置於電腦上的ADB用戶端連線。

Android與Linux中有很多好用的執行命令工具可以用來控制Android系統與取得Android系統訊息。使用這些控制命令有個簡單的方法就是透過ADB來執行。

探索Android JB版本的模擬器裡的資料夾，於/system/bin的資料夾就可找到不少可用的執行命令。可使用adb shell "ls /system/bin"去觀察有多少命令在這個資料夾。

Android系統架構於Linux上，Android本身提供一些一些控制命令。在Linux端，其命令有許多是來自於原來的Linux Kernel。但或多或少為了配合嵌入式的裝置，還是有微幅修改。大多的原生Linux命令用法是相當類似的。因此可以先查詢Android系統中的Linux提供多少命令，對照Linux系統的使用方法，就可以獲得許多的資訊。

範例
am - Activity Manager, Java 語言設計的執行命令，可控制Android的四大元件，原始碼可參考 platform_frameworks_base/blob/master/cmds/am/src/com/android/commands/am/Am.java

monkey - 穩定性的工具，工具執行會不斷發出隨機事件，Java 語言設計的執行命令，原始碼可參考 platform_development/blob/master/cmds/monkey/src/com/android/commands/monkey/Monkey.java

pm - Package Manager 可以對Package做相關的操作，Java 設計的執行命令，原始碼可參考 platform_frameworks_base/blob/master/cmds/pm/src/com/android/commands/pm/Pm.java

dmesg - Linux Debug Message, 輸出Linux相關的訊息，C語言設計的執行命令,，與原生的Linux系統有相同的用法。原始碼可參考 platform_system_core/blob/master/toolbox/dmesg.c

ps - Process State, 輸出程序的id與記憶體使用情形等，C語言設計的執行命令，與原生的Linux系統有相同的用法。原始碼可參考 android/platform_system_core/blob/master/toolbox/ps.c

以上的範例我們可以看到Android系統的控制命令主要有分為Java語言與C語言生成的控制程式。但基於Linux的強大功能，還能執行例如Python與Perl等語言。

Reference
Android Architecture, http://source.android.com/tech/security/
Android Source Code Mirror Site, https://github.com/android/
Package Manager, http://developer.android.com/reference/android/content/pm/PackageManager.html

Android Log 訊息 - Bugreport

2012-10-17T18:59:00.002-07:00

序

當一個人生病去看醫生，會說出症狀，醫生或做一些檢測來確認引起不良反應的原因。對於一個Android的裝置也一樣。在開發過程中，工程開發人員常會發現一些問題。這時候需要檢測裝置的發生原因。因此可以透過Android的內部紀錄訊息來檢測發生甚麼問題導致不良因素。

從何處下手?

Android 內有提供一個指令，稱為bugreport。可以透過指令adb bugreport adb shell bugreport來取得Bugreport中的資訊。使用這個指令取得Android 4.1的模擬器內的bugreport可得到以下的六十八種紀錄訊息。這些訊息可以用來診斷Android目前的健康情況。

UPTIME (uptime)

MEMORY INFO (/proc/meminfo)

CPU INFO (top -n 1 -d 1 -m 30 -t)

PROCRANK (procrank)

VIRTUAL MEMORY STATS (/proc/vmstat)

VMALLOC INFO (/proc/vmallocinfo)

SLAB INFO (/proc/slabinfo)

ZONEINFO (/proc/zoneinfo)

PAGETYPEINFO (/proc/pagetypeinfo)

BUDDYINFO (/proc/buddyinfo)

KERNEL WAKELOCKS (/proc/wakelocks)

KERNEL CPUFREQ (/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)

PROCESSES (ps -P)

PROCESSES AND THREADS (ps -t -p -P)

LIBRANK (librank)

KERNEL LOG (dmesg)

LIST OF OPEN FILES (/system/xbin/su root lsof)

SMAPS OF ALL PROCESSES

SHOW MAP 1 (/init) (/system/xbin/su root showmap 1)

BLOCKED PROCESS WAIT-CHANNELS

SYSTEM LOG (logcat -v threadtime -d *:v)

EVENT LOG (logcat -b events -v threadtime -d *:v)

RADIO LOG (logcat -b radio -v threadtime -d *:v)

VM TRACES JUST NOW (/data/anr/traces.txt.bugreport: 2012-10-17 08:21:46)

VM TRACES AT LAST ANR (/data/anr/traces.txt: 2012-10-17 08:16:11)

NETWORK DEV INFO (/proc/net/dev)

QTAGUID NETWORK INTERFACES INFO (/proc/net/xt_qtaguid/iface_stat_all)

QTAGUID NETWORK INTERFACES INFO (xt) (/proc/net/xt_qtaguid/iface_stat_fmt)

QTAGUID CTRL INFO (/proc/net/xt_qtaguid/ctrl)

QTAGUID STATS INFO (/proc/net/xt_qtaguid/stats)

NETWORK ROUTES (/proc/net/route)

NETWORK ROUTES IPV6 (/proc/net/ipv6_route)

LAST KMSG (/proc/last_kmsg)

LAST PANIC CONSOLE (/data/dontpanic/apanic_console)

LAST PANIC THREADS (/data/dontpanic/apanic_threads)

SYSTEM SETTINGS (/system/xbin/su root sqlite3 /data/…

NETWORK INTERFACES (/system/xbin/su root netcfg)

IP RULES (ip rule show)

IP RULES v6 (ip -6 rule show)

ROUTE TABLE 60 (ip route show table 60)

ROUTE TABLE 61 v6 (ip -6 route show table 60)

ROUTE TABLE 61 (ip route show table 61)

ROUTE TABLE 61 v6 (ip -6 route show table 61)

ARP CACHE (/proc/net/arp)

IPTABLES (/system/xbin/su root iptables -L -nvx)

IP6TABLES (/system/xbin/su root ip6tables -L -nvx)

IPTABLE NAT (/system/xbin/su root iptables -t nat -L -nvx)

IPTABLE RAW (/system/xbin/su root iptables -t raw -L -nvx)

IP6TABLE RAW (/system/xbin/su root ip6tables -t raw -L -nvx)

WIFI NETWORKS (/system/xbin/su root wpa_cli list_networks)

SYSTEM PROPERTIES

VOLD DUMP (vdc dump)

SECURE CONTAINERS (vdc asec list)

FILESYSTEMS & FREE SPACE (/system/xbin/su root df)

PACKAGE SETTINGS (/system/xbin/su root cat /data/system/packages.xml)

PACKAGE UID ERRORS (/data/system/uiderrors.txt: 2012-10-15 02:30:29)

LAST RADIO LOG (parse_radio_log /proc/last_radio_log)

BACKLIGHTS

BINDER FAILED TRANSACTION LOG (/sys/kernel/debug/binder/failed_transaction_log)

BINDER TRANSACTION LOG (/sys/kernel/debug/binder/transaction_log)

BINDER TRANSACTIONS (/sys/kernel/debug/binder/transactions)

BINDER STATS (/sys/kernel/debug/binder/stats)

BINDER STATE (/sys/kernel/debug/binder/state)

DUMP VENDOR RIL LOGS (/system/xbin/su root vril-dump)

DUMPSYS (dumpsys)

APP ACTIVITIES (dumpsys activity all)

APP SERVICES (dumpsys activity service all)

APP SERVICES (dumpsys activity provider all)

在這些訊息中包含Android與Linux層的各種訊息，並能取得各種不同類別的訊息。例如，活動與事件、記憶體使用情形、系統狀態、射頻狀態，與網路狀態等。

值得探討的是，若產品是一個Android的手機或附有通訊功能的平板電腦。有些訊息包含電信通訊技術相關的底層訊息。這些訊息是通訊晶片與電信基定台的交換訊息。而在Bugreport的功能中可能無法傳遞這些訊息。需要特定的軟體或裝置去取得這些電信交換的訊息。

The log message Android is telling you - Bugreport

2012-10-17T02:42:00.002-07:00

Preface

When someone get sick or get hurt and go to see a doctor, he must tell what's wrong to doctor. What if the Android device got some problems, how to know what wrong is on itself? Certainly, you need to look at the Log message that Android export.

Where to start?

There's a command called bugreport. You can get all information that Android/Linux can tell you. The command is either adb bugreport or adb shell bugreport. In case you try to use the command to get the bug report from Android emulator with JB, you'll get almost 68 kind of log message as follows.

UPTIME (uptime)

MEMORY INFO (/proc/meminfo)

CPU INFO (top -n 1 -d 1 -m 30 -t)

PROCRANK (procrank)

VIRTUAL MEMORY STATS (/proc/vmstat)

VMALLOC INFO (/proc/vmallocinfo)

SLAB INFO (/proc/slabinfo)

ZONEINFO (/proc/zoneinfo)

PAGETYPEINFO (/proc/pagetypeinfo)

BUDDYINFO (/proc/buddyinfo)

KERNEL WAKELOCKS (/proc/wakelocks)

KERNEL CPUFREQ (/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)

PROCESSES (ps -P)

PROCESSES AND THREADS (ps -t -p -P)

LIBRANK (librank)

KERNEL LOG (dmesg)

LIST OF OPEN FILES (/system/xbin/su root lsof)

SMAPS OF ALL PROCESSES

SHOW MAP 1 (/init) (/system/xbin/su root showmap 1)

BLOCKED PROCESS WAIT-CHANNELS

SYSTEM LOG (logcat -v threadtime -d *:v)

EVENT LOG (logcat -b events -v threadtime -d *:v)

RADIO LOG (logcat -b radio -v threadtime -d *:v)

VM TRACES JUST NOW (/data/anr/traces.txt.bugreport: 2012-10-17 08:21:46)

VM TRACES AT LAST ANR (/data/anr/traces.txt: 2012-10-17 08:16:11)

NETWORK DEV INFO (/proc/net/dev)

QTAGUID NETWORK INTERFACES INFO (/proc/net/xt_qtaguid/iface_stat_all)

QTAGUID NETWORK INTERFACES INFO (xt) (/proc/net/xt_qtaguid/iface_stat_fmt)

QTAGUID CTRL INFO (/proc/net/xt_qtaguid/ctrl)

QTAGUID STATS INFO (/proc/net/xt_qtaguid/stats)

NETWORK ROUTES (/proc/net/route)

NETWORK ROUTES IPV6 (/proc/net/ipv6_route)

LAST KMSG (/proc/last_kmsg)

LAST PANIC CONSOLE (/data/dontpanic/apanic_console)

LAST PANIC THREADS (/data/dontpanic/apanic_threads)

SYSTEM SETTINGS (/system/xbin/su root sqlite3 /data/…

NETWORK INTERFACES (/system/xbin/su root netcfg)

IP RULES (ip rule show)

IP RULES v6 (ip -6 rule show)

ROUTE TABLE 60 (ip route show table 60)

ROUTE TABLE 61 v6 (ip -6 route show table 60)

ROUTE TABLE 61 (ip route show table 61)

ROUTE TABLE 61 v6 (ip -6 route show table 61)

ARP CACHE (/proc/net/arp)

IPTABLES (/system/xbin/su root iptables -L -nvx)

IP6TABLES (/system/xbin/su root ip6tables -L -nvx)

IPTABLE NAT (/system/xbin/su root iptables -t nat -L -nvx)

IPTABLE RAW (/system/xbin/su root iptables -t raw -L -nvx)

IP6TABLE RAW (/system/xbin/su root ip6tables -t raw -L -nvx)

WIFI NETWORKS (/system/xbin/su root wpa_cli list_networks)

SYSTEM PROPERTIES

VOLD DUMP (vdc dump)

SECURE CONTAINERS (vdc asec list)

FILESYSTEMS & FREE SPACE (/system/xbin/su root df)

PACKAGE SETTINGS (/system/xbin/su root cat /data/system/packages.xml)

PACKAGE UID ERRORS (/data/system/uiderrors.txt: 2012-10-15 02:30:29)

LAST RADIO LOG (parse_radio_log /proc/last_radio_log)

BACKLIGHTS

BINDER FAILED TRANSACTION LOG (/sys/kernel/debug/binder/failed_transaction_log)

BINDER TRANSACTION LOG (/sys/kernel/debug/binder/transaction_log)

BINDER TRANSACTIONS (/sys/kernel/debug/binder/transactions)

BINDER STATS (/sys/kernel/debug/binder/stats)

BINDER STATE (/sys/kernel/debug/binder/state)

DUMP VENDOR RIL LOGS (/system/xbin/su root vril-dump)

DUMPSYS (dumpsys)

APP ACTIVITIES (dumpsys activity all)

APP SERVICES (dumpsys activity service all)

APP SERVICES (dumpsys activity provider all)

These messages include all the information on Android and Linux layer and tell you about various message about Activities Event, Memory, System state, Radio state, Network state and so on.

Note, each Android phone has a modem function. Typically, the modem message contains the transition message between base station and modem chip insider Android phone. This kinda message may not be output from Linux kernel message. Hence, the bugreport function cannot output such a message as well.

手動更新 Nexus 7 到最新版本

2012-10-17T00:12:00.004-07:00

序

谷歌已經發行Nexus 7的4.1.2的版本於官方網站。有些人的Nexus裝置可能還沒收到平板電腦的主動通知來做升級。現在可以用本篇文章所介紹的方式來升級你的Google Nexus裝置。

這邊的方法適用於若你把你的Nexus做了其他事情導致作業系統異常。可以試用本篇的方法讓你的Nexus回到最新的工廠出廠版本。

介紹

以下的方法已經實驗過是可行的方式。執行前請先備份你的資料。因為更新會導致你的資料被全數刪除。再使用這個方法前，請確認你的Android裝置有開啟USB偵錯模式，並且能讓你的電腦認到你的Nexus的ADB Interface驅動裝置。

1. 使用adb reboot-bootloader的指令，重新開機你的電腦到快速開機(fastboot)模式。
2. 用fastboot oem unlock的指令對bootloader做解鎖動作。
　- 使用這個指令會讓你的Nexus出現一個警告訊息。若你能同意這個訊息請選同意。若無法同意請勿執行下列步驟。
3. 使用聲音的大小按鍵來選擇你的選項，確定選項後，在按下電源按鍵來確定執行同意。
4. 從網址https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz下載4.1.2的工廠出廠版本。
5. 解壓縮下載的檔案到並執行資料夾的flash-all.bat檔案。
6. 放下你的Nexus，直到更新完成前都不要做任何操作。
7. 更新完成後，記得執行上鎖bootloader的動作來保護你的Nexus資料安全。使用adb reboot-bootloader讓Nexus重新開機進入快速開機模式後，執行fastboot oem lock的指令於電腦上。

想要找到更多的Nexus裝置的工廠版本可以上https://developers.google.com/android/nexus/images?hl=zh-TW找到更多的訊息。

參考資料
Bootloader unlock, https://groups.google.com/forum/?fromgroups=#!msg/android-building/Ld5FoFinN7k/xcZPFBikw0MJ
Nexus Factory Image, https://developers.google.com/android/nexus/images?hl=zh-TW

Android / Linux Shell Commands

2012-10-16T23:08:00.002-07:00

Preface:

Android is running on Linux System and a Java based operating system. As you can see on Google Development Site, the architecture is as follows.

http://source.android.com/tech/security/#android-platform-security-architecture

Android is working on dark green (Android Runtime) and light blue (Applications & Application Framework) portion of above graph. The Dalvik VM is involved in Android Runtime block, which is used to run the Java Based Application or System on Application Framework and Application Layer.
Linux is working on light green (Libraries) and pink (Linux Kernel) portion of above graph.
This architecture can be always a reference for any Android powered device. However, there're something needed to be added or modified in real case.

Introduction

Android SDK provides a tool - ADB. There's a ADB server inside the Android powered devices and a ADB client in desktop/NB devices for connecting to ADB server. There're a lot of useful command in Android or Linux layer we can use for our interesting purpose. One of easy way to use them is to use ADB tool to invoke those commands for our purpose.

Explore the folder in Android emulator with JB build, there're a lot of command existed in /system/bin. To explore the file list in this folder by using adb shell "ls system/bin".

For instance,
am - Activity Manager, Java based command, the source code is located at platform_frameworks_base/blob/master/cmds/am/src/com/android/commands/am/Am.java
am is activity manager which can control application components in Android. Look at am page for more information

monkey - a stability test tool which generates random events for Android powered device, Java based command. The source code is located at platform_development/blob/master/cmds/monkey/src/com/android/commands/monkey/Monkey.java

pm - Package Manager which can manipulate package relative task, Java based command. The source code is located at platform_frameworks_base/blob/master/cmds/pm/src/com/android/commands/pm/Pm.java

dmesg - Linux Debug Message which can output Linux relative message, a C language based, the same usage with Linux System. The source code is located at platform_system_core/blob/master/toolbox/dmesg.c

ps - Process State, which output the process state with process id (pid), ram usage...etc, a C language based, the same usage with Linux System. The source code is located at android/platform_system_core/blob/master/toolbox/ps.c

From above examples, we know the commands in Android powered devices can be separated to C and Java language based. Either one can be used on Android. However the layer to execute these commands is different. There're many other language can be run on Linux such as python, perl, bash...etc. Hence, it's not only C or Java based executable file but also other languages can be run on Android powered devices.

Reference
Android Architecture, http://source.android.com/tech/security/
Android Source Code Mirror Site, https://github.com/android/
Package Manager, http://developer.android.com/reference/android/content/pm/PackageManager.html

Android Activity Manager 中文版

2012-10-15T22:54:00.004-07:00

English Version
序

Android的系統主要有四個應用的元件。有以下這四種元件 - 活動(Activities)、服務(Services)、傳播接收器(Broadcast receivers)、與內容提供者(Content providers)。當中只有活動這個元件有使用者介面。

活動管理器 (Activity Manager)是一個可以控制這些元件的一個工具。

介紹
活動管理器必須使用Shell指令"am"。若要了解am有哪些功能與參數可以使用，可以使用指令 "adb shell am"。執行這個指令必須把你的Android裝置連接到電腦並且啟動USB偵錯模式。

以下是執行adb shell am的輸出結果:
usage: am [subcommand] [options]
usage: am start [-D] [-W] [-P ] [--start-profiler ]
[--R COUNT] [-S] [--opengl-trace]
am startservice
am force-stop
am kill
am kill-all
am broadcast
am instrument [-r] [-e ] [-p ] [-w]
[--no-window-animation]
am profile start
am profile stop []
am dumpheap [flags]
am set-debug-app [-w] [--persistent]
am clear-debug-app
am monitor [--gdb ]
am screen-compat [on|off]
am display-size [reset|MxN]
am to-uri [INTENT]
am to-intent-uri [INTENT]

am start: start an Activity. Options are:
-D: enable debugging
-W: wait for launch to complete
--start-profiler : start profiler and send results to
-P : like above, but profiling stops when app goes idle
-R: repeat the activity launch 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

am startservice: start a Service.

am force-stop: force stop everything associated with .

am kill: Kill all processes associated with . Only kills.
processes that are safe to kill -- that is, will not impact the user
experience.

am kill-all: Kill all background processes.

am broadcast: send a broadcast Intent.

am instrument: start an Instrumentation. Typically this target
is the form /. Options are:
-r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with
[-e perf true] to generate raw output for performance measurements.
-e : set argument to . For test runners a
common form is [-e [,...]].
-p : write profiling data to
-w: wait for instrumentation to finish before returning. Required for
test runners.
--no-window-animation: turn off window animations will running.

am profile: start and stop profiler on a process.

am dumpheap: dump the heap of a process. Options are:
-n: dump native heap instead of managed heap

am set-debug-app: set application 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 monitor: start monitoring for crashes or ANRs.
--gdb: start gdbserv on the given port at crash/ANR

am screen-compat: control screen compatibility mode of .

am display-size: override display size.

am to-uri: print the given Intent specification as a URI.

am to-intent-uri: print the given Intent specification as an intent: URI.

specifications include these flags and arguments:
[-a ] [-d ] [-t ]
[-c [-c ] ...]
[-e|--es ...]
[--esn ...]
[--ez ...]
[--ei ...]
[--el ...]
[--ef ...]
[--eu ...]
[--ecn ]
[--eia [, [--ela [, [--efa [, [-n ] [-f ]
[--grant-read-uri-permission] [--grant-write-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]
[ | | ]

應用範例:

強制執行某個Package停止工作
adb shell "am -force-stop PACKAGE"
例:
adb shell "am -force-stop com.android.browser"
這個指令會強制停止顯示在畫面上的瀏覽器跳出。使用這個指令來強制停止工作，相關的Package也會同步被強制停止。

瀏覽指定網頁
adb shell "am start -a android.intent.action.VIEW -d url"
這個指令的參數-a指的是要執行的動作(action)，-d指的是執行動作所需要的資料(Data)。這邊的動作參數的值是 android.intent.action.VIEW，表示要做觀看的動作。-d參數後面的資料是網頁資料。
例:
adb shell "am start -a android.intent.action.VIEW -d http://google.com"
這個指令會開啟預設的瀏覽器並且開啟google.com的網頁。

撥電話
adb shell "am start -a android.intent.action.CALL -d tel:phone_number"
這個指令使用了動作為android.intent.action.CALL，表示要執行呼叫的動作，而其後的資料值為tel:phone_number，其中tel:為撥電話的多媒體型態(MIME Type)，tel:之後為所要撥出的電話號碼。
例:
am start -a android.intent.action.CALL -d tel:777
這個範例會使手機撥打電話號碼777。

呼叫出一個指定的活動(Activity)
adb shell "am start -n package/activity_name_or_full_activity_name_with_package"
範例中，-n後面要指定package的名稱與斜線/及activity的名稱呼叫某個Activity被執行。
例:
adb shell "am start -n com.android.settings/com.android.settings.Settings"
這個範例中，設定的使用者介面會被帶到前景。

利用am新增一個聯絡人
adb shell "am start -a android.intent.action.INSERT -t vnd.android.cursor.dir/contact -e name 'Android Auto' -e phone 1234567890"
這個範例的參數中，動作是 android.intent.action.INSERT，表示要做輸入的動作。-t後面接的值是多媒體的格式。這邊看到的多媒體格式為聯絡人的格式。-e後面接的是輸入欄位的名稱與欄位的值。這個範例輸入兩個欄位，一個是名稱(name)，另一個是電話號碼(phone)。它們的值分別為android與1234567890。這些參數與動作必須在應用程式的Manifest XML中有出現，才能使用他。若使用在不同的應用程式，你可以先確認源碼是否有相關的參數與設定。

使用的方法還有很多種，這邊只舉幾個例子讓讀者們啟發，可以做延伸的應用。

Upgrade your Nexus 7 (Wi-Fi) to 4.2 Manually

2012-10-15T18:55:00.002-07:00

Preface

Google has released 4.2 for Nexus 7 on WEB. Maybe someone has not received OTA notification for upgrade. If your device got some problem on your flash OS because of certain reasons, you can also recover your Nexus devices by the image that Google released on WEB.

Note that you can select the image rom for your Nexus device. You need to download the rom code with the same model for your Nexus device and then you can upgrade your Nexus device. For different Nexus model, you can take a look on web site - https://developers.google.com/android/nexus/

Instruction

You can follow the instruction below to upgrade or restore your Nexus. Note, you need to backup your personal data in advance, because using this instruction would erase all your data.

1. Reboot the device as fastboot mode by command - adb reboot-bootloader.
2. Unlock your bootloader by command - fastboot oem unlock
- The warning screen would bring up, please read it and make decision if you agree or not. If you don't agree, you cannot do the following action.
3. Using volume up or volume down to navigate the options and press power key to execute the selected option. If you agree the warning shows on screen, move the option to agree or ok or accept and then press power key to confirm the option.
4. Download the image from Google - https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz for 4.1 and https://dl.google.com/dl/android/aosp/nakasi-jop40c-factory-6aabb391.tgz for 4.2.
5. Unzip all the file to the folder and double click flash-all.bat within the folder.
6. Don't touch your Nexus 7 until flash is successfully.
7. After the flash process is done, lock your bootloader to secure your Nexus by command adb reboot-bootloader and then perform fastboot oem lock.

Above instruction may be used to recover your other Nexus device. You can look at web sit https://developers.google.com/android/nexus/images?hl=zh-TW for more information.

In case you don't receive the OTA upgrade notification, another way to upgrade your Nexus 7 is as follows,
Google Service Framework stop and Clear Cache. And then press the upgrade check on your Nexus. This is a method I got from someone's talk. You may be able to try it in case you just want to upgrade your Nexus 7. Why the method can be workable? I guess it's a bug for Nexus 7 OTA upgrade.

Reference
Bootloader unlock, https://groups.google.com/forum/?fromgroups=#!msg/android-building/Ld5FoFinN7k/xcZPFBikw0MJ
Nexus Factory Image, https://developers.google.com/android/nexus/images?hl=zh-TW

Android Activity Manager

2012-10-15T00:03:00.001-07:00

中文版
Preface

There're four application components in Android. They're Activities, Services, Broadcast receivers, and Content providers.There's only one component has User Interface. That's Activities. Activity Manger can help you to control the application components in Android. Let's take a look how to well use the Activity Manager for our work.

Introduction
There's a shell command called am, which performs the task by Activity Manager. The help of am, you can send the adb command - adb shell am when your computer are connect to your Android device.

usage: am [subcommand] [options]
usage: am start [-D] [-W] [-P ] [--start-profiler ]
[--R COUNT] [-S] [--opengl-trace]
am startservice
am force-stop
am kill
am kill-all
am broadcast
am instrument [-r] [-e ] [-p ] [-w]
[--no-window-animation]
am profile start
am profile stop []
am dumpheap [flags]
am set-debug-app [-w] [--persistent]
am clear-debug-app
am monitor [--gdb ]
am screen-compat [on|off]
am display-size [reset|MxN]
am to-uri [INTENT]
am to-intent-uri [INTENT]

am start: start an Activity. Options are:
-D: enable debugging
-W: wait for launch to complete
--start-profiler : start profiler and send results to
-P : like above, but profiling stops when app goes idle
-R: repeat the activity launch 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

am startservice: start a Service.

am force-stop: force stop everything associated with .

am kill: Kill all processes associated with . Only kills.
processes that are safe to kill -- that is, will not impact the user
experience.

am kill-all: Kill all background processes.

am broadcast: send a broadcast Intent.

am instrument: start an Instrumentation. Typically this target
is the form /. Options are:
-r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with
[-e perf true] to generate raw output for performance measurements.
-e : set argument to . For test runners a
common form is [-e [,...]].
-p : write profiling data to
-w: wait for instrumentation to finish before returning. Required for
test runners.
--no-window-animation: turn off window animations will running.

am profile: start and stop profiler on a process.

am dumpheap: dump the heap of a process. Options are:
-n: dump native heap instead of managed heap

am set-debug-app: set application 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 monitor: start monitoring for crashes or ANRs.
--gdb: start gdbserv on the given port at crash/ANR

am screen-compat: control screen compatibility mode of .

am display-size: override display size.

am to-uri: print the given Intent specification as a URI.

am to-intent-uri: print the given Intent specification as an intent: URI.

specifications include these flags and arguments:
[-a ] [-d ] [-t ]
[-c [-c ] ...]
[-e|--es ...]
[--esn ...]
[--ez ...]
[--ei ...]
[--el ...]
[--ef ...]
[--eu ...]
[--ecn ]
[--eia [, [--ela [, [--efa [, [-n ] [-f ]
[--grant-read-uri-permission] [--grant-write-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]
[ | | ]

Sample applications:

Force to stop working for specified package,
adb shell "am -force-stop PACKAGE"
Ex:
adb shell "am -force-stop com.android.browser"
In this case, if the browser is in the foreground, the browser would be stopped working and dismissed.
Note, the relative package would also be forced to stop working.

Trigger Android device to bring up the broswer and open a specified URL
adb shell "am start -a android.intent.action.VIEW -d url"
Within this command, start stands for doing something, -a stands for action, and -d stands for the data of action required.
Ex:
adb shell "am start -a android.intent.action.VIEW -d http://google.com"
This example represents a view action for opening a url.

Make a phone call
adb shell "am start -a android.intent.action.CALL -d tel:phone_number"
Within this command, action is to make a call - android.intent.action.CALL, and action data is tel:phone_number.
Ex:
am start -a android.intent.action.CALL -d tel:777
In this example, Android device would make a phone call with number 777.

Launch an activity with specified package name
adb shell "am start -n package/activity_name_or_full_activity_name_with_package"
Within this example, -n is followed by component name and the component would be launched by executing this command.
Ex:
adb shell "am start -n com.android.settings/com.android.settings.Settings"
In this example, the settings activity would be brought up to top screen.

Create a new contact by am
adb shell "am start -a android.intent.action.INSERT -t vnd.android.cursor.dir/contact -e name 'Android Auto' -e phone 1234567890"
Within the command, action is insertion, -t stands for MIME type of inserting data in contact, -e stands for extra key that is defined in Manifest XML file, the name is followed by -e for the extra key to be used for contact, and the value of extra key - name is followed by extra key - name. The parameters for -e phone 1234567890 has identical usage with -e name 'Anddroid Auto'. Contract app would fill the field of assigning extra keys for new contact in Android after executing above command. With respecting to action - android.intent.action.INSERT, it's necessary to have this configuration in Manifest XML. Or Android would do nothing for this command. That means in case you want to use this command on another activity, you need to check if this configuration's existed in Manifest XML file of the App you want to control.

There're a lot of parameters you can use for controlling Android. Above examples provided you some idea to extend your usage for your work

Android MonkeyRunner with Jythan - A simple example to get start

2012-10-14T20:09:00.002-07:00

中文版
Preface
The MonkeyRunner is a tool provided by Google Android Development Team and released with Android SDK. The MonkeyRunner is consisted of a set of command and use Jython script as its interpreting program language. The Jython script is process by Java VM rather than C/C++. We can add some logic statement into the script for more flexible control by Jython script.

Before you start to read this article, you need to know how to set up the environment of monkeyrunner. If you don't know how to do it, you can read my another article at http://android-test-tw.blogspot.com/2012/10/android-automation-test-by-monkeyrunner.html in this blog in advance.

Brief Jython:

Let's brief Jython Script for monkeyrunner below before we go over next section.

The variable for Jython language, it can manipulate several type of variable such as Number, String, and List. The variable in Jython doesn't need to be declared. All you have to do is to assign to value to it.

Let's take a look some simple example and description below. You can copy the script to a text file and save it to a file named example.py (file name can be any valid file name in your system). Open a cmd window and type monkeyrunner.bat example.py and press enter key on your computer.

Assign a number to a variable.
num = 1
Assign a string to a variable.
str = "Hello"
str = 'Hello2'
Assign a list to a variable.
list = ['mail','inbox',100,200]

The logic statement and loop control are described as follows,

The if statement in Jython is as follows,
if_stmt ::= "if" expression ":" suite
( "elif" expression ":" suite )*
["else" ":" suite]

Ex:
if num < 0:
num = 0
   print('Negative changed to zero')
  elif num == 0:
   print('Zero')
  elif num == 1:
   print('Single')
  else:
   print('More')

The while statement in Jython is as follows,
while_stmt ::= "while" expression ":" suite
["else" ":" suite]

Ex:

num = 100
go = True

while go:
getNum = int(raw_input('Input a number : '))
if getNum == num:
print 'That is right.'
go = False
else:
print 'Oh No~'
else:
print 'Game over.'
print 'Done'

The for statement in Jython is as follows,

for_stmt ::= "for" target_list "in" expression_list ":" suite

["else" ":" suite]

Ex:

for i in range(9):
print(i)
else:
print 'done'

A simple example:

First, you need to bring up a cmd window on windows operation system and attach your Android device to computer and check if the computer can detect you ADB interface of Android powered device.

In this example we want to verify the result of run-time image and make decision for next action. At this case, we need to add logic statement in monkeyrunner. The logic script refers Jython Script. However we can refer to Python script tutorial for writing statement because Jython uses the same script with Python. Note, not all the Python script and components/class you can use on monkeyrunner. However you can try to use it.

Following example shows you how to turn on Bluetooth radio on your Android device and check the UI (user interface) if Radio icon has set to Bluetooth On. And turn off Bluetooth radio. The goal is to perform turn on and off Bluetooth Radio repeatedly and check the result by UI.

In this case we need to use a method of MonkeyRunner class that official web site doesn't mention. That's a API - MonkeyRunner.loadImageFromFile(Full_File_Path);

In order to compare the screenshot for the testing result, we need to get a screenshot for pass criteria. We can use MonkeyRunner to get the screenshot by Jython script. The piece of script is as follows.

result = device1.takeSnapshot()
result.getSubImage ((133,85,85,28))
result.writeToFile('./capture1.png','PNG')

The screenshot of Bluetooth On below was captured at settings/wireless screen on Android device and ran the above script. Note, the screen resolution is 240x432 and OS version is 4.1 in emulator.

capture1.png

Ex:

from com.android.monkeyrunner import MonkeyRunner, MonkeyDevice, MonkeyImage
#Import class of MonkeyRunner, MonkeyDevice, and MonkeyImage.
device1 = MonkeyRunner.waitForConnection(10000,"emulator-5554")
print 'connected'
#Connect Android device from computer and assign handler to variable -device1.
monkeyimage1 = MonkeyRunner.loadImageFromFile('./capture1.png')
print 'capture1.png loaded'
#Load a existing image file by load image API and assign handler to variable - monkeyimage1;
device1.press('KEYCODE_HOME','DOWN_AND_UP',' ')
print 'home key are triggered'
#Send home key event to bring up Launcher
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
device1.press('KEYCODE_MENU','DOWN_AND_UP',' ')
#Send menu key event
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
device1.touch ( 95, 417, "DOWN_AND_UP")
#Touch system settings in menu list
MonkeyRunner.sleep(3);
#Wait for reaction of Android device
for i in range(1000):
device1.touch ( 197, 96, "DOWN_AND_UP")
#Touch bluetooth On
MonkeyRunner.sleep(2);
monkeyimage2 = device1.takeSnapshot()
#Take a screenshot on Android device and assign handler to variable monkeyimage2
monkeyimage2 = monkeyimage2.getSubImage ((133,85,85,28))
#Get specified rectangle from screenshot got by last step for the result we want to check and assign handler to variable monkeyimage2 again.
if monkeyimage2.sameAs ( monkeyimage1, 1 ):
print str(i+1)+':pass'
else:
print str(i+1)+':fail'
#Compare the result if both images of pre-loaded and run-time screenshot are the same.
device1.touch ( 155, 95, "DOWN_AND_UP")
#Touch bluetooth Off
else:
print 'done'

Reference:

Android Automation Test by Monkeyrunner

2012-10-10T23:47:00.001-07:00

中文版
Preface

There're a lot of brand company used Android as their product operation system around the world in 2012. Every company add their value added feature and competition into the Android powered device. Since they've identical system base, they can be controlled by the same tool. That is monkeyrunner. The powerful tool - monkeyrunner is developed by Google Android team. Utilize the tool, you can save your cost on equipment and quantity of testing resource.

What does monkeyrunner stand for?

The monkeyrunner provide a set of command to control your Android device. The user can send the control command to Android powered device by computer such as touch screen, key pressed/hold, install/uninstall your App, limited Linux shell script, wake your device, inputing text message, reboot, sliding your screen, and save your device screen to image file on PNG or bitmap format...etc.

Where can we start to play it?

You need a Android emulator or Android powered device.

Install J2SDK into your computer. Either version 6 or 7 is applicable. Get it from following url in case you don't have it.
http://www.oracle.com/technetwork/java/javase/downloads/index.html

Install Android SDK. Get it from following url in case you don't have it.
http://developer.android.com/sdk/index.html

Google provides 3 kind of OS platform forAndroid SDK
1. Microsoft Windows
2. Linux (i386) (Ubuntu is Linux system and the best choice)
3. Mac OS X (intel)

Configure you ADB USB Driver

I'll introduce the content by using Microsoft Windows OS. Install your usb and adb interface driver by usb driver provided by Google Android SDK or Brand company's web site.

In case you are using Unbutu operation system for your Android device, you don't need a USB driver for ADB Interface.

I'll suggest add the path of folders of tools and platform-tools in Android SDK into environment variable - path.That's convenient when you open a command line windows and execute the commands for Android controlled.

Last step is to enable USB debug mode for Android device. Typically, this option is in Settings->Development->USB Debug

Finally, Check your computer recognize your Android powered device by command of adb devices as follows. The serial number of Android device is followed by words "device". That means Android device is connected to your computer and work properly.

After configuration is done, you can start to use monkeyrunner for controlling your Android powered devices.

Foundamental practice

The monkeyrunner command should be sent by computer and use adb connection. Let's have a basic example as follows.

Open a command window by command cmd at start->run on your computer and type monkeyrunner.bat.

At this moment, your can open another command window to check if your Android device is connected to computer successfully.

Type the following script to your monkeyrunner.bat command window. Note, you need to be careful for case sensitivity. The words can be different in meaning based on different use of uppercase and lowercase letters.

First line, the command of "from com.android.monkeyrunner import ..." is to loaded relative API from monkeyrunner.
Second line, assign the handler of Android device to variable - device.
Third line, send the menu key event to Android device.

Before sending press command.

After sending press command.

More benefit for you by monkeyrunner

Take a look on official Android development web site, monkeyrunner can help you to perform multiple Android device control, functional test, regression test, and extended automation. To be clear, monkeyrunner can help you to do the repeated operation or test and mitigate your requirement on human resource.

As we've talk about the benefit aforementioned, monkeyrunner can help you to touch screen, slide screen, monitor the variation of screen...etc. You can utilize monkeyrunner to record the scenario of specified operations and playback them for your testing purpose on Android powered device.

The monkeyrunner can help you to do the test over day and night without any complain. The tool is very helpful for the product to meet the schedule of Time To Market.

Advanced practice

Let's have a example with more scenario for using monkeyrunner below. I'd like to introduce a test for Bluetooth on/off.

Let your Android powered device go into Launcher in advance and run the following script.

	monkeyrunner script
>>>	device1.press('KEYCODE_MENU','DOWN_AND_UP',' ')
	Send menu key event, as figure-m2
>>>	device1.touch ( 95, 417, "DOWN_AND_UP")
	Touch settings in menu list, as figure-m-3
>>>	device1.touch ( 197, 96, "DOWN_AND_UP")
	Touch bluetooth On, as figure-m-4
>>>	device1.touch ( 155, 95, "DOWN_AND_UP")
	Touch bluetooth Off, as figure-m-5

figure-m1

figure-m2

figure-m3

figure-m4

figure-m5

I'll list more useful examples for monkeyrunner to control Android device. Welcome to visit my blog again for the latest information in the future.

Reference
monkeyrunner, http://developer.android.com/tools/help/monkeyrunner_concepts.html , published by Google Inc.

Android Automation Test for Stability by Monkey

2012-10-10T20:21:00.003-07:00

中文版
Preface

There's a Monkey existed in Android OS. Android device would do the things randomly once you launch the Monkey program in Android device.

Typically, we used Monkey to do the stability test against Android device. Although it's not predictable for running action by Monkey program, we still can limit some actions for Monkey program under particular condition(s). Let's look how Monkey benefit the quality of Android device.

What does Money stand for?

There'are two kind of Monkey program in Android. However they're totally different for the purpose. They're monkeyrunner and Money program. For the former one, Android device can be controlled by pre-defined scenario/action. For the poster one, it generates random events for Android device.
By different purpose, we often used monkeyrunner to do the functional test and used Monkey to do the stability test against Android device.
I've a separate page to talk about monkeyrunner. We are going to talk about the Monkey here.

Why do we use monkey to test our product?

It's hardly to predict each user how to use their Android device. Hence, utilize a good tool to help our work is a important matter. A good qualified product should be not lockup or reboot occurred even the device is operated by arbitrary operations. This is the reason why we used Monkey to help find the quality issue early.

How to use Monkey program?

Monkey is existed in Android devices. When you want to launch Monkey program, you need to use shell command by ADB tool on computer.

Ex:

adb shell monkey -v 500

The above command shows you an example that monkey would generate 500 events randomly against Android.

Here are the options you can use for Monkey program and announce on official Android Dev Site.

Category	Option	Description
General	`--help`	Prints a simple usage guide.
General	`-v`	Each -v on the command line will increment the verbosity level. Level 0 (the default) provides little information beyond startup notification, test completion, and final results. Level 1 provides more details about the test as it runs, such as individual events being sent to your activities. Level 2 provides more detailed setup information such as activities selected or not selected for testing.
Events	`-s`	Seed value for pseudo-random number generator. If you re-run the Monkey with the same seed value, it will generate the same sequence of events.
	`--throttle`	Inserts a fixed delay between events. You can use this option to slow down the Monkey. If not specified, there is no delay and the events are generated as rapidly as possible.
	`--pct-touch`	Adjust percentage of touch events. (Touch events are a down-up event in a single place on the screen.)
	`--pct-motion`	Adjust percentage of motion events. (Motion events consist of a down event somewhere on the screen, a series of pseudo-random movements, and an up event.)
	`--pct-trackball`	Adjust percentage of trackball events. (Trackball events consist of one or more random movements, sometimes followed by a click.)
	`--pct-nav`	Adjust percentage of "basic" navigation events. (Navigation events consist of up/down/left/right, as input from a directional input device.)
	`--pct-majornav`	Adjust percentage of "major" navigation events. (These are navigation events that will typically cause actions within your UI, such as the center button in a 5-way pad, the back key, or the menu key.)
	`--pct-syskeys`	Adjust percentage of "system" key events. (These are keys that are generally reserved for use by the system, such as Home, Back, Start Call, End Call, or Volume controls.)
	`--pct-appswitch`	Adjust percentage of activity launches. At random intervals, the Monkey will issue a startActivity() call, as a way of maximizing coverage of all activities within your package.
	`--pct-anyevent`	Adjust percentage of other types of events. This is a catch-all for all other types of events such as keypresses, other less-used buttons on the device, and so forth.
Constraints	`-p`	If you specify one or more packages this way, the Monkey will only allow the system to visit activities within those packages. If your application requires access to activities in other packages (e.g. to select a contact) you'll need to specify those packages as well. If you don't specify any packages, the Monkey will allow the system to launch activities in all packages. To specify multiple packages, use the -p option multiple times — one -p option per package.
Constraints	`-c`	If you specify one or more categories this way, the Monkey will only allow the system to visit activities that are listed with one of the specified categories. If you don't specify any categories, the Monkey will select activities listed with the category Intent.CATEGORY_LAUNCHER or Intent.CATEGORY_MONKEY. To specify multiple categories, use the -c option multiple times — one -c option per category.
Debugging	`--dbg-no-events`	When specified, the Monkey will perform the initial launch into a test activity, but will not generate any further events. For best results, combine with -v, one or more package constraints, and a non-zero throttle to keep the Monkey running for 30 seconds or more. This provides an environment in which you can monitor package transitions invoked by your application.
	`--hprof`	If set, this option will generate profiling reports immediately before and after the Monkey event sequence. This will generate large (~5Mb) files in data/misc, so use with care. See Traceview for more information on trace files.
	`--ignore-crashes`	Normally, the Monkey will stop when the application crashes or experiences any type of unhandled exception. If you specify this option, the Monkey will continue to send events to the system, until the count is completed.
	`--ignore-timeouts`	Normally, the Monkey will stop when the application experiences any type of timeout error such as a "Application Not Responding" dialog. If you specify this option, the Monkey will continue to send events to the system, until the count is completed.
	`--ignore-security-exceptions`	Normally, the Monkey will stop when the application experiences any type of permissions error, for example if it attempts to launch an activity that requires certain permissions. If you specify this option, the Monkey will continue to send events to the system, until the count is completed.
	`--kill-process-after-error`	Normally, when the Monkey stops due to an error, the application that failed will be left running. When this option is set, it will signal the system to stop the process in which the error occurred. Note, under a normal (successful) completion, the launched process(es) are not stopped, and the device is simply left in the last state after the final event.
	`--monitor-native-crashes`	Watches for and reports crashes occurring in the Android system native code. If --kill-process-after-error is set, the system will stop.
	`--wait-dbg`	Stops the Monkey from executing until a debugger is attached to it.

ex:
adb shell "monkey -s 1 --throttle 100 -v -v -v --ignore-crashes --ignore-timeouts --ignore-security-exceptions 99999999"

In this case, we expect to see if any operation would cause the system reboot or lockup and ignore the factors that would cause the Monkey program stopped. Take a look on the description aforementioned for the condition that command used in this example.

There're two options we cannot see the description on official web site. However they can be found on help description when you send the command adb shell monkey to Android device. Let's take a look on them below.

Constraints	--pkg-blacklist-file	Set a blacklist for the package that are not going to do the test by Monkey. This option are followed by a text file. The text file contain a list of packages. Note, each package can only be listed on one line.
Constraints	--pkg-whitelist-file	Set a whitelist for the package that are going to do the test by Monkey. The random event would only be generated by specified package name in whiltelist. This option are followed by a text file. The text file contain a list of packages. Note, each package can only be listed on one line.

Ex:
adb shell "monkey -v --pkg-blacklist-file /data/local/tmp/blacklist.txt 500"

The content of blacklist.txt is as follows,
com.google.android.apps.maps
com.android.launcher

In this case, Monkey would not do anything for Google Map and Launcher. It's also a special case because we set Launcher in blacklist. You may only see the lock screen and unknow what the Monkey is doing. You can check logcat log to see if any action that Monkey does. If you remove the com.android.launcher from blacklist.txt, the Monkey would not do the things for Google Map only.

Reference
UI/Application Exerciser Monkey, http://developer.android.com/tools/help/monkey.html

Android Automation Test for Stability by Monkey 中文版

2012-10-09T02:48:00.002-07:00

English Version

序

在Android的作業系統中，有一隻猴子 (Monkey) 的程式。這個程式啟動後就會讓你的Android裝置像猴子一樣的活蹦亂跳，到處亂跑。

這樣的猴子特性剛好可以讓我們來對Android裝置做穩定性測試。事實上，這個猴子程式亂跑的範圍 (Scope) 與活力 (Interval) 及方向 (Event) 還是可以被規範的．以下讓我們來看看如何駕馭這隻猴子程式，讓這個猴子來幫助我們的產品開發。

猴子程式是甚麼 ?

在Android的官方自動化測試領域有兩隻猴子，一個稱做猴子跑步 (monkeyrunner)，另一個就是我們在這要談的猴子 (Monkey)。這兩者的區別是，前者可以精準的控制Android裝置的行為。後者是藉由亂數產生的事件來對Android裝置做隨意且不可預期的操作。在目的上，monkeyrunner能用來做功能性驗證，與指定行為的穩定度測試。不同於monkeyrunner，Monkey可用於隨意的大量性操作來測試Android手機的整個性統或是指定應用程式(App)的穩定度。

為什麼用猴子來測試我們的產品 ?

每當我們完成一個產品，我們很希望能快點分享出去。但面對千千萬萬的使用者，無法了解每個人的操作習慣。在許多年輕的工程師，累積除錯的經驗尚未成熟前，又面臨產品計畫的時間壓力，常會忽略一些小細節。又或者是一個協同開發的大型複雜專案，整合管理出現漏洞時，但沒有人發現。這時候利用猴子程式來幫忙抓出可能性的錯誤是一個挺有效率的方式。

一個好品質的應用程式 (App)或是產品 (Android 裝置)即使在隨便亂操作的情況下，應該要能做出所有的防錯處理。程式崩潰 (Crash) 或是當機 (Lock up or Reboot)不應該出現。基於這樣的理由，使用monkey能讓我們所開發的產品能快速的讓潛在的問題浮現。

如何駕馭猴子(Monkey)程式

Monkey內存在Android裝置內，因此我們要使用猴子程式，可以透過ADB的方式對手機下Shell程式的指令。

adb shell monkey -v 500

以上這個指令會對Android裝置下達500個連續指令做隨意的操作。

以下表格說明使用參數去規範Monkey:

類別	參數選項	說明
一般	`--help`	顯示Monkey的相關用法。
一般	`-v`	每一個 -v 的參數在adb shell monkey之後，會增加執行中的資訊。只有一個-v的Monkey執行會提供少量的資訊。若有兩個-v (E.g. adb shell monkey -v -v)，執行中會堤供較多的訊息，諸如獨自被傳送到你的App (Activity)的事件. 若有三個 -v ，執行中會提供更多像是設定的資訊等的訊息。
事件	`-s`	亂數種子。用來產生亂數事件使用。若使用相同的亂數來執行monkey測試，他會產生相同的程序的事件。
	`--throttle`	在每個事件執行後與下個事件產生的間隔時間。若不設定，每個事件無間隔時間。這個設定可用來緩和測試以避免系統硬體的效能不佳時，排除硬體效能因素所產生的問題。
	`--pct-touch`	調整觸碰事件產生的發生率百分比。(觸碰事件是一個按壓下去與放開於螢幕同一個點的事件)
	`--pct-motion`	調整移動的事件觸發發生率百分比。(這個事件是由一個點按壓下螢幕中的一個點並隨意滑動到另外一個座標位置再放開的事件)
	`--pct-trackball`	調整軌跡球觸發事件。
	`--pct-nav`	調整基本方向按鍵事件的發生率百分比。(方向事件包含上下左右)
	`--pct-majornav`	調整主要的方向按鍵事件的發生百分比。(這些方向的事件一般都是在你的使用者介面有影響，例如五個方向按鍵、返回按鍵(Back)、或是選單按鍵等(Menu))
	`--pct-syskeys`	調整系統按鍵觸發事件的發生率百分比。(例如家按鍵(Home、返回按鍵(Back)、發話按鍵(Start Call),斷話鍵(End Call), 或是聲音鍵(Volumn up/down))
	`--pct-appswitch`	調整App (Activity)啟動的發生率百分比。(Monkey會透過startActivity()這個API呼叫Activity做為最大化測試涵蓋率到你要測試的包裝(package)的方法)
	`--pct-anyevent`	調整其他型態的類別事件發生率的百分比。這是一個可以抓住所有其他型態的如按鍵壓下的事件，其他比較少使用在裝置上的事件等。
限制	`-p`	限制monkey只測試指定的Packages. 若你要測試的Package會與其他的Package有關連，你必須一起指定這些Package來執行這項參數．若你無使用這個參數，Monkey會測試系統內所有的Package。要指定多個Package必須下達多個 -p，每個 -p 後面只能放一個Package。
限制	`-c`	若你指定一個或多個分類(categories)，Monkey將會只允許系統去探訪你所指定的分類的活動 ( Activity )。若你沒有指定分類，monkey會選取所有列在分類為 Intent.CATEGORY_LAUNCHER 或 Intent.CATEGORY_MONKEY 的活動( activities )。指定多個分類要多次使用 -c 參數，每一個參數只能指定一個分類。
除錯	`--dbg-no-events`	當指定這個參數，Monkey將操作測試活動 ( activity ) 初始化執行，但將不會產生任何進一步的事件。最佳的結果是與 -v 參數結合使用一個或多個包裝( Package )的限制與一個非零值的 throttle 參數以保持Monkey持續執行超過30秒。這提供一個可以觀察被應用程式呼叫的包裝 ( Package ) 的資訊交換 ( Package ) 的環境
	`--hprof`	若設定了這個參數，將會於Monkey事件程序的前與後立即產生問題發生特徵的報告，這將會產生近5Mb的檔案於Android裝置內的data/misc資料夾。必須小心使用。可查詢Traceview取得更多的資訊。
	`--ignore-crashes`	一般來說，當應用程式遭遇到任何類型的應用程式崩潰( Crash )或無法掌控的例外( unhandled exception )問題，monkey會停下來。這些錯誤像是應用程式無回應( Application Not Responding)的對話框。若你使用了這個參數，Monkey會持續的傳送事件直到你所設定的參數數量完成。
	`--ignore-timeouts`	一般來說，當應用程式遭遇到任何類型的到期(timeout)問題，monkey會停下來。這些錯誤像是應用程式無回應( Application Not Responding)的對話框。若你使用了這個參數，Monkey會持續的傳送事件直到你所設定的參數數量完成。
	`--ignore-security-exceptions`	一般來說，當應用程式遭遇到任何類型的權限問題monkey會停下來。舉例來說，如果你嘗試去喚起一個需要某些權限的活動( Activity )就會遇到這樣的情形。若你使用了這個參數，Monkey會持續的傳送事件直到你所設定的參數數量完成。
	`--kill-process-after-error`	一般來說，當Monkey因為錯誤(Error)停止，應用程式的錯誤會留在畫面上。若這個參數被設定於monkey中，牠會發出信號去停止有問題的程序( Process )。注意，一個正常的或成功的完成，被執行的程序不會被停止，裝置只是簡單的留在最後一個事件發生後的狀態。
	`--monitor-native-crashes`	等待並且報告Android系統的native源碼損毀發生。若有設定 --kill-process-after-error 參數，系統將會停止monkey測試。
	`--wait-dbg`	重執行中停止monkey直到除錯器(debugger)連接到裝置。

範例：

adb shell "monkey -s 1 --throttle 100 -v -v -v --ignore-crashes --ignore-timeouts --ignore-security-exceptions 99999999"
在這個例子中，主要是希望能夠發現有甚麼方法會造成手機當機或重新開機的現象。設定為亂數種子為1，每個事件發生的間隔時間為100毫秒，忽略App的損毀 ( Crash )問題，忽略ANR的問題，忽略因為應用程式權限不足導致跳出Monkey的問題，執行99999999個事件。

在Android官網上還有兩個參數我們看不到說明，以下我對這兩個參數做說明：

限制	--pkg-blacklist-file	限制monkey不測試紀錄於文字檔案內的Packages，若你無使用這個參數，Monkey會測試系統內所有的Package。要指定多個Package不被執行必須在文字檔案內紀錄所有不要測試的Packages名稱，文字檔案內每一行只能放一個Package。
限制	--pkg-whitelist-file	限制monkey只測試於指向的文字檔案的指定的Packages. 若你要測試的Package會與其他的Package有關連，你必須一起指定這些Package來執行這項參數．若你無使用這個參數，Monkey會測試系統內所有的Package。要指定多個Package必須在文字檔案內紀錄所有要測試的Packages名稱，文字檔案內每一行只能放一個Package。

範例：
adb shell "monkey -v --pkg-blacklist-file /data/local/tmp/blacklist.txt 500"

其中blacklist.txt的內容為
com.google.android.apps.maps
com.android.launcher

在這個範例中，monkey的執行不會執行Google Map與Launcher。特別的是，因為我們設定Launcher在黑名單中 ( blacklist.txt ) ，畫面有可能會持續停留在上鎖的畫面且持續的進行monkey測試。直到500個事件發生完畢，monkey才會停止。

參考資料
UI/Application Exerciser Monkey, http://developer.android.com/tools/help/monkey.html

Android 自動化操作與測試 - monkeyrunner

2012-10-08T02:22:00.001-07:00

English Version
序

在2012這個年代，Android大軍已經在各家品牌廠與中國的白牌廠商等硬體廠商遍地開花。各式各樣的品牌，琳瑯滿目。不過在這個一個Android大軍的共同點，大家都是系出同門。來自谷歌大門。因此，我們有幸得以使用相同的開發或控制資源於不同廠牌的Android手機或機器人。

對於一些軟體或硬體開發廠商來說，要確保自己的產品能夠有足夠的品質，必須投資相當多的測試資源。在測試過程中，最昂貴的投資不外乎是設備與人。但谷歌在開發Android時，已經貼心的幫後續使用Android OS的廠商們提供一個操控Android機器人可溝通的語言。他就是猴子跑步－ monkeyrunner。利用這個套件可以不需要購買額外特別昂貴的軟體設備．同時也可以協助人力成本的運用。

猴子跑步 (monkeyrunner) 是甚麼 ?

monkeyrunner是谷歌的Android開發團隊提供的一套工具，這套工具題供一組指令集，讓使用者可以發送控制命令給Android手機、平板電腦或Android驅動的電子設備。

monkeyrunner工具所提供的指令包含發送按鍵(Key/Button)控制事件、拉滑(Drag/Slide)螢幕控制事件、觸控(Touch)螢幕控制、儲存即時螢幕畫面成為圖檔(為PNG或BMP格式)、傳回選定圖片檔案與即時Android畫面比較的結果、輸入一段文字、執行Shell命令、顯示提示訊息、喚醒螢幕、安裝APP、移除APP、設定重新開機與取得系統資訊等功能。

該從哪開始 ?

首先你需要一個Android的裝置，若有實際的Android硬體裝置比較好。但若沒有，又想跟monkeyrunner玩耍，Android SDK內建的Emulator也是一個選擇。

你的電腦需要安裝Oracle的J2SDK，6或7版本皆可。可於下方網址取得。
http://www.oracle.com/technetwork/java/javase/downloads/index.html

你需要下載Android SDK，可於下方網址取得。
http://developer.android.com/sdk/index.html

Android SDK可於以下三種作業系統使用
1. Microsoft Windows
2. Linux (i386) (Ubuntu 是Linux 系統中開發Android程式比較好的選擇)
3. Mac OS X (intel)

設定ADB USB Driver
以Microsoft Windows作業系統為例，插入USB線到手機與電腦後，第一次連線電腦通常需要安裝ADB USB Driver，於Windows作業系統會要求安裝不明裝置的USB Driver。關於Google Nexus的裝置，你可用Android SDK中的USB Driver (置於SDK_目錄\extras\google\usb_driver)來安裝ADB Interface Driver。若您的裝置不是Nexus，你則需要安裝手機品牌廠的ADB USB Driver。例如HTC的手機，你需要到HTC的官網去下載。

以Unbutu作業系統與在各系統的Emulator為例，不需要安裝USB Driver。

通常我會建議大家把Android SDK的tools與platform-tools兩個資料夾的路徑加在系統環境變數的path中. 這樣可以讓你在執行過程中呼叫adb與monkeyrunner的環境更加的便利。

最後一個步驟就是設定Android裝置進入USB Debug Mode。這個選項在大部分的Android裝置會放在設定->開發人員選項->USB偵錯。

最後確認一下，喚出cmd視窗，使用adb devices的指令，確認電腦有認到Android裝置，如下畫面。

執行adb devices後，會出現目前已連接上你的電腦USB的Android裝置的機器序號，在序號後必須是顯示device才能算是連線成功。

以上設置需求完成後，就可以來跟猴子跑步玩耍。

基礎練習

monkeyrunner的執行方式必須由電腦端發起，並且透過adb連線來對Android裝置下命令。現在讓我們來用一個最簡單的範例帶您進入monkeyrunner的控制。

以下的範例以Microsoft Windows 7的方式呈現. Windows XP或Vista的行為應該與Windows 7大同小異。

打開Android SDK的資料夾，資料夾內有個tools的資料夾，執行內部有個monkeyrunner.bat的批次檔。

開啟另一個cmd視窗，確認你的Android device的序號(Serial Number)後面顯示device。

在已開啟的monkeyrunner視窗中輸入如下的內容:

monkeyrunner命令中，大小寫的字母視為相異，務必確認大小寫一致。

第一個命令＜from com.android.monkeyrunner import ...＞是把monkeyrunner相關的class預載進來執行環境。
第二個命令是進行Android device與電腦的monkeyrunner建立連線，並且把連線的掌控權交給device這個變數。若電腦同時接到多台Android裝置，需要在waitForConnection的括號中輸入指定的Android裝置序號，例如("emulator-5554")。
第三個命令是利用第二個命令已經設定好的並擁有控制權的變數device來下指令。這邊下的指令是按壓選單鍵控制。因此可以看到以下Android裝置的圖片一為下press指令前，第二張圖片為下press指令後，主畫面的選單跳出來。

下press指令前

下press指令後

猴子能協助你跑那些地方

在Google的官方網頁中提到，monkeyrunner可以做幾個用途，這些用途有多個Android裝置控制、功能測試、回歸測試、與延伸自動化。其實說得明白些，monkeyrunner可以讓你取代人工操作螢幕上可執行的動作。如前文所提，monkeyrunner可以幫你觸碰螢幕、拉滑畫面、觀察螢幕上圖像的變化。只要讓adb與monkeyrunner環境可以順利執行，就可以用預先錄製下來的一連串行動 (Scenario)，對Android裝置做控制。

以一般使用者想做的事，最可能會有反覆性的動作應該會是玩Android遊戲時要練功。若是反覆性行為就可以利用monkeyrunner來達成。

以軟體或硬體開發商而言，想要開發一個有品質的產品，除了優良的設計流程管理，也不能漏掉最重要的驗收階段。對於每一個產品功能 (Feature)，要有反覆性的驗證，對於穩定度測試，monkeyrunner更能24小時，日以繼夜，任勞任怨的為你工作。除了操控用的電腦當機情形外，基本上他不會罷工。

進階練習

介紹到這，我們可以來舉個稍微多點情境的例子。若我們想要做一個Bluetooth開啟與關閉測試，我們可以利用monkeyrunner來幫我們達成。

首先我們讓手機進到主畫面(Launcher)，然後執行下列的動作：

	monkeyrunner 指令
>>>	device1.press('KEYCODE_MENU','DOWN_AND_UP',' ')
	觸發Menu按鍵，呼叫選單，如圖m-2
>>>	device1.touch ( 95, 417, "DOWN_AND_UP")
	觸發觸碰Menu清單的Settings選項，如圖m-3
>>>	device1.touch ( 197, 96, "DOWN_AND_UP")
	觸發觸碰Bluetooth Off的螢幕位子，如圖m-4
>>>	device1.touch ( 155, 95, "DOWN_AND_UP")
	觸發觸碰Bluetooth On的螢幕位子，如圖m-5

圖-m1

圖-m2

圖-m3

圖-m4

圖-m5

後語
我們談完基本的monkeyrunner的用法，這些基本的方法可以很快的延伸到我們所想要的多種情景操作．但monkeyrunner可以做更多，才能達到我們所想要的結果．在別篇文章我們會再介紹monkeyrunner的強大用途．

參考資料
monkeyrunner, http://developer.android.com/tools/help/monkeyrunner_concepts.html , published by Google Inc.

Android Tech on control and test

Using Shell Script on Android

在Android做LTP (Linux Test Project)測試

在Android做LTP (Linux Test Project)測試

序:

參考資料:

Linux Test Project (LTP) on Android

Perform LTP on Android

Preface

Introduction

Reference

Android Power State Information Acquired

Extending monkeyrunner with Plugins - Jar File

Build an Android SDK

Android Build Environment Setup

Preface

Setup Your Ubuntu

Dumpsys Information - Android Open Source

A guide to Activity, Service, and Content Provider Testing by JUnit

Android / Linux Shell Command List

網站地圖

Android MonkeyRunner 和 Jythan - 從一個簡單的範例開始

Android 與 Linux 的執行命令

Android Log 訊息 - Bugreport

The log message Android is telling you - Bugreport

手動更新 Nexus 7 到最新版本

Android / Linux Shell Commands

Android Activity Manager 中文版

Upgrade your Nexus 7 (Wi-Fi) to 4.2 Manually

Android Activity Manager

Android MonkeyRunner with Jythan - A simple example to get start

Android Automation Test by Monkeyrunner

Android Automation Test for Stability by Monkey

Android Automation Test for Stability by Monkey 中文版

Android 自動化操作與測試 - monkeyrunner