diff options
Diffstat (limited to 'docs/html/guide/developing/tools')
| -rw-r--r-- | docs/html/guide/developing/tools/adb.jd | 6 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adt.jd | 5 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/android.jd | 29 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/emulator.jd | 455 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/index.jd | 4 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/monkeyrunner_concepts.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/proguard.jd | 2 |
7 files changed, 269 insertions, 234 deletions
diff --git a/docs/html/guide/developing/tools/adb.jd b/docs/html/guide/developing/tools/adb.jd index d32cf66..50c7236 100644 --- a/docs/html/guide/developing/tools/adb.jd +++ b/docs/html/guide/developing/tools/adb.jd @@ -546,12 +546,12 @@ of each message, given as <code><priority>/<tag></code>. </p> <p>Log messages contain a number of metadata fields, in addition to the tag and priority. You can modify the output format for messages so that they display a specific metadata field. To do so, you use the <code>-v</code> option and specify one of the supported output formats listed below. </p> <ul> - <li><code>brief</code> — Display priority/tag and PID of originating process (the default format).</li> + <li><code>brief</code> — Display priority/tag and the PID of process issuing the message (the default format).</li> <li><code>process</code> — Display PID only.</li> <li><code>tag</code> — Display the priority/tag only. </li> - <li><code>thread</code> — Display process:thread and priority/tag only. </li> <li><code>raw</code> — Display the raw log message, with no other metadata fields.</li> - <li><code>time</code> — Display the date, invocation time, priority/tag, and PID of the originating process.</li> + <li><code>time</code> — Display the date, invocation time, priority/tag, and PID of the process issuing the message.</li> + <li><code>threadtime</code> — Display the date, invocation time, priority, tag, and the PID and TID of the thread issuing the message.</li> <li><code>long</code> — Display all metadata fields and separate messages with a blank lines.</li> </ul> diff --git a/docs/html/guide/developing/tools/adt.jd b/docs/html/guide/developing/tools/adt.jd index e48a5ae..d473e85 100644 --- a/docs/html/guide/developing/tools/adt.jd +++ b/docs/html/guide/developing/tools/adt.jd @@ -102,9 +102,8 @@ Project site.</p> (<strong>Window > Open Perspective > Traceview</strong>). </li> <li><a href="{@docRoot}guide/developing/tools/android.html">android</a>: Provides access to - the Android SDK and AVD Manager. Other <code>android</code> features such as creating or - updating projects (application and library) are integrated throughout the Eclipse IDE - (<strong>Window > Android SDK and AVD Manager</strong>). </li> + the Android SDK Manager and AVD Manager. Other <code>android</code> features such as creating or + updating projects (application and library) are integrated throughout the Eclipse IDE. </li> <li><a href="{@docRoot}guide/developing/debugging/debugging-ui.html#HierarchyViewer">Hierarchy Viewer</a>: Allows you to visualize your application's view hierarchy to find inefficiencies diff --git a/docs/html/guide/developing/tools/android.jd b/docs/html/guide/developing/tools/android.jd index a67012f..295a720 100644 --- a/docs/html/guide/developing/tools/android.jd +++ b/docs/html/guide/developing/tools/android.jd @@ -15,9 +15,16 @@ Line</a>.</li> the Command Line</a>.</li> <li>Update your Android SDK with new platforms, add-ons, and documentation. See <a href= - "{@docRoot}sdk/adding-components.html">Adding SDK Components</a>.</li> + "{@docRoot}sdk/adding-components.html">Adding SDK Packages</a>.</li> </ul>If you are using Eclipse, the <code>android</code> tool's features are integrated into ADT, so you should not need to use this tool directly. + + <p class="note"><strong>Note:</strong> The documentation of options below is not exhaustive +and may be out of date. For the most current list of options, execute <code>android +--help</code>.</p> + + + <h2>Syntax</h2> <pre>android [global options] action [action options]</pre> @@ -52,6 +59,26 @@ Line</a>.</li> </tr> <tr> + <td rowspan="6"><code>avd</code></td> + + <td>None</td> + + <td>Launch the AVD Manager</td> + + <td></td> + </tr> + + <tr> + <td rowspan="6"><code>sdk</code></td> + + <td>None</td> + + <td>Launch the Android SDK Manager</td> + + <td></td> + </tr> + + <tr> <td rowspan="6"><code>create avd</code></td> <td><code>-n <name></code></td> diff --git a/docs/html/guide/developing/tools/emulator.jd b/docs/html/guide/developing/tools/emulator.jd index 5151ec1..21d4263 100644 --- a/docs/html/guide/developing/tools/emulator.jd +++ b/docs/html/guide/developing/tools/emulator.jd @@ -8,8 +8,8 @@ parent.link=index.html <h2>In this document</h2> <ol> - <li><a href="#startup-options">Emulator Startup Options</a></li> - <li><a href="#KeyMapping">Emulator Keyboard Mapping</a></li> + <li><a href="#KeyMapping">Keyboard Commands</a></li> + <li><a href="#startup-options">Command Line Parameters</a></li> </ol> <h2>See also</h2> @@ -22,30 +22,123 @@ parent.link=index.html </div> -<p>The Android SDK includes a mobile device emulator — a virtual mobile device +<p>The Android SDK includes a mobile device emulator — a virtual mobile device that runs on your computer. The emulator lets you develop and test Android applications without using a physical device.</p> -<p>When the emulator is running, you can interact with the emulated mobile -device just as you would an actual mobile device, except that you use your mouse -pointer to "touch" the touchscreen and can use some keyboard keys to -invoke certain keys on the device. </p> - -<p>This document is a reference to the available command line options and the keyboard mapping to device keys. -For a complete guide to using the Android Emulator, see +<p>This document is a reference to the available command line options and the keyboard mapping to +device keys. +For a complete guide to using the Android Emulator, see <a href="{@docRoot}guide/developing/devices/emulator.html">Using the Android Emulator</a>. -<h2 id="startup-options">Emulator Startup Options</h2> +<h2 id="KeyMapping">Keyboard Commands</h2> -<p>The emulator supports a variety of options that you can specify -when launching the emulator, to control its appearance or behavior. -Here's the command-line usage for launching the emulator with options: </p> +<p>Table 1 summarizes the mappings between the emulator keys and the keys of your keyboard.</p> + +<p class="table-caption"><strong>Table 1.</strong> Emulator keyboard mapping</p> +<table border="0" style="clear:left;"> + <tr> + <th>Emulated Device Key </th> + <th>Keyboard Key </th> + </tr> + <tr> + <td>Home</td> + <td>HOME</td> + </tr> + <tr> + <td>Menu (left softkey)</td> + <td>F2 <em>or</em> Page-up button</td> + </tr> + <tr> + <td>Star (right softkey)</td> + <td>Shift-F2 <em>or </em>Page Down</td> + </tr> + <tr> + <td>Back</td> + <td>ESC</td> + </tr> + <tr> + <td>Call/dial button </td> + <td>F3</td> + </tr> + <tr> + <td>Hangup/end call button</td> + <td>F4</td> + </tr> + <tr> + <td>Search</td> + <td>F5 </td> + </tr> + <tr> + <td>Power button</td> + <td>F7 </td> + </tr> + <tr> + <td>Audio volume up button</td> + <td>KEYPAD_PLUS, Ctrl-F5</td> + </tr> + + <tr> + <td>Audio volume down button</td> + <td>KEYPAD_MINUS, Ctrl-F6</td> + </tr> + <tr> + <td>Camera button</td> + <td>Ctrl-KEYPAD_5, Ctrl-F3</td> + </tr> + <tr> + <td>Switch to previous layout orientation (for example, portrait, landscape)</td> + <td>KEYPAD_7, Ctrl-F11</td> + </tr> + <tr> + <td>Switch to next layout orientation (for example, portrait, landscape)</td> + <td>KEYPAD_9, Ctrl-F12</td> + </tr> + <tr> + <td>Toggle cell networking on/off</td> + <td>F8</td> + </tr> + <tr> + <td>Toggle code profiling</td> + <td>F9 (only with <code>-trace</code> startup option)</td> + </tr> + <tr> + <td>Toggle fullscreen mode</td> + <td>Alt-Enter</td> + </tr> + <tr> + <td>Toggle trackball mode</td> + <td>F6</td> + </tr> + <tr> + <td>Enter trackball mode temporarily (while key is pressed)</td> + <td>Delete</td> + </tr> + <tr> + <td>DPad left/up/right/down</td> + <td>KEYPAD_4/8/6/2</td> + </tr> + <tr> + <td>DPad center click</td> + <td>KEYPAD_5</td> + </tr> + <tr> + <td>Onion alpha increase/decrease</td> + <td>KEYPAD_MULTIPLY(*) / KEYPAD_DIVIDE(/)</td> + </tr> +</table> -<pre>emulator -avd <avd_name> [-<option> [<value>]] ... [-<qemu args>]</pre> -<p class="table-caption"><strong>Table 1.</strong>Emulator startup options</p> +<h2 id="startup-options">Command Line Parameters</h2> +<p>The emulator supports a variety of options that you can specify +when launching the emulator, to control its appearance or behavior. +Here's the command-line syntax of the options available to the {@code emulator} program:</p> + +<pre>emulator -avd <avd_name> [-<option> [<value>]] ... [-<qemu args>]</pre> + +<p class="table-caption"><strong>Table 2.</strong> Emulator command line parameters</p> <table> <tr> <th width="10%" >Category</th> @@ -55,106 +148,55 @@ Here's the command-line usage for launching the emulator with options: </p> </tr> <tr> - <td rowspan="9">Help</td> - <td><code>-help</code></td> - <td>Print a list of all emulator options.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-all</code></td> - <td>Print help for all startup options.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-<option></code></td> - <td>Print help for a specific startup option.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-debug-tags</code></td> - <td>Print a list of all tags for <code>-debug <tags></code>.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-disk-images</code></td> - <td>Print help for using emulator disk images.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-environment</code></td> - <td>Print help for emulator environment variables.</td> - <td> </td> -</tr><tr> - <td><code>-help-keys</code></td> - <td>Print the current mapping of keys.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-keyset-file</code></td> - <td>Print help for defining a custom key mappings file.</td> - <td> </td> -</tr> -<tr> - <td><code>-help-virtual-device</code></td> - <td>Print help for Android Virtual Device usage.</td> - <td> </td> -</tr> -<tr> <td>AVD</td> <td><code>-avd <avd_name></code> or <br> <code>@<avd_name></code></td> <td><strong>Required</strong>. Specifies the AVD to load for this emulator instance.</td> <td>You must create an AVD configuration before launching the emulator. For - information, see <a href="{@docRoot}guide/developing/devices/managing-avds.html#createavd"> - Managing AVDs with AVD Manager</a>.</td> + information, see <a href="{@docRoot}guide/developing/devices/managing-avds.html">Managing + AVDs with AVD Manager</a>.</td> <tr> <td rowspan="7">Disk Images</td> <td><code>-cache <filepath></code></td> <td>Use <filepath> as the working cache partition image. </td> - <td>Optionally, you can specify a path relative to the current working directory. + <td>An absolute or relative path to the current working directory. If no cache file is specified, the emulator's default behavior is to use a temporary file instead. <p>For more information on disk images, use <code>-help-disk-images</code>.</p> </td></tr> <tr> <td><code>-data <filepath></code></td> - <td>Use <filepath> as the working user-data disk image. </td> - <td>Optionally, you can specify a path relative to the current working directory. - If <code>-data</code> is not used, the emulator looks for a file named "userdata-qemu.img" - in the storage area of the AVD being used (see <code>-avd</code>). + <td>Use {@code <filepath>} as the working user-data disk image. </td> + <td>Optionally, you can specify a path relative to the current working directory. + If <code>-data</code> is not used, the emulator looks for a file named {@code userdata-qemu.img} + in the storage area of the AVD being used (see <code>-avd</code>). </td></tr> <!-- <tr> <td><code>-datadir <dir></code></td> <td>Search for the user-data disk image specified in <code>-data</code> in <dir></td> - <td><code><dir></code> is a path relative to the current working directory. + <td><code><dir></code> is a path relative to the current working directory. -<p>If you do not specify <code>-datadir</code>, the emulator looks for the user-data image -in the storage area of the AVD being used (see <code>-avd</code>)</p><p>For more information +<p>If you do not specify <code>-datadir</code>, the emulator looks for the user-data image +in the storage area of the AVD being used (see <code>-avd</code>)</p><p>For more information on disk images, use <code>-help-disk-images</code>.</p> </td></tr> --> -<!-- +<!-- <tr> <td><code>-image <filepath></code></td> <td>Use <filepath> as the system image.</td> - <td>Optionally, you can specify a path relative to the current working directory. + <td>Optionally, you can specify a path relative to the current working directory. Default is <system>/system.img.</td> </tr> --> <tr> <td><code>-initdata <filepath></code></td> - <td>When resetting the user-data image (through <code>-wipe-data</code>), copy the contents + <td>When resetting the user-data image (through <code>-wipe-data</code>), copy the contents of this file to the new user-data disk image. By default, the emulator copies the <code><system>/userdata.img</code>.</td> - <td>Optionally, you can specify a path relative to the current working directory. See also <code>-wipe-data</code>. <p>For more information on disk images, use <code>-help-disk-images</code>.</p></td> -</tr> -<!-- -<tr> - <td><code>-kernel <filepath></code></td> - <td>Use <filepath> as the emulated kernel.</td> - <td>Optionally, you can specify a path relative to the current working directory. </td> + <td>Optionally, you can specify a path relative to the current working directory. See also <code>-wipe-data</code>. + <p>For more information on disk images, use <code>-help-disk-images</code>.</p></td> </tr> ---> <tr> <td><code>-nocache</code></td> <td>Start the emulator without a cache partition.</td> @@ -163,8 +205,9 @@ on disk images, use <code>-help-disk-images</code>.</p> <tr> <td><code>-ramdisk <filepath></code></td> <td>Use <filepath> as the ramdisk image.</td> - <td>Default value is <code><system>/ramdisk.img</code>. - <p>Optionally, you can specify a path relative to the current working directory. For more information on disk images, use <code>-help-disk-images</code>.</p> + <td>Default value is <code><system>/ramdisk.img</code>. + <p>Optionally, you can specify a path relative to the current working directory. + For more information on disk images, use <code>-help-disk-images</code>.</p> </td> </tr> <tr> @@ -178,17 +221,17 @@ on disk images, use <code>-help-disk-images</code>.</p> <tr> <td><code>-system <dirpath></code></td> <td>Search for system, ramdisk and user data images in <dir>.</td> - <td><code><dir></code> is a directory path relative to the current + <td><code><dir></code> is a directory path relative to the current working directory.</td> </tr> --> <tr> <td><code>-wipe-data</code></td> - <td>Reset the current user-data disk image (that is, the file specified by <code>-datadir</code> and - <code>-data</code>, or the default file). The emulator deletes all data from the user data image file, - then copies the contents of the file at <code>-inidata</code> data to the image file before starting. + <td>Reset the current user-data disk image (that is, the file specified by <code>-datadir</code> and + <code>-data</code>, or the default file). The emulator deletes all data from the user data image file, + then copies the contents of the file at <code>-inidata</code> data to the image file before starting. </td> - <td>See also <code>-initdata</code>. + <td>See also <code>-initdata</code>. <p>For more information on disk images, use <code>-help-disk-images</code>.</p> </td> </tr> @@ -196,7 +239,7 @@ on disk images, use <code>-help-disk-images</code>.</p> <td rowspan="9">Debug</td> <td><code>-debug <tags></code></td> <td>Enable/disable debug messages for the specified debug tags.</td> - <td><code><tags></code> is a space/comma/column-separated list of debug component names. + <td><code><tags></code> is a space/comma/column-separated list of debug component names. Use <code>-help-debug-tags</code> to print a list of debug component names that you can use. </td> </tr> <tr> @@ -217,16 +260,16 @@ on disk images, use <code>-help-disk-images</code>.</p> <tr> <td><code>-shell</code></td> <td>Create a root shell console on the current terminal.</td> - <td>You can use this command even if the adb daemon in the emulated system is broken. + <td>You can use this command even if the adb daemon in the emulated system is broken. Pressing Ctrl-c from the shell stops the emulator instead of the shell.</td> </tr> <tr> <td><code>-shell-serial <device></code></td> - <td>Enable the root shell (as in <code>-shell</code> and specify the QEMU character + <td>Enable the root shell (as in <code>-shell</code> and specify the QEMU character device to use for communication with the shell.</td> - <td><device> must be a QEMU device type. See the documentation for '-serial <em>dev</em>' at - <a href="http://wiki.qemu.org/download/qemu-doc.html">wiki.qemu.org</a> - for more information.</p> + <td><device> must be a QEMU device type. See the documentation for '-serial <em>dev</em>' at + <a href="http://wiki.qemu.org/download/qemu-doc.html">http://wiki.qemu.org/download/qemu-doc.html</a> + for a list of device types. <p>Here are some examples: </p> <ul> @@ -250,11 +293,11 @@ on disk images, use <code>-help-disk-images</code>.</p> <tr> <td><code>-verbose</code></td> <td>Enable verbose output.</td> - <td>Equivalent to <code>-debug-init</code>. -<p>You can define the default verbose output options used by emulator instances in the Android environment variable -ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, specifying only the stem of each option: + <td>Equivalent to <code>-debug-init</code>. +<p>You can define the default verbose output options used by emulator instances in the Android environment variable +ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, specifying only the stem of each option: <code>-debug-<tags>.</code> </p> -<p>Here's an example showing ANDROID_VERBOSE defined with the <code>-debug-init</code> and <code>-debug-modem</code> options: +<p>Here's an example showing ANDROID_VERBOSE defined with the <code>-debug-init</code> and <code>-debug-modem</code> options: <p><code>ANDROID_VERBOSE=init,modem</code></p> <p>For more information about debug tags, use <code><-help-debug-tags></code>.</p> </td> @@ -316,8 +359,9 @@ ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, s <tr> <td><code>-netdelay <delay></code></td> <td>Set network latency emulation to <delay>.</td> - <td>Default value is <code>none</code>. See the table in <a href="#netdelay">Network Delay Emulation</a> for - supported <code><delay></code> values. </td> + <td>Default value is <code>none</code>. See the table in + <a href="{@docRoot}guide/developing/devices/emulator.html#netdelay">Network Delay Emulation</a> + for supported <code><delay></code> values. </td> </tr> <tr> <td><code>-netfast</code></td> @@ -326,18 +370,19 @@ ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, s <tr> <td><code>-netspeed <speed></code></td> <td>Set network speed emulation to <speed>.</td> - <td>Default value is <code>full</code>. See the table in <a href="#netspeed">Network Speed Emulation</a> for + <td>Default value is <code>full</code>. See the table in + <a href="{@docRoot}guide/developing/devices/emulator.html#netspeed">Network Speed Emulation</a> for supported <code><speed></code> values. </td> </tr> <tr> <td><code>-port <port></code></td> <td>Set the console port number for this emulator instance to <code><port></code>.</td> - <td>The console port number must be an even integer between 5554 and 5584, inclusive. <code><port></code>+1 + <td>The console port number must be an even integer between 5554 and 5584, inclusive. <code><port></code>+1 must also be free and will be reserved for ADB.</td> </tr> <tr> <td><code>-report-console <socket></code></td> - <td>Report the assigned console port for this emulator instance to a remote third party + <td>Report the assigned console port for this emulator instance to a remote third party before starting the emulation. </td> <td><code><socket></code> must use one of these formats: @@ -347,14 +392,14 @@ ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, s <p>Use <code>-help-report-console</code></p> to view more information about this topic. </td> </tr> <tr> - <td rowspan="8">System</td> + <td rowspan="10">System</td> <td><code>-cpu-delay <delay></code></td> <td>Slow down emulated CPU speed by <delay> </td> <td>Supported values for <delay> are integers between 0 and 1000. -<p>Note that the <delay> does not correlate to clock speed or other absolute metrics -— it simply represents an abstract, relative delay factor applied non-deterministically -in the emulator. Effective performance does not always +<p>Note that the <delay> does not correlate to clock speed or other absolute metrics +— it simply represents an abstract, relative delay factor applied non-deterministically +in the emulator. Effective performance does not always scale in direct relationship with <delay> values.</p> </td> </tr> @@ -362,9 +407,9 @@ scale in direct relationship with <delay> values.</p> <td><code>-gps <device></code></td> <td>Redirect NMEA GPS to character device.</td> <td>Use this command to emulate an NMEA-compatible GPS unit connected to - an external character device or socket. The format of <code><device></code> must be QEMU-specific - serial device specification. See the documentation for 'serial -dev' at - <a href="http://www.bellard.org/qemu/qemu-doc.html#SEC10">http://www.bellard.org/qemu/qemu-doc.html#SEC10</a>. + an external character device or socket. The format of <code><device></code> must be QEMU-specific + serial device specification. See the documentation for 'serial -dev' at + <a href="http://wiki.qemu.org/download/qemu-doc.html">http://wiki.qemu.org/download/qemu-doc.html</a>. </td> </tr> <tr> @@ -372,18 +417,37 @@ scale in direct relationship with <delay> values.</p> <td>Disable JNI checks in the Dalvik runtime.</td><td> </td></tr> <tr> <td><code>-qemu</code></td> - <td>Pass arguments to qemu.</td> - <td> </td></tr> + <td>Pass arguments to the qemu emulator software.</td> + <td><p class="caution"><strong>Important:</strong> When using this option, make sure it is the + <em>last option</em> specified, since all options after it are interpretted as qemu-specific + options.</p></td></tr> +<tr> + <td><code>-qemu -enable-kvm</code></td> + <td>Enable KVM acceleration of the emulator virtual machine.</td> + <td>This option is only effective when your system is set up to use + <a href="{@docRoot}guide/developing/devices/emulator.html#vm-linux">KVM-based VM acceleration</a>. + You can optionally specify a memory size ({@code -m <size>}) for the VM, which should match + your emulator's memory size:</p> + {@code -qemu -m 512 -enable-kvm}<br> + {@code -qemu -m 1024 -enable-kvm} + </td></tr> <tr> <td><code>-qemu -h</code></td> <td>Display qemu help.</td> <td></td></tr> <tr> + <td><code>-gpu on</code></td> + <td>Turn on graphics acceleration for the emulator.</td> + <td>This option is only available for emulators using a system image with API Level 15, revision 3 + and higher. For more information, see + <a href="{@docRoot}guide/developing/devices/emulator.html#accel-graphics">Using the Android + Emulator</a>.</td></tr> +<tr> <td><code>-radio <device></code></td> <td>Redirect radio mode to the specified character device.</td> - <td>The format of <code><device></code> must be QEMU-specific - serial device specification. See the documentation for 'serial -dev' at -<a href="http://www.bellard.org/qemu/qemu-doc.html#SEC10">http://www.bellard.org/qemu/qemu-doc.html#SEC10</a>. + <td>The format of <code><device></code> must be QEMU-specific + serial device specification. See the documentation for 'serial -dev' at +<a href="http://wiki.qemu.org/download/qemu-doc.html">http://wiki.qemu.org/download/qemu-doc.html</a>. </td> </tr> <tr> @@ -419,8 +483,8 @@ scale in direct relationship with <delay> values.</p> <tr> <td><code>-scale <scale></code></td> <td>Scale the emulator window. </td> - <td><code><scale></code> is a number between 0.1 and 3 that represents the desired scaling factor. You can - also specify scale as a DPI value if you add the suffix "dpi" to the scale value. A value of "auto" + <td><code><scale></code> is a number between 0.1 and 3 that represents the desired scaling factor. You can + also specify scale as a DPI value if you add the suffix "dpi" to the scale value. A value of "auto" tells the emulator to select the best window size.</td> </tr> <tr> @@ -434,7 +498,7 @@ scale in direct relationship with <delay> values.</p> <tr> <td><code>-keyset <file></code></td> <td>Use the specified keyset file instead of the default.</td> - <td>The keyset file defines the list of key bindings between the emulator and the host keyboard. + <td>The keyset file defines the list of key bindings between the emulator and the host keyboard. For more information, use <code>-help-keyset</code> to print information about this topic. </td> </tr> @@ -460,113 +524,58 @@ option. Using this option may yield unexpected and in some cases misleading results, since the density with which to render the skin may not be defined. AVDs let you associate each skin with a default density and override the default as needed. For more information, see <a -href="{@docRoot}guide/developing/devices/managing-avds.html#createavd"> -Managing Virtual Devices with AVD Manager</a>. +href="{@docRoot}guide/developing/devices/managing-avds.html">Managing Virtual Devices +with AVD Manager</a>. </td> </tr> <tr> <td><code>-skindir <dir></code></td> <td>This emulator option is deprecated. </td> - <td>See comments for <code>-skin</code>, above.</td></tr> -</table> - - - -<h2 id="KeyMapping">Emulator Keyboard Mapping</h2> - -<p>The table below summarizes the mappings between the emulator keys and and -the keys of your keyboard. </p> -<p class="table-caption"><strong>Table 2.</strong> Emulator keyboard mapping</p> -<table border="0" style="clear:left;"> - <tr> - <th>Emulated Device Key </th> - <th>Keyboard Key </th> - </tr> - <tr> - <td>Home</td> - <td>HOME</td> - </tr> - <tr> - <td>Menu (left softkey)</td> - <td>F2 <em>or</em> Page-up button</td> - </tr> - <tr> - <td>Star (right softkey)</td> - <td>Shift-F2 <em>or </em>Page Down</td> - </tr> - <tr> - <td>Back</td> - <td>ESC</td> - </tr> - <tr> - <td>Call/dial button </td> - <td>F3</td> - </tr> - <tr> - <td>Hangup/end call button</td> - <td>F4</td> - </tr> - <tr> - <td>Search</td> - <td>F5 </td> - </tr> - <tr> - <td>Power button</td> - <td>F7 </td> - </tr> - <tr> - <td>Audio volume up button</td> - <td>KEYPAD_PLUS, Ctrl-5</td> - </tr> - - <tr> - <td>Audio volume down button</td> - <td>KEYPAD_MINUS, Ctrl-F6</td> - </tr> - <tr> - <td>Camera button</td> - <td>Ctrl-KEYPAD_5, Ctrl-F3</td> - </tr> - <tr> - <td>Switch to previous layout orientation (for example, portrait, landscape)</td> - <td>KEYPAD_7, Ctrl-F11</td> - </tr> - <tr> - <td>Switch to next layout orientation (for example, portrait, landscape)</td> - <td>KEYPAD_9, Ctrl-F12</td> - </tr> - <tr> - <td>Toggle cell networking on/off</td> - <td>F8</td> - </tr> - <tr> - <td>Toggle code profiling</td> - <td>F9 (only with <code>-trace</code> startup option)</td> - </tr> - <tr> - <td>Toggle fullscreen mode</td> - <td>Alt-Enter</td> - </tr> - <tr> - <td>Toggle trackball mode</td> - <td>F6</td> - </tr> - <tr> - <td>Enter trackball mode temporarily (while key is pressed)</td> - <td>Delete</td> - </tr> - <tr> - <td>DPad left/up/right/down</td> - <td>KEYPAD_4/8/6/2</td> - </tr> - <tr> - <td>DPad center click</td> - <td>KEYPAD_5</td> - </tr> - <tr> - <td>Onion alpha increase/decrease</td> - <td>KEYPAD_MULTIPLY(*) / KEYPAD_DIVIDE(/)</td> - </tr> + <td>See comments for <code>-skin</code>, above.</td> +</tr> +<tr> + <td rowspan="9">Help</td> + <td><code>-help</code></td> + <td>Print a list of all emulator options.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-all</code></td> + <td>Print help for all startup options.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-<option></code></td> + <td>Print help for a specific startup option.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-debug-tags</code></td> + <td>Print a list of all tags for <code>-debug <tags></code>.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-disk-images</code></td> + <td>Print help for using emulator disk images.</td> + <td> </td> + </tr> +<tr> + <td><code>-help-environment</code></td> + <td>Print help for emulator environment variables.</td> + <td> </td>s +</tr><tr> + <td><code>-help-keys</code></td> + <td>Print the current mapping of keys.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-keyset-file</code></td> + <td>Print help for defining a custom key mappings file.</td> + <td> </td> +</tr> +<tr> + <td><code>-help-virtual-device</code></td> + <td>Print help for Android Virtual Device usage.</td> + <td> </td> +</tr> </table> - -<p>Note that, to use keypad keys, you must first disable NumLock on your development computer. </p> diff --git a/docs/html/guide/developing/tools/index.jd b/docs/html/guide/developing/tools/index.jd index 3d831f3..5e9f686 100644 --- a/docs/html/guide/developing/tools/index.jd +++ b/docs/html/guide/developing/tools/index.jd @@ -12,8 +12,8 @@ latest Android platform.</p> <h2 id="tools-sdk">SDK Tools</h2> <p>The SDK tools are installed with the SDK starter package and are periodically updated. The SDK tools are required if you are developing Android applications. The most important SDK tools -include the Android SDK and AVD Manager (<code>android</code>), the emulator -(<code>emulator</code>), and the Dalvik Debug Monitor Server +include the Android SDK Manager (<code>android sdk</code>), the AVD Manager (<code>android +avd</code>) the emulator (<code>emulator</code>), and the Dalvik Debug Monitor Server (<code>ddms</code>). A short summary of some frequently-used SDK tools is provided below.</p> <dl> diff --git a/docs/html/guide/developing/tools/monkeyrunner_concepts.jd b/docs/html/guide/developing/tools/monkeyrunner_concepts.jd index 499b610..346a0c6 100644 --- a/docs/html/guide/developing/tools/monkeyrunner_concepts.jd +++ b/docs/html/guide/developing/tools/monkeyrunner_concepts.jd @@ -236,7 +236,7 @@ Table 1 explains the flags and arguments. You can generate an API reference for monkeyrunner by running: </p> <pre> -monkeyrunner <format> help.py <outfile> +monkeyrunner help.py <format> <outfile> </pre> <p> The arguments are: diff --git a/docs/html/guide/developing/tools/proguard.jd b/docs/html/guide/developing/tools/proguard.jd index eca262a..ea8a1ea 100644 --- a/docs/html/guide/developing/tools/proguard.jd +++ b/docs/html/guide/developing/tools/proguard.jd @@ -39,7 +39,7 @@ parent.link=index.html sized <code>.apk</code> file that is more difficult to reverse engineer. Because ProGuard makes your application harder to reverse engineer, it is important that you use it when your application utilizes features that are sensitive to security like when you are - <a href="{@docRoot}guide/publishing/licensing.html">Licensing Your Applications</a>.</p> + <a href="{@docRoot}guide/market/licensing/index.html">Licensing Your Applications</a>.</p> <p>ProGuard is integrated into the Android build system, so you do not have to invoke it manually. ProGuard runs only when you build your application in release mode, so you do not |