Difference between revisions of "Android Tools"

From eLinux.org
Jump to: navigation, search
(target-side tools: add reference to sqlite3 tool)
(Running adbd on non-Android systems)
 
(4 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
* make sure that adbd runs on the board. If it doesn't run, you might want to check the <tt>init.rc</tt> file.
 
* make sure that adbd runs on the board. If it doesn't run, you might want to check the <tt>init.rc</tt> file.
 
* make sure that the network connection between host and the board is working - test pinging both ways.
 
* make sure that the network connection between host and the board is working - test pinging both ways.
* on the host, type the following (and yes, you need to specify the board's IP address on the host):
+
* on the host, type the following (you need to specify the board's IP address on the host):
 
   ADBHOST=<target-ip> tools/adb kill-server
 
   ADBHOST=<target-ip> tools/adb kill-server
 
   ADBHOST=<target-ip> tools/adb shell
 
   ADBHOST=<target-ip> tools/adb shell
 
* you should now get a prompt on the board, you can exit the prompt if you want.
 
* you should now get a prompt on the board, you can exit the prompt if you want.
 
* <tt>tools/adb devices</tt> should now list the device.
 
* <tt>tools/adb devices</tt> should now list the device.
 +
 +
===== Running adbd on non-Android systems =====
 +
It is sometimes useful to use adbd on non-Android embedded Linux systems.  Here is a patch that can be applied to adb (source as of 2014-04-05) to change it to avoid "Android-isms" in the build.  Instructions are in a README.NONANDROID.TXT file.
 +
 +
[[File:0001-Add-support-for-non-Android-use-of-adbd.patch]]
 +
 +
This patch can be applied to your adb source by cd'ing to the directory /system/core/adb, applying the patch with:
 +
$ git am 0001-Add-support-for-non-Android-use-of-adbd.patch
  
 
==== aapt ====
 
==== aapt ====
Line 113: Line 121:
  
 
==== toolbox ====
 
==== toolbox ====
stop, start - commands to stop and start services on an Android system
+
toolbox is the equivalent of busybox on an Android system.  That is, it is a multi-function
 +
program that provides many difference commands from a single binary.
 +
this includes things like: ps, ls, top, stop, start - commands to stop and start services on an Android system
 +
 
 +
See [[Android toolbox]] for details about individual commands.
  
 
== other tools ==
 
== other tools ==
Line 127: Line 139:
 
You can get a binary busybox for Android [http://benno.id.au/blog/2007/11/14/android-busybox here]
 
You can get a binary busybox for Android [http://benno.id.au/blog/2007/11/14/android-busybox here]
 
The site includes instructions for easy installation on your device.
 
The site includes instructions for easy installation on your device.
 +
 +
If you're interested in including busybox into a platform build:
 +
* precompiled binaries [https://github.com/Gnurou/busybox-android here]
 +
* a [https://video.linux.com/videos/busybox-integration-on-android presentation] on how to build (or not) and integrate busybox into platform build (slides available [https://events.linuxfoundation.org/images/stories/pdf/lf_abs12_sun.pdf here]).
  
 
=== smem ===
 
=== smem ===

Latest revision as of 23:13, 7 April 2014

Here are some development tools useful for working with Android

Android SDK

host-side tools

adb

adb is the android debugger - it also doubles as file transfer agent. The setup consists of an adbd on the target in the /sbin directory. On the host two programs are run: the adb application (in the SDK's tools directory) and an adb server, started by the adb application.

For emulators, adb will usually run automagically.

For real boards - with debugging over USB, you might need to do work, as is documented here: http://developer.android.com/guide/developing/device.html#setting-up .

For real boards that do not have a USB connection but have Ethernet instead, you might need to do a few tricks.

  • make sure that adbd runs on the board. If it doesn't run, you might want to check the init.rc file.
  • make sure that the network connection between host and the board is working - test pinging both ways.
  • on the host, type the following (you need to specify the board's IP address on the host):
  ADBHOST=<target-ip> tools/adb kill-server
  ADBHOST=<target-ip> tools/adb shell
  • you should now get a prompt on the board, you can exit the prompt if you want.
  • tools/adb devices should now list the device.
Running adbd on non-Android systems

It is sometimes useful to use adbd on non-Android embedded Linux systems. Here is a patch that can be applied to adb (source as of 2014-04-05) to change it to avoid "Android-isms" in the build. Instructions are in a README.NONANDROID.TXT file.

File:0001-Add-support-for-non-Android-use-of-adbd.patch

This patch can be applied to your adb source by cd'ing to the directory /system/core/adb, applying the patch with:

$ git am 0001-Add-support-for-non-Android-use-of-adbd.patch

aapt

The Android Asset Packaging Tool is used to create, inspect and manage Android packages.

You can use this to see details about a package, it's resources, and xml information.

The Android developer page on aapt is somewhat meager.

See Android aapt for substantially more information.

ddms

The Dalvik Debug Monitor Server is a host-based tool which interacts with and Android target system and can show numerous bits of information, including the log, cpu and memory utilization, and lots of details about individual processes.

See the DDMS developer guide


Fastboot

Android Fastboot is a tool to boot and manipulate the partitions on an Android development phone.

Toolchains

Android provides pre-built toolchains (C/C++ compilers and linkers), but requires the installation of a java compiler (JDK) from an external source.

As of NDK version r5 (December 2010), the toolchains can now be used in standalone cross-compiler mode. See docs/STANDALONE-TOOLCHAIN.html in the NDK for information about this. Previously, the toolchains could be used within the build system, but it was difficult and error prone to compile native programs outside the Android build system with them.

Emulator

The emulator is a version of QEMU, which mimics the instruction set of an ARM processor, and the hardware that one might find on a mobile phone. The emulator runs on an x86 system, but executes an ARM linux kernel and programs. The flow of control is:

    • application ->
    • dalvik VM ->
    • C/C++ libraries ->
    • ARM linux kernel ->
    • emulated instructions and hardware (QEMU)->
    • C libraries->
    • x86 kernel ->
    • real hardware

traceview

target-side tools

am

Activity Manager - can be used to start applications at the command line, or send intents to running applications.

dumpstate

dumps the state of the system. It scans the /proc filesystem, and collects various system properties, and puts them in a single report, suitable for sending to someone for support or development help.

logcat

This is the user tool for accessing the Android system log. This is implemented at a special option in adb (I'm not sure what the difference is between "adb logcat" and "adb shell logcat")

You can find lots of information about logcat on the Android logger page, and at http://developer.android.com/guide/developing/tools/adb.html#logcat

monkey

procrank

procrank shows a listing of processes on the system, sorted by one of the memory utilization metrics. See Android Memory Usage#procrank

service

Can be used to send an individual service message.

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.

On one forum, I saw that you could switch between portrait and landscape with:

$ service call window 18 i32 1 # to set to landscape on the emulator
$ service call window 18 i32 0 # to set to portrait on the emulator

service list will show a list of different services that can be communicated with.

sqlite3

sqlite3 is a command-line database client program, for manipulating sqlite databases.

See http://www.higherpass.com/Android/Tutorials/Accessing-Data-With-Android-Cursors/ for a tutorial and some examples of using sqlite.

toolbox

toolbox is the equivalent of busybox on an Android system. That is, it is a multi-function program that provides many difference commands from a single binary. this includes things like: ps, ls, top, stop, start - commands to stop and start services on an Android system

See Android toolbox for details about individual commands.

other tools

agcc

bootchart

busybox

Android ships with a utility suite (called 'toolbox') that is not busybox.

You can get a binary busybox for Android here The site includes instructions for easy installation on your device.

If you're interested in including busybox into a platform build:

  • precompiled binaries here
  • a presentation on how to build (or not) and integrate busybox into platform build (slides available here).

smem

  • smem - smem is a tools for analyzing the memory usage on a system

strace

Eclipse

The officially supported integrated development environment (IDE) is Eclipse (currently 3.4 or 3.5) using the Android Development Tools (ADT) Plugin, though developers may use any text editor to edit Java and XML files then use command line tools (Java Development Kit and Apache Ant are required) to create, build and debug Android applications as well as control attached Android devices (e.g., triggering a reboot, installing software package(s) remotely).

Hardware

Serial Cable for G1

You can build a serial cable to use with the G1, which is helpful to see kernel boot messages on the serial console.

See http://www.instructables.com/id/Android_G1_Serial_Cable

Back to Android Portal