Skip to content

Most visited

Recently visited


Tracer for OpenGL ES

Tracer is a tool for analyzing OpenGL for Embedded Systems (ES) code in your Android application. The tool allows you to capture OpenGL ES commands and frame by frame images to help you understand how your graphics commands are being executed.

Note: The Tracer tool requires a device running Android 4.1 (API Level 16) or higher.

Running Tracer

To run Tracer in Device Monitor:

  1. Start the Android Device Monitor tool.
  2. Activate the perspective for Tracer by choosing Window > Open Perspective...
  3. Select Tracer for OpenGL ES and click OK.

Generating a Trace

Tracer captures OpenGL ES command execution logs and can also capture progressive images of the frames generated by those commands to enable you to perform logical and visual analysis of your OpenGL ES code. The Tracer tool operates by connecting to a device running Android 4.1 (API Level 16) or higher that is running the application you want to analyze. The Tracer tool captures trace information while the application is running and saves it to a .gltrace file for analysis.

Figure 1. Trace capture dialog box.

To capture an OpenGL ES trace for an Android application:

  1. Connect the Android device using a USB cable and make sure it is enabled for debugging. For more information, see Using Hardware Devices.
  2. In the Device Monitor, activate the Tracer for OpenGL ES perspective.
  3. On the toolbar, click the trace capture button ().
  4. In the dialog box, select the Device to use for the trace.
  5. In the Application Package field, enter the full application package name containing the activity you want to trace, for example:
  6. In the Activity to launch field, enter the class name of the activity you want to trace, for example: OpenGLES20Complete

    Note: If you are tracing the default activity for the application, you can leave this field blank.

  7. Select the desired Data Collection Options.

    Note: If you want to capture progressive frame images for each drawing call, enable the Read back currently bound framebuffer on glDraw*() option. Be aware that using this option can result in large trace files.

  8. Enter a Destination File for the trace output.
  9. Click Trace to start the trace capture.
  10. On the connected device, exercise the functions of your application you want to trace.
  11. In the dialog box, Stop Tracing to complete the tracing run.

Analyzing a Trace

After you have generated a trace, you can load it for review and analysis.

To review a captured trace:

  1. In Device Monitor, activate the Tracer for OpenGL ES perspective.
  2. On the toolbar, click the trace load button ().
  3. After loading a trace, select a frame and review the OpenGL ES calls. Drawing commands are highlighted in blue.
This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience.
(Sep 2017 survey)