From 50e990c64fa23ce94efa76b9e72df7f8ec3cee6a Mon Sep 17 00:00:00 2001 From: Scott Main Date: Thu, 21 Jun 2012 17:14:39 -0700 Subject: Massive clobber of all HTML files in developer docs for new site design Change-Id: Idc55a0b368c1d2c1e7d4999601b739dd57f08eb3 --- docs/html/tools/debugging/debugging-devtools.jd | 77 +++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 docs/html/tools/debugging/debugging-devtools.jd (limited to 'docs/html/tools/debugging/debugging-devtools.jd') diff --git a/docs/html/tools/debugging/debugging-devtools.jd b/docs/html/tools/debugging/debugging-devtools.jd new file mode 100644 index 0000000..3a05120 --- /dev/null +++ b/docs/html/tools/debugging/debugging-devtools.jd @@ -0,0 +1,77 @@ +page.title=Using the Dev Tools App +parent.title=Debugging +parent.link=index.html +@jd:body + +

The Dev Tools application is installed by default on all system images included with the SDK, + so you can use it with the Android Emulator. With the Dev Tools application, you can enable a + number of settings on your device that will make it easier to test and debug your applications.

+ +

The Dev Tools application relies on a number of permissions that are not available for + third party applications. If you'd like to install the Dev Tools application + on a real development device, you'd have to build a system image for that device and sign + the Dev Tools application with the same key as used for the system image.

+ +

To get started, launch the Dev Tools application and select Development Settings. This will + open the Development Settings page with the following options (among others):

+ +
+
Debug app
+ +
+ Lets you select the application to debug. You do not need to set this to attach a debugger, + but setting this value has two effects: + +
    +
  • It will prevent Android from throwing an error if you pause on a breakpoint for a long + time while debugging.
    • + +
  • It will enable you to select the Wait for Debugger option to pause application + startup until your debugger attaches (described next).
    • +
+
+ +
Wait for debugger
+ +
Blocks the selected application from loading until a debugger attaches. This way you can + set a breakpoint in {@link android.app.Activity#onCreate onCreate()}, + which is important to debug the startup process of an Activity. + When you change this option, any currently running instances of the selected application will + be killed. In order to check this box, you must have selected a debug application as described + in the previous option. You can do the same thing by adding {@link + android.os.Debug#waitForDebugger()} to your code.
+ +
Show screen updates
+ +
Flashes a momentary pink rectangle on any screen sections that are being redrawn. This is + very useful for discovering unnecessary screen drawing.
+ +
Immediately destroy activities
+ +
Tells the system to destroy an activity as soon as it is stopped (as if Android had to + reclaim memory).  This is very useful for testing the {@link + android.app.Activity#onSaveInstanceState} / {@link + android.app.Activity#onCreate(android.os.Bundle)} code path, which would otherwise be difficult + to force. Choosing this option will probably reveal a number of problems in your application + due to not saving state. For more information about saving an activity's state, see the + Activities +document.
+ +
Show CPU usage
+ +
Displays CPU meters at the top of the screen, showing how much the CPU is being used. The + top red bar shows overall CPU usage, and the green bar underneath it shows the CPU time spent + in compositing the screen. +

Note: You cannot turn this feature off once it is on, without + restarting the emulator.

+ +
Show background
+ +
Displays a background pattern when no activity screens are visible. This typically does not + happen, but can happen during debugging.
+
+ +

These settings will be remembered across emulator restarts.

+ + + -- cgit v1.1