Android tracing, monitoring and debugging

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

This article provides useful information to start using Android^™ tracing, monitoring and debugging environments.

1. Specific Linux trace and debug tools[edit source]

In Android^™ various Linux trace and debug tools are available. To get the global picture you can refer to Linux tracing, monitoring and debugging page.

2. Android tools[edit source]

2.1. Application debugging[edit source]

To debug your Android application you can use Android Studio to do so. Please read the official documentation about Android Studio^[1].

2.2. adeb[edit source]

To go deep in specific kernel analysis you can have a look to the ADEB page that explain how to put BCC tools in place.

This consits in putting a Debian distribution into the Android system itself to execute more debug commands.

2.3. ftrace[edit source]

ftrace is a debugging tool for understanding what is going on inside the Linux kernel. Please see the official documentation^[2].

2.4. logcat[edit source]

logcat is a tool to access Android log informations^[3].

2.5. perfetto[edit source]

To analyse system performance Android provide the tool perfetto.

To install you can refer to the AOSP documentation^[4].

To use it have a look to the perfetto documentation^[5].

3. References[edit source]

[1] ttps://developer.android.com/studio/debug

[2] ttps://source.android.com/devices/tech/debug/ftrace#atrace

[3] ttps://developer.android.com/studio/command-line/logcat

[4] ttps://android.googlesource.com/platform/external/perfetto/+/HEAD/docs/build-instructions.md

[5] ttps://developer.android.com/studio/command-line/perfetto

[1]

[2]

[3]

[4]

[5]