Who is this for?
This is an introductory topic for Android application and games developers new to Arm Performance Studio.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Capture a Streamline profile from a debuggable Android application
- Generate and inspect a Performance Advisor report
- Capture and analyze a frame with Frame Advisor and RenderDoc for Arm GPUs
- Use Mali Offline Compiler to estimate shader cost
Prerequisites
Before starting, you will need the following:
- An Android device.
- An debuggable build of your application built with OpenGL ES versions 2.0 to 3.2, or Vulkan versions 1.0 to 1.2.
- For OpenGL ES applications, your device must be running Android 10 or later.
- For Vulkan applications, your device must be running Android 9 or later.
- Arm Performance Studio installed. Follow the
Arm Performance Studio install guide
for instructions.
- Android SDK Platform tools installed for the Android Debug bridge (adb).
Summary
AI-assisted
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication.
Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll profile an Android graphics application on Arm Mali-based GPUs using Arm Performance Studio. After preparing a debuggable build, you’ll connect an Android device over adb, explore a provided Streamline sample to understand the available views, then capture a profile from your own application and generate a Performance Advisor report with the CLI. You’ll also perform frame-level inspection with Frame Advisor and RenderDoc for Arm GPUs, and use Mali Offline Compiler to estimate shader cost. By the end, you’ll understand how to progress from example data to capturing on-device profiles and interpreting reports that inform deeper frame and shader analysis.
Frequently asked questions
AI-assisted
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication.
Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Open the Performance Studio Hub and launch Streamline. In the Start view, choose Android (adb) as the device type and select your device from the list.
What should I check in my app build before profiling with Streamline?Build a debuggable version and include options that facilitate call stack unwinding by Streamline. For Unity, enable Development Build in Build settings.
What steps import the example Streamline capture?In Streamline, select File > Import, choose Import Streamline Sample Captures, then select the Android example and finish. The sample capture is added so you can open it and explore the views.
How do I generate a Performance Advisor report from a capture?Open a terminal, navigate to the capture location, and run streamline-cli with the -pa option on the .apc file (for example, “Android - GPU Bound Example.apc”). The capture is processed and a Performance Advisor report is produced.
Do I need Python for Performance Advisor?Yes. Performance Advisor uses a Python script to connect to your device and requires Python 3.8 or later.