Lines Matching refs:Android

1 # Android application profiling
3 This section shows how to profile an Android application.
6 Profiling an Android application involves three steps:
7 1. Prepare an Android application.
14 - [Android application profiling](#android-application-profiling)
16   - [Prepare an Android application](#prepare-an-android-application)
21   - [Report in Android Studio](#report-in-android-studio)
28 ## Prepare an Android application
35 For the debug build type, Android studio sets android::debuggable="true" in AndroidManifest.xml,
41 For the release build type, Android studio sets android::debuggable="false" in AndroidManifest.xml,
47 If you are on Android >= Q, you can add profileableFromShell flag in AndroidManifest.xml, this makes
59 If you are on Android >= O, we can use [wrap.sh](https://developer.android.com/ndk/guides/wrap-scri…
101 Android studio strips symbol table and debug info of native libraries in the apk. So the profiling
104 be the path of your Android Studio project.
109 On Android >= P, simpleperf supports profiling Java code, no matter whether it is executed by
112 On Android O, simpleperf supports profiling Java code which is compiled into native instructions,
116 On Android N, simpleperf supports profiling Java code that is compiled into native instructions.
119 On Android <= M, simpleperf doesn't support profiling Java code.
128 # Open SimpleperfExamplesWithNative project with Android studio, and build this project
139 We can use [app-profiler.py](scripts_reference.md#app_profilerpy) to profile Android applications.
145 # Android >= P.
247 ## Report in Android Studio
250 Android Studio cpu profiler. The conversion can be done either on device or on host. If you have
255 # Then open perf.trace in Android Studio to show it.