diff --git a/docs/html/images/gltracer/dialog-trace.png b/docs/html/images/gltracer/dialog-trace.png new file mode 100644 index 0000000000000..86676235eb139 Binary files /dev/null and b/docs/html/images/gltracer/dialog-trace.png differ diff --git a/docs/html/images/gltracer/icon-capture.png b/docs/html/images/gltracer/icon-capture.png new file mode 100644 index 0000000000000..9cbdb3b7b1ced Binary files /dev/null and b/docs/html/images/gltracer/icon-capture.png differ diff --git a/docs/html/images/gltracer/icon-load-trace.png b/docs/html/images/gltracer/icon-load-trace.png new file mode 100644 index 0000000000000..f3957b8e3d0fd Binary files /dev/null and b/docs/html/images/gltracer/icon-load-trace.png differ diff --git a/docs/html/tools/help/gltracer.jd b/docs/html/tools/help/gltracer.jd new file mode 100644 index 0000000000000..35c405ef7a9b2 --- /dev/null +++ b/docs/html/tools/help/gltracer.jd @@ -0,0 +1,103 @@ +page.title=Tracer for OpenGL ES +@jd:body + +
+
+

In this document

+
    +
  1. Running Tracer
    2. +
  2. Generating a Trace
    3. +
  3. Analyzing a Trace
    4. +
+

See also

+
    +
  1. Tools
    2. +
+
+
+ +

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

+ +

Tracer can be run as part of the Eclipse Android Development Tools (ADT) plugin or as part of the +Device Monitor tool.

+ +

To run Tracer in Eclipse:

+ +
    +
  1. Start Eclipse and open a workspace that contains an Android project.
    2. +
  2. Activate the perspective for Tracer by choosing Window > Open Perspective > +Other...
    3. +
  3. Select Tracer for OpenGL ES and click OK.
    4. +
+ +

To run Tracer in Device Monitor:

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

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 {@code .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. +
  2. In Eclipse or Device Monitor, activate the Tracer for OpenGL ES +perspective.
    3. +
  3. On the toolbar, click the trace capture button ().
    4. +
  4. In the dialog box, select the Device to use for the trace.
    5. +
  5. In the Application Package field, enter the full application package name +containing the activity you want to trace, for example: {@code com.example.android.opengl}
    6. +
  6. In the Activity to launch field, enter the class name of the activity you +want to trace, for example: {@code OpenGLES20Complete} +

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

    +
    7. +
  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. +
  8. Enter a Destination File for the trace output.
    9. +
  9. Click Trace to start the trace capture.
    10. +
  10. On the connected device, exercise the functions of your application you want to trace.
    11. +
  11. In the dialog box, Stop Tracing to complete the tracing run.
    12. +
+ +

Analyzing a Trace

+ +

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

+ +

To review a captured trace:

+ +
    +
  1. In Eclipse or Device Monitor, activate the Tracer for OpenGL ES +perspective.
    2. +
  2. On the toolbar, click the trace load button ().
    3. +
  3. After loading a trace, select a frame and review the OpenGL ES calls. Drawing commands are +highlighted in blue.
    4. +
\ No newline at end of file diff --git a/docs/html/tools/help/monitor.jd b/docs/html/tools/help/monitor.jd new file mode 100644 index 0000000000000..8e2ea36ae25dd --- /dev/null +++ b/docs/html/tools/help/monitor.jd @@ -0,0 +1,24 @@ +page.title=Debug Monitor +@jd:body + +

Android Debug Monitor is a stand-alone tool that provides a graphical user interface for +several Android application debugging and analysis tools. The Monitor tool does not +require installation of a integrated development environment, such as Eclipse, and encapsulates the +following tools:

+ + + +

Usage

+ +

To start Debug Monitor, enter the following command from the SDK tools/ +directory:

+ 
monitor
+ +

Start an Android emulator or connect an Android device via USB cable, and connect the Debug +Monitor to the device by selecting it in the Devices window.

diff --git a/docs/html/tools/tools_toc.cs b/docs/html/tools/tools_toc.cs index 94bf8bc8e802b..c7cdded460f3d 100644 --- a/docs/html/tools/tools_toc.cs +++ b/docs/html/tools/tools_toc.cs @@ -130,6 +130,7 @@ class="en">Tools Help
  • ADT
  • android
  • bmgr +
  • Device Monitor
  • dmtracedump
  • Draw 9-Patch
  • Emulator
    • @@ -153,6 +154,7 @@ class="en">MonkeyRunner
  • ProGuard
    • +
  • Tracer for OpenGL ES
  • Traceview
  • zipalign