summaryrefslogtreecommitdiff
path: root/docs/Android.markdown
diff options
context:
space:
mode:
authorJose Fonseca <jfonseca@vmware.com>2016-01-07 16:11:38 +0000
committerJose Fonseca <jfonseca@vmware.com>2016-01-07 16:12:30 +0000
commit71a33a59fe2c36c092effb35aceb2ba7930cf90b (patch)
tree1fa4f64c3a6af482fe57c5373709ef475a1dbdee /docs/Android.markdown
parent5e96ed318db1ba8037eb402724bc052240ac9e05 (diff)
docs: Rename Dalvik -> Android.
As it seems Dalvik use has been discontinued. [ci skip]
Diffstat (limited to 'docs/Android.markdown')
-rw-r--r--docs/Android.markdown45
1 files changed, 45 insertions, 0 deletions
diff --git a/docs/Android.markdown b/docs/Android.markdown
new file mode 100644
index 00000000..23064b83
--- /dev/null
+++ b/docs/Android.markdown
@@ -0,0 +1,45 @@
+# Tracing Java applications on Android #
+
+Android's Java virtual machine, runs as a system service (started at
+bootup by `init`) and Java applications are run by forks of the initial
+resident process. Thus, injecting apitrace's tracing library is different from
+other operating systems.
+
+The following discussion assumes that tracing library is copied to `/data`:
+
+ adb push /path/to/apitrace/libs/[arch]/egltrace.so /data
+
+
+## Tracing on Android 4.0 and newer ##
+
+Starting from Android 4.0 (Ice Cream Sandwich) release, the system supports
+running designated processes with wrappers, in which case a new Java VM is
+started with 'system()' library call for that process.
+
+Obtain the process name of the application to be traced (the one reported in
+`ps` output, such as `com.android.settings`), and set two system properties:
+
+ PROCNAME=com.android.settings
+ adb root
+ adb shell ln -s /data/data/apitrace.github.io.eglretrace/libgnustl.so /data/libgnustl.so
+ adb shell setprop wrap.$PROCNAME LD_PRELOAD="/data/libgnustl_shared.so:/data/egltrace.so"
+ adb shell setprop debug.apitrace.procname $PROCNAME
+
+(the former is read by Dalvik and specifies wrapping prefix, the latter is
+read by apitrace itself and used in case apitrace is preloaded into Java VM
+globally to specify which process should be traced). Elevating privileges
+via `adb root` is required to set the first property.
+
+If the `wrap.$PROCNAME` property name is longer than 31 characters [you'll need
+to truncate it](https://github.com/apitrace/apitrace/issues/296).
+
+Make sure the process is not loaded before starting to trace it, for example
+use `-S` flag to `am start`:
+
+ adb shell am start -S $PROCNAME
+
+Use `adb logcat \*:S apitrace` to examine apitrace debug output. Trace files
+are saved into `/data/data/$PROCNAME` directory by default:
+
+ adb pull /data/data/$PROCNAME/$PROCNAME.trace
+ adb shell rm /data/data/$PROCNAME/$PROCNAME.trace