diff options
Diffstat (limited to 'docs/html/guide/developing')
| -rw-r--r-- | docs/html/guide/developing/debugging/index.jd | 37 | ||||
| -rw-r--r-- | docs/html/guide/developing/device.jd | 3 | ||||
| -rw-r--r-- | docs/html/guide/developing/index.jd | 14 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/etc1tool.jd | 68 |
4 files changed, 99 insertions, 23 deletions
diff --git a/docs/html/guide/developing/debugging/index.jd b/docs/html/guide/developing/debugging/index.jd index 1f1a4ca..0ad1a08 100644 --- a/docs/html/guide/developing/debugging/index.jd +++ b/docs/html/guide/developing/debugging/index.jd @@ -1,4 +1,4 @@ -page.title=Debugging +page.title=Debugging @jd:body @@ -10,7 +10,7 @@ page.title=Debugging <li><a href="#stack">Debugging Environment</a></li> <li><a href="#addltools">Additional Debugging Tools</a></li> - + <li><a href="#tips">Debugging Tips</a></li> </ol> </div> @@ -50,7 +50,7 @@ page.title=Debugging <dd>The Dalvik VM (Virtual Machine) supports the JDWP protocol to allow debuggers to attach to a VM. Each application runs in a VM and exposes a unique port that you can attach a debugger to - via DDMS. If you want to debug multiple applications, attaching to each port might become + via DDMS. If you want to debug multiple applications, attaching to each port might become tedious, so DDMS provides a port forwarding feature that can forward a specific VM's debugging port to port 8700. You can switch freely from application to application by highlighting it in the Devices tab of DDMS. DDMS forwards the appropriate port to port 8700. Most modern Java IDEs include a JDWP debugger, @@ -109,11 +109,11 @@ page.title=Debugging that provide useful information such as CPU usage and frame rate. You can also transfer the application to a hardware device.</dd> </dl> - - - <h2 id="tips">Debugging Tips</h2> - -<p>While debugging, keep these helpful tips in mind to help you figure out common problems with your + + + <h2 id="tips">Debugging Tips</h2> + +<p>While debugging, keep these helpful tips in mind to help you figure out common problems with your applications:</p> <dl> @@ -131,14 +131,14 @@ Debugging with the Dev Tools App</a>. </dd> <dt><strong>Get application and system state information from the emulator</strong></dt> -<dd>You can access dumpstate information from the <code>adb shell</code> commands. See +<dd>You can access dumpstate information from the <code>adb shell</code> commands. See <a href="{@docRoot}guide/developing/tools/adb.html#dumpsys">dumpsys and dumpstate</a> on the adb topic page.</dd> <dt><strong>Get wireless connectivity information</strong></dt> -<dd>You can get information about wireless connectivity using DDMS. +<dd>You can get information about wireless connectivity using DDMS. From the <strong>Device</strong> menu, select <strong>Dump radio state</strong>.</dd> @@ -165,6 +165,16 @@ logcat -b radio <dt><strong>Use debugging helper classes</strong></dt> <dd>Android provides debug helper classes such as {@link android.util.Log util.Log} and {@link android.os.Debug} for your convenience. </dd> + +<dt><strong>Garbage collection</strong></dt> +<dd> +The debugger and garbage collector are currently loosely integrated. The VM guarantees that any +object the debugger is aware of is not garbage collected until after the debugger disconnects. +This can result in a buildup of objects over time while the debugger is connected. For example, +if the debugger sees a running thread, the associated {@link java.lang.Thread} object is not +garbage collected even after the thread terminates. +</dd> + </dl> <p>See the <a href="{@docRoot}resources/faq/troubleshooting.html">Troubleshooting</a> document @@ -176,10 +186,3 @@ for answers to some common developing and debugging issues.</p> - - - - - - - diff --git a/docs/html/guide/developing/device.jd b/docs/html/guide/developing/device.jd index cb5a0b6..bde170e 100644 --- a/docs/html/guide/developing/device.jd +++ b/docs/html/guide/developing/device.jd @@ -142,6 +142,9 @@ USB device support on Linux. The USB Vendor ID is the value given to the <td>Huawei</td> <td><code>12d1</code></td></tr> <tr> + <td>K-Touch</td> + <td><code>24e3</code></td></tr> + <tr> <td>Kyocera</td> <td><code>0482</code></td></tr> <tr> diff --git a/docs/html/guide/developing/index.jd b/docs/html/guide/developing/index.jd index 3d7e353..722c75a 100644 --- a/docs/html/guide/developing/index.jd +++ b/docs/html/guide/developing/index.jd @@ -98,20 +98,22 @@ information. <dt>Jarsigner (or similar signing tool)</dt> - <dd>To sign your .apk file with a private key generated by keytool. Jarsigner is part of the + <dd>To sign your .apk file with a private key generated by Keytool. Jarsigner is part of the JDK.</dd> </dl> - <p>If you are using Eclipse and ADT, tools such as <code>adb</code> and the <code>android</code> - are called by Eclipse and ADT under the hood or similar functionality is provided within Eclipse. - You need to be familiar with <code>adb</code>, however, because certain functions are not accessible from - Eclipse, such as the <code>adb</code> shell commands. You might also need to call Keytool and Jarsigner to + <p>If you are using Eclipse and ADT, tools such as <code>adb</code> and <code>android</code> + are automatically called by Eclipse and ADT so you don't have to manually invoke these tools. + You need to be familiar with <code>adb</code>, however, because certain functions are not +accessible from + Eclipse, such as the <code>adb</code> shell commands. You might also need to call Keytool and +Jarsigner to sign your applications, but you can set up Eclipse to do this automatically as well.</p> <p>For more information on the tools provided with the Android SDK, see the <a href="{@docRoot}guide/developing/tools/index.html">Tools</a> section of the documentation.</p> -<h2 id="ThirdParty">Third-Party Development Tools</h2> +<h2 id="ThirdParty">Other Third-Party Development Tools</h2> <p> The tools described in this section are not developed by the Android SDK team. The Android Dev Guide does not provide documentation for these tools. Please refer to the linked documents in each diff --git a/docs/html/guide/developing/tools/etc1tool.jd b/docs/html/guide/developing/tools/etc1tool.jd new file mode 100644 index 0000000..a7f76f5 --- /dev/null +++ b/docs/html/guide/developing/tools/etc1tool.jd @@ -0,0 +1,68 @@ +page.title=etc1tool +parent.title=Tools +parent.link=index.html +@jd:body + + + <p><code>etc1tool</code> is a command line utility that lets you encode PNG + images to the ETC1 compression standard and decode ETC1 compressed images back to PNG.</p> + + <p>The usage for <code>etc1tool</code> is:</p> +<pre>etc1tool infile [--help | --encode | --encodeNoHeader | --decode] [--showDifference +diff-file] [-o outfile]</pre> + + <table> + <tr> + <th>Option</th> + + <th>Description</th> + </tr> + + <tr> + <td><code>infile</code></td> + + <td>The input file to compress</td> + </tr> + + <tr> + <td><code>--help</code></td> + + <td>Print usage information</td> + </tr> + + <tr> + <td><code>--encode</code></td> + + <td>Create an ETC1 file from a PNG file. + This is the default mode for the tool if nothing is specified.</td> + </tr> + + <tr> + <td><code>--encodeNoHeader</code></td> + + <td>Create a raw ETC1 data file (without a header) from a PNG file.</td> + </tr> + + <tr> + <td><code>--decode</code></td> + + <td>Create a PNG file from an ETC1 file</td> + </tr> + + <tr> + <td><code>--showDifference <em>diff-file</em></code></td> + + <td>Write the difference between the original and encoded image to + <code><em>diff-file</em></code> (only valid when encoding).</td> + </tr> + + <tr> + <td><code>-o <em>outfile</em></code></td> + + <td>Specify the name of the output file. + If <code><em>outfile</em></code> is not specified, the output file is constructed + from the input filename with the appropriate suffix (<code>.pkm</code> or <code>.png</code>). + </td> + </tr> + + </table>
\ No newline at end of file |