diff options
Diffstat (limited to 'docs/html/tools/help')
| -rw-r--r-- | docs/html/tools/help/adb.jd | 1 | ||||
| -rw-r--r-- | docs/html/tools/help/android.jd | 25 | ||||
| -rw-r--r-- | docs/html/tools/help/draw9patch.jd | 40 | ||||
| -rw-r--r-- | docs/html/tools/help/hierarchy-viewer.jd | 29 | ||||
| -rw-r--r-- | docs/html/tools/help/index.jd | 24 | ||||
| -rw-r--r-- | docs/html/tools/help/lint.jd | 27 | ||||
| -rw-r--r-- | docs/html/tools/help/proguard.jd | 145 | ||||
| -rw-r--r-- | docs/html/tools/help/sdk-manager.jd | 2 | ||||
| -rw-r--r-- | docs/html/tools/help/systrace.jd | 3 |
9 files changed, 185 insertions, 111 deletions
diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index e2dd196..41c6686 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -962,7 +962,6 @@ install [options] <PATH> </code></td> <td>Installs a package (specified by {@code <PATH>}) to the system. <p>Options: <ul> - <li>{@code -l}: Install the package with forward lock. <li>{@code -r}: Reinstall an exisiting app, keeping its data. <li>{@code -t}: Allow test APKs to be installed. <li>{@code -i <INSTALLER_PACKAGE_NAME>}: Specify the installer package name. diff --git a/docs/html/tools/help/android.jd b/docs/html/tools/help/android.jd index 19891e8..0d7d2aa 100644 --- a/docs/html/tools/help/android.jd +++ b/docs/html/tools/help/android.jd @@ -6,25 +6,26 @@ parent.link=index.html <p>{@code android} is an important development tool that lets you:</p> <ul> - <li>Create, delete, and view Android Virtual Devices (AVDs). See <a href= - "{@docRoot}tools/devices/managing-avds-cmdline.html">Managing AVDs from the Command -Line</a>.</li> + <li>Create, delete, and view Android Virtual Devices (AVDs). See <a href= + "{@docRoot}tools/devices/managing-avds-cmdline.html">Managing AVDs from the Command Line</a>.</li> - <li>Create and update Android projects. See <a href= + <li>Create and update Android projects. See <a href= "{@docRoot}tools/projects/projects-cmdline.html">Managing Projects from the Command Line</a>.</li> - <li>Update your Android SDK with new platforms, add-ons, and documentation. See <a href= - "{@docRoot}sdk/exploring.html">Exploring the SDK</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. - + <li>Update your Android SDK with new platforms, add-ons, and documentation. See <a href= + "{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>.</li> + </ul> + +<p>If you are using Android Studio or Eclipse, the <code>android</code> tool's features are +integrated into the IDE, so you should not need to use this tool directly. </p> + <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> diff --git a/docs/html/tools/help/draw9patch.jd b/docs/html/tools/help/draw9patch.jd index 859b1cf..7c26441 100644 --- a/docs/html/tools/help/draw9patch.jd +++ b/docs/html/tools/help/draw9patch.jd @@ -2,42 +2,50 @@ page.title=Draw 9-patch page.tags=NinePatch @jd:body -<p>The Draw 9-patch tool allows you to easily create a - {@link android.graphics.NinePatch} graphic using a WYSIWYG editor.</p> -<p>For an introduction to Nine-patch graphics and how they work, please read -the section about Nine-patch in the -<a href="{@docRoot}guide/topics/graphics/2d-graphics.html#nine-patch">2D Graphics</a> +<p>The Draw 9-patch tool is a WYSIWYG editor that allows you to create bitmap images that +automatically resize to accommodate the contents of the view and the size of the screen. Selected +parts of the image are scaled horizontally or vertically based indicators drawn within the image. </p> +<p>For an introduction to NinePatch graphics and how they work, please read +the section about NinePatch Drawables in the +<a href="{@docRoot}guide/topics/graphics/2d-graphics.html#nine-patch">Canvas and Drawables</a> document.</p> <img src="{@docRoot}images/draw9patch-norm.png" style="float:right" alt="" height="300" width="341" /> -<p>Here's a quick guide to create a Nine-patch graphic using the Draw 9-patch tool. -You'll need the PNG image with which you'd like to create a NinePatch.</p> +<p>Here's a quick guide to create a NinePatch graphic using the Draw 9-patch tool. +You'll need the PNG image with which you'd like to create a NinePatch image.</p> <ol> - <li>From a terminal, launch the <code>draw9patch</code> application from your SDK - <code>/tools</code> directory. + <li>From a terminal, run the <code>draw9patch</code> command from your SDK + <code>sdk/tools</code> directory to launch the Draw 9-patch tool. </li> - <li>Drag your PNG image into the Draw 9-patch window + <li>Drag your PNG image into the Draw 9-patch window (or <strong>File</strong> > <strong>Open 9-patch...</strong> to locate the file). Your workspace will now open. <p>The left pane is your drawing area, in which you can edit the lines for the - stretchable patches and content area. The right + stretchable patches and content area. The right pane is the preview area, where you can preview your graphic when stretched.</p> </li> - <li>Click within the 1-pixel perimeter to draw the lines that define the stretchable - patches and (optional) content area. Right-click (or hold Shift and click, on Mac) to erase + <li>Click within the 1-pixel perimeter to draw the lines that define the stretchable + patches and (optional) content area. Right-click (or hold Shift and click, on Mac) to erase previously drawn lines. </li> <li>When done, select <strong>File</strong> > <strong>Save 9-patch...</strong> <p>Your image will be saved with the <code>.9.png</code> file name.</p> </li> </ol> - <p class="note"><strong>Note:</strong> A normal PNG file (<code>*.png</code>) will be - loaded with an empty one-pixel border added around the image, in which you can draw + + <p>To make sure that your NinePatch graphics scale down properly, verify that any + stretchable regions are at least 2x2 pixels in size. + Otherwise, they may disappear when scaled down. Also, provide one pixel of extra safe space in + the graphics before and after stretchable regions to avoid interpolation during scaling that may + cause the color at the boundaries to change. </p> + + <p class="note"><strong>Note:</strong> A normal PNG file (<code>*.png</code>) will be + loaded with an empty one-pixel border added around the image, in which you can draw the stretchable patches and content area. - A previously saved 9-patch file (<code>*.9.png</code>) will be loaded as-is, + A previously saved NinePatch file (<code>*.9.png</code>) will be loaded as-is, with no drawing area added, because it already exists.</p> <img src="{@docRoot}images/draw9patch-bad.png" style="float:right;clear:both" alt="" height="300" width="341" diff --git a/docs/html/tools/help/hierarchy-viewer.jd b/docs/html/tools/help/hierarchy-viewer.jd index 4a346e0..da4cc1e 100644 --- a/docs/html/tools/help/hierarchy-viewer.jd +++ b/docs/html/tools/help/hierarchy-viewer.jd @@ -3,16 +3,27 @@ parent.title=Tools parent.link=index.html @jd:body -<p>Hierarchy Viewer allows you to debug and optimize your user -interface. It provides a visual representation of the layout's View hierarchy -(the Layout View) and a magnified inspector of the display (the Pixel Perfect View). -</p> +<p>The Hierarchy Viewer allows you to debug and optimize your user +interface. It provides a visual representation of the layout's View hierarchy +(the Layout View) and a magnified inspector of the display (the Pixel Perfect View). </p> + +<p>To start the Hierarchy Viewer, do one of the following: </p> -<p>To start Hierarchy Viewer, enter the following command from the SDK <code>tools/</code> directory:</p> - <pre>hierarchyviewer</pre> -</ol> +<ul> +<li> From Android Studio, choose <strong>Tools > Android Device Monitor</strong> or click the +Android Device Monitor icon +<img src="{@docRoot}images/tools/hierarchicalviewer-icon.png" alt=""/>. Click the Open Perspectives +icon <img src="{@docRoot}images/tools/studio-DDMS-open-perspective-icon.png" alt=""/> and select +<strong>Hierarchy View</strong>. </li> +<li>From the SDK <code>tools/</code> directory, enter: + <pre>monitor</pre> </li> +</ul> -<p>For more information on how to use Hierarchy Viewer, see -<a href="{@docRoot}tools/debugging/debugging-ui.html">Debugging and Profiling UIs</a> +<p>For more information on how to use the Hierarchy Viewer, see +<a href="{@docRoot}tools/debugging/debugging-ui.html">Optimizing Your UI</a>. </p> +<p class="note"><strong>Note:</strong> The command line version of Hierarchy Viewer has been +deprecated. </p> + + diff --git a/docs/html/tools/help/index.jd b/docs/html/tools/help/index.jd index 75324b7..4c97d0c 100644 --- a/docs/html/tools/help/index.jd +++ b/docs/html/tools/help/index.jd @@ -70,11 +70,6 @@ avd</code>) the emulator (<code>emulator</code>), and the Dalvik Debug Monitor S an emulator instance or connected Android-powered device. It also provides access to the device shell for advanced command-line operations.</dd> - <dt><a href="{@docRoot}tools/help/uiautomator/index.html">uiautomator</a></dt> - <dd>The {@code uiautomator} testing framework lets you test your user interface (UI) efficiently - by creating automated functional UI testcases that can be run against your app on one or - more devices.</dd> - <dt><a href="{@docRoot}tools/debugging/ddms.html">Dalvik Debug Monitor Server (ddms)</a></dt> <dd>Lets you debug Android applications.</dd> @@ -95,25 +90,6 @@ with Traceview and dmtracedump</a></dd> <dd>Converts the HPROF file that is generated by the Android SDK tools to a standard format so you can view the file in a profiling tool of your choice.</dd> - - <dt><a href="{@docRoot}tools/help/monkey.html">Monkey</a></dt> - <dd>Runs on your emulator or device and generates pseudo-random streams of user events such -as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey -to stress-test applications that you are developing, in a random yet repeatable manner. - <ul> - <li><a href="{@docRoot}tools/help/MonkeyDevice.html"><span -class="en">MonkeyDevice</span></a></li> - <li><a href="{@docRoot}tools/help/MonkeyImage.html"><span -class="en">MonkeyImage</span></a></li> - <li><a href="{@docRoot}tools/help/MonkeyRunner.html"><span -class="en">MonkeyRunner</span></a></li> - </ul> - </dd> - - <dt><a href="{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a></dt> - <dd>Provides an API for writing programs that control an Android device or emulator from -outside of Android code.</dd> - <dt><a href="{@docRoot}tools/help/systrace.html">Systrace</a></dt> <dd>Lets you analyze the execution of your application in the context of system processes, to help diagnose display and performance issues.</dd> diff --git a/docs/html/tools/help/lint.jd b/docs/html/tools/help/lint.jd index ba31f6d..0f52689 100644 --- a/docs/html/tools/help/lint.jd +++ b/docs/html/tools/help/lint.jd @@ -14,14 +14,23 @@ parent.link=index.html </div> </div> -<p>The Android {@code lint} tool is a static code analysis tool that checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, accessibility, and internationalization. </p> -<p>For more information on running {@code lint}, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p> +<p>The Android {@code lint} tool is a static code analysis tool that checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, accessibility, and internationalization.</p> -<h2 id="syntax">Syntax</h2> +<p>In Android Studio, the configured <code>lint</code> and other IDE inspections run automatically +whenever you compile your program. You can also manually run inspections in Android Studio +by selecting <strong>Analyze > Inspect Code</strong> from the application or right-click menu. +The <em>Specify Inspections Scope</em> dialog appears so you can specify the desired inspection +profile and scope.</p> + +<p>For more information on enabling {@code lint} inspections and running {@code lint}, +see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p> + +<h2 id="syntax">Command Line Syntax</h2> <p> <pre>lint [flags] <project directory></pre> -For example, you can issue the following command to scan the Java and XML files under the {@code myproject} directory and its subdirectories. The result is displayed on the console. +For example, you can issue the following command to scan the Java and XML files under the +{@code myproject} directory and its subdirectories. The result is displayed on the console. <pre>lint myproject</pre> You can also use {@code lint} to check for a specific issue. For example, you can run the following command to scan the files under the {@code myproject} directory and its subdirectories to check for XML attributes missing the Android namespace prefix. The issue ID {@code MissingPrefix} tells lint to only scan for this issue. @@ -172,7 +181,11 @@ You can create an HTML report for the issues that {@code lint} detects. For exam <h2 id="config_keywords">Configuring Java and XML Source Files</h2> <p>To configure lint checking, you can apply the following annotation or attribute to the source files in your Android project. </p> <ul> -<LI>To disable lint checking for a specific Java class or method, use the <code>@SuppressLint</code> annotation. </LI> -<li>To disable lint checking for specific sections of your XML file, use the <code>tools:ignore</code> attribute. </li> +<LI>To disable {@code lint} checking for a specific Java class or method, use the <code>@SuppressLint</code> +annotation. </LI> +<li>To disable {@code lint} checking for specific sections of your XML file, use the +<code>tools:ignore</code> attribute. </li> </ul> -<p>You can also specify your lint checking preferences for a specific Android project in the lint.xml file. For more information on configuring lint, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p> +<p>You can also specify your {@code lint} checking preferences for a specific Android project in +the <code>lint.xml</code> file. For more information on configuring {@code lint}, see +<a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p> diff --git a/docs/html/tools/help/proguard.jd b/docs/html/tools/help/proguard.jd index aa9a0bc..b5d84ed 100644 --- a/docs/html/tools/help/proguard.jd +++ b/docs/html/tools/help/proguard.jd @@ -8,7 +8,9 @@ parent.link=index.html <h2>In this document</h2> <ol> - <li><a href="#enabling">Enabling ProGuard</a></li> + <li><a href="#enabling-gradle">Enabling ProGuard (Gradle Builds)</a></li> + + <li><a href="#enabling">Enabling ProGuard (Ant Builds)</a></li> <li><a href="#configuring">Configuring ProGuard</a></li> @@ -37,7 +39,10 @@ parent.link=index.html </div> </div> - <p>The ProGuard tool shrinks, optimizes, and obfuscates your code by removing unused code and + + + <p>The <a href="http://proguard.sourceforge.net">ProGuard</a> tool shrinks, optimizes, and + obfuscates your code by removing unused code and renaming classes, fields, and methods with semantically obscure names. The result is a smaller 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 @@ -45,44 +50,102 @@ parent.link=index.html <a href="{@docRoot}google/play/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 - have to deal with obfuscated code when you build your application in debug mode. + manually. ProGuard runs only when you build your application in release mode, so you do not + have to deal with obfuscated code when you build your application in debug mode. Having ProGuard run is completely optional, but highly recommended.</p> - + <p>This document describes how to enable and configure ProGuard as well as use the <code>retrace</code> tool to decode obfuscated stack traces.</p> - <h2 id="enabling">Enabling ProGuard</h2> + + <h2 id="enabling-gradle">Enabling ProGuard (Gradle Builds)</h2> + <p>When you create a project in Android Studio or with the Gradle build system, the + <code>minifyEnabled</code> property in the <code>build.gradle</code> file enables and disables + ProGuard for release builds. The <code>minifyEnabled</code> property is part of the + <code>buildTypes</code> <code>release</code> block that controls the settings applied to + release builds. Set the <code>minifyEnabled</code> property to <code>true</code> to enable + ProGuard, as shown in this example. </p> + + <pre class="no-pretty-print"> + android { + ... + + buildTypes { + release { + minifyEnabled true + proguardFiles getDefaultProguardFile('proguard-android.txt'), + 'proguard-rules.pro' + } + } + } + </pre> + + <p>The <code>getDefaultProguardFile('proguard-android.txt')</code> method obtains the default + ProGuard settings from the Android SDK <code>tools/proguard/</code> folder. The + <code>proguard-android-optimize.txt</code> file is also available in this Android SDK + folder with the same rules but with optimizations enabled. ProGuard optimizations perform + analysis at the bytecode level, inside and across methods to help make your app smaller and run + faster. Android Studio adds the <code>proguard-rules.pro</code> file at the root of the module, + so you can also easily add custom ProGuard rules specific to the current module. </p> + + <p>You can also add ProGuard files to the <code>getDefaultProguardFile</code> + directive for all release builds or as part of the <code>productFlavor</code> settings in the + <code>build.gradle</code> file to customize the settings applied to build variants. This example + adds the <code>proguard-rules-new.pro</code> to the <code>proguardFiles</code> + directive and the <code>other-rules.pro</code> file to the <code>flavor2</code> product flavor. </p> + +<pre class="no-pretty-print"> + android { + ... + + buildTypes { + release { + minifyEnabled true + proguardFiles getDefaultProguardFile('proguard-android.txt'), + 'proguard-rules.pro', 'proguard-rules-new.pro' + } + } + + productFlavors { + flavor1 { + } + flavor2 { + proguardFile 'other-rules.pro' + } + } + } + </pre> + + + + <h2 id="enabling">Enabling ProGuard (Ant Builds)</h2> <p>When you create an Android project, a <code>proguard.cfg</code> file is automatically generated in the root directory of the project. This file defines how ProGuard optimizes and obfuscates your code, so it is very important that you understand how to customize it for your needs. The default configuration file only covers general cases, so you most likely have to edit - it for your own needs. See the following section about <a href="#configuring">Configuring ProGuard</a> for information on - customizing the ProGuard configuration file.</p> + it for your own needs. See the following section about <a href="#configuring">Configuring + ProGuard</a> for information on customizing the ProGuard configuration file.</p> <p>To enable ProGuard so that it runs as part of an Ant or Eclipse build, set the <code>proguard.config</code> property in the <code><project_root>/project.properties</code> file. The path can be an absolute path or a path relative to the project's root.</p> -<p class="note"><strong>Note:</strong> When using Android Studio, you must add Proguard -to your <code>gradle.build</code> file's build types. For more information, see the -<a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Running-ProGuard" ->Gradle Plugin User Guide</a>. + <p>If you left the <code>proguard.cfg</code> file in its default location (the project's root + directory), you can specify its location like this:</p> -<p>If you left the <code>proguard.cfg</code> file in its default location (the project's root directory), -you can specify its location like this:</p> <pre class="no-pretty-print"> proguard.config=proguard.cfg </pre> + <p> You can also move the the file to anywhere you want, and specify the absolute path to it: </p> + <pre class="no-pretty-print"> proguard.config=/path/to/proguard.cfg </pre> - <p>When you build your application in release mode, either by running <code>ant release</code> or by using the <em>Export Wizard</em> in Eclipse, the build system automatically checks to see if the <code>proguard.config</code> property is set. If it is, ProGuard automatically processes @@ -116,19 +179,19 @@ proguard.config=/path/to/proguard.cfg <li><code><project_root>/proguard</code> if you are using Eclipse.</li> </ul> - + <p class="caution"><strong>Caution:</strong> Every time you run a build in release mode, these files are overwritten with the latest files generated by ProGuard. Save a copy of them each time you release your - application in order to de-obfuscate bug reports from your release builds. - For more information on why saving these files is important, see + application in order to de-obfuscate bug reports from your release builds. + For more information on why saving these files is important, see <a href="#considerations">Debugging considerations for published applications</a>. </p> <h2 id="configuring">Configuring ProGuard</h2> - <p>For some situations, the default configurations in the <code>proguard.cfg</code> file will - suffice. However, many situations are hard for ProGuard to analyze correctly and it might remove code - that it thinks is not used, but your application actually needs. Some examples include:</p> + <p>For some situations, the default configurations in the ProGuard configuration file will + suffice. However, many situations are hard for ProGuard to analyze correctly and it might remove + code that it thinks is not used, but your application actually needs. Some examples include:</p> <ul> <li>a class that is referenced only in the <code>AndroidManifest.xml</code> file</li> @@ -138,61 +201,63 @@ proguard.config=/path/to/proguard.cfg <li>dynamically referenced fields and methods</li> </ul> - <p>The default <code>proguard.cfg</code> file tries to cover general cases, but you might + <p>The default ProGuard configuration file tries to cover general cases, but you might encounter exceptions such as <code>ClassNotFoundException</code>, which happens when ProGuard strips away an entire class that your application calls.</p> <p>You can fix errors when ProGuard strips away your code by adding a <code>-keep</code> line in - the <code>proguard.cfg</code> file. For example:</p> + the ProGuard configuration file. For example:</p> <pre> -keep public class <MyClass> </pre> <p>There are many options and considerations when using the <code>-keep</code> option, so it is - highly recommended that you read the + highly recommended that you read the <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard - Manual</a> for more information about customizing your configuration file. The - <em>Overview of Keep options</em> and <em>Examples</em> sections are particularly helpful. + Manual</a> for more information about customizing your configuration file. The + <em>Overview of Keep options</em> and <em>Examples</em> sections are particularly helpful. The <a href= "http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/troubleshooting.html">Troubleshooting - </a> section of the ProGuard Manual outlines other common problems you might encounter + </a> section of the ProGuard Manual outlines other common problems you might encounter when your code gets stripped away.</p> <h2 id="decoding">Decoding Obfuscated Stack Traces</h2> <p>When your obfuscated code outputs a stack trace, the method names are obfuscated, which makes debugging hard, if not impossible. Fortunately, whenever ProGuard runs, it outputs a - <code><project_root>/bin/proguard/mapping.txt</code> file, which shows you the original - class, method, and field names mapped to their obfuscated names.</p> + <code>mapping.txt</code> file, which shows you the original class, method, and field names + mapped to their obfuscated names.</p> <p>The <code>retrace.bat</code> script on Windows or the <code>retrace.sh</code> script on Linux - or Mac OS X can convert an obfuscated stack trace to a readable one. It is located in the - <code><sdk_root>/tools/proguard/</code> directory. The syntax for executing the + or Mac OS X can convert an obfuscated stack trace to a readable one. It is located + in the <code><sdk_root>/tools/proguard/</code> directory. The syntax for executing the <code>retrace</code> tool is:</p> <pre>retrace.bat|retrace.sh [-verbose] mapping.txt [<stacktrace_file>]</pre> <p>For example:</p> - + <pre>retrace.bat -verbose mapping.txt obfuscated_trace.txt</pre> - + <p>If you do not specify a value for <em><stacktrace_file></em>, the <code>retrace</code> tool reads from standard input.</p> <h3 id="considerations">Debugging considerations for published applications</h3> - <p>Save the <code>mapping.txt</code> file for every release that you publish to your users. - By retaining a copy of the <code>mapping.txt</code> file for each release build, + <p>Save the <code>mapping.txt</code> file for every release that you publish to your users. + By retaining a copy of the <code>mapping.txt</code> file for each release build, you ensure that you can debug a problem if a user encounters a bug and submits an obfuscated stack trace. A project's <code>mapping.txt</code> file is overwritten every time you do a release build, so you must be - careful about saving the versions that you need.</p> + careful about saving the versions that you need. For Eclipse, this file is stored in + <code><project_root>/bin/proguard/</code>. For Android Studio, this file is stored in + the app <code>build/outs/</code> folder. </p> <p>For example, say you publish an application and continue developing new features of the application for a new version. You then do a release build using ProGuard soon after. The build overwrites the previous <code>mapping.txt</code> file. A user submits a bug report - containing a stack trace from the application that is currently published. You no longer have a way + containing a stack trace from the application that is currently published. You no longer have a way of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the version on the user's device is gone. There are other situations where your <code>mapping.txt</code> file can be overwritten, so ensure that you save a copy for every release that you anticipate you have to debug.</p> - <p>How you save the <code>mapping.txt</code> file is your decision. For example, you can rename them to - include a version or build number, or you can version control them along with your source - code.</p> + <p>How you save the <code>mapping.txt</code> files is your decision. For example, you can rename + the files to include a version or build number, or you can version control them along with your + source code.</p> diff --git a/docs/html/tools/help/sdk-manager.jd b/docs/html/tools/help/sdk-manager.jd index b084237..0c77395 100644 --- a/docs/html/tools/help/sdk-manager.jd +++ b/docs/html/tools/help/sdk-manager.jd @@ -16,7 +16,7 @@ your environment.</p> <li>On Windows, double-click the <code>SDK Manager.exe</code> file at the root of the Android SDK directory.</li> <li>On Mac or Linux, open a terminal and navigate to the <code>tools/</code> directory in the -Android SDK, then execute <code>android sdk</code>.</li> +location where the Android SDK is installed, then execute <code>android sdk</code>.</li> </ul> <p>You can select which packages you want to download by toggling the checkboxes on the left, then diff --git a/docs/html/tools/help/systrace.jd b/docs/html/tools/help/systrace.jd index d6fc05e..4461da9 100644 --- a/docs/html/tools/help/systrace.jd +++ b/docs/html/tools/help/systrace.jd @@ -68,7 +68,8 @@ or the Android <a href="{@docRoot}tools/help/monitor.html">Device Monitor</a>. <ol> <li>In <a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>, open an Android application project.</li> - <li>Open the Device Monitor by selecting <strong>Tools > Android > Monitor</strong>.</li> + <li>Open the Device Monitor by selecting <strong>Tools > Android > Android Device + Monitor</strong>.</li> <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no devices are listed, make sure your device is connected via USB cable and that debugging is enabled on the device.</li> |