+++ /dev/null
-toc:
-- title: Download
- path: /sdk/index.html
- section:
- - title: Install Android Studio
- path: /sdk/installing/index.html
-
-- title: Workflow
- path: /tools/workflow/index.html
- section:
- - title: Projects
- path: /tools/projects/index.html
- - title: Build and Run
- path: /tools/building/index.html
- - title: Virtual Devices
- path: /tools/devices/index.html
- - title: Hardware Devices
- path: /tools/device.html
- section:
- - title: USB Drivers
- path: /tools/extras/oem-usb.html
- - title: Testing
- path: /tools/testing/index.html
- - title: Debugging
- path: /tools/debugging/index.html
- - title: Publishing
- path: /tools/publishing/publishing_overview.html
- path_attributes:
- - name: zh-cn-lang
- value: 发布概述
- section:
- - title: Preparing for Release
- path: /tools/publishing/preparing.html
- path_attributes:
- - name: zh-cn-lang
- value: 准备发布
- - title: Versioning Your Apps
- path: /tools/publishing/versioning.html
- - title: Signing Your Apps
- path: /tools/publishing/app-signing.html
-
-- title: Android Studio
- path: /tools/studio/index.html
- section:
- - title: Features
- path: /tools/studio/studio-features.html
- - title: Configuration
- path: /tools/studio/studio-config.html
- section:
- - title: SDK Manager
- path: /tools/help/sdk-manager.html
- - title: Project Tools
- path: /sdk/installing/create-project.html
- section:
- - title: Project Structure Management
- path: /tools/help/project-mgmt.html
- - title: Using Code Templates
- path: /tools/projects/templates.html
- - title: Building and Running
- path: /tools/building/building-studio.html
- - title: Code Tools
- path: /tools/studio/code-tools.html
- section:
- - title: Improving Your Code with lint
- path: /tools/debugging/improving-w-lint.html
- - title: Improving Code Inspection with Annotations
- path: /tools/debugging/annotations.html
- - title: Shrink Your Code and Resources
- path: /tools/help/proguard.html
- - title: Supporting URLs and App Indexing in Android Studio
- path: /tools/help/app-link-indexing.html
- - title: UI Tools
- path: /tools/studio/ui-tools.html
- section:
- - title: Layout Editor
- path: /sdk/installing/studio-layout.html
- - title: Theme Editor
- path: /tools/help/theme-editor.html
- - title: Translations Editor
- path: /tools/help/translations-editor.html
- - title: Vector Asset Studio
- path: /tools/help/vector-asset-studio.html
- - title: Image Asset Studio
- path: /tools/help/image-asset-studio.html
- - title: AVD Manager
- path: /tools/devices/managing-avds.html
- - title: Android Emulator
- path: /tools/devices/emulator.html
- section:
- - title: Android Emulator Command-Line Features
- path: /tools/help/emulator.html
- - title: Debugging Tools
- path: /tools/debugging/debugging-studio.html
- section:
- - title: DDMS
- path: /tools/debugging/ddms.html
- - title: Android Monitor
- path: /tools/help/android-monitor.html
- section:
- - title: logcat Monitor
- path: /tools/help/am-logcat.html
- - title: Memory Monitor
- path: /tools/help/am-memory.html
- - title: CPU Monitor
- path: /tools/help/am-cpu.html
- - title: GPU Monitor
- path: /tools/help/am-gpu.html
- - title: Network Monitor
- path: /tools/help/am-network.html
- - title: Tips and Tricks
- path: /sdk/installing/studio-tips.html
- - title: Migrating from Eclipse ADT
- path: /sdk/installing/migrate.html
- section:
- - title: Transition Guide
- path: /tools/studio/eclipse-transition-guide.html
-
-- title: Tools Help
- path: /tools/help/index.html
- section:
- - title: adb
- path: /tools/help/adb.html
- - title: android
- path: /tools/help/android.html
- section:
- - title: Managing AVDs
- path: /tools/devices/managing-avds-cmdline.html
- - title: Managing Projects
- path: /tools/projects/projects-cmdline.html
- - title: AVD Manager
- path: /tools/help/avd-manager.html
- - title: bmgr
- path: /tools/help/bmgr.html
- - title: Desktop Head Unit
- path: /tools/help/desktop-head-unit.html
- - title: Device Monitor
- path: /tools/help/monitor.html
- - title: dmtracedump
- path: /tools/help/dmtracedump.html
- - title: Draw 9-Patch
- path: /tools/help/draw9patch.html
- - title: etc1tool
- path: /tools/help/etc1tool.html
- - title: Hierarchy Viewer
- path: /tools/help/hierarchy-viewer.html
- section:
- - title: Optimizing your UI
- path: /tools/debugging/debugging-ui.html
- - title: hprof-conv
- path: /tools/help/hprof-conv.html
- - title: jobb
- path: /tools/help/jobb.html
- - title: lint
- path: /tools/help/lint.html
- - title: logcat
- path: /tools/help/logcat.html
- section:
- - title: Reading and Writing Logs
- path: /tools/debugging/debugging-log.html
- - title: mksdcard
- path: /tools/help/mksdcard.html
- - title: Tracer for OpenGL ES
- path: /tools/help/gltracer.html
- - title: zipalign
- path: /tools/help/zipalign.html
-
-- title: Build System
- path: /sdk/installing/studio-build.html
- section:
- - title: Running Gradle Builds
- path: /tools/building/building-cmdline.html
- - title: Configuring Gradle Builds
- path: /tools/building/configuring-gradle.html
- - title: Android Plugin for Gradle
- path: /tools/building/plugin-for-gradle.html
- - title: Manifest Merging
- path: /tools/building/manifest-merge.html
- - title: Apps Over 64K Methods
- path: /tools/building/multidex.html
-
-- title: Performance Tools
- path: /tools/performance/index.html
- section:
- - title: Overdraw Debugger
- path: /tools/performance/debug-gpu-overdraw/index.html
- - title: Rendering Profiler
- path: /tools/performance/profile-gpu-rendering/index.html
- - title: Hierarchy Viewer
- path: /tools/performance/hierarchy-viewer/index.html
- section:
- - title: Setup
- path: /tools/performance/hierarchy-viewer/setup.html
- - title: Profiling
- path: /tools/performance/hierarchy-viewer/profiling.html
- - title: Memory Profilers
- path: /tools/performance/comparison.html
- section:
- - title: Memory Monitor
- path: /tools/performance/memory-monitor/index.html
- - title: Heap Viewer
- path: /tools/performance/heap-viewer/index.html
- - title: Allocation Tracker
- path: /tools/performance/allocation-tracker/index.html
- - title: Investigating Your RAM Usage
- path: /tools/debugging/debugging-memory.html
- - title: Traceview
- path: /tools/debugging/debugging-tracing.html
- section:
- - title: Walkthrough
- path: /tools/performance/traceview/index.html
- - title: Command Reference
- path: /tools/help/traceview.html
- - title: Systrace
- path: /tools/debugging/systrace.html
- section:
- - title: Walkthrough
- path: /tools/performance/systrace/index.html
- - title: Command Reference
- path: /tools/help/systrace.html
- - title: Battery Profilers
- path: /tools/performance/batterystats-battery-historian/index.html
- section:
- - title: Historian Charts
- path: /tools/performance/batterystats-battery-historian/charts.html
-
-- title: Testing Tools
- path: /tools/testing/testing-tools.html
- section:
- - title: Testing Concepts
- path: /tools/testing/testing_android.html
- - title: Testing Support Library
- path: /tools/testing-support-library/index.html
- section:
- - title: API Reference
- path: /reference/android/support/test/package-summary.html
- - title: Testing with Android Studio
- path: /training/testing/start/index.html
- - title: Testing from the Command-Line
- path: /tools/testing/testing_otheride.html
- - title: monkey
- path: /tools/help/monkey.html
- - title: monkeyrunner
- path: /tools/help/monkeyrunner_concepts.html
- section:
- - title: MonkeyDevice
- path: /tools/help/MonkeyDevice.html
- - title: MonkeyImage
- path: /tools/help/MonkeyImage.html
- - title: MonkeyRunner
- path: /tools/help/MonkeyRunner.html
-
-- title: Support Library
- path: /tools/support-library/index.html
- section:
- - title: Features
- path: /tools/support-library/features.html
- - title: Setup
- path: /tools/support-library/setup.html
-
-- title: Data Binding Library
- path: /tools/data-binding/guide.html
-
-- title: Revisions
- path: /tools/revisions/index.html
- section:
- - title: Android Studio
- path: /tools/revisions/studio.html
- - title: SDK Tools
- path: /tools/sdk/tools-notes.html
- - title: SDK Build Tools
- path: /tools/revisions/build-tools.html
- - title: Android Plugin for Gradle
- path: /tools/revisions/gradle-plugin.html
- - title: SDK Platforms
- path: /tools/revisions/platforms.html
- - title: ADT Plugin
- path: /tools/sdk/eclipse-adt.html
-
-- title: NDK
- path: /tools/sdk/ndk/index.html
+++ /dev/null
-page.title=Building and Running from the Command Line
-parent.title=Building and Running
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#DebugMode">Building in Debug Mode</a></li>
- <li><a href="#ReleaseMode">Building in Release Mode</a>
- <ol>
- <li><a href="#ManualReleaseMode">Build unsigned</a></li>
- <li><a href="#AutoReleaseMode">Build signed and aligned</a></li>
- <li><a href="#OnceBuilt">Once built and signed in release mode</a></li>
- </ol>
- </li>
- <li><a href="#RunningOnEmulator">Running on the Emulator</a></li>
- <li><a href="#RunningOnDevice">Running on a Device</a></li>
- <li><a href="#Signing">Application Signing</a></li>
- <li><a href="#PluginReference">Plugin Language Reference</a></li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/studio-build.html">
- Build System</a></li>
- <li><a href="{@docRoot}tools/devices/managing-avds-cmdline.html">
- Managing AVDs from the Command Line</a></li>
- <li><a href="{@docRoot}tools/devices/emulator.html">
- Using the Android Emulator</a></li>
- <li><a href="{@docRoot}tools/publishing/app-signing.html">
- Signing Your Applications</a></li>
- </ol>
- </div>
- </div>
-
- <p>By default, there are two build types to build your application using the Gradle build settings:
- one for debugging your application — <em>debug</em> — and one for building your
- final package for release — <em>release mode</em>. Regardless of which build type
- your modules use, the app must be signed before it can install on an emulator or device—with
- a debug key when building in debug mode and with your own private key when building in release mode.</p>
-
- <p>Whether you're building with the debug or release build type, you need to run
- and build your module. This will create the .apk file that you can install on an emulator or device.
- When you build using the debug build type, the .apk file is automatically signed by the SDK tools
- with a debug key based on the <code>debuggable true</code> setting in the module's build.gradle file,
- so it's instantly ready for installation onto an emulator or attached
- development device. You cannot distribute an application that is signed with a debug key.
- When you build using the release build type, the .apk file is <em>unsigned</em>, so you
- must manually sign it with your own private key, using Keytool and Jarsigner settings in the
- module's <code>build.gradle</code> file.</p>
-
- <p>It's important that you read and understand <a href=
- "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>, particularly once
- you're ready to release your application and share it with end-users. That document describes the
- procedure for generating a private key and then using it to sign your APK file. If you're just
- getting started, however, you can quickly run your applications on an emulator or your own
- development device by building in debug mode.</p>
-
- <p>If you don't have <a href="http://www.gradle.org/">Gradle</a>, you can obtain it from the <a href="http://gradle.org/">Gradle
- home page</a>. Install it and make sure it is in your executable PATH. Before calling Gradle, you
- need to declare the JAVA_HOME environment variable to specify the path to where the JDK is
- installed.</p>
-
- <p class="note"><strong>Note:</strong> When using <code>ant</code> and installing JDK on Windows,
- the default is to install in the "Program Files" directory. This location will cause
- <code>ant</code> to fail, because of the space. To fix the problem, you can specify the JAVA_HOME
- variable like this:
- <pre>set JAVA_HOME=c:\Progra~1\Java\<jdkdir></pre>
-
- <p>The easiest solution, however, is to install JDK in a non-space directory, for example:</p>
-
- <pre>c:\java\jdk1.7</pre>
-
- <h2 id="DebugMode">Building in Debug Mode</h2>
-
- <p>For immediate application testing and debugging, you can build your application in debug mode
- and immediately install it on an emulator. In debug mode, the build tools automatically sign your
- application with a debug key and optimize the package with {@code zipalign}.</p>
-
- <p>To build in debug mode, open a command-line and navigate to the root of your project directory.
- Use Gradle to build your project in debug mode, invoke the <code>assembleDebug</code> build task
- using the Gradle wrapper script (<code>gradlew assembleRelease</code>).
-
- <p>This creates your debug <code>.apk</code> file inside the module <code>build/</code>
- directory, named <code><your_module_name>-debug.apk</code>. The file is already signed
- with the debug key and has been aligned with
- <a href="{@docRoot}tools/help/zipalign.html"><code>zipalign</code></a>. </p>
-
- <p>On Windows platforms, type this command:</p>
-
-<pre>
-> gradlew.bat assembleDebug
-</pre>
-
-<p>On Mac OS and Linux platforms, type these commands:</p>
-
-<pre>
-$ chmod +x gradlew
-$ ./gradlew assembleDebug
-</pre>
-
- <p>The first command (<code>chmod</code>) adds the execution permission to the Gradle wrapper
- script and is only necessary the first time you build this project from the command line.</p>
-
- <p>After you build the project, the output APK for the app module is located in
- <code>app/build/outputs/apk/</code>, and the output AAR for any lib modules is located in
- <code>lib/build/outputs/libs/</code>.</p>
-
- <p>To see a list of all available build tasks for your project, type this command:</p>
-
-<pre>
-$ ./gradlew tasks
-</pre>
-
- <p>Each time you change a source file or resource, you must run Gradle again in order to package up
- the latest version of the application.</p>
-
- <p>To install and run your application on an emulator, see the section about <a href=
- "{@docRoot}tools/building/building-studio.html">Running on the Emulator</a>.</p>
-
- <h2 id="ReleaseMode">Building in Release Mode</h2>
-
- <p>When you're ready to release and distribute your application to end-users, you must build your
- application in release mode. Once you have built in release mode, it's a good idea to perform
- additional testing and debugging with the final .apk.</p>
-
- <p>Before you start building your application in release mode, be aware that you must sign the
- resulting application package with your private key, and should then align it using the {@code
- zipalign} tool. There are two approaches to building in release mode: build an unsigned package
- in release mode and then manually sign and align the package, or allow the build script to sign
- and align the package for you.</p>
-
- <h3 id="ManualReleaseMode">Build unsigned</h3>
-
- <p>If you build your application <em>unsigned</em>, then you will need to manually sign and align
- the package.</p>
-
- <p>To build an <em>unsigned</em> .apk in release mode, open a command-line and navigate to the
- root of your module directory. Invoke the <code>assembleRelease</code> build task.</li>
-
- <p>On Windows platforms, type this command:</p>
-
-<pre>
-> gradlew.bat assembleRelease
-</pre>
-
-<p>On Mac OS and Linux platforms, type this command:</p>
-
-<pre>
-$ ./gradlew assembleRelease
-</pre>
-
-
- <p>This creates your Android application .apk file inside the project <code>bin/</code>
- directory, named <code><em><your_module_name></em>-unsigned.apk</code>.</p>
-
- <p class="note"><strong>Note:</strong> The .apk file is <em>unsigned</em> at this point and can't
- be installed until signed with your private key.</p>
-
- <p>Once you have created the unsigned .apk, your next step is to sign the .apk with your private
- key and then align it with {@code zipalign}. To complete this procedure, read <a href=
- "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
-
- <p>When your <code>.apk</code> has been signed and aligned, it's ready to be distributed to end-users.
- You should test the final build on different devices or AVDs to ensure that it
- runs properly on different platforms.</p>
-
- <h3 id="AutoReleaseMode">Build signed and aligned</h3>
-
- <p>If you would like, you can configure the Android build script to automatically sign and align
- your application package. To do so, you must provide the path to your keystore and the name of
- your key alias in your modules's build.gradle file. With this information provided,
- the build will prompt you for your keystore and alias password when you build using the release
- build type and produce your final application package, which will be ready for distribution.</p>
-
- <p>To specify your keystore and alias, open the module build.gradle file (found in
- the root of the module directory) and add entries for {@code storeFile}, {@code storePassword},
- {@code keyAlias} and {@code keyPassword}.
- For example:</p>
- <pre>
-storeFile file("myreleasekey.keystore")
-keyAlias "MyReleaseKey"
-</pre>
-
- <p>Save your changes. Now you can build a <em>signed</em> .apk in release mode:</p>
-
- <ol>
- <li>Open a command-line and navigate to the root of your module directory.</li>
-
- <li>Edit the build.gradle file to build your project in release mode:
- <p><pre>
-...
-android {
- ...
- defaultConfig { ... }
- signingConfigs {
- release {
- storeFile file("myreleasekey.keystore")
- storePassword "password"
- keyAlias "MyReleaseKey"
- keyPassword "password"
- }
- }
- buildTypes {
- release {
- ...
- signingConfig signingConfigs.release
- }
- }
-}
-...
-</pre></p>
- </li>
-
- <li>When prompted, enter you keystore and alias passwords.
-
- <p class="caution"><strong>Caution:</strong> As described above, your password will be
- visible on the screen.</p>
- </li>
- </ol>
-
- <p>This creates your Android application .apk file inside the module <code>build/</code>
- directory, named <code><em><your_module_name></em>-release.apk</code>. This .apk file has
- been signed with the private key specified in build.gradle file and aligned with {@code
- zipalign}. It's ready for installation and distribution.</p>
-
- <h3 id="OnceBuilt">Once built and signed in release mode</h3>
-
- <p>Once you have signed your application with a private key, you can install and run it on an
- <a href="#RunningOnEmulator">emulator</a> or <a href="#RunningOnDevice">device</a>. You can
- also try installing it onto a device from a web server. Simply upload the signed .apk to a web
- site, then load the .apk URL in your Android web browser to download the application and begin
- installation. (On your device, be sure you have enabled
- <em>Settings > Applications > Unknown sources</em>.)</p>
-
- <h2 id="RunningOnEmulator">Running on the Emulator</h2>
-
- <p>Before you can run your application on the Android Emulator, you must <a href=
- "{@docRoot}tools/devices/managing-avds.html">create an AVD</a>.</p>
-
- <p>To run your application:</p>
-
- <ol>
- <li>
- <strong>Open the AVD Manager and launch a virtual device</strong>
-
- <p>From your SDK's <code>platform-tools/</code> directory, execute the {@code android} tool
-with the <code>avd</code> options:</p>
- <pre>
-android avd
-</pre>
-
- <p>In the <em>Virtual Devices</em> view, select an AVD and click <strong>Start</strong>.</p>
- </li>
-
- <li>
- <strong>Install your application</strong>
-
- <p>From your SDK's <code>tools/</code> directory, install the {@code .apk} on the
- emulator:</p>
- <pre>
-adb install <em><path_to_your_bin></em>.apk
-</pre>
-
- <p>Your .apk file (signed with either a release or debug key) is in your module {@code build/}
- directory after you build your application.</p>
-
- <p>If there is more than one emulator running, you must specify the emulator upon which to
- install the application, by its serial number, with the <code>-s</code> option. For
- example:</p>
- <pre>
-adb -s emulator-5554 install <em>path/to/your/app</em>.apk
-</pre>
-
- <p>To see a list of available device serial numbers, execute {@code adb devices}.</p>
- </li>
- </ol>
-
- <p>If you don't see your application on the emulator, try closing the emulator and launching the
- virtual device again from the AVD Manager. Sometimes when you install an application for the
- first time, it won't show up in the application launcher or be accessible by other applications.
- This is because the package manager usually examines manifests completely only on emulator
- startup.</p>
-
- <p>Be certain to create multiple AVDs upon which to test your application. You should have one
- AVD for each platform and screen type with which your application is compatible. For instance, if
- your application compiles against the Android 4.0 (API Level 14) platform, you should create an
- AVD for each platform equal to and greater than 4.0 and an AVD for each <a href=
- "{@docRoot}guide/practices/screens_support.html">screen type</a> you support, then test your
- application on each one.</p>
-
- <p class="note"><strong>Tip:</strong> If you have <em>only one</em> emulator running, you can
- build your application and install it on the emulator in one simple step. Navigate to the root of
- your project directory and use Ant to compile the project with <em>install mode</em>: <code>ant
- install</code>. This will build your application, sign it with the debug key, and install it on
- the currently running emulator.</p>
-
- <h2 id="RunningOnDevice">Running on a Device</h2>
-
- <p>Before you can run your application on a device, you must perform some basic setup for your
- device:</p>
-
- <ul>
- <li>Enable <strong>USB debugging</strong> on your device. You can find the option under
- <strong>Settings > Developer options</strong>.
- <p class="note"><strong>Note:</strong> On Android 4.2 and newer, <strong>Developer
- options</strong> is hidden by default. To make it available, go
- to <strong>Settings > About phone</strong> and tap <strong>Build number</strong>
- seven times. Return to the previous screen to find <strong>Developer options</strong>.</p>
- </li>
-
- <li>Ensure that your development computer can detect your device when connected via USB</li>
- </ul>
-
- <p>Read <a href="{@docRoot}tools/device.html#setting-up">Setting up a Device for
- Development</a> for more information.</p>
-
- <p>Once your device is set up and connected via USB, navigate to your SDK's <code>platform-tools/</code>
- directory and install the <code>.apk</code> on the device:</p>
- <pre>
-adb -d install <em>path/to/your/app</em>.apk
-</pre>
-
- <p>The {@code -d} flag specifies that you want to use the attached device (in case you also have
- an emulator running).</p>
-
- <p>For more information on the tools used above, please see the following documents:</p>
-
- <ul>
- <li><a href="{@docRoot}tools/help/android.html">android Tool</a></li>
-
- <li><a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a></li>
-
- <li><a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a> (ADB)</li>
- </ul>
-
- <h2 id="Signing">Application Signing</h2>
-
- <p>As you begin developing Android applications, understand that all Android applications must be
- digitally signed before the system will install them on an emulator or device. There are two ways
- to do this: with a <em>debug key</em> (for immediate testing on an emulator or development
- device) or with a <em>private key</em> (for application distribution).</p>
-
- <p>The Android build tools help you get started by automatically signing your .apk files with a
- debug key at build time. This means that you can build your application and install it on the
- emulator without having to generate your own private key. However, please note that if you intend
- to publish your application, you <strong>must</strong> sign the application with your own private
- key, rather than the debug key generated by the SDK tools.</p>
-
- <p>Please read <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your
- Applications</a>, which provides a thorough guide to application signing on Android and what it
- means to you as an Android application developer. The document also includes a guide to publishing
- and signing your application.</p>
-
- <h2 id="PluginReference">Android Plugin for Gradle</h2>
-
- <p>The Android build system uses the Android plugin for Gradle to support the Gradle Domain
- Specific Language (DSL) and declarative language elements. See the
- <a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plug-in for Gradle</a> section for
- a description of the plugin and a link to the complete list of the supported Gradle DSL elements.</p>
-
-
-
+++ /dev/null
-page.title=Building and Running from Android Studio
-parent.title=Building and Running
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li>
- <a href="#run-configuration">Changing the run configuration</a>
- </li>
-
- <li>
- <a href="#changing-variant">Changing build variants</a>
- </li>
-
- <li>
- <a href="#gradle-console">Monitoring the build process</a>
- </li>
-
- <li>
- <a href="#generating-apks">Generating APKs</a>
- </li>
-
- <li>
- <a href="#instant-run">About Instant Run</a>
- <ol>
- <li>
- <a href="#set-up-ir">Configuring and optimizing your project for Instant Run</a>
- </li>
-
- <li>
- <a href="#ir-limitations">Limitations of Instant Run</a>
- </li>
- </ol>
- </li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/studio-build.html">
- Build System</a></li>
- <li><a href="{@docRoot}tools/devices/managing-avds.html">
- Managing AVDs with AVD Manager</a></li>
- <li><a href="{@docRoot}tools/devices/emulator.html">
- Using the Android Emulator</a></li>
- <li><a href="{@docRoot}tools/device.html">
- Using Hardware Devices</a></li>
- <li><a href="{@docRoot}tools/publishing/app-signing.html">
- Signing Your Applications</a></li>
- </ol>
- </div>
-</div>
-
-<p>
- By default, Android Studio sets up new projects to deploy to the Emulator or
- a physical device with just a few clicks. With Instant Run, you can push
- changes to methods and existing app resources to a running app without
- building a new APK, so code changes are visible almost instantly.
-</p>
-
-<p>
- To build and run your app, click <strong>Run 'app'</strong> <img src=
- "{@docRoot}images/tools/as-run.png" alt="" style=
- "vertical-align:bottom;margin:0;">. Android Studio builds your app with
- Gradle, asks you to select a deployment target (an emulator or a connected
- device), and then deploys your app to it. You can customize some of this
- default behavior, such as selecting an automatic deployment target, by
- <a href="#run-configuration">changing the run configuration</a>.
-</p>
-
-<p>
- If you want to <a href="{@docRoot}tools/devices/emulator.html">use the Android
- Emulator</a> to run your app, you need to have an Android Virtual Device
- (AVD) ready. If you haven't already created one, then after you click
- <strong>Run 'app'</strong>, click <strong>Create New Emulator</strong> in the
- <strong>Select Deployment Target</strong> dialog. Follow the Virtual Device
- Configuration wizard to define the type of device you want to emulate. For
- more information, see <a href=
- "{@docRoot}tools/devices/managing-avds.html">Managing AVDs with the AVD
- Manager</a>.
-</p>
-
-<p>
- If you're using a physical Android device, you need to enable USB debugging
- on the device. For more information, see <a href=
- "{@docRoot}tools/device.html">Using Hardware Devices</a>.
-</p>
-
-<p class="note">
- <strong>Note:</strong> You can also deploy your app in debug mode by clicking
- <strong>Debug 'app'</strong> <img src=
- "{@docRoot}images/tools/as-debugbutton.png" alt="" style=
- "vertical-align:bottom;margin:0;">. Running your app in debug mode
- allows you to set breakpoints in your code, examine variables and evaluate
- expressions at run time, and run debugging tools. To learn more, read about
- <a href="{@docRoot}tools/debugging/debugging-studio.html">Debugging with
- Android Studio</a>.
-</p>
-
-<h3 id="run-configuration">
- Changing the run configuration
-</h3>
-
-<p>
- The run configuration specifies the module to run, package to deploy,
- activity to start, target device, emulator settings, and Logcat options. The
- default run configuration launches the default project activity and uses the
- <strong>Device Chooser</strong> for target device selection. If the default
- settings don't suit your project or module, you can customize the run
- configuration, or even create a new one, at the project, default, and module
- levels. To edit a run configuration:
-</p>
-
-<ol>
- <li>Select <strong>Run</strong> > <strong>Edit Configurations</strong>.
- </li>
-
- <li>Expand the <strong>Android Application</strong> item and select an
- existing run configuration.
- <ul>
- <li>To create a new run configuration, click the '<strong>+</strong>'
- button in the top left corner of the dialog box and select
- <strong>Android Application</strong>.
- </li>
- </ul>
- </li>
-
- <li>With a run configuration selected, adjust your desired settings. For
- example, in the <strong>General</strong> tab, you can specify the APK
- installation settings, launch options, and deployment target options.
- </li>
-</ol>
-
-<h3 id="changing-variant">
- Changing the build variant
-</h3>
-
-<p>
- By default, Android Studio builds the debug version of your app, which is
- intended only for testing, when you click <strong>Run 'app'</strong>. You
- need to build the release version when <a href=
- "{@docRoot}tools/publishing/preparing.html">preparing your app for public
- release</a>.
-</p>
-<p>
- To change the build variant Android Studio uses, go to <strong>Build</strong>
- > <strong>Select Build Variant</strong> and select a different one from
- the drop-down menu. By default, new projects are set up with a debug and
- release build variant.
-</p>
-
-<p>
- Using <em>product flavors</em>, you can create additional build variants for
- different versions of your app, each having different features or device
- requirements. To learn more about build variants and product flavors, read
- <a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle
- Builds</a>.
-</p>
-
-<h3 id="gradle-console">
- Monitoring the build process
-</h3>
-
-<p>
- You can view details about the build process by clicking <strong>Gradle
- Console</strong> <img src="{@docRoot}images/tools/as-gradlebutton.png" alt=""
- style="vertical-align:bottom;margin:0;">. The console displays each
- task that Gradle executes in order to build your app, as shown in figure 1.
-</p>
-
-<img src="{@docRoot}images/tools/studio-gradle-console.png" alt="">
-<p class="img-caption">
- <strong>Figure 1.</strong> The Gradle Console in Android Studio.
-</p>
-
-<p>
- If your build variants use product flavors, Gradle also invokes tasks to
- build those product flavors. To view the list of all available build tasks,
- click <strong>Gradle</strong> <img src=
- "{@docRoot}images/tools/as-gradle.png" alt="" style=
- "vertical-align:bottom;margin:0;"> on the right side of the IDE
- window.
-</p>
-
-<p>
- If an error occurs during the build process, the <em>Messages</em> window
- appears to describe the issue. Gradle may recommend some command-line
- options to help you resolve the issue, such as <code>--stacktrace</code> or
- <code>--debug</code>. To use command-line options with your build process:
-</p>
-
-<ol>
- <li>Open the <strong>Settings</strong> or <strong>Preferences</strong>
- dialog:
- <ul>
- <li>On Windows or Linux, select <strong>File</strong> >
- <strong>Settings</strong> from the main menu.
- </li>
-
- <li>On Mac OSX, select <strong>Android Studio</strong> >
- <strong>Preferences</strong> from the main menu.
- </li>
- </ul>
- </li>
-
- <li>Navigate to <strong>Build, Execution, Deployment</strong> >
- <strong>Compiler</strong>.
- </li>
-
- <li>In the text field next to <em>Command-line Options</em>, enter your
- command-line options.
- </li>
-
- <li>Click <strong>OK</strong> to save and exit.
- </li>
-</ol>
-
-<p>
- Gradle will apply these command-line options the next time you try building
- your app.
-</p>
-
-<h3 id="generating-apks">
- Generating APKs
-</h3>
-
-<p>
- When you click <strong>Run 'app'</strong>, Android Studio generates a debug
- APK and deploys it to your target device. Before you can generate a release
- version of your app for public distribution, however, you must first learn
- how to <a href="{@docRoot}tools/publishing/app-signing.html#studio">sign your
- app</a>. You can then generate multiple signed APKs of your debug or release
- build variants. To locate the generated APK files, click the link in the
- pop-up dialog, as shown in figure 2.
-</p>
-
-<p>
- <img src="{@docRoot}images/tools/as-find-apk.png" alt="">
-</p>
-
-<p class="img-caption">
- <strong>Figure 2.</strong> Click the link to locate the generated APK
- files.
-</p>
-
-<h2 id="instant-run">About Instant Run</h3>
-
-<p>
- Introduced in Android Studio 2.0, Instant Run is a behavior for the
- <strong>Run</strong> <img src="{@docRoot}images/tools/as-run.png" alt=""
- style="vertical-align:bottom;margin:0;"> and <strong>Debug</strong> <img src=
- "{@docRoot}images/tools/as-debugbutton.png" alt="" style=
- "vertical-align:bottom;margin:0;"> commands that significantly reduces the
- time between updates to your app. Although your first build may take longer
- to complete, Instant Run pushes subsequent updates to your app without
- building a new APK, so changes are visible much more quickly.
-</p>
-
-<p>
- Instant Run is supported only when you deploy the debug build variant, use
- Android Plugin for Gradle version 2.0.0 or higher, and set
- <code>minSdkVersion</code> to 15 or higher in your app's module-level
- <code>build.gradle</code> file. For the best performance, set
- <code>minSdkVersion</code> to 21 or higher.
-</p>
-
-<p>
- After deploying an app, a small, yellow thunderbolt icon appears within the
- <strong>Run</strong> <img src=
- "{@docRoot}images/tools/instant-run/as-irrun.png" alt="" style=
- "vertical-align:bottom;margin:0;"> button (or <strong>Debug</strong>
- <img src="{@docRoot}images/tools/instant-run/as-irdebug.png" alt="" style=
- "vertical-align:bottom;margin:0;"> button), indicating that Instant Run is
- ready to push updates the next time you click the button. Instead of building
- a new APK, it pushes just those new changes and, in some cases, the app
- doesn't even need to restart but immediately shows the effect of those code
- changes.
-</p>
-
-<p>
- Instant Run pushes updated code and resources to your connected device or
- emulator by performing a <em>hot swap</em>, <em>warm swap</em>, or <em>cold
- swap</em>. It automatically determines the type of swap to perform based on
- the type of change you made. The following table describes how Instant Run
- behaves when you push certain code changes to a target device.
-</p>
-
-<table id="ir-table">
- <col width="40%">
- <tr>
- <th scope="col">
- Code Change
- </th>
- <th scope="col">
- Instant Run Behavior
- </th>
- </tr>
-
- <tr id="hot-swap">
- <td>
- <ul>
- <li>Change implementation code of an existing method
- </li>
- </ul>
- </td>
- <td>
- <p>
- Supported with <strong>hot swap</strong>: This is the
- fastest type of swap and makes changes visible much more quickly. Your
- application keeps running and a stub method with the new implementation is used
- the next time the method is called.
- </p>
-
- <p>
- Hot swaps do not re-initialize objects in your running app. You may need to
- restart the current activity, or <a href="#rerun">restart the app</a>, before
- you see certain updates. By default, Android Studio automatically restarts the
- current activity after performing a hot swap. If you do not want this behavior,
- you can <a href="#activity-restart">disable automatic activity restarts</a>.
- </p>
- </td>
- </tr>
-
- <tr id="warm-swap">
- <td>
- <ul>
- <li>Change or remove an existing resource
- </li>
- </ul>
- </td>
- <td>
- Supported with <strong>warm swap</strong>: This swap
- is still very fast, but Instant Run must restart the current activity when it
- pushes the changed resources to your app. Your app keeps running, but a small
- flicker may appear on the screen as the activity restarts—this is normal.
- </td>
- </tr>
-
- <tr id="cold-swap">
- <td>
- Structural code changes, such as:
- <ul>
- <li>Add, remove, or change:
- <ul>
- <li>an annotation
- </li>
-
- <li>an instance field
- </li>
-
- <li>a static field
- </li>
-
- <li>a static method signature
- </li>
-
- <li>an instance method signature
- </li>
- </ul>
- </li>
-
- <li>Change which parent class the current class inherits from
- </li>
-
- <li>Change the list of implemented interfaces
- </li>
-
- <li>Change a class's static initializer
- </li>
-
- <li>Reorder layout elements that use dynamic resource IDs
- </li>
- </ul>
- </td>
- <td>
- <p>
- Supported with <strong>cold swap</strong> (API level 21 or higher): This swap
- is a bit slower because, although a new APK is not required, Instant Run must
- restart the whole app when it pushes structural code changes.
- </p>
-
- <p>
- For target devices running API level 20 or lower, Android Studio
- deploys a full APK.
- </p>
- </td>
- </tr>
-
- <tr>
- <td>
- <ul>
- <li>Change the app manifest
- </li>
-
- <li>Change resources referenced by the app manifest
- </li>
-
- <li>Change an Android widget UI element
- </li>
- </ul>
- </td>
- <td>
- <p>
- When making changes to the app's manifest or resources referenced by the
- manifest, Android Studio automatically <strong>deploys a new build</strong>
- in order to apply these changes. This is because certain information about
- the app, such as its name, app icon resources, and intent filters, are
- determined from the manifest when the APK is installed on the device.
- </p>
-
- <p>
- If your build process automatically updates any part of the app manifest,
- such as automatically iterating <code>versionCode</code> or
- <code>versionName</code>, you will not be able to benefit from the full
- performance of Instant Run. When using Instant Run, you should disable
- automatic updates to any part in the app manifest in your debug build
- variants.
- </p>
-
- <p>
- When updating an Android widget UI element, you need to perform a <a href=
- "#rerun">Clean and Rerun</a> to see your changes. Alternatively, because
- performing clean builds may take longer while using Instant Run, you can
- temporarily <a href="#disable-ir">disable Instant Run</a> while making
- updates to your widget UI.
- </p>
- </td>
- </tr>
-</table>
-
-<p class="note">
- <strong>Note:</strong> If you need to restart your app after a crash, do not
- launch it from your target device. Restarting your app from your target
- device does not apply any of your code changes since the last cold swap or
- <em>incremental build</em>. To launch your app with all your recent changes,
- click <strong>Run</strong> <img src="{@docRoot}images/tools/as-run.png" alt=
- "" style="vertical-align:bottom;margin:0;"> (or <strong>Debug</strong>
- <img src="{@docRoot}images/tools/as-debugbutton.png" alt="" style=
- "vertical-align:bottom;margin:0;">) from Android Studio.
-</p>
-
-<h4 id="rerun">
- Using Rerun
-</h4>
-
-<p>
- When pushing code changes that affect certain initializers, such as changes
- to an app's {@link android.app.Application#onCreate onCreate()} method, you
- need to restart your app for the changes to take effect. To perform an
- <em>incremental build</em> and restart the app, click <strong>Rerun</strong>
- <img src="{@docRoot}images/tools/as-restart.png" alt="" style=
- "vertical-align:bottom;margin:0;">.
-</p>
-
-<p>
- If you need to deploy a <em>clean build</em>, select <strong>Run</strong>
- > <strong>Clean and Rerun 'app'</strong> <img src=
- "{@docRoot}images/tools/as-cleanrerun.png" alt="" style=
- "vertical-align:bottom;margin:0;"> from the main menu, or hold down the
- <strong>Shift</strong> key while clicking <strong>Rerun</strong> <img src=
- "{@docRoot}images/tools/as-restart.png" alt="" style=
- "vertical-align:bottom;margin:0;">. This action stops the running app,
- performs a full clean build, and deploys the new APK to your target device.
-</p>
-
-<h4 id="activity-restart">
- Disabling automatic activity restart
-</h4>
-
-<p>
- When performing a hot swap, your app keeps running but Android Studio
- automatically restarts the current activity. To disable this default setting:
-</p>
-
-<ol>
- <li>Open the <strong>Settings</strong> or <strong>Preferences</strong>
- dialog:
- <ul>
- <li>On Windows or Linux, select <strong>File</strong> >
- <strong>Settings</strong> from the main menu.
- </li>
-
- <li>On Mac OSX, select <strong>Android Studio</strong> >
- <strong>Preferences</strong> from the main menu.
- </li>
- </ul>
- </li>
-
- <li>Navigate to <strong>Build, Execution, Deployment</strong> >
- <strong>Instant Run</strong>.
- </li>
-
- <li>Uncheck the box next to <strong>Restart activity on code
- changes</strong>.
- </li>
-</ol>
-
-<p>
- If automatic activity restart is disabled, you can manually restart the current
- activity from the menu bar by selecting <strong>Run</strong> > <strong>Restart
- Activity</strong>.
-</p>
-
-<h3 id="set-up-ir">
- Configuring and optimizing your project for Instant Run
-</h3>
-
-<p>
- Android Studio enables Instant Run by default for projects built using
- Android Plugin for Gradle 2.0.0 and higher.
-</p>
-
-<p>
- To update an existing project with the latest version of the plugin:
-</p>
-
-<ol>
- <li>Open the <strong>Settings</strong> or <strong>Preferences</strong>
- dialog.
- </li>
-
- <li>
- <p>
- Navigate to <strong>Build, Execution, Deployment</strong> >
- <strong>Instant Run</strong> and click <strong>Update Project</strong>,
- as shown in figure 3.
- </p>
-
- <p>
- If the option to update the project does not appear, it’s already
- up-to-date with the latest Android Plugin for Gradle.
- </p>
-
- <img src="{@docRoot}images/tools/instant-run/update-project-dialog.png"
- alt="" height="51">
-
- <p class="img-caption">
- <strong>Figure 3.</strong> Updating the Android Plugin for Gradle for an
- existing project.
- </p>
- </li>
-</ol>
-
-<p>
- You also need to <a href="#changing-variant">change the build variant</a> to
- a debug version of your app to start using Instant Run.
-</p>
-
-<h4 id="configure-dexoptions">
- Improve build times by configuring DEX resources
-</h4>
-
-<p>
- When you deploy a clean build, Android Studio instruments your app to allow
- Instant Run to push code and resource updates. Although updating the running
- app happens much more quickly, the first build may take longer to complete.
- You can improve the build process by configuring a few <a class=
- "external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html">
- <code>DexOptions</code></a> settings:
-</p>
-
-<dl>
- <dt>
- <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html#com.android.build.gradle.internal.dsl.DexOptions:maxProcessCount">
- <code>maxProcessCount</code></a>
- </dt>
-
- <dd>
- Sets the maximum number of DEX processes that can be started concurrently.
- If the Gradle daemon is already running, you need to stop the process
- before initializing it with a new maximum process count. You can terminate
- the Gradle daemon by calling one of the following from the
- <em>Terminal</em> window:
- <ul>
- <li>On Windows, call <code>gradlew --stop</code>
- </li>
-
- <li>On Linux/Mac OSX, call <code>./gradlew --stop</code>
- </li>
- </ul>
- </dd>
-
- <dt>
- <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html#com.android.build.gradle.internal.dsl.DexOptions:javaMaxHeapSize">
- <code>javaMaxHeapSize</code></a>
- </dt>
-
- <dd>
- Sets the maximum memory allocation pool size for the dex operation. When
- passing a value, you can append the letter 'k' to indicate kilobytes, 'm'
- to indicate megabytes, or 'g' to indicate gigabytes.
- </dd>
-</dl>
-
-<p>
- The following example sets <code>maxProcessCount</code> to 4 and
- <code>javaMaxHeapSize</code> to "2g" in the module-level
- <code>build.gradle</code> file:
-</p>
-
-<pre>
-android {
- ...
- dexOptions {
- maxProcessCount 4 // this is the default value
- javaMaxHeapSize "2g"
- }
-}
-</pre>
-
-<p>
- You should experiment with these settings by incrementing their values and
- observing the effect on your build times. You could experience a negative
- impact to performance if you allocate too many resources to the dexing process.
-</p>
-
-<h4>
- Enabling dexing-in-process and incremental Java compilation
-</h4>
-
-<p>
- <a href="{@docRoot}tools/revisions/gradle-plugin.html#revisions">Android
- Plugin for Gradle version 2.1.0</a> and higher features additional build
- process improvements, including incremental Java compilation and
- dexing-in-process. Incremental Java compilation is enabled by default and
- reduces compilation time during development by only recompiling portions of
- the source that have changed or need to be recompiled.
-</p>
-
-<p>
- Dexing-in-process performs dexing within the build process rather than in a
- separate, external VM processes. This not only makes incremental builds much
- faster, but also significantly speeds up full builds. To enable this feature,
- you need to set the Gradle daemon's maximum heap size to at least 2048 MB. You
- can do this by including the following in your project's
- <code>gradle.properties</code> file:
-
-<pre>
-org.gradle.jvmargs = -Xmx2048m
-</pre>
-
-</p>
-
-<p>
- If you have defined a value for <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html#com.android.build.gradle.internal.dsl.DexOptions:javaMaxHeapSize">
- <code>javaMaxHeapSize</code></a> in your module-level <code>build.gradle</code>
- file, you need to set the daemon's max heap size to the value of
- <code>javaMaxHeapSize</code> + 1024 MB. For example, if you have set
- <code>javaMaxHeapSize</code> to "2g", you need to add the following to your
- project's <code>gradle.properties</code> file:
-
-<pre>
-org.gradle.jvmargs = -Xmx3072m
-</pre>
-
-</p>
-
-<h4 id="windows-defender">
- Excluding your project from Windows Defender
-</h4>
-
-<p>
- On Windows systems, Windows Defender may cause slowdowns while using Instant
- Run. If you are using Windows Defender, you should <a class="external-link"
- href=
- "http://answers.microsoft.com/en-us/protect/wiki/protect_defender-protect_scanning/how-to-exclude-a-filefolder-from-windows-defender/f32ee18f-a012-4f02-8611-0737570e8eee">
- exclude your Android Studio project folder from Windows Defender malware
- scans</a>.
-</p>
-
-<h4 id="crashlytics">
- Disabling Crashlytics for your debug build variant
-</h4>
-
-<p>
- Using Crashlytics is known to cause slower build times. To improve build
- performance while developing your app, you can <a class="external-link" href=
- "https://docs.fabric.io/android/crashlytics/build-tools.html#disabling-crashlytics-for-debug-builds">
- disable Crashlytics for your debug build variant</a>.
-</p>
-
-<h3 id="ir-limitations">
- Limitations of Instant Run
-</h3>
-
-<p>
- Instant Run is designed to speed up the build and deploy process in most
- situations. However, there are some aspects to using Instant Run that might
- affect its behavior and compatibility with your app. If you experience any
- other issues while using Instant Run, please <a class="external-link" href=
- "http://tools.android.com/filing-bugs">file a bug</a>.
-</p>
-
-<h4 id="multiple-devices">
- Deploying to multiple devices
-</h4>
-
-<p>
- Instant Run uses different techniques to perform hot, warm, and cold swaps
- that are specific to the API level of the target device. For this reason,
- while deploying an app to multiple devices at once, Android Studio
- temporarily turns off Instant Run.
-</p>
-
-<h4 id="ir-multidex">
- Multidexing your app
-</h4>
-
-<p>
- If your project is configured for <a href=
- "{@docRoot}tools/building/multidex.html#mdex-pre-l">Legacy Multidex</a>—that
- is, when <code>build.gradle</code> is configured with <code>multiDexEnabled
- true</code> and <code>minSdkVersion 20</code> or lower—and you deploy to
- target devices running Android 4.4 (API level 20) or lower, Android Studio
- disables Instant Run.
-</p>
-
-<p>
- If <code>minSdkVersion</code> is set to 21 or higher, Instant Run
- automatically configures your app for multidex. Because Instant Run only
- works with the debug version of your app, you may need to <a href=
- "{@docRoot}tools/building/multidex.html#mdex-gradle">configure your app for
- multidex</a> when deploying your release build variant.
-</p>
-
-<h4 id="instrumented-tests">
- Running instrumented tests and performance profilers
-</h4>
-
-<p>
- Instrumented tests load both the debug APK and a test APK into the same
- process on a test device, allowing control methods to override the normal
- lifecycle of the app and perform tests. While running or debugging
- instrumented tests, Android Studio does not inject the additional methods
- required for Instant Run and turns the feature off.
-</p>
-
-<p>
- While profiling an app, you should disable Instant Run. There is a small
- performance impact when using Instant Run and a slightly larger impact when
- overriding methods with a hot swap. This performance impact could interfere
- with information provided by performance profiling tools. Additionally, the
- stub methods generated with each hot swap can complicate stack traces.
-</p>
-
-<h4 id="plugins">
- Using third-party plugins
-</h4>
-
-<p>
- Android Studio temporarily disables the Java Code Coverage Library (JaCoCo)
- and ProGuard while using Instant Run. Because Instant Run only works with
- debug builds, this does not affect your release build.
-</p>
-
-<p>
- Certain third-party plugins that perform bytecode enhancement may cause
- issues with how Instant Run instruments your app. If you experience these
- issues, but want to continue using Instant Run, you should disable those
- plugins for your debug build variant. You can also help improve compatibility
- with third-party plugins by <a class="external-link" href=
- "http://tools.android.com/filing-bugs">filing a bug</a>.
-</p>
-
-<h4 id="multi-process-apps">
- Pushing changes to multi-process apps
-</h4>
-
-<p>
- Instant Run only instruments your app's main process in order to perform hot
- swaps and warm swaps. When pushing code changes to other app processes, such
- as changes to a method implementation or an existing resource, Instant Run
- performs a <a href="#cold-swap">cold swap</a>.
-</p>
-
-<h4 id="disable-ir">
- Disabling Instant Run
-</h4>
-
-<p>
- To disable Instant Run:
-</p>
-
-<ol>
- <li>Open the <strong>Settings</strong> or <strong>Preferences</strong>
- dialog.
- </li>
-
- <li>Navigate to <strong>Build, Execution, Deployment</strong> >
- <strong>Instant Run</strong>.
- </li>
-
- <li>Uncheck the box next to <strong>Enable Instant Run</strong>.
- </li>
-</ol>
\ No newline at end of file
+++ /dev/null
-page.title=Configuring Gradle Builds
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-<h2>In this document</h2>
-<ol>
- <li><a href="#buildFileBasics">Build Configuration Basics</a>
- <ol>
- <li><a href="#buildFileBasics">Declare dependencies</a></li>
- <li><a href="#buildFileBasics">Run ProGuard</a></li>
- <li><a href="#configureSigning">Configure signing settings</a></li>
- </ol>
- </li>
-
-
- <li><a href="#workBuildVariants">Work with build variants</a></li>
-</ol>
-
-
-<h2>See also</h2>
-<ul>
-<li><a href="{@docRoot}tools/building/plugin-for-gradle.html">
-Android Plugin for Gradle</a></li>
-</ul>
-</div>
-</div>
-
-
-<p>This section builds on the
-<a href="{@docRoot}sdk/installing/studio-build.html">Build System Overview</a> and
-<a href="{@docRoot}tools/building/building-studio.html">Build and Running from Android Studio</a>
-to show you how to use build variants based on product flavors and build types.</p>
-
-
-<h2 id="buildFileBasics">Build Configuration Basics</h2>
-
-<p>Android Studio projects contain a top-level build file and a build file for each module. The
-build files are called <code>build.gradle</code>, and they are plain text files that use
-<a href="http://groovy.codehaus.org">Groovy</a> syntax to configure the build with the elements
-provided by the Android plugin for Gradle. In most cases, you only need to edit the build files
-at the module level. For example, the build file for the app module in the
-<code>BuildSystemExample</code> project looks like this:</p>
-
-<pre>
-apply plugin: 'com.android.application'
-
-android {
- compileSdkVersion 19
- buildToolsVersion "19.0.0"
-
- defaultConfig {
- minSdkVersion 8
- targetSdkVersion 19
- versionCode 1
- versionName "1.0"
- }
- buildTypes {
- release {
- minifyEnabled true
- proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
- }
- }
-}
-
-dependencies {
- compile project(":lib")
- compile 'com.android.support:appcompat-v7:19.0.1'
- compile fileTree(dir: 'libs', include: ['*.jar'])
-}
-</pre>
-
-<p><code>apply plugin: 'com.android.application'</code> applies the Android plugin for Gradle to this build.
-This adds Android-specific build tasks to the top-level build tasks and makes the
-<code>android {...}</code> element available to specify Android-specific build options.</p>
-
-<p><code>android {...}</code> configures all the Android-specific build options:</p>
-
-<ul>
- <li>The <code>compileSdkVersion</code> property specifies the compilation target.</li>
- <li><p>The <code>buildToolsVersion</code> property specifies what version of the build tools
- to use. To install several versions of the build tools, use the SDK Manager.</p>
- <p class="note"><strong>Note:</strong> Always use a build tools version whose major
- revision number is higher or equal to that of your compilation target and target SDK.</p>
- </li>
- <li><p>The <code>defaultConfig</code> element configures core settings and
- entries in the manifest file (<code>AndroidManifest.xml</code>) dynamically from the
- build system. The values in <code>defaultConfig</code> override those in the manifest
- file.</p>
- <p>The configuration specified in the <code>defaultConfig</code> element applies
- to all build variants, unless the configuration for a build variant overrides some
- of these values.</p>
- </li>
- <li>The <code>buildTypes</code> element controls how to build and package your app.
- By default, the build system defines two build types: <em>debug</em> and
- <em>release</em>. The debug build type includes debugging symbols and is signed with
- the debug key. The release build type is not signed by default.
- In this example the build file configures the release version to use
- ProGuard.</li>
-</ul>
-
-<p>The <code>dependencies</code> element is outside and after the <code>android</code> element.
-This element declares the dependencies for this module. Dependencies are covered in the following
-sections.</p>
-
-<p class="note"><strong>Note:</strong> When you make changes to the build files in your project,
-Android Studio requires a project sync to import the build configuration changes. Click
-<strong>Sync Now</strong> on the yellow notification bar that appears for Android Studio
-to import the changes.</p>
-
-<img src="{@docRoot}images/tools/as-gradlesync.png" alt="" />
-<p class="img-caption"><strong>Figure 1.</strong> Sync the project in Android Studio.</p>
-
-<h3 id="declareDeps">Declare dependencies</h3>
-
-<p>The <code>app</code> module in this example declares three
-dependencies:</p>
-
-<pre>
-...
-dependencies {
- // Module dependency
- compile project(":lib")
-
- // Remote binary dependency
- compile 'com.android.support:appcompat-v7:19.0.1'
-
- // Local binary dependency
- compile fileTree(dir: 'libs', include: ['*.jar'])
-}
-</pre>
-
-<p>Each of these dependencies is described below. The build system adds all the
-<code>compile</code> dependencies to the compilation classpath and includes them in the final
-package.</p>
-
-<h4>Module dependencies</h4>
-
-<p>The <code>app</code> module depends on the <code>lib</code> module, because
-<code>MainActivity</code> launches <code>LibActivity1</code> as described in
-<a href="#openActFromLib">Open an Activity from a Library Module</a>.</p>
-
-<p><code>compile project(":lib")</code> declares a dependency on the <code>lib</code>
-module of <code>BuildSystemExample</code>. When you build the <code>app</code> module,
-the build system assembles and includes the <code>lib</code> module.</p>
-
-<h4>Remote binary dependencies</h4>
-
-<p>The <code>app</code> and <code>lib</code> modules both use the <code>ActionBarActivity</code>
-class from the Android Support Library, so these modules depend on it.</p>
-
-<p><code>compile 'com.android.support:appcompat-v7:19.0.1'</code> declares a dependency on
-version 19.0.1 of the Android Support Library by specifying its Maven coordinates. The Android Support
-Library is available in the <em>Android Repository</em> package of the Android SDK. If your
-SDK installation does not have this package, download and install it using the SDK Manager.</p>
-
-Android Studio configures projects to use the Maven Central Repository by default. (This
-configuration is included in the top-level build file for the project.)</p>
-
-<h4>Local binary dependencies</h4>
-
-<p>Some modules do not use any binary dependencies from the
-local file system. If you have modules that require local binary dependencies, copy the JAR
-files for these dependencies into <code><moduleName>/libs</code> inside your project.</p>
-
-<p><code>compile fileTree(dir: 'libs', include: ['*.jar'])</code> tells the build system that any
-JAR file inside <code>app/libs</code> is a dependency and should be included in the compilation
-classpath and in the final package.</p>
-
-<p>For more information about dependencies in Gradle, see
-<a href="http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html">Dependency
-Management Basics</a> in the Gradle User Guide.</p>
-
-<h3 id="runProguard">Run ProGuard</h3>
-
-<p>The build system can run
-<a href="http://developer.android.com/tools/help/proguard.html">ProGuard</a> to obfuscate your
-classes during the build process. In <code>BuildSystemExample</code>, modify the build file for
-the app module to run ProGuard for the release build:</p>
-
-<pre>
-...
-android {
- ...
- buildTypes {
- release {
- minifyEnabled true
- proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
- }
- }
-}
-...
-</pre>
-
-<p><code>getDefaultProguardFile('proguard-android.txt')</code> obtains the default ProGuard
-settings from the Android SDK installation. Android Studio adds the module-specific rules file
-<code>proguard-rules.pro</code> at the root of the module, where you can add custom ProGuard
-rules.</p>
-
-
-
-<h3>Application ID for package identification </h3>
-<p>With the Android build system, the <em>applicationId</em> attribute is used to
-uniquely identify application packages for publishing. The application ID is set in the
-<em>android</em> section of the <code>build.gradle</code> file.
-</p>
-
- <pre>
- apply plugin: 'com.android.application'
-
- android {
- compileSdkVersion 19
- buildToolsVersion "19.1"
-
- defaultConfig {
- <strong>applicationId "com.example.my.app"</strong>
- minSdkVersion 15
- targetSdkVersion 19
- versionCode 1
- versionName "1.0"
- }
- ...
- </pre>
-
-<p class="note"><strong>Note:</strong> The <em>applicationId</em> is specified only in your
-{@code build.gradle} file, and not in the AndroidManifest.xml file.</p>
-
-<p>When using build variants, the build system enables you to uniquely identify different
-packages for each product flavors and build types. The application ID in the build type is added as
-a suffix to those specified for the product flavors. </p>
-
- <pre>
- productFlavors {
- pro {
- applicationId = "com.example.my.pkg.pro"
- }
- free {
- applicationId = "com.example.my.pkg.free"
- }
- }
-
- buildTypes {
- debug {
- applicationIdSuffix ".debug"
- }
- }
- ....
- </pre>
-
-<p>The package name must still be specified in the manifest file. It is used in your source code
-to refer to your R class and to resolve any relative activity/service registrations. </p>
-
- <pre>
- <?xml version="1.0" encoding="utf-8"?>
- <manifest xmlns:android="http://schemas.android.com/apk/res/android"
- <strong>package="com.example.app"</strong>>
- </pre>
-
-<p class="note"><strong>Note:</strong> If you have multiple manifests (for example, a product
-flavor specific manifest and a build type manifest), the package name is optional in those manifests.
-If it is specified in those manifests, the package name must be identical to the package name
-specified in the manifest in the <code>src/main/</code> folder. </p>
-
-<p>For more information about the build files and process, see
-<a href="{@docRoot}sdk/installing/studio-build.html">Build System Overview</a>.</p>
-
-
-
-<h3 id="configureSigning">Configure signing settings</h3>
-
-<p>The debug and the release versions of the app differ on whether the application can be
-debugged on secure devices and on how the APK is signed. The build system signs the debug
-version with a default key and certificate using known credentials to avoid a password prompt at
-build time. The build system does not sign the release version unless you explicitly define a
-signing configuration for this build. If you do not have a release key, you can generate one as
-described in <a href="{@docRoot}tools/publishing/app-signing.html">Signing your Applications</a>.</p>
-
-
-<h2 id="workBuildVariants">Work with build variants</h2>
-
-<p>This section describes how the build system can help you create different versions of the same
-application from a single project. This is useful when you have a demo version and a paid version
-of your app, or if you want to distribute multiple APKs for different device configurations on
-Google Play.</p>
-
-<p>The build system uses <em>product flavors</em> to create different product versions of your app.
-Each product version of your app can have different features or device requirements. The build
-system also uses build types to apply different build and packaging settings to each product version.
-Each product flavor and build type combination forms a build variant. The build system generates a
-different APK for each build variant of your app. </p>
-
-<h3>Build variants</h3>
-
-<p>This example project consists of the two default build types (<em>debug</em> and <em>release</em>)
-and two product flavors for app type (demo and full). For more information on advanced uses of
-build variants, see
-<a href="{@docRoot}sdk/installing/studio-build.html"> Build System Overview</a> .</p>
-
-
-<h4>Product flavors </h4>
-
-<p>To create different product versions of your app:</p>
-
-<ol>
- <li>Define product flavors in the build file.</li>
- <li>Create additional source directories for each flavor.</li>
- <li>Add the flavor-specific sources to your project.</li>
-</ol>
-
-<p>The rest of this section walks you through these steps in detail using a
-<code>BuildSystemExample</code> project. You create two flavors of the
-<code>BuildSystemExample</code> app, a demo flavor and a full flavor. Both flavors share
-<code>MainActivity</code>, to which you add a new button to launch a new activity,
-<code>SecondActivity</code>. This new activity is different for each flavor, so you simulate a
-situation where the new activity would have more features in the full flavor than in the demo
-flavor. At the end of the exercise, you end up with two different APKs, one for each flavor.</p>
-
-<h3>Define product flavors in the build file</h3>
-
-<p>To define two product flavors, edit the build file for the app module to add the following
-configuration:</p>
-
-<pre>
-...
-android {
- ...
- defaultConfig { ... }
- signingConfigs { ... }
- buildTypes { ... }
- productFlavors {
- demo {
- applicationId "com.buildsystemexample.app.demo"
- versionName "1.0-demo"
- }
- full {
- applicationId "com.buildsystemexample.app.full"
- versionName "1.0-full"
- }
- }
-}
-...
-</pre>
-
-<p>The product flavor definitions support the same properties as the <code>defaultConfig</code>
-element. The base configuration for all flavors is specified in <code>defaultConfig</code>, and each
-flavor overrides any default values. The build file above uses the <code>applicationId</code>
-property to assign a different package name to each flavor: since each flavor definition creates a
-different app, they each need a distinct package name.</p>
-
-<p class="note"><strong>Note:</strong> To distribute your app using
-<a href="{@docRoot}google/play/publishing/multiple-apks.html">Multiple APK Support</a> in
-Google Play, assign the same package name to all variants and give each variant a different
-<code>versionCode</code>. To distribute different variants of your app as separate apps in Google
-Play, assign a different package name to each variant.</p>
-
-<h4>Add additional source directories for each flavor</h4>
-
-<p>Now you create source folders and add a <code>SecondActivity</code> to each flavor. To create
-the source directory structure for the demo flavor:</p>
-
-<ol>
- <li>On the <em>Project</em> panel, expand <strong>BuildSystemExample</strong>, and then expand
- the <strong>app</strong> directory.</li>
- <li>Right-click the <strong>src</strong> directory under <em>app</em> and select
- <strong>New</strong> > <strong>Directory</strong>.</li>
- <li>Enter "demo" as the name of the new directory and click <strong>OK</strong>.</li>
- <li><p>Similarly, create the following directories:</p>
- <ul>
- <li><code>app/src/demo/java</code></li>
- <li><code>app/src/demo/res</code></li>
- <li><code>app/src/demo/res/layout</code></li>
- <li><code>app/src/demo/res/values</code></li>
- </ul>
- </li>
-</ol>
-
-<p>The resulting directory structure looks like figure 1.</p>
-
-<img src="{@docRoot}images/tools/as-demoflavordirs.png" alt="" />
-<p class="img-caption"><strong>Figure 1.</strong> New source directories for the demo flavor.</p>
-
-<h4>Add a new activity to each flavor</h4>
-
-<p>To add <code>SecondActivity</code> to the <code>demo</code> flavor:</p>
-
-<ol>
- <li>On the <em>Project</em> panel, right click on the <strong>app</strong> module and select
- <strong>New</strong> > <strong>Activity</strong>.</li>
- <li>Select <strong>Blank Activity</strong> and click <strong>Next</strong>.</li>
- <li>Enter "SecondActivity" as the activity name.</li>
- <li>Enter "com.buildsystemexample.app" as the package name and click
- <strong>Finish</strong>.</li>
- <li>Right click on the <strong>java</strong> directory under <em>app/src/demo</em> and select
- <strong>New</strong> > <strong>Package</strong>.</li>
- <li>Enter "com.buildsystemexample.app" as the package name and click <strong>OK</strong>.</li>
- <li>Drag <strong>SecondActivity</strong> and drop it under the new package in
- <em>app/src/demo/java</em>.</li>
- <li>Accept the default values and click <strong>Refactor</strong>.</li>
-</ol>
-
-<p>To add the layout for <code>SecondActivity</code> and a strings resource to the demo flavor:</p>
-
-<ol>
- <li>Drag <strong>activity_second.xml</strong> from <em>app/src/main/res/layout</em> and drop it
- inside <em>app/src/demo/res/layout</em>.</li>
- <li>Accept the default values on the window that appears and click <code>OK</code>.</li>
- <li>Copy <strong>strings.xml</strong> from <em>app/src/main/res</em> into
- <em>app/src/demo/res</em>.</li>
- <li><p>Replace the contents of the new copy of <code>strings.xml</code> with the
- following:</p>
- <p><pre>
-<?xml version="1.0" encoding="utf-8"?>
-<resources>
- <string name="hello_world">Demo version only.</string>
-</resources>
-</pre></p>
- </li>
-</ol>
-
-<p>Now you add source folders and <code>SecondActivity</code> to the full flavor by making a copy
-of the <code>demo</code> flavor:</p>
-
-<ol>
- <li>On the <em>Project</em> panel, right click on the <strong>demo</strong> directory under
- <em>app/src</em> and select <strong>Copy</strong>.</li>
- <li>Right-click on the <strong>src/</strong> directory under <em>app/</em> and select
- <strong>Paste</strong>.</li>
- <li>On the window that appears, enter "full" as the new name and click <strong>OK</strong>.</li>
- <li><p>Replace the contents of <strong>strings.xml</strong> under <em>src/full/res/values</em>
- with the following:</p>
- <p><pre>
-<?xml version="1.0" encoding="utf-8"?>
-<resources>
- <string name="hello_world">This is the full version!</string>
-</resources>
-</pre></p>
- </li>
-</ol>
-
-<p class="note"><strong>Note:</strong> From this point on, you could develop
-<code>SecondActivity</code> independently inside each
-flavor. For example, you could add more features to this activity in the <code>full</code> flavor.</p>
-
-<p>To work on files from a particular flavor, click on <strong>Build Variants</strong> on the left
-of the IDE window and select the flavor you want to modify in the <em>Build Variants</em> panel,
-as shown in figure 2. Android Studio may show errors in source files from flavors other than the
-one selected in the <em>Build Variants</em> panel, but this does not affect the outcome of the
-build.</p>
-
-<img src="{@docRoot}images/tools/as-buildvariants.png" alt="" />
-<p class="img-caption"><strong>Figure 2.</strong> The Build Variants panel.</p>
-
-<h4>Launch a flavor-specific activity from the main activity</h4>
-
-<p>Since the flavor-specific activity (<code>SecondActivity</code>) has the same package name and
-activity name in both flavors, you can launch it from the main activity, which is common to all
-flavors. To modify the main activity:</p>
-
-<ol>
- <li><p>Edit <code>activity_main.xml</code> and add a new button to
- <code>MainActivity</code>:</p>
- <p><pre>
-<LinearLayout ...>
- ...
- <Button
- android:id="@+id/button2"
- android:layout_width="wrap_content"
- android:layout_height="wrap_content"
- android:text="@string/button2"
- android:onClick="onButton2Clicked"/>
-</LinearLayout>
-</pre></p>
- </li>
- <li>Click on the areas marked in red in the layout file and press <strong>Alt</strong>+
- <strong>Enter</strong>. Follow the suggestions from Android Studio to add a new string
- resource with value “Open Second Activity” and an <code>onButton2Clicked</code> method to
- <code>MainActivity</code>.</li>
- <li><p>Add the following code to the <code>onButton2Clicked</code> method of
- <code>MainActivity</code>:</p>
- <p><pre>
-public void onButton2Clicked(View view) {
- Intent intent = new Intent(this, SecondActivity.class);
- startActivity(intent);
-}
-</pre></p>
- </li>
- <li><p>Edit the app's manifest to include a reference to <code>SecondActivity</code>:</p>
- <p><pre>
-<manifest ...>
- <application ...>
- ...
- <activity
- android:name="com.buildsystemexample.app.SecondActivity"
- android:label="@string/title_activity_second" >
- </activity>
- </application>
-</manifest>
-</pre></p>
- </li>
-</ol>
-
-
-<h4>Build types </h4>
-<p>Build types represent the build packaging versions generated for each app package. By default,
-the debug and release build types are provided.
-</p>
-
-<pre>
-...
-android {
- ...
- defaultConfig { ... }
- signingConfigs { ... }
- buildTypes { ... }
- productFlavors {...}
- buildTypes {
- release {
- minifyEnabled false
- proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
- }
- debug {
- debuggable true
- }
- }
-}
-...
-</pre>
-
-<p class="note"><strong>Note:</strong> Although only the <em>release</em> build type appears in
-the default <strong>build.gradle</strong> file, both the release and debug build types are
-applied to each build. </p>
-
-<p>In this example, the product flavors and build types create the following build variants:
-<ul>
-<li>demoDebug</li>
-<li>demoRelease</li>
-<li>fullDebug</li>
-<li>fullRelease</li>
-</ul>
-
-<p>To build this example, click the <strong>Build</strong> menu option in Android Studio or invoke
-the <code>assemble</code> task from the command line. </p>
-
-<p class="note"><strong>Note:</strong> The <strong>Build > Make Project</strong> option compiles
-all the source files in the entire project that have been modified since the last compilation. The
-<strong>Build > Rebuild Project</strong> option recomplies all the source files in the project.</p>
-
-<p>Separate output folders are created for each build variant. </p>
+++ /dev/null
-page.title=Building and Running Overview
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/building/building-studio.html">
- Building Your Project from Android Studio</a></li>
- <li><a href="{@docRoot}tools/building/building-cmdline.html">
- Building Your Project from the Command Line</a></li>
- <li><a href="{@docRoot}sdk/installing/studio-build.html">
- Build System</a></li>
- </ol>
-</div>
-</div>
-
-
-<p>The Android build process provides project and module build settings so that
-your Android modules are compiled and packaged into <code>.apk</code> files, the containers
-for your application binaries, based on your build settings. The apk file for each app contains all
-of the information necessary to run your application on a device or emulator, such as compiled
-<code>.dex</code> files (<code>.class</code> files converted to Dalvik byte code), a binary version
-of the <code>AndroidManifest.xml</code> file, compiled resources (<code>resources.arsc</code>) and
-uncompiled resource files for your application.</p>
-
-<p>To run an application on an emulator or device, the application must be signed using debug or
-release mode. You typically want to sign your application in debug mode when you develop and test
-your application, because the build system uses a debug key with a known password so you do not have
-to enter it every time you build. When you are ready to release the application to Google
-Play, you must sign the application in release mode, using your own private key.</p>
-
-<p>If you are using Android development tools, the build system can sign the application for you
-when build your app for debugging. You must obtain a certificate to sign your app when you build
-and app for release. For more information on signing applications, see
-<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
-
-<p>The following diagram depicts the components involved in building and running an application:</p>
-
-<img src="{@docRoot}images/build-simplified.png" />
+++ /dev/null
-page.title=Manifest Merging
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#merge-rules">Merge Conflict Rules</a></li>
- <li><a href="#markers-selectors">Merge Conflict Markers and Selectors</a></li>
- <li><a href="#inject-values">Injecting Build Values into a Manifest</a></li>
- <li><a href="#merge-prodflavorsGroups">Manifest Merging Across Product Flavor Groups</a></li>
- <li><a href="#implicit-permissions">Implicit Permissions</a></li>
- <li><a href="#merge-errors">Handling Manifest Merge Build Errors</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/studio-build.html">Build System Overview</a></li>
- <li><a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a> </li>
- </ol>
-
-</div>
-</div>
-
-
-<p>With Android Studio and <a href="http://www.gradle.org">Gradle</a>-based builds, each app can
-contain manifest files in multiple locations, such as the <code>src/main/</code> folder for
-the <code>productFlavor</code>, libraries, Android ARchive (AAR) bundles of Android Library
-projects, and dependencies. During the build process, manifest merging combines the settings from
-the various <code>AndroidManifest.xml</code> files included in your app into a single, generated APK
-manifest file for app packaging and distribution. Manifest settings are merged based on the manifest
-priority, determined by the manifest's file location. Building your app merges the
-manifest elements, attributes, and sub-elements from these manifests for the specified
-<a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">build variant</a>.</p>
-
-
-<h2 id="merge-rules">Merge Conflict Rules</h2>
-<p>Merge conflicts occur when merged manifests contain the same manifest element but with a
-different attribute value that does not resolve based on the default merge conflict rules.
-<a href="#markers-selectors">Conflict markers and selectors</a> can also define custom merge rules,
-such as allowing an imported library to have a <code>minSdkVersion</code> higher than the
-version defined in the other higher priority manifests. </p>
-
-<p>The manifest merge priority determines which manifest settings are retained in merge conflicts,
-with the settings in higher priority manifest overwriting those in lower priority manifests.
-The following list details which manifest settings are are the highest priority during the merge
-process:</p>
-
-<ul>
- <li>Highest priority: <code>buildType</code> manifest settings </li>
- <li>Higher priority: <code>productFlavor</code> manifest settings </li>
- <li>Medium priority: Manifests in the <code>src/main/</code> directory of an app project</li>
- <li>Low priority: Dependency and library manifest settings </li>
-</ul>
-
-<p>Manifest merge conflicts are resolved at the XML node and
-attribute levels based on the following merge rules. </p>
-
-<table>
- <tr>
- <th scope="col">High Priority Element</th>
- <th scope="col">Low Priority Element</th>
- <th scope="col">Manifest Merge Result</th>
- </tr>
- <tr>
- <td rowspan="3">no attribute</td>
- <td>no attribute</td>
- <td>no attribute</td>
- </tr>
- <tr>
-
- <td>attribute set to default</td>
- <td>default attribute</td>
- </tr>
- <tr>
-
- <td>attribute set to non-default </td>
- <td>low priority attribute</td>
- </tr>
- <tr>
- <td>attribute set to default</td>
- <td rowspan="2">no attribute</td>
- <td>default attribute</td>
- </tr>
- <tr>
- <td>attribute set to non-default </td>
-
- <td>high priority attribute</td>
- </tr>
- <tr>
- <td>attribute set to default</td>
- <td>attribute set to default</td>
- <td>default attribute</td>
- </tr>
- <tr>
- <td>attribute set to default</td>
- <td>attribute set to non-default </td>
- <td>low priority attribute</td>
- </tr>
- <tr>
- <td>attribute set to non-default</td>
- <td>attribute set to default</td>
- <td>high priority attribute</td>
- </tr>
- <tr>
- <td>attribute set to non-default</td>
- <td>attribute set to non-default </td>
- <td>Merge if settings match, otherwise causes conflict error.</td>
- </tr>
- </table>
-
-
-
-<p>Exceptions to the manifest merge rules: </p>
-
-<ul>
- <li>The <code>uses-feature android:required;</code> and
- <code>uses-library android:required</code> elements default to <code>true</code> and use
- an <em>OR</em> merge so that any required feature or library is included in the generated APK. </li>
-
- <li>If not declared, the
- <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code><uses-sdk></code></a>
- elements, <code>minSdkVersion</code> and
- <code>targetSdkVersion</code>, default to a value of 1. When
- merge conflicts occur, the value in the higher priority manifest version is used.</li>
-
- <li>Importing a library with a <code>minSdkVersion</code> value higher than the app's
- <code>src/main/</code> manifest manifest generates an error unless
- the <code>overrideLibrary</code> conflict marker is used.
-
- <p class="note"><strong>Note:</strong> If not explicitly declared, the <code>targetSdkVersion</code>
- defaults to the <code>minSdkVersion</code> value. When no <code><uses-sdk></code> element is
- present in any manifest or the <code>build.gradle</code> file, the
- <code>minSdkVersion</code> defaults to 1.</p> </li>
-
- <li>When importing a library with a <code>targetSdkVersion</code> value lower than the app's
- <code>src/main/</code> manifest, the manifest merge
- process explicitly grants permissions and ensures that the imported library functions properly. </li>
-
- <li>The <code>manifest</code> element only merges with child manifest elements. </li>
-
- <li>The <code>intent-filter</code> element is never changed and is always added to the common
- parent node in the merged manifest. </li>
-</ul>
-
-<p class="caution"><strong>Important:</strong> After the manifests are merged, the build process
-overrides the final manifest settings with any settings that are also in the
-<code>build.gradle</code> file. For more details, see
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>. </p>
-
-
-
-<h2 id="markers-selectors">Merge Conflict Markers and Selectors</h2>
-<p>Manifest markers and selectors override the default merge rules through
-specific conflict resolutions. For example, use a conflict marker to
-merge a library manifest with a higher <code>minSdkVersion</code> value than the higher priority
-manifest, or to merge manifests with the same activity but different <code>android:theme</code>
-values. </p>
-
-<h3 id="conflict-markers">Merge Conflict Markers</h3>
-<p>A merge conflict marker is a special attribute in the Android tools namespace that defines a
-specific merge conflict resolution. Create a conflict marker to avoid a merge conflict error for
-conflicts not resolved by the default merge rules. Supported merge conflict markers include:</p>
-
-<dl>
- <dt><code>merge</code></dt>
- <dd>Merges attributes when there are no conflicts with the merge rules. The default merge
- action.</dd>
- <dt><code>replace</code></dt>
- <dd>Replaces attributes in the lower priority manifest with those from the higher priority
- manifest.</dd>
- <dt><code>strict</code></dt>
- <dd>Sets the merge policy level so that merged elements with same attributes, but different
- values generate a build failure, unless resolved through the conflict rules.</dd>
- <dt><code>merge-only</code></dt>
- <dd>Allows merge actions for only lower priority attributes.</dd>
- <dt><code>remove</code></dt>
- <dd>Removes the specified lower priority element from the merged manifest.</dd>
- <dt><code>remove-All</code></dt>
- <dd>Removes all lower priority elements of the same node type from the merged manifest.</dd>
-</dl>
-
-
-<p>By default, the manifest merge process applies the <code>merge</code> conflict marker to
-the node level. All declared manifest attributes default to a <code>strict</code>
-merging policy. </p>
-
-<p>To set a merge conflict marker, first declare the namespace in the
-<code>AndroidManifest.xml</code> file. Then, enter the merge conflict marker in the manifest to
-specify a custom merge conflict action. This example inserts the <code>replace</code> marker to
-set a replace action to resolve conflicts between the <code>android:icon</code> and
-<code>android:label</code> manifest elements. </p>
-
-<pre>
-
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.android.tests.flavorlib.app"
- xmlns:tools="http://schemas.android.com/tools">
-
- <application
- android:icon="@drawable/icon"
- android:label="@string/app_name"
- tools:replace="icon, label">
- ...
-
-</manifest>
-
-</pre>
-
-
-<h4>Marker attributes</h4>
-<p>Conflict markers use <code>tools:node</code> and <code>tools:attr</code> attributes to
-restrict merge actions at the XML node or attribute level. </p>
-
-<p>The <code>tools:attr</code> markers use only the <code>restrict</code>, <code>remove</code>, and
-<code>replace</code> merge actions. Multiple <code>tools:attr</code> marker values can be applied
-to a specific element. For example, use <code>tools:replace="icon, label, theme"</code> to replace
-lower priority <code>icon</code>, <code>label</code>, and <code>theme</code> attributes. </p>
-
-
-<h4>Merge conflict marker for imported libraries</h4>
-<p>The <code>overrideLibrary</code> conflict marker applies to the <code><uses-sdk></code>
-manifest declaration and is used to import a library even though the library's
-<code><uses-sdk></code> values, such as <code>minSdkVersion</code>
-are set to different values than those in the other higher priority manifests. </p>
-
-<p>Without this marker, library manifest merge conflicts from the
-<code><uses-sdk></code> values cause the merge process to fail.</p>
-
-<p>This example applies the <code>overrideLibrary</code> conflict marker to resolve the merge
-conflict between <code>minSdkVersion</code> values in the <code>src/main/</code> manifest and an
-imported library manifest.
-
-
-<p><code>src/main/</code> manifest: </p>
-<pre>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.android.example.app"
- xmlns:tools="http://schemas.android.com/tools">
- ...
- <uses-sdk android:targetSdkVersion="22" android:minSdkVersion="2"
- tools:overrideLibrary="com.example.lib1, com.example.lib2"/>
- ...
-</pre>
-
-<p>Library manifest: </p>
-
-<pre>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.example.lib1">
- ...
- <uses-sdk android:minSdkVersion="4" />
- ...
- </manifest>
-</pre>
-
-<p class="note"><strong>Note:</strong> The default merge process does not allow importing a library
-with a higher <code>minSdkVersion</code> than the app's <code>src/main/</code> manifest unless
-the <code>overrideLibrary</code> conflict marker is used. </p>
-
-
-
-<h3 id="marker-selectors">Marker Selectors</h3>
-<p>Marker selectors limit a merge action to a specific lower priority manifest. For example, a
-marker selector can be used to remove a permission from only one library, while allowing the
-same permission from other libraries.</p>
-
-<p>This example uses the <code>tools:node</code> marker to remove the <code>permisionOne</code>
-attribute, while the <code>tools:selector</code> selector specifies the specific library as
-<em>com.example.lib1</em>. The <code>permisionOne</code> permission is filtered from only the
-<code>lib1</code> library manifests. </p>
-
-<pre>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.android.example.app"
- xmlns:tools="http://schemas.android.com/tools">
- ...
- <permission
- android:name="permissionOne"
- tools:node="remove"
- tools:selector="com.example.lib1">
- ...
-</pre>
-
-
-
-<h2 id="inject-values">Injecting Build Values into a Manifest</h2>
-<p>Manifest merging can also be configured to use manifest placeholders to inject
-property values from the <code>build.gradle</code> file into the manifest attributes. </p>
-
-<p>Manifest placeholders use the syntax <code>${name}</code> for attribute values, where
-<code>name</code> is the injected <code>build.gradle</code> property. The <code>build.gradle</code>
-file uses the <code>manifestPlaceholders</code> property to define the placeholder values. </p>
-
-<p class="note"><strong>Note:</strong> Unresolved placeholder names in apps cause build failures.
-Unresolved placeholder names in libraries generate warnings and need to be resolved when importing
-the library into an app.</p>
-
-<p>This example shows the manifest placeholder <code>${applicationId}</code> used to inject the
-<code>build.gradle</code> <code>applicationId</code> property value in to <code>android:name</code>
-attribute value. </p>
-
-<p class="note"><strong>Note:</strong> Android Studio provides a default
-<code>${applicationId}</code> placeholder for the <code>build.gradle</code>
-<code>applicationId</code> value that is not shown in the build file.
-When building an AAR (Android ARchive) package for library modules, do not provide an
-automatic <code>@{applicationId}</code> placeholder in the
-<a href="{@docRoot}tools/building/manifest-merge.html">manifest merge</a> settings.
-Instead, use a different placeholder, such as <code>@{libApplicationId}</code> and
-provide a value for it if you want to include application Ids in the archive library. </p>
-
-
-<p>Manifest entry:</p>
-
-<pre>
-
-<activity
-android:name=".Main">
- <intent-filter>
- <action android:name="${applicationId}.foo">
- </action>
-</intent-filter>
-</activity>
-
-</pre>
-
-
-<p>Gradle build file:</p>
-
-<pre>
-android {
- compileSdkVersion 22
- buildToolsVersion "22.0.1"
-
- productFlavors {
- flavor1 {
- applicationId = "com.mycompany.myapplication.productFlavor1"
- }
-}
-
-</pre>
-
-<p>Merged manifest value: </p>
-
-<pre>
-<action android:name="com.mycompany.myapplication.productFlavor1.foo">
-</pre>
-
-
-<p>The manifest placeholder syntax and build file <code>manifestPlaceholders</code>
-property can be used to inject other manifest values. For properties other than the
-<code>applicationId</code>, the <code>manifestPlaceholders</code> property is explicitly declared
-in the <code>build.gradle</code> file. This example shows the manifest placeholder for injecting
-<code>activityLabel</code> values.</p>
-
-<p>Gradle build file: </p>
-
-<pre>
-android {
- defaultConfig {
- manifestPlaceholders = [ activityLabel:"defaultName"]
- }
- productFlavors {
- free {
- }
- pro {
- manifestPlaceholders = [ activityLabel:"proName" ]
- }
- }
-
-</pre>
-
-<p>Placeholder in the manifest file: </p>
-
-<pre>
-<activity android:name=".MainActivity" android:label="${activityLabel}" >
-</pre>
-
-<p class="note"><strong>Note:</strong> The placeholder value supports partial value injection,
-for example <code>android:authority="com.acme.${localApplicationId}.foo"</code>. </p>
-
-
-
-<h2 id="merge-prodflavorsGroups">Manifest Merging Across Product Flavor Groups</h2>
-
-<p>When using the <code>GroupableProductFlavor</code> property, the manifest merge
-priority of any manifests in the product flavor groups follows the order in which the
-product flavor groups are listed in the build file. The manifest merge process creates a single
-merged manifest for the product flavor groups based on the configured build variant. </p>
-
-<p>For example, if a build variant references the product flavors <code>x86</code>,
-<code>mdpi</code>, <code>21</code>, and <code>paid</code> from the respective product flavor
-groups <code>ABI</code>, <code>Density</code>, <code>API</code>, and <code>Prod</code>, listed
-in this order in the <code>build.gradle</code> file, then the manifest merge process merges the
-manifests in this priority order, which follows how the product flavors are listed in the build
-file.</p>
-
-<p>To illustrate this example, the following table shows how the product flavors are listed for
-each product flavor group. This combination of product flavors and groups defines the
-build variant. </p>
-<table>
- <tr>
- <th scope="col">Product Flavor Group</th>
- <th scope="col">Product Flavor</th>
- <tr>
- <td>ABI</td>
- <td>x86</td>
- </tr>
- <tr>
- <td>density</td>
- <td>mdpi</td>
- </tr>
- <tr>
- <td>API</td>
- <td>22</td>
- </tr>
- <tr>
- <td>prod</td>
- <td>paid</td>
- </tr>
-</table>
-
-<p>Manifest merge order:</p>
-
- <ul>
- <li>prod-paid AndroidManifest.xml (lowest priority) merges into API-22 AndroidManifest.xml</li>
- <li>API-22 AndroidManifest.xml merges into density-mpi AndroidManifest.xml</li>
- <li>density-mpi AndroidManifest.xml merges into ABI-x86 AndroidManifest.xml (highest priority)</li>
- </ul>
-
-
-<h2 id="implicit-permissions">Implicit Permissions</h2>
-<p>Importing a library that targets an Android runtime with implicitly
-granted permissions may automatically add the permissions to the resulting merged manifest.
-For example, if an application with a <code>targetSdkVersion</code> of 16 imports a library with a
-<code>targetSdkVersion</code> of 2, Android Studio adds the <code>WRITE_EXTERNAL_STORAGE</code>
-permission to ensure permission compatibility across the SDK versions.
-
-<p class="note"><strong>Note:</strong> More recent Android releases replace implicit
-permissions with permission declarations.</p>
-
-
-This table lists the importing library versions and the declared permissions.
-</p>
-
- <table>
- <tr>
- <th>Importing this library version</th>
- <th>Declares this permission in the manifest </th>
- </tr>
- <tr>
- <td><code>targetSdkVersion</code> < 2 </td>
- <td><code>WRITE_EXTERNAL_STORAGE</code> </td>
- </tr>
- <tr>
- <td><code>targetSdkVersion</code> < 4 </td>
- <td><code>WRITE_EXTERNAL_STORAGE</code>, <code>READ_PHONE_STATE</code> </td>
- </tr>
- <tr>
- <td>Declared <code>WRITE_EXTERNAL_STORAGE</code></td>
- <td><code>READ_EXTERNAL_STORAGE</code></td>
- </tr>
- <tr>
- <td><code>targetSdkVersion</code> < 16 and using the <code>READ_CONTACTS</code>
- permission</td>
- <td><code>READ_CALL_LOG</code></td>
- </tr>
- <tr>
- <td><code>targetSdkVersion</code> < 16 and using the <code>WRITE_CONTACTS</code>
- permission</td>
- <td><code>WRITE_CALL_LOG</code></td>
- </tr>
- </table>
-
-
-
-<h2 id="merge-errors">Handling Manifest Merge Build Errors</h2>
-<p>During the build process, the manifest merge process stores a record of each merge transaction
-in the <code>manifest-merger-<productFlavor>-report.txt</code> file in the module
-<code>build/outputs/logs</code> folder. A different log file is generated for each of the
-module's build variants. </p>
-
-<p>When a manifest merge build error occurs, the merge process records the error message
-describing the merge conflict in the log file. For example, the
-<code>android:screenOrientation</code> merge conflict between the following manifests causes
-a build error. </p>
-
-<p>Higher priority manifest declaration: </p>
-
-<pre>
-<activity
- android:name="com.foo.bar.ActivityOne"
- android:screenOrientation="portrait"
- android:theme="@theme1"/>
-</pre>
-
-<p>Lower priority manifest declaration: </p>
-
-<pre>
-<activity
- android:name="com.foo.bar.ActivityOne"
- android:screenOrientation="landscape"/>
-</pre>
-
-<p>Error log:</p>
-
-<pre>
-/project/app/src/main/AndroidManifest.xml:3:9 Error:
- Attribute activity@screenOrientation value=(portrait) from AndroidManifest.xml:3:9
- is also present at flavorlib:lib1:unspecified:3:18 value=(landscape)
- Suggestion: add 'tools:replace="icon"' to <activity> element at AndroidManifest.xml:1:5 to override
-</pre>
-
-
+++ /dev/null
-page.title=Building Apps with Over 64K Methods
-page.tags="65536","references","max","65k","dex","64k","multidex","multi-dex","methods"</p>
-
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#about">
- About the 64K Reference Limit</a>
- <ol>
- <li><a href="#mdex-pre-l">Multidex support prior to Android 5.0</a></li>
- <li><a href="#mdex-on-l">Multidex support for Android 5.0 and higher</a></li>
- </ol>
- </li>
- <li><a href="#avoid">
- Avoiding the 64K Limit</a></li>
- <li><a href="#mdex-gradle">
- Configuring Your App for Multidex with Gradle</a>
- <ol>
- <li><a href="#limitations">
- Limitations of the multidex support library</a></li>
- </ol>
- </li>
- <li><a href="#dev-build">
- Optimizing Multidex Development Builds</a>
- <ol>
- <li><a href="#variants-studio">
- Using Build Variants in Android Studio</a></li>
- </ol>
- </li>
- <li><a href="#testing">
- Testing Multidex Apps</a></li>
- </ol>
-
- <h2>See Also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/proguard.html">ProGuard</a>
- </li>
- </ol>
- </div>
-</div>
-
-
-<p>
- As the Android platform has continued to grow, so has the size of Android apps. When your
- application and the libraries it references reach a certain size, you encounter build errors that
- indicate your app has reached a limit of the Android app build architecture. Earlier versions of
- the build system report this error as follows:
-</p>
-
-<pre>
-Conversion to Dalvik format failed:
-Unable to execute dex: method ID not in [0, 0xffff]: 65536
-</pre>
-
-<p>
- More recent versions of the Android build system display a different error, which is an
- indication of the same problem:
-</p>
-
-<pre>
-trouble writing output:
-Too many field references: 131000; max is 65536.
-You may try using --multi-dex option.
-</pre>
-
-<p>
- Both these error conditions display a common number: 65,536. This number is significant in that
- it represents the total number of references that can be invoked by the code within a single
- Dalvik Executable (dex) bytecode file. If you have built an Android app and received this error,
- then congratulations, you have a lot of code! This document explains how to move past this
- limitation and continue building your app.
-</p>
-
-<p class="note">
- <strong>Note:</strong> The guidance provided in this document supersedes the guidance given in
- the Android Developers blog post <a href=
- "http://android-developers.blogspot.com/2011/07/custom-class-loading-in-dalvik.html">Custom Class
- Loading in Dalvik</a>.
-</p>
-
-
-<h2 id="about">About the 64K Reference Limit</h2>
-
-<p>
- Android application (APK) files contain executable bytecode files in the form
- of <a href="https://source.android.com/devices/tech/dalvik/">Dalvik</a>
- Executable (DEX) files, which contain the compiled code used to run your app.
- The Dalvik Executable specification limits the total number of methods that
- can be referenced within a single DEX file to 65,536—including Android
- framework methods, library methods, and methods in your own code. In the
- context of computer science, the term <a class="external-link" href=
- "https://en.wikipedia.org/wiki/Kilo-"><em>Kilo, K</em></a>, denotes 1024 (or
- 2^10). Because 65,536 is equal to 64 X 1024, this limit is referred to as the
- '64K reference limit'.
-</p>
-
-<p>
- Getting past this limit requires that you configure your app build process to
- generate more than one DEX file, known as a <em>multidex</em> configuration.
-</p>
-
-<h3 id="mdex-pre-l">Multidex support prior to Android 5.0</h3>
-
-<p>
- Versions of the platform prior to Android 5.0 (API level 21) use the Dalvik
- runtime for executing app code. By default, Dalvik limits apps to a single
- classes.dex bytecode file per APK. In order to get around this limitation,
- you can use the <a href=
- "{@docRoot}tools/support-library/features.html#multidex">multidex support
- library</a>, which becomes part of the primary DEX file of your app and then
- manages access to the additional DEX files and the code they contain.
-</p>
-
-<p class="note">
- <strong>Note:</strong> If your project is configured for multidex with
- <code>minSdkVersion 20</code> or lower, and you deploy to target devices
- running Android 4.4 (API level 20) or lower, Android Studio disables <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">Instant Run</a>.
-</p>
-
-<h3 id="mdex-on-l">Multidex support for Android 5.0 and higher</h3>
-
-<p>
- Android 5.0 (API level 21) and higher uses a runtime called ART which
- natively supports loading multiple dex files from application APK files. ART
- performs pre-compilation at application install time which scans for
- classes(..N).dex files and compiles them into a single .oat file for
- execution by the Android device. For more information on the Android 5.0
- runtime, see <a href=
- "https://source.android.com/devices/tech/dalvik/art.html">Introducing
- ART</a>.
-</p>
-
-<p class="note">
- <strong>Note:</strong> While using <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">Instant Run</a>,
- Android Studio automatically configures your app for multidex when your app's
- <code>minSdkVersion</code> is set to 21 or higher. Because Instant Run only
- works with the debug version of your app, you still need to configure your
- release build for multidex to avoid the 64K limit.
-</p>
-
-<h2 id="avoid">Avoiding the 64K Limit</h2>
-
-<p>
- Before configuring your app to enable use of 64K or more method references, you should take steps
- to reduce the total number of references called by your app code, including methods defined by
- your app code or included libraries. The following strategies can help you avoid hitting the dex
- reference limit:
-</p>
-
-<ul>
- <li>
- <strong>Review your app's direct and transitive dependencies</strong> - Ensure any large library
- dependency you include in your app is used in a manner that outweighs the amount of code
- being added to the application. A common anti-pattern is to include a very large library
- because a few utility methods were useful. Reducing your app code dependencies can often help
- you avoid the dex reference limit.
- </li>
- <li>
- <strong>Remove unused code with ProGuard</strong> - Configure the <a href=
- "{@docRoot}tools/help/proguard.html">ProGuard</a> settings for your app to run ProGuard and
- ensure you have shrinking enabled for release builds. Enabling shrinking ensures you
- are not shipping unused code with your APKs.
- </li>
-</ul>
-
-
-<p>
- Using these techniques can help you avoid the build configuration changes required to enable more
- method references in your app. These steps can also decrease the size of your APKs, which is
- particularly important for markets where bandwidth costs are high.
-</p>
-
-
-<h2 id="mdex-gradle">Configuring Your App for Multidex with Gradle</h2>
-
-<p>
- The Android plugin for Gradle available in Android SDK Build Tools 21.1 and higher supports
- multidex as part of your build configuration. Make sure you update the Android SDK Build Tools
- tools and the Android Support Repository to the latest version using the <a href=
- "{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> before attempting to configure your app
- for multidex.
-</p>
-
-<p>
- Setting up your app development project to use a multidex configuration requires that you make a
- few modifications to your app development project. In particular you need to perform the
- following steps:
-</p>
-
-<ul>
- <li>Change your Gradle build configuration to enable multidex</li>
- <li>Modify your manifest to reference the {@link android.support.multidex.MultiDexApplication}
- class</li>
-</ul>
-
-<p>
- Modify the module-level <code>build.gradle</code> file configuration to
- include the support library and enable multidex output, as shown in the
- following code snippet:
-</p>
-
-<pre>
-android {
- compileSdkVersion 21
- buildToolsVersion "21.1.0"
-
- defaultConfig {
- ...
- minSdkVersion 14
- targetSdkVersion 21
- ...
-
- // Enabling multidex support.
- multiDexEnabled true
- }
- ...
-}
-
-dependencies {
- compile 'com.android.support:multidex:1.0.0'
-}
-</pre>
-
-<p>
- In your manifest add the {@link android.support.multidex.MultiDexApplication} class from the
- multidex support library to the application element.
-</p>
-
-<pre>
-<?xml version="1.0" encoding="utf-8"?>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.example.android.multidex.myapplication">
- <application
- ...
- android:name="android.support.multidex.MultiDexApplication">
- ...
- </application>
-</manifest>
-</pre>
-
-<p>
- When these configuration settings are added to an app, the Android build tools construct a
- primary dex (classes.dex) and supporting (classes2.dex, classes3.dex) as needed. The build system
- will then package them into an APK file for distribution.
-</p>
-
-<p class="note">
- <strong>Note:</strong> If your app uses extends the {@link android.app.Application} class, you
- can override the attachBaseContext() method and call MultiDex.install(this) to enable multidex.
- For more information, see the {@link android.support.multidex.MultiDexApplication} reference
- documentation.
-</p>
-
-<h3 id="limitations">Limitations of the multidex support library</h3>
-
-<p>
- The multidex support library has some known limitations that you should be aware of and test for
- when you incorporate it into your app build configuration:
-</p>
-
-<ul>
- <li>The installation of .dex files during startup onto a device's data partition is complex and
- can result in Application Not Responding (ANR) errors if the secondary dex files are large. In
- this case, you should apply code shrinking techniques with ProGuard to minimize the size of dex
- files and remove unused portions of code.
- </li>
-
- <li>Applications that use multidex may not start on devices that run versions of the platform
- earlier than Android 4.0 (API level 14) due to a Dalvik linearAlloc bug (Issue <a href=
- "http://b.android.com/22586">22586</a>). If you are targeting API levels earlier than 14, make
- sure to perform testing with these versions of the platform as your application can have issues
- at startup or when particular groups of classes are loaded. Code shrinking can reduce or possibly
- eliminate these potential issues.
- </li>
-
- <li>Applications using a multidex configuration that make very large memory allocation
- requests may crash during run time due to a Dalvik linearAlloc limit (Issue <a href=
- "http://b.android.com/78035">78035</a>). The allocation limit was increased in Android 4.0 (API
- level 14), but apps may still run into this limit on Android versions prior to
- Android 5.0 (API level 21).
- </li>
-
- <li>There are complex requirements regarding what classes are needed in the primary dex file when
- executing in the Dalvik runtime. The Android build tooling updates handle the Android
- requirements, but it is possible that other included libraries have additional dependency
- requirements including the use of introspection or invocation of Java methods from native code.
- Some libraries may not be able to be used until the multidex build tools are updated to allow you
- to specify classes that must be included in the primary dex file.
- </li>
-</ul>
-
-
-<h2 id="dev-build">Optimizing Multidex Development Builds</h2>
-
-<p>
- A multidex configuration requires significantly increased build processing time because the build
- system must make complex decisions about what classes must be included in the primary DEX file
- and what classes can be included in secondary DEX files. This means that routine builds performed
- as part of the development process with multidex typically take longer and can potentially slow
- your development process.
-</p>
-
-<p>
- In order to mitigate the typically longer build times for multidex output, you should create two
- variations on your build output using the Android plugin for Gradle
- <a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Product-flavors">
- {@code productFlavors}</a>: a development flavor and a production flavor.
-</p>
-
-<p>
- For the development flavor, set a minimum SDK version of 21. This setting generates multidex
- output much faster using the ART-supported format. For the release flavor, set a minimum SDK
- version which matches your actual minimum support level. This setting generates a multidex APK
- that is compatible with more devices, but takes longer to build.
-</p>
-
-<p>
- The following build configuration sample demonstrates the how to set up these flavors in a Gradle
- build file:
-</p>
-
-<pre>
-android {
- productFlavors {
- // Define separate dev and prod product flavors.
- dev {
- // dev utilizes minSDKVersion = 21 to allow the Android gradle plugin
- // to pre-dex each module and produce an APK that can be tested on
- // Android Lollipop without time consuming dex merging processes.
- minSdkVersion 21
- }
- prod {
- // The actual minSdkVersion for the application.
- minSdkVersion 14
- }
- }
- ...
- buildTypes {
- release {
- runProguard true
- proguardFiles getDefaultProguardFile('proguard-android.txt'),
- 'proguard-rules.pro'
- }
- }
-}
-dependencies {
- compile 'com.android.support:multidex:1.0.0'
-}
-</pre>
-
-<p>
- After you have completed this configuration change, you can use the <code>devDebug</code> variant
- of your app, which combines the attributes of the <code>dev</code> productFlavor and the
- <code>debug</code> buildType. Using this target creates a debug app with proguard disabled,
- multidex enabled, and minSdkVersion set to Android API level 21. These settings cause the Android
- gradle plugin to do the following:
-</p>
-
-<ol>
- <li>Build each module of the application (including dependencies) as separate dex files. This is
- commonly referred to as pre-dexing.
- </li>
-
- <li>Include each dex file in the APK without modification.
- </li>
-
- <li>Most importantly, the module dex files will not be combined, and so the long-running
- calculation to determine the contents of the primary dex file is avoided.
- </li>
-</ol>
-
-<p>
- These settings result in fast, incremental builds, because only the dex files of modified modules
- are recomputed and repackaged into the APK file. The APK that results from these builds can be
- used to test on Android 5.0 devices only. However, by implementing the configuration as a flavor,
- you preserve the ability to perform normal builds with the release-appropriate minimum SDK level
- and proguard settings.
-</p>
-
-<p>
- You can also build the other variants, including a <code>prodDebug</code> variant
- build, which takes longer to build, but can be used for testing outside of development.
- Within the configuration shown, the <code>prodRelease</code> variant would be the final testing
- and release version. If you are executing gradle tasks from the command line, you can use
- standard commands with <code>DevDebug</code> appended to the end (such as <code>./gradlew
- installDevDebug</code>). For more information about using flavors with Gradle tasks, see the
- <a href="http://tools.android.com/tech-docs/new-build-system/user-guide">Gradle Plugin User
- Guide</a>.
-</p>
-
-<p>
- <strong>Tip:</strong> You can also provide a custom manifest, or a custom application class for each
- flavor, allowing you to use the support library MultiDexApplication class, or calling
- MultiDex.install() only for the variants that need it.
-</p>
-
-
-<h3 id="variants-studio">Using Build Variants in Android Studio</h3>
-
-<p>
- Build variants can be very useful for managing the build process when using multidex. Android
- Studio allows you to select these build variants in the user interface.
-</p>
-
-<p>
- To have Android Studio build the "devDebug" variant of your app:
-</p>
-
-<ol>
- <li>Open the <em>Build Variants</em> window from the left-sidebar. The option is located next to
- <em>Favorites</em>.
- </li>
-
- <li>Click the name of the build variant to select a different variant, as shown in Figure 1.
- </li>
-</ol>
-
-<img src="{@docRoot}images/tools/studio-build-variant.png" alt="" height="XXX" id="figure1">
-<p class="img-caption">
- <strong>Figure 1.</strong> Screen shot of the Android Studio left panel showing a build variant.
-</p>
-
-<p class="note">
- <strong>Note</strong>: The option to open this window is only available after you have
- successfully synchronized Android Studio with your Gradle build file using the <strong>Tools >
- Android > Sync Project with Gradle Files</strong> command.
-</p>
-
-
-<h2 id="testing">Testing Multidex Apps</h2>
-
-<p>
- When using instrumentation tests with multidex apps, additional configuration is required to
- enable the test instrumentation. Because the location of code for classes in multidex apps is not
- within a single DEX file, instrumentation tests do not run properly unless configured for
- multidex.
-</p>
-
-<p>
- To test a multidex app with instrumentation tests, configure the
- <a href="{@docRoot}reference/com/android/test/runner/MultiDexTestRunner.html">
- MultiDexTestRunner</a> from the multidex testing support library. The following sample
- {@code build.gradle} file demonstrates how to configure your build to use this test runner:
-</p>
-
-<pre>
-android {
- defaultConfig {
- ...
- testInstrumentationRunner "com.android.test.runner.MultiDexTestRunner"
- }
-}
-</pre>
-
-<p class="note">
- <strong>Note:</strong> With Android Plugin for Gradle versions lower than 1.1, you need to add
- the following dependency for <code>multidex-instrumentation</code>:
-<pre>
-dependencies {
- androidTestCompile('com.android.support:multidex-instrumentation:1.0.1') {
- exclude group: 'com.android.support', module: 'multidex'
- }
-}
-</pre>
-</p>
-
-
-<p>
- You may use the instrumentation test runner class directly or extend it to fit your testing
- needs. Alternatively, you can override onCreate in existing instrumentations like this:
-</p>
-
-<pre>
-public void onCreate(Bundle arguments) {
- MultiDex.install(getTargetContext());
- super.onCreate(arguments);
- ...
-}
-</pre>
-
-<p class="note">
- <strong>Note:</strong> Use of multidex for creating a test APK is not currently supported.
-</p>
+++ /dev/null
-page.title=Android Plugin for Gradle
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-<h2>In this document</h2>
-<ol>
- <li><a href="#buildConf">Build Configuration</a></li>
- <li><a href="#buildConv">Build by Convention</a></li>
- <li><a href="#projectModules">Project and Module Settings</a></li>
- <li><a href="#dependencies">Dependencies</a></li>
- <li><a href="#buildTasks">Build Tasks</a></li>
- <li><a href="#gradleWrapper">Gradle Wrapper</a></li>
- <li><a href="#buildVariants">Build Variants</a></li>
-</ol>
-
-<h2>Reference</h2>
-<ul>
- <li>
- <a class="external-link" href="http://google.github.io/android-gradle-dsl">
- Android Plugin DSL</a>
- </li>
-</ul>
-
-<h2>See also</h2>
-<ul>
-<li><a href="{@docRoot}sdk/installing/studio-build.html">
-Build System Overview</a></li>
-<li><a href="{@docRoot}tools/building/index.html">
-Building and Running</a></li>
-<li><a href="{@docRoot}tools/building/building-studio.html">
-Building and Running from Android Studio</a></li>
-</ul>
-
-</div>
-</div>
-
-<p>The Android build system consists of an Android plugin for <em>Gradle</em>.
-<a href="http://www.gradle.org/">Gradle</a> is an advanced build toolkit that manages
-dependencies and allows you to define custom build logic. Android Studio uses a Gradle wrapper
-to fully integrate the Android plugin for Gradle. The Android plugin for Gradle also runs
-independent of Android Studio. This means that you can build your Android apps from within Android
-Studio and from the command line on your machine or on machines where Android Studio is not installed
-(such as continuous integration servers).</p>
-
-<p>The output of the build is the same whether you are building a project from the command line,
-on a remote machine, or using Android Studio.</p>
-
-<h2 id="buildConf">Build Configuration</h2>
-
-<p>The build configuration for your project is defined inside <code>build.gradle</code> files,
-which are plain text files that use the syntax and options from Gradle and the Android plugin
-to configure the following aspects of your build:</p>
-
-<ul>
- <li><em>Build variants</em>. The build system can generate multiple APKs with different
- product and build configurations for the same module. This is useful when you want to
- build different versions of your application without having to create a separate projects
- or modules for each version.</li>
- <li><em>Dependencies</em>. The build system manages project dependencies and supports
- dependencies from your local filesystem and from remote repositories. This prevents you
- from having to search, download, and copy binary packages for your dependencies into your
- project directory.</li>
- <li><em>Manifest entries</em>. The build system enables you to specify values for some
- elements of the manifest file in the build variant configuration. These build values
- override the existing values in the manifest file. This is useful if you want to generate
- multiple APKs for your modules where each of the <code>apk</code> files has a different
- application name, minimum SDK version, or target SDK version. When multiple manifests are
- present, manifest settings are merged in priority of buildType and productFlavor,
- <code>/main</code> manifest, and the library manifests.</li>
- <li><em>Signing</em>. The build system enables you to specify signing settings in the build
- configuration, and it can sign your APKs during the build process.</li>
- <li><em>ProGuard</em>. The build system enables you to specify a different
- <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> rules
- file for each build variant. The build system can run ProGuard to obfuscate your classes
- during the build process.</li>
- <li><em>Testing</em>. For most templates, the build system creates a test directory,
- <em>androidTest</em> and generates a test APK from the test sources in your project, so
- you do not have to create a separate test project. The build system can also run your tests
- during the build process.</li>
-</ul>
-
-<p>Gradle build files use Domain Specific Language (DSL) to describe and manipulate the build logic
-through <em>Groovy</em> syntax. <a href="http://groovy.codehaus.org/">Groovy</a> is a dynamic
-language that you can use to define custom build logic and to interact with the Android-specific
-elements provided by the Android plugin for Gradle.</p>
-
-<h2 id="buildConv">Build by Convention</h2>
-
-<p>The Android Studio build system assumes <em>sensible defaults</em> for the project structure
-and other build options. If your project adheres to these conventions, your Gradle build files are
-very simple. When some of these conventions do not apply to your project, the flexibility of the
-build system allows you to configure almost every aspect of the build process. For example, if
-you need to replace the default source folders in your module directories, you can configure a new
-directory structure in the module's build file. </p>
-
-<h2 id="projectModules">Project and Module Settings</h2>
-
-<p>A <em>project</em> in Android Studio represents the top-level Android development structure.
-Android Studio projects contain project files and one or more application modules. A
-<em>module</em> is a component of your app that you can build, test, or debug independently.
-Modules contain the source code and resources for your apps. Android Studio projects can contain
-several kinds of modules:</p>
-
-<ul>
- <li><em>Android application modules</em> contain application (mobile, TV, Wear, Glass) code and
- may depend on library modules, although many Android apps consist of only one application
- module. The build system generates APK packages for application modules. </li>
- <li><em>Android library modules</em> contain reusable Android-specific code and resources.
- The build system generates an AAR (Android ARchive) package for library modules.</li>
- <li><em>App Engine modules</em> contain code and resources for App Engine integration.</li>
- <li><em>Java library modules</em> contain reusable code. The build system generates a
- JAR package for Java library modules.</li>
-</ul>
-
-<p>Android Studio projects contain a top-level project Gradle build file that allows you to add the
-configuration options common to all application modules in the project. Each application module
-also has its own build.gradle file for build settings specific to that module.</p>
-
-<h3 id="projectBuildFile">Project Build File</h3>
-<p>By default, the project-level Gradle file uses <em>buildscript</em> to define the Gradle
-<em>repositories</em> and <em>dependencies</em>. This allows different projects to use different
-Gradle versions. Supported repositories include JCenter, Maven Central, or Ivy. This example
-declares that the build script uses the JCenter repository and a classpath dependency artifact
-that contains the Android plugin for Gradle version 1.0.1.
-</p>
-<p>
-<pre>
-buildscript {
- repositories {
- jcenter()
- }
- dependencies {
- classpath 'com.android.tools.build:gradle:1.0.1'
-
- // NOTE: Do not place your application dependencies here: they belong
- // in the individual module build.gradle files
- }
-}
-
-allprojects {
- repositories {
- jcenter()
- }
-}
-</pre>
-
-<p class="note"><strong>Note:</strong> The SDK location for the Android Studio project is defined in
-the <em>local.properties</em> file in the <code>sdk.dir<sdk location></code> setting or through an
-<code>ANDROID_HOME</code> environment variable.</p>
-
-<h3 id="moduleBuildFile">Module Build File</h3>
-<p>The application module Gradle build file allows you to configure module build settings,
-including overriding the <code>src/main</code> manifest settings and setting custom packaging
-options. </p>
-
-<ul>
- <li>android settings </li>
- <ul>
- <li>compileSdkVersion</li>
- <li>buildToolsVersion</li>
- </ul>
-
- <li>defaultConfig and productFlavors </li>
- <ul>
- <li>manifest properties such as applicationId, minSdkVersion, targetSdkVersion, and test
- information</li>
- </ul>
-
- <li>buildTypes</li>
- <ul>
- <li>build properties such as debuggable, ProGuard enabling, debug signing, version name
- suffix and testinformation</li>
- </ul>
-
- <li>dependencies</li>
-</ul>
-
-<p>This example applies the Android plugin, uses the default configuration to override several
-manifest properties, creates two build types: release and debug, and declares several dependencies.
-</p>
-
-<pre>
-apply plugin: 'com.android.application'
-
-android {
- compileSdkVersion 20
- buildToolsVersion "20.0.0"
-
- defaultConfig {
- applicationId "com.mycompany.myapplication"
- minSdkVersion 13
- targetSdkVersion 20
- versionCode 1
- versionName "1.0"
- }
-
- buildTypes {
- release {
- minifyEnabled false
- proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
- }
- debug {
- debuggable true
- }
- }
-}
-
-dependencies {
- compile fileTree(dir: 'libs', include: ['*.jar'])
- compile 'com.android.support:appcompat-v7:20.0.0'
- compile project(path: ':app2, configuration: 'android-endpoints')
-}
-</pre>
-
-
-<p class="note"><strong>Note:</strong> You can inject custom build logic for property values defined
-by a function that gets called by the property, for example:
-<pre>
-def computeVersionName() {
- ...
-}
-
-android {
- defaultConfig {
- versionName computeVersionName()
- ...
- }
-}
-</pre>
-</p>
-
-
-
-<h2 id="dependencies">Dependencies</h2>
-
-<p>The Android Studio build system manages project dependencies and supports module dependencies,
-local binary dependencies, and remote binary dependencies.</p>
-
-<dl>
- <dt><em>Module Dependencies</em></dt>
- <dd><p>An application module can include in its build file a list of other modules it depends on.
- When you build this module, the build system assembles and includes the required
- modules.</p></dd>
- <dt><em>Local Dependencies</em></dt>
- <dd><p>If you have binary archives in your local filesystem that a module depends on, such as
- JAR files, you can declare these dependencies in the build file for that module.</p></dd>
- <dt><em>Remote Dependencies</em></dt>
- <dd><p>When some of your dependencies are available in a remote repository, you do not have
- to download them and copy them into your project. The Android Studio build system supports
- remote dependencies from repositories, such as <a href="http://maven.apache.org/">Maven</a>,
- and dependency managers, such as <a href="http://ant.apache.org/ivy/">Ivy</a>. </p>
- <p>Many popular software libraries and tools are available in public Maven repositories.
- For these dependencies you only have to specify their Maven coordinates, which uniquely
- identify each element in a remote repository. The format for Maven coordinates used in the
- build system is <code>group:name:version</code>. For example, the Maven coordinates for
- version 16.0.1 of the Google Guava libraries are
- <code>com.google.guava:guava:16.0.1</code>.</p>
- <p>The <a href="http://search.maven.org">Maven Central Repository</a> is widely used to
- distribute many libraries and tools.</p>
- </dd>
-</dl>
-
-<h2 id="buildTasks">Build Tasks</h2>
-
-<p>The Android Studio build system defines a hierarchical set of build tasks: the top-level or
-anchor tasks invoke dependent tasks to produce their collective build outcomes. The top-level build
-tasks are:</p>
-
-<dl>
- <dt>assemble </dt>
- <dd><p>Builds the project output. </p></dd>
- <dt>check </dt>
- <dd><p>Runs checks and tests.</p></dd>
- <dt>build </dt>
- <dd><p>Runs both assemble and check. </p></dd>
- <dt>clean </dt>
- <dd><p>Performs the clean.</p></dd>
-</dl>
-
-<p>The Android plugin provides the <em>connectedCheck</em> and <em>deviceCheck</em> tasks
-for checks run on connected, emulated, and remote devices. Gradle tasks can be viewed by clicking
-the Gradle tab</a> in the right margin.</p>
-
-<p>You can view the list of available tasks and invoke any task from Android Studio and from
-the command line, as described in
-<a href="{@docRoot}tools/building/building-studio.html">Building and Running from Android Studio</a>
-and <a href="{@docRoot}tools/building/building-cmdline.html">Build the project from
-the command line</a>.</p>
-
-<h2 id="gradleWrapper">Gradle Wrapper</h2>
-
-<p>Android Studio projects contain the <em>Gradle wrapper</em>, which consists of:</p>
-
-<ul>
- <li>A JAR file</li>
- <li>A properties file</li>
- <li>A shell script for Windows platforms</li>
- <li>A shell script for Mac and Linux platforms</li>
-</ul>
-
-<p class="note"><strong>Note:</strong> You should submit all of these files to your source
-control system.</p>
-
-<p>Using the Gradle wrapper (instead of the local Gradle installation) ensures that
-you always run the version of Gradle defined in the <em>local.properties</em> file. To configure your
-project to use a newer version of Gradle, edit the properties file and specify the new version there.
-</p>
-
-<p>Android Studio reads the properties file from the Gradle wrapper directory inside your project
-and runs the wrapper from this directory, so you can seamlessly work with multiple projects
-that require different versions of Gradle.</p>
-
-<p class="note"><strong>Note:</strong> Android Studio does not use the shell scripts, so any
-changes you make to them won't work when building from the IDE. You should define your custom
-logic inside Gradle build files instead.</p>
-
-<p>You can run the shell scripts to build your project from the command line on your development
-machine and on other machines where Android Studio is not installed.</p>
-
-<p class="caution"><strong>Caution:</strong> When you create a project, only use the Gradle wrapper
-scripts and JAR from a trusted source, such as those generated by Android Studio. </p>
-
-
-<h2 id="buildVariants">Build Variants</h2>
-
-<p>Each version of your app is represented in the build system by a <em>build variant</em>.
-Build variants are combinations of product flavors and build types. Product flavors represent
-product build versions of an app, such as free and paid. Build types represent the build
-packaging versions generated for each app package, such as debug and release. The build system
-generates APKs for each combination of product flavor and build type.</p>
-
-<p>By default, Android Studio defines default configuration settings, <code>defaultConfig</code> in
-the build.gradle file, and two build types (<em>debug</em> and <em>release</em>). This creates two
-build variants, debug and release, and the build system generates an
-APK for each variant. </p>
-
-<p>Adding two product flavors, <em>demo</em> and <em>full</em> along
-with the default build types <em>debug</em> and <em>release</em> generates four build variants,
-each with its own customized configuration:</p>
-
-<ul>
- <li>demoDebug</li>
- <li>demoRelease</li>
- <li>fullDebug</li>
- <li>fullRelease</li>
-</ul>
-
-Resources are merged across the multiple Android application sources:
-<ul>
- <li>Build variants based on the buildType, and productFlavor build settings</li>
- <li>The main sourceSet, generally located in src/main/res</li>
- <li>Library Project dependencies, which contribute resources through the res entry in their aar
- bundle.</li>
-</ul>
-
-<p>The priority of the merge order from lowest to highest is libraries/dependencies -> main src ->
-productFlavor -> buildType.</p>
-
-
-<p>Some projects have complex combinations of features along more than one dimension, but they
-still represent the same app. For example, in addition to having a demo and a full version of the
-app, some games may contain binaries specific to a particular CPU/ABI. The flexibility of
-the build system makes it possible to generate the following build variants for such a project:</p>
-
-<ul>
- <li>x86-demoDebug</li>
- <li>x86-demoRelease</li>
- <li>x86-fullDebug</li>
- <li>x86-fullRelease</li>
- <li>arm-demoDebug</li>
- <li>arm-demoRelease</li>
- <li>arm-fullDebug</li>
- <li>arm-fullRelease</li>
- <li>mips-demoDebug</li>
- <li>mips-demoRelease</li>
- <li>mips-fullDebug</li>
- <li>mips-fullRelease</li>
-</ul>
-
-<p>This project would consist of two build types (<em>debug</em> and <em>release</em>)
-and two <em>dimensions</em> of product flavors, one for app type (demo or full) and one for
-CPU/ABI (x86, ARM, or MIPS). </p>
-
-
-<h3 id="sourceDirectories">Source directories</h3>
-
-<p>To build each version of your app, the build system combines source code and
-resources from:</p>
-
-<ul>
- <li><code>src/main/</code> - the main source directory (the default configuration common to all
- variants)</li>
- <li><code>src/<buildType>/</code> - the <buildType> source directory</li>
- <li><code>src/<productFlavor>/</code> - the <productFlavor> source directory</li>
-</ul>
-
-<p class="note"><strong>Note:</strong> The build type and product flavor source directories are optional,
-as Android Studio does not create these directories for you. You should create these directories
-as you add build types and product flavors to the build configuration files. The build system does not
-use these directories if they are not present.</p>
-
-<p>For projects that do not define any flavors, the build system uses the <em>defaultConfig</em>
-settings, the main app directory and the default build type directories. For example, to generate
-the default <em>debug</em> and <em>release</em> build variants in projects with no product flavors,
-the build system uses:</p>
-<ul>
- <li><code>src/main/</code> (default configuration)</li>
- <li><code>src/release/</code> (build type)</li>
- <li><code>src/debug/</code> (build type)</li>
-</ul>
-
-<p>For projects that define a set of product flavors, the build system merges the build type, product
-flavor and main source directories. For example, to generate the <em>full-debug</em> build variant,
-the build system merges the build type, product flavor and main directories:</p>
-<ul>
- <li><code>src/main/</code> (default configuration)</li>
- <li><code>src/debug/</code> (build type)</li>
- <li><code>src/full/</code> (flavor)</li>
-</ul>
-
-<p>For projects that use flavor dimensions, the build system merges one flavor source directory per
-dimension. For example, to generate the <em>arm-demo-release</em> build variant, the build system
-merges:</p>
-<ul>
- <li><code>src/main/</code> (default configuration)</li>
- <li><code>src/release/</code> (build type)</li>
- <li><code>src/demo/</code> (flavor - app type dimension)</li>
- <li><code>src/arm/</code> (flavor - ABI dimension)</li>
-</ul>
-
-
-<p>The source code from these directories is used together to generate the output for a build
-variant. You can have classes with the same name in different directories as long as those
-directories are not used together in the same variant. </p>
-
-<p>The build system also merges all the manifests into a single manifest, so each build variant
-can define different components or permissions in the final manifest. The manifest merge priority
-from lowest to highest is libraries/dependencies -> main src -> productFlavor -> buildType. </p>
-
-<p>The build system merges all the resources from the all the source directories. If different
-folders contain resources with the same name for a build variant, the priority order is the
-following: build type resources override those from the product flavor, which override the
-resources in the main source directory, which override those in any libraries.</p>
-
-<p class="note"><strong>Note:</strong> Build variants enable you to reuse common activities,
-application logic, and resources across different versions of your app.</p>
-
-
+++ /dev/null
-page.title=Improving Code Inspection with Annotations
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#adding-nullness">Adding Nullness Annotations</a></li>
- <li><a href="#res-annotations">Adding Resource Annotations</a></li>
- <li><a href="#thread-annotations">Adding Thread Annotations</a></li>
- <li><a href="#value-constraint">Adding Value Constraint Annotations</a></li>
- <li><a href="#permissions">Adding Permission Annotations</a></li>
- <li><a href="#check-result">Adding CheckResult Annotations</a></li>
- <li><a href="#call-super">Adding CallSuper Annotations</a></li>
- <li><a href="#enum-annotations">Creating Enumerated Annotations</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/lint.html">lint (reference)</a></li>
- <li><a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a></li>
- <li><a href="{@docRoot}tools/studio/index.html#annotations">Annotations in Android Studio</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>Using code inspections tools such as <a href="{@docRoot}tools/help/lint.html">lint</a> can help
-you find problems and improve your code, but inspection tools can only infer so much. Android
-resource ids, for example, use an {@code int} to identify strings, graphics, colors and other
-resource types, so inspection tools cannot tell when you have specified a string resource where
-you should have specified a color. This situation means that your app may render incorrectly or
-fail to run at all, even if you use code inspection. </p>
-
-<p>Annotations allow you to provide hints to code inspections tools like {@code lint}, to help
-detect these, more subtle code problems. They are added as metadata tags that you attach to
-variables, parameters, and return values to inspect method return values, passed parameters, and
-local variables and fields. When used with code inspections tools, annotations can help you detect
-problems, such as null pointer exceptions and resource type
-conflicts. </p>
-
-<p>For more information on enabling <a href="{@docRoot}tools/help/lint.html">lint</a> inspections
-and running <a href="{@docRoot}tools/help/lint.html">lint</a>,
-see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p>
-
-<p>Android supports a variety of annotations for insertion in the methods, parameters, and return
-values in your code, for example:</p>
-
-<dl>
- <dt>{@link android.support.annotation.Nullable @Nullable}</dt>
- <dd>Can be null.</dd>
-
- <dt>{@link android.support.annotation.NonNull @NonNull}</dt>
- <dd>Cannot be null.</dd>
-
- <dt>{@link android.support.annotation.StringRes @StringRes}</dt>
- <dd>References a <a href="{@docRoot}reference/android/R.string.html"><code>R.string</code></a>
- resource.</dd>
-
- <dt>{@link android.support.annotation.DrawableRes @DrawableRes}</dt>
- <dd>References a
- <a href="{@docRoot}guide/topics/resources/drawable-resource.html"><code>Drawable</code></a>
- resource. </dd>
-
- <dt>{@link android.support.annotation.ColorRes @ColorRes}</dt>
- <dd>References a <a href="{@docRoot}reference/android/graphics/Color.html"><code>Color</code></a>
- resource. </dd>
-
- <dt>{@link android.support.annotation.InterpolatorRes @InterpolatorRes}</dt>
- <dd>References a
- <a href="{@docRoot}reference/android/view/animation/Interpolator.html"><code>Interpolator</code></a>
- resource. </dd>
-
- <dt>{@link android.support.annotation.AnyRes @AnyRes}</dt>
- <dd>References any type of <a href="{@docRoot}reference/android/R.html"><code>R.</code></a>
- resource. </dd>
-
- <dt><code>@UiThread</code></dt>
- <dd>Calls from a UI
- <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </dd>
- </dl>
-
-<p>For a complete list of the supported annotations, either examine the contents of the
-{@link android.support.annotation Support-Annotations} library or use the
-auto-complete feature to display the available options for the <code>import
-android.support.annotation.</code> statement. The
-<a href="{@docRoot}tools/help/sdk-manager.html"> SDK Manager</a> packages the
-{@link android.support.annotation Support-Annotations} library in the Android Support Repository
-for use with Android Studio and in the Android
-<a href="{@docRoot}tools/support-library/index.html">Support Library</a> for use with other Android
-development tools.</p>
-
-
-<p>To add annotations to your code, first add a dependency to the
-{@link android.support.annotation Support-Annotations} library. In Android Studio,
-add the dependency using the <strong>File > Project Structure > Dependencies</strong> menu
-option or your <code>build.gradle</code> file. The following example shows how to add the
-{@link android.support.annotation Support-Annotations} library dependency in the
-<code>build.gradle</code> file: </p>
-
-<pre>
-dependencies {
- compile 'com.android.support:support-annotations:22.2.0'
-}
-</pre>
-
-
-<p>The {@link android.support.annotation Support-Annotations} library is decorated with the
-supported annotations so using this library's methods and resources automatically checks the code
-for potential problems.</p>
-
-<p>If you include annotations in a library and use the
-<a href="{@docRoot}tools/building/plugin-for-gradle.html"><code>Android Plugin for Gradle</code></a>
-to build an Android ARchive (AAR) artifact of that library, the annotations are included as part
-of the artifact in XML format in the <code>annotations.zip</code> file. </p>
-
-<p>To start a code inspection from Android Studio, which includes validating annotations and
-automatic <a href="{@docRoot}tools/help/lint.html">lint</a> checking, select
-<strong>Analyze > Inspect Code</strong> from the menu options. Android Studio displays conflict
-messages throughout the code to indication annotation conflicts and suggest possible
-resolutions.</p>
-
-
-<h2 id="adding-nullness">Adding Nullness Annotations</h2>
-<p>Add {@link android.support.annotation.Nullable @Nullable} and
-{@link android.support.annotation.NonNull @NonNull} annotations to check
-the nullness of a given variable, parameter, or return value. For example, if a local variable
-that contains a null value is passed as a parameter to a method with the
-{@link android.support.annotation.NonNull @NonNull} annotation
-attached to that parameter, building the code generates a warning indicating a non-null conflict. </p>
-
-<p>This example attaches the {@link android.support.annotation.NonNull @NonNull} annotation to
-the <code>context</code> and <code>attrs</code> parameters to check that the passed parameter
-values are not null. </p>
-
-<pre>
-import android.support.annotation.NonNull;
-...
-
- /** Add support for inflating the <fragment> tag. */
- @NonNull
- @Override
- public View onCreateView(String name, @NonNull Context context,
- @NonNull AttributeSet attrs) {
- ...
- }
-...
-</pre>
-
-<p class="note"><strong>Note:</strong> Android Studio supports running a nullability analysis to
-automatically infer and insert nullness annotations in your code. For more information about
-inferring nullability in Android Studio, see
-<a href="{@docRoot}tools/studio/index.html#annotations">Annotations in Android Studio</a>. </p>
-
-
-<h2 id="res-annotations">Adding Resource Annotations</h2>
-<p>Validating resource types can be useful as Android references to resources, such as
-<a href="{@docRoot}guide/topics/resources/drawable-resource.html"><code>Drawables</code></a> and
-<a href="{@docRoot}reference/android/R.string.html"><code>R.string</code></a> resources, are
-passed as integers. Code that expects a parameter to reference a specific type of resource, for
-example <a href="{@docRoot}guide/topics/resources/drawable-resource.html"><code>Drawables</code></a>,
-can be passed the expected reference type of <code>int</code>, but actually reference a different
-type of resource, such as a <code>R.string</code></a> resource. </p>
-
-<p>For example, add {@link android.support.annotation.StringRes @StringRes} annotations to check
-that a resource parameter contains a
-<a href="{@docRoot}reference/android/R.string.html"><code>R.string</code></a>
-reference. During code inspection, the annotation generates a warning if a <code>R.string</code>
-reference is not passed in the parameter.</p>
-
-<p>This example attaches the {@link android.support.annotation.StringRes @StringRes}
-annotation to the <code>resId</code> parameter to validate that it is really a string resource. </p>
-
-<pre>
-import android.support.annotation.StringRes;
-...
- public abstract void setTitle(@StringRes int resId);
- ...
-</pre>
-
-
-<p>Annotations for the other resource types, such as
-{@link android.support.annotation.DrawableRes @DrawableRes},
-{@link android.support.annotation.DimenRes @DimenRes},
-{@link android.support.annotation.ColorRes @ColorRes}, and
-{@link android.support.annotation.InterpolatorRes @InterpolatorRes} can be added using
-the same annotation format and run during the code inspection. </p>
-
-
-
-
-<h2 id="thread-annotations">Adding Thread Annotations</h2>
-<p>Thread annotations check if a method is called from a specific type of
-<a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. The following thread
-annotations are supported: </p>
-<ul>
- <li><code>@UiThread</code> </li>
- <li><code>@MainThread</code> </li>
- <li><code>@WorkerThread</code> </li>
- <li><code>@BinderThread</code>
-</ul>
-
-<p class="note"><strong>Note:</strong> The <code>@MainThread</code>
-and the <code>@UiThread</code> annotations are interchangeable so
-methods calls from either thread type are allowed for these annotations. </p>
-
-
-<p>If all methods in a class share the same threading requirement, you can add a single
-<a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>
-annotation to the class to verify that all methods in the class are called from the same type of
-<a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </p>
-
-<p>A common use of the <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>
-annotation is to validate method overrides in the
-<a href="{@docRoot}reference/android/os/AsyncTask.html">AsyncTask</a> class as this class performs
-background operations and publishes results only on the UI
-<a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </p>
-
-
-
-<h2 id="value-constraint">Adding Value Constraint Annotations</h2>
-<p>Use the <code>@IntRange</code>,
-<code>@FloatRange</code>, and
-<code>@Size</code> annotations to validate the values of passed
-parameters. </p>
-
-<p>The <code>@IntRange</code> annotation validates that the parameter
-value is within a specified range. The following example ensures that the <code>alpha</code>
-parameter contains an integer value from 0 to 255: </p>
-
-<pre>
-public void setAlpha(@IntRange(from=0,to=255) int alpha) { … }
-</pre>
-
-<p>The <code>@FloatRange</code> annotation checks that the parameter
-value is within a specified range of floating point values. The following example ensures that the
-<code>alpha</code> parameter contains a float value from 0.0 to 1.0: </p>
-
-<pre>
-public void setAlpha(@FloatRange(from=0.0, to=1.0) float alpha) {...}
-</pre>
-
-<p>The <code>@Size</code> annotation checks the size of a collection or
-array, as well as the length of a string. For example, use the <code>@Size(min=1)</code>
-annotation to check if a collection is not empty, and the <code>@Size(2)</code> annotation to
-validate that an array contains exactly two values. The following example ensures that the
-<code>location</code> array contains at least one element: </p>
-
-<pre>
-int[] location = new int[3];
-button.getLocationOnScreen(@Size(min=1) location);
-</pre>
-
-
-<h2 id="permissions">Adding Permission Annotations</h2>
-<p>Use the <code>@RequiresPermission</code> annotation to
-validate the permissions of the caller of a method. To check for a single permission from a
-list the valid permissions, use the <code>anyOf</code> attribute. To check for a set of
-permissions, use the <code>allOf</code> attribute. The following example annotates the
-<code>setWallpaper</code> method to ensure that the caller of the method has the
-<code>permission.SET_WALLPAPERS</code> permission. </p>
-
-<pre>
-@RequiresPermission(Manifest.permission.SET_WALLPAPER)
-public abstract void setWallpaper(Bitmap bitmap) throws IOException;
-</pre>
-
-<p>This example requires the caller of the {@code copyFile()} method to have both read and write
-permissions to external storage:</p>
-<pre>
-@RequiresPermission(allOf = {
- Manifest.permission.READ_EXTERNAL_STORAGE,
- Manifest.permission.WRITE_EXTERNAL_STORAGE})
-public static final void copyFile(String dest, String source) {
- ...
-}
-</pre>
-
-<h2 id="check-result">Adding CheckResults Annotations</h2>
-<p>Use the <code>@CheckResults</code> annotation to
-validate that a method's result or return value is actually used. The following example annotates
-the <code>checkPermissions</code> method to ensure the return value of the method is actually
-referenced. It also names the
-<a href="{@docRoot}reference/android/content/ContextWrapper.html#enforcePermission">enforcePermission</a>
-method as a method to be suggested to the developer as a replacement. </p>
-
-
-
-<pre>
-@CheckResult(suggest="#enforcePermission(String,int,int,String)")
-public abstract int checkPermission(@NonNull String permission, int pid, int uid);
-</pre>
-
-{@link android.support.annotation.StringDef @StringDef}
-
-
-<h2 id="call-super">Adding CallSuper Annotations</h2>
-<p>Use the <code>@CallSuper</code> annotation to validate that an
-overriding method calls the super implementation of the method. The following example annotates
-the <code>onCreate</code> method to ensure that any overriding method implementations call
-<code>super.onCreate()</code>. </p>
-
-<pre>
-@CallSuper
-protected void onCreate(Bundle savedInstanceState) {
-}
-</pre>
-
-
-
-<h2 id="enum-annotations">Creating Enumerated Annotations</h2>
-<p>Use the {@link android.support.annotation.IntDef @IntDef} and
-{@link android.support.annotation.StringDef @StringDef} annotations
-so you can create enumerated annotations of integer and string sets to validate other types of code
-references, such as passing references to a set of constants. </p>
-
-<p>The following example illustrates the steps to create an enumerated annotation that ensures
-a value passed as a method parameter references one of the defined constants.</p>
-
-<pre>
-import android.support.annotation.IntDef;
-...
-public abstract class ActionBar {
- ...
- //Define the list of accepted constants
- @IntDef({NAVIGATION_MODE_STANDARD, NAVIGATION_MODE_LIST, NAVIGATION_MODE_TABS})
-
- //Tell the compiler not to store annotation data in the <code>.class</code> file
- @Retention(RetentionPolicy.SOURCE)
-
- //Declare the <code>NavigationMode</code> annotation
- public @interface NavigationMode {}
-
- //Declare the constants
- public static final int NAVIGATION_MODE_STANDARD = 0;
- public static final int NAVIGATION_MODE_LIST = 1;
- public static final int NAVIGATION_MODE_TABS = 2;
-
- //Decorate the target methods with the annotation
- @NavigationMode
- public abstract int getNavigationMode();
-
- //Attach the annotation
- public abstract void setNavigationMode(@NavigationMode int mode);
-
-</pre>
-
-<p>When you build this code, a warning is generated if the <code>mode</code> parameter does
-not reference one of the defined constants (<code>NAVIGATION_MODE_STANDARD</code>,
-<code>NAVIGATION_MODE_LIST</code>, or <code>NAVIGATION_MODE_TABS</code>).</p>
-
-<p>You can also define an annotation with a <code>flag</code> to check if a parameter
-or return value references a valid pattern. This example creates the
-<code>DisplayOptions</code> annotation with a list of valid <code>DISPLAY_</code> constants. </p>
-
-<pre>
-import android.support.annotation.IntDef;
-...
-
-@IntDef(flag=true, value={
- DISPLAY_USE_LOGO,
- DISPLAY_SHOW_HOME,
- DISPLAY_HOME_AS_UP,
- DISPLAY_SHOW_TITLE,
- DISPLAY_SHOW_CUSTOM
-})
-@Retention(RetentionPolicy.SOURCE)
-public @interface DisplayOptions {}
-
-...
-</pre>
-
-<p>When you build code with an annotation flag, a warning is generated if the decorated parameter
-or return value does not reference a valid pattern.</p>
-
-
+++ /dev/null
-page.title=Using DDMS
-parent.title=Debugging
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li><a href="#running">Running DDMS</a></li>
- <li><a href="#how-ddms-works">How DDMS Interacts with a Debugger</a></li>
-
- <li><a href="#using-ddms">Using DDMS</a>
- <ol>
- <li><a href="#heap">Viewing heap usage for a process</a></li>
- <li><a href="#alloc">Tracking memory allocation of objects</a></li>
- <li><a href="#emulator">Working with an emulator or device's file system</a></li>
- <li><a href="#thread">Examining thread information</a></li>
- <li><a href="#profiling">Starting method profiling</a></li>
- <li><a href="#network">Using the Network Traffic tool</a></li>
- <li><a href="#logcat">Using LogCat</a></li>
- <li><a href="#ops-location">Emulating phone operations and location</a></li>
- </ol>
-
- </li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/android-monitor.html">Android Monitor</a></li>
- <li><a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a></li>
- </ol>
-
- </div>
- </div>
-
- <p>Android Studio includes a debugging tool called the Dalvik Debug Monitor Server (DDMS), which
- provides port-forwarding services, screen capture on the device, thread and heap information on
- the device, logcat, process, and radio state information, incoming call and SMS spoofing,
- location data spoofing, and more. This page provides a modest discussion of DDMS features; it is
- not an exhaustive exploration of all the features and capabilities.</p>
-
- <h2 id="running">Running DDMS</h2>
- <p>DDMS is integrated into Android Studio. To use it, launch the
- <a href="{@docRoot}tools/help/monitor.html">Android Device Monitor</a>, and click the
- <strong>DDMS</strong> menu button. DDMS works with both the emulator and a
- connected device. If both are connected and running simultaneously, DDMS defaults to the emulator.</p>
-
-
- <h2 id="how-ddms-works">How DDMS Interacts with a Debugger</h2>
-
- <p>On Android, every application runs in its own process, each of which runs in its own virtual machine
- (VM). Each VM exposes a unique port that a debugger can attach to.</p>
-
- <p>When DDMS starts, it connects to <a href="{@docRoot}tools/help/adb.html">adb</a>.
- When a device is connected, a VM monitoring service is created between
- <code>adb</code> and DDMS, which notifies DDMS when a VM on the device is started or terminated. Once a VM
- is running, DDMS retrieves the VM's process ID (pid), via <code>adb</code>, and opens a connection to the
- VM's debugger, through the adb daemon (adbd) on the device. DDMS can now talk to the VM using a
- custom wire protocol.</p>
-
- <p>DDMS assigns a debugging port to each VM on the device. Typically,
- DDMS assigns port 8600 for the first debuggable VM, the next on 8601, and so on. When a debugger
- connects to one of these ports, all traffic is forwarded to the debugger from the associated
- VM. You can only attach a single debugger to a single port, but DDMS can handle multiple, attached
- debuggers.</p>
-
- <p>By default, DDMS also listens on another debugging port, the DDMS "base port" (8700, by default).
- The base port is a port forwarder, which can accept VM traffic from any debugging port and forward
- it to the debugger on port 8700. This allows you to attach one debugger to port 8700, and debug
- all the VMs on a device. The traffic that is forwarded is determined by the currently selected process
- in the DDMS Devices view.</p>
-
- <p>The following screenshot shows a typical DDMS screen. If you are starting DDMS from
- the command line, the screen is slightly different, but much of the functionality is identical.
- Notice that the highlighted process, <code>com.android.email</code>, that is running in the emulator
- has the debugging port 8700 assigned to it as well as 8606. This signifies that DDMS is currently
- forwarding port 8606 to the static debugging port of 8700.</p>
-
- <img src="{@docRoot}images/debug-ddms.png"
- width="1024" />
- <p class="img-caption"><strong>Figure 1.</strong>
- Screenshot of DDMS</p>
-
- <p>If you are using the command line, read <a href=
- "{@docRoot}tools/debugging/debugging-projects-cmdline.html#debuggingPort">Configuring
- your IDE to attach to the debugging port</a>, for more information on attaching your
- debugger.</p>
-
- <p class="note"><strong>Tip:</strong> You can set a number of DDMS preferences in
- <strong>File</strong> > <strong>Preferences</strong>. Preferences are saved to
- <code>$HOME/.android/ddms.cfg</code>.</p>
-
- <p class="warning"><strong>Known debugging issues with Dalvik</strong><br />
- Debugging an application in the Dalvik VM should work the same as it does in other VMs. However,
- when single-stepping out of synchronized code, the "current line" cursor may jump to the last
- line in the method for one step.</p>
-
- <h2 id="using-ddms">Using DDMS</h2>
- The following sections describe how to use DDMS and the various tabs and panes that are part of the
- DDMS GUI. The Android Studio version and the command line version have minor UI differences, but
- the same functionality. For information on running DDMS, see the previous section in this document,
- <a href="#running">Running DDMS</a>.
-
-
- <h3 id="heap">Viewing heap usage for a process</h3>
-
- <p>DDMS allows you to view how much heap memory a process is using. This information is useful in
- tracking heap usage at a certain point of time during the execution of your application.</p>
- <p>To view heap usage for a process:</p>
- <ol>
- <li>In the Devices tab, select the process that you want to see the heap information for.</li>
-
- <li>Click the <strong>Update Heap</strong> button to enable heap information for the
- process.</li>
-
- <li>In the Heap tab, click <strong>Cause GC</strong> to invoke garbage collection, which
- enables the collection of heap data. When the operation completes, you will see a group of
- object types and the memory that has been allocated for each type. You can click <strong>Cause
- GC</strong> again to refresh the data.</li>
-
- <li>Click on an object type in the list to see a bar graph that shows the number of objects
- allocated for a particular memory size in bytes.</li>
- </ol>
-
- <h3 id="alloc">Tracking memory allocation of objects</h3>
-
- <p>DDMS provides a feature to track objects that are being allocated to memory and to see which
- classes and threads are allocating the objects. This allows you to track, in real time, where
- objects are being allocated when you perform certain actions in your application. This
- information is valuable for assessing memory usage that can affect application performance.
- </p>
-
- <p>To track memory allocation of objects:</p>
- <ol>
- <li>In the Devices tab, select the process that you want to enable allocation tracking
- for.</li>
-
- <li>In the Allocation Tracker tab, click the <strong>Start Tracking</strong> button to begin
- allocation tracking. At this point, anything you do in your application will be tracked.</li>
-
- <li>Click <strong>Get Allocations</strong> to see a list of objects that have been allocated
- since you clicked on the <strong>Start Tracking</strong> button. You can click on <strong>Get
- Allocations</strong> again to append to the list new objects that have been
- allocated.</li>
-
- <li>To stop tracking or to clear the data and start over, click the <strong>Stop Tracking
- button</strong>.</li>
-
- <li>Click on a specific row in the list to see more detailed information such as the method and
- line number of the code that allocated the object.</li>
- </ol>
-
- <h3 id="emulator">Working with an emulator or device's file system</h3>
-
- <p>DDMS provides a File Explorer tab that allows you to view, copy, and delete files on the
- device. This feature is useful in examining files that are created by your application or if you
- want to transfer files to and from the device.</p>
-
- <p>To work with an emulator or device's file system:</p>
- <ol>
- <li>In the Devices tab, select the emulator that you want to view the file system for.</li>
-
- <li>To copy a file from the device, locate the file in the File Explorer and click the
- <strong>Pull file</strong> button.</li>
-
- <li>To copy a file to the device, click the <strong>Push file</strong> button on the File
- Explorer tab.</li>
- </ol>
-
- <!-- Need to elaborate more on where things are stored in the file system,
- databases, apks, user info, files that are important to look at -->
-
- <h3 id="thread">Examining thread information</h3>
-
- <p>The Threads tab in DDMS shows you the currently running threads for a selected process.</p>
-
- <ol>
- <li>In the Devices tab, select the process that you want to examine the threads for.</li>
-
- <li>Click the <strong>Update Threads</strong> button.</li>
-
- <li>In the Threads tab, you can view the thread information for the selected process.</li>
- </ol>
-
- <h3 id="profiling">Starting method profiling</h3>
-
- <p>Method profiling is a means to track certain metrics about a method, such as number of calls,
- execution time, and time spent executing the method. If you want more granular control over
- where profiling data is collected, use the {@link android.os.Debug#startMethodTracing()} and
- {@link android.os.Debug#stopMethodTracing()} methods. For more information about generating trace logs, see
- <a href="debugging-tracing.html">Profiling and Debugging UIs</a>.</p>
-
- <p>Before you start method profiling in DDMS, be aware of the following restrictions:</p>
- <ul>
- <li>Android 2.1 and earlier devices must
- have an SD card present and your application must have permission to write to the SD card.
- <li>Android 2.2 and later devices do not need an SD card. The trace log files are
- streamed directly to your development machine.</li>
- </ul>
-
- <p>To start method profiling:</p>
- <ol>
- <li>On the Devices tab, select the process that you want to enable method profiling for.</li>
-
- <li>Click the <strong>Start Method Profiling</strong> button.</li>
-
- <li>In Android 4.4 and later, choose either trace-based profiling or sample-based profiling
- with a specified sampling interval. For earlier versions of Android, only trace-based profiling
- is available.</li>
-
- <li>Interact with your application to start the methods that you want to profile.</li>
-
- <li>Click the <strong>Stop Method Profiling</strong> button. DDMS stops profiling your
- application and opens <a href="{@docRoot}tools/debugging/debugging-ui.html">Traceview</a>
- with the method profiling information that was collected
- between the time you clicked on <strong>Start Method Profiling</strong> and <strong>Stop Method
- Profiling</strong>.</li>
- </ol>
-
- <h3 id="network">Using the Network Traffic tool</h3>
-
- <p>In Android 4.0, the DDMS (Dalvik Debug Monitor Server) includes a Detailed
-Network Usage tab that makes it possible to track when your application is
-making network requests. Using this tool, you can monitor how and when your app
-transfers data and optimize the underlying code appropriately. You can also
-distinguish between different traffic types by applying a “tag” to network
-sockets before use.</p>
-
-<p>These tags are shown in a stack area chart in DDMS, as shown in figure 2:</p>
-
-<img src="{@docRoot}images/developing/ddms-network.png" />
-<p class="img-caption"><strong>Figure 2.</strong> Network Usage tab.</p>
-
-<p>By monitoring the frequency of your data transfers, and the amount of data
-transferred during each connection, you can identify areas of your application
-that can be made more battery-efficient. Generally, you should look for
-short spikes that can be delayed, or that should cause a later transfer to be
-pre-empted. </p>
-
-<p>To better identify the cause of transfer spikes, the
-{@link android.net.TrafficStats} API allows you
-to tag the data transfers occurring within a thread using {@link
-android.net.TrafficStats#setThreadStatsTag setThreadStatsTag()}, followed
-by manually tagging (and untagging) individual sockets using {@link
-android.net.TrafficStats#tagSocket tagSocket()} and {@link
-android.net.TrafficStats#untagSocket untagSocket()}. For example:</p>
-
-<pre>TrafficStats.setThreadStatsTag(0xF00D);
-TrafficStats.tagSocket(outputSocket);
-// Transfer data using socket
-TrafficStats.untagSocket(outputSocket);</pre>
-
-<p>Alternatively, the {@link java.net.URLConnection} APIs included in the platform
-automatically tag sockets internally based on the active tag (as identified by
-{@link android.net.TrafficStats#getThreadStatsTag getThreadStatsTag()}).
-These APIs correctly tag/untag sockets when recycled through
-keep-alive pools. In the following example,
-{@link android.net.TrafficStats#setThreadStatsTag setThreadStatsTag()}
-sets the active tag to be {@code 0xF00D}.
-There can only be one active tag per thread.
-That is the value that will
-be returned by {@link android.net.TrafficStats#getThreadStatsTag getThreadStatsTag()}
-and thus used by the HTTP client to tag sockets. The {@code finally} statement
-invokes
-{@link android.net.TrafficStats#clearThreadStatsTag clearThreadStatsTag()}
-to clear the tag.</p>
-
-<pre>TrafficStats.setThreadStatsTag(0xF00D);
- try {
- // Make network request using your http client.
- } finally {
- TrafficStats.clearThreadStatsTag();
-}</pre>
-
-<p>Socket tagging is supported in Android 4.0, but real-time stats will only be
-displayed on devices running Android 4.0.3 or higher.</p>
-
- <h3 id="logcat">Using LogCat</h3>
-
- <p>LogCat is integrated into DDMS, and outputs the messages that you print out using the {@link android.util.Log}
- class along with other system messages such as stack traces when exceptions are thrown. View the
- <a href="{@docRoot}tools/debugging/debugging-log.html">Reading and
- Writing Log Messages.</a> topic for more information on how to log messages to the LogCat.</p>
-
- <p>When you have set up your logging, you can use the LogCat feature of DDMS to filter certain
- messages with the following buttons:</p>
-
- <ul>
- <li>Verbose</li>
-
- <li>Debug</li>
-
- <li>Info</li>
-
- <li>Warn</li>
-
- <li>Error</li>
- </ul>
-
- <p>You can also setup your own custom filter to specify more details such as filtering messages
- with the log tags or with the process id that generated the log message. The add filter,
- edit filter, and delete filter buttons let you manage your custom filters.</p>
-
- <h3 id="ops-location">Emulating phone operations and location</h3>
- <p>The <strong>Emulator Control</strong> tab, shown in Figure 1, is no longer
- supported. Use the
- <a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a>
- for these features.</p>
-
-
+++ /dev/null
-page.title=Reading and Writing Logs
-
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li><a href="#startingLogcat">Starting LogCat</a></li>
-
- <li><a href="#filteringOutput">Filtering Log Output</a></li>
-
- <li><a href="#outputFormat">Controlling Log Output Format</a></li>
-
- <li><a href="#alternativeBuffers">Viewing Alternative Log Output Buffers</a></li>
-
- <li><a href="#viewingStd">Viewing stdout and stderr</a></li>
-
- <li><a href="#logClass">Logging from Code</a></li>
- </ol>
- </div>
- </div>
-
- <p>The Android logging system provides a mechanism for collecting and viewing system debug
- output. Logcat dumps a log of system messages, which include things such as stack traces when the
- emulator throws an error and messages that you have written from your application by using the
- {@link android.util.Log} class. You can run LogCat through ADB or from DDMS, which allows you to
- read the messages in real time.</p>
-
- <h2 id="startingLogcat">Using LogCat</h2>
-
- <p>You can use LogCat from within DDMS or call it on an ADB shell. For more information on how to
- use LogCat within DDMS, see <a href="{@docRoot}tools/debugging/ddms.html#logcat">Using
- DDMS</a>. To run LogCat, through the ADB shell, the general usage is:</p>
- <pre>
-[adb] logcat [<option>] ... [<filter-spec>] ...
-</pre>
-
- <p>You can use the <code>logcat</code> command from your development computer or from a remote
- adb shell in an emulator/device instance. To view log output in your development computer, you
- use</p>
- <pre>
-$ adb logcat
-</pre>
-
- <p>and from a remote adb shell you use</p>
- <pre>
-# logcat
-</pre>
-
- <p>The following table describes the <code>logcat</code> command line options:</p>
-
- <table>
- <tr>
- <td><code>-c</code></td>
-
- <td>Clears (flushes) the entire log and exits.</td>
- </tr>
-
- <tr>
- <td><code>-d</code></td>
-
- <td>Dumps the log to the screen and exits.</td>
- </tr>
-
- <tr>
- <td><code>-f <filename></code></td>
-
- <td>Writes log message output to <code><filename></code>. The default is
- <code>stdout</code>.</td>
- </tr>
-
- <tr>
- <td><code>-g</code></td>
- <td>Prints the size of the specified log buffer and exits.</td>
- </tr>
-
- <tr>
- <td><code>-n <count></code></td>
-
- <td>Sets the maximum number of rotated logs to <code><count></code>. The default value
- is 4. Requires the <code>-r</code> option.</td>
- </tr>
-
- <tr>
- <td><code>-r <kbytes></code></td>
-
- <td>Rotates the log file every <code><kbytes></code> of output. The default value is
- 16. Requires the <code>-f</code> option.</td>
- </tr>
-
- <tr>
- <td><code>-s</code></td>
-
- <td>Sets the default filter spec to silent.</td>
- </tr>
-
- <tr>
- <td><code>-v <format></code></td>
-
- <td>Sets the output format for log messages. The default is <code>brief</code> format. For a
- list of supported formats, see <a href="#outputFormat">Controlling Log Output
- Format</a>.</td>
- </tr>
- </table>
-
- <h3 id="filteringOutput">Filtering Log Output</h3>
-
- <p>Every Android log message has a <em>tag</em> and a <em>priority</em> associated with it.</p>
-
- <ul>
- <li>The tag of a log message is a short string indicating the system component from which the
- message originates (for example, "View" for the view system).</li>
-
- <li>The priority is one of the following character values, ordered from lowest to highest
- priority:</li>
-
- <li style="list-style: none; display: inline">
- <ul>
- <li><code>V</code> — Verbose (lowest priority)</li>
-
- <li><code>D</code> — Debug</li>
-
- <li><code>I</code> — Info</li>
-
- <li><code>W</code> — Warning</li>
-
- <li><code>E</code> — Error</li>
-
- <li><code>F</code> — Fatal</li>
-
- <li><code>S</code> — Silent (highest priority, on which nothing is ever printed)</li>
- </ul>
- </li>
- </ul>
-
- <p>You can obtain a list of tags used in the system, together with priorities, by running
- LogCat and observing the first two columns of each message, given as
- <code><priority>/<tag></code>.</p>
-
- <p>Here's an example of logcat output that shows that the message relates to priority level "I"
- and tag "ActivityManager":</p>
- <pre>
-I/ActivityManager( 585): Starting activity: Intent { action=android.intent.action...}
-</pre>
-
- <p>To reduce the log output to a manageable level, you can restrict log output using <em>filter
- expressions</em>. Filter expressions let you indicate to the system the tags-priority
- combinations that you are interested in — the system suppresses other messages for the
- specified tags.</p>
-
- <p>A filter expression follows this format <code>tag:priority ...</code>, where <code>tag</code>
- indicates the tag of interest and <code>priority</code> indicates the <em>minimum</em> level of
- priority to report for that tag. Messages for that tag at or above the specified priority are
- written to the log. You can supply any number of <code>tag:priority</code> specifications in a
- single filter expression. The series of specifications is whitespace-delimited.</p>
-
- <p>Here's an example of a filter expression that suppresses all log messages except those with
- the tag "ActivityManager", at priority "Info" or above, and all log messages with tag "MyApp",
- with priority "Debug" or above:</p>
- <pre>
-adb logcat ActivityManager:I MyApp:D *:S
-</pre>
-
- <p>The final element in the above expression, <code>*:S</code>, sets the priority level for all
- tags to "silent", thus ensuring only log messages with "ActivityManager" and "MyApp" are displayed. Using
- <code>*:S</code> is an excellent way to ensure that log output is restricted to the filters that
- you have explicitly specified — it lets your filters serve as a "whitelist" for log
- output.</p>
-
- <p>The following filter expression displays all log messages with priority level "warning" and higher, on all tags:</p>
- <pre>
-adb logcat *:W
-</pre>
-
- <p>If you're running LogCat from your development computer (versus running it on a
- remote adb shell), you can also set a default filter expression by exporting a value for the
- environment variable <code>ANDROID_LOG_TAGS</code>:</p>
- <pre>
-export ANDROID_LOG_TAGS="ActivityManager:I MyApp:D *:S"
-</pre>
-
- <p>Note that <code>ANDROID_LOG_TAGS</code> filter is not exported to the emulator/device
- instance, if you are running LogCat from a remote shell or using <code>adb shell
- logcat</code>.</p>
-
- <h3 id="outputFormat">Controlling Log Output Format</h3>
-
- <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 the 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>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
- 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 blank
- lines.</li>
- </ul>
-
- <p>When starting LogCat, you can specify the output format you want by using the
- <code>-v</code> option:</p>
- <pre>
-[adb] logcat [-v <format>]
-</pre>
-
- <p>Here's an example that shows how to generate messages in <code>thread</code> output
- format:</p>
- <pre>
-adb logcat -v thread
-</pre>
-
- <p>Note that you can only specify one output format with the <code>-v</code> option.</p>
-
- <h3 id="alternativeBuffers">Viewing Alternative Log Buffers</h3>
-
- <p>The Android logging system keeps multiple circular buffers for log messages, and not all of
- the log messages are sent to the default circular buffer. To see additional log messages, you can
- run the <code>logcat</code> command with the <code>-b</code> option, to request viewing of an alternate
- circular buffer. You can view any of these alternate buffers:</p>
-
- <ul>
- <li><code>radio</code> — View the buffer that contains radio/telephony related
- messages.</li>
-
- <li><code>events</code> — View the buffer containing events-related messages.</li>
-
- <li><code>main</code> — View the main log buffer (default)</li>
- </ul>
-
- <p>The usage of the <code>-b</code> option is:</p>
- <pre>
-[adb] logcat [-b <buffer>]
-</pre>
-
- <p>Here's an example of how to view a log buffer containing radio and telephony messages:</p>
- <pre>
-adb logcat -b radio
-</pre><a name="stdout"
- id="stdout"></a>
-
- <h2 id="viewingStd">Viewing stdout and stderr</h2>
-
- <p>By default, the Android system sends <code>stdout</code> and <code>stderr</code>
- (<code>System.out</code> and <code>System.err</code>) output to <code>/dev/null</code>. In
- processes that run the Dalvik VM, you can have the system write a copy of the output to the log
- file. In this case, the system writes the messages to the log using the log tags
- <code>stdout</code> and <code>stderr</code>, both with priority <code>I</code>.</p>
-
- <p>To route the output in this way, you stop a running emulator/device instance and then use the
- shell command <code>setprop</code> to enable the redirection of output. Here's how you do it:</p>
- <pre>
-$ adb shell stop
-$ adb shell setprop log.redirect-stdio true
-$ adb shell start
-</pre>
-
- <p>The system retains this setting until you terminate the emulator/device instance. To use the
- setting as a default on the emulator/device instance, you can add an entry to
- <code>/data/local.prop</code> on the device.</p>
-
- <h2 id="logClass">Logging from Code</h2>
-
- <p>The {@link android.util.Log} class allows you to create log entries in your code that display
- in the LogCat tool. Common logging methods include:</p>
-
- <ul>
- <li>{@link android.util.Log#v(java.lang.String, java.lang.String)
- Log.v(String, String)} (verbose)</li>
-
- <li>{@link android.util.Log#d(java.lang.String, java.lang.String)
- Log.d(String, String)} (debug)</li>
-
- <li>{@link android.util.Log#i(java.lang.String, java.lang.String)
- Log.i(String, String)} (information)</li>
-
- <li>{@link android.util.Log#w(java.lang.String, java.lang.String)
- Log.w(String, String)} (warning)</li>
-
- <li>{@link android.util.Log#e(java.lang.String, java.lang.String)
- Log.e(String, String)} (error)</li>
- </ul>
-
- <p>For example, using the following call:</p>
-
- <pre class="no-pretty-print">
-Log.i("MyActivity", "MyClass.getView() — get item number " + position);
-</pre>
-
- <p>The LogCat outputs something like:</p>
- <pre class="no-pretty-print">
-I/MyActivity( 1557): MyClass.getView() — get item number 1
-</pre>
+++ /dev/null
-page.title=Investigating Your RAM Usage
-page.tags=memory,OutOfMemoryError
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#LogMessages">Interpreting Log Messages</a></li>
- <li><a href="#ViewHeap">Viewing Heap Updates</a></li>
- <li><a href="#TrackAllocations">Tracking Allocations</a></li>
- <li><a href="#ViewingAllocations">Viewing Overall Memory Allocations</a></li>
- <li><a href="#HeapDump">Capturing a Heap Dump</a></li>
- <li><a href="#TriggerLeaks">Triggering Memory Leaks</a></li>
-</ol>
- <h2>See Also</h2>
- <ul>
- <li><a href="{@docRoot}training/articles/memory.html">Managing Your App's Memory</a></li>
- </ul>
- </div>
- </div>
-
-
-
-
-<p>Because Android is designed for mobile devices, you should always be careful about how much
-random-access memory (RAM) your app uses. Although Dalvik and ART perform
-routine garbage collection (GC), this doesn’t mean you can ignore when and where your app allocates and
-releases memory. In order to provide a stable user experience that allows the system to quickly
-switch between apps, it is important that your app does not needlessly consume memory when the user
-is not interacting with it.</p>
-
-<p>Even if you follow all the best practices for <a href="{@docRoot}training/articles/memory.html"
->Managing Your App Memory</a> during
-development (which you should), you still might leak objects or introduce other memory bugs. The
-only way to be certain your app is using as little memory as possible is to analyze your app’s
-memory usage with tools. This guide shows you how to do that.</p>
-
-
-<h2 id="LogMessages">Interpreting Log Messages</h2>
-
-<p>The simplest place to begin investigating your app’s memory usage is the runtime log messages.
-Sometimes when a GC occurs, a message is printed to
-<a href="{@docRoot}tools/help/logcat.html">logcat</a>. The logcat output is also available in the
-Device Monitor or directly in an IDE such as Android Studio.</p>
-
-<h3 id="DalvikLogMessages">Dalvik Log Messages</h3>
-
-<p>In Dalvik (but not ART), every GC prints the following information to logcat:</p>
-
-<pre class="no-pretty-print">
-D/dalvikvm: <GC_Reason> <Amount_freed>, <Heap_stats>, <External_memory_stats>, <Pause_time>
-</pre>
-
-<p>Example:</p>
-
-<pre class="no-pretty-print">
-D/dalvikvm( 9050): GC_CONCURRENT freed 2049K, 65% free 3571K/9991K, external 4703K/5261K, paused 2ms+2ms
-</pre>
-
-<dl>
-<dt>GC Reason</dt>
-<dd>
-What triggered the GC and what kind of collection it is. Reasons that may appear
-include:
-<dl>
-<dt><code>GC_CONCURRENT</code></dt>
-<dd>A concurrent GC that frees up memory as your heap begins to fill up.</dd>
-
-<dt><code>GC_FOR_MALLOC</code></dt>
-<dd>A GC caused because your app attempted to allocate memory when your heap was
-already full, so the system had to stop your app and reclaim memory.</dd>
-
-<dt><code>GC_HPROF_DUMP_HEAP</code></dt>
-<dd>A GC that occurs when you request to create an HPROF file to analyze your heap.</dd>
-
-<dt><code>GC_EXPLICIT</code>
-<dd>An explicit GC, such as when you call {@link java.lang.System#gc()} (which you
-should avoid calling and instead trust the GC to run when needed).</dd>
-
-<dt><code>GC_EXTERNAL_ALLOC</code></dt>
-<dd>This happens only on API level 10 and lower (newer versions allocate everything in the Dalvik
-heap). A GC for externally allocated memory (such as the pixel data stored in
-native memory or NIO byte buffers).</dd>
-</dl>
-</dd>
-
-<dt>Amount freed</dt>
-<dd>The amount of memory reclaimed from this GC.</dd>
-
-<dt>Heap stats</dt>
-<dd>Percentage free of the heap and (number of live objects)/(total heap size).</dd>
-
-<dt>External memory stats</dt>
-<dd>Externally allocated memory on API level 10 and lower (amount of allocated memory) / (limit at
-which collection will occur).</dd>
-
-<dt>Pause time</dt>
-<dd>Larger heaps will have larger pause times. Concurrent pause times show two pauses: one at the
-beginning of the collection and another near the end.</dd>
-</dl>
-
-<p>As these log messages accumulate, look out for increases in the heap stats (the
-{@code 3571K/9991K} value in the above example). If this value continues to increase, you may have
-a memory leak.</p>
-
-
-<h3 id="ARTLogMessages">ART Log Messages</h3>
-
-<p>Unlike Dalvik, ART doesn't log messages for GCs that were not explicitly requested. GCs are only
-printed when they are they are deemed slow. More precisely, if the GC pause exceeds than 5ms or
-the GC duration exceeds 100ms. If the app is not in a pause perceptible process state,
-then none of its GCs are deemed slow. Explicit GCs are always logged.</p>
-
-<p>ART includes the following information in its garbage collection log messages:</p>
-
-<pre class="no-pretty-print">
-I/art: <GC_Reason> <GC_Name> <Objects_freed>(<Size_freed>) AllocSpace Objects, <Large_objects_freed>(<Large_object_size_freed>) <Heap_stats> LOS objects, <Pause_time(s)>
-</pre>
-
-<p>Example:</p>
-
-<pre class="no-pretty-print">
-I/art : Explicit concurrent mark sweep GC freed 104710(7MB) AllocSpace objects, 21(416KB) LOS objects, 33% free, 25MB/38MB, paused 1.230ms total 67.216ms
-</pre>
-
-<dl>
-<dt>GC Reason</dt>
-<dd>
-What triggered the GC and what kind of collection it is. Reasons that may appear
-include:
-<dl>
-<dt><code>Concurrent</code></dt>
-<dd>A concurrent GC which does not suspend app threads. This GC runs in a background thread
-and does not prevent allocations.</dd>
-
-<dt><code>Alloc</code></dt>
-<dd>The GC was initiated because your app attempted to allocate memory when your heap
-was already full. In this case, the garbage collection occurred in the allocating thread.</dd>
-
-<dt><code>Explicit</code>
-<dd>The garbage collection was explicitly requested by an app, for instance, by
-calling {@link java.lang.System#gc()} or {@link java.lang.Runtime#gc()}. As with Dalvik, in ART it is
-recommended that you trust the GC and avoid requesting explicit GCs if possible. Explicit GCs are
-discouraged since they block the allocating thread and unnecessarily was CPU cycles. Explicit GCs
-could also cause jank if they cause other threads to get preempted.</dd>
-
-<dt><code>NativeAlloc</code></dt>
-<dd>The collection was caused by native memory pressure from native allocations such as Bitmaps or
-RenderScript allocation objects.</dd>
-
-<dt><code>CollectorTransition</code></dt>
-<dd>The collection was caused by a heap transition; this is caused by switching the GC at run time.
-Collector transitions consist of copying all the objects from a free-list backed
-space to a bump pointer space (or visa versa). Currently collector transitions only occur when an
-app changes process states from a pause perceptible state to a non pause perceptible state
-(or visa versa) on low RAM devices.
-</dd>
-
-<dt><code>HomogeneousSpaceCompact</code></dt>
-<dd>Homogeneous space compaction is free-list space to free-list space compaction which usually
-occurs when an app is moved to a pause imperceptible process state. The main reasons for doing
-this are reducing RAM usage and defragmenting the heap.
-</dd>
-
-<dt><code>DisableMovingGc</code></dt>
-<dd>This is not a real GC reason, but a note that collection was blocked due to use of
-GetPrimitiveArrayCritical. while concurrent heap compaction is occuring. In general, the use of
-GetPrimitiveArrayCritical is strongly discouraged due to its restrictions on moving collectors.
-</dd>
-
-<dt><code>HeapTrim</code></dt>
-<dd>This is not a GC reason, but a note that collection was blocked until a heap trim finished.
-</dd>
-
-</dl>
-</dd>
-
-
-<dl>
-<dt>GC Name</dt>
-<dd>
-ART has various different GCs which can get run.
-<dl>
-<dt><code>Concurrent mark sweep (CMS)</code></dt>
-<dd>A whole heap collector which frees collects all spaces other than the image space.</dd>
-
-<dt><code>Concurrent partial mark sweep</code></dt>
-<dd>A mostly whole heap collector which collects all spaces other than the image and zygote spaces.
-</dd>
-
-<dt><code>Concurrent sticky mark sweep</code></dt>
-<dd>A generational collector which can only free objects allocated since the last GC. This garbage
-collection is run more often than a full or partial mark sweep since it is faster and has lower pauses.
-</dd>
-
-<dt><code>Marksweep + semispace</code></dt>
-<dd>A non concurrent, copying GC used for heap transitions as well as homogeneous space
-compaction (to defragement the heap).</dd>
-
-</dl>
-</dd>
-
-<dt>Objects freed</dt>
-<dd>The number of objects which were reclaimed from this GC from the non large
-object space.</dd>
-
-<dt>Size freed</dt>
-<dd>The number of bytes which were reclaimed from this GC from the non large object
-space.</dd>
-
-<dt>Large objects freed</dt>
-<dd>The number of object in the large object space which were reclaimed from this garbage
-collection.</dd>
-
-<dt>Large object size freed</dt>
-<dd>The number of bytes in the large object space which were reclaimed from this garbage
-collection.</dd>
-
-<dt>Heap stats</dt>
-<dd>Percentage free and (number of live objects)/(total heap size).</dd>
-
-<dt>Pause times</dt>
-<dd>In general pause times are proportional to the number of object references which were modified
-while the GC was running. Currently, the ART CMS GCs only has one pause, near the end of the GC.
-The moving GCs have a long pause which lasts for the majority of the GC duration.</dd>
-</dl>
-
-<p>If you are seeing a large amount of GCs in logcat, look for increases in the heap stats (the
-{@code 25MB/38MB} value in the above example). If this value continues to increase and doesn't
-ever seem to get smaller, you could have a memory leak. Alternatively, if you are seeing GC which
-are for the reason "Alloc", then you are already operating near your heap capacity and can expect
-OOM exceptions in the near future. </p>
-
-<h2 id="ViewHeap">Viewing Heap Updates</h2>
-
-<p>To get a little information about what kind of memory your app is using and when, you
-can view real-time updates to your app's heap in Android Studio's
-<a href="{@docRoot}tools/studio/index.html#heap-dump">HPROF viewer</a> or in the Device Monitor:</p>
-
-<h3>Memory Monitor in Android Studio</h3>
-<p>Use Android Studio to view your app's memory use: </p>
-<ol>
- <li>Start your app on a connected device or emulator.</li>
- <li>Open the Android run-time window, and view the free and allocated memory in the Memory
- Monitor. </li>
- <li>Click the Dump Java Heap icon
- (<img src="{@docRoot}images/tools/studio-dump-heap-icon.png" style="vertical-align:bottom;margin:0;height:21px"/>)
- in the Memory Monitor toolbar.
- <p>Android Studio creates the heap snapshot file with the filename
- <code>Snapshot-yyyy.mm.dd-hh.mm.ss.hprof</code> in the <em>Captures</em> tab. </p>
- </li>
- <li>Double-click the heap snapshot file to open the HPROF viewer.
- <p class="note"><strong>Note:</strong> To convert a heap dump to standard HPROF format in
- Android Studio, right-click a heap snapshot in the <em>Captures</em> view and select
- <strong>Export to standard .hprof</strong>.</p> </li>
- <li>Interact with your app and click the
- (<img src="{@docRoot}images/tools/studio-garbage-collect.png" style="vertical-align:bottom;margin:0;height:17px"/>)
- icon to cause heap allocation.
- </li>
- <li>Identify which actions in your app are likely causing too much allocation and determine where
- in your app you should try to reduce allocations and release resources.
-</ol>
-
-<h3>Device Monitor </h3>
-<ol>
-<li>Open the Device Monitor.
-<p>From your <code><sdk>/tools/</code> directory, launch the <code>monitor</code> tool.</p>
-</li>
-<li>In the Debug Monitor window, select your app's process from the list on the left.</li>
-<li>Click <strong>Update Heap</strong> above the process list.</li>
-<li>In the right-side panel, select the <strong>Heap</strong> tab.</li>
-</ol>
-
-<p>The Heap view shows some basic stats about your heap memory usage, updated after every
-GC. To see the first update, click the <strong>Cause GC</strong> button.</p>
-
-<img src="{@docRoot}images/tools/monitor-vmheap@2x.png" width="760" alt="" />
-<p class="img-caption"><strong>Figure 1.</strong> The Device Monitor tool,
-showing the <strong>[1] Update Heap</strong> and <strong>[2] Cause GC</strong> buttons.
-The Heap tab on the right shows the heap results.</p>
-
-
-<p>Continue interacting with your app to watch your heap allocation update with each garbage
-collection. This can help you identify which actions in your app are likely causing too much
-allocation and where you should try to reduce allocations and release
-resources.</p>
-
-
-
-<h2 id="TrackAllocations">Tracking Allocations</h2>
-
-<p>As you start narrowing down memory issues, you should also use the Allocation Tracker to
-get a better understanding of where your memory-hogging objects are allocated. The Allocation
-Tracker can be useful not only for looking at specific uses of memory, but also to analyze critical
-code paths in an app such as scrolling.</p>
-
-<p>For example, tracking allocations when flinging a list in your app allows you to see all the
-allocations that need to be done for that behavior, what thread they are on, and where they came
-from. This is extremely valuable for tightening up these paths to reduce the work they need and
-improve the overall smoothness of the UI.</p>
-
-<p>To use the Allocation Tracker, open the Memory Monitor in Android Studio and click the
-<a href="{@docRoot}tools/studio/index.html#alloc-tracker" style="vertical-align:bottom;margin:0;height:21px">
-Allocation Tracker</a> icon. You can also track allocations in the Android Device Monitor:</p>
-
-
-<h3>Android Studio </h3>
-<p>To use the <a href="{@docRoot}tools/studio/index.html#alloc-tracker">Allocation Tracker</a> in
-Android Studio: </p>
-
-<ol>
- <li>Start your app on a connected device or emulator</li>
- <li>Open the Android run-tme window, and view the free and allocated memory in the Memory
- Monitor. </li>
- <li>Click the Allocation Tracker icon
- (<img src="{@docRoot}images/tools/studio-allocation-tracker-icon.png" style="vertical-align:bottom;margin:0;height:21px"/>) in the Memory Monitor tool bar to start and stop memory
- allocations.
- <p>Android Studio creates the allocation file with the filename
- <code>Allocations-yyyy.mm.dd-hh.mm.ss.alloc</code> in the <em>Captures</em> tab. </p>
- </li>
- <li>Double-click the allocation file to open the Allocation viewer. </li>
- <li>Identify which actions in your app are likely causing too much allocation and determine where
- in your app you should try to reduce allocations and release resources.
-</ol>
-
-
-
-<h3>Device Monitor</h3>
-<ol>
-<li>Open the Device Monitor.
-<p>From your <code><sdk>/tools/</code> directory, launch the <code>monitor</code> tool.</p>
-</li>
-<li>In the DDMS window, select your app's process in the left-side panel.</li>
-<li>In the right-side panel, select the <strong>Allocation Tracker</strong> tab.</li>
-<li>Click <strong>Start Tracking</strong>.</li>
-<li>Interact with your app to execute the code paths you want to analyze.</li>
-<li>Click <strong>Get Allocations</strong> every time you want to update the
-list of allocations.</li>
- </ol>
-
-<p>The list shows all recent allocations,
-currently limited by a 512-entry ring buffer. Click on a line to see the stack trace that led to
-the allocation. The trace shows you not only what type of object was allocated, but also in which
-thread, in which class, in which file and at which line.</p>
-
-<img src="{@docRoot}images/tools/monitor-tracker@2x.png" width="760" alt="" />
-<p class="img-caption"><strong>Figure 2.</strong> The Device Monitor tool,
-showing recent app allocations and stack traces in the Allocation Tracker.</p>
-
-
-<p class="note"><strong>Note:</strong> You will always see some allocations from {@code
-DdmVmInternal} and elsewhere that come from the allocation tracker itself.</p>
-
-<p>Although it's not necessary (nor possible) to remove all allocations from your performance
-critical code paths, the allocation tracker can help you identify important issues in your code.
-For instance, some apps might create a new {@link android.graphics.Paint} object on every draw.
-Moving that object into a global member is a simple fix that helps improve performance.</p>
-
-
-
-
-
-
-<h2 id="ViewingAllocations">Viewing Overall Memory Allocations</h2>
-
-<p>For further analysis, you may want to observe how your app's memory is
-divided between different types of RAM allocation with the
-following <a href="{@docRoot}tools/help/adb.html">adb</a> command:</p>
-
-<pre class="no-pretty-print">
-adb shell dumpsys meminfo <package_name|pid> [-d]
-</pre>
-
-<p>The -d flag prints more info related to Dalvik and ART memory usage.</p>
-
-<p>The output lists all of your app's current allocations, measured in kilobytes.</p>
-
-<p>When inspecting this information, you should be familiar with the
-following types of allocation:</p>
-
-<dl>
-<dt>Private (Clean and Dirty) RAM</dt>
-<dd>This is memory that is being used by only your process. This is the bulk of the RAM that the system
-can reclaim when your app’s process is destroyed. Generally, the most important portion of this is
-“private dirty” RAM, which is the most expensive because it is used by only your process and its
-contents exist only in RAM so can’t be paged to storage (because Android does not use swap). All
-Dalvik and native heap allocations you make will be private dirty RAM; Dalvik and native
-allocations you share with the Zygote process are shared dirty RAM.</dd>
-
-<dt>Proportional Set Size (PSS)</dt>
-<dd>This is a measurement of your app’s RAM use that takes into account sharing pages across processes.
-Any RAM pages that are unique to your process directly contribute to its PSS value, while pages
-that are shared with other processes contribute to the PSS value only in proportion to the amount
-of sharing. For example, a page that is shared between two processes will contribute half of its
-size to the PSS of each process.</dd>
-</dl>
-
-
-<p>A nice characteristic of the PSS measurement is that you can add up the PSS across all processes to
-determine the actual memory being used by all processes. This means PSS is a good measure for the
-actual RAM weight of a process and for comparison against the RAM use of other processes and the
-total available RAM.</p>
-
-
-<p>For example, below is the the output for Map’s process on a Nexus 5 device. There is a lot of
-information here, but key points for discussion are listed below.</p>
-<code>adb shell dumpsys meminfo com.google.android.apps.maps -d</code>
-
-<p class="note"><strong>Note:</strong> The information you see may vary slightly from what is shown
-here, as some details of the output differ across platform versions.</p>
-
-<pre class="no-pretty-print">
-** MEMINFO in pid 18227 [com.google.android.apps.maps] **
- Pss Private Private Swapped Heap Heap Heap
- Total Dirty Clean Dirty Size Alloc Free
- ------ ------ ------ ------ ------ ------ ------
- Native Heap 10468 10408 0 0 20480 14462 6017
- Dalvik Heap 34340 33816 0 0 62436 53883 8553
- Dalvik Other 972 972 0 0
- Stack 1144 1144 0 0
- Gfx dev 35300 35300 0 0
- Other dev 5 0 4 0
- .so mmap 1943 504 188 0
- .apk mmap 598 0 136 0
- .ttf mmap 134 0 68 0
- .dex mmap 3908 0 3904 0
- .oat mmap 1344 0 56 0
- .art mmap 2037 1784 28 0
- Other mmap 30 4 0 0
- EGL mtrack 73072 73072 0 0
- GL mtrack 51044 51044 0 0
- Unknown 185 184 0 0
- TOTAL 216524 208232 4384 0 82916 68345 14570
-
- Dalvik Details
- .Heap 6568 6568 0 0
- .LOS 24771 24404 0 0
- .GC 500 500 0 0
- .JITCache 428 428 0 0
- .Zygote 1093 936 0 0
- .NonMoving 1908 1908 0 0
- .IndirectRef 44 44 0 0
-
- Objects
- Views: 90 ViewRootImpl: 1
- AppContexts: 4 Activities: 1
- Assets: 2 AssetManagers: 2
- Local Binders: 21 Proxy Binders: 28
- Parcel memory: 18 Parcel count: 74
- Death Recipients: 2 OpenSSL Sockets: 2
-</pre>
-
-<p>Here is an older dumpsys on Dalvik of the gmail app:</p>
-
-<pre class="no-pretty-print">
-** MEMINFO in pid 9953 [com.google.android.gm] **
- Pss Pss Shared Private Shared Private Heap Heap Heap
- Total Clean Dirty Dirty Clean Clean Size Alloc Free
- ------ ------ ------ ------ ------ ------ ------ ------ ------
- Native Heap 0 0 0 0 0 0 7800 7637(6) 126
- Dalvik Heap 5110(3) 0 4136 4988(3) 0 0 9168 8958(6) 210
- Dalvik Other 2850 0 2684 2772 0 0
- Stack 36 0 8 36 0 0
- Cursor 136 0 0 136 0 0
- Ashmem 12 0 28 0 0 0
- Other dev 380 0 24 376 0 4
- .so mmap 5443(5) 1996 2584 2664(5) 5788 1996(5)
- .apk mmap 235 32 0 0 1252 32
- .ttf mmap 36 12 0 0 88 12
- .dex mmap 3019(5) 2148 0 0 8936 2148(5)
- Other mmap 107 0 8 8 324 68
- Unknown 6994(4) 0 252 6992(4) 0 0
- TOTAL 24358(1) 4188 9724 17972(2)16388 4260(2)16968 16595 336
-
- Objects
- Views: 426 ViewRootImpl: 3(8)
- AppContexts: 6(7) Activities: 2(7)
- Assets: 2 AssetManagers: 2
- Local Binders: 64 Proxy Binders: 34
- Death Recipients: 0
- OpenSSL Sockets: 1
-
- SQL
- MEMORY_USED: 1739
- PAGECACHE_OVERFLOW: 1164 MALLOC_SIZE: 62
-</pre>
-
-<p>Generally, you should be concerned with only the <code>Pss Total</code> and <code>Private Dirty</code>
-columns. In some cases, the <code>Private Clean</code> and <code>Heap Alloc</code> columns also offer
-interesting data. Here is some more information about the different memory allocations (the rows)
-you should observe:
-
-<dl>
-<dt><code>Dalvik Heap</code></dt>
-<dd>The RAM used by Dalvik allocations in your app. The <code>Pss Total</code> includes all Zygote
-allocations (weighted by their sharing across processes, as described in the PSS definition above).
-The <code>Private Dirty</code> number is the actual RAM committed to only your app’s heap, composed of
-your own allocations and any Zygote allocation pages that have been modified since forking your
-app’s process from Zygote.
-
-<p class="note"><strong>Note:</strong> On newer platform versions that have the <code>Dalvik
-Other</code> section, the <code>Pss Total</code> and <code>Private Dirty</code> numbers for Dalvik Heap do
-not include Dalvik overhead such as the just-in-time compilation (JIT) and GC
-bookkeeping, whereas older versions list it all combined under <code>Dalvik</code>.</p>
-
-<p>The <code>Heap Alloc</code> is the amount of memory that the Dalvik and native heap allocators keep
-track of for your app. This value is larger than <code>Pss Total</code> and <code>Private Dirty</code>
-because your process was forked from Zygote and it includes allocations that your process shares
-with all the others.</p>
-</dd>
-
-<dt><code>.so mmap</code> and <code>.dex mmap</code></dt>
-<dd>The RAM being used for mapped <code>.so</code> (native) and <code>.dex</code> (Dalvik or ART)
-code. The <code>Pss Total</code> number includes platform code shared across apps; the
-<code>Private Clean</code> is your app’s own code. Generally, the actual mapped size will be much
-larger—the RAM here is only what currently needs to be in RAM for code that has been executed by
-the app. However, the .so mmap has a large private dirty, which is due to fix-ups to the native
-code when it was loaded into its final address.
-</dd>
-
-<dt><code>.oat mmap</code></dt>
-<dd>This is the amount of RAM used by the code image which is based off of the preloaded classes
-which are commonly used by multiple apps. This image is shared across all apps and is unaffected
-by particular apps.
-</dd>
-
-<dt><code>.art mmap</code></dt>
-<dd>This is the amount of RAM used by the heap image which is based off of the preloaded classes
-which are commonly used by multiple apps. This image is shared across all apps and is unaffected
-by particular apps. Even though the ART image contains {@link java.lang.Object} instances, it does not
-count towards your heap size.
-</dd>
-
-<dt><code>.Heap</code> (only with -d flag)</dt>
-<dd>This is the amount of heap memory for your app. This excludes objects in the image and large
-object spaces, but includes the zygote space and non-moving space.
-</dd>
-
-<dt><code>.LOS</code> (only with -d flag)</dt>
-<dd>This is the amount of RAM used by the ART large object space. This includes zygote large
-objects. Large objects are all primitive array allocations larger than 12KB.
-</dd>
-
-<dt><code>.GC</code> (only with -d flag)</dt>
-<dd>This is the amount of internal GC accounting overhead for your app. There is not really any way
-to reduce this overhead.
-</dd>
-
-<dt><code>.JITCache</code> (only with -d flag)</dt>
-<dd>This is the amount of memory used by the JIT data and code caches. Typically, this is zero
-since all of the apps will be compiled at installed time.
-</dd>
-
-<dt><code>.Zygote</code> (only with -d flag)</dt>
-<dd>This is the amount of memory used by the zygote space. The zygote space is created during
-device startup and is never allocated into.
-</dd>
-
-<dt><code>.NonMoving</code> (only with -d flag)</dt>
-<dd>This is the amount of RAM used by the ART non-moving space. The non-moving space contains
-special non-movable objects such as fields and methods. You can reduce this section by using fewer
-fields and methods in your app.
-</dd>
-
-<dt><code>.IndirectRef</code> (only with -d flag)</dt>
-<dd>This is the amount of RAM used by the ART indirect reference tables. Usually this amount is
-small, but if it is too high, it may be possible to reduce it by reducing the number of local and
-global JNI references used.
-</dd>
-
-<dt><code>Unknown</code></dt>
-<dd>Any RAM pages that the system could not classify into one of the other more specific items.
-Currently, this contains mostly native allocations, which cannot be identified by the tool when
-collecting this data due to Address Space Layout Randomization (ASLR). As with the Dalvik heap, the
-<code>Pss Total</code> for Unknown takes into account sharing with Zygote, and <code>Private Dirty</code>
-is unknown RAM dedicated to only your app.
-</dd>
-
-<dt><code>TOTAL</code></dt>
-<dd>The total Proportional Set Size (PSS) RAM used by your process. This is the sum of all PSS fields
-above it. It indicates the overall memory weight of your process, which can be directly compared
-with other processes and the total available RAM.
-
-<p>The <code>Private Dirty</code> and <code>Private Clean</code> are the total allocations within your
-process, which are not shared with other processes. Together (especially <code>Private Dirty</code>),
-this is the amount of RAM that will be released back to the system when your process is destroyed.
-Dirty RAM is pages that have been modified and so must stay committed to RAM (because there is no
-swap); clean RAM is pages that have been mapped from a persistent file (such as code being
-executed) and so can be paged out if not used for a while.</p>
-
-</dd>
-
-<dt><code>ViewRootImpl</code></dt>
-<dd>The number of root views that are active in your process. Each root view is associated with a
-window, so this can help you identify memory leaks involving dialogs or other windows.
-</dd>
-
-<dt><code>AppContexts</code> and <code>Activities</code></dt>
-<dd>The number of app {@link android.content.Context} and {@link android.app.Activity} objects that
-currently live in your process. This can be useful to quickly identify leaked {@link
-android.app.Activity} objects that can’t be garbage collected due to static references on them,
-which is common. These objects often have a lot of other allocations associated with them and so
-are a good way to track large memory leaks.</dd>
-
-<p class="note"><strong>Note:</strong> A {@link android.view.View} or {@link
-android.graphics.drawable.Drawable} object also holds a reference to the {@link
-android.app.Activity} that it's from, so holding a {@link android.view.View} or {@link
-android.graphics.drawable.Drawable} object can also lead to your app leaking an {@link
-android.app.Activity}.</p>
-
-</dd>
-</dl>
-
-
-
-
-
-
-
-
-
-<h2 id="HeapDump">Capturing a Heap Dump</h2>
-
-<p>A heap dump is a snapshot of all the objects in your app's heap, stored in a binary format called
-HPROF. Your app's heap dump provides information about the overall state of your app's heap so you
-can track down problems you might have identified while viewing heap updates.</p>
-
-
-<p>To retrieve your heap dump from within Android Studio, use the
-<a href="{@docRoot}tools/studio/index.html#mem-cpu">Memory Monitor</a> and
-<a href="{@docRoot}tools/studio/index.html#heap-dump">HPROF viewer</a>.
-
-<p>You can also still perform these procedures in the Android monitor:</p>
-<ol>
-<li>Open the Device Monitor.
-<p>From your <code><sdk>/tools/</code> directory, launch the <code>monitor</code> tool.</p>
-</li>
-<li>In the DDMS window, select your app's process in the left-side panel.</li>
-<li>Click <strong>Dump HPROF file</strong>, shown in figure 3.</li>
-<li>In the window that appears, name your HPROF file, select the save location,
-then click <strong>Save</strong>.</li>
-</ol>
-
-<img src="{@docRoot}images/tools/monitor-hprof@2x.png" width="760" alt="" />
-<p class="img-caption"><strong>Figure 3.</strong> The Device Monitor tool,
-showing the <strong>[1] Dump HPROF file</strong> button.</p>
-
-<p>If you need to be more precise about when the dump is created, you can also create a heap dump
-at the critical point in your app code by calling {@link android.os.Debug#dumpHprofData
-dumpHprofData()}.</p>
-
-<p>The heap dump is provided in a format that's similar to, but not identical to one from the Java
-HPROF tool. The major difference in an Android heap dump is due to the fact that there are a large
-number of allocations in the Zygote process. But because the Zygote allocations are shared across
-all app processes, they don’t matter very much to your own heap analysis.</p>
-
-<p>To analyze your heap dump, you can use <a href=
-"{@docRoot}tools/help/am-memory.html">Memory Monitor</a> in Android Studio.
-You can also use a standard tool like jhat. However, first
-you'll need to convert the HPROF file from Android's format to the J2SE HPROF format. You can do
-this using the <code>hprof-conv</code> tool provided in the
-<code><sdk>/platform-tools/</code>
-directory. Simply run the <code>hprof-conv</code> command with two arguments: the original HPROF
-file and the location to write the converted HPROF file. For example:</p>
-
-<pre class="no-pretty-print">
-hprof-conv heap-original.hprof heap-converted.hprof
-</pre>
-
-
-
-<p>You can now load the converted file into a heap analysis tool that understands
-the J2SE HPROF format.</p>
-
-<p>When analyzing your heap, you should look for memory leaks caused by:</p>
-<ul>
-<li>Long-lived references to an Activity, Context, View, Drawable, and other objects that may hold a
-reference to the container Activity or Context.</li>
-<li>Non-static inner classes (such as a Runnable, which can hold the Activity instance).</li>
-<li>Caches that hold objects longer than necessary.</li>
-</ul>
-
-
-
-
-<h2 id="TriggerLeaks">Triggering Memory Leaks</h2>
-
-<p>While using the tools described above, you should aggressively stress your app code and try
-forcing memory leaks. One way to provoke memory leaks in your app is to let it
-run for a while before inspecting the heap. Leaks will trickle up to the top of the allocations in
-the heap. However, the smaller the leak, the longer you need to run the app in order to see it.</p>
-
-<p>You can also trigger a memory leak in one of the following ways:</p>
-<ol>
-<li>Rotate the device from portrait to landscape and back again multiple times while in different
-activity states. Rotating the device can often cause an app to leak an {@link android.app.Activity},
-{@link android.content.Context}, or {@link android.view.View} object because the system
-recreates the {@link android.app.Activity} and if your app holds a reference
-to one of those objects somewhere else, the system can't garbage collect it.</li>
-<li>Switch between your app and another app while in different activity states (navigate to
-the Home screen, then return to your app).</li>
-</ol>
-
-<p class="note"><strong>Tip:</strong> You can also perform the above steps by using the "monkey"
-test framework. For more information on running the monkey test framework, read the <a href=
-"{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a>
-documentation.</p>
+++ /dev/null
-page.title=Debugging with Android Studio
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-<h2>In this document</h2>
-<ol>
- <li><a href="#runDebug">Run your App in Debug Mode</a>
- <ol>
- <li><a href="#attachDebug">Attach the debugger to a running process</a></li>
- </ol>
- <li><a href="#systemLog">Use the System Log</a>
- <ol>
- <li><a href="#systemLogWrite">Write log messages in your code</a></li>
- <li><a href="#systemLogView">View the system log</a></li>
- </ol>
- </li>
- <li><a href="#breakPoints">Work with Breakpoints</a>
- <ol>
- <li><a href="#breakPointsView">View and configure breakpoints</a></li>
- <li><a href="#breakPointsDebug">Debug your app with breakpoints</a></li>
- </ol>
- </li>
- <li><a href="#allocTracker">Track Object Allocation</a></li>
- <li><a href="#deviceMonitor">Analyze Runtime Metrics to Optimize your App</a></li>
- <li><a href="#screenCap">Capture Screenshots and Videos</a></li>
-</ol>
-<h2>See also</h2>
-<ul>
-<li><a href="{@docRoot}sdk/installing/studio-tips.html">
-Android Studio Tips and Tricks</a></li>
-<li><a href="{@docRoot}tools/debugging/index.html">Debugging</a></li>
-<li><a href="{@docRoot}tools/help/android-monitor.html">Android Monitor</a></li>
-<li><a href="{@docRoot}tools/help/monitor.html">Device Monitor</a></li>
-<li><a href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a></li>
-</div>
-</div>
-
-<p>Android Studio enables you to debug apps running on the emulator or on an Android device.
-With Android Studio, you can:</p>
-
-<ul>
- <li>Select a device to debug your app on.</li>
- <li>View the system log.</li>
- <li>Set breakpoints in your code.</li>
- <li>Examine variables and evaluate expressions at run time.</li>
- <li>Run the debugging tools from the Android SDK.</li>
- <li>Capture screenshots and videos of your app.</li>
-</ul>
-
-<p>To debug your app, Android Studio builds a debuggable version of your app, connects
-to a device or to the emulator, installs the app and runs it. The IDE shows the system log
-while your app is running and provides debugging tools to filter log messages, work with
-breakpoints, and control the execution flow.</p>
-
-
-<h2 id="runDebug">Run your App in Debug Mode</h2>
-
-<div class="figure" style="width:419px">
- <img src="{@docRoot}images/tools/as-debugdevices.png" alt=""/>
- <p class="img-caption"><strong>Figure 1.</strong> The Choose Device window enables you to
- select a physical Android device or a virtual device to debug your app.</p>
-</div>
-
-<p>To run your app in debug mode, you build an APK signed with a debug key and install it on a
-physical Android device or on the Android emulator.
-To set up an Android device for development, see <a href="{@docRoot}tools/device.html">Using
-Hardware Devices</a>. For more information about the emulator provided by the Android SDK, see
-<a href="{@docRoot}tools/devices/emulator.html">Using the Emulator.</a></p>
-
-<p>To debug your app in Android Studio:</p>
-
-<ol>
- <li>Open your project in Android Studio.</li>
- <li>Click <strong>Debug</strong> <img src="{@docRoot}images/tools/as-debugbutton.png"
- style="vertical-align:bottom;margin:0;height:22px" alt=""/> in the toolbar.</li>
- <li>On the <em>Choose Device</em> window, select a hardware device from the list or
- choose a virtual device.</li>
- <li>Click <strong>OK</strong>. Your app starts on the selected device.</li>
-</ol>
-
-<p>Figure 1 shows the <em>Choose Device</em> window. The list shows all the Android devices
-connected to your computer. Select <strong>Launch Emulator</strong> to use an Android virtual device
-instead. Click the ellipsis <img src="{@docRoot}images/tools/as-launchavdm.png"
-style="vertical-align:bottom;margin:0;height:19px" alt=""/> to open the
-<a href="{@docRoot}tools/devices/managing-avds.html">Android Virtual Device Manager</a>.</p>
-
-<p>Android Studio opens the <em>Debug</em> tool window when you debug your app. To open the
-<em>Debug</em> window manually, click <strong>Debug</strong>
-<img src="{@docRoot}images/tools/as-debugwindowbutton.png"
-alt="" style="vertical-align:bottom;margin:0;height:20px"/>.
-This window shows threads and variables in the <em>Debugger</em> tab, the device status in the
-<em>Console</em> tab, and the system log in the <em>Logcat</em> tab. The <em>Debug</em> tool
-window also provides other debugging tools covered in the following sections.</p>
-
-<img src="{@docRoot}images/tools/as-debugview.png" alt="" />
-<p class="img-caption"><strong>Figure 2.</strong> The Debug tool window in Android Studio showing
-the current thread and the object tree for a variable.</p>
-
-<h3 id="attachDebug">Attach the debugger to a running process</h3>
-
-<p>You don't always have to restart your app to debug it. To debug an app that
-you're already running:</p>
-
-<ol>
-<li>Click <strong>Attach debugger to Android process</strong>
-<img src="{@docRoot}images/tools/as-attach.png"
-alt="Attach debugger to Android process icon"
-style="vertical-align:bottom;margin:0;height:20px"/>.</li>
-<li>In the <em>Choose Process</em> dialog, select the process you want to
-attach the debugger to.</li>
-<p>By default, the debugger shows the device and app process for the current
-project, as well as any connected hardware devices or virtual devices on your
-computer. Select <strong>Show all processes</strong> to show all processes on
-all devices; the display includes any services that your app created as well as
-system processes, for example.</p>
-<p>From the <strong>Debugger</strong> menu, you can select <strong>Java</strong>,
-<strong>Native</strong>, or <strong>Hybrid</strong>. The latter two options are
-available only if your project contains some native C or C++ source code.</p>
-<li>Click <strong>OK</strong>.</li>
-<p>The <em>Debug</em> window appears. In this case, notice the two tabs to the
-right of the Debug window title: one tab is for debugging native code and the
-other for Java code, as indicated by <strong>-java</strong>. </p>
-<img src="{@docRoot}images/tools/db-attachprocess.png" width="587"
-alt="" />
-<p>Separate debugging sessions have separate tabs and different port numbers,
-which are displayed in parentheses in the tab.</p>
-</ol>
-
-<h2 id="systemLog">Use the System Log</h2>
-
-<p>The system log shows system messages while you debug your app. These messages include
-information from apps running on the device. If you want to use the
-system log to debug your app, make sure your code writes log messages and prints the stack
-trace for exceptions while your app is in the development phase.</p>
-
-<h3 id="systemLogWrite">Write log messages in your code</h3>
-
-<p>To write log messages in your code, use the {@link android.util.Log} class. Log messages
-help you understand the execution flow by collecting the system debug output while you interact
-with your app. Log messages can tell you what part of your application failed. For more
-information about logging, see <a href="{@docRoot}tools/debugging/debugging-log.html">
-Reading and Writing Logs</a>.</p>
-
-<p>The following example shows how you might add log messages to determine if previous state
-information is available when your activity starts:</p>
-
-<pre>
-import android.util.Log;
-...
-public class MyActivity extends Activity {
- private static final String TAG = MyActivity.class.getSimpleName();
- ...
- @Override
- public void onCreate(Bundle savedInstanceState) {
- if (savedInstanceState != null) {
- Log.d(TAG, "onCreate() Restoring previous state");
- /* restore state */
- } else {
- Log.d(TAG, "onCreate() No saved state available");
- /* initialize app */
- }
- }
-}
-</pre>
-
-<p>During development, your code can also catch exceptions and write the stack trace to the system
-log:</p>
-
-<pre>
-void someOtherMethod() {
- try {
- ...
- } catch (SomeException e) {
- Log.d(TAG, "someOtherMethod()", e);
- }
-}
-</pre>
-
-<p class="note"><strong>Note:</strong> Remove debug log messages and stack trace print calls from
-your code when you are ready to publish your app. You could do this by setting a <code>DEBUG</code>
-flag and placing debug log messages inside conditional statements.</p>
-
-
-<h3 id="systemLogView">View the system log</h3>
-
-<p>Both the <em>Android DDMS</em> (Dalvik Debug Monitor Server) and the <em>Debug</em> tool windows
-show the system log; however, the <em>Android DDMS</em> tool window lets you view only log messages
-for a particular process. To view the system log on the <em>Android DDMS</em> tool window:</p>
-
-<ol>
- <li>Start your app as described in <a href="#runDebug">Run your App in Debug Mode</a>.</li>
- <li>Click <strong>Android</strong> <img src="{@docRoot}images/tools/as-android.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/> to open the <em>Android DDMS</em>
- tool window.</li>
- <li>If the system log is empty in the <em>Logcat view</em>, click <strong>Restart</strong>
- <img src="{@docRoot}images/tools/as-restart.png" alt=""
- style="vertical-align:bottom;margin:0;height:22px"/>.</li>
-</ol>
-
-<img src="{@docRoot}images/tools/as-ddmslog.png" alt="" />
-<p class="img-caption"><strong>Figure 4.</strong> The system log in the Android DDMS tool
-window.</p>
-
-<p>The <em>Android DDMS</em> tool window gives you access to some DDMS features from Android Studio.
-For more information about DDMS, see <a href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a>.
-</p>
-
-<p>The system log shows messages from Android services and other Android apps. To filter the log
-messages to view only the ones you are interested in, use the tools in the <em>Android DDMS</em>
-window:</p>
-
-<ul>
- <li>To show only log messages for a particular process, select the process in the
- <em>Devices</em> view and then click <strong>Only Show Logcat from Selected
- Process</strong> <img src="{@docRoot}images/tools/as-currentproc.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>. If the <em>Devices</em> view
- is not available, click <strong>Restore Devices View</strong>
- <img src="{@docRoot}images/tools/as-showdevview.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/> on the right of the <em>Android
- DDMS</em> tool window. This button is only visible when you hide the <em>Devices</em>
- window.</li>
- <li>To filter log messages by log level, select a level under <em>Log Level</em> on the top
- of the <em>Android DDMS</em> window.</li>
- <li>To show only log messages that contain a particular string, enter the string in the search
- box and press <strong>Enter</strong>.</li>
-</ul>
-
-
-<h2 id="breakPoints">Work with Breakpoints</h2>
-
-<p>Breakpoints enable you to pause the execution of your app at a particular line of code, examine
-variables, evaluate expressions, and continue the execution line by line. Use breakpoints to
-determine the causes of run-time errors that you can't fix by looking at your code only. To debug
-your app using breakpoints:</p>
-
-<ol>
- <li>Open the source file in which you want to set a breakpoint.</li>
- <li>Locate the line where you want to set a breakpoint and click on it.</li>
- <li>Click on the yellow portion of the side bar to the left of this line, as shown in figure 5.</li>
- <li>Start your app as described in <a href="#runDebug">Run your App in Debug Mode</a>.</li>
-</ol>
-
-<p>Android Studio pauses the execution of your app when it reaches the breakpoint. You can then
-use the tools in the <em>Debug</em> tool window to identify the cause of the error.</p>
-
-<img src="{@docRoot}images/tools/as-breakpointline.png" alt="" />
-<p class="img-caption"><strong>Figure 5.</strong> A red dot appears next to the line when you set
-a breakpoint.</p>
-
-<h3 id="breakPointsView">View and configure breakpoints</h3>
-
-<p>To view all the breakpoints and configure breakpoint settings, click <strong>View
-Breakpoints</strong> <img src="{@docRoot}images/tools/as-viewbreakbutton.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/> on the left side of the <em>Debug</em> tool
-window. The <em>Breakpoints</em> window appears, as shown in figure 6.</p>
-
-<img src="{@docRoot}images/tools/as-breakpointswindow.png" alt="" />
-<p class="img-caption"><strong>Figure 6.</strong> The Breakpoints window lists all the current
-breakpoints and includes behavior settings for each.</p>
-
-<p>The <em>Breakpoints</em> window lets you enable or disable each breakpoint from the
-list on the left. If a breakpoint is disabled, Android Studio does not pause your app when
-it hits that breakpoint. Select a breakpoint from the list to configure its settings.
-You can configure a breakpoint to be disabled at first and have the system enable it after a
-different breakpoint is hit. You can also configure whether a breakpoint should be disabled after
-it is hit. To set a breakpoint for any exception, select <strong>Exception Breakpoints</strong>
-in the list of breakpoints.</p>
-
-<h3 id="breakPointsDebug">Debug your app with breakpoints</h3>
-
-<p>After you set breakpoints in your code, click <strong>Rerun</strong>
-<img src="{@docRoot}images/tools/as-restart.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/> to start the app again. When a breakpoint is
-hit, Android Studio pauses the app and highlights the breakpoint in the source code. The
-<em>Debug</em> tool window lets you examine variables and control the execution step by
-step:</p>
-
-<ul>
- <li>
- <p>To examine the object tree for a variable, expand it in the <em>Variables</em> view. If
- the <em>Variables</em> view is not visible, click <strong>Restore Variables View</strong>
- <img src="{@docRoot}images/tools/as-varviewbutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
- <li>
- <p>To evaluate an expression at the current execution point, click <strong>Evaluate
- Expression</strong> <img src="{@docRoot}images/tools/as-evalexpbutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
- <li>
- <p>To advance to the next line in the code (without entering a method), click <strong>Step
- Over</strong> <img src="{@docRoot}images/tools/as-stepoverbutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
- <li>
- <p>To advance to the first line inside a method call, click <strong>Step
- Into</strong> <img src="{@docRoot}images/tools/as-stepintobutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
- <li>
- <p>To advance to the next line outside the current method, click <strong>Step
- Out</strong> <img src="{@docRoot}images/tools/as-stepoutbutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
- <li>
- <p>To continue running the app normally, click <strong>Resume Program</strong>
- <img src="{@docRoot}images/tools/as-resumeprogrambutton.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/>.</p>
- </li>
-</ul>
-
-<img src="{@docRoot}images/tools/as-variablesview.png" alt="" />
-<p class="img-caption"><strong>Figure 7.</strong> The Variables view in the Debug tool window.</p>
-
-
-<h2 id="allocTracker">Track Object Allocation</h2>
-
-<p>Android Studio lets you track objects that are being allocated on the Java heap and see which
-classes and threads are allocating these objects. This allows you to see the list of objects
-allocated during a period of interest. This information is valuable for assessing memory usage
-that can affect application performance.</p>
-
-<p>To track memory allocation of objects:</p>
-
-<ol>
-<li>Start your app as described in <a href="#runDebug">Run Your App in Debug Mode</a>.</li>
-<li>Click <strong>Android</strong> <img src="{@docRoot}images/tools/as-android.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/> to open the <em>Android DDMS</em>
-tool window.</li>
-<li>On the <em>Android DDMS</em> tool window, select the <strong>Devices | logcat tab</strong>.</li>
-<li>Select your device from the dropdown list.</li>
-<li>Select your app by its package name from the list of running apps.</li>
-<li>Click <strong>Start Allocation Tracking</strong>
-<img src="{@docRoot}images/tools/as-allocstart.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/></li>
-<li>Interact with your app on the device.</li>
-<li>Click <strong>Stop Allocation Tracking</strong>
-<img src="{@docRoot}images/tools/as-allocstop.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/></li>
-</ol>
-
-<p>Android Studio shows the objects that the system allocated with the following information:</p>
-
-<ul>
-<li>Allocation order</li>
-<li>Allocated class</li>
-<li>Allocation size</li>
-<li>Thread ID</li>
-<li>Allocation method, class, and line number</li>
-<li>Stack trace at the point of allocation</li>
-</ul>
-
-<img src="{@docRoot}images/tools/as-alloctrack.png" alt="" width="750" height="252" />
-<p class="img-caption"><strong>Figure 8.</strong> Object allocation tracking in Android Studio.</p>
-
-
-<h2 id="deviceMonitor">Analyze Runtime Metrics to Optimize your App</h2>
-
-<p>Even if your application does not generate runtime errors, this does not mean it is free of
-problems. You should also consider the following issues:</p>
-
-<ul>
- <li>Does your app use memory efficiently?</li>
- <li>Does your app generate unnecessary network traffic?</li>
- <li>What methods should you focus your attention on to improve the performance of your app?</li>
- <li>Does your app behave properly when the user receives a phone call or a message?</li>
-</ul>
-
-<p>The Android Device Monitor is a stand-alone tool with a graphical user interface for serveral
-Android application debugging and analysis tools, including the Dalvik Debug Monitor Server (DDMS).
-You can use the Android Device Monitor to analyze memory usage, profile methods,
-monitor network traffic and simulate incoming calls and messages.</p>
-
-<p>To open the Android Device Monitor from Android Studio, click
-<strong>Monitor</strong> <img src="{@docRoot}images/tools/as-monitorbutton.png" alt=""
-style="vertical-align:bottom;margin:0;height:20px"/> on the toolbar. The Android Device Monitor
-opens in a new window.</p>
-
-<p>For more information about the Android Device Monitor and DDMS, see
-<a href="{@docRoot}tools/help/monitor.html">Device Monitor</a> and
-<a href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a>.</p>
-
-
-<h2 id="screenCap">Capture Screenshots and Videos</h2>
-
-<p>Android Studio enables you to capture a screenshot or a short video of the device screen
-while your app is running. Screenshots and videos are useful as promotional materials for your
-app, and you can also attach them to bug reports that you send to your development team.</p>
-
-<p>To take a screenshot of your app:</p>
-
-<ol>
- <li>Start your app as described in <a href="#runDebug">Run your App in Debug Mode</a>.</li>
- <li>Click <strong>Android</strong> <img src="{@docRoot}images/tools/as-android.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/> to open the <em>Android DDMS</em>
- tool window.</li>
- <li>Click <strong>Screen Capture</strong> <img src="{@docRoot}images/tools/as-capture.png"
- style="vertical-align:bottom;margin:0;height:22px" alt=""/> on the left side of the
- <em>Android DDMS</em> tool window.</li>
- <li>Optional: To add a device frame around your screenshot, enable the <em>Frame screenshot</em>
- option.</li>
- <li>Click <strong>Save</strong>.</li>
-</ol>
-
-<p>To take a video recording of your app:</p>
-
-<ol>
- <li>Start your app as described in <a href="#runDebug">Run your App in Debug Mode</a>.</li>
- <li>Click <strong>Android</strong> <img src="{@docRoot}images/tools/as-android.png" alt=""
- style="vertical-align:bottom;margin:0;height:20px"/> to open the <em>Android DDMS</em>
- tool window.</li>
- <li>Click <strong>Screen Record</strong> <img src="{@docRoot}images/tools/as-record.png"
- style="vertical-align:bottom;margin:0;height:22px" alt=""/> on the left side of the
- <em>Android DDMS</em> tool window.</li>
- <li>Click <strong>Start Recording</strong>.</li>
- <li>Interact with your app.</li>
- <li>Click <strong>Stop Recording</strong>.</li>
- <li>Enter a file name for the recording and click <strong>OK</strong>.</li>
-</ol>
+++ /dev/null
-page.title=Profiling with Traceview and dmtracedump
-parent.title=Debugging
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li>
- <a href="#traceviewLayout">Traceview Layout</a>
-
- <ol>
- <li><a href="#timelinepanel">Timeline Panel</a></li>
-
- <li><a href="#profilepanel">Profile Panel</a></li>
- </ol>
- </li>
-
- <li><a href="#creatingtracefiles">Creating Trace Files</a></li>
-
- <li><a href="#copyingfiles">Copying Trace Files to a Host Machine</a></li>
-
- <li><a href="#runningtraceview">Viewing Trace Files in Traceview</a></li>
-
- <li><a href="#dmtracedump">Using dmtracedump</a></li>
-
- <li><a href="#knownissues">Traceview Known Issues</a></li>
- </ol>
- </div>
- </div>
-
- <p>Traceview is a graphical viewer for execution logs that you create by using the {@link
- android.os.Debug} class to log tracing information in your code. Traceview can help you debug
- your application and profile its performance.</p>
-
- <h2 id="traceviewLayout">Traceview Layout</h2>
-
- <p>When you have a trace log file (generated by adding tracing code to your application or by DDMS),
- you can load the log files in Traceview, which displays the log data in two panels:</p>
-
- <ul>
- <li>A <a href="#timelinepanel">timeline panel</a> -- describes when each thread and method
- started and stopped</li>
-
- <li>A <a href="#timelinepanel">profile panel</a> -- provides a summary of what happened inside
- a method</li>
- </ul>
-
- <p>The sections below provide addition information about the traceview output panes.</p>
-
- <h3 id="timelinepanel">Timeline Panel</h3>
-
- <p>Figure 1 shows a close up of the timeline panel. Each thread’s execution is shown
- in its own row, with time increasing to the right. Each method is shown in another color (colors
- are reused in a round-robin fashion starting with the methods that have the most inclusive time).
- The thin lines underneath the first row show the extent (entry to exit) of all the calls to the
- selected method.</p>
-
- <img src="{@docRoot}images/traceview_timeline.png"
- alt="Traceview timeline panel"
- width="893"
- height="284" />
- <p class="img-caption"><strong>Figure 1.</strong> The Traceview Timeline Panel</p>
-
- <h3 id="profilepanel">Profile Panel</h3>
-
- <p>Figure 2 shows the profile pane, a summary of all the time spent
- in a method. The table shows both the inclusive and exclusive times (as well as the percentage of
- the total time). Exclusive time is the time spent in the method. Inclusive time is the time spent
- in the method plus the time spent in any called functions. We refer to calling methods as
- "parents" and called methods as "children." When a method is selected (by clicking on it), it
- expands to show the parents and children. Parents are shown with a purple background and children
- with a yellow background. The last column in the table shows the number of calls to this method
- plus the number of recursive calls. The last column shows the number of calls out of the total
- number of calls made to that method. In this view, we can see that there were 14 calls to
- <code>LoadListener.nativeFinished();</code> looking at the timeline panel shows that one of those calls took
- an unusually long time.</p>
-
- <img src="{@docRoot}images/traceview_profile.png"
- alt="Traceview profile panel."
- width="892"
- height="630" />
- <p class="img-caption"><strong>Figure 2.</strong> The Traceview Profile Panel</p>
-
- <h2 id="creatingtracefiles">Creating Trace Files</h2>
-
- <p>To use Traceview, you need to generate log files containing the trace information you want to
- analyze.</p>
-
- <p>There are two ways to generate trace logs:</p>
- <ul>
- <li>Include the {@link android.os.Debug} class in your code and call its
- methods such as {@link android.os.Debug#startMethodTracing()} and {@link
- android.os.Debug#stopMethodTracing()}, to start and stop logging of trace information to disk.
- This option is very precise because
- you can specify exactly where to start and stop logging trace data in your code.</li>
- <li>Use the method profiling feature of DDMS to generate trace logs. This option is less
- precise because you do not modify code, but rather specify when to start and stop logging with
- DDMS. Although you have less control on exactly where logging starts and stops,
- this option is useful if you don't have access to the application's code, or if you do
- not need precise log timing.
- </li>
- </ul>
-
- <p>Before you start generating trace logs, be aware of the following restrictions:</p>
- <ul>
- <li>If you are using the {@link android.os.Debug} class,
- your application must have permission to write to external storage
- ({@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE}). </li>
- <li>If you are using DDMS:
- <ul>
- <li>Android 2.1 and earlier devices must
- have an SD card present and your application must have permission to write to the SD card.
- <li>Android 2.2 and later devices do not need an SD card. The trace log files are
- streamed directly to your development machine.</li>
- </ul>
- </li>
- </ul>
-
- <p>This document focuses on using the {@link android.os.Debug} class to generate trace data. For more information on using DDMS
- to generate trace data, see <a href="ddms.html#profiling">Using the Dalvik Debug Monitor Server.</a>
- </p>
-
- <p>To create the trace files, include the {@link android.os.Debug} class and call one of the
- {@link android.os.Debug#startMethodTracing() startMethodTracing()} methods. In the call, you
- specify a base name for the trace files that the system generates. To stop tracing, call {@link
- android.os.Debug#stopMethodTracing() stopMethodTracing()}. These methods start and stop method
- tracing across the entire virtual machine. For example, you could call
- {@link android.os.Debug#startMethodTracing() startMethodTracing()} in
- your activity's {@link android.app.Activity#onCreate onCreate()} method, and call
- {@link android.os.Debug#stopMethodTracing() stopMethodTracing()} in that activity's
- {@link android.app.Activity#onDestroy()} method.</p>
- <pre>
- // start tracing to "/sdcard/calc.trace"
- Debug.startMethodTracing("calc");
- // ...
- // stop tracing
- Debug.stopMethodTracing();
-</pre>
-
- <p>When your application calls {@link android.os.Debug#startMethodTracing() startMethodTracing()},
- the system creates a file called
- <code><trace-base-name>.trace</code>. This contains the binary method trace data and a
- mapping table with thread and method names.</p>
-
- <p>The system then begins buffering the generated trace data, until your application calls
- {@link android.os.Debug#stopMethodTracing() stopMethodTracing()}, at which time it writes
- the buffered data to the output file. If the system
- reaches the maximum buffer size before you call {@link android.os.Debug#stopMethodTracing()
- stopMethodTracing()}, the system stops tracing
- and sends a notification to the console.</p>
-
- <p>Interpreted code runs more slowly when profiling is enabled. Don't try to generate
- absolute timings from the profiler results (such as, "function X takes 2.5 seconds to run"). The
- times are only useful in relation to other profile output, so you can see if changes have made
- the code faster or slower relative to a previous profiling run.</p>
-
- <p>In Android 4.4 and later, you can use sample-based profiling to profile with less runtime
- performance impact. To enable sample profiling, call {@link
- android.os.Debug#startMethodTracingSampling(java.lang.String, int, int)
- startMethodTracingSampling()} with a specified sampling interval. The system will then gather
- samples periodically until tracing is stopped via {@link android.os.Debug#stopMethodTracing()
- stopMethodTracing()}.</p>
-
- <h2 id="copyingfiles">Copying Trace Files to a Host Machine</h2>
-
- <p>After your application has run and the system has created your trace files
- <code><trace-base-name>.trace</code> on a device or emulator, you must copy those files to
- your development computer. You can use <code>adb pull</code> to copy the files. Here's an example
- that shows how to copy an example file, calc.trace, from the default location on the emulator to
- the /tmp directory on the emulator host machine:</p>
- <pre>
-adb pull /sdcard/calc.trace /tmp
-</pre>
-
- <h2 id="runningtraceview">Viewing Trace Files in Traceview</h2>
-
- <p>To run Traceview and view the trace files:</p>
- <ul>
- <li>start the
- <a href="{@docRoot}tools/help/monitor.html">Android Device Monitor</a>. </li>
- <li>In the Android Device Monitor tool bar, click <strong>DDMS</strong> and select a process. </li>
- <li>Click the <strong>Start Method Profiling</strong> icon to start method profiling. </li>
- <li>After the profiling is complete, click the <strong>Stop Method Profiling</strong> icon to
- display the traceview. </li>
- </ul>
-
- <p class="note"><strong>Note:</strong> If you are trying to view the trace logs of an application
- that is built with ProGuard enabled (release mode build), some method and member names might be obfuscated.
- You can use the Proguard <code>mapping.txt</code> file to figure out the original unobfuscated names. For more information
- on this file, see the <a href="{@docRoot}tools/help/proguard.html">Proguard</a> documentation.</p>
-
- <h2 id="dmtracedump">Using dmtracedump</h2>
-
- <p><code>dmtracedump</code> is a tool that gives you an alternate way of generating
- graphical call-stack diagrams from trace log files. The tool uses the Graphviz Dot utility to
- create the graphical output, so you need to install Graphviz before running dmtracedump.</p>
-
- <p>The dmtracedump tool generates the call stack data as a tree diagram, with each call
- represented as a node. It shows call flow (from parent node to child nodes) using arrows. The
- diagram below shows an example of dmtracedump output.</p>
- <img src=
- "{@docRoot}images/tracedump.png"
- width="485"
- height="401" />
- <p class="img-caption"><strong>Figure 3.</strong> Screenshot of dmtracedump</p>
-
- <p>For each node, dmtracedump shows <code><ref>
- <em>callname</em> (<inc-ms>, <exc-ms>,<numcalls>)</code>, where</p>
-
- <ul>
- <li><code><ref></code> -- Call reference number, as used in trace logs</li>
-
- <li><code><inc-ms></code> -- Inclusive elapsed time (milliseconds spent in method,
- including all child methods)</li>
-
- <li><code><exc-ms></code> -- Exclusive elapsed time (milliseconds spent in method,
- not including any child methods)</li>
-
- <li><code><numcalls></code> -- Number of calls</li>
- </ul>
-
- <p>The usage for dmtracedump is:</p>
- <pre>
-dmtracedump [-ho] [-s sortable] [-d trace-base-name] [-g outfile] <trace-base-name>
-</pre>
-
- <p>The tool then loads trace log data from <code><trace-base-name>.data</code> and
- <code><trace-base-name>.key</code>. The table below lists the options for dmtracedump.</p>
-
- <table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><code>-d <trace-base-name></code></td>
-
- <td>Diff with this trace name</td>
- </tr>
-
- <tr>
- <td><code>-g <outfile></code></td>
-
- <td>Generate output to <outfile></td>
- </tr>
-
- <tr>
- <td><code>-h</code></td>
-
- <td>Turn on HTML output</td>
- </tr>
-
- <tr>
- <td><code>-o</code></td>
-
- <td>Dump the trace file instead of profiling</td>
- </tr>
-
- <tr>
- <td><code>-d <trace-base-name></code></td>
-
- <td>URL base to the location of the sortable javascript file</td>
- </tr>
-
- <tr>
- <td><code>-t <percent></code></td>
-
- <td>Minimum threshold for including child nodes in the graph (child's inclusive time as a
- percentage of parent inclusive time). If this option is not used, the default threshold
- is 20%.</td>
- </tr>
- </table>
-
-
-
- <h2 id="knownissues">Traceview Known Issues</h2>
-
- <dl>
- <dt>Threads</dt>
-
- <dd>
- Traceview logging does not handle threads well, resulting in these two problems:
-
- <ol>
- <li>If a thread exits during profiling, the thread name is not emitted (fixed in Android 5.1
- and later);</li>
-
- <li>The VM reuses thread IDs. If a thread stops and another starts, they may get the same
- ID.</li>
- </ol>
- </dd>
-
- </dl>
+++ /dev/null
-page.title=Optimizing Your UI
-parent.title=Debugging
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li>
- <a href="#HierarchyViewer">
- Using Hierarchy Viewer
- </a>
- <ol>
- <li><a href="#runhv">Running Hierarchy Viewer and choosing a window</a></li>
- <li><a href="#viewhierarchy">About the View Hierarchy window</a></li>
- <li><a href="#indiView">Working with an individual View in Tree View</a></li>
- <li><a href="#hvdebugging">Debugging with View Hierarchy</a></li>
- <li><a href="#hvoptimize">Optimizing with View Hierarchy</a></li>
- </ol>
- </li>
- <li>
- <a href="#pixelperfect">
- Using Pixel Perfect
- </a>
- <ol>
- <li><a href="#aboutpixelperfect">About the Pixel Perfect window</a></li>
- <li><a href="#overlays">Working with Pixel Perfect overlays</a></li>
- </ol>
- </li>
- <li><a href="#lint">Using lint to optimize your UI</a></li>
- </ol>
- <h2>Related videos</h2>
- <ol>
- <li>
-<iframe title="Hierarchyviewer"
- width="210" height="160"
- src="//www.youtube.com/embed/PAgE7saQUUY?rel=0&hd=1"
- frameborder="0" allowfullscreen>
-</iframe>
- </li>
- <li>
-<iframe title="Pixel Perfect"
- width="210" height="160"
- src="//www.youtube.com/embed/C45bMZGdN7Y?rel=0&hd=1"
- frameborder="0"
- allowfullscreen>
-</iframe>
- </li>
- </ol>
- </div>
- </div>
-
-
-<p>Sometimes your application's layout can slow down your application.
-To help debug issues in your layout, the Android SDK provides the Hierarchy Viewer and
-<code><a href="{@docRoot}tools/help/lint.html">lint</a></code> tools. </p>
-
- <p>The Hierarchy Viewer application allows you to debug and optimize your user interface. It
- provides a visual representation of the layout's View hierarchy (the View Hierarchy window)
- with performance information for each node in the layout,
- and a magnified view of the display (the Pixel Perfect window) to closely examine the pixels
- in your layout.</p>
-
- <p>Android <code><a href="{@docRoot}tools/help/lint.html">lint</a></code> is a static code
- scanning tool that helps you optimize the layouts and layout
- hierarchies of your applications, as well as detect other common coding problems. You can run it
- against your layout files or resource
- directories to quickly check for inefficiencies or other types of problems that could be
- affecting the performance of your application.</p>
-
-<h2 id="HierarchyViewer">Using Hierarchy Viewer</h2>
-
-<h3 id="runhv">Running Hierarchy Viewer and choosing a window</h3>
-<p>
- To run Hierarchy Viewer, follow these steps:</p>
-<ol>
- <li>
- Connect your device or launch an emulator.
- <p>
- To preserve security, Hierarchy Viewer can only connect to devices running a
- developer version of the Android system.
- </p>
- </li>
- <li>
- If you have not done so already, install the application you want to work with.
- </li>
- <li>
- Run the application, and ensure that its UI is visible.
- </li>
- <li>
- From a terminal, launch <code>hierarchyviewer</code> from the
- <code><sdk>/tools/</code>
- directory.
- </li>
- <li>
- The first window you see displays a list of devices and emulators. To expand the list
- of Activity objects for a device or emulator, click the arrow on the left. This displays a
- list of the Activity objects whose UI is currently visible on the device or emulator. The
- objects are listed by their Android component name. The list includes both your application
- Activity and system Activity objects. A screenshot of this window appears in
- figure 1.
- </li>
- <li>
- Select the name of your Activity from the list. You can now look at its view
- hierarchy using the View Hierarchy window, or look at a magnified image of the UI using
- the Pixel Perfect window.
- </li>
-</ol>
-<p>
- To learn how to use the View Hierarchy window, go to
- <a href="#viewhierarchy">About the View Hierarchy window</a>. To learn how to use the
- Pixel Perfect window, go to <a href="#pixelperfect">About the Pixel Perfect window</a>.
-</p>
-<img id="Fig1" src="{@docRoot}images/developing/hv_device_window.png" alt="" height="600"/>
-<p class="img-caption"><strong>Figure 1.</strong> Hierarchy Viewer device window</p>
-<h3 id="viewhierarchy">About the View Hierarchy window</h3>
-<p>
- The View Hierarchy window displays the View objects that form the UI of the
- Activity that is running on your device or emulator. You use it to look at individual
- View objects within the context of the entire View tree. For each View object, the View
- Hierarchy window also displays rendering performance data.
-</p>
-<p>
- To see the View Hierarchy window, run Hierarchy Viewer as described in
- the section <a href="#runhv">Running Hierarchy Viewer and choosing a window</a>. Next, click
- <strong>View Hierarchy</strong> at the top of the device window.
-</p>
-<p>
- You should see four panes:
-</p>
-<ul>
- <li>
- <strong>Tree View</strong>: The left-hand pane displays the Tree View,
- a diagram of the Activity object's hierarchy of views. Use Tree View to examine individual
- View objects and see the relationships between View objects in your UI.
- <p>
- To zoom in on the pane, use the slider at the bottom of the pane, or use your mouse
- scroll wheel. To move around in the pane or reveal View objects that are not currently
- visible, click and drag the pane.
- </p>
- <p>
- To highlight the nodes in the tree whose class or ID match a search string, enter the
- string in the <strong>Filter by class or id:</strong> edit box at the bottom of the
- window. The background of nodes that match the search string will change from gray to
- bright blue.
- </p>
- <p>
- To save a screenshot of Tree View to a PNG file, click <strong>Save As PNG</strong> at
- the top of the View Hierarchy window. This displays a dialog in which you can choose
- a directory and file name.
- </p>
- <p>
- To save a layered screenshot of your device or emulator to an Adobe Photoshop (PSD)
- file, click <strong>Capture Layers</strong> at the top of the View Hierarchy window.
- This displays a dialog in which you can choose a directory or file name.
- Each View in the UI is saved as a separate Photoshop layer.
- </p>
- <p>
- In Photoshop (or similar program that accepts .psd files), you can hide, show or edit a
- layer independently of others. When you save a layered screenshot, you can examine and
- modify the image of an individual View object. This helps you experiment with design
- changes.
- </p>
- </li>
- <li>
- The upper right-hand pane displays the <strong>Tree Overview</strong>, a smaller map
- representation of the entire Tree View window. Use Tree Overview to identify the part of the
- view tree that is being displayed in Tree View.
- <p>
- You can also use Tree Overview to move around in the Tree View pane. Click and drag
- the shaded rectangle over an area to reveal it in Tree View.
- </p>
- </li>
- <li>
- The middle right-hand pane displays the <strong>Properties View</strong>,
- a list of the properties for a selected View object. With Properties View, you can
- examine all the properties without having to look at your application source.
- <p>
- The properties are organized by category. To find an individual property, expand
- a category name by clicking the arrow on its left. This reveals all the properties
- in that category.
- </p>
- </li>
- <li>
- The lower right-hand pane displays the <strong>Layout View</strong>,
- a block representation of the UI. Layout View is another way to navigate through your UI.
- When you click on a View object in Tree View, its position in the UI is highlighted.
- Conversely, when you click in an area of Layout View, the View object for that area is
- highlighted in Tree View.
- <p>
- The outline colors of blocks in Layout View provide additional information:
- </p>
- <ul>
- <li>
- Bold red: The block represents the the View that is currently selected in
- Tree View.
- </li>
- <li>
- Light red: The block represents the parent of the block outlined in bold red.
- </li>
- <li>
- White: The block represents a visible View that is not a parent or child of the
- View that is currently selected in Tree View.
- </li>
- </ul>
- </li>
-</ul>
-<p>
- When the UI of the current Activity changes, the View Hierarchy window is not automatically
- updated. To update it, click <strong>Load View Hierarchy</strong> at the top of the window.
-</p>
-<p>
- Also, the window is not updated if you switch to a new Activity. To update it, start by
- clicking the window selection icon in the bottom left-hand corner of the window. This
- navigates back to the Window Selection window. From this window, click the Android
- component name of the new Activity and then click <strong>Load View Hierarchy</strong>
- at the top of the window.
-</p>
-<p>
- A screenshot of the View Hierarchy window appears in figure 2.
-</p>
-<img id="Fig2" src="{@docRoot}images/developing/hv_view_hierarchy_window.png" alt="" height="600"/>
-<p class="img-caption"><strong>Figure 2.</strong> The View Hierarchy window</p>
-<h3 id="indiView">Working with an individual View in Tree View</h3>
-<p>
- Each node in Tree View represents a single View. Some information is always visible. Starting
- at the top of the node, you see the following:
-</p>
-<ol>
- <li>
- View class: The View object's class.
- </li>
- <li>
- View object address: A pointer to View object.
- </li>
- <li>
- View object ID: The value of the
- <code><a href="{@docRoot}guide/topics/resources/layout-resource.html#idvalue">android:id</a>
- </code> attribute.
- </li>
- <li>
- Performance indicators: A set of three colored dots that indicate the rendering
- speed of this View relative to other View objects in the tree. The three dots
- represent (from left to right) the measure, layout, and draw times of the rendering.
- <p>
- The colors indicate the following relative performance:
- </p>
- <ul>
- <li>
- Green: For this part of the render time, this View is in the faster 50% of all
- the View objects in the tree. For example, a green dot for the measure time means
- that this View has a faster measure time than 50% of the View objects in the tree.
- </li>
- <li>
- Yellow: For this part of the render time, this View is in the slower 50% of all
- the View objects in the tree. For example, a yellow dot for the layout time means
- that this View has a slower layout time than 50% of the View objects in the tree.
- </li>
- <li>
- Red: For this part of the render time, this View is the slowest one in the tree.
- For example, a red dot for the draw time means that this View takes the most
- time to draw of all the View objects in the tree.
- </li>
- </ul>
- </li>
- <li>
- View index: The zero-based index of the View in its parent View. If it is the only child,
- this is 0.
- </li>
-</ol>
-<p>
- When you select a node, additional information for the View appears in a small window above
- the node. When you click one of the nodes, you see the following:
-</p>
-<ul>
- <li>
- Image: The actual image of the View, as it would appear in the emulator. If the View has
- children, these are also displayed.
- </li>
- <li>
- View count: The number of View objects represented by this node. This includes the View
- itself and a count of its children. For example, this value is 4 for a View that has 3
- children.
- </li>
- <li>
- Render times: The actual measure, layout, and draw times for the View rendering, in
- milliseconds. These represent the same values as the performance indicators mentioned in
- the preceding section.
- </li>
-</ul>
-<p>
- An annotated screenshot of an individual node in the Tree View window appears in figure 3.
-</p>
-<img id="Fig3" src="{@docRoot}images/developing/hv_treeview_screenshot.png" alt="" height="600"/>
-<p class="img-caption"><strong>Figure 3.</strong> An annotated node in Tree View</p>
-<h3 id="hvdebugging">Debugging with View Hierarchy</h3>
-<p>
- The View Hierarchy window helps you debug an application by providing a static display
- of the UI. The display starts with your application's opening screen. As you step through
- your application, the display remains unchanged until you redraw it by invalidating and
- then requesting layout for a View.
-</p>
-<p>
- To redraw a View in the display:
-</p>
- <ul>
- <li>
- Select a View in Tree View. As you move up towards the root of the tree (to the
- left in the Tree View), you see the highest-level View objects. Redrawing a high-level
- object usually forces the lower-level objects to redraw as well.
- </li>
- <li>
- Click <strong>Invalidate</strong> at the top of the window. This marks the View as
- invalid, and schedules it for a redraw at the next point that a layout is requested.
- </li>
- <li>
- Click <strong>Request Layout</strong> to request a layout. The View and its children
- are redrawn, as well as any other View objects that need to be redrawn.
- </li>
- </ul>
-<p>
- Manually redrawing a View allows you to watch the View object tree and examine the properties of
- individual View objects one step at a time as you go through breakpoints in your code.
-</p>
-<h3 id="hvoptimize">Optimizing with View Hierarchy</h3>
-<p>
- View Hierarchy also helps you identify slow render performance. You start by looking at the
- View nodes with red or yellow performance indicators to identify the slower View objects. As you
- step through your application, you can judge if a View is consistently slow or slow only in
- certain circumstances.
-</p>
-<p>
- Remember that slow performance is not necessarily evidence of a problem, especially for
- ViewGroup objects. View objects that have more children and more complex View objects render
- more slowly.
-</p>
-<p>
- The View Hierarchy window also helps you find performance issues. Just by looking at the
- performance indicators (the dots) for each View node, you can see which View objects are the
- slowest to measure, layout, and draw. From that, you can quickly identify the problems you
- should look at first.
-</p>
-<h2 id="pixelperfect">Using Pixel Perfect</h2>
-<p>
- Pixel Perfect is a tool for examining pixel properties and laying out UIs from a design drawing.
-</p>
-<h3 id="aboutpixelperfect">About the Pixel Perfect window</h3>
-<p>
- The Pixel Perfect window displays a magnified image of the screen that is currently
- visible on the emulator or device. In it, you can examine the properties
- of individual pixels in the screen image. You can also use the Pixel Perfect window
- to help you lay out your application UI based on a bitmap design.
-</p>
-<p>
- To see the Pixel Perfect window, run Hierarchy Viewer, as described in
- the section <a href="#runhv">Running Hierarchy Viewer and choosing a window</a>. Next, click
- <strong>Inspect Screenshot</strong> at the top of the device window. The Pixel Perfect window
- appears.
-</p>
-<p>
- In it, you see three panes:
-</p>
-<ul>
- <li>
- View Object pane: This is a hierarchical list of the View objects that are currently
- visible on the device or emulator screen, including both the ones in your application and
- the ones generated by the system. The objects are listed by their View class.
- To see the class names of a View object's children, expand the View by clicking the
- arrow to its left. When you click a View, its position is highlighted in the Pixel Perfect
- pane on the right.
- </li>
- <li>
- Pixel Perfect Loupe pane: This is the magnified screen image. It is overlaid by a grid in
- which each square represents one pixel. To look at the information for a pixel, click in its
- square. Its color and X,Y coordinates appear at the bottom of the pane.
- <p>
- The magenta crosshair in the pane corresponds to the positioning
- crosshair in the next pane. It only moves when you move the crosshair in the next pane.
- </p>
- <p>
- To zoom in or out on the image, use the <strong>Zoom</strong> slider at the bottom of
- the pane, or use your mouse's scroll wheel.
- </p>
- <p>
- When you select a pixel in the Loupe pane, you see the following information at the
- bottom of the pane:
- </p>
- <ul>
- <li>
- Pixel swatch: A rectangle filled with the same color as the pixel.
- </li>
- <li>
- HTML color code: The hexadecimal RGB code corresponding to the pixel color
- </li>
- <li>
- RGB color values: A list of the (R), green (G), and blue (B) color values of the
- pixel color. Each value is in the range 0-255.
- </li>
- <li>
- X and Y coordinates: The pixel's coordinates, in device-specific pixel units.
- The values are 0-based, with X=0 at the left of the screen and Y=0 at the top.
- </li>
- </ul>
- </li>
- <li>
- Pixel Perfect pane: This displays the currently visible screen as it would appear in the
- emulator.
- <p>
- You use the cyan crosshair to do coarse positioning. Drag the crosshair in the image,
- and the Loupe crosshair will move accordingly. You can also click on a point in the
- Pixel Perfect pane, and the crosshair will move to that point.
- </p>
- <p>
- The image corresponding to the View object selected in the View Object pane is
- outlined in a box that indicates the View object's position on the screen. For the
- selected object, the box is bold red. Sibling and parent View objects have a light
- red box. View objects that are neither parents nor siblings are in white.
- </p>
- <p>
- The layout box may have other rectangles either inside or outside it, each of which
- indicates part of the View. A purple or green rectangle indicates the View bounding box.
- A white or black box inside the layout box represents the <strong>padding</strong>, the
- defined distance between the View object's content and its bounding box. An outer white
- or black rectangle represents the <strong>margins</strong>, the distance between the
- View bounding box and adjacent View objects. The padding and margin boxes are white if
- the layout background is black, and vice versa.
- </p>
- <p>
- You can save the screen image being displayed in the Pixel Perfect pane as a PNG file.
- This produces a screenshot of the current screen. To do this, click
- <strong>Save as PNG</strong> at the top of the window. This displays a dialog,
- in which you can choose a directory and filename for the file.
- </p>
- </li>
-</ul>
-<p>
- The panes are not automatically refreshed when you change one of the View objects or go to
- another Activity. To refresh the Pixel Perfect pane and the Loupe pane, click
- <strong>Refresh Screenshot</strong> at the top of the window. This will change the panes
- to reflect the current screen image. You still may need to refresh the View Object pane;
- to do this, click <strong>Refresh Tree</strong> at the top of the window.
-</p>
-<p>
- To automatically refresh the panes while you are debugging, set
- <strong>Auto Refresh</strong> at the top of the window, and then set a refresh rate
- with the <strong>Refresh Rate</strong> slider at the bottom of the Loupe pane.
-</p>
-<h3 id="overlays">Working with Pixel Perfect overlays</h3>
-<p>
- You often construct a UI based on a design done as a bitmap image. The Pixel Perfect window
- helps you match up your View layout to a bitmap image by allowing you to load the bitmap as an
- <strong>overlay</strong> on the screen image.
-</p>
-<p>
- To use a bitmap image as an overlay:
-</p>
-<ul>
- <li>
- Start your application in a device or emulator and navigate to the Activity whose UI you
- want to work with.
- </li>
- <li>
- Start Hierarchy Viewer and navigate to the Pixel Perfect window.
- </li>
- <li>
- At the top of the window, click <strong>Load Overlay</strong>. A dialog opens, prompting
- for the image file to load. Load the image file.
- </li>
- <li>
- Pixel Perfect displays the overlay over the screen image in the Pixel Perfect pane. The
- lower left corner of the bitmap image (X=0, Y=<em>max value</em>) is anchored on the lower
- leftmost pixel (X=0, Y=<em>max screen</em>) of the screen.
- <p>
- By default, the overlay has a 50% transparency, which allows you to see the screen
- image underneath. You can adjust this with the <strong>Overlay:</strong> slider at the
- bottom of the Loupe pane.
- </p>
- <p>
- Also by default, the overlay is not displayed in the Loupe pane. To display it,
- set <strong>Show in Loupe</strong> at the top of the window.
- </p>
- </li>
-</ul>
-<p>
- The overlay is not saved as part of the screenshot when you save the screen image as a PNG
- file.
-</p>
-<p>
- A screenshot of the Pixel Perfect window appears in figure 4.
-</p>
-<img id="Fig4" src="{@docRoot}images/developing/hv_pixelperfect.png"
- alt=""
- height="600"/>
-<p class="img-caption"><strong>Figure 4.</strong> The Pixel Perfect window</p>
-
-
-<h2 id="lint">Using lint to Optimize Your UI</h2>
-<p>The Android <a href="{@docRoot}tools/help/lint.html">lint</a> tool lets you analyze the XML
-files that define your application's UI to find inefficiencies in the view hierarchy.</p>
-<p class="note"><strong>Note: </strong>The Android <code>layoutopt</code> tool has been replaced by the {@code lint} tool beginning in SDK Tools revision 16. The {@code lint} tool reports UI layout performance issues in a similar way as <code>layoutopt</code>, and detects additional problems.</p>
-<p>For more information about using {@code lint}, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a> and the <a href="{@docRoot}tools/help/lint.html">lint tools help</a>.</p>
+++ /dev/null
-page.title=Improving Your Code with lint
-parent.title=Debugging
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In This Document</h2>
-
- <ol>
- <li><a href="#overview">Overview</a></li>
- <li><a href="#studio">Running lint from Android Studio</a></li>
- <li><a href="#commandline">Running lint from the command-line</a></li>
- <li><a href="#config">Configuring lint</a>
- <ol>
- <LI><a href="#studio_config">Configuring Lint in Android Studio</a></LI>
- <LI><a href="#pref">Configuring the lint file</a></LI>
- <LI><a href="#src">Configuring lint checking in Java and XML source files</a></LI>
- </ol>
- </li>
- </ol>
- <h2>See Also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/lint.html">lint (reference)</a></li>
- <li><a href="{@docRoot}tools/degugging/annotations.html">Using Android Annotations</a></li>
- </ol>
- </div>
-</div>
-
-
-<p>
-In addition to testing that your Android application meets its functional requirements, it's
-important to ensure that your code has no structural problems. Poorly structured code can impact the
-reliability and efficiency of your Android apps and make your code harder to maintain. For example,
-if your XML resource files contain unused namespaces, this takes up space and incurs unnecessary
-processing. Other structural issues, such as use of deprecated elements or API calls that are not
-supported by the target API versions, might lead to code failing to run correctly.</p>
-
-<h2 id="overview">Overview</h2>
-<p>The Android SDK provides a code scanning tool called <a href="{@docRoot}tools/help/lint.html"><code>lint</code></a>
-that can help you to easily identify and correct problems with the structural quality of your code,
-without having to execute the app or write any test cases. Each problem detected by the tool is
-reported with a description message and a severity level, so that you can quickly prioritize the
-critical improvements that need to be made. You can also configure a problem's severity level to
-ignore issues that are not relevant for your project, or raise the severity level. The tool has a
-command-line interface, so you can easily integrate it into your automated testing process.</p>
-<p>The {@code lint} tool checks your Android project source files for potential bugs and
-optimization improvements for correctness, security, performance, usability, accessibility, and
-internationalization. You can run {@code lint} from the command-line or from Android Studio.</p>
-
-<p class="note"><strong>Note:</strong> In Android Studio, additional
-<a href="https://www.jetbrains.com/idea/help/inspection-basics.html?search=inspection" class="external-link"
-target="_blank">IntelliJ code inspections</a> run when your code is compiled in Android Studio to
-streamline code review.</p>
-
-<p>Figure 1 shows how the {@code lint} tool processes the application source files.</p>
-<img id="Fig1" src="{@docRoot}images/tools/lint.png" alt="">
-<p class="img-caption"><strong>Figure 1.</strong> Code scanning workflow with the {@code lint} tool</p>
-<dl>
-<dt><b>Application source files</b></dt>
-<dd>The source files consist of files that make up your Android project, including Java and XML
-files, icons, and ProGuard configuration files. </dd>
-<dt><b>The <code>lint.xml</code> file</b></dt>
-<dd>A configuration file that you can use to specify any {@code lint} checks that you want to
-exclude and to customize problem severity levels.</dd>
-<dt><b>The {@code lint} tool</b></dt>
-<dd>A static code scanning tool that you can run on your Android project from the command-line or
-Android Studio. The {@code lint} tool checks for structural code problems that could affect the
-quality and performance of your Android application. It is strongly recommended that you correct any
-errors that {@code lint} detects before publishing your application.</dd>
-<dt><b>Results of {@code lint} checking</b></dt>
-<dd>You can view the results from {@code lint} in the console or in the <strong>Event Log</strong>
-in Android Studio. Each issue is identified by the location in the source files where it occurred
-and a description of the issue.</dd>
-</dl>
-<p>The {@code lint} tool is automatically installed as part of the Android SDK Tools revision 16 or
-higher.</p>
-
-
-<h2 id="studio">Running lint in Android Studio</h2>
-<p>In Android Studio, the configured <code>lint</code> and
-IDE inspections run automatically whenever you build your app. The IDE inspections are
-configured along with the {@code lint} checks to run
-<a href="https://www.jetbrains.com/idea/help/inspection-basics.html?search=inspection" class="external-link"
-target="_blank">IntelliJ code inspections</a> to streamline code review.</p>
-
-<p class="note"><strong>Note:</strong> To view and modify inspection severity
-levels, use the <strong>File > Settings > Project Settings</strong> menu to open the
-<em>Inspection Configuration</em> page with a list of the supported inspections.</p>
-
-
-<p>With Android Studio, you can also run {@code lint} inspections for a specific build variant,
-or for all build variants from the <code>build.gradle</code> file. Add the
-<code>lintOptions</code> property to the <code>android</code> settings in the build file.
-This code snippet from a Gradle build file shows how to set the <code>quiet</code> option to
-<code>true</code> and the <code>abortOnError</code> option to <code>false</code>. </p>
-
-<pre>
-android {
- lintOptions {
- // set to true to turn off analysis progress reporting by lint
- quiet true
- // if true, stop the gradle build if errors are found
- abortOnError false
- // if true, only report errors
- ignoreWarnings true
- }
- ...
- }
-</pre>
-
-
-<p>To manually run inspections in Android Studio, from the application or right-click menu,
-choose <strong>Analyze > Inspect Code</strong>. The <em>Specify Inspections Scope</em> dialog
-appears so you can specify the desired inspection scope and profile.</p>
-
-
-
-
-<h2 id="commandline">Running lint from the Command-Line</h2>
-<p>
-To run {@code lint} against a list of files in a project directory:
-<pre>lint [flags] <project directory></pre>
-<p>For example, you can issue the following command to scan the files under the {@code myproject}
-directory and its subdirectories. The issue ID <code>MissingPrefix</code> tells {@code lint} to
-only scan for XML attributes that are missing the Android namespace prefix.</p>
-<pre>lint --check MissingPrefix myproject </pre>
-<p>To see the full list of flags and command-line arguments supported by the tool:</p>
-<pre>lint --help</pre>
-</p>
-
-<h3>Example lint output</h3>
-<p>The following example shows the console output when the {@code lint} command is run against a
-project called Earthquake. </p>
-<pre>
-$ lint Earthquake
-
-Scanning Earthquake: ...............................................................................................................................
-Scanning Earthquake (Phase 2): .......
-AndroidManifest.xml:23: Warning: <uses-sdk> tag appears after <application> tag [ManifestOrder]
- <uses-sdk android:minSdkVersion="7" />
- ^
-AndroidManifest.xml:23: Warning: <uses-sdk> tag should specify a target API level (the highest verified version; when running on later versions, compatibility behaviors may be enabled) with android:targetSdkVersion="?" [UsesMinSdkAttributes]
- <uses-sdk android:minSdkVersion="7" />
- ^
-res/layout/preferences.xml: Warning: The resource R.layout.preferences appears to be unused [UnusedResources]
-res: Warning: Missing density variation folders in res: drawable-xhdpi [IconMissingDensityFolder]
-0 errors, 4 warnings
-</pre>
-<p>The output above lists four warnings and no errors in this project. Three warnings
-({@code ManifestOrder}, {@code UsesMinSdkAttributes}, and {@code UnusedResources}) were found in
-the project's <code>AndroidManifest.xml</code> file. The remaining warning
-({@code IconMissingDensityFolder}) was found in the <code>Preferences.xml</code> layout file.</p>
-
-<h2 id="config">Configuring lint</h2>
-<p>By default, when you run a {@code lint} scan, the tool checks for all issues that are supported
-by {@code lint}. You can also restrict the issues for {@code lint} to check and assign the severity
-level for those issues. For example, you can disable {@code lint} checking for specific issues that
-are not relevant to your project and configure {@code lint} to report non-critical issues at a lower
-severity level.</p>
-<p>You can configure {@code lint} checking at different levels:</p>
-<ul>
-<LI>Globally, for the entire project</LI>
-<li>Per project module</li>
-<li>Per production module</li>
-<li>Per test module</li>
-<li>Per open files</li>
-<li>Per class hierarchy</li>
-<li>Per Version Control System (VCS) scopes</li>
-</ul>
-
-<h3 id="studio_config">Configuring Lint in Android Studio</h3>
-
-<p>The built-in Lint tool checks your code while you're using
-Android Studio. You can view warnings and errors in two ways: </p>
-<ul>
-<li>As pop-up text in the Code Editor. When Lint finds a problem, it highlights
-the problematic code in yellow, or underlines the code in red for more serious
-issues.</li>
-<li>In the Lint <em>Inspection Results</em> window after you select
-<strong>Analyze</strong> > <strong>Inspect Code</strong>.</li>
-</ul>
-
-
-
-<p>To set default Lint checks:</p>
-<ol>
-<li>In Android Studio, open your project.
-</li>
-<li>Select <strong>File</strong> > <strong>Other Settings</strong> >
- <strong>Default Settings</strong>.</li>
-<li>In the <em>Default Preferences</em> dialog, select <strong>Editor</strong>
-> <strong>Inspections</strong>. </li>
-<li>In the <strong>Profile</strong> field, select <strong>Default</strong> or
- <strong>Project Default</strong> to set the
- <a href="https://www.jetbrains.com/help/idea/2016.1/specify-inspection-scope-dialog.html?origin=old_help"
- class="external-link">scope</a> for Android Studio or just for this project,
- respectively. </li>
-<li>Expand a category and change the Lint settings as needed.</li>
-<p>You can select individual checks, or entire categories.</p>
-
-<li>Click <strong>OK</strong>.</li>
-</ol>
-
-
-
-<p>To produce a list of Lint checks displayed in the <em>Inspection Results</em>
-window:</p>
-<ol>
-<li>In Android Studio, open your project
- and select a portion of your project that you want to test.</li>
-<li>Select <strong>Analyze</strong> > <strong>Inspect Code</strong>.</li>
-<li>In the <em>Specify Inspection Scope </em>dialog, select the inspection
-<a href="https://www.jetbrains.com/help/idea/2016.1/specify-inspection-scope-dialog.html?origin=old_help"
- class="external-link">scope</a> and profile. </li>
-
-<p>The scope specifies the files you want to analyze, and the profile specifies
-the Lint checks you’d like to perform.</p>
-<li>If you want to change the Lint settings, click <strong>…</strong>. In the
-<em>Inspections</em> dialog, optionally click <strong>Manage</strong> to define
-a new profile, specify the Lint settings you want, and then click
-<strong>OK</strong>.</li>
-<p>In the <em>Inspections</em> dialog, you can search for a string
-to find Lint checks. Note that changing Lint settings for a
-profile in the <em>Inspections</em> dialog doesn’t change the default settings,
-as described in the previous procedure. It does change the settings for profiles
-displayed in the <em>Inspections</em> dialog, however.</p>
-<li>Click <strong>OK</strong>.</li>
-<p>The results appear in the <em>Inspection Results</em> window, organized by
-category.</p>
-
-</ol>
-
-
-
-<h3 id="pref">Configuring the lint file</h3>
-<p>You can specify your {@code lint} checking preferences in the <code>lint.xml</code> file. If you
-are creating this file manually, place it in the root directory of your Android project. If you are
-configuring {@code lint} preferences in Android Studio, the <code>lint.xml</code> file is
-automatically created and added to your Android project for you.</p>
-<p>The <code>lint.xml</code> file consists of an enclosing <code><lint></code> parent tag that
-contains one or more children <code><issue></code> elements. Each <code><issue></code>
-is identified by a unique <code>id</code> attribute value, which is defined by {@code lint}.</p>
-<pre>
-<?xml version="1.0" encoding="UTF-8"?>
- <lint>
- <!-- list of issues to configure -->
-</lint>
-</pre>
-<p>By setting the severity attribute value in the <code><issue></code> tag, you can disable
-{@code lint} checking for an issue or change the severity level for an issue. </p>
-<p class="note"><strong>Tip: </strong>To see the full list of issues supported by the {@code lint}
-tool and their corresponding issue IDs, run the <code>lint --list</code> command.</p>
-
-<h4>Sample lint.xml file</h4>
-<p>The following example shows the contents of a <code>lint.xml</code> file.</p>
-<pre>
-<?xml version="1.0" encoding="UTF-8"?>
-<lint>
- <!-- Disable the given check in this project -->
- <issue id="IconMissingDensityFolder" severity="ignore" />
-
- <!-- Ignore the ObsoleteLayoutParam issue in the specified files -->
- <issue id="ObsoleteLayoutParam">
- <ignore path="res/layout/activation.xml" />
- <ignore path="res/layout-xlarge/activation.xml" />
- </issue>
-
- <!-- Ignore the UselessLeaf issue in the specified file -->
- <issue id="UselessLeaf">
- <ignore path="res/layout/main.xml" />
- </issue>
-
- <!-- Change the severity of hardcoded strings to "error" -->
- <issue id="HardcodedText" severity="error" />
-</lint>
-</pre>
-
-<h3 id="src">Configuring lint checking in Java and XML source files</h3>
-<p>You can disable {@code lint} checking from your Java and XML source files.</p>
-
-<p class="note"><strong>Tip: </strong>If you are using Android Studio, you can use the
-<strong>File > Settings > Project Settings > Inspections</strong> feature to manage the
-{@code lint} checking to your Java or XML source files.
-</p>
-
-<h4>Configuring lint checking in Java</h4>
-<p>To disable {@code lint} checking specifically for a Java class or method in your Android project,
-add the <code>@SuppressLint</code> annotation to that Java code. </p>
-<p>The following example shows how you can turn off {@code lint} checking for the {@code NewApi}
-issue in the <code>onCreate</code> method. The {@code lint} tool continues to check for the
-{@code NewApi} issue in other methods of this class.</p>
-<pre>
-@SuppressLint("NewApi")
-@Override
-public void onCreate(Bundle savedInstanceState) {
- super.onCreate(savedInstanceState);
- setContentView(R.layout.main);
-</pre>
-<p>The following example shows how to turn off {@code lint} checking for the {@code ParserError}
-issue in the <code>FeedProvider</code> class:</p>
-<pre>
-@SuppressLint("ParserError")
-public class FeedProvider extends ContentProvider {
-</pre>
-<p>To suppress checking for all {@code lint} issues in the Java file, use the {@code all} keyword,
-like this:</p>
-<pre>
-@SuppressLint("all")
-</pre>
-
-<h4>Configuring lint checking in XML</h4>
-<p>You can use the <code>tools:ignore</code> attribute to disable {@code lint} checking for specific
-sections of your XML files. In order for this attribute to be recognized by the {@code lint} tool,
-the following namespace value must be included in your XML file:</p>
-<pre>
-namespace xmlns:tools="http://schemas.android.com/tools"
-</pre>
-<p>The following example shows how you can turn off {@code lint} checking for the
-{@code UnusedResources} issue for the <code><LinearLayout></code> element of an XML layout
-file. The <code>ignore</code> attribute is inherited by the children elements of the parent element
-in which the attribute is declared. In this example, the {@code lint} check is also disabled for the
-child <code><TextView></code> element. </p>
-<pre>
-<LinearLayout
- xmlns:android="http://schemas.android.com/apk/res/android"
- xmlns:tools="http://schemas.android.com/tools"
- tools:ignore="UnusedResources" >
-
- <TextView
- android:text="@string/auto_update_prompt" />
-</LinearLayout>
-</pre>
-<p>To disable more than one issue, list the issues to disable in a comma-separated string. For
-example:</p>
-<pre>
-tools:ignore="NewApi,StringFormatInvalid"
-</pre>
-<p>To suppress checking for all {@code lint} issues in the XML element, use the {@code all} keyword,
-like this:</p>
-<pre>
-tools:ignore="all"
-</pre>
+++ /dev/null
-page.title=Debugging
-@jd:body
-
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <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>
- </div>
-
- <p>The Android SDK provides most of the tools that you need to debug your applications. You need
- a JDWP-compliant debugger if you want to be able to do things such as step through code,
- view variable values, and pause execution of an application. If you are using Android Studio, a
- JDWP-compliant debugger is already included and there is no setup required. If you are using
- another IDE, you can use the debugger that comes with it and attach the debugger to a special
- port so it can communicate with the application VMs on your devices. The main components that
- comprise a typical Android debugging environment are:</p>
-
- <dl>
- <dt><a href="{@docRoot}tools/help/adb.html"><strong>adb</strong></a></dt>
-
- <dd><code>adb</code> acts as a middleman between a device and your development system. It
- provides various
- device management capabilities, including moving and syncing files to the emulator, running a
- UNIX shell on the device or emulator, and providing a general means to communicate with
- connected emulators and devices.</dd>
-
- <dt><a href="{@docRoot}tools/debugging/ddms.html"><strong>Dalvik Debug Monitor
- Server</strong></a></dt>
-
- <dd>DDMS is a graphical program that communicates with your devices through <code>adb</code>. DDMS can
- capture screenshots, gather thread and stack information, spoof incoming calls and SMS
- messages, and has many other features.</dd>
-
- <dt><strong><a href="{@docRoot}tools/device.html">Device</a> or
- <a href="{@docRoot}tools/devices/index.html">Android Virtual Device</a></strong></dt>
-
- <dd>Your application must run in a device or in an AVD so that it can be debugged. An
- <code>adb</code> device daemon runs on the device or emulator and provides a means for the
- <code>adb</code> host daemon to communicate with the device or emulator.</dd>
-
- <dt><strong>JDWP debugger</strong></dt>
-
- <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
- 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,
- or you can use a command line debugger such as <a href="http://download.oracle.com/javase/6/docs/technotes/tools/">
- <code>jdb</code></a>.</dd>
- </dl>
-
- <h2>Debugging Environment</h2>
-
- <p>Figure 1 shows how the various debugging tools work together in a typical
- debugging environment.</p>
- <img src="{@docRoot}images/debugging.png"
- alt="Debugging workflow" />
- <p class="img-caption><strong>Figure 1. </strong> Debugging Workflow</p>
-
- <p>On your emulator or device, each application runs in its own instance of a Dalvik VM. The
- <code>adb</code> device daemon allows communication with the VMs from an outside party.</p>
-
- <p>On your development machine, the <code>adb</code> host daemon communicates with the
- <code>adb</code> device daemon and allows tools such as DDMS to communicate with the device or emulator.
- The <code>adb</code> host daemon also allows you to access shell commands on the device as well as
- providing capabilities such as application installation and file transferring.</p>
-
- <p>Each application VM on the device or emulator exposes a debugging port that you can attach to
- via DDMS. DDMS can forward any of these ports to a static debugging port (typically port 8700) by
- selecting the application that you want to debug in the DDMS user interface. A JDWP debugger can
- attach to this static debugging port and debug all the applications that are running on the
- device or emulator without having to attach to multiple ports.</p>
-
- <p>If you are using Android Studio, much of these interconnections are hidden from you. DDMS,
- <code>adb</code>, and a
- JDWP debugger are all setup for you and you can access them through the Debug and DDMS view. If
- you are developing with another IDE environment, you may have to invoke these tools manually.</p>
-
- <h2 id="addltools">Additional Debugging Tools</h2>
-
- <p>In addition to the main debugging tools, the Android SDK provides additional tools to help you
- debug and profile your applications:</p>
-
- <dl>
- <dt><strong><a href="{@docRoot}tools/debugging/debugging-ui.html">Heirarchy Viewer
- and layoutopt</a></strong></dt>
-
- <dd>Graphical programs that let you debug and profile user interfaces.</dd>
-
- <dt><strong><a href=
- "{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a></strong></dt>
-
- <dd>A graphical viewer that displays trace file data for method calls and times saved by your
- application, which can help you profile the performance of your application.</dd>
-
- <dt><strong><a href="{@docRoot}tools/debugging/debugging-devtools.html">Dev Tools
- Android application</a></strong></dt>
-
- <dd>The Dev Tools application included in the emulator system image exposes several settings
- 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
-applications:</p>
-
-<dl>
-<dt><strong>Dump the stack trace</strong></dt>
-<dd>To obtain a stack dump from emulator, you can log
-in with <code>adb shell</code>, use <code>ps</code> to find the process you
-want, and then <code>kill -3</code>. The stack trace appears in the log file.
-</dd>
-
-<dt><strong>Display useful info on the emulator screen</strong></dt>
-<dd>The device can display useful information such as CPU usage or highlights
-around redrawn areas. Turn these features on and off in the developer settings
-window as described in <a href="{@docRoot}tools/debugging/debugging-devtools.html">
-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
-<a href="{@docRoot}tools/help/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.
-From the <strong>Device</strong> menu, select <strong>Dump
-radio state</strong>.</dd>
-
-<dt><strong>Log trace data</strong></dt>
-<dd>You can log method calls and other tracing data in an activity by calling
-{@link android.os.Debug#startMethodTracing(String) startMethodTracing()}. See <a
-href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with Traceview and
-dmtracedump</a> for details. </dd>
-
-<dt><strong>Log radio data</strong></dt>
-<dd>By default, radio information is not logged to the system (it is a lot of
-data). However, you can enable radio logging using the following commands:
-
-<pre class="no-pretty-print">
-adb shell
-logcat -b radio
-</pre>
-</dd>
-
-<dt><strong>Capture screenshots</strong></dt>
-<dd>The Dalvik Debug Monitor Server (DDMS) can capture screenshots from the emulator. Select
-<strong>Device > Screen capture</strong>.</dd>
-
-<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>
-
-
-
-
-
-
-
-
+++ /dev/null
-page.title=Analyzing UI Performance with Systrace
-page.tags=systrace,speed
-parent.title=Debugging
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#overview">Overview</a></li>
- <li><a href="#generate">Generating a Trace</a></li>
- <li><a href="#analysis">Analyzing a Trace</a>
- <ol>
- <li><a href="#frames">Inspecting Frames</a></li>
- <li><a href="#alerts">Investigating Alerts</a></li>
- </ol>
- </li>
- <li><a href="#app-trace">Tracing Application Code</a></li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/systrace.html">Systrace</a></li>
- </ol>
- </div>
-</div>
-
-<p>While developing your application, you should check that user interactions are buttery smooth,
-running at a consistent 60 frames per second. If something goes wrong, and a frame gets dropped, the
-first step in fixing the problem is understanding what the system is doing.</p>
-
-<p>The Systrace tool allows you to collect and inspect timing information across an entire Android
-device, which is called a <em>trace</em>. It shows where time and CPU cycles are being spent,
-displaying what each thread and process is doing at any given time. It also inpects the captured
-tracing information to highlight problems that it observes, from list item recycling to rendering
-content, and provide recommendations about how to fix them. This document explains how to navigate
-the trace files produced by the tool, and use them to analyze the performance of an application's
-user interface (UI).</p>
-
-<h2 id="overview">Overview</h2>
-
-<p>Systrace helps you analyze how the execution of your application fits into the many running
-systems on an Android device. It puts together system and application thread execution on a common
-timeline. In order to analyze your app with Systrace, you first collect a trace log of your app, and
-the system activity. The generated trace allows you to view highly detailed, interactive reports
-showing everything happening in the system for the traced duration.</p>
-
-<img src="{@docRoot}images/systrace/overview.png" alt="Systrace example overview" id="figure1" />
-<p class="img-caption">
- <strong>Figure 1.</strong> An example Systrace, showing 5 seconds of scrolling an app when it
- is not performing well.
-</p>
-
-<p>Figure 1. shows a trace captured while scrolling an app that is not rendering smoothly. By
-default, a zoomed out view of the traced duration is shown. The horizontal axis is time, and trace
-events are grouped by process, and then by thread on the vertical axis.</p>
-
-<p>The groupings are in the order Kernel, SurfaceFlinger (the android compositor process), followed
-by apps, each labeled by package name. Each app process contains all of the tracing signals from
-each thread it contains, including a hierarchy of high level tracing events based on the enabled
-tracing categories.</p>
-
-
-<h2 id="generate">Generating a Trace</h2>
-
-<p>In order to create a trace of your application, you must perform a few setup steps. First, you
-must have a device running Android 4.1 (API 16) or higher. Set up the device
-for <a href="{@docRoot}tools/device.html#setting-up">debugging</a>, connect it to your development
-system, and install your application. Some types of trace information, specifically disk activity
-and kernel work queues, require that you have root access to the device. However, most Systrace log
-data only requires that the device be enabled for developer debugging.</p>
-
-<p>Systrace traces can be run either from
-a <a href="{@docRoot}tools/help/systrace.html#options">command line</a> or from a
-<a href="{@docRoot}tools/help/systrace.html#gui">graphical user interface</a>. This guide focuses on
-using the command line options.</p>
-
-<h3 id="running-4.3">Tracing on Android 4.3 and higher</h3>
-
-<p>To run a trace on Android 4.3 and higher devices:</p>
-
-<ol>
- <li>Make sure the device is connected through a USB cable and is
- <a href="{@docRoot}tools/device.html#setting-up">enabled for debugging</a>.</li>
- <li>Run the trace with the options you want, for example:
-<pre>
-$ cd android-sdk/platform-tools/systrace
-$ python systrace.py --time=10 -o mynewtrace.html sched gfx view wm
-</pre>
- </li>
- <li>On the device, execute any user actions you want be included in the trace.</li>
-</ol>
-
-<p>For more information on the available options for running Systrace, see the
-<a href="#options-4.3">Systrace</a> help page.</p>
-
-
-<h3 id="running-4.2">Tracing on Android 4.2 and lower</h3>
-
-<p>To use Systrace effectively with devices running Android 4.2 and lower,
- you must configure the types of processes you want to trace before running a trace.
- The tool can gather the following types of process information:</p>
-
-<ul>
- <li>General system processes such as graphics, audio and input processes (selected using trace
- <a href="#tags">category tags</a>).</li>
- <li>Low level system information such as CPU, kernel and disk activity (selected using
- <a href="#options">options</a>).</li>
-</ul>
-
-<p>To set trace tags for Systrace using the command-line:</p>
-
-<ol>
- <li>Use the {@code --set-tags} option:
-<pre>
-$ cd android-sdk/platform-tools/systrace
-$ python systrace.py --set-tags=gfx,view,wm
-</pre>
- </li>
- <li>Stop and restart the {@code adb} shell to enable tracing of these processes.
-<pre>
-$ adb shell stop
-$ adb shell start
-</pre></li>
-</ol>
-
-<p>To set trace tags for Systrace using the device user interface:</p>
-
-<ol>
- <li>On the device connected for tracing, navigate to: <strong>Settings >
- Developer options > Monitoring > Enable traces</strong>.</li>
- <li>Select the categories of processes to be traced and click <strong>OK</strong>.</li>
-</ol>
-
-<p class="note">
- <strong>Note:</strong> The {@code adb} shell does not have to be stopped and restarted when
- selecting trace tags using this method.
-</p>
-
-<p>After you have configured the category tags for your trace, you can start collecting
- information for analysis.</p>
-
-<p>To run a trace using the current trace tag settings:</p>
-
-<ol>
- <li>Make sure the device is connected through a USB cable and is
- <a href="{@docRoot}tools/device.html#setting-up">enabled for debugging</a>.</li>
- <li>Run the trace with the low-level system trace options and limits you want, for example:
-<pre>
-$ python systrace.py --cpu-freq --cpu-load --time=10 -o mytracefile.html
-</pre>
- </li>
- <li>On the device, execute any user actions you want be included in the trace.</li>
-</ol>
-
-<p>For more information on the available options for running Systrace, see the
-<a href="#options-pre-4.3">Systrace</a> help page.</p>
-
-
-<h2 id="analysis">Analyzing a Trace</h2>
-
-<p>After you have generated a trace, open the output html file using a web browser. This section
-explains how to analyze and interpret the information that the tool produces to find and fix UI
-performance problems.</p>
-
-<h3 id="frames">Inspecting Frames</h3>
-
-<p>Each app that is rendering frames shows a row of frame circles, which are typically colored
-green. Circles that are colored yellow or red, exceeding the 16.6 millisecond run time limit
-required to maintain a stable 60 frames per second. Zoom in using the 'w' key to see the frames of
-your application, and look for long-running frames getting in the way of smoothness.</p>
-
-<p class="note">
- <strong>Note:</strong> Hit the '?' key, or the button in the top right for help navigating the
- trace.
-</p>
-
-<img src="{@docRoot}images/systrace/frame-unselected.png" alt="Zoomed in view of a frame" id="figure2" />
-<p class="img-caption">
- <strong>Figure 2.</strong> Systrace display after zooming in on a long-running frame.
-</p>
-
-<p>Clicking on one such frame highlights it, focusing only on the work done by the system for that
-frame. On devices running Android 5.0 (API level 21) or higher, this work is split between the UI
-Thread and RenderThread. On prior versions, all work in creating a frame is done on the UI
-Thread.</p>
-
-<p>Click on individual components of the frame to see how long they took to run. Some events, such
-as <em>performTraversals</em>, describe what the system is doing in that method when you select
-it. Selecting a frame displays any alerts present in that frame.</p>
-
-<h3 id="alerts">Investigating Alerts</h3>
-
-<p>Systrace does automatic analysis of the events in the trace, and highlights many performance
-problems as alerts, suggesting what to do next.</p>
-
-<img src="{@docRoot}images/systrace/frame-selected.png" alt="Problematic frame selected" id="figure3" />
-<p class="img-caption">
- <strong>Figure 3.</strong> Selecting the problematic frame, an alert is shown identifying a problem.
-</p>
-
-<p>After you select a slow frame such as the one shown in Figure 3, an alert may be displayed. In
-the case above, it calls out that the primary problem with the frame is too much work being done
-inside {@link android.widget.ListView} recycling and rebinding. There are links to the relevant
-events in the trace, which can be followed to explain more about what the system is doing during
-this time.</p>
-
-<p>If you see too much work being done on the UI thread, as in this case with this
-{@link android.widget.ListView} work, you can
-use <a href="{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a>, the app code profiling
-tool, to investigate exactly what is taking so much time.</p>
-
-<p>Note that you can also find about every alert in the trace by clicking the <em>Alerts</em> tab to
-the far right of the window. Doing so expands the Alerts panel, where you can see every alert that
-the tool discovered in your trace, along with an occurrence count.</p>
-
-<img src="{@docRoot}images/systrace/frame-selected-alert-tab.png" alt="Alert tab shown" id="figure4" />
-<p class="img-caption">
- <strong>Figure 4.</strong> Clicking the Alert button to the right reveals the alert tab.
-</p>
-
-<p>The Alerts panel helps you see which problems occur in the trace, and how often they contribute
-to jank. Think of the alerts panel as a list of bugs to be fixed, often a tiny change or improvement
-in one area can eliminate an entire class of alerts from your application!</p>
-
-
-<h2 id="app-trace">Tracing Application Code</h2>
-
-<p>The tracing signals defined by the framework do not have visibility into everything your
-application is doing, so you may want to add your own. In Android 4.3 (API level 18) and higher, you
-can use the methods of the {@link android.os.Trace} class to add signals to your code. This
-technique can help you see what work your application's threads are doing at any given time. Tracing
-begin and end events do add overhead while a trace is being captured, a few microseconds each, but
-sprinkling in a few per frame, or per worker thread task can go a long way to adding context to a
-trace of your app.</p>
-
-<p>The following code example shows how to use the {@link android.os.Trace} class to track
-execution of an application method, including two nested code blocks within that method.</p>
-
-<pre>
-public void ProcessPeople() {
- Trace.beginSection("ProcessPeople");
- try {
- Trace.beginSection("Processing Jane");
- try {
- // code for Jane task...
- } finally {
- Trace.endSection(); // ends "Processing Jane"
- }
-
- Trace.beginSection("Processing John");
- try {
- // code for John task...
- } finally {
- Trace.endSection(); // ends "Processing John"
- }
- } finally {
- Trace.endSection(); // ends "ProcessPeople"
- }
-}
-</pre>
-
-<!-- todo: move these two Notes to the android.os.Trace class -->
-<p class="note">
- <strong>Note:</strong> When you nest trace calls within each other, the
- {@link android.os.Trace#endSection} method ends the most recently called
- {@link android.os.Trace#beginSection} method. This means that a trace started within another
- trace cannot extend beyond the end of the enclosing trace, so make sure your beginning and
- ending method calls are properly matched to measure your applications processing.
-</p>
-
-<p class="note">
- <strong>Note:</strong> Traces must begin and end on the same thread. Do not call
- {@link android.os.Trace#beginSection} on one thread of execution and then attempt to end the
- trace with a call to {@link android.os.Trace#endSection} on another thread.
-</p>
-
-<p>When using application-level tracing with Systrace, you must specify the package name of your
-application in the user interface or specify the {@code -a} or {@code --app=} options on the
-command line. For more information, see the
-<a href="{@docRoot}tools/help/systrace.html">Systrace usage guide</a>.</p>
-
-<p>You should enable app level tracing when profiling your app, even if you have not added signals
-yourself. Library code can include very useful tracing signals when you enable application-level
-tracing. The {@link android.support.v7.widget.RecyclerView} class is a great example of this,
-providing information about several important stages of work it executes.</p>
-
+++ /dev/null
-page.title=Using Hardware Devices
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#device-developer-options">Enabling On-device Developer Options</a></li>
- <li><a href="#setting-up">Setting up a Device for Development</a>
- <ol>
- <li><a href="#VendorIds">USB Vendor IDs</a></li>
- </ol>
- </li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/win-usb.html">Google USB Driver</a></li>
- <li><a href="{@docRoot}tools/extras/oem-usb.html">OEM USB Drivers</a></li>
- </ol>
-</div>
-</div>
-
-<p>When building a mobile application, it's important that you always test your application on a
-real device before releasing it to users. This page describes how to set up your development
-environment and Android-powered device for testing and debugging on the device.</p>
-
-<p>You can use any Android-powered device as an environment for running,
-debugging, and testing your applications. The tools included in the SDK make it easy to install and
-run your application on the device each time you compile. You can install your application on the
-device directly from Android Studio or from the command line with ADB. If
-you don't yet have a device, check with the service providers in your area to determine which
-Android-powered devices are available.</p>
-
-<p>If you want a SIM-unlocked phone, then you might consider a Nexus phone. To purchase a
-Nexus phone, visit the <a href="https://play.google.com/store/devices">Google Play</a> store.</p>
-
-<p class="note"><strong>Note:</strong> When developing on a device, keep in mind that you should
-still use the <a
-href="{@docRoot}tools/devices/emulator.html">Android emulator</a> to test your
-application
-on configurations that are not equivalent to those of your real device. Although the emulator
-does not allow you to test every device feature (such as the accelerometer), it does
-allow you to verify that your application functions properly on different versions of the Android
-platform, in different screen sizes and orientations, and more.</p>
-
-
-<h2 id="developer-device-options" style="margin-bottom: 0px;">Enabling On-device Developer Options</h2>
-
-<img src="/images/tools/dev-options-inmilk.png" alt="" style="float:right;margin-left:30px">
-
-<p>Android-powered devices have a host of developer options that you can
-access on the phone, which let you:</p>
-<ul>
- <li>Enable debugging over USB.</li>
- <li>Quickly capture bug reports onto the device.</li>
- <li>Show CPU usage on screen.</li>
- <li>Draw debugging information on screen such as layout bounds,
- updates on GPU views and hardware layers, and other information.</li>
- <li>Plus many more options to simulate app stresses or enable debugging options.</li>
-</ul>
-<p>To access these settings, open the <em>Developer options</em> in the
-system Settings. On Android 4.2 and higher, the <strong>Developer options</strong> screen is
-hidden by default. To make it visible, go to
-<b>Settings > About phone</b> and tap <b>Build number</b> seven times. Return to the previous
-screen to find <strong>Developer options</strong> at the bottom.</p>
-
-
-
-
-<h2 id="setting-up">Setting up a Device for Development</h2>
-
-<p>With an Android-powered device, you can develop and debug your Android applications just as you
-would on the emulator. Before you can start, there are just a few things to do:</p>
-
-<ol>
- <li>Verify that your application is "debuggable" in your manifest or <em>build.gradle</em> file.
- <p>In the build file, make sure the <em>debuggable</em> property in the <em>debug</em> build
- type is set to true. The build type property overrides the manifest setting. </p>
-<pre>
-android {
- buildTypes {
- debug {
- debuggable true
- }
-</pre>
-
- <p>In the <code>AndroidManifest.xml</code> file, add <code>android:debuggable="true"</code> to
-the <code><application></code> element.</p>
- <p class="note"><strong>Note:</strong> If you manually enable debugging in the manifest
- file, be sure to disable it in your release build (your published application
-should usually <em>not</em> be debuggable).</p></li>
- <li>Enable <strong>USB debugging</strong> on your device by going to
- <strong>Settings > Developer options</strong>.
- <p class="note"><strong>Note:</strong> On Android 4.2 and newer, <strong>Developer
- options</strong> is hidden by default. To make it available, go
- to <strong>Settings > About phone</strong> and tap <strong>Build number</strong>
- seven times. Return to the previous screen to find <strong>Developer options</strong>.</p>
- </li>
- <li>Set up your system to detect your device.
- <ul>
- <li>If you're developing on Windows, you need to install a USB driver for adb. For an
-installation guide and links to OEM drivers, see the <a href="{@docRoot}tools/extras/oem-usb.html">OEM USB
-Drivers</a> document.</li>
- <li>If you're developing on Mac OS X, it just works. Skip this step.</li>
- <li>If you're developing on Ubuntu Linux, you need to add a
-<code>udev</code> rules file that contains a USB configuration for each type of device
-you want to use for development. In the rules file, each device manufacturer
-is identified by a unique vendor ID, as specified by the
-<code>ATTR{idVendor}</code> property. For a list of vendor IDs, see <a
-href="#VendorIds">USB Vendor IDs</a>, below. To set up device detection on
-Ubuntu Linux:
-
- <ol type="a">
- <li>Log in as root and create this file:
- <code>/etc/udev/rules.d/51-android.rules</code></span>.
- <p>Use this format to add each vendor to the file:<br/>
- <code>SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"</code>
- <br /><br />
-
- In this example, the vendor ID is for HTC. The <code>MODE</code>
-assignment specifies read/write permissions, and <code>GROUP</code> defines
-which Unix group owns the device node. </p>
-
- <p class="note"><strong>Note:</strong> The rule syntax
-may vary slightly depending on your environment. Consult the <code>udev</code>
-documentation for your system as needed. For an overview of rule syntax, see
-this guide to <a
-href="http://www.reactivated.net/writing_udev_rules.html">writing udev
-rules</a>.</p>
- </li>
- <li>Now execute:<br/>
- <code>chmod a+r /etc/udev/rules.d/51-android.rules</code>
- </li>
- </ol>
- </li>
- </ul>
- </li>
-</ol>
-
-
-<p class="note"><strong>Note:</strong> When you connect a device running Android 4.2.2 or higher
-to your computer, the system shows a dialog asking whether to accept an RSA key that allows
-debugging through this computer. This security mechanism protects user devices because it ensures
-that USB debugging and other adb commands cannot be executed unless you're able to unlock the
-device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with
-SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or
-higher.</p>
-
-
-<p>When plugged in over USB, you can verify that your device is connected by executing <code>adb
-devices</code> from your SDK {@code platform-tools/} directory. If connected,
-you'll see the device name listed as a "device."</p>
-
-<p>If using Android Studio, run or debug your application as usual. You will be
-presented with a <b>Device Chooser</b> dialog that lists the available
-emulator(s) and connected device(s). Select the device upon which you want to
-install and run the application.</p>
-
-<p>If using the <a href="{@docRoot}tools/help/adb.html">Android
-Debug Bridge</a> (adb), you can issue commands with the <code>-d</code> flag to
-target your connected device.</p>
-
-<h3 id="VendorIds">USB Vendor IDs</h3>
-
-<p>This table provides a reference to the vendor IDs needed in order to add USB
-device support on Linux. The USB Vendor ID is the value given to the
-<code>ATTR{idVendor}</code> property in the rules file, as described
-above.</p>
-
-<table>
- <tr>
- <th>Company</th><th>USB Vendor ID</th></tr>
- <tr>
- <td>Acer</td>
- <td><code>0502</code></td>
- </tr>
- <tr>
- <td>ASUS</td>
- <td><code>0b05</code></td>
- </tr>
- <tr>
- <td>Dell</td>
- <td><code>413c</code></td>
- </tr>
- <tr>
- <td>Foxconn</td>
- <td><code>0489</code></td>
- </tr>
- <tr>
- <td>Fujitsu</td>
- <td><code>04c5</code></td>
- </tr>
- <tr>
- <td>Fujitsu Toshiba</td>
- <td><code>04c5</code></td>
- </tr>
- <tr>
- <td>Garmin-Asus</td>
- <td><code>091e</code></td>
- </tr>
- <tr>
- <td>Google</td>
- <td><code>18d1</code></td>
- </tr>
- <tr>
- <td>Haier</td>
- <td><code>201E</code></td>
- </tr>
- <tr>
- <td>Hisense</td>
- <td><code>109b</code></td>
- </tr>
- <tr>
- <td>HP</td>
- <td><code>03f0</code></td>
- </tr>
- <tr>
- <td>HTC</td>
- <td><code>0bb4</code></td>
- </tr>
- <tr>
- <td>Huawei</td>
- <td><code>12d1</code></td>
- </tr>
- <tr>
- <td>Intel</td>
- <td><code>8087</code></td>
- </tr>
- <tr>
- <td>K-Touch</td>
- <td><code>24e3</code></td>
- </tr>
- <tr>
- <td>KT Tech</td>
- <td><code>2116</code></td>
- </tr>
- <tr>
- <td>Kyocera</td>
- <td><code>0482</code></td>
- </tr>
- <tr>
- <td>Lenovo</td>
- <td><code>17ef</code></td>
- </tr>
- <tr>
- <td>LG</td>
- <td><code>1004</code></td>
- </tr>
- <tr>
- <td>Motorola</td>
- <td><code>22b8</code></td>
- </tr>
- <tr>
- <td>MTK</td>
- <td><code>0e8d</code></td>
- </tr>
- <tr>
- <td>NEC</td>
- <td><code>0409</code></td>
- </tr>
- <tr>
- <td>Nook</td>
- <td><code>2080</code></td>
- </tr>
- <tr>
- <td>Nvidia</td>
- <td><code>0955</code></td>
- </tr>
- <tr>
- <td>OTGV</td>
- <td><code>2257</code></td>
- </tr>
- <tr>
- <td>Pantech</td>
- <td><code>10a9</code></td>
- </tr>
- <tr>
- <td>Pegatron</td>
- <td><code>1d4d</code></td>
- </tr>
- <tr>
- <td>Philips</td>
- <td><code>0471</code></td>
- </tr>
- <tr>
- <td>PMC-Sierra</td>
- <td><code>04da</code></td>
- </tr>
- <tr>
- <td>Qualcomm</td>
- <td><code>05c6</code></td>
- </tr>
- <tr>
- <td>SK Telesys</td>
- <td><code>1f53</code></td>
- </tr>
- <tr>
- <td>Samsung</td>
- <td><code>04e8</code></td>
- </tr>
- <tr>
- <td>Sharp</td>
- <td><code>04dd</code></td>
- </tr>
- <tr>
- <td>Sony</td>
- <td><code>054c</code></td>
- </tr>
- <tr>
- <td>Sony Ericsson</td>
- <td><code>0fce</code></td>
- </tr>
- <tr>
- <td>Sony Mobile Communications</td>
- <td><code>0fce</code></td>
- </tr>
- <tr>
- <td>Teleepoch</td>
- <td><code>2340</code></td>
- </tr>
- <tr>
- <td>Toshiba</td>
- <td><code>0930</code></td>
- </tr>
- <tr>
- <td>ZTE</td>
- <td><code>19d2</code></td>
- </tr>
-</table>
+++ /dev/null
-page.title=Running Apps in the Android Emulator
-parent.title=Android Studio
-parent.link=index.html
-page.tags=emulator
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#about">About the Android Emulator</a></li>
- <li><a href="#runningapp">Running an App in the Android Emulator</a></li>
- <li><a href="#runningemulator">Launching the Android Emulator Without Running an App</a></li>
- <li><a href="#navigate">Navigating on the Screen</a></li>
- <li><a href="#tasks">Performing Basic Tasks in the Emulator</a></li>
- <li><a href="#extended">Working With Extended Controls, Settings, and Help</a></li>
-
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/help/emulator.html">Android Emulator Command Line Features</a></li>
- <li><a href="{@docRoot}tools/devices/managing-avds.html">Managing AVDs with
- AVD Manager</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>The Android Emulator simulates a device and displays it on your development
-computer. It lets you prototype, develop, and test
-Android apps without using a hardware device. The emulator supports Android
-phone, tablet, Android Wear, and Android TV devices. It comes with predefined
-device types
-so you can get started quickly, and you can create your own device definitions
-and emulator skins.</p>
-
-<p>The Android Emulator is fast,
-powerful, and feature-rich. It can transfer information faster than using
-a connected hardware device, speeding up the development process. The
-multi-core feature lets the emulator take advantage of multiple core
-processors on your development computer to improve emulator performance even
-more.</p>
-
-<img src="{@docRoot}images/tools/e-emulator.png" style="height:400px" alt="emulator"/>
-
-<h2 id="about">About the Android Emulator</h2>
-
-<p>You can launch an app on the emulator when you run your project, or you can
-drag an APK file onto the emulator to install it. As with a hardware device,
-after you install an app
-on a virual device, it remains until you uninstall or replace it. If needed, you
-can test how multiple apps, such as your own or system apps, work with each
-other.</p>
-
-<h3 id="features">Features for trying out your apps</h3>
-
-<p>You interact with the emulator just as you would with a hardware device, but
-using your mouse and keyboard, and emulator buttons and controls.
-The emulator supports virtual hardware buttons and touchscreens, including
-two-finger operations,
-as well as directional pads (D-pads), trackballs, wheels, and various
-sensors. You can dynamically resize the emulator window as needed, zoom in and
-out, change the orientation, and even take a screenshot.</p>
-
-<p>When your app is running on
-the emulator, it can use the services of the Android platform to invoke other
-apps, access the network, play audio and video, accept audio input,
-store and retrieve data, notify the user, and render graphical transitions and
-themes. The emulator has controls that let
-you easily send incoming phone calls and text messages, specify
-the location of the device, simulate fingerprint scans, specify network
-speed and status, and simulate battery properties. The emulator can
-simulate an SD card and internal data storage; you can drag a file, such as a
-graphics or data file, onto the emulator to store it.</p>
-
-<h3 id="avds">Android Virtual Device configurations</h3>
-
-<p>The emulator uses an Android Virtual Device (AVD) configuration to determine
-the look, functionality, and system image of the simulated device. AVDs let you
-define certain hardware aspects of your emulated devices and allow you to create
-many configurations to test different Android platforms and hardware
-permutations.</p>
-
-<p>Each AVD functions as an independent device, with its own private storage for
-user data, SD card, and so on. When you launch the emulator with an AVD
-configuration, it automatically loads the user data and SD card data from the
-AVD directory. By default, the emulator stores the user data, SD card data, and
-cache in the AVD directory.</p>
-
-<p>To create and manage AVDs, use the
-<a href="{@docRoot}tools/devices/managing-avds.html">AVD Manager</a>.
-For more information, see
-<a href="{@docRoot}tools/devices/index.html">Managing Virtual Devices</a>.</p>
-
-<h3 id="system">System images</h3>
-
-<p>The Android Emulator runs a full
-Android system stack, down to the kernel level, that includes a set of
-preinstalled apps (such as the dialer) that you can access from your
-apps. You can choose which version of the Android system you want to
-run in the emulator when creating AVDs.
-</p>
-
-<p>The Android system images available through the AVD Manager contain
-code for the Android Linux kernel, the native libraries, the VM, and the
-various Android packages (such as the Android framework and preinstalled
-apps).</p>
-
-<h3 id="dependencies">Dependencies and prerequisites</h3>
-<p>The Android Emulator has the following requirements:</p>
- <ul>
- <li>Android Studio 2.0 or higher</li>
- <li>SDK Tools 25.0.10 or higher</li>
- <li><a href="{@docRoot}sdk/index.html#Requirements">System
- requirements</a></li>
- <li>Newly created AVDs to replace any AVDs for emulator 24.0.<em>x</em> or
- lower</li>
- <li>Active network connection for certain operations, such as testing app
- features that require it</li>
- <li>adb integration enabled through <strong>Tools</strong> >
- <strong>Android</strong> > <strong>Enable ADB Integration</strong>
- </li>
-</ul>
-
-<h3 id="limitations">What's not supported</h3>
-
-<p>The Android Emulator supports most features of a device, but doesn't
-include virtual hardware for:</p>
-<ul>
-<li>WiFi</li>
-<li>Bluetooth</li>
-<li>NFC</li>
-<li>SD card insert/eject</li>
-<li>Device-attached headphones</li>
-<li>USB</li>
-</ul>
-<p>The watch emulator for Android Wear doesn't support the Overview
-(Recent Apps) button, D-pad, and fingerprint sensor.</p>
-
-<p>While most end users of phones and tablets tend to use earlier API levels,
-Android Wear and Android TV users tend to use the latest releases. Using recent
-releases can give you a better experience using the emulator.
-</p>
-
-<h2 id="runningapp">Running an App in the Android Emulator</h2>
-
-<p>You can run an app from an Android Studio project. Or, you can run an app
-that's been installed on the emulator as you would run any app on a device.</p>
-
-<p>To start the emulator and run an app in your project:</p>
-<ol>
-<li>Open an Android Studio project and select Run <img src="{@docRoot}images/tools/e-irun.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Run icon" />.</li>
- <p>The <em>Select Deployment Target</em> dialog appears.</p>
-<img src="{@docRoot}images/tools/e-selectdeploymenttarget.png"
-style="height:250px" alt="Select Deployment Target dialog" />
-<li>If you receive an error or warning message at the top of the dialog, click
-the link to correct the problem or get more information.</li>
-<p>The <strong>No USB devices or running emulators detected</strong> warning
-means that you don’t currently have any emulators running, or any detected
-hardware devices connected to your computer. If you
-don’t have hardware devices connected to your computer, or any emulators
-running, you can ignore it. </p>
-<p>Some errors you must fix before you can continue, such as certain Hardware
-Accelerated Execution Manager (Intel® HAXM) errors.</p>
-<li>In the <em>Select Deployment Target</em> dialog, select an existing emulator
-definition, and then click <strong>OK</strong>.</p>
-<p>If you don’t see a definition you want to use, click <strong>Create New
-Emulator</strong> to launch the AVD Manager. After you define a new AVD, in
-the <em>Select Deployment
-Target</em> dialog, click <strong>OK</strong>.</p>
-<p>If you want to use this emulator definition as the default for your project,
-select <strong>Use same selection for future launches</strong>.</p>
-<p>The emulator launches and displays your app.</p>
-<li>Test your app in the emulator.</li>
-<p>You can use the features described in the following sections:</p>
-<ul>
-<li><a href="#navigate">Navigating on the Screen</a></li>
-<li><a href="#tasks">Performing Basic Tasks in the Emulator</a></li>
-<li><a href="#extended">Working With Extended Controls, Settings, and Help</a></li>
-</ul>
-<li>To close the emulator, click Close <img src="{@docRoot}images/tools/e-iclose.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Close icon" />.</li>
- <p>The emulator device stores the installed app so you can run it again, if
- needed. You need to uninstall an app to remove it. If you run the project
- again on the same emulator, it replaces the app with the new version.</p>
-</ol>
-
-<h2 id="runningemulator">Launching the Android Emulator Without Running an App</h2>
-
-<p>To start the emulator:</p>
-<ol>
-<li><a href="{@docRoot}tools/devices/managing-avds.html">Open the AVD Manager</a>.</li>
-<li>Double-click an AVD, or click Run <img src="{@docRoot}images/tools/e-irun.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Run icon" />.</li>
- <p>The Android Emulator appears.</p>
- <p>While the emulator is running, you can run Android Studio projects and
- choose the
- emulator as the target device. You can also drag one or more APKs onto the
- emulator to install them, and then run them.</p>
-</ol>
-
-
-<h2 id="navigate">Navigating on the Screen</h2>
-
-<p>Use your computer mouse pointer to mimic your finger on the touchscreen;
-select menu items and input fields; and click buttons and controls.
-Use your computer keyboard to type characters and enter emulator shortcuts.</p>
-<table border="0" style="clear:left;">
-<tr>
- <th scope="col">Feature</th>
- <th scope="col">Description</th>
- </tr>
-
- <tr>
- <td>Swipe the screen</td>
- <td>Point to the screen, press and hold the primary mouse button, swipe
- across the screen, and then release.</td>
- </tr>
- <tr>
- <td>Drag an item</td>
- <td>Point to an item on the screen, press and hold the primary mouse
- button, move the item, and then release.</td>
- </tr>
- <tr>
- <td>Tap <div>(touch)</div></td>
- <td>Point to the screen, press the primary mouse button, and then release.
- For example, you could click a text field to start typing in it, select an
- app, or press a button.</td>
- </tr>
- <tr>
- <td>Double tap</td>
- <td>Point to the screen, press the primary mouse button quickly twice,
- and then release.</td>
- </tr>
- <tr>
- <td>Touch and hold</td>
- <td>Point to an item on the screen, press the primary mouse button, hold,
- and then release. For example, you could open options for an item. </td>
- </tr>
- <tr>
- <td>Type</td>
- <td>You can type in the emulator by using your computer keyboard, or using
- a keyboard that pops up on the emulator screen. For example, you could
- type in a text field after you selected it.</td>
- </tr>
- <tr>
- <td><nobr>Pinch and spread</nobr></td>
- <td><div>Pressing Ctrl or Command (⌘) brings up a pinch gesture multi-touch
- interface. The mouse acts as the first finger, and across the anchor point
- is the second finger. Drag the cursor to move the first point.</div>
- <div>Clicking the left mouse button acts like touching down both points, and
- releasing acts like picking both up.</div></td>
- </tr>
-</table>
-
-<h2 id="tasks">Performing Basic Tasks in the Emulator</h2>
-
-<p>The panel on the right side of the emulator lets you perform various tasks.
-You can also drag files onto the emulator to install apps and download files.
-</p>
-<table border="0" style="clear:left;">
- <tr>
- <th scope="col">Feature</th>
- <th scope="col">Description</th>
- <th scope="col">Keyboard Shortcut</th>
- </tr>
- <tr>
- <td>Close<br><img src="{@docRoot}images/tools/e-iclose.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Close icon" /></td>
- <td>Close the emulator.</td>
- <td></td>
- </tr>
- <tr>
- <td>Minimize<br><img src="{@docRoot}images/tools/e-iminimize.png"
- style="vertical-align:sub;margin:0;height:9px" alt="Minimize icon" /></td>
- <td>Minimize the emulator window.</td>
- <td></td>
- </tr>
- <tr>
- <td>Resize</td>
- <td>Resize the emulator as you would any other operating system window. The
-emulator maintains an aspect ratio appropriate for your device.</td>
- <td>⌘↑ and ⌘↓</td>
- </tr>
- <tr>
- <td>Power<br><img src="{@docRoot}images/tools/e-ipower.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Power icon" /></td>
- <td>Click to turn the screen on or off.<br>Click and hold to turn the device
- on or off. </td>
- <td><div>Ctrl+P</div> <div>⌘P</div></td>
- </tr>
- <tr>
- <td>Volume Up<br><img src="{@docRoot}images/tools/e-ivolumeup.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Volume Up icon" /></td>
- <td>Click to view a slider control and turn the volume up. Click again to
- turn it up more, or use the slider control to change the volume. </td>
- <td><div>Ctrl+=</div><div>⌘=</div></td>
- </tr>
- <tr>
- <td>Volume Down<br><img src="{@docRoot}images/tools/e-ivolumedown.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Volume Down icon" /></td>
- <td>Click to view a slider control and turn the volume down. Click again to
- turn it down more, or use the slider control to change the volume. </td>
- <td><div>Ctrl+-</div><div>⌘-<div></td>
- </tr>
- <tr>
- <td>Rotate Left<br><img src="{@docRoot}images/tools/e-irotateleft.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Rotate Left icon" /></td>
- <td>Rotate the phone 90 degrees counterclockwise.</td>
- <td><div>Ctrl+Left</div><div>⌘←</div></td>
- </tr>
- <tr>
- <td>Rotate Right<br><img src="{@docRoot}images/tools/e-irotateright.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Rotate Right icon" /></td>
- <td>Rotate the phone 90 degrees clockwise.</td>
- <td><div>Ctrl+Right</div><div>⌘→</div></td>
- </tr>
- <tr>
- <td>Take Screenshot<br><img src="{@docRoot}images/tools/e-itakescreenshot.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Take Screenshot icon" />
- </td>
- <td>Click to take a screenshot of the device. The default save location is
- your computer desktop. To change the save location, select
- <strong>…</strong> > <strong>Settings</strong>. The emulator creates a
- file with the name <code>Screenshot_<em>yyyymmdd-hhmmss</em>.png</code>
- using the year, month, day, hour, minute, and second of the capture, for
- example, <code>Screenshot_20160219-145848.png</code>. </td>
- <td><div>Ctrl+S</div><div>⌘S<div></td>
- </tr>
- <tr>
- <td><nobr>Enter Zoom Mode</nobr><br><img src="{@docRoot}images/tools/e-izoom.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Enter Zoom Mode icon" />
- </td>
- <td><p>Click so the cursor changes to the zoom icon:</p>
-<ul>
- <li> Left-click the screen to zoom in by 25%, up to a maximum of about twice
- the screen resolution of the virtual device.
- <li> Right-click to zoom out.
- <li> Left-click and drag to select a box-shaped area to zoom in on.
- <li> Right-click and drag a selection box to reset to default zoom.
- <li> Ctrl-click to touch the screen while in zoom mode.
-</ul>
-<p>Click Enter Zoom Mode again to return to normal screen size.</p></td>
- <td><div>Ctrl+Z</div><div>⌘Z</div>
- <div>While in zoom mode:</div>
- <div>Ctrl+Up</div><div>Ctrl+Down</div>
- <div>Ctrl+Shift+Up</div><div>Ctrl+Shift+Down</div>
- <div>Ctrl+Shift+Left</div><div>Ctrl+Shift+Right</div>
- <div>⌘↑ and ⌘↓</div>
- <div>⇧⌘↑ and ⇧⌘↓</div>
- <div>⇧⌘← and ⇧⌘→</div></td>
- </tr>
- <tr>
- <td>Back<br><img src="{@docRoot}images/tools/e-iback.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Back icon" /></td>
- <td>Return to the previous screen, or close a dialog box, an options menu,
- the Notifications panel, or the onscreen keyboard. </td>
- <td><div>Ctrl+Backspace</div>
- <div>⌘⌫</div></td>
- </tr>
- <tr>
- <td>Home<br><img src="{@docRoot}images/tools/e-ihome.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Home icon" /></td>
- <td>Return to the Home screen. Press and hold to open the item specific to
- your API level. </td>
- <td><div>Ctrl+H</div><div>⌘⇧H</div></td>
- </tr>
- <tr>
- <td><div>Overview<br><img src="{@docRoot}images/tools/e-ioverview.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Overview icon" /></div>
- <div>(Recent Apps)</div></td>
- <td>Tap to open a list of thumbnail images of apps you’ve worked with
- recently. To open an app, tap it. To remove a thumbnail from the list,
- swipe it left or right. This button isn't supported for Android Wear.</td>
- <td><div>Ctrl+O</div><div>⌘O</div></td>
- </tr>
- <tr>
- <td>Menu</td>
- <td>Type the keyboard shortcut to simulate the Menu button, for example,
- to open the menu for the selected app.</td>
- <td><div>Ctrl+M</div><div>⌘M</div></td>
- </tr>
- <tr>
- <td>More<br><img src="{@docRoot}images/tools/e-imore.png"
- style="vertical-align:sub;margin:0;height:9px" alt="More icon" /></td>
- <td>Click to access other features and settings, described in the next
- table.</td>
- <td></td>
- </tr>
- <tr>
- <td>Install an APK</td>
- <td>Drag an APK file onto the emulator screen. An APK Installer dialog
- appears. When the installation completes, you can view the app in your
- apps list.The app didn’t install if a dialog appears that says “APK failed
- to install.”</td>
- <td></td>
- </tr>
- <tr>
- <td>Add a file</td>
- <td>Drag any file onto the emulator screen. It’s placed in the
- <code>/sdcard/Download</code> directory. Navigate to the file using the
- method for the API level. For example, for API 22, this is the navigation
- path: <strong>Settings</strong> > <strong>Device: Storage & USB</strong>
- > <strong>Internal Storage</strong> > <strong>Explore</strong>
- (Virtual SD Card). </td>
- <td></td>
- </tr>
- <tr>
- <td>Toggle trackball mode</td>
- <td></td>
- <td>F6</td>
- </tr>
-</table>
-
-<h2 id="extended">Working With the Extended Controls, Settings, and Help</h2>
-
-<p>The extended controls let you send data, change device properties, control
-apps, and more. To access the controls, select <strong>…</strong> in the
-emulator panel and then select the option you want in the left panel of the
-<em>Extended Controls</em> dialog.</p>
-
-<table border="0" style="clear:left;">
- <tr>
- <th scope="col">Feature</th>
- <th scope="col">Description</th>
- <th scope="col">Keyboard Shortcuts</th>
- </tr>
- <tr>
- <td>Location</td>
- <td>
-<p>The emulator lets you simulate “my location” information: the location where
-the emulated device is currently located. For example, if you click My Location
-<img src="{@docRoot}images/tools/e-ilocation.png"
- style="vertical-align:sub;margin:0;height:17px" alt="My Location icon" />
- in Google Maps and then send a location, the map shows it.</p>
- <p>To send a GPS location:</p>
-<ol>
- <li> Select <strong>Decimal</strong> or <strong>Sexagesimal</strong>.</li>
- <li> Specify the location.</li>
-
-<p>In decimal mode, enter a <strong>Latitude</strong> value in the range -90.0
-to +90.0 degrees and a <strong>Longitude</strong> value in the range -180.0 to
-+180.0 degrees.</p>
-<p>In sexigesimal mode, enter a three-part <strong>Latitude</strong> value in
-the range -90 to +90 degrees, 0 to 59 minutes, and 0.0 to 60.0
-seconds. Enter a <strong>Longitude</strong> value in the range -180 to +180
-degrees, 0 to 59 minutes, and 0.0 to 60.0 seconds.</p>
-<p>For the latitude, - indicates south and + indicates north; for the longitude,
-- indicates west and + indicates east. The + is optional.</p>
-<p>Optionally specify an <strong>Altitude</strong> value in the range
--1,000.0 to +10,000.0 meters.</p>
-
- <li> Click <strong>Send</strong>.</li>
-</ol>
-<p>To use geographic data from a GPS exchange format (GPX) or Keyhole Markup
-Language (KML) file:</p>
-<ol>
- <li> Click <strong>Load GPX/KML</strong>.</li>
- <li> In the file dialog, select a file on your computer and click
- <strong>Open</strong>.</li>
- <li> Optionally select a <strong>Speed</strong>.</li>
-<p>The speed defaults to the <strong>Delay</strong> value (<strong>Speed
-1X</strong>). You can increase the speed by double (<strong>Speed</strong>
-<strong>2X</strong>), triple (<strong>Speed 3X</strong>), and so on.</p>
-
- <li> Click Run <img src="{@docRoot}images/tools/e-irun.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Run icon" />.</li>
-</ol>
-</td>
- <td><div>Ctrl+Shift+L</div><div>⇧⌘L</div></td>
- </tr>
- <tr>
- <td>Cellular</td>
- <td><p>The emulator lets you simulate various network conditions. You can
- approximate the network speed for different network protocols, or you can
- specify <strong>Full</strong>, which transfers data as quickly as your
- computer allows. Specifying a network protocol is always slower than
- <strong>Full</strong>. You can also specify the voice and data network
- status, such as roaming. The defaults are set in the AVD.</p>
- <p>Select a <strong>Network type</strong>:</p>
-<ul>
- <li> GSM - Global System for Mobile Communications</li>
- <li> HSCSD - High-Speed Circuit-Switched Data</li>
- <li> GPRS - Generic Packet Radio Service</li>
- <li> EDGE - Enhanced Data rates for GSM Evolution</li>
- <li> UMTS - Universal Mobile Telecommunications System</li>
- <li> HSPDA - High-Speed Downlink Packet Access</li>
- <li> Full (default)</li>
-</ul>
-<p>Select a <strong>Voice status</strong>, <strong>Data status</strong>, or
-both:</p>
-<ul>
- <li> Home (default)</li>
- <li> Roaming</li>
- <li> Searching</li>
- <li> Denied (emergency calls only)</li>
- <li> Unregistered (off)</li>
-</ul>
-</td>
- <td><div>Ctrl+Shift+C</div><div>⇧⌘C</td>
- </tr>
- <tr>
- <td>Battery</td>
- <td><p>You can simulate the battery properties of a device to see how your
- app performs under different conditions. To select a <strong>Charge
- level</strong>, use the slider control.</p>
- <p>Select a <strong>Charger connection</strong> value:</p>
-<ul>
- <li>None</li>
- <li>AC charger</li>
-</ul>
-<p>Select a <strong>Battery health</strong> value:</p>
-<ul>
- <li> Good (default)</li>
- <li> Failed</li>
- <li> Dead</li>
- <li> Overvoltage</li>
- <li> Overheated</li>
- <li> Unknown</li>
-</ul>
-<p>Select a <strong>Battery status </strong>value:</p>
-<ul>
- <li> Unknown</li>
- <li> Charging (default)</li>
- <li> Discharging</li>
- <li> Not charging</li>
- <li> Full</li>
-</ul>
-</td>
- <td><div>Ctrl+Shift+B</div><div>⇧⌘B</div></td>
- </tr>
- <tr>
- <td>Phone</td>
- <td><p>The emulator lets you simulate incoming phone calls and text
- messages. Note that the information flow is one way, from the control to
- the emulator. For example, the control doesn’t change its state if the
- emulator hangs up; you need to end the call in the control.</p>
- <p>To initiate a call to the emulator:</p>
-<ol>
- <li> Select or type a phone number in the <strong>From</strong> field.</li>
- <li> Click <strong>Call Device</strong>.</li>
- <li> Optionally click <strong>Hold Call</strong> to put the call on hold.</li>
- <li> To end the call, click <strong>End Call</strong>.</li>
-</ol>
-<p>To send a text message to the emulator:</p>
-<ol>
- <li> Select or type a phone number in the <strong>From</strong> field.</li>
- <li> Type a message in the <strong>SMS message</strong> field.</li>
- <li> Click <strong>Send Message</strong>.</li>
-</ol>
-</td>
- <td><div>Ctrl+Shift+P</div><div>⇧⌘P</div></td>
- </tr>
- <tr>
- <td>Directional Pad</td>
- <td><p>If the AVD has the directional pad enabled in the hardware profile,
- you can use the directional pad controls with the emulator. However, not
- all devices can support the directional pad; for example, an Android watch.
- The buttons simulate the following actions:</p>
-<img src="{@docRoot}images/tools/e-dpad.png"
- style="vertical-align:sub;margin:0;width:244px" alt="Directional Pad Control" />
-</td>
- <td><div>Ctrl+Shift+D</div><div>⇧⌘D</div></td>
- </tr>
- <tr>
- <td>Fingerprint</td>
- <td><p>This control can simulate 10 different fingerprint scans. You can
- use it to test fingerprint integration in your app. This feature isn't
- supported for Android Wear.</p>
- <p>To simulate a fingerprint scan on the virtual device:</p>
-<ol>
- <li> Prepare an app to receive a fingerprint.</li>
- <li> Select a <strong>Fingerprint</strong> value.</li>
- <li> Click <strong>Touch Sensor</strong>.</li>
-</ol>
-</td>
- <td><div>Ctrl+Shift+F</div><div>⇧⌘F</div></td>
- </tr>
- <tr>
- <td>Settings</td>
- <td><p>You can specify the following settings:</p>
-<ul>
- <li> <strong>Emulator window theme</strong> - Select Light or Dark.</li>
- <li> <strong>Send keyboard shortcuts to</strong> - By default, some keyboard
- combinations will trigger emulator control shortcuts. If you’re developing
- an app that includes keyboard shortcuts, such as one targeted at
- devices with Bluetooth keyboards, you can change this setting to send
- <em>all</em> keyboard input to the virtual device, including input
- that would be a shortcut in the emulator.</li>
- <li> <strong>Screenshot save location</strong> - Click the folder icon to
- specify a location to save screenshots of the emulator screen.</li>
- <li> <strong>Use detected ADB location</strong> - If you're running the
- emulator from Android Studio, you should select this setting (the default).
- If you run the emulator from outside Android Studio and want it to use a
- specific adb executable, deselect this option and specify the SDK Tools
- location. If this setting is incorrect, features such as drag-and-drop app
- install and file copy, and screenshot capture, won't work. </li>
- <li> <strong>When to send crash reports</strong> - Select Always, Never, or
- Ask. </li>
-</ul>
-</td>
- <td>Ctrl+Shift+S<br>⇧⌘S</td>
- </tr>
- <tr>
- <td>Help > Keyboard Shortcuts</td>
- <td><p>See the keyboard shortcuts that the emulator accepts. For the
- shortcuts to work, you need to:</p>
-<ul>
- <li>Select <strong>Settings</strong> > <strong>Send keyboard shortcuts
- to</strong> > <strong>Emulator controls (default)</strong>.</li>
-</ul>
-</td>
- <td>F1<br>⌘/</td>
- </tr>
- <tr>
- <td>Help > Emulator Help</td>
- <td><p>To go to the online documentation for the emulator, click
- <strong>Documentation</strong>.</p>
- <p>To file a bug against the emulator, click <strong>File a Bug</strong>.
- </p>
- <p>To make suggestions, click <strong>Send Feedback</strong>.</p>
- <p>All of these links require an internet connection and a browser.</p> </td>
- <td>F1<br>⌘/</td>
- </tr>
- <tr>
- <td>Help > About</td>
- <td><p>See which adb port the emulator uses, as well as the Android and
- emulator version numbers. Compare the latest available emulator version
- with your version to determine if you have the latest software installed.
- </p>
- <p>The emulator serial number is <strong>emulator-<em></strong>adb_port</em>,
- which you can specify as an adb command line option, for example.</p></td>
- <td>F1<br>⌘/</td>
- </tr>
-</table>
-
-
-
-
-
+++ /dev/null
-page.title=Managing Virtual Devices
-@jd:body
-
-
- <p>An Android Virtual Device (AVD) is an emulator configuration that lets you model an actual
- device by defining hardware and software options to be emulated by the Android Emulator.</p>
-
- <p>The easiest way to create an AVD is to use the graphical
- <a href="{@docRoot}tools/devices/managing-avds.html">AVD Manager</a>, which you launch
- from Android Studio by clicking <strong>Tools > Android > AVD Manager</strong>. You can
- also start the AVD Manager from the command line by calling the <code>android</code> tool with
- the <code>avd</code> options, from the <strong><sdk>/tools/</strong> directory.</p>
-
- <p>You can also create AVDs on the command line by passing the <code>android</code> tool options.
- For more information on how to create AVDs in this manner, see
- <a href="{@docRoot}tools/devices/managing-avds-cmdline.html">Managing Virtual Devices from the
- Command Line</a>.</p>
-
- <p>An AVD consists of:</p>
-
- <ul>
- <li>A hardware profile: Defines the hardware features of the virtual
- device. For example, you can define whether the device has a camera, whether it uses a physical
- QWERTY keyboard or a dialing pad, how much memory it has, and so on.</li>
-
- <li>A mapping to a system image: You can define what version of the Android platform will run
- on the virtual device. You can choose a version of the standard Android platform or the system
- image packaged with an SDK add-on.</li>
-
- <li>Other options: You can specify the emulator skin you want to use with the AVD, which lets
- you control the screen dimensions, appearance, and so on. You can also specify the emulated SD
- card to use with the AVD.</li>
-
- <li>A dedicated storage area on your development machine: the device's user data (installed
- applications, settings, and so on) and emulated SD card are stored in this area.</li>
- </ul>
-
- <p>You can create as many AVDs as you need, based on the types of device you want to model.
- To thoroughly test your application, you should create an AVD for each general device configuration
- (for example, different screen sizes and platform versions) with which your application is compatible
- and test your application on each one.</p>
-
- <p>Keep these points in mind when you are selecting a system image target for your AVD:</p>
-
- <ul>
- <li>The API Level of the target is important, because your application will not be able to run
- on a system image whose API Level is less than that required by your application, as specified
- in the <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">
- <code>minSdkVersion</code></a> attribute of the application's manifest file. For more
- information about the relationship between system API Level and application
- <code>minSdkVersion</code>, see <a href=
- "{@docRoot}tools/publishing/versioning.html">Specifying Minimum System API Version</a>.</li>
-
- <li>You should create at least one AVD that uses a target whose API Level is greater than that required
- by your application, because it allows you to test the
- forward-compatibility of your application. Forward-compatibility testing ensures that, when
- users who have downloaded your application receive a system update, your application will
- continue to function normally.</li>
-
- <li>If your application declares a
- <a href="{@docRoot}guide/topics/manifest/uses-library-element.html"><code>uses-library</code></a>
- element in its manifest file, the application can only run on a system image in which that external
- library is present. If you want to run your application on an emulator, create an AVD that
- includes the required library. Usually, you must create such an AVD using an Add-on component for the
- AVD's platform (for example, the Google APIs Add-on contains the Google Maps library).</li>
- </ul>
-
- <p>To learn how to manage AVDs using a graphical tool, read <a href=
- "{@docRoot}tools/devices/managing-avds.html">Managing AVDs with AVD Manager</a>. To
- learn how to manage AVDs on the command line, read
- <a href="{@docRoot}tools/devices/managing-avds-cmdline.html">Managing AVDs
- from the Command Line</a>.</p>
-
-
-
-
-
-
+++ /dev/null
-page.title=Managing AVDs from the Command Line
-parent.title=Managing Virtual Devices
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#listingtargets">Listing Targets</a></li>
- <li><a href="#AVDCmdLine">Creating AVDs</a>
- <ol>
- <li><a href="#CustomDensity">Customize the device resolution or density</a></li>
- <li><a href="#DefaultLocation">Default location of AVD files</a></li>
- <li><a href="#hardwareopts">Setting hardware emulation options</a></li>
- </ol>
- </li>
- <li><a href="#moving">Moving an AVD</a></li>
- <li><a href="#updating">Updating an AVD</a></li>
- <li><a href="#deleting">Deleting an AVD</a></li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/building/building-cmdline.html">Building and Running
-from the Command Line</a></li>
- <li><a href="{@docRoot}tools/devices/emulator.html">Using the Android
-Emulator</a></li>
- </ol>
- </div>
-</div>
-
-
-<p>The <code>android</code> tool lets you manage AVDs on the command line. For a complete reference
-of the command line options that you can use, see the reference for the
-<a href="{@docRoot}tools/help/android.html"><code>android</code></a> tool.</p>
-
-
-
-<h2 id="listingtargets">Listing Targets</h2>
-
-<p>To generate a list of system image targets, use this command: </p>
-
-<pre>android list targets</pre>
-
-<p>The <code>android</code> tool scans the <code><sdk>/platforms/</code> and
-<code><sdk>/add-ons/</code> directories looking for valid system images and
-then generates the list of targets. Here's an example of the command output:
-</p>
-
-<pre>Available Android targets:
-id: 1 or "android-3"
- Name: Android 1.5
- Type: Platform
- API level: 3
- Revision: 4
- Skins: QVGA-L, HVGA-L, HVGA (default), HVGA-P, QVGA-P
-id: 2 or "android-4"
- Name: Android 1.6
- Type: Platform
- API level: 4
- Revision: 3
- Skins: QVGA, HVGA (default), WVGA800, WVGA854
-id: 3 or "android-7"
- Name: Android 2.1-update1
- Type: Platform
- API level: 7
- Revision: 2
- Skins: QVGA, WQVGA400, HVGA (default), WVGA854, WQVGA432, WVGA800
-id: 4 or "android-8"
- Name: Android 2.2
- Type: Platform
- API level: 8
- Revision: 2
- Skins: WQVGA400, QVGA, WVGA854, HVGA (default), WVGA800, WQVGA432
-id: 5 or "android-9"
- Name: Android 2.3
- Type: Platform
- API level: 9
- Revision: 1
- Skins: HVGA (default), WVGA800, WQVGA432, QVGA, WVGA854, WQVGA400
-</pre>
-
-
-
-<h2 id="AVDCmdLine">Creating AVDs</h2>
-
-<p>In addition to creating AVDs with the
-<a href="{@docRoot}tools/help/avd-manager.html">AVD Manager user interface</a>,
-you can also create them by passing in command line arguments to the <code>android</code> tool.
-</p>
-
-<p>Open a terminal window and change to
-the <code><sdk>/tools/</code> directory, if needed.</p>
-
-<p>To create each AVD, you issue the command <code>android create avd</code>,
-with options that specify a name for the new AVD and the system image you want
-to run on the emulator when the AVD is invoked. You can specify other options on
-the command line also, such as the emulated SD card size, the emulator skin, or a custom
-location for the user data files.</p>
-
-<p>Here's the command-line usage for creating an AVD: </p>
-
-<pre>android create avd -n <name> -t <targetID> [-<option> <value>] ... </pre>
-
-<p>You can use any name you want for the AVD, but since you are likely to be
-creating multiple AVDs, you should choose a name that lets you recognize the
-general characteristics offered by the AVD. The target ID is an integer assigned by the
-<code>android</code> tool. The target ID is not derived from the system image name,
-version, or API Level, or other attribute, so you need to run the <code>android list targets</code>
-command to list the target ID of each system image. You should do this <em>before</em> you run
-the <code>android create avd</code> command. See the <a
-href="{@docRoot}tools/help/android.html">android</a>
-tool documentation for more information on the command line options.</p>
-
-
-<p>When you've selected the target you want to use and made a note of its ID,
-use the <code>android create avd</code> command to create the AVD, supplying the
-target ID as the <code>-t</code> argument. Here's an example that creates an
-AVD with name "my_android1.5" and target ID "2" (the standard Android 1.5
-system image in the list above): </p>
-
-<pre>android create avd -n my_android1.5 -t 2</pre>
-
-<p>If the target you selected was a standard Android system image ("Type:
-platform"), the <code>android</code> tool next asks you whether you want to
-create a custom hardware profile. </p>
-<pre>Android 1.5 is a basic Android platform.
-Do you wish to create a custom hardware profile [no]</pre>
-
-<p>If you want to set custom hardware emulation options for the AVD, enter
-"yes" and set values as needed. If you want to use the default hardware
-emulation options for the AVD, just press the return key (the default is "no").
-The <code>android</code> tool creates the AVD with name and system image mapping you
-requested, with the options you specified. For more information, see <a href="#hardwareopts">
-Setting Hardware Emulation Options</a>.
-
-<p class="note"><strong>Note:</strong> If you are creating an AVD whose target is an SDK add-on, the
-<code>android</code> tool does not allow you to set hardware emulation options.
-It assumes that the provider of the add-on has set emulation options
-appropriately for the device that the add-on is modeling, and so prevents you
-from resetting the options. </p>
-
-
-<h3 id="CustomDensity">Customize the device resolution or density</h3>
-
-<p>When testing your application, we recommend that you test your application in several different
-AVDs, using different screen configurations (different combinations of size and density). In
-addition, you should set up the AVDs to run at a physical size that closely matches an actual
-device.</p>
-
-<p>To set up your AVDs for a specific resolution or density, follow these steps:</p>
-
-<ol>
- <li>Use the <code>create avd</code> command to create a new AVD, specifying
-the <code>--skin</code> option with a value that references either a default
-skin name (such as "WVGA800") or a custom skin resolution (such as 240x432).
-Here's an example:
- <pre>android create avd -n <name> -t <targetID> --skin WVGA800</pre>
- </li>
- <li>To specify a custom density for the skin, answer "yes" when asked whether
-you want to create a custom hardware profile for the new AVD.</li>
- <li>Continue through the various profile settings until the tool asks you to
-specify "Abstracted LCD density" (<em>hw.lcd.density</em>). Enter an appropriate
-value, such as "120" for a low-density screen, "160" for a medium density screen,
-or "240" for a high-density screen.</li>
- <li>Set any other hardware options and complete the AVD creation.</li>
-</ol>
-
-<p>In the example above (WVGA medium density), the new AVD will emulate a 5.8"
-WVGA screen.</p>
-
-<p>As an alternative to adjusting the emulator skin configuration, you can use
-the emulator skin's default density and add the <code>-dpi-device</code> option
-to the <a href="{@docRoot}tools/help/emulator.html">emulator</a> command line when
-starting the AVD. For example:</p>
-
-<pre>emulator -avd WVGA800 -scale 96dpi -dpi-device 160</pre>
-
-
-
-<h3 id="DefaultLocation">Default location of AVD files</h3>
-
-<p>When you create an AVD, the <code>android</code> tool creates a dedicated directory for it
-on your development computer. The directory contains the AVD configuration file,
-the user data image and SD card image (if available), and any other files
-associated with the device. Note that the directory does not contain a system
-image — instead, the AVD configuration file contains a mapping to the
-system image, which it loads when the AVD is launched. </p>
-
-<p>The <code>android</code> tool also creates an <code><AVD_name>.ini</code> file for the AVD at the
-root of the <code>.android/avd/</code> directory on your computer. The file specifies the
-location of the AVD directory and always remains at the root the .android
-directory.</p>
-
-<p>By default, the <code>android</code> tool creates the AVD directory inside
-<code>~/.android/avd/</code> (on Linux/Mac), <code>C:\Documents and
-Settings\<user>\.android\</code> on Windows XP, and
-<code>C:\Users\<user>\.android\</code> on Windows 7 and Vista.
-If you want to use a custom location for the AVD directory, you
-can do so by using the <code>-p <path></code> option when
-you create the AVD: </p>
-
-<pre>android create avd -n my_android1.5 -t 2 -p path/to/my/avd</pre>
-
-<p>If the .android directory is hosted on a network drive, we recommend using
-the <code>-p</code> option to place the AVD directory in another location.
-The AVD's .ini file remains in the .android directory on the network
-drive, regardless of the location of the AVD directory.
-
-
-<h3 id="hardwareopts">Setting hardware emulation options</h3>
-
-<p>When you are creating a new AVD that uses a standard Android system image ("Type:
-platform"), the <code>android</code> tool lets you set hardware emulation
-options for virtual device. The table below lists the options available and the
-default values, as well as the names of properties that store the emulated
-hardware options in the AVD's configuration file (the config.ini file in the
-AVD's local directory). </p>
-
-<p class="table-caption"><strong>Table 1.</strong> Available hardware profile options for AVDs and
-the default values </p>
-
-<table>
-<tr>
-<th>Characteristic</th>
-<th>Description</th>
-<th>Property</th>
-</tr>
-
-<tr>
-<td>Device ram size</td>
-<td>The amount of physical RAM on the device, in megabytes. Default value is "96".
-<td>hw.ramSize</td>
-</tr>
-
-<tr>
-<td>Touch-screen support</td>
-<td>Whether there is a touch screen or not on the device. Default value is "yes".</td>
-<td>hw.touchScreen
-
-<tr>
-<td>Trackball support </td>
-<td>Whether there is a trackball on the device. Default value is "yes".</td>
-<td>hw.trackBall</td>
-</tr>
-
-<tr>
-<td>Keyboard support</td>
-<td>Whether the device has a QWERTY keyboard. Default value is "yes".</td>
-<td>hw.keyboard</td>
-</tr>
-
-<tr>
-<td>DPad support</td>
-<td>Whether the device has DPad keys. Default value is "yes".</td>
-<td>hw.dPad</td>
-</tr>
-
-<tr>
-<td>GSM modem support</td>
-<td>Whether there is a GSM modem in the device. Default value is "yes".</td>
-<td>hw.gsmModem</td>
-</tr>
-
-<tr>
-<td>Camera support</td>
-<td>Whether the device has a camera. Default value is "no".</td>
-<td>hw.camera</td>
-</tr>
-
-<tr>
-<td>Maximum horizontal camera pixels</td>
-<td>Default value is "640".</td>
-<td>hw.camera.maxHorizontalPixels</td>
-</tr>
-
-<tr>
-<td>Maximum vertical camera pixels</td>
-<td>Default value is "480".</td>
-<td>hw.camera.maxVerticalPixels</td>
-</tr>
-
-<tr>
-<td>GPS support</td>
-<td>Whether there is a GPS in the device. Default value is "yes".</td>
-<td>hw.gps</td>
-</tr>
-
-<tr>
-<td>Battery support</td>
-<td>Whether the device can run on a battery. Default value is "yes".</td>
-<td>hw.battery</td>
-</tr>
-
-<tr>
-<td>Accelerometer</td>
-<td>Whether there is an accelerometer in the device. Default value is "yes".</td>
-<td>hw.accelerometer</td>
-</tr>
-
-<tr>
-<td>Audio recording support</td>
-<td>Whether the device can record audio. Default value is "yes".</td>
-<td>hw.audioInput</td>
-</tr>
-
-<tr>
-<td>Audio playback support</td>
-<td>Whether the device can play audio. Default value is "yes".</td>
-<td>hw.audioOutput</td>
-</tr>
-
-<tr>
-<td>SD Card support</td>
-<td>Whether the device supports insertion/removal of virtual SD Cards. Default value is "yes".</td>
-<td>hw.sdCard</td>
-</tr>
-
-<tr>
-<td>Cache partition support</td>
-<td>Whether we use a /cache partition on the device. Default value is "yes".</td>
-<td>disk.cachePartition</td>
-</tr>
-
-<tr>
-<td>Cache partition size</td>
-<td>Default value is "66MB".</td>
-<td>disk.cachePartition.size </td>
-</tr>
-
-<tr>
-<td>Abstracted LCD density</td>
-<td>Sets the generalized density characteristic used by the AVD's screen. Default value is "160".</td>
-<td>hw.lcd.density </td>
-</tr>
-
-<tr>
-<td>Trackball support</td>
-<td>Whether there is a trackball present.</td>
-<td>hw.trackBall </td>
-</tr>
-</table>
-
-
-<h2 id="moving">Moving an AVD</h2>
-
-<p>If you want to move or rename an AVD, you can do so using this command:</p>
-
-<pre>android move avd -n <name> [-<option> <value>] ...</pre>
-
-<h2 id="updating">Updating an AVD</h2>
-
-<p>If, for any reason, the platform/add-on root folder has its name changed (maybe because the user has installed an update of the platform/add-on) then the AVD will not be able to load the system image that it is mapped to. In this case, the <code>android list targets</code> command will produce this output:
-
-<pre>The following Android Virtual Devices could not be loaded:
-Name: foo
-Path: <path>/.android/avd/foo.avd
-Error: Invalid value in image.sysdir. Run 'android update avd -n foo' </pre>
-
-<p>To fix this error, use the <code>android update avd</code> command to recompute the path to the system images.</p>
-
-<h2 id="deleting">Deleting an AVD</h2>
-
-<p>You can use the <code>android</code> tool to delete an AVD. Here is the command usage:</p>
-
-<pre>android delete avd -n <name> </pre>
-
-<p>When you issue the command, the <code>android</code> tool looks for an AVD matching the
-specified name deletes the AVD's directory and files. </p>
+++ /dev/null
-page.title=Managing AVDs with the AVD Manager
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#viewing">Viewing and Managing Your AVDs</a></li>
- <li><a href="#createavd">Creating an AVD</a></li>
- <li><a href="#createhp">Creating a Hardware Profile</a></li>
- <li><a href="#workingavd">Working With Existing AVDs</a></li>
- <li><a href="#workinghp">Working With Existing Hardware Profiles</a>
- </li>
- <li><a href="#emulator">Running and Stopping an Emulator, and
- Clearing Data</li>
- <li><a href="#importexporthp">Importing and Exporting Hardware
- Profiles</li>
- <li><a href="#hpproperties">Hardware Profile Properties</a></li>
- <li><a href="#avdproperties">AVD Properties</a></li>
- <li><a href="#skins">Creating Emulator Skins</a></li>
- </ol>
- <h2>Dependencies and prerequisites</h2>
- <ul>
- <li>Android Studio 2.0 or higher</li>
- <li>SDK Tools 25.0.10 or higher</li>
- <li>Active network connection for certain operations, such as downloading
- system images</li>
- <li>adb integration enabled through <strong>Tools</strong> >
- <strong>Android</strong> >
- <strong>Enable ADB Integration</strong></li>
- </ul>
- </div>
- </div>
-
- <p>An Android Virtual Device (AVD) definition lets you define the
- characteristics of an Android phone, tablet, Android Wear, or Android TV
- device that you want to simulate in the
- <a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a>.
- The AVD Manager helps you easily create and manage AVDs. </p>
-
- <p>To effectively test your app, you should create an AVD that models each
- device type that your app is designed to support. For example, we recommend
- that you create an AVD for each API level that's equal to and higher than the
- minimum version you've specified in your manifest
- <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"
- style="white-space: nowrap;"
- >{@code <uses-sdk>}</a> tag.</p>
-
- <p>An AVD contains a hardware profile, system image, skin, and other
- properties.</p>
-
- <p>The hardware profile defines the characteristics of a device as
- shipped from the factory. The AVD Manager comes preloaded with certain
- hardware profiles, such as Nexus phone devices, and you can define and import
- hardware profiles as needed. You can override some of the settings in your
- AVD, if needed.</p>
-
- <p>The AVD Manager helps you choose a system image for your AVD by providing
- recommendations. It also lets
- you download system images, some with add-on libraries, like Google APIs,
- which your app might require. x86 system images run the fastest in the
- emulator. Android Wear and Android TV devices tend to run best (and have
- the largest installed base) on recent releases, while users of Android phones
- and tablets tend to use slightly older releases, as shown in the
- <a href="{@docRoot}about/dashboards/index.html">API level
- dashboards</a>.</p>
-
- <p>An emulator skin specifies the appearance of a device. The AVD Manager
- provides some predefined skins. You can also define your own, or use skins
- provided by third parties.</p>
-
- <p>Just as with a real device, for apps to use certains features defined in an
- AVD, such as the camera, it must have the corresponding
- <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a>
- setting in the app manifest.</p>
-
-<h2 id="viewing">Viewing and Managing Your AVDs</h2>
-
-<p>The AVD Manager lets you manage your AVDs all in one place.</p>
-
-<p>To run the AVD Manager:</p>
-
-<ul>
- <li> In Android Studio, select <strong>Tools</strong> >
- <strong>Android</strong> > <strong>AVD Manager</strong>.</li>
- <li> Click AVD Manager <img src="{@docRoot}images/tools/avd-manager-studio.png"
- style="vertical-align:sub;margin:0;height:17px" alt="AVD Manager icon">
- in the toolbar.</li>
-</ul>
-
-<p>The AVD Manager appears.</p>
-
-<img src="{@docRoot}images/tools/avd-main.png" alt="AVD Manager main window" />
-
-<p>It displays any AVDs you’ve already defined. When you first install
-Android Studio, it creates one AVD. If you defined AVDs for Android Emulator
-24.0.<em>x</em> or lower, you need to recreate them.</p>
-
-<p>From this page you can:</p>
-
-<ul>
- <li> Define a new <a href="#createavd">AVD</a> or
- <a href="#createhp">hardware profile</a>.</li>
- <li> Edit an existing <a href="#workingavd">AVD</a> or
- <a href="#workinghp">hardware profile</a>.</li>
- <li> Delete an <a href="#workingavd">AVD</a> or
- <a href="#workinghp">hardware profile</a>.</li>
- <li> <a href="#importexporthp">Import or export</a> hardware profile
- definitions.</li>
- <li> <a href="#emulator">Run</a> an AVD to start the emulator.</li>
- <li> <a href="#emulator">Stop</a> an emulator.</li>
- <li> <a href="#emulator">Clear</a> data and start fresh, from the same state
- as when you first ran the emulator.</li>
- <li> <a href="#workingavd">Show</a> the associated AVD <code>.ini</code> and
- <code>.img</code> files on disk.</li>
- <li> <a href="#workingavd">View</a> AVD configuration details that you can
- include in any bug
- reports to the Android Studio team.</li>
-</ul>
-
-
- <h2 id="createavd">Creating an AVD</h2>
-
- <p>You can <a href="#newavd">create a new AVD</a> from the beginning, or
- <a href="#copyavd">duplicate an AVD</a> and change some properties.</p>
-
- <p id="newavd">To create a new AVD:</p>
-
- <ol>
- <li id="selecthardwarepage">From the
- <a href="#viewing"><em>Your Virtual Devices</em></a> page of
- the AVD Manager, click <strong>Create Virtual Device</strong>.</li>
-
- <p>Alternatively,
- <a href="{@docRoot}training/basics/firstapp/running-app.html">run your
- app</a> from within Android Studio. In the <em>Select Deployment Target</em>
- dialog, click <strong>Create New Emulator</strong>.</p>
-
- <p>The <em>Select Hardware</em> page appears.</p>
- <img src="{@docRoot}images/tools/avd-hardwareprofile.png"
- alt="Hardware Profile page of the AVD Manager">
-
- <li>Select a hardware profile,
- and then click <strong>Next</strong>.</li>
-
- <p>If you don't see the hardware profile you want, you can
- <a href="#createhp">create</a>
- or <a href="#importexporthp">import</a> a hardware profile.</p>
-
- <p id="systemimagepage">The <em>System Image</em> page appears.</p>
- <img src="{@docRoot}images/tools/avd-systemimage.png"
- alt="System Image page of the AVD Manager">
-
- </li>
- <li>Select the system image for a particular API level, and then click
- <strong>Next</strong>.
- </li>
- <p>The <strong>Recommended</strong> tab lists recommended system images. The
- other tabs include a more complete list. The right pane describes the
- selected system image. x86 images run the fastest in the emulator.</p>
- <p>If you see <strong>Download</strong> next to the system image, you need
- to click it to download the system image. You must be connected to the
- internet to download it.</p>
-
- <p id="verifyconfigpage">The <em>Verify Configuration</em> page appears.</p>
- <img src="{@docRoot}images/tools/avd-verifyconfig.png"
- alt="Verify Configuration page of the AVD Manager">
-
- <li>Change <a href="#avdproperties">AVD properties</a> as needed,
- and then click <strong>Finish</strong>.
- <p>Click <strong>Show Advanced Settings</strong> to show more
- settings, such as the skin.</p>
- </li>
-
- <p>The new AVD appears in the <em>Your Virtual Devices</em> page or the
- <em>Select Deployment Target</em> dialog.</p>
-</ol>
-
-
- <p id="copyavd">To create an AVD starting with a copy:</p>
-
- <ol>
- <li>From the
- <a href="#viewing"><em>Your Virtual Devices</em></a> page of
- the AVD Manager, right-click an AVD and select
- <strong>Duplicate</strong>.</li>
-
- <p>Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>Duplicate</strong>.</p>
-
- <p>The <a href="#verifyconfigpage"><em>Verify Configuration</em></a>
- page appears.</p>
-
- <li>Click <strong>Change</strong> or <strong>Previous</strong> if you
- need to make changes on the
- <a href="#systemimagepage"><em>System Image</em></a> and
- <a href="#hardwareprofilepage"><em>Hardware Profile</em></a> pages.</li>
-
- <li>Make your changes, and then click <strong>Finish</strong>.</li>
-
- <p>The AVD appears in the <em>Your Virtual Devices</em> page.
-
-</ol>
-
-
-<h2 id="createhp">Creating a Hardware Profile</h2>
-
-<p>The AVD Manager provides predefined hardware profiles for common devices so
-you can easily add them to your AVD definitions. If
-you need to define a different device, you can create a new hardware profile.
-You can <a href="#newhp">define a new hardware profile</a> from the beginning,
-or <a href="#copyavd">copy a hardware profile</a> as a start. The preloaded
-hardware profiles aren't editable.</p>
-
-<p id="newhp">To create a new hardware profile from the beginning:</p>
-<ol>
- <li>In the <a href="#selecthardwarepage"><em>Select Hardware</em></a>
- page, click <strong>New Hardware Profile</strong>.</li>
-
- <li>In the <em>Configure Hardware Profile</em> page, change the
- <a href="#hpproperties">hardware profile properties</a> as
- needed.</li>
-
- <li>Click <strong>Finish</strong>.</li>
- <p>Your new hardware profile appears in the <em>Select Hardware</em> page.
- You can optionally <a href="#selecthardwarepage">create an AVD</a>
- that uses the hardware profile
- by clicking <strong>Next</strong>. Or, click <strong>Cancel</strong> to return
- to the <em>Your Virtual Devices</em> page or <em>Select Deployment Target</em>
- dialog.</p>
- </ol>
-
-<p id="copyhp">To create a hardware profile starting with a copy:</p>
-
- <ol>
- <li>In the <a href="#selecthardwarepage"><em>Select Hardware</em></a>
- page, select a hardware profile and click <strong>Clone Device</strong>.</li>
-
- <p>Or right-click a hardware profile and select <strong>Clone</strong>.</li>
-
- <li>In the <em>Configure Hardware Profile</em> page, change the
- <a href="#hpproperties">hardware profile properties</a> as
- needed.</li>
-
- <li>Click <strong>Finish</strong>.</li>
-
- <p>Your new hardware profile appears in the <em>Select Hardware</em> page.
- You can optionally <a href="#selecthardwarepage">create an AVD</a>
- that uses the hardware profile
- by clicking <strong>Next</strong>. Or, click <strong>Cancel</strong> to return
- to the <em>Your Virtual Devices</em> page or <em>Select Deployment Target</em>
- dialog.</p>
- </ol>
-
-
-<h2 id="workingavd">Working With Existing AVDs</h2>
-
- <p>From the <a href="#viewing"><em>Your Virtual Devices</em></a> page, you can
- perform the following operations on an existing AVD:</p>
- <ul>
- <li>To edit an AVD, click Edit
- <img src="{@docRoot}images/tools/studio-advmgr-actions-edit-icon.png"
- style="vertical-align:sub;margin:0;height:17px"> and
- <a href="#copyavd">make your changes</a>.</li>
- <li>To delete an AVD, right-click an AVD and select
- <strong>Delete</strong>. Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>Delete</strong>.</li>
- <li>To show the associated AVD <code>.ini</code> and
- <code>.img</code> files on disk, right-click an AVD and select
- <strong>Show on Disk</strong>. Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>Show on Disk</strong>.</li>
- <li> To view AVD configuration details that you can
- include in any bug reports to the Android Studio team, right-click an AVD and
- select <strong>View Details</strong>. Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>View Details</strong>.</li>
- </ul>
-
-
-<h2 id="workinghp">Working With Existing Hardware Profiles</h2>
-
-<p>From the <a href="#selecthardwarepage"><em>Select Hardware</em></a> page,
-you can
- perform the following operations on an existing hardware profile:</p>
- <ul>
- <li>To edit a hardware profile, select it and click
- <strong>Edit Device</strong>. Or right-click a hardware profile and select
- <strong>Edit</strong>. Next,
- <a href="#copyhp">make your changes</a>.</li>
-
- <li>To delete a hardware profile, right-click it and select
- <strong>Delete</strong>. </li>
- </ul>
- <p>You can't edit or delete the predefined hardware profiles.</p>
-
-<h2 id="emulator">Running and Stopping an Emulator, and Clearing Data</h2>
-
- <p>From the <a href="#viewing"><em>Your Virtual Devices</em></a> page, you can
- perform the following operations on an emulator:</p>
- <ul>
- <li>To run an emulator that uses an AVD, double-click the AVD. Or click Run
- <img src="{@docRoot}images/tools/as-avd-start.png"
- style="vertical-align:sub;margin:0;height:17px">.</li>
- <li>To stop a running emulator, right-click an AVD and select
- <strong>Stop</strong>. Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>Stop</strong>.</li>
- <li>To clear the data for an emulator, and return it to the same state as when
- it was first defined, right-click an AVD and select
- <strong>Wipe Data</strong>. Or click Menu
- <img src="{@docRoot}images/tools/studio-advmgr-actions-dropdown-icon.png"
- style="vertical-align:sub;margin:0;height:17px">
- and select <strong>Wipe Data</strong>.</li>
- </ul>
-
-<h2 id="importexporthp">Importing and Exporting Hardware Profiles</h2>
-
-<p>From the <a href="#selecthardwarepage"><em>Select Hardware</em></a> page,
-you can import and export hardware profiles:</p>
- <ul>
- <li>To import a hardware profile, click
- <strong>Import Hardware Profiles</strong> and select the XML file containing
- the definition on your computer.</li>
-
- <li>To export a hardware profile, right-click it and select
- <strong>Export</strong>. Specify the location where you want to store the
- XML file containing the definition.</i>
- </ul>
-
-<h2 id="hpproperties">Hardware Profile Properties</h2>
-
-<p>You can specify the following properties of hardware profiles in the
-<a href="#createhp"><em>Configure Hardware Profile</em></a> page. AVD
-configuration properties override hardware profile properties, and emulator
-properties that you set while the emulator is running override them both.</p>
-
-<p>The predefined hardware profiles included with the AVD Manager aren't
-editable. However, you can copy them and edit the copies.</p>
-
-
-<table>
- <tr>
- <th scope="col">Hardware Profile Property</th>
- <th scope="col">Description</th>
- </tr>
- <tr>
- <td>Device Name</td>
- <td>Name of the hardware profile. The name can contain uppercase or
- lowercase letters,
- numbers from 0 to 9, periods (.), underscores (_), and parentheses ( () ).
- The name of the file storing the hardware profile is derived from the
- hardware profile name.
- </td>
- </tr>
- <tr>
- <td>Device Type</td>
- <td>Select one of the following:
-<ul>
- <li> Phone/Tablet
- <li> Android Wear
- <li> Android TV
-</ul>
-</td>
- </tr>
-
- <tr>
- <td>Screen Size </td>
- <td>The physical size of the screen, in inches, measured at the diagonal.
- If the size is larger than your computer screen, it’s reduced in size at
- launch.</td>
- </tr>
- <tr>
- <td>Screen Resolution</td>
- <td>Type a width and height in pixels to specify the total number of pixels
- on the simulated screen.</td>
-
- </tr>
- <tr>
- <td>Round</td>
- <td>Select this option if the device has a round screen, such as an
- Android Wear device. </td>
- </tr>
- <tr>
- <td>Memory: RAM</td>
- <td>Type a RAM size for the device and select the units, one of B (byte),
- KB (kilobyte), MB (megabyte), GB (gigabyte), or TB (terabyte).</td>
- </tr>
-
- <tr>
- <td>Input: Has Hardware Buttons (Back/Home/Menu)</td>
- <td>Select this option if your device has hardware navigation buttons.
- Deselect it if these buttons are implemented in software only. If you
- select this option, the buttons won’t appear on the screen. You can use the
- emulator side panel to “press” the buttons, in either case.</td>
- </tr>
- <tr>
- <td>Input: Has Hardware Keyboard</td>
- <td>Select this option if your device has a hardware keyboard. Deselect it
- if it doesn’t. If you select this option, a keyboard won’t appear on the
- screen. You can use your computer keyboard to send keystrokes to the
- emulator, in either case.</td>
- </tr>
- <tr>
- <td>Navigation Style</td>
- <td><p>Select one of the following:</p>
-<ul>
- <li> None - No hardware controls. Navigation is through the software.
- <li> D-pad - Directional Pad support.
- <li> Trackball
- <li> Wheel
-</ul>
- <p>These options are for actual hardware controls on the device itself.
- However,
- the events sent to the device by an external controller are the same.</p>
-</td>
- </tr>
- <tr>
- <td>Supported Device States</td>
- <td><p>Select one or both options:</p>
-<ul>
- <li> Portrait - Oriented taller than wide.
- <li> Landscape - Oriented wider than tall.
-</ul>
-<p>If you select both, you can switch between orientations in the emulator.
-You must select at least one option to continue.</p></td>
- </tr>
- <tr>
- <td>Cameras</td>
- <td><p>Select one or both options:</p>
-<ul>
- <li> Back-Facing Camera - The lens faces away from the user.
- <li> Front-Facing Camera - The lens faces toward the user.
-</ul>
-<p>Later, you can use a webcam or a photo provided by the emulator to simulate
-taking a photo with the camera.</td>
- </tr>
-
- <tr>
- <td>Sensors: Accelerometer</td>
- <td>Select if the device has hardware that helps the device determine
- its orientation.</td>
- </tr>
- <tr>
- <td>Sensors: Gyroscope</td>
- <td>Select if the device has hardware that detects rotation or twist.
- In combination with an
- accelerometer, it can provide smoother orientation detection and support
- a six-axis orientation system.</td>
- </tr>
- <tr>
- <td>Sensors: GPS</td>
- <td>Select if the device has hardware that supports the Global Positioning
- System (GPS)
- satellite-based navigation system.</td>
- </tr>
- <tr>
- <td>Sensors: Proximity Sensor</td>
- <td>Select if the device has hardware that detects if the device is close
- to your face during a
- phone call to disable input from the screen.</td>
- </tr>
- <tr>
- <td>Default Skin</td>
- <td>Select a skin that controls what the device looks like when displayed
- in the
- emulator. Remember that specifying a screen size that's too small for the
- resolution can mean that the screen is cut off, so you can't see the whole
- screen. See
- <a href="{@docRoot}tools/devices/managing-avds.html#skins">Creating Emulator Skins</a>
- for more information.</td>
- </tr>
-</table>
-
-<h2 id="avdproperties">AVD Properties</h2>
-
-<p>You can specify the following properties for AVD configurations
-in the <a href="#verifyconfigpage"><em>Verify Configuration</em></a> page.
-The AVD configuration specifies the interaction between the development
-computer and the emulator, as well as properties you want to override in the
-hardware profile.</p>
-
-<p>AVD configuration properties override hardware profile properties,
-and emulator
-properties that you set while the emulator is running override them both.</p>
-
-<table>
- <tr>
- <th scope="col">AVD Property</th>
- <th scope="col">Description</th>
- </tr>
- <tr>
- <td>AVD Name</td>
- <td>Name of the AVD. The name can contain uppercase or
- lowercase letters,
- numbers from 0 to 9, periods (.), underscores (_), and parentheses ( () ).
- The name of the file storing the AVD configuration is derived from the AVD
- name.
- </td>
- </tr>
- <tr>
- <td>AVD ID (Advanced)</td>
- <td>The AVD filename is derived from the ID, and you can use the ID to
- refer to the AVD from the command line.</td>
- </tr>
- <tr>
- <td>Hardware Profile</td>
- <td>Click <strong>Change</strong> to select a different hardware profile in
- the <a href="#selecthardwarepage"><em>Select Hardware</em></a> page.</td>
- </tr>
- <tr>
- <td>System Image</td>
- <td>Click <strong>Change</strong> to select a different system image in the
- <a href="#systemimagepage"><em>System Image</em></a> page.
- An active internet connection is required to download a new image. </td>
- </tr>
-
- <tr>
- <td>Startup: Scale </td>
- <td>Select the initial size you want to use when the emulator launches.
- This size might be adjusted to a smaller size if it’s larger than the
- computer screen. The default is Auto (automatic).</td>
- </tr>
- <tr>
- <td>Startup: Orientation</td>
- <td><p>Select one option for the initial emulator orientation:</p>
-<ul>
- <li> Portrait - Oriented taller than wide.
- <li> Landscape - Oriented wider than tall.
-</ul>
-<p>An option is enabled only if it’s selected in the hardware profile. When
-running the AVD in the emulator, you can change the orientation if portrait and
-landscape are supported in the hardware profile.</p></td>
- </tr>
- <tr>
- <td>Camera (Advanced)</td>
- <td><p>Select one or both options:</p>
-<ul>
- <li> Front - The lens faces away from the user.
- <li> Back - The lens faces toward the user.
-</ul>
-<p>This option is available only if it's selected in the hardware profile; it's
-not available for Android Wear and Android TV.</p></td>
- </tr>
-
- <tr>
- <td>Network: Speed (Advanced)</td>
- <td><p>Select a network protocol to determine the speed of data transfer:
- </p>
- <ul>
- <li>GSM - Global System for Mobile Communications</li>
-<li>HSCSD - High-Speed Circuit-Switched Data</li>
-<li>GPRS - Generic Packet Radio Service</li>
-<li>EDGE - Enhanced Data rates for GSM Evolution</li>
-<li>UMTS - Universal Mobile Telecommunications System</li>
-<li>HSPDA - High-Speed Downlink Packet Access</li>
-<li>Full (default) - Transfer data as quickly as your computer allows.</li>
-</ul>
-</td>
- </tr>
- <tr>
- <td>Network: Latency (Advanced)</td>
- <td>Select a network protocol to set how much time (delay) it takes for the
- protocol to transfer a data packet from one point to another point.</td>
- </tr>
-
- <tr>
- <td>Emulated Performance: Graphics</td>
- <td><p>Select how graphics are rendered in the emulator:</p>
- <ul>
- <li>Hardware - Use your computer graphics card for faster rendering.</li>
- <li>Software - Emulate the graphics in software, which is useful if you're
- having a problem with rendering in your graphics card.</li>
- <li>Auto - Let the emulator decide the best option based on your graphics
- card.</li>
- </td>
- </tr>
- <tr>
- <td>Multi-Core CPU (Advanced)</td>
- <td>Select the number of processor cores on your computer that you’d like
- to use for the emulator. Using more processor cores speeds up the emulator.
- </td>
- </tr>
-
- <tr>
- <td>Memory and Storage: RAM</td>
- <td>The amount of RAM on the device. This value is set by the hardware
- manufacturer, but you can override it, if needed, such as for faster
- emulator operation. Increasing the size uses more resources on your
- computer. Type a RAM size and select the
- units, one of B (byte), KB (kilobyte), MB (megabyte), GB (gigabyte), or
- TB (terabyte).</td>
- </tr>
- <tr>
- <td>Memory and Storage: VM Heap</td>
- <td>The VM heap size. This value is set by the hardware
- manufacturer, but you can override it, if needed. Type a heap size and
- select the
- units, one of B (byte), KB (kilobyte), MB (megabyte), GB (gigabyte), or
- TB (terabyte). For more information on Android VMs, see
- <a href="{@docRoot}tools/help/am-memory.html#vm">Memory Management for
- Different Virtual Machines</a>.</td>
- </tr>
- <tr>
- <td>Memory and Storage: Internal Storage</td>
- <td>The amount of nonremovable memory space available on the device. This
- value is set by the hardware
- manufacturer, but you can override it, if needed. Type a size and select the
- units, one of B (byte), KB (kilobyte), MB (megabyte), GB (gigabyte), or
- TB (terabyte).</td>
- </tr>
- <tr>
- <td>Memory and Storage: SD Card</td>
- <td>The amount of removable memory space available to store data on the
- device. To use a virtual SD card managed by Android Studio, select
- <strong>Studio</strong>, type a size, and select the
- units, one of B (byte), KB (kilobyte), MB (megabyte), GB (gigabyte), or
- TB (terabyte). A minimum of 100 MB is recommended to use the camera. To
- manage the space in a file, select <strong>External File</strong> and
- click <strong>...</strong> to specify the file and location. For more
- information, see <a href="{@docRoot}tools/help/mksdcard.html">mksdcard</a>.
- </td>
- </tr>
-
- <tr>
- <td>Device Frame: Enable Device Frame</td>
- <td>Select to enable a frame around the emulator window that mimics the
- look of a real device.</td>
- </tr>
- <tr>
- <td>Custom Skin Definition (Advanced)</td>
- <td>Select a skin that controls what the device looks like when displayed in
- the emulator. Remember that specifying a screen size that's too small for
- the resolution can mean that the screen is cut off, so you can't see the
- whole screen. See
- <a href="{@docRoot}tools/devices/managing-avds.html#skins">Creating Emulator Skins</a>
- for more information.</td>
- </tr>
- <tr>
- <td>Keyboard: Enable Keyboard Input (Advanced)</td>
- <td>Select this option if you want to use your hardware keyboard to interact
- with the emulator. It's disabled for Android Wear and Android TV.</td>
- </tr>
-</table>
-
-
-<h2 id="skins">Creating Emulator Skins</h2>
-
-<p>An Android emulator skin is a collection of files that define the visual
-and control elements of
-an emulator display. If the skin definitions available in the AVD settings
-don't meet your requirements,
-you can create your own custom skin definition, and then apply it to your AVD.
-</p>
-
-<p>Each emulator skin contains:</p>
- <ul>
- <li>A <code>hardware.ini</code> file</li>
- <li>Layout files for supported orientations (landscape, portrait) and
- physical configuration</li>
- <li>Image files for display elements, such as background, keys and
- buttons</li>
- </ul>
-<p>To create and use a custom skin:</p>
- <ol>
- <li>Create a new directory where you will save your skin configuration
- files. </li>
- <li>Define the visual appearance of the skin in a text file named
- <code>layout</code>. This file defines many characteristics of the skin,
- such as the
- size and image assets for specific buttons. For example:
-<pre class="no-prettyprint">
-parts {
- device {
- display {
- width 320
- height 480
- x 0
- y 0
- }
- }
-
- portrait {
- background {
- image background_port.png
- }
-
- buttons {
- power {
- image button_vertical.png
- x 1229
- y 616
- }
- }
- }
- ...
-}
-</pre></li>
-
- <li>Add the bitmap files of the device images in the same directory.</li>
- <li>Specify additional hardware-specific device configurations in a
- <code>hardware.ini</code>
- file for the device settings, such as <code>hw.keyboard</code> and
- <code>hw.lcd.density</code>.</li>
- <li>Archive the files in the skin folder and select the archive file as a
- custom skin.</li>
-</ol>
-
-<p>For more detailed information about creating emulator skins, see the
-<a href="https://android.googlesource.com/platform/external/qemu/+/emu-master-dev/docs/ANDROID-SKIN-FILES.TXT"
->Android Emulator Skin File Specification</a> in the tools source code.</p>
-
-
-
+++ /dev/null
-page.title=Extras
-page.noplus=1
-@jd:body
-
-<p>SDK extras add functionality to your development environment. You can download all of the SDK extras into your development environment using the SDK Manager. </p>
+++ /dev/null
-page.title=OEM USB Drivers
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#InstallingDriver">Installing a USB Driver</a>
- <ol>
- <li><a href="#Win7">Windows 7</a></li>
- <li><a href="#WinVista">Windows Vista</a></li>
- </ol>
- </li>
- <li><a href="#Drivers">OEM Drivers</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/device.html">Using Hardware Devices</a></li>
- <li><a href="{@docRoot}sdk/win-usb.html">Google USB Driver</a></li>
- </ol>
-</div>
-</div>
-
-<p>If you are developing on Windows and would like to connect an Android-powered device
-to test your applications, then you need to install the appropriate USB driver. This document
-provides links to the web sites for several original equipment manufacturers (OEMs),
-where you can download the appropriate USB driver for your device. However, this list is
-not exhaustive for all available Android-powered devices.</p>
-
-<p>If you're developing on Mac OS X or Linux, then you probably don't need to install a USB driver.
-To start developing with your device, read <a
-href="{@docRoot}tools/device.html">Using Hardware Devices</a>.</p>
-
-<p>The Google USB Driver is <strong>required for Windows only</strong> in order to perform
-<a href="{@docRoot}tools/help/adb.html">adb</a> debugging with any of
-the <strong>Google Nexus devices</strong>. The one exception is the
-Galaxy Nexus: the driver for Galaxy Nexus is distributed by <a
-href="http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN">Samsung</a>
-(listed as model GT-I9250TSGGEN).</p>
-
-
-
-<h2 id="InstallingDriver">Installing a USB Driver</h2>
-
-<p>First, find the appropriate driver for your device from the <a href="#Drivers">OEM drivers</a>
-table below.</p>
-
-<p>Once you've downloaded your USB driver, follow the instructions below to install or upgrade the
-driver, based on your version of Windows and whether you're installing for the first time
-or upgrading an existing driver.</p>
-
-<p class="note"><strong>Tip:</strong> When you finish the USB driver installation,
-see <a
-href="{@docRoot}tools/device.html">Using Hardware Devices</a> for
-other important information about using an Android-powered device for
-development.</p>
-
-<ol class="nolist">
- <li><a href="#Win7">Windows 7</a></li>
- <li><a href="#WinVista">Windows Vista</a></li>
-</ol>
-
-
-<p class="caution"><strong>Caution:</strong>
-You may make changes to <code>android_winusb.inf</code> file found inside
-<code>usb_driver\</code> (for example, to add support for other devices),
-however, this will lead to security warnings when you install or upgrade the
-driver. Making any other changes to the driver files may break the installation
-process.</p>
-
-
-<h3 id="Win7">Windows 7</h3>
-
-
-<p>To install the Android USB driver on Windows 7 for the first time:</p>
-<ol>
- <li>Connect your Android-powered device to your computer's USB port.</li>
- <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer,
- and select <strong>Manage</strong>.</li>
- <li>Select <strong>Devices</strong> in the left pane.</li>
- <li>Locate and expand <em>Other device</em> in the right pane.</li>
- <li>Right-click the device name (such as <em>Nexus S</em>) and select <strong>Update
- Driver Software</strong>.
- This will launch the Hardware Update Wizard.</li>
- <li>Select <strong>Browse my computer for driver software</strong> and click
- <strong>Next</strong>.</li>
- <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB
-Driver is located in {@code <sdk>\extras\google\usb_driver\}.)</li>
- <li>Click <strong>Next</strong> to install the driver.</li>
-</ol>
-
-<p>Or, to <em>upgrade</em> an existing Android USB driver on Windows 7 with the new
-driver:</p>
-
-<ol>
- <li>Connect your Android-powered device to your computer's USB port.</li>
- <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer,
- and select <strong>Manage</strong>.</li>
- <li>Select <strong>Device Manager</strong> in the left pane of the Computer Management
- window.</li>
- <li>Locate and expand <em>Android Phone</em> in the right pane.</li>
- <li>Right-click on <em>Android Composite ADB Interface</em> and select <strong>Update
- Driver</strong>.
- This will launch the Hardware Update Wizard.</li>
- <li>Select <strong>Install from a list or specific location</strong> and click
- <strong>Next</strong>.</li>
- <li>Select <strong>Search for the best driver in these locations</strong>; un-check
-<strong>Search removable media</strong>; and check <strong>Include this location in the
-search</strong>.</li>
- <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB
-Driver is located in {@code <sdk>\extras\google\usb_driver\}.)</li>
- <li>Click <strong>Next</strong> to upgrade the driver.</li>
-</ol>
-
-
-
-<h3 id="WinVista">Windows Vista</h3>
-
-<p>To install the Android USB driver on Windows Vista for the first time:</p>
-
-<ol>
- <li>Connect your Android-powered device to your computer's USB port. Windows
- will detect the device and launch the Found New Hardware wizard.</li>
- <li>Select <strong>Locate and install driver software</strong>.</li>
- <li>Select <strong>Don't search online</strong>.</li>
- <li>Select <strong>I don't have the disk. Show me other options</strong>.</li>
- <li>Select <strong>Browse my computer for driver software</strong>.</li>
- <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB
-Driver is located in {@code <sdk>\extras\google\usb_driver\}.) As long as you specified the
-exact location of the
- installation package, you may leave <strong>Include subfolders</strong> checked or
- unchecked—it doesn't matter.</li>
- <li>Click <strong>Next</strong>. Vista may prompt you to confirm the privilege elevation
- required for driver installation. Confirm it.</li>
- <li>When Vista asks if you'd like to install the Google ADB Interface device,
- click <strong>Install</strong> to install the driver.</li>
-</ol>
-
-<p>Or, to <em>upgrade</em> an existing Android USB driver on Windows Vista with the new
-driver:</p>
-
-<ol>
- <li>Connect your Android-powered device to your computer's USB port.</li>
- <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer,
- and select <strong>Manage</strong>.</li>
- <li>Select <strong>Device Manager</strong> in the left pane.</li>
- <li>Locate and expand <em>ADB Interface</em> in the right pane.</li>
- <li>Right-click on <em>Android Composite ADB Interface</em>, and select <strong>Update
- Driver Software</strong>.</li>
- <li>When Vista starts updating the driver, a prompt will ask how you want to
- search for the driver
- software. Select <strong>Browse my computer for driver software</strong>.</li>
- <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB
-Driver is located in {@code <sdk>\extras\google\usb_driver\}.) As long as you specified the
-exact location of the
- installation package, you may leave <strong>Include subfolders</strong> checked or
- unchecked—it doesn't matter.</li>
- <li>Click <strong>Next</strong>. Vista might prompt you to confirm the privilege elevation
- required for driver installation. Confirm it.</li>
- <li>When Vista asks if you'd like to install the Google ADB Interface device,
- click <strong>Install</strong> to upgrade the driver.</li>
-</ol>
-
-
-<h2 id="Drivers">OEM Drivers</h2>
-
-
-<table>
-<tr>
- <th>OEM</th>
- <th>Driver URL</th></tr>
- <tr>
- <td>
- Acer
- </td>
- <td>
- <a href=
- "http://www.acer.com/worldwide/support/mobile.html">http://www.acer.com/worldwide/support/mobile.html</a>
- </td>
- </tr>
-
- <tr>
- <td style="font-variant:small-caps">
- alcatel one touch
- </td>
- <td>
- <a href=
- "http://www.alcatelonetouch.com/global-en/support/">http://www.alcatelonetouch.com/global-en/support/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Asus
- </td>
- <td>
- <a href="http://support.asus.com/download/">http://support.asus.com/download/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Blackberry
- </td>
- <td>
- <a href=
- "https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608">
- https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Dell
- </td>
- <td>
- <a href=
- "http://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml">
- http://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Fujitsu
- </td>
- <td>
- <a href=
- "http://www.fmworld.net/product/phone/sp/android/develop/">http://www.fmworld.net/product/phone/sp/android/develop/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Hisense
- </td>
- <td>
- <a href=
- "http://app.hismarttv.com/dss/resourcecontent.do?method=viewResourceDetail&resourceId=16&type=5">
- http://app.hismarttv.com/dss/resourcecontent.do?method=viewResourceDetail&resourceId=16&type=5</a>
- </td>
- </tr>
-
- <tr>
- <td>
- HTC
- </td>
- <td>
- <a href="http://www.htc.com">http://www.htc.com</a><br>
- Click on the support tab to select your products/device. Different regions will have
- different links.
- </td>
- </tr>
-
- <tr>
- <td>
- Huawei
- </td>
- <td>
- <a href=
- "http://consumer.huawei.com/en/support/index.htm">http://consumer.huawei.com/en/support/index.htm</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Intel
- </td>
- <td>
- <a href="http://www.intel.com/software/android">http://www.intel.com/software/android</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Kyocera
- </td>
- <td>
- <a href=
- "http://www.kyocera-wireless.com/support/phone_drivers.htm">http://www.kyocera-wireless.com/support/phone_drivers.htm</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Lenovo
- </td>
- <td>
- <a href=
- "http://support.lenovo.com/us/en/GlobalProductSelector">http://support.lenovo.com/us/en/GlobalProductSelector</a>
- </td>
- </tr>
-
- <tr>
- <td>
- LGE
- </td>
- <td>
- <a href=
- "http://www.lg.com/us/support/software-firmware">http://www.lg.com/us/support/software-firmware</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Motorola
- </td>
- <td>
- <a href=
- "https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481">https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- MTK
- </td>
- <td>
- <a href=
- "http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip">http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip</a>
- (ZIP download)
- </td>
- </tr>
-
- <tr>
- <td>
- Oppo
- </td>
- <td>
- <a href=
- "http://www.oppo.com/index.php?q=software/view&sw_id=631">http://www.oppo.com/index.php?q=software/view&sw_id=631</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Pegatron
- </td>
- <td>
- <a href=
- "http://www.pegatroncorp.com/download/New_Duke_PC_Driver_0705.zip">http://www.pegatroncorp.com/download/New_Duke_PC_Driver_0705.zip</a>
- (ZIP download)
- </td>
- </tr>
-
- <tr>
- <td>
- Samsung
- </td>
- <td>
- <a href=
- "http://www.samsung.com/us/support/downloads">http://www.samsung.com/us/support/downloads</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Sharp
- </td>
- <td>
- <a href="http://k-tai.sharp.co.jp/support/">http://k-tai.sharp.co.jp/support/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Sony Mobile Communications
- </td>
- <td>
- <a href=
- "http://developer.sonymobile.com/downloads/drivers/">http://developer.sonymobile.com/downloads/drivers/</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Toshiba
- </td>
- <td>
- <a href=
- "http://support.toshiba.com/sscontent?docId=4001814">http://support.toshiba.com/sscontent?docId=4001814</a>
- </td>
- </tr>
-
- <tr>
- <td>
- Xiaomi
- </td>
- <td>
- <a href=
- "http://www.xiaomi.com/c/driver/index.html">http://www.xiaomi.com/c/driver/index.html</a>
- </td>
- </tr>
-
- <tr>
- <td>
- ZTE
- </td>
- <td>
- <a href=
- "http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442">http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442</a>
- </td>
- </tr>
-</table>
\ No newline at end of file
+++ /dev/null
-page.title=MonkeyDevice
-parent.title=monkeyrunner
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>
- A monkeyrunner class that represents a device or emulator accessible by the workstation running
-<code><a href="{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a></code>.
-</p>
-<p>
- This class is used to control an Android device or emulator. The methods send UI events,
- retrieve information, install and remove applications, and run applications.
-</p>
-<p>
- You normally do not have to create an instance of <code>MonkeyDevice</code>. Instead, you
- use
-<code><a href="{@docRoot}tools/help/MonkeyRunner.html#waitForConnection">
-MonkeyRunner.waitForConnection()</a></code> to create a new object from a connection to a device or
-emulator. For example, instead of
-using:</p>
-<pre>
-newdevice = MonkeyDevice()
-</pre>
-<p>
- you would use:
-</p>
-<pre>
-newdevice = MonkeyRunner.waitForConnection()
-</pre>
-<h2>Summary</h2>
- <table id="constants" class="jd-sumtable" style="background-color: white;">
- <tr>
- <th colspan="12" style="background-color: #E2E2E2">Constants</th>
- </tr>
- <tr class="api" style="background-color: white;">
- <td class="jd-typecol"><em>string</em></td>
- <td class="jd-linkcol"><a href="#ACTION_DOWN">DOWN</a></td>
- <td class="jd-descrcol" width="100%">
- Use this with the <code>type</code> argument of
- <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a>
- </code>
- to send a DOWN event.
- </td>
- </tr>
- <tr class="api" style="background-color: white;">
- <td class="jd-typecol"><em>string</em></td>
- <td class="jd-linkcol"><a href="#ACTION_UP">UP</a></td>
- <td class="jd-descrcol" width="100%">
- Use this with the <code>type</code> argument of
- <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a>
- </code>
- to send an UP event.
- </td>
- </tr>
- <tr class="api" style="background-color: white;">
- <td class="jd-typecol"><em>string</em></td>
- <td class="jd-linkcol"><a href="#ACTION_DOWN_AND_UP">DOWN_AND_UP</a></td>
- <td class="jd-descrcol" width="100%">
- Use this with the <code>type</code> argument of
- <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a>
- </code>
- to send a DOWN event immediately followed by an UP event.
- </td>
- </tr>
- </table>
-<table id="pubmethods" class="jd-sumtable">
- <tr>
- <th colspan="12" style="background-color: #E2E2E2">Methods</th>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#broadcastIntent">broadcastIntent</a>
- </span>
- (<em>string</em> uri,
- <em>string</em> action,
- <em>string</em> data,
- <em>string</em> mimetype,
- <em>iterable</em> categories
- <em>dictionary</em> extras,
- <em>component</em> component,
- <em>iterable</em> flags)
- </nobr>
- <div class="jd-descrdiv">
- Broadcasts an Intent to this device, as if the Intent were coming from an
- application.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#drag">drag</a>
- </span>
- (<em>tuple</em> start,
- <em>tuple</em> end,
- <em>float</em> duration,
- <em>integer</em> steps)
- </nobr>
- <div class="jd-descrdiv">
- Simulates a drag gesture (touch, hold, and move) on this device's screen.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>object</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#getProperty">getProperty</a>
- </span>
- (<em>string</em> key)
- </nobr>
- <div class="jd-descrdiv">
- Given the name of a system environment variable, returns its value for this device.
- The available variable names are listed in the <a href="#getProperty">
- detailed description</a> of this method.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>object</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#getSystemProperty">getSystemProperty</a>
- </span>
- (<em>string</em> key)
- </nobr>
- <div class="jd-descrdiv">
-. The API equivalent of <code>adb shell getprop <key>. This is provided for use
- by platform developers.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#installPackage">installPackage</a>
- </span>
- (<em>string</em> path)
- </nobr>
- <div class="jd-descrdiv">
- Installs the Android application or test package contained in packageFile onto this
- device. If the application or test package is already installed, it is replaced.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>dictionary</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#instrument">instrument</a>
- </span>
- (<em>string</em> className,
- <em>dictionary</em> args)
- </nobr>
- <div class="jd-descrdiv">
- Runs the specified component under Android instrumentation, and returns the results
- in a dictionary whose exact format is dictated by the component being run. The
- component must already be present on this device.
- </div>
- </td>
- </tr>
- <tr class="api">
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#press">press</a>
- </span>
- (<em>string</em> name,
- <em>dictionary</em> type)
- </nobr>
- <div class="jd-descrdiv">
- Sends the key event specified by type to the key specified by
- keycode.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#reboot">reboot</a>
- </span>
- (<em>string</em> into)
- </nobr>
- <div class="jd-descrdiv">
- Reboots this device into the bootloader specified by bootloadType.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#removePackage">removePackage</a>
- </span>
- (<em>string</em> package)
- </nobr>
- <div class="jd-descrdiv">
- Deletes the specified package from this device, including its data and cache.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>object</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#shell">shell</a>
- </span>
- (<em>string</em> cmd)
- </nobr>
- <div class="jd-descrdiv">
- Executes an <code>adb</code> shell command and returns the result, if any.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#startActivity">startActivity</a>
- </span>
- (<em>string</em> uri,
- <em>string</em> action,
- <em>string</em> data,
- <em>string</em> mimetype,
- <em>iterable</em> categories
- <em>dictionary</em> extras,
- <em>component</em> component,
- <em>flags</em>)
- </nobr>
- <div class="jd-descrdiv">
- Starts an Activity on this device by sending an Intent constructed from the
- supplied arguments.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">
- MonkeyImage
- </a>
- </code>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#takeSnapshot">takeSnapshot</a>()
- </span>
- </nobr>
- <div class="jd-descrdiv">
- Captures the entire screen buffer of this device, yielding a
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">
- MonkeyImage
- </a>
- </code> object containing a screen capture of the current display.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#touch">touch</a>
- </span>
- (<em>integer</em> x,
- <em>integer</em> y,
- <em>integer</em> type)
- </nobr>
- <div class="jd-descrdiv">
- Sends a touch event specified by type to the screen location specified
- by x and y.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#touch">type</a>
- </span>
- (<em>string</em> message)
- </nobr>
- <div class="jd-descrdiv">
- Sends the characters contained in message to this device, as if they
- had been typed on the device's keyboard. This is equivalent to calling
- <code><a href="#press">press()</a></code> for each keycode in <code>message</code>
- using the key event type <code><a href="#ACTION_DOWN_AND_UP"></a>DOWN_AND_UP</code>.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#touch">wake</a>
- </span>
- ()
- </nobr>
- <div class="jd-descrdiv">
- Wakes the screen of this device.
- </div>
- </td>
- </tr>
-</table>
-<!-- ========= ENUM CONSTANTS DETAIL ======== -->
-<h2>Constants</h2>
-<A NAME="ACTION_DOWN"></a>
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- DOWN
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- <code><a href="#press">press()</a></code> or
- <code><a href="#press">touch()</a></code> value.
- Specifies that a DOWN event type should be sent to the device, corresponding to
- pressing down on a key or touching the screen.
- </p>
- </div>
- </div>
-</div>
-<A NAME="ACTION_UP"></A>
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- UP
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- <code><a href="#press">press()</a></code> or
- <code><a href="#press">touch()</a></code> value.
- Specifies that an UP event type should be sent to the device, corresponding to
- releasing a key or lifting up from the screen.
- </p>
- </div>
- </div>
-</div>
-<A NAME="ACTION_DOWN_AND_UP"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- DOWN_AND_UP
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- <code><a href="#press">press()</a></code>,
- <code><a href="#press">touch()</a></code> or
- <code><a href="#type">type()</a></code> value.
- Specifies that a DOWN event type followed by an UP event type should be sent to the
- device, corresponding to typing a key or clicking the screen.
- </p>
- </div>
- </div>
-</div>
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methods -->
-<h2>Public Methods</h2>
-<A NAME="broadcastIntent"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">broadcastIntent</span>
- <span class="normal">
- (
- <em>string</em> uri,
- <em>string</em> action,
- <em>string</em> data,
- <em>string</em> mimetype,
- <em>iterable</em> categories
- <em>dictionary</em> extras,
- <em>component</em> component,
- <em>iterable</em> flags)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Broadcasts an Intent to this device, as if the Intent were coming from an
- application. See {@link android.content.Intent Intent} for more information about the
- arguments.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>uri</th>
- <td>
- The URI for the Intent.
- (see {@link android.content.Intent#setData(android.net.Uri) Intent.setData()}).
- </td>
- </tr>
- <tr>
- <th>action</th>
- <td>
- The action for this Intent
- (see {@link android.content.Intent#setAction(java.lang.String) Intent.setAction()}).
- </td>
- </tr>
- <tr>
- <th>data</th>
- <td>
- The data URI for this Intent
- (see {@link android.content.Intent#setData(android.net.Uri) Intent.setData()}).
- </td>
- </tr>
- <tr>
- <th>mimetype</th>
- <td>
- The MIME type for the Intent
- (see {@link android.content.Intent#setType(java.lang.String) Intent.setType()}).
- </td>
- </tr>
- <tr>
- <th>categories</th>
- <td>
- An iterable data structure containing strings that define categories for this
- Intent
- (see
- {@link android.content.Intent#addCategory(java.lang.String) Intent.addCategory()}).
- </td>
- </tr>
- <tr>
- <th>extras</th>
- <td>
- A dictionary of extra data for this Intent
- (see {@link android.content.Intent#putExtra(java.lang.String,java.lang.String)
- Intent.putExtra()}
- for an example).
- <p>
- The key for each dictionary item should be a <em>string</em>. The item's value
- can be any simple or structured data type.
- </p>
- </td>
- </tr>
- <tr>
- <th>component</th>
- <td>
- The component for this Intent (see {@link android.content.ComponentName}).
- Using this argument will direct the Intent to a specific class within a specific
- Android package.
- </td>
- </tr>
- <tr>
- <th>flags</th>
- <td>
- An iterable data structure containing flags that control how the Intent is handled
- (see {@link android.content.Intent#setFlags(int) Intent.setFlags()}).
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="drag"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">drag</span>
- <span class="normal">
- (
- <em>tuple</em> start,
- <em>tuple</em> end,
- <em>float</em> duration,
- <em>integer</em> steps)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Simulates a drag gesture (touch, hold, and move) on this device's screen.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>start</th>
- <td>
- The starting point of the drag gesture, in the form of a <em>tuple</em>
- (x,y) where x and y are <em>integers</em>.
- </td>
- </tr>
- <tr>
- <th>end</th>
- <td>
- The end point of the drag gesture, in the form of a <em>tuple</em> (x,y)
- where x and y are <em>integers</em>.
- </td>
- </tr>
- <tr>
- <th>duration</th>
- <td>The duration of the drag gesture in seconds. The default is 1.0 seconds.</td>
- </tr>
- <tr>
- <th>steps</th>
- <td>The number of steps to take when interpolating points. The default is 10.</td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="getProperty"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>object</em>
- </span>
- <span class="sympad">getProperty</span>
- <span class="normal">
- (<em>string</em> key)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Given the name of a system environment variable, returns its value for this device.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>key</th>
- <td>
- The name of the system environment variable. The available variable names are listed in
- <a href="#table1">Table 1. Property variable names</a> at the end of this topic.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- The value of the variable. The data format varies according to the variable requested.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="getSystemProperty"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>object</em>
- </span>
- <span class="sympad">getSystemProperty</span>
- <span class="normal">
- (<em>string</em> key)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Synonym for <code><a href="#getProperty">getProperty()</a></code>.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>key</th>
- <td>
- The name of the system environment variable. The available variable names are listed in
- <a href="#table1">Table 1. Property Variable Names</a>.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- The value of the variable. The data format varies according to the variable requested.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="installPackage"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">installPackage</span>
- <span class="normal">
- (<em>string</em> path)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Installs the Android application or test package contained in packageFile
- onto this device. If the application or test package is already installed, it is
- replaced.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>path</th>
- <td>
- The fully-qualified path and filename of the <code>.apk</code> file to install.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="instrument"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>dictionary</em>
- </span>
- <span class="sympad">instrument</span>
- <span class="normal">
- (
- <em>string</em> className,
- <em>dictionary</em> args)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Runs the specified component with Android instrumentation, and returns the results
- in a dictionary whose exact format is dictated by the component being run. The
- component must already be present on this device.
- </p>
- <p>
- Use this method to start a test case that uses one of Android's test case classes.
- See <a href="{@docRoot}tools/testing/testing_android.html">Testing
- Fundamentals</a> to learn more about unit testing with the Android testing
- framework.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>className</th>
- <td>
- The name of an Android component that is already installed on this device, in the
- standard form packagename/classname, where packagename is the
- Android package name of a <code>.apk</code> file on this device, and
- classname is the class name of an Android component (Activity,
- ContentProvider, Service, or BroadcastReceiver) in that file. Both
- packagename and classname must be fully qualified. See
- {@link android.content.ComponentName} for more details.
- </td>
- </tr>
- <tr>
- <th>args</th>
- <td>
- A dictionary containing flags and their values. These are passed to the component as it
- is started. If the flag does not take a value, set its dictionary value to an empty
- string.
- </td>
- </tr>
- </table>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- <p>
- A dictionary containing the component's output. The contents of the dictionary
- are defined by the component itself.
- </p>
- <p>
- If you use {@link android.test.InstrumentationTestRunner} as the class name in
- the componentName argument, then the result dictionary contains
- the single key "stream". The value of "stream" is a <em>string</em> containing
- the test output, as if <code>InstrumentationTestRunner</code> was run from the
- command line. The format of this output is described in
- <a href="{@docRoot}tools/testing/testing_otheride.html">
- Testing in Other IDEs</a>.
- </p>
- </li>
- </ul>
- </div>
- </div>
- </div>
-</div>
-<A NAME="press"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">press</span>
- <span class="normal">
- (<em>string</em> name,
- <em>integer</em> type)
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Sends the key event specified by <code>type</code> to the key specified by
- <code>keycode</code>.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>name</th>
- <td>
- The name of the keycode to send. See {@link android.view.KeyEvent} for a list of
- keycode names. Use the keycode name, not its integer value.
- </td>
- </tr>
- <tr>
- <th>type</th>
- <td>
- The type of key event to send. The allowed values are <code><a href="#ACTION_DOWN">
- DOWN</a></code>, <code><a href="#ACTION_UP">UP</a></code>, and
- <code><a href="#ACTION_DOWN_AND_UP">DOWN_AND_UP</a></code>.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="reboot"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">reboot</span>
- <span class="normal">
- (<em>string</em> bootloadType)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Reboots this device into the bootloader specified by <code>bootloadType</code>.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>into</th>
- <td>
- The type of bootloader to reboot into. The allowed values are
- "bootloader", "recovery", or "None".
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="removePackage"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">removePackage</span>
- <span class="normal">
- (<em>string</em> package)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Deletes the specified package from this device, including its data and cache.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>package</th>
- <td>
- The Android package name of an <code>.apk</code> file on this device.
- </td>
- </table>
- </div>
- </div>
-</div>
-<A NAME="shell"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>object</em>
- </span>
- <span class="sympad">shell</span>
- <span class="normal">
- (<em>string</em> cmd)
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Executes an <code>adb</code> shell command and returns the result, if any.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>cmd</th>
- <td>
- The command to execute in the <code>adb</code> shell. The form of these commands is
- described in the topic <a href="{@docRoot}tools/help/adb.html">Android
- Debug Bridge</a>.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- The results of the command, if any. The format of the results is determined by the
- command.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="startActivity"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">startActivity</span>
- <span class="normal">
- (
- <em>string</em> uri,
- <em>string</em> action,
- <em>string</em> data,
- <em>string</em> mimetype,
- <em>iterable</em> categories
- <em>dictionary</em> extras,
- <em>component</em> component,
- <em>iterable</em> flags)
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Starts an Activity on this device by sending an Intent constructed from the
- supplied arguments.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>uri</th>
- <td>
- The URI for the Intent.
- (see {@link android.content.Intent#setData(android.net.Uri) Intent.setData()}).
- </td>
- </tr>
- <tr>
- <th>action</th>
- <td>
- The action for the Intent
- (see {@link android.content.Intent#setAction(java.lang.String) Intent.setAction()}).
- </td>
- </tr>
- <tr>
- <th>data</th>
- <td>
- The data URI for the Intent
- (see {@link android.content.Intent#setData(android.net.Uri) Intent.setData()}).
- </td>
- </tr>
- <tr>
- <th>mimetype</th>
- <td>
- The MIME type for the Intent
- (see {@link android.content.Intent#setType(java.lang.String) Intent.setType()}).
- </td>
- </tr>
- <tr>
- <th>categories</th>
- <td>
- An iterable data structure containing strings that define categories for the
- Intent
- (see
- {@link android.content.Intent#addCategory(java.lang.String) Intent.addCategory()}).
- </td>
- </tr>
- <tr>
- <th>extras</th>
- <td>
- A dictionary of extra data for the Intent
- (see
- {@link android.content.Intent#putExtra(java.lang.String,java.lang.String)
- Intent.putExtra()}
- for an example).
- <p>
- The key for each dictionary item should be a <em>string</em>. The item's value
- can be any simple or structured data type.
- </p>
- </td>
- </tr>
- <tr>
- <th>component</th>
- <td>
- The component for the Intent
- (see {@link android.content.ComponentName}). Using this argument will direct the
- Intent to a specific class within a specific Android package.
- </td>
- </tr>
- <tr>
- <th>flags</th>
- <td>
- An iterable data structure containing flags that control how the Intent is handled
- (see {@link android.content.Intent#setFlags(int) Intent.setFlags()}).
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="takeSnapshot"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">
- MonkeyImage
- </a>
- </code>
- </span>
- <span class="sympad">takeSnapshot</span>
- <span class="normal">
- ()
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Captures the entire screen buffer of this device, yielding a
- screen capture of the current display.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- A <a href="{@docRoot}tools/help/MonkeyImage.html">
- MonkeyImage</a> object containing the image of the current display.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="touch"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">touch</span>
- <span class="normal">
- (
- <em>integer</em> x,
- <em>integer</em> y,
- <em>string</em> type)
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Sends a touch event specified by type to the screen location specified
- by x and y.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>x</th>
- <td>
- The horizontal position of the touch in actual device pixels, starting from the left of
- the screen in its current orientation.
- </td>
- </tr>
- <tr>
- <th>y</th>
- <td>
- The vertical position of the touch in actual device pixels, starting from the top of
- the screen in its current orientation.
- </td>
- </tr>
- <tr>
- <th>type</th>
- <td>
- The type of key event to send. The allowed values are <code><a href="#ACTION_DOWN">
- DOWN</a></code>, <code><a href="#ACTION_UP">UP</a></code>, and
- <code><a href="#ACTION_DOWN_AND_UP">DOWN_AND_UP</a></code>.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="type"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">type</span>
- <span class="normal">
- (<em>string</em> message)
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Sends the characters contained in message to this device, as if they
- had been typed on the device's keyboard. This is equivalent to calling
- <code><a href="#press">press()</a></code> for each keycode in <code>message</code>
- using the key event type <code><a href="#ACTION_DOWN_AND_UP">DOWN_AND_UP</a></code>.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>message</th>
- <td>
- A string containing the characters to send.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="wake"></A>
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">wake</span>
- <span class="normal">
- ()
- </span>
- </h4>
- <div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Wakes the screen of this device.
- </p>
- </div>
- </div>
-</div>
-<hr></hr>
-<h2>Appendix</h2>
- <p class="table-caption" id="table1">
- <strong>Table 1.</strong>Property variable names used with
- <span class="sympad"><a href="#getProperty">getProperty()</a></span> and
- <span class="sympad"><a href="#getSystemProperty">getSystemProperty()</a></span>.
- </p>
- <table>
- <tr>
- <th>
- Property Group
- </th>
- <th>
- Property
- </th>
- <th>
- Description
- </th>
- <th>
- Notes
- </th>
- </tr>
- <tr>
- <td rowspan="17"><code>build</code></td>
- <td><code>board</code></td>
- <td>Code name for the device's system board</td>
- <td rowspan="17">
- See {@link android.os.Build}
- </td>
- </tr>
- <tr>
- <td><code>brand</code></td>
- <td>The carrier or provider for which the OS is customized.</td>
- </tr>
- <tr>
- <td><code>device</code></td>
- <td>The device design name.</td>
- </tr>
- <tr>
- <td><code>fingerprint</code></td>
- <td>A unique identifier for the currently-running build.</td>
- </tr>
- <tr>
- <td><code>host</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>ID</code></td>
- <td>A changelist number or label.</td>
- </tr>
- <tr>
- <td><code>model</code></td>
- <td>The end-user-visible name for the device.</td>
- </tr>
- <tr>
- <td><code>product</code></td>
- <td>The overall product name.</td>
- </tr>
- <tr>
- <td><code>tags</code></td>
- <td>Comma-separated tags that describe the build, such as "unsigned" and "debug".</td>
- </tr>
- <tr>
- <td><code>type</code></td>
- <td>The build type, such as "user" or "eng".</td>
- </tr>
- <tr>
- <td><code>user</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>CPU_ABI</code></td>
- <td>
- The name of the native code instruction set, in the form CPU type plus
- ABI convention.
- </td>
- </tr>
- <tr>
- <td><code>manufacturer</code></td>
- <td>The product/hardware manufacturer.</td>
- </tr>
- <tr>
- <td><code>version.incremental</code></td>
- <td>
- The internal code used by the source control system to represent this version
- of the software.
- </td>
- </tr>
- <tr>
- <td><code>version.release</code></td>
- <td>The user-visible name of this version of the software.</td>
- </tr>
- <tr>
- <td><code>version.sdk</code></td>
- <td>The user-visible SDK version associated with this version of the OS.</td>
- </tr>
- <tr>
- <td><code>version.codename</code></td>
- <td>
- The current development codename, or "REL" if this version of the software has been
- released.
- </td>
- </tr>
- <tr>
- <td rowspan="3"><code>display</code></td>
- <td><code>width</code></td>
- <td>The device's display width in pixels.</td>
- <td rowspan="3">
- See
- {@link android.util.DisplayMetrics} for details.
- </td>
- </tr>
- <tr>
- <td><code>height</code></td>
- <td>The device's display height in pixels.</td>
- </tr>
- <tr>
- <td><code>density</code></td>
- <td>
- The logical density of the display. This is a factor that scales
- DIP (Density-Independent Pixel) units to the device's resolution. DIP is adjusted so
- that 1 DIP is equivalent to one pixel on a 160 pixel-per-inch display. For example,
- on a 160-dpi screen, density = 1.0, while on a 120-dpi screen, density = .75.
- <p>
- The value does not exactly follow the real screen size, but is adjusted to
- conform to large changes in the display DPI. See
- {@link android.util.DisplayMetrics#density} for more details.
- </p>
- </td>
- </tr>
- <tr>
- <td rowspan="6"><code>am.current</code></td>
- <td><code>package</code></td>
- <td>The Android package name of the currently running package.</td>
- <td rowspan="6">
- The <code>am.current</code> keys return information about the currently-running
- Activity.
- </td>
- </tr>
- <tr>
- <td><code>action</code></td>
- <td>
- The current activity's action. This has the same format as the <code>name</code>
- attribute of the <code>action</code> element in a package manifest.
- </td>
- </tr>
- <tr>
- <td><code>comp.class</code></td>
- <td>
- The class name of the component that started the current Activity. See
- <code><a href="#comppackage">comp.package</a></code> for more details.</td>
- </tr>
- <tr>
- <td><a name="comppackage"><code>comp.package</code></a></td>
- <td>
- The package name of the component that started the current Activity. A component
- is specified by a package name and the name of class that the package contains.
- </td>
- </tr>
- <tr>
- <td><code>data</code></td>
- <td>The data (if any) contained in the Intent that started the current Activity.</td>
- </tr>
- <tr>
- <td><code>categories</code></td>
- <td>The categories specified by the Intent that started the current Activity.</td>
- </tr>
- <tr>
- <td rowspan="3"><code>clock</code></td>
- <td><code>realtime</code></td>
- <td>
- The number of milliseconds since the device rebooted, including deep-sleep
- time.
- </td>
- <td rowspan="3">
- See {@link android.os.SystemClock} for more information.
- </td>
- </tr>
- <tr>
- <td><code>uptime</code></td>
- <td>
- The number of milliseconds since the device rebooted, <em>not</em> including
- deep-sleep time
- </td>
- </tr>
- <tr>
- <td><code>millis</code></td>
- <td>current time since the UNIX epoch, in milliseconds.</td>
- </tr>
- </table>
+++ /dev/null
-page.title=MonkeyImage
-parent.title=monkeyrunner
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-
-<p>
- A monkeyrunner class to hold an image of the device or emulator's screen. The image is
- copied from the screen buffer during a screenshot. This object's methods allow you to
- convert the image into various storage formats, write the image to a file, copy parts of
- the image, and compare this object to other <code>MonkeyImage</code> objects.
-</p>
-<p>
- You do not need to create new instances of <code>MonkeyImage</code>. Instead, use
-<code><a href="{@docRoot}tools/help/MonkeyDevice.html#takeSnapshot">
-MonkeyDevice.takeSnapshot()</a></code> to create a new instance from a screenshot. For example, use:
-</p>
-<pre>
-newimage = MonkeyDevice.takeSnapshot()
-</pre>
-<h2>Summary</h2>
-<table id="pubmethods" class="jd-sumtable">
- <tr>
- <th colspan="12" style="background-color: #E2E2E2">Methods</th>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>string</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#convertToBytes">convertToBytes</a>
- </span>
- (<em>string</em> format)
- </nobr>
- <div class="jd-descrdiv">
- Converts the current image to a particular format and returns it as a
- <em>string</em> that you can then access as an <em>iterable</em> of binary bytes.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>tuple</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#getRawPixel">getRawPixel</a>
- </span>
- (<em>integer</em> x,
- <em>integer</em> y)
- </nobr>
- <div class="jd-descrdiv">
- Returns the single pixel at the image location (x,y), as an
- a <em>tuple</em> of <em>integer</em>, in the form (a,r,g,b).
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>integer</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#getRawPixelInt">getRawPixelInt</a>
- </span>
- (<em>integer</em> x,
- <em>integer</em> y)
- </nobr>
- <div class="jd-descrdiv">
- Returns the single pixel at the image location (x,y), as
- a 32-bit <em>integer</em>.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a>
- </code>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#getSubImage">getSubImage</a>
- </span>
- (<em>tuple</em> rect)
- </nobr>
- <div class="jd-descrdiv">
- Creates a new <code>MonkeyImage</code> object from a rectangular selection of the
- current image.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>boolean</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#sameAs">sameAs</a>
- </span>
- (<code><a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a></code>
- other,
- <em>float</em> percent)
- </nobr>
- <div class="jd-descrdiv">
- Compares this <code>MonkeyImage</code> object to another and returns the result of
- the comparison. The <code>percent</code> argument specifies the percentage
- difference that is allowed for the two images to be "equal".
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>void</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#writeToFile">writeToFile</a>
- </span>
- (<em>string</em> path,
- <em>string</em> format)
- </nobr>
- <div class="jd-descrdiv">
- Writes the current image to the file specified by <code>filename</code>, in the
- format specified by <code>format</code>.
- </div>
- </td>
- </tr>
-</table>
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methods -->
-<h2>Public Methods</h2>
-<A NAME="convertToBytes"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- <span class="sympad">convertToBytes</span>
- <span class="normal">
- (
- <em>string</em> format)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Converts the current image to a particular format and returns it as a <em>string</em>
- that you can then access as an <em>iterable</em> of binary bytes.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>format</th>
- <td>
- The desired output format. All of the common raster output formats are supported.
- The default value is "png" (Portable Network Graphics).
- </td>
- </tr>
- </table>
- </div>
-</div>
-</div>
-<A NAME="getRawPixel"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>tuple</em>
- </span>
- <span class="sympad">getRawPixel</span>
- <span class="normal">
- (<em>integer</em> x,
- <em>integer</em> y)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Returns the single pixel at the image location (x,y), as an
- a <em>tuple</em> of <em>integer</em>, in the form (a,r,g,b).
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>x</th>
- <td>
- The horizontal position of the pixel, starting with 0 at the left of the screen in the
- orientation it had when the screenshot was taken.
- </td>
- </tr>
- <tr>
- <th>y</th>
- <td>
- The vertical position of the pixel, starting with 0 at the top of the screen in the
- orientation it had when the screenshot was taken.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- A tuple of integers representing the pixel, in the form (a,r,g,b) where
- a is the alpha channel value, and r, g, and b are the red, green, and blue values,
- respectively.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="getRawPixelInt"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>tuple</em>
- </span>
- <span class="sympad">getRawPixelInt</span>
- <span class="normal">
- (<em>integer</em> x,
- <em>integer</em> y)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Returns the single pixel at the image location (x,y), as an
- an <em>integer</em>. Use this method to economize on memory.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>x</th>
- <td>
- The horizontal position of the pixel, starting with 0 at the left of the screen in the
- orientation it had when the screenshot was taken.
- </td>
- </tr>
- <tr>
- <th>y</th>
- <td>
- The vertical position of the pixel, starting with 0 at the top of the screen in the
- orientation it had when the screenshot was taken.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- The a,r,g, and b values of the pixel as 8-bit values combined into a 32-bit
- integer, with a as the leftmost 8 bits, r the next rightmost, and so forth.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="getSubImage"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a>
- </code>
- </span>
- <span class="sympad">getSubImage</span>
- <span class="normal">
- (<em>tuple</em> rect)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Creates a new <code>MonkeyImage</code> object from a rectangular selection of the
- current image.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>rect</th>
- <td>
- A tuple (x, y, w, h) specifying the selection. x and y specify the 0-based pixel
- position of the upper left-hand corner of the selection. w specifies the width of the
- region, and h specifies its height, both in units of pixels.
- <p>
- The image's orientation is the same as the screen orientation at the time the
- screenshot was made.
- </p>
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- A new <code>MonkeyImage</code> object containing the selection.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="sameAs"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>boolean</em>
- </span>
- <span class="sympad">sameAs</span>
- <span class="normal">
- (
- <code>
- <a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a>
- </code> otherImage,
- <em>float</em> percent
- )
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Compares this <code>MonkeyImage</code> object to another and returns the result of
- the comparison. The <code>percent</code> argument specifies the percentage
- difference that is allowed for the two images to be "equal".
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>other</th>
- <td>
- Another <code>MonkeyImage</code> object to compare to this one.
- </td>
- </tr>
- <tr>
- <th>
- percent
- </th>
- <td>
- A float in the range 0.0 to 1.0, inclusive, indicating
- the percentage of pixels that need to be the same for the method to return
- <code>true</code>. The default is 1.0, indicating that all the pixels
- must match.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- Boolean <code>true</code> if the images match, or boolean <code>false</code> otherwise.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="writeToFile"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">writeToFile</span>
- <span class="normal">
- (<em>string</em> filename,
- <em>string</em> format)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Writes the current image to the file specified by <code>filename</code>, in the
- format specified by <code>format</code>.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>path</th>
- <td>
- The fully-qualified filename and extension of the output file.
- </td>
- </tr>
- <tr>
- <th>
- format
- </th>
- <td>
- The output format to use for the file. If no format is provided, then the
- method tries to guess the format from the filename's extension. If no
- extension is provided and no format is specified, then the default format of
- "png" (Portable Network Graphics) is used.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
+++ /dev/null
-page.title=MonkeyRunner
-parent.title=monkeyrunner
-parent.link=index.html
-@jd:body
-
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>
- A monkeyrunner class that contains static utility methods.
-</p>
-<h2>Summary</h2>
-<table id="pubmethods" class="jd-sumtable">
- <tr>
- <th colspan="12" style="background-color: #E2E2E2">Methods</th>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#alert">alert</a>
- </span>
- (<em>string</em> message,
- <em>string</em> title,
- <em>string</em> okTitle)
- </nobr>
- <div class="jd-descrdiv">
- Displays an alert dialog to the process running the current
- program.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>integer</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#choice">choice</a>
- </span>
- (<em>string</em> message,
- <em>iterable</em> choices,
- <em>string</em> title)
- </nobr>
- <div class="jd-descrdiv">
- Displays a dialog with a list of choices to the process running the current program.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#help">help</a>
- </span>
- (<em>string</em> format)
- </nobr>
- <div class="jd-descrdiv">
- Displays the monkeyrunner API reference in a style similar to that of Python's
- <code>pydoc</code> tool, using the specified format.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <em>string</em>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#input">input</a>
- </span>
- (<em>string</em> message,
- <em>string</em> initialValue,
- <em>string</em> title,
- <em>string</em> okTitle,
- <em>string</em> cancelTitle)
- </nobr>
- <div class="jd-descrdiv">
- Displays a dialog that accepts input.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- void
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#sleep">sleep</a>
- </span>
- (<em>float</em> seconds)
- </nobr>
- <div class="jd-descrdiv">
- Pauses the current program for the specified number of seconds.
- </div>
- </td>
- </tr>
- <tr class="api" >
- <td class="jd-typecol">
- <nobr>
- <code>
- <a href="{@docRoot}tools/help/MonkeyDevice.html">MonkeyDevice</a>
- </code>
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%">
- <nobr>
- <span class="sympad">
- <a href="#waitForConnection">waitForConnection</a>
- </span>
- (<em>float</em> timeout,
- <em>string</em> deviceId)
- </nobr>
- <div class="jd-descrdiv">
- Tries to make a connection between the <code>monkeyrunner</code> backend and the
- specified device or emulator.
- </div>
- </td>
- </tr>
-</table>
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methods -->
-<h2>Public Methods</h2>
-<A NAME="alert"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- <span class="sympad">alert</span>
- <span class="normal">
- (
- <em>string</em> message,
- <em>string</em> title,
- <em>string</em> okTitle)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Displays an alert dialog to the process running the current
- program. The dialog is modal, so the program pauses until the user clicks the dialog's
- button.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>message</th>
- <td>
- The message to display in the dialog.
- </td>
- </tr>
- <tr>
- <th>title</th>
- <td>
- The dialog's title. The default value is "Alert".
- </td>
- </tr>
- <tr>
- <th>okTitle</th>
- <td>
- The text displayed in the dialog button. The default value is "OK".
- </td>
- </tr>
- </table>
- </div>
-</div>
-</div>
-<A NAME="choice"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>integer</em>
- </span>
- <span class="sympad">choice</span>
- <span class="normal">
- (<em>string</em> message,
- <em>iterable</em> choices,
- <em>string</em> title)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Displays a dialog with a list of choices to the process running the current program. The
- dialog is modal, so the program pauses until the user clicks one of the dialog's
- buttons.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>message</th>
- <td>
- The prompt message displayed in the dialog.
- </td>
- </tr>
- <tr>
- <th>choices</th>
- <td>
- A Python iterable containing one or more objects that are displayed as strings. The
- recommended form is an array of strings.
- </td>
- </tr>
- <tr>
- <th>
- title
- </th>
- <td>
- The dialog's title. The default is "Input".
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- If the user makes a selection and clicks the "OK" button, the method returns
- the 0-based index of the selection within the iterable.
- If the user clicks the "Cancel" button, the method returns -1.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="help"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">help</span>
- <span class="normal">
- (<em>string</em> format)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Displays the monkeyrunner API reference in a style similar to that of Python's
- <code>pydoc</code> tool, using the specified format.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>format</th>
- <td>
- The markup format to use in the output. The possible values are "text" for plain text
- or "html" for HTML.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="input"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <em>string</em>
- </span>
- <span class="sympad">input</span>
- <span class="normal">
- (<em>string</em> message
- <em>string</em> initialValue,
- <em>string</em> title,
- <em>string</em> okTitle,
- <em>string</em> cancelTitle)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Displays a dialog that accepts input and returns it to the program. The dialog is
- modal, so the program pauses until the user clicks one of the dialog's buttons.
- </p>
- <p>
- The dialog contains two buttons, one of which displays the okTitle value
- and the other the cancelTitle value. If the user clicks the okTitle button,
- the current value of the input box is returned. If the user clicks the cancelTitle
- button, an empty string is returned.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>message</th>
- <td>
- The prompt message displayed in the dialog.
- </td>
- </tr>
- <tr>
- <th>initialValue</th>
- <td>
- The initial value to display in the dialog. The default is an empty string.
- </td>
- </tr>
- <tr>
- <th>title</th>
- <td>
- The dialog's title. The default is "Input".
- </td>
- </tr>
- <tr>
- <th>okTitle</th>
- <td>
- The text displayed in the okTitle button. The default is "OK".
- </td>
- </tr>
- <tr>
- <th>cancelTitle</th>
- <td>
- The text displayed in the cancelTitle button. The default is "Cancel".
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- If the user clicks the okTitle button, then the method returns the current value of
- the dialog's input box. If the user clicks the cancelTitle button, the method returns
- an empty string.
- </li>
- </ul>
- </div>
- </div>
-</div>
-<A NAME="sleep"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- void
- </span>
- <span class="sympad">sleep</span>
- <span class="normal">
- (
- <em>float</em> seconds
- )
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Pauses the current program for the specified number of seconds.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>seconds</th>
- <td>
- The number of seconds to pause.
- </td>
- </tr>
- </table>
- </div>
- </div>
-</div>
-<A NAME="waitForConnection"></A>
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- <code>
- <a href="{@docRoot}tools/help/MonkeyDevice.html">MonkeyDevice</a>
- </code>
- </span>
- <span class="sympad">waitForConnection</span>
- <span class="normal">
- (<em>float</em> timeout,
- <em>string</em> deviceId)
- </span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr">
- <p>
- Tries to make a connection between the <code>monkeyrunner</code> backend and the
- specified device or emulator.
- </p>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Arguments</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</th>
- <td>
- The number of seconds to wait for a connection. The default is to wait forever.
- </td>
- </tr>
- <tr>
- <th>
- deviceId
- </th>
- <td>
- A regular expression that specifies the serial number of the device or emulator. See
- the topic
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>
- for a description of device and emulator serial numbers.
- </td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist">
- <li>
- A <code><a href="{@docRoot}tools/help/MonkeyDevice.html">MonkeyDevice</a></code>
- instance for the device or emulator. Use this object to control and communicate with the
- device or emulator.
- </li>
- </ul>
- </div>
- </div>
-</div>
+++ /dev/null
-page.title=Android Debug Bridge
-parent.title=Tools
-parent.link=index.html
-page.tags=adb
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#Enabling">Enabling adb Debugging</a></li>
- <li><a href="#issuingcommands">Syntax</a></li>
- <li><a href="#commandsummary">Commands</a></li>
- <li><a href="#devicestatus">Querying for Emulator/Device Instances</a></li>
- <li><a href="#directingcommands">Directing Commands to a Specific Emulator/Device Instance</a></li>
- <li><a href="#move">Installing an Application</a></li>
- <li><a href="#forwardports">Forwarding Ports</a></li>
- <li><a href="#copyfiles">Copying Files to or from an Emulator/Device Instance</a></li>
- <li><a href="#stopping">Stopping the adb Server</a></li>
- <li><a href="#wireless">Wireless usage</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an
-emulator instance or connected Android-powered device. It is a client-server program that includes
-three components: </p>
-
-<ul>
- <li>A client, which runs on your development machine. You can invoke a client from a shell
-by issuing an adb command. Other Android tools such as DDMS also create
-adb clients. </li>
- <li>A server, which runs as a background process on your development machine. The server
-manages communication between the client and the adb daemon running on an emulator or device. </li>
- <li>A daemon, which runs as a background process on each emulator or device instance. </li>
-</ul>
-
-<p>You can find the {@code adb} tool in {@code <sdk>/platform-tools/}.</p>
-
-<p>When you start an adb client, the client first checks whether there is an adb server
-process already running. If there isn't, it starts the server process. When the server starts,
-it binds to local TCP port 5037 and listens for commands sent from adb clients—all adb
-clients use port 5037 to communicate with the adb server. </p>
-
-<p>The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port. Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example: </p>
-
-<p style="margin-left:2em">
-Emulator 1, console: 5554<br/>
-Emulator 1, adb: 5555<br>
-Emulator 2, console: 5556<br>
-Emulator 2, adb: 5557<br>
-and so on...
-</p>
-
-<p>As shown, the emulator instance connected to adb on port 5555 is the same as the instance
-whose console listens on port 5554. </p>
-
-<p>Once the server has set up connections to all emulator instances, you can use adb commands to
-access those instances. Because the server manages connections to emulator/device
-instances and handles commands from multiple adb clients, you can control any emulator/device
-instance from any client (or from a script).</p>
-
-
-<h2 id="Enabling">Enabling adb Debugging</h2>
-
-<p>In order to use adb with a device connected over USB, you must enable
-<strong>USB debugging</strong> in the device system settings, under <strong>
-Developer options</strong>.</p>
-
-<p>On Android 4.2 and higher, the Developer options screen is
-hidden by default. To make it visible, go to
-<b>Settings > About phone</b> and tap <b>Build number</b> seven times. Return to the previous
-screen to find <strong>Developer options</strong> at the bottom.</p>
-
-<p>On some devices, the Developer options screen may be located or named differently.</p>
-
-<p class="note"><strong>Note:</strong> When you connect a device running Android 4.2.2 or higher
-to your computer, the system shows a dialog asking whether to accept an RSA key that allows
-debugging through this computer. This security mechanism protects user devices because it ensures
-that USB debugging and other adb commands cannot be executed unless you're able to unlock the
-device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with
-SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or
-higher.</p>
-
-<p>For more information about connecting to a device over USB, read
-<a href="{@docRoot}tools/device.html">Using Hardware Devices</a>.</p>
-
-
-
-
-<h2 id="issuingcommands">Syntax</h2>
-
-<p>You can issue adb commands from a command line on your development machine or from a script.
-The usage is: </p>
-
-<pre class="no-pretty-print">
-adb [-d|-e|-s <serialNumber>] <command>
-</pre>
-
-<p>If there's only one emulator running or only one device connected, the adb command is
-sent to that device by default. If multiple emulators are running and/or multiple devices are
-attached, you need to use the <code>-d</code>, <code>-e</code>, or <code>-s</code>
-option to specify the target device to which the command should be directed. </p>
-
-
-
-<h2 id="commandsummary">Commands</h2>
-
-<p>The table below lists all of the supported adb commands and explains their meaning and usage. </p>
-
-<p class="table-caption"><strong>Table 1.</strong> Available adb commands</p>
-<table>
-<tr>
- <th>Category</th>
- <th>Command</th>
- <th>Description</th>
- <th>Comments</th>
-</tr>
-
-<tr>
-<td rowspan="3">Target Device</td>
-<td><code>-d</code></td>
-<td>Direct an adb command to the only attached USB device.</td>
-<td>Returns an error if more than one USB device is attached.</td>
-</tr>
-
-<tr>
-<td><code>-e</code></td>
-<td>Direct an adb command to the only running emulator instance.</td>
-<td>Returns an error if more than one emulator instance is running. </td>
-</tr>
-
-<tr>
-<td><code>-s <serialNumber></code></td>
-<td>Direct an adb command a specific emulator/device instance, referred to by its adb-assigned serial number (such as "emulator-5556").</td>
-<td>See <a href="#directingcommands">Directing
-Commands to a Specific Emulator/Device Instance</a>.</td>
-</tr>
-
-<tr>
-<td rowspan="3">General</td>
-<td><code>devices</code></td>
-<td>Prints a list of all attached emulator/device instances.</td>
-<td>See <a href="#devicestatus">Querying for Emulator/Device Instances</a> for more information.</td>
-</tr>
-
-<tr>
-<td><code>help</code></td>
-<td>Prints a list of supported adb commands.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>version</code></td>
-<td>Prints the adb version number. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td rowspan="3">Debug</td>
-<td ><code>logcat [option] [filter-specs]</code></td>
-<td>Prints log data to the screen. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>bugreport</code></td>
-<td>Prints <code>dumpsys</code>, <code>dumpstate</code>, and <code>logcat</code> data to the screen, for the purposes of bug reporting. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>jdwp</code></td>
-<td>Prints a list of available JDWP processes on a given device. </td>
-<td>You can use the <code>forward jdwp:<pid></code> port-forwarding specification to connect to a specific JDWP process. For example: <br>
- <code>adb forward tcp:8000 jdwp:472</code><br>
- <code>jdb -attach localhost:8000</code></p>
- </td>
-</tr>
-
-<tr>
-<td rowspan=3">Data</td>
-<td><code>install <path-to-apk></code></td>
-<td>Pushes an Android application (specified as a full path to an .apk file) to an emulator/device. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>pull <remote> <local></code></td>
-<td>Copies a specified file from an emulator/device instance to your development computer. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>push <local> <remote></code></td>
-<td>Copies a specified file from your development computer to an emulator/device instance. </td>
-<td> </td>
-</tr>
-
-<tr>
-<td rowspan="2">Ports and Networking</td>
-<td><code>forward <local> <remote></code></td>
-<td>Forwards socket connections from a specified local port to a specified remote port on the emulator/device instance. </td>
-<td>Port specifications can use these schemes:
-<ul><li><code>tcp:<portnum></code></li>
-<li><code>local:<UNIX domain socket name></code></li>
-<li><code>dev:<character device name></code></li>
-<li><code>jdwp:<pid></code></li></ul>
-</td>
-</tr>
-
-<tr>
-<td><code>ppp <tty> [parm]...</code></td>
-<td>Run PPP over USB.
-<ul>
-<li><code><tty></code> — the tty for PPP stream. For example <code>dev:/dev/omap_csmi_ttyl</code>. </li>
-<li><code>[parm]... </code> — zero or more PPP/PPPD options, such as <code>defaultroute</code>, <code>local</code>, <code>notty</code>, etc.</li></ul>
-
-<p>Note that you should not automatically start a PPP connection. </p></td>
-<td></td>
-</tr>
-
-<tr>
-<td rowspan="3">Scripting</td>
-<td><code>get-serialno</code></td>
-<td>Prints the adb instance serial number string.</td>
-<td rowspan="2">See <a href="#devicestatus">Querying for Emulator/Device Instances</a> for more information. </td>
-</tr>
-
-<tr>
-<td><code>get-state</code></td>
-<td>Prints the adb state of an emulator/device instance.</td>
-</td>
-</tr>
-
-<tr>
-<td><code>wait-for-device</code></td>
-<td>Blocks execution until the device is online — that is, until the instance state is <code>device</code>.</td>
-<td>You can prepend this command to other adb commands, in which case adb will wait until the emulator/device instance is connected before issuing the other commands. Here's an example:
-<pre class="no-pretty-print">adb wait-for-device shell getprop</pre>
-
-Note that this command does <em>not</em> cause adb to wait until the entire system is fully booted. For that reason, you should not prepend it to other commands that require a fully booted system. As an example, the <code>install</code> requires the Android package manager, which is available only after the system is fully booted. A command such as
-
-<pre class="no-pretty-print">adb wait-for-device install <app>.apk</pre>
-
-would issue the <code>install</code> command as soon as the emulator or device instance connected to the adb server, but before the Android system was fully booted, so it would result in an error. </td>
-</tr>
-
-
-
-<tr>
-<td rowspan="2">Server</td>
-<td><code>start-server</code></td>
-<td>Checks whether the adb server process is running and starts it, if not.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>kill-server</code></td>
-<td>Terminates the adb server process.</td>
-<td> </td>
-</tr>
-
-
-
-<tr>
-<td rowspan="2">Shell</td>
-<td><code>shell</code></td>
-<td>Starts a remote shell in the target emulator/device instance.</td>
-<td rowspan="2">See <a href="{@docRoot}tools/help/shell.html#shellcommands">ADB Shell Commands</a> for more information. </td>
-</tr>
-
-<tr>
-<td><code>shell [shellCommand]</code></td>
-<td>Issues a shell command in the target emulator/device instance and then exits the remote shell.</td>
-</tr>
-
-</table>
-
-
-
-
-
-
-
-
-
-
-<h2 id="devicestatus">Querying for Emulator/Device Instances</h2>
-
-<p>Before issuing adb commands, it is helpful to know what emulator/device instances are connected to the adb server. You can generate a list of attached emulators/devices using the <code>devices</code> command: </p>
-
- <pre class="no-pretty-print">adb devices</pre>
-
-<p>In response, adb prints this status information for each instance:</p>
-
-<ul>
- <li>Serial number — A string created by adb to uniquely identify an emulator/device instance by its
- console port number. The format of the serial number is <code><type>-<consolePort></code>.
- Here's an example serial number: <code>emulator-5554</code></li>
- <li>State — The connection state of the instance may be one of the following:
- <ul>
- <li><code>offline</code> — the instance is not connected to adb or is not responding.</li>
- <li><code>device</code> — the instance is now connected to the adb server. Note that this state does not
- imply that the Android system is fully booted and operational, since the instance connects to adb
- while the system is still booting. However, after boot-up, this is the normal operational state of
- an emulator/device instance.</li>
- <li><code>no device</code> — there is no emulator/device connected.
- </ul>
- </li>
-</ul>
-
-<p>The output for each instance is formatted like this: </p>
-
- <pre class="no-pretty-print">[serialNumber] [state]</pre>
-
-<p>Here's an example showing the <code>devices</code> command and its output:</p>
-
- <pre class="no-pretty-print">adb devices
-List of devices attached
-emulator-5554 device
-emulator-5556 device
-emulator-5558 device</pre>
-
-
-
-
-
-
-<h2 id="directingcommands">Directing Commands to a Specific Emulator/Device Instance</h2>
-
-<p>If multiple emulator/device instances are running, you must specify a target instance
-when issuing adb commands. To do so, use the <code>-s</code> option in the commands. The usage
-for the <code>-s</code> option is:</p>
-
-<pre class="no-pretty-print">adb -s <serialNumber> <command> </pre>
-
-<p>As shown, you specify the target instance for a command using its adb-assigned serial number.
-You can use the <code>devices</code> command to obtain the serial numbers of running
-emulator/device instances. For example: </p>
-
-<pre class="no-pretty-print">adb -s emulator-5556 install helloWorld.apk</pre>
-
-<p>Note that, if you issue a command without specifying a target emulator/device instance
-while multiple devices are available, adb generates an error.
-
-<p>If you have multiple devices available (hardware or emulated), but only one is an emulator,
-simply use the {@code -e} option to send commands to the emulator. Likewise if there's multiple
-devices but only one hardware device attached, use the {@code -d} option to send commands to
-the hardware device.
-
-
-
-
-<h2 id="move">Installing an Application</h2>
-<p>You can use adb to copy an application from your development computer and install it on an emulator/device instance. To do so, use the <code>install</code> command. With the command, you must specify the path to the .apk file that you want to install:</p>
-
-<pre class="no-pretty-print">adb install <path_to_apk></pre>
-
-<p>For more information about how to create an .apk file that you can install on an emulator/device
-instance, see <a href="{@docRoot}tools/building/index.html">Building and Running</a></p>
-
-<p>Note that, if you are using Android Studio, you do not need to use adb (or aapt) directly to install your application on the emulator/device. Instead, Android Studio handles the packaging and installation of the application for you. </p>
-
-
-
-
-
-
-<h2 id="forwardports">Forwarding Ports</h2>
-
- <p>You can use the <code>forward</code> command to set up arbitrary port forwarding — forwarding of requests on a specific host port to a different port on an emulator/device instance. Here's how you would set up forwarding of host port 6100 to emulator/device port 7100:</p>
-<pre class="no-pretty-print">adb forward tcp:6100 tcp:7100</pre>
- <p>You can also use adb to set up forwarding to named abstract UNIX domain sockets, as illustrated here:</p>
-<pre class="no-pretty-print">adb forward tcp:6100 local:logd </pre>
-
-
-
-
-
-<h2 id="copyfiles">Copying Files to or from an Emulator/Device Instance</h2>
-
-<p>You can use the adb commands <code>pull</code> and <code>push</code> to copy files to
-and from an emulator/device instance. Unlike the <code>install</code> command,
-which only copies an APK file to a specific location, the <code>pull</code> and <code>push</code>
-commands let you copy arbitrary directories and files to any location in an
-emulator/device instance. </p>
-
-<p>To copy a file or directory (and its sub-directories) <em>from</em> the emulator or device, use</p>
-<pre class="no-pretty-print">adb pull <remote> <local></pre>
-
-<p>To copy a file or directory (and its sub-directories) <em>to</em> the emulator or device, use</p>
- <pre class="no-pretty-print">adb push <local> <remote></pre>
-
-<p>In the commands, <code><local></code> and <code><remote></code> refer to the
-paths to the target files/directory on your development machine (local) and on the
-emulator/device instance (remote). For example: </p>
-<pre class="no-pretty-print">adb push foo.txt /sdcard/foo.txt</pre>
-
-
-
-
-<h2 id="stopping">Stopping the adb Server</h2>
-
-<p>In some cases, you might need to terminate the adb server process and then restart it
-to resolve the problem (e.g., if adb does not respond to a command).</p>
-
-<p>To stop the adb server, use the <code>kill-server</code> command.
-You can then restart the server by issuing any other adb command. </p>
-
-
-<h2 id="wireless">Wireless usage</h2>
-
-<p>
-adb is usually used over USB. However, it is also possible to use over
-Wi-Fi, as described here.
-</p>
-
-<ol>
-
-<li>
-<p>Connect your Android device and adb host computer
-to a common Wi-Fi network accessible to both.
-We have found that not all access points
-are suitable; you may need to use an access point
-whose firewall is configured properly to support adb.</p>
-
-<p class="note"><strong>Note: </strong>If you are attempting to connect
-to a Wear device, force it to connect to Wi-Fi by shutting off Bluetooth
-on the phone connected to it.</p>
-</li>
-
-<li>
-Connect the device to the host computer with a USB cable.
-</li>
-
-<li>
-Set the target device to listen for a TCP/IP connection on port 5555.
-<pre class="no-pretty-print">
-$ adb tcpip 5555
-</pre>
-</li>
-
-<li>
-Disconnect the USB cable from the target device.
-</li>
-
-<li>
-Find the IP address of the Android device. For example, on a Nexus device, you can find
-the IP address at <strong>Settings</strong> > <strong>About tablet</strong>
-(or <strong>About phone</strong>) > <strong>Status</strong> > <strong>IP address</strong>. Or,
-on an Android Wear device, you can find the IP address at <strong>Settings</strong> >
-<strong>Wi-Fi Settings</strong> > <strong>Advanced</strong> > <strong>IP address</strong>.
-</li>
-
-<li>
-Connect to the device, identifying it by IP address.
-<pre class="no-pretty-print">
-$ adb connect <device-ip-address>
-</pre>
-</li>
-
-
-<li>
-Confirm that your host computer is connected to the target device:
-<pre class="no-pretty-print">
-$ adb devices
-List of devices attached
-<device-ip-address>:5555 device
-</pre>
-
-</ol>
-
-<p>
-You're now good to go!
-</p>
-
-<p>
-If the adb connection is ever lost:
-</p>
-
-<ol>
-
-<li>
-Make sure that your host is still connected to the same Wi-Fi network your Android device is.
-</li>
-
-<li>
-Reconnect by executing the "adb connect" step again.
-</li>
-
-<li>
-Or if that doesn't work, reset your adb host:
-<pre class="no-pretty-print">
-adb kill-server
-</pre>
-and then start over from the beginning.
-</li>
-
-</ol>
+++ /dev/null
-page.title=Android Developer Tools
-page.tags=adt
-@jd:body
-
-<p class="caution">
- <strong>Important:</strong> Support for the Android Developer Tools (ADT) in Eclipse has ended,
- per our <a href=
- "http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html"
- class="external-link">announcement</a>. You should migrate your app development projects to
- Android Studio as soon as possible. For more information on transitioning to Android Studio, see
- <a href="{@docRoot}sdk/installing/migrate.html">Migrating from Eclipse ADT</a>.
-</p>
-
- <p>Formerly the official IDE solution for Android development, Android Developer Tools (ADT)
- is a plugin for Eclipse that provides GUI-based access to many of the command-line SDK tools,
- along with a UI design tool for rapid prototyping, designing, and building of your app's
- user interface.</p>
-
- <p>As with ADT, support for the <a href="http://ant.apache.org/"
- class="external-link">Ant</a>
- tool for building from the command line has ended.
- <a href="{@docRoot}tools/building/plugin-for-gradle.html">Gradle</a> is now the supported method
- of building Android apps.
- </p>
+++ /dev/null
-page.title=Allocation Tracker
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Memory Monitor to capture allocation data about your app. The Allocation Tracker displays each method responsible for an allocation, as well as the allocation size and number of instances.
-page.image=tools/help/thumbnails/am_alloctracker.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#display">Understanding the Allocation Tracker Display</a></li>
- <li><a href="#alloc-snapshot">Taking and Displaying a Snapshot of Allocation Data</a></li>
- <li><a href="#alloc-viewing">Viewing a Saved Allocation Tracking File</a></li>
- <li><a href="#alloc-sorting">Sorting Allocation Data</a></li>
- <li><a href="#alloc-source">Displaying Java Source</a></li>
- <li><a href="#alloc-files">Working with Allocation Tracking Files</a></li>
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/articles/memory.html">Managing Your App's Memory</a></li>
- <li><a href="{@docRoot}guide/practices/verifying-apps-art.html#GC_Migration">Addressing Garbage Collection Issues</a></li>
- <li><a href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a></li>
- </ol>
-
-</div>
-</div>
-
-
-
-
-<p>Android Studio allows you to track memory allocation as it monitors memory use. Tracking memory
- allocation allows you to monitor where objects are being allocated when you perform certain
- actions. Knowing these allocations enables you to adjust the method calls related to those actions
- to optimize app performance and memory use.</p>
-
-<p>The Allocation Tracker does the following:</p>
-<ul>
-<li>Shows when and where your code allocates object types, their size, allocating thread, and stack
- traces.</li>
-<li>Helps recognize memory churn through recurring allocation/deallocation patterns.</li>
-<li>Helps you track down memory leaks when used in combination with the HPROF Viewer. For example,
- if you see a bitmap object resident on the heap, you can find its allocation location with
- Allocation Tracker.</li>
-</ul>
-
-
-<p>However, it takes time and experience to learn to interpret the output from this tool.</p>
-
-<h2 id="display">
- Understanding the Allocation Tracker Display
-</h2>
-
-<p>
- The Allocation Tracker looks similar to the following figure:
-</p>
-<img src="{@docRoot}images/tools/am-alloctracker.png" />
-<p>
-
-
-<p>The tool displays the following information: </p>
-
-<table>
- <tr>
- <th scope="col">Column</th>
- <th scope="col">Description</th>
- </tr>
-
- <tr>
- <td><strong>Method</strong></td>
- <td>The Java method responsible for the allocation.</td>
- </tr>
- <tr>
- <td><strong>Count</strong></td>
- <td>Total number of instances allocated.</td>
- </tr>
- <tr>
- <td><strong>Size</strong></td>
- <td>The total amount of allocated memory in bytes.</td>
- </tr>
-
-</table>
-
-<h2 id="alloc-snapshot">Taking and Displaying a Snapshot of Allocation Data</h2>
-
-<p>To examine allocation data:</p>
-<ol>
- <li><a href="{@docRoot}tools/help/am-memory.html#displaying">Display a running app in the Memory
- Monitor</a>.</li>
-<li>Click Start Allocation Tracking
- <img src="{@docRoot}images/tools/am-ialloctracking.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Start Allocation Tracking icon" />. </li>
-<li>Click Start Allocation Tracking
- <img src="{@docRoot}images/tools/am-ialloctracking.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Start Allocation Tracking icon" /> again to
- deselect it and end the snapshot. </li>
-
- <p>The Memory Monitor displays the period when it took the snapshot. In the following
- figure, you can see the snapshot period, as shown on the left. By comparison, when you dump the
- Java heap, the Memory Monitor displays just the point where the heap snapshot was taken, as
- shown on the right.</p>
- <img src="{@docRoot}images/tools/am-dumpalloc2.png" />
-
-<p>Android Studio creates the heap snapshot file with the
- filename <code><em>package_yyyy.mm.dd_hh.mm.ss</em>.alloc</code> using the activity package (or
- project) name, year, month, day,
- hour, minute, and second of the capture, for example,
- <code>com.android.calc_2015.11.17_14.58.48.alloc</code>.</p>
-
- The Allocation Tracker appears.
-</p>
-
-<li>Optionally click the graphic icon <img src="{@docRoot}images/tools/am-igraphic.png"
-style="vertical-align:sub;margin:0;height:17px"
- alt="graphic icon" /> to display a visual representation of the data.
- </li>
-
-
-
-
-<li>Select the Group By menu option you want to display: </li>
-<ul>
-<li><strong>Group by Allocator</strong> </li>
-<li><strong>Group by Method</strong></li>
-</ul>
-
-</ol>
-
-
-<h2 id="alloc-viewing">Viewing a Saved Allocation Tracking File</h2>
-<p>After you capture allocation data, Android Studio automatically stores it so
-you can view it again.</p>
-<p>To view an allocation tracking file in the Allocation Tracker:</p>
-
-
-<ol>
-<li>Click
-<img src="{@docRoot}images/tools/am-icaptures.png"
-style="vertical-align:sub;margin:0;height:17px"
- alt="Captures icon" /> in the main window.</li>
-
-<p>Or select <strong>View</strong> > <strong>Tools Windows</strong> >
-<strong>Captures</strong>.</p>
-<p>The <em>Captures</em> window appears.</p>
-<li>Open the <strong>Allocation Tracking</strong> folder.</li>
-<li>Double-click the file to view it.</li>
-</ol>
-
-<h2 id="alloc-sorting">Sorting Allocation Data</h2>
-
-<p>To sort allocation data:</p>
-<ul>
-<li>In the Allocation Tracker, click a column heading to sort the table by ascending or
- descending order. </li>
-</ul>
-
-
-<h2 id="alloc-source">Displaying Java Source</h2>
-<p>For some items displayed in the Allocation Tracker, you can view the Java source.</p>
-<p>To display Java source:</p>
-<ul>
-<li>In the Allocation Tracker, right-click a method and then select <strong>Jump to Source</strong>.
-</li>
-<li>In the Allocation Tracker, select a method and then click Jump to Source
- <img src="{@docRoot}images/tools/am-ijumptosource.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Jump to Source icon" />. </li>
-</ul>
-
-<p>The source code appears in the Code Editor.</p>
-
-
-<h2 id="alloc-files">Working with Allocation Tracking Files</h2>
-<p>You can rename, locate, and delete an allocation tracking file from within
-Android Studio.</p>
-
-<h3 id="alloc-renaming">Renaming an allocation tracking file</h3>
-
-<p>If you rename a file from within Android Studio, it continues to appear in the <em>Captures</em>
- window.</p>
-<p>To rename an allocation tracking file:</p>
-<ol>
-<li>In the <em>Captures</em> window, right-click the file and select <strong>Rename</strong>.</li>
-<li>In the <em>Rename</em> dialog, specify the name of the file and click <strong>OK</strong>.</li>
-</ol>
-
-
-<h3 id="alloc-locating">Locating an allocation tracking file</h3>
-<p>You can quickly discover where Android Studio stored allocation tracking files on disk.</p>
-
-
-<p>To locate an allocation tracking file from Android Studio: </p>
-<ul>
-<li>In the <em>Captures</em> window, right-click allocation file and select
- <strong>Show</strong> or <strong>Reveal</strong>.</li>
-
-<p>Android Studio opens an operating system file browser displaying the location where the file
- resides.</p>
-</ul>
-
-<p class="note"><strong>Note:</strong> If you move an allocation tracking file, Android Studio
- no longer displays it in the <em>Captures</em> window. To display the file, use
- <strong>File</strong>
- > <strong>Open</strong>. Also, rename the file from the <em>Captures</em>
- window and not in the operating system file browser. </p>
-
-<h3 id="alloc-deleting">Deleting an allocation tracking file</h3>
-
-
-<p>To delete an allocation tracking file: </p>
-<ul>
-<li>In the <em>Captures</em> window, right-click an allocation tracking file and select
- <strong>Delete</strong>.</li>
-
-<p>Android Studio deletes the file from the <em>Captures</em> dialog and from disk. </p>
-</ul>
+++ /dev/null
-page.title=Android Monitor Basics
-parent.title=Android Monitor
-parent.link=index.html
-page.tags=monitor
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#byb">Prerequisites and Dependencies</a></li>
- <li><a href="#displaying">Displaying Android Monitor</a></li>
- <li><a href="#profiling">Profiling a Running App in Android Monitor</a></li>
- <li><a href="#switching">Switching between Devices and Apps</a></li>
- <li><a href="#rearranging">Rearranging Android Monitor Windows</a></li>
- <li><a href="#terminating">Terminating an App</a></li>
- <li><a href="#removing">Removing an App from a Device</a></li>
- <li><a href="#other">Using Other Main Window Features</a></li>
-</ol>
-
-
-
-
-
-</div>
-</div>
-
-<p>
- Android Monitor has a main window that contains the logcat, Memory, CPU, GPU, and Network
- Monitors. From this window, you can select a device and app process to work with, terminate an
- app, collect <code>dumpsys</code> system information, and create screenshots and videos of the
- running app.
-</p>
-
-
-<h2 id="byb">
- Prerequisites and Dependencies
-</h2>
-
-<p>
- Before you start using Android Monitor, you need to set up your environment, as well as the
- hardware device or emulator. All of the monitors require the following:
-</p>
- <ul>
- <li>If you want to run your app on a hardware device (as opposed to the emulator), connect it
- to the USB port. Make sure your development computer
- <a href="{@docRoot}tools/device.html#setting-up">detects your device</a>, which often
- happens automatically when you connect it.
- </li>
- <li>Enable ADB integration by selecting <strong>Tools</strong> > <strong>Android</strong>
- > <strong>Enable ADB Integration</strong>. <strong>Enable ADB Integration</strong>
- should have a check mark next to it in the menu to indicate it's enabled.
- </li>
- <li>
- <a href="{@docRoot}tools/help/monitor.html">Android Device Monitor</a> can’t be running.
- </li>
- </ul>
-
- <p>
- All but the logcat Monitor have these additional requirements:
-</p>
-<ul>
- <li>
- <a href="{@docRoot}tools/device.html#device-developer-options">Enable</a> <strong><a href=
- "{@docRoot}tools/device.html#device-developer-options">USB debugging</a></strong> in
- <strong>Developer Options</strong> on the device or emulator.
- </li>
-
- <li>In your app, set the <code>debuggable</code> property to <code>true</code> in the manifest or
- <code>build.gradle</code> file (it’s initially set by default).
- </li>
-</ul>
-
-
-<p>
- The GPU Monitor has this requirement as well:
-</p>
-<ul>
- <li>For Android 5.0 (API level 21) and Android 5.1 (API level 22), in <strong>Developer
- Options</strong> on the device or emulator, set <strong>Profile GPU rendering</strong> to
- <strong>In adb shell dumpsys gfxinfo</strong>.
- </li>
-</ul>
-<p>
- The Network Monitor and the Video Capture tool work with a hardware device
- only, not the emulator.
-</p>
-
-
-
-<h2 id="displaying">
- Displaying Android Monitor
-</h2>
-
-<p>
- Android Monitor is integrated into the Android Studio main window:
-</p>
-
-<ul>
- <li>To display Android Monitor, click <img src="{@docRoot}images/tools/am-icon.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Android Monitor icon" />,
- which by default is at the bottom of the main window.
- </li>
-
- <li>To hide Android Monitor, click <img src="{@docRoot}images/tools/am-icon.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Android Monitor icon" /> again.
- </li>
- <li>Or select <strong>View</strong> > <strong>Tool Windows</strong> >
- <strong>Android Monitor</strong>.</li>
-</ul>
- <p class="note">
- <strong>Note:</strong> If you don't see the sidebar buttons, you can
- display them by selecting <strong>View</strong> >
- <strong>Tool Buttons</strong>.
- </p>
-<p>
- Android Monitor looks like the following figure:
-</p>
-<img src="{@docRoot}images/tools/am-androidmon2.png" style="vertical-align:sub;margin:0" />
-
-<h2 id="profiling">
- Profiling a Running App in Android Monitor
-</h2>
-
-<p>
- After you've met the prerequisites and optionally connected a hardware device, you're ready
- to profile an app in Android Monitor:
-</p>
-
-<ol>
-
- <li>Open an app project and <a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">run the app</a> on a device or
- emulator.
- </li>
-
- <li>Display Android Monitor and click the tab for the monitor you want to view.
- </li>
- <li>Follow the instructions about using the monitor:
- </li>
- <ul>
- <li><a href="{@docRoot}tools/help/am-logcat.html">logcat Monitor</a>
- </li>
-
- <li><a href="{@docRoot}tools/help/am-memory.html">Memory Monitor</a>
- </li>
-
- <li><a href="{@docRoot}tools/help/am-cpu.html">CPU Monitor</a>
- </li>
-
- <li><a href="{@docRoot}tools/help/am-gpu.html">GPU Monitor</a>
- </li>
-
- <li>
- <a href="{@docRoot}tools/help/am-network.html">Network Monitor</a>
- </li>
- </ul>
-</ol>
- <h2 id="switching">
- Switching between Devices and Apps
- </h2>
-
- <p>
- By default, Android Monitor displays data for your most recently run app. You can switch to
- another device and app as needed. In addition to currently running apps, you can view
- information about apps that are no longer running so you can continue to see any information
- about them that you gathered previously.
- </p>
-
- <p>
- At the top of the Android Monitor main window are two menus listing devices and processes. To
- switch to another device, process, or both:
- </p>
-
- <ol>
- <li>Select the device or emulator.
- </li>
-
- <p>
- The Device menu lists the devices and emulators that are running or have run during your
- current session. There are various status messages that can appear in the Device menu:
- </p>
-
- <ul>
- <li>
- <strong>DISCONNECTED</strong> - You closed an emulator or unplugged a device from the
- computer.
- </li>
-
- <li>
- <strong>UNAUTHORIZED</strong> - A device needs you to accept the incoming computer
- connection. For example, if the connected device displays an <em>Allow USB Debugging</em>
- dialog, click <strong>OK</strong> to allow the connection.
- </li>
-
- <li>
- <strong>OFFLINE</strong> - Android Monitor can’t communicate with a device, even though it
- has detected that device.
- </li>
- </ul>
-
- <li>Select the process.
- </li>
- <p>
- The Process menu lists the processes that are running or have run during your current session. If
- a process is no longer running, the menu displays a status of <strong>DEAD</strong>.
-</p>
-</ol>
-
-
-
-
-<h2 id="rearranging">
- Rearranging Android Monitor Windows
-</h2>
-
-<p>
- You can rearrange the Android Monitor windows for optimal viewing during your
- tests:
-</p>
-<ul>
- <li>To move a monitor up or down, click Move Monitor Up
- <img src="{@docRoot}images/tools/am-imoveup.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Move Monitor Up icon" /> or Move Monitor Down
- <img src="{@docRoot}images/tools/am-imovedown.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Move Monitor Down icon" />.
- </li>
- <li>To minimize or maximize a monitor, click Minimize Monitor
- <img src="{@docRoot}images/tools/am-iminimize.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Minimize Monitor icon" />
- or Maximize Monitor
- <img src="{@docRoot}images/tools/am-imaximize.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Maximize Monitor icon" />.
- </li>
-</ul>
-
-<p>
- To rearrange the <strong>logcat</strong> and <strong>Monitors</strong> tabs:
-</p>
-<ul>
- <li>To reorder the logcat or monitor group, move the tabs back and forth.
- </li>
-
- <li>To move the logcat or monitor group to a standalone window, drag a tab
- to a different location on the screen. Or, select
- <img src="{@docRoot}images/tools/am-igear.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Gear menu icon" /> > <strong>Floating Mode</strong>.
- </li>
-
-
- <li>To dock a standalone window, drag it to the Android Monitor
- tab area.</li>
-
-
- <li>To combine the logcat and monitor group displays together, drag a tab and
- move it onto another monitor.
- </li>
-
- <li>To hide a tab, click the
- <img src="{@docRoot}images/tools/am-ihide.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Hide icon" /> icon. To make it reappear, click Restore Monitors View
- <img src="{@docRoot}images/tools/am-imaximize.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Restore Monitors View icon" />
- or the Restore logcat View
- <img src="{@docRoot}images/tools/am-imaxlogcat.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Restore logcat View icon" />
- on the far right of the row of tabs.
- </li>
-</ul>
-
-<h2 id="terminating">
- Terminating an App
-</h2>
-
-<p>
- To stop an app you’ve run from Android Studio:
-</p>
-
-<ol>
- <li>
- <a href="#switching">Select the device and the process</a> in the Android Monitor
- menus, if needed.
- </li>
-
- <li>Click Terminate Application <img src="{@docRoot}images/tools/am-iterminate.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Terminate App icon" />.
- </li>
-
-
-<p>
- The process status changes to <strong>DEAD</strong> in the Processes menu. The emulator or device
- continues to run, but the app closes. Any running monitors in Android Monitor stop.
-</p>
-</ol>
-
-<h2 id="removing">
- Removing an App from a Device
-</h2>
-
-<p>
- To remove an app from a device you use for development, use the normal uninstall procedure on the
- device.
-</p>
-
-<p>
- If you run a new version of an app from Android Studio that’s been already installed on a
- hardware device, the device displays an <em>Application Installation Failed</em> dialog. Click
- <strong>OK</strong> to install the new version of the app.
-</p>
-
-<h2 id="other">
- Using Other Main Window Features
-</h2>
-<p>
- From the Android Monitor main window, you can also do the following:
-</p>
-
-<ul>
- <li>
- <a href="{@docRoot}tools/help/am-sysinfo.html">Examine <code>dumpsys</code> system information</a>.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-screenshot.html">Take a screen capture of the device</a>.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-video.html">Record a video from the screen</a>.
- </li>
-</ul>
-
+++ /dev/null
-page.title=CPU Monitor
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the CPU Monitor to display CPU usage in real time and the percentage of total CPU time (including all cores) used in user and kernel mode.
-page.image=tools/help/thumbnails/am-cpumon.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#running">Displaying a Running App in the CPU Monitor</a></li>
- <li><a href="#snapshot">Recording Call Stack Changes</a></li>
-</ol>
-
-</div>
-</div>
-
-
-<p>
- The CPU Monitor lets you easily monitor the central processing unit (CPU) usage of your app. It
- displays CPU usage in real time and displays the percentage of total CPU time (including all cores)
- used in user and kernel mode. In user mode, the code must use system APIs to access hardware or
- memory, has access to virtual memory addresses only, and crashes are usually
- recoverable. In kernel mode, the code can directly access
- hardware, including physical memory addresses; crashes halt the device.
-</p>
-
-
-<h2 id="running">
- Displaying a Running App in the CPU Monitor
-</h2>
-
-<p>
- To display an app running on a particular device or emulator in the CPU Monitor:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on a hardware device or
- emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
- <li>Click the <strong>Monitors</strong> tab and <a href=
- "{@docRoot}tools/help/am-basics.html#rearranging">display the CPU Monitor</a>.
- </li>
-
-
- <li>Enable the CPU Monitor by clicking Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> to deselect it.
- </li>
-
-
-<p>
- The CPU Monitor starts to display any CPU usage.
- In the graph, the y-axis displays the percentage of CPU used. The x-axis records the time elapsed
- and starts with seconds, and then minutes and seconds, and so on.
-</p>
-<img src="{@docRoot}images/tools/am-cpumon2.png" style="vertical-align:sub;margin:0" />
- <li>To stop the CPU Monitor, click Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> again to select
- it.
- </li>
-</ol>
-
-<h2 id="snapshot">
- Recording Call Stack Changes
-</h2>
-
-<p>
- You can capture a record of the changes on the call stack during a particular
- time period while the CPU Monitor is running. For more information, see
- <a href="{@docRoot}tools/help/am-methodtrace.html">Method Trace</a>.
-</p>
-
-
-
-
+++ /dev/null
-page.title=GPU Monitor
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the GPU Monitor for a visual representation of how much time it takes to render the frames of a UI window. Use this information to optimize the code that displays graphics and conserve memory.
-page.image=tools/help/thumbnails/am-gpumon.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#running">Displaying a Running App in the GPU Monitor</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>
- The GPU Monitor gives you a quick visual representation of how much time it takes to render the
- frames of a UI window. It profiles the amount of time it takes for the render thread to prepare,
- process, and execute the draw commands. The GPU Monitor can help you to:
-</p>
-
-<ul>
- <li>Quickly see how a UI window performs.
- </li>
-
- <li>Identify whether any part of the rendering pipeline stands out in using processing time.
- </li>
-
- <li>Look for spikes in frame rendering time associated with user or program actions.
- </li>
-</ul>
-
-<p>
- For example, if displaying a static photo continues to take Graphics Processor Unit
- (GPU) resources long after it has finished
- drawing on the screen, that’s a likely candidate for optimization.
-</p>
-
-
-<h2 id="running">
- Displaying a Running App in the GPU Monitor
-</h2>
-
-<p>
- To display an app running on a particular device or emulator in the GPU Monitor:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on a hardware device or
- emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
- <li>Click the <strong>Monitors</strong> tab and <a href=
- "{@docRoot}tools/help/am-basics.html#rearranging">display the GPU Monitor</a>.
- </li>
-
- <li>Enable the GPU Monitor by clicking Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> to deselect it.
- </li>
-
- <p>
- Any GPU usage begins to appear in the GPU Monitor:
-</p>
- <img src="{@docRoot}images/tools/am-gpumon2.png" style="vertical-align:sub;margin:0" />
-
-<p>
- The y-axis is the amount of time it takes the GPU to execute, process, prepare, and draw frames,
- in milliseconds. The x-axis records the time elapsed; it starts with seconds, and then minutes
- and seconds, and so on.
-</p>
-
- <li>To stop the GPU Monitor, click Pause <img src="{@docRoot}images/tools/am-ipause.png" style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> again to select
- it.
- </li>
-</ol>
+++ /dev/null
-page.title=HPROF Viewer and Analyzer
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Memory Monitor to dump the Java heap to an HPROF file. The HPROF Viewer displays classes, instances of each class, and a reference tree to help you track memory usage and find memory leaks.
-page.image=tools/help/thumbnails/am_hprofviewer.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#why">Why Look at the Java Heap?</a></li>
- <li><a href="#display">Understanding the HPROF Viewer Display</a></li>
- <li><a href="#hprof-snapshot">Taking a Snapshot of the Java Heap</a></li>
- <li><a href="#hprof-viewing">Viewing a Saved HPROF File</a></li>
- <li><a href="#hprof-diving">Diving into Heap Dump Data in the HPROF Viewer</a></li>
- <li><a href="#hprof-analyzing">Analyzing Heap Dump Data in the HPROF Analyzer</a></li>
- <li><a href="#hprof-sorting">Sorting Heap Dump Data</a></li>
- <li><a href="#hprof-source">Displaying Java Source</a></li>
- <li><a href="#hprof-files">Working with HPROF Files</a></li>
-
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/articles/memory.html">Managing Your App's Memory</a></li>
- <li><a href="{@docRoot}guide/practices/verifying-apps-art.html#GC_Migration">Addressing Garbage Collection Issues</a></li>
- <li><a href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<p>
- When you're monitoring memory usage in the Memory Monitor you can, at the same time, dump a
- snapshot of the Java heap to an Android-specific Heap/CPU Profiling (HPROF) file. The HPROF Viewer
- displays classes, instances of each class, and a reference tree to help you track memory usage
- and find memory leaks. HPROF is a binary heap dump format originally supported by J2SE.
-</p>
-<h2 id="why">
- Why Look at the Java Heap?
-</h2>
-<p>The Java heap display does the following:</p>
-
-<ul>
- <li>Shows snapshots of a number of objects allocated by type.
- </li>
-
- <li>Samples data every time a garbage collection event occurs naturally or is triggered by you.
- </li>
-
- <li>Helps identify which object types might be involved in memory leaks.
- </li>
-</ul>
-
-<p>
- However, you have to look for changes over time yourself by tracking what's happening in the
- graph.
-</p>
-
-<p>
- The HPROF Analyzer finds the following potential issues:
-</p>
-
-<ul>
- <li>All destroyed activity instances that are reachable from garbage collection roots.
- </li>
-
- <li>Where the target program has strings that repeat values.
- </li>
-</ul>
-
-<p>
- A dominator is at the top of a tree. If you remove it, you also remove the branches of the tree
- it dominates, so it’s a potential way to free memory.
-</p>
-
-<h2 id="display">
- Understanding the HPROF Viewer Display
-</h2>
-
-<p>
- The HPROF Viewer looks similar to the following figure:
-</p>
-<img src="{@docRoot}images/tools/am-hprofviewer.png" />
-<p>
- The tool displays the following information:
-</p>
-
-<table>
- <tr>
- <th scope="col">Column</th>
- <th scope="col">Description</th>
- </tr>
-
- <tr>
- <td><strong>Class Name</strong></td>
- <td>The Java class responsible for the memory.</td>
- </tr>
-
- <tr>
- <td><strong>Total Count</strong></td>
- <td>Total number of instances outstanding.</td>
- </tr>
- <tr>
- <td><strong>Heap Count</strong></td>
- <td>Number of instances in the selected heap.</td>
- </tr>
- <tr>
- <td><strong>Sizeof</strong></td>
- <td>Size of the instances (currently, 0 if the size is variable).</td>
- </tr>
- <tr>
- <td><strong>Shallow Size</strong></td>
- <td>Total size of all instances in this heap.</td>
- </tr>
- <tr>
- <td><strong>Retained Size</strong></td>
- <td>Size of memory that all instances of this class is dominating.</td>
- </tr>
- <tr>
- <td><strong>Instance</strong></td>
- <td>A specific instance of the class.</td>
- </tr>
- <tr>
- <td><strong>Reference Tree</strong></td>
- <td>References that point to the selected instance, as well as references pointing to the
- references.</td>
- </tr>
- <tr>
- <td><strong>Depth</strong></td>
- <td>The shortest number of hops from any GC root to the selected instance.</td>
- </tr>
- <tr>
- <td><strong>Shallow Size</strong></td>
- <td>Size of this instance.</td>
- </tr>
- <tr>
- <td><strong>Dominating Size</strong></td>
- <td>Size of memory that this instance is dominating.</td>
- </tr>
-</table>
-
-<p>If you click <strong>Capture Analysis</strong>, the HPROF Analyzer appears: </p>
-<img src="{@docRoot}images/tools/am-hprofanalyzer.png" />
-<p>You can detect leaked activities and find duplicate strings with the HPROF Analyzer.</p>
-
-<h2 id="hprof-snapshot">
- Taking and Displaying a Snapshot of the Java Heap
-</h2>
-
-<p>
- To examine a snapshot of the Java heap:
-</p>
-
-<ol>
- <li><a href="{@docRoot}tools/help/am-memory.html#displaying">Display a running app in the Memory
- Monitor</a>.</li>
- <li>Click Dump Java Heap
- <img src="{@docRoot}images/tools/am-idump.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Dump Java Heap icon" />.
- </li>
-
-
-<p>
- When the icon on the Memory Monitor display changes from
- <img src="{@docRoot}images/tools/am-idumpstart.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Dump Java Heap Start icon" /> to
- <img src="{@docRoot}images/tools/am-idumpend.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Dump Java Heap End icon" />, the file is ready. Android Studio creates the heap snapshot
- file with the
- filename <code><em>package_yyyy.mm.dd_hh.mm.ss</em>.hprof</code> using
- the activity package (or project) name, year, month, day, hour, minute, and second of the
- capture, for example,
- <code>com.android.calc_2015.11.17_14.58.48.hprof</code>.
-</p>
-<p>
- The HPROF Viewer appears.
-</p>
-</ol>
-
-<h2 id="hprof-viewing">Viewing a Saved HPROF File</h2>
-<p>After you do a heap dump, Android Studio automatically stores it so you can view it again.
- </p>
- <p>To view an HPROF file in the HPROF Viewer:</p>
-
-<ol>
-<li>Click
-<img src="{@docRoot}images/tools/am-icaptures.png"
-style="vertical-align:sub;margin:0;height:17px"
- alt="Captures icon" /> in the main window.</li>
-<p>Or select <strong>View</strong> > <strong>Tools Windows</strong> >
-<strong>Captures</strong>.</p>
-<p>The <em>Captures</em> window appears.</p>
-<li>Open the <strong>Heap Snapshot</strong> folder.</li>
-
-
- <li>Double-click the file to view it in the HPROF Viewer.
- </li>
-<p>
- The HPROF Viewer appears.
-</p>
-
-
- <li>Select the Heap menu option you want to display:
- <ul>
- <li>
- <strong>App heap</strong> - The heap used by the current app.
- </li>
-
- <li><strong>Image heap</strong> - The memory mapped copy of the
- current app on disk.
- </li>
-
-
- <li>
- <strong>Zygote heap</strong> - The common set of libraries and runtime classes and data that
- all apps are forked
- from. The zygote space is created during device startup and is never allocated into.
- </li>
-
- </ul>
-
- <li>Select the View menu option you want to display:
- <ul>
- <li>
- <strong>Class List View</strong>
- </li>
-
- <li>
- <strong>Package Tree View</strong>
- </li>
- </ul>
- </ol>
-
-
-<h2 id="hprof-diving">
- Diving into Heap Dump Data in the HPROF Viewer
-</h2>
-<p>The following steps outline the typical workflow:</p>
-<ol>
-<li>In the HPROF Viewer, select a class name. </li>
-<li>Select an instance of that class.</li>
-<li>Examine the reference tree.</li>
-<li>Right-click an item to <strong>Jump to source</strong> or <strong>Go to instance</strong>,
- as needed.</li>
-</ol>
-
-
-
-<h2 id="hprof-analyzing">Analyzing Heap Dump Data in the HPROF Analyzer</h2>
-<p>You can detect leaked activities and find duplicate strings with the HPROF Analyzer.
- </p>
- <p>To use the HPROF Analyzer:</p>
-<ol>
-<li>In the <em>Captures</em> window, double-click an <code>.hprof</code> file to display it in the
- HPROF Viewer. </li>
-<li>Click <strong>Capture Analysis</strong> on the right side of the main Android Studio window.</li>
-
-
-<p>The HPROF Analyzer appears to the right of the HPROF Analyzer, by default.</p>
-
-
-
-<li>In the <strong>Analyzer Tasks</strong> list, select the items you want to find.</li>
-<li>Click Perform Analysis <img src="{@docRoot}images/tools/am-iperformanalysis.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Perform Analysis icon" />.</li>
-<li>Examine the items in <strong>Analysis Results</strong>. Click an item to display it in the
- HPROF Viewer.</li>
-</ol>
-
-
-
-<h2 id="hprof-sorting">Sorting Heap Dump Data</h2>
-<p>To sort heap dump data:</p>
-<ul>
-<li>In the HPROF Viewer, click a column heading to sort the table by ascending or descending
- order. </li>
-</ul>
-
-
-<h2 id="hprof-source">Displaying Java Source</h2>
-<p>For some items displayed in the HPROF Viewer, you can go straight to its
-source code.
-</p>
-<p>To display Java source:</p>
-<ul>
-<li>In the HPROF Viewer, right-click a class, instance, or item in the reference tree, and then
- select <strong>Jump to Source</strong>. </li>
-
-
-<p>The source code appears in the Code Editor.</p>
-</ul>
-
-<h2 id="hprof-files">Working with HPROF Files</h2>
-<p>You can rename, locate, and delete an HPROF file from within Android Studio.
-You can also convert it to standard HPROF format to use with other analysis
-tools.</p>
-
-<h3 id="hprof-renaming">Renaming an HPROF file</h3>
-
-<p>If you rename a file from within Android Studio, it continues to appear in
-the <em>Captures</em> window.</p>
-<p>To rename an HPROF file:</p>
-<ol>
-<li>In the <em>Captures</em> window, right-click the file and select <strong>Rename</strong>. </li>
-<li>In the dialog, specify the name of the file and click <strong>OK</strong>.</li>
-</ol>
-
-
-<h3 id="hprof-locating">Locating a heap dump file on disk</h3>
-<p>You can quickly discover where Android Studio stored HPROF files on disk.</p>
-
-
-<p>To locate an HPROF file on disk: </p>
-<ul>
-<li>In the <em>Captures</em> window, right-click a heap snapshot file and select
- <strong>Show</strong> or <strong>Reveal</strong>.</li>
-
-<p>Android Studio opens an operating system file browser displaying the location where the file
- resides.</p>
-</ul>
-<p class="note"><strong>Note:</strong> If you move an HPROF file, Android Studio no longer
- displays it in the <em>Captures</em> window. To display it, use
- <strong>File</strong> > <strong>Open</strong>. Also, if you want to rename the file, do it
- from the <em>Captures</em> window and not in the operating system file browser. </p>
-
-<h3 id="hprof-deleting">Deleting a heap dump file</h3>
-
-<p>To delete a heap dump file: </p>
-<ul>
-<li>In the <em>Captures</em> window, right-click a heap snapshot file and select
- <strong>Delete</strong>.</li>
-
-<p>Android Studio deletes the file from the <em>Captures</em> dialog and from disk. </p>
-</ul>
-
-<h3 id="hprof-converting">Converting a heap dump file to standard HPROF format</h3>
-<p>You can convert an HPROF file to standard format so you can use it outside of Android Studio with
- other analysis tools. </p>
- <p>To convert an HPROF file:</p>
-<ol>
-<li>In the <em>Captures</em> window, right-click a heap snapshot file and select <strong>Export to
- standard .hprof</strong>.</li>
-<li>In the <em>Convert Android Java Heap Dump</em> dialog, specify a filename and click
- <strong>OK</strong>.</li>
-
-
-<p>Android Studio creates a binary HPROF file in the location you specified.</p>
-</ol>
+++ /dev/null
-page.title=logcat Monitor
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the logcat Monitor to view system and user-defined log messages. You can filter the messages to display just the items that interest you.
-page.image=tools/help/thumbnails/am-logcatmon2.png
-page.article=true
-
-@jd:body
-<div id="qv-wrapper">
- <div id="qv">
- <h2>
- In this document
- </h2>
-
- <ol>
- <li>
- <a href="#format">logcat Message Format</a>
- </li>
-
- <li>
- <a href="#running">Displaying a Running App in the logcat Monitor</a>
- </li>
-
- <li>
- <a href="#level">Setting the Log Level</a>
- </li>
-
- <li>
- <a href="#searching">Searching logcat Messages</a>
- </li>
-
- <li>
- <a href="#filtering">Filtering logcat Messages</a>
- </li>
-
- <li>
- <a href="#logheader">Configuring the logcat Header Display</a>
- </li>
-
- <li>
- <a href="#stack">Moving Up and Down the Stack Trace</a>
- </li>
-
- <li>
- <a href="#logend">Moving to the End of the Log</a>
- </li>
-
- <li>
- <a href="#printing">Printing and Writing to a File</a>
- </li>
-
- <li>
- <a href="#clearing">Clearing and Restarting the Log</a>
- </li>
-
- </ol>
-
- <h2>
- See also
- </h2>
-
- <ol>
- <li>
- <a href="{@docRoot}tools/debugging/debugging-log.html">Reading and Writing Logs</a>
- </li>
- </ol>
-
- </div>
-</div>
-
-<p>
- The Android logging system provides a mechanism for collecting and viewing system debug output.
- The logcat Monitor displays system messages, such as when a garbage collection occurs, as well as
- messages that you added to your app by using the <a href=
- "{@docRoot}reference/android/util/Log.html">Log</a> class.
- It displays messages in real time and also keeps a history so you can view older
- messages.
-</p>
-
-<p>
- To display just the information of interest, you can create filters, modify how much information
- is displayed in messages, set priority levels, display messages produced by app code
- only, and search the log. By default, the logcat Monitor shows the log output related to the
- most recently run app only.
-</p>
-
-<p>
- When an app throws an exception, the logcat Monitor shows a message followed by the associated
- stack trace containing links to
- the code. This feature can help you fix errors and improve app operation.
-</p>
-
-<h2 id="format">
- logcat Message Format
-</h2>
-
-<p>
- Every Android log message has a tag and a priority associated with it. The tag of a system
- log message
- is a short string indicating the system component from which the message originates (for example,
- {@link android.app.ActivityManager}). A user-defined tag can be any string that you find helpful,
- such as the name of the current class (the recommended tag). You define it in a
- {@link android.util.Log} method call, for example:
-</p>
-
-<pre>
-Log.d(tag, message);
-</pre>
-<p>
- The priority is one of the following values:
-</p>
-
-<ul>
- <li>
- <strong>V</strong> — Verbose (lowest priority)
- </li>
-
- <li>
- <strong>D</strong> — Debug
- </li>
-
- <li>
- <strong>I</strong> — Info
- </li>
-
- <li>
- <strong>W</strong> — Warning
- </li>
-
- <li>
- <strong>E</strong> — Error
- </li>
-
- <li>
- <strong>A</strong> — Assert
- </li>
-</ul>
-
-<p>
- The log message format is:
-</p>
-
-<pre class="no-pretty-print">
-<em>date time PID-TID/package priority/tag: message</em>
-</pre>
-
-<p>
- For example, the following log message has a priority of <code>V</code> and a tag of
- <code>AuthZen</code>:
-</p>
-
-<pre class="no-pretty-print">
-12-10 13:02:50.071 1901-4229/com.google.android.gms V/AuthZen: Handling delegate intent.
-</pre>
-<p>
- PID stands for process identifier and TID is thread identifier; they can be the same if there’s
- only one thread.
-</p>
-
-<h2 id="running">
- Displaying a Running App in the logcat Monitor
-</h2>
-
-<p>
- To display the log messages for a particular app:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on a hardware device or
- emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
-
- <li>Click the <strong>logcat</strong> tab.
- </li>
-
-
-<p>
- By default, the logcat Monitor displays just the log messages for your app running on the
- device or emulator:
-</p>
-<img src="{@docRoot}images/tools/am-logcatmon2.png" />
-<p>
- To change this default, see <a href="#filtering">Filtering logcat Messages</a>.
-</p>
-<li>Optionally <a href=
- "{@docRoot}tools/help/am-basics.html#switching">select a different device, emulator, or process</a>.
- </li>
-</ol>
-
-<h2 id="level">
- Setting the Log Level
-</h2>
-
-<p>
- You can control how many messages appear in the logcat Monitor by setting the log level. You can
- display all messages, or just the messages indicating the most severe conditions.
-</p>
-
-<p>
- Remember that the logcat Monitor continues to collect all messages regardless of the log level setting.
- The setting just determines what the logcat Monitor displays.
-</p>
-
-<p>
- To set the log level:
-</p>
-
-<ul>
- <li>In the <strong>Log level</strong> menu, select one of the following values:
- </li>
-
- <ul>
- <li>
- <strong>Verbose</strong> - Show all log messages (the default).
- </li>
-
- <li>
- <strong>Debug</strong> - Show debug log messages that are useful during development only,
- as well as the message levels lower in this list.
- </li>
-
- <li>
- <strong>Info</strong> - Show expected log messages for regular usage, as well as the
- message levels lower in this list.
- </li>
-
- <li>
- <strong>Warn</strong> - Show possible issues that are not yet errors, as well as the
- message levels lower in this list.
- </li>
-
- <li>
- <strong>Error</strong> - Show issues that have caused errors, as well as the message level
- lower in this list.
- </li>
-
- <li>
- <strong>Assert</strong> - Show issues that the developer expects should never happen.
- </li>
- </ul>
-
-</ul>
-
- <h2 id="searching">
- Searching logcat Messages
- </h2>
-
- <p>
- To search the messages currently displayed in the logcat Monitor:
- </p>
-
- <ol>
- <li>Optionally select <strong>Regex</strong> if you want to use a regular expression
- search pattern.
- </li>
-
- <li>Type a character sequence in the search field <img src="{@docRoot}images/tools/am-isearch.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Search icon" />.
- </li>
-
- <p>
- The logcat Monitor display changes accordingly.
- </p>
- </li>
-
- <li>Press Enter to store the search string in the menu during this session.
- </li>
-
- <li>To repeat a search, choose it from the search menu. Select or deselect
- <strong>Regex</strong> as needed (the setting isn’t remembered).
- </li>
- </ol>
-
- <h2 id="filtering">
- Filtering logcat Messages
- </h2>
-
- <p>
- One way to reduce the log output to a manageable level is to restrict it by using a filter.
- </p>
-
- <p class="note">
- <strong>Note:</strong> The filter applies to your full logcat history, not just those messages
- currently displayed in the logcat Monitor. Make sure your other display options are set
- appropriately so you can see the filter output you want to examine.
- </p>
-
- <p>
- To define and apply a filter:
- </p>
-
- <ol>
- <li>In the filter menu, select a filter option:
- <ul>
- <li>
- <strong>Show only selected application</strong> - Display the messages produced by the
- app code only (the default). The logcat Monitor filters the log messages using the PID
- of the active app.
- </li>
-
- <li>
- <strong>No Filters</strong> - Apply no filters. The logcat Monitor
- displays all log messages from the device, regardless of which process you selected.
- </li>
-
- <li>
- <strong>Edit Filter Configuration</strong> - Create or modify a custom filter. For
- example, you could create a filter to view log messages from two apps at the same time.
- </li>
- </ul>
-
- <p>
- After you define filters, you can also select them in the menu. To remove them from the
- menu, delete them.
- </p>
-
- <li>If you selected <strong>Edit Filter Configuration</strong>, create or modify a
- filter.
- <ol type="a">
- <li>Specify the filter parameters in the <em>Create New Logcat Filter</em> dialog:
- </li>
-
-
- <ul>
- <li>
- <strong>Filter Name</strong> - Type the name of a filter you want to define, or
- select it in the left pane to modify an existing filter. The name can contain
- lowercase characters, underscores, and digits only.
- </li>
-
- <li>
- <strong>Log Tag</strong> - Optionally specify a tag. For more information, see
- <a href="#format">logcat Message Format</a>.
- </li>
-
- <li>
- <strong>Log Message</strong> - Optionally specify log message text. For more
- information, see <a href="#format">logcat Message Format</a>.
- </li>
-
- <li>
- <strong>Package Name</strong> - Optionally specify a package name. For more
- information, see <a href="#format">logcat Message Format</a>.
- </li>
-
- <li>
- <strong>PID</strong> - Optionally specify a process ID. For more information, see
- <a href="#format">logcat Message Format</a>.
- </li>
-
- <li>
- <strong>Log Level</strong> - Optionally select a log level. For more information,
- see <a href="#level">Setting the Log Level</a>.
- </li>
-
- <li>
- <strong>Regex</strong> - Select this option to use regular expression syntax for
- that parameter.
- </li>
- </ul>
-
- <li>
- Click <strong>+</strong> to add the filter definition to the left pane.
- </li>
-
- <p>
- To remove a filter, select it in the left pane and click <strong>-</strong>.
- </p>
-
- <li>
- When you’re finished, click <strong>OK</strong>. If you click
- <strong>Cancel</strong>, any filter additions or modifications are lost.
- </li>
- </ol>
- <li>
- Make sure you see the log messages you want to examine.
- </li>
- <p>
- If you don't think you see the log messages you want, try selecting
- <strong>No filters</strong> and <a href="#searching">searching</a> for particular
- log messages.
- </p>
- </ol>
-
- <h2 id="logheader">
- Configuring the logcat Header Display
- </h2>
-
- <p>
- To customize the header display to show just the information you’re interested
- in:
- </p>
-
- <ul>
- <li>Select Use Soft Wraps <img src="{@docRoot}images/tools/am-isoftwraps.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Use Soft Wraps icon" />
- to see the entire
- message and prevent it from running off of the right edge.
- </li>
-
- <li>Click Configure Logcat Header <img src="{@docRoot}images/tools/am-igear.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Configure Logcat header icon" />
- to specify
- elements of the messages that you want to show or hide, and then click
- <strong>OK</strong>.
- </li>
- </ul>
-
- <p>
- For more information about message elements, see <a href=
- "#format">logcat Message Format</a>.
- </p>
-
- <h2 id="stack">
- Moving Up and Down the Stack Trace
- </h2>
-
- <p>
- When the app throws an exception, the message includes a stack trace of method calls.
- logcat
- Monitor lets you quickly locate stack traces in the log and view the associated code
- in the Code Editor. If needed (and possible), the decompiler derives source code that
- you can view.
- </p>
- <p>
- To move up and down the stack trace, and view the associated code in the Code Editor:
- </p>
- <ul>
- <li>Click Up the Stack Trace <img src="{@docRoot}images/tools/am-iupstack.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Up the Stack Trace icon" />
- to move to the
- previous method in relation to the current position in the log.
- </li>
-
- <li>Click Down the Stack Trace <img src="{@docRoot}images/tools/am-idownstack.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Down the Stack Trace icon" />
- to move to
- the next method in relation to the current position in the log.
- </li>
- </ul>
-
- <h2 id="logend">
- Moving to the End of the Log
- </h2>
-
- <p>
- Clicking a particular message stops the display of messages.
- </p>
- <p>
- To quickly move to
- the end of the log to see the real-time message flow:
- </p>
-
-<ul>
- <li>Click Scroll to the End <img src="{@docRoot}images/tools/am-iscrollend.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Scroll to the End icon" />.
- </li>
-
- <li>Press the End key.
- </li>
-
- <li>Scroll or press the Page Down key until you reach the end.
-</li>
-</ul>
-
-<h2 id="printing">
- Printing and Writing to a File
-</h2>
-<p>
- To preserve log information, you can send the log to a printer, write the log to a PDF file, or
- copy and paste the log into a text file.
-</p>
-<p>
- To print the log or write it to a PDF file:
-</p>
-<ol>
- <li>Click Print <img src="{@docRoot}images/tools/am-iprint.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Print icon" />.
- </li>
- <li>
- In the Android Studio <em>Print</em> dialog, optionally change print parameters, and then click
- <strong>Print</strong>.
- </li>
- <li>
- In the operating system <em>Print</em> dialog, optionally change print parameters, and then click
- <strong>Print</strong>.
- </li>
- <p>
- You can set the parameters to send the log to a printer or write it to a PDF file.
-</p>
-</ol>
-<p>
- To copy the log to a text file:
-</p>
-<ol>
- <li>In the logcat Monitor, select and then copy log text.
- </li>
- <p>Press Ctrl+A (⌘A) to select all.</p>
- <li>
- Open a text editor and paste the text into a file.
- </li>
-</ol>
-
-<h2 id="clearing">
- Clearing and Restarting the Log
-</h2>
-<p>
- To clear (flush) the entire log:
-</p>
-<ul>
- <li>Click Clear logcat <img src="{@docRoot}images/tools/am-iclear.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Clear logcat icon" />.
- </li>
-</ul>
-
-
-<p>
- If there's a problem and the log is no longer progressing, you can restart the log:
-</p>
-
-<ul>
- <li>Click Restart <img src="{@docRoot}images/tools/am-irestart.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Restart icon" />.
- </li>
-</ul>
\ No newline at end of file
+++ /dev/null
-page.title=Memory Monitor
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Memory Monitor to evaluate memory usage and find deallocated objects, locate memory leaks, and track the amount of memory the connected device is using.
-page.image=tools/help/thumbnails/am-memorymon.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#workflow">Memory Monitor Workflow</a>
- <ol>
- <li><a href="#treeroot">Garbage collection roots and dominator trees</a></li>
- <li><a href="#analysis">Memory leak and use analysis</a></li>
- <li><a href="#vm">Memory management for different virtual machines</a></li>
- </ol>
- </li>
- <li><a href="#displaying">Displaying a Running App in the Memory Monitor</a></li>
- <li><a href="#forcing">Forcing a Garbage Collection Event</a></li>
- <li><a href="#snapshot">Taking a Snapshot of the Java Heap and Memory Allocation</a></li>
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/articles/memory.html">Managing Your App's Memory</a></li>
- <li><a href="{@docRoot}guide/practices/verifying-apps-art.html#GC_Migration">Addressing Garbage Collection Issues</a></li>
- <li><a href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>
- Android Studio provides a Memory Monitor so you can more easily monitor app performance and
- memory usage to find deallocated objects, locate memory leaks, and track the amount of memory the
- connected device is using. The Memory Monitor reports how your app allocates memory and helps you
- to visualize the memory your app uses. It lets you:
-</p>
-
-<ul>
- <li>Show a graph of available and allocated Java memory over time.
- </li>
-<li>Show garbage collection (GC) events
- over time.
- </li>
- <li>Initiate garbage collection events.
- </li>
-
- <li>Quickly test whether app slowness might be related to excessive garbage collection events.
- </li>
-
- <li>Quickly test whether app crashes may be related to running out of memory.
- </li>
-</ul>
-
-<h2 id="workflow">
- Memory Monitor Workflow
-</h2>
-
-<p>
- To profile and optimize memory use, the typical workflow is to run your app and do the following:
-</p>
-
-<ol>
- <li>Profile the app using the Memory Monitor to find out whether undesirable garbage collection
- event patterns might be causing performance problems.
- </li>
-
- <li>If you see many garbage collection events in a short amount of time, dump the Java heap to
- identify candidate object types that get or stay allocated unexpectedly or unnecessarily.
- </li>
-
- <li>Start allocation tracking to determine where any problems are happening in your code.
- </li>
-</ol>
-
-<p>
- The Java heap data shows in real-time what types of objects your application has allocated, how
- many, and their sizes on the heap. Viewing the heap helps you to:
-</p>
-
-<ul>
- <li>Get a sense of how your app allocates and frees memory.
- </li>
-
- <li>Identify memory leaks.
- </li>
-</ul>
-
-<p>
- Allocation tracking records app memory allocations and lists all allocations for the
- profiling cycle, including the call stack, size, and allocating code. It helps you to:
-</p>
-
-<ul>
- <li>Identify where many similar object types, from roughly the same call stack, are allocated and
- deallocated over a very short period of time.
- </li>
-
- <li>Find the places in your code that may contribute to inefficient memory use.
- </li>
-</ul>
-
-<h3 id="treeroot">
- Garbage collection roots and dominator trees
-</h3>
-
-<p>
- When you dump the Java heap, the Memory Monitor creates an Android-specific Heap/CPU Profiling
- (HPROF) file that you can view in the HPROF Viewer. The HPROF Viewer indicates a garbage
- collection root with the <img src="{@docRoot}images/tools/am-igcroot.png"
- style="vertical-align:sub;margin:0;height:17px" alt="GC Root icon" /> icon (and a depth of zero)
- and a
- dominator with the <img src="{@docRoot}images/tools/am-idom.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Dominator icon" /> icon.
-</p>
-
-<p>
- There are several kinds of garbage collection roots in Java:
-</p>
-
-<ul>
-<li>references on the stack</li>
-<li>Java Native Interface (JNI) native objects and memory</li>
-<li>static variables and functions</li>
-<li>threads and objects that can be referenced </li>
-<li>classes loaded by the bootstrap loader</li>
-<li>finalizers and unfinalized objects</li>
-<li>busy monitor objects</li>
-</ul>
-
-<p>
- The HPROF file provides the list of roots to the HPROF Viewer.
-</p>
-
-<p>
- A dominator tree traces paths to objects created by the app. An object dominates another object
- if the only way to reach the other object is, directly or indirectly, through the dominator
- object. When you examine objects and paths created by an app in an effort to optimize memory use,
- try to remove objects that are no longer needed. You can release a dominator object to
- release all subordinate objects. For example, in the following figure, if you were to
- remove object B, that would also release the memory used by the objects it dominates, which are
- objects C, D, E, and F. In fact, if objects C, D, E, and F were marked for removal, but object B
- was still referring to them, that could be the reason that they weren’t released.
-</p>
-
- <img src="{@docRoot}images/tools/am-domtree.png" height="200" />
-
-<h3 id="analysis">
- Memory leak and use analysis
-</h3>
-
-<p>
- An app performs better if it uses memory efficiently and releases the memory when it’s no longer
- needed.
- Memory leaks that are large or that grow over time are the most important to correct.
-</p>
-
-<p>
- One way to optimize memory usage is to analyze large arrays. For example, can you reduce the size
- of individual elements in the array to save memory?
-</p>
-
-<p>
- Another area that deserves attention is objects that the app no longer needs but continues to
- reference. You can gather heap dumps over different periods of time and compare them to determine
- if you have a growing memory leak, such as an object type that your code creates multiple times
- but doesn’t destroy. These objects could be part of a growing array or an object tree, for
- example. To track down this problem, compare the heap dumps and see if you have a particular
- object type that continues to have more and more instances over time.
-</p>
-
-<p>
- Continually growing object trees that contain root or dominator objects can prevent subordinate
- objects from being garbage-collected. This issue is a common cause of memory leaks, out-of-memory
- errors,
- and crashes. Your app could have a small number of objects that are preventing a large number of
- subordinate objects from being destroyed, so it runs out of memory quickly. To find these issues,
- get a heap dump and examine the amount of memory held by root and dominator objects. If the
- memory is substantial, you’ve likely found a good place to start optimizing your memory use.
-</p>
-
-<p>
- As you start narrowing down memory issues, you should also use the Allocation Tracker to get a
- better understanding of where your memory-hogging objects are allocated. The Allocation Tracker
- can be valuable not only for looking at specific uses of memory, but also for analyzing critical
- code paths, such as loading and scrolling. For example, tracking allocations when flinging a list
- in your app
- allows you to see all of the allocations that need to be done for that behavior, what thread they
- are on, and where they came from. This information is extremely valuable for tightening up these
- paths to reduce the work they need and improve the overall smoothness of the UI.
-</p>
-
-<p>
- It’s useful to examine your algorithms for allocations that are unnecessary or that create the
- same object many times instead of reusing them. For example, do you create temporary objects and
- variables within recursive loops? If so, try creating an object or variable before
- the loop for use within the loop. Otherwise, your app might needlessly allocate many objects and
- variables, depending on the number of recursions.
-</p>
-
-<p>
- It’s important to perform allocation tests on portions of your code that create the most and
- largest objects, as those areas offer the most optimization opportunities. In addition to unit
- tests, you should test your app with production-realistic data loads, especially those algorithms
- that are data-driven. Also, make sure to account for the app caching and startup phase, which can
- sometimes be slow; allocation analysis is best done after that phase to produce accurate results.
-</p>
-
-<p>
- After you optimize code, be sure to test that it worked. You need to test under different load
- conditions and also without running the Memory Monitor tools. Compare results before and after
- optimization to make sure that performance has actually improved.
-</p>
-
-<h3 id="vm">
- Memory management for different virtual machines
-</h3>
-
-<p>
- Android Monitor uses the Virtual Machine (VM) that the device or emulator uses:
-</p>
-
-<ul>
- <li>Android 4.3 (API level 18) and lower uses the Dalvik VM.
- </li>
-
- <li>In Android 4.4 (API level 19), the Android RunTime (ART) VM is an option, while the Dalvik VM
- is the default.
- </li>
-
- <li>Android 5.0 (API level 21) and higher uses the ART VM.
- </li>
-</ul>
-
-<p>
- The VM handles garbage collection. The Dalvik VM uses a mark-and-sweep scheme for garbage
- collection. The ART VM uses a generational scheme, combined with mark-and-sweep when memory needs
- a more thorough garbage collection, such as when memory becomes excessively fragmented. The
- logcat Monitor displays some messages that indicate the type of garbage collection that occurred
- and why.
-</p>
-
-<p>
- Memory Monitor results can vary between the different VMs. As a result, if you’re supporting both
- VMs, you might want to test with both. In addition, the VMs available for different API levels
- can have different behavior. For example, the Dalvik VM in Android 2.3 (API level 10) and lower
- uses externally allocated memory while higher versions allocate in the Dalvik heap only.
-</p>
-
-<p>
- You can’t reconfigure the Dalvik and ART VMs to tune performance. Instead, you should examine
- your app code to determine how to improve its operation, for example, reducing the size of very
- large arrays.
-</p>
-
-<p>
- There are programmatic ways to manipulate when the VM performs garbage collection, although it’s
- not a best practice. These techniques can be specific to the VM. For more information, see
- <a href=
- "{@docRoot}guide/practices/verifying-apps-art.html#GC_Migration">Addressing
- Garbage Collection (GC) Issues</a> and <a href=
- "{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM
- Usage</a>.
-</p>
-
-<p>
- The ART VM adds a number of performance, development, and debugging improvements over the Dalvik
- VM. For more information, see <a href=
- "https://source.android.com/devices/tech/dalvik/index.html">ART and Dalvik</a>.
-</p>
-
-<h2 id="displaying">
- Displaying a Running App in the Memory Monitor
-</h2>
-
-<p>
- To display an app running on a particular device or emulator in the Memory Monitor:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on a hardware device or
- emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
- <li>Click the <strong>Monitors</strong> tab and <a href=
- "{@docRoot}tools/help/am-basics.html#rearranging">display the Memory Monitor</a>.
- </li>
-
-
- <li>Enable the Memory Monitor by clicking Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> to deselect it.
- </li>
-
-
-<p>
- In the graph, the y-axis displays the free and allocated RAM in megabytes. The x-axis shows the
- time elapsed; it starts with seconds, and then minutes and seconds, and so on. The amount of free
- memory, measured in megabytes,
- is shown in a light color, and allocated memory is a darker color. When there’s a sharp drop in
- allocated memory, that indicates a garbage collection event. </p>
-
-
-
-<p>
- To force a garbage collection event, click Initiate GC <img src="{@docRoot}images/tools/am-igc.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Initiate GC icon" />.
-</p>
-
- <p>In the following figure, the VM initiated the first garbage collection event, while the
- developer forced the second.
-</p>
-<img src="{@docRoot}images/tools/am-gc2.png" />
-
- <li>Interact with your app and watch how it affects memory usage in the Memory Monitor. You can
- identify garbage collection patterns for your app and determine whether they're healthy and what
- you expect.
- </li>
-
-
-<p>
- The graph can show you potential issues:
-</p>
-
-<ul>
- <li>Excessive garbage collection events slow down the app.
- </li>
-
- <li>The app runs out of memory, which causes it to crash.
- </li>
-
- <li>Potential memory leaks.
- </li>
-</ul>
-
-<p>
- For example, you might see the following signs of problems:
-</p>
-
-<ul>
- <li>Your app is static, but you see memory being allocated in the monitor.
- </li>
-
- <li>You see spikes of memory allocations in the monitor, but you don’t think there’s any app
- logic to cause this behavior.
- </li>
-</ul>
- <li>To stop the Memory Monitor, click Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> again to select it.
- </li>
-
-</ol>
-
-<h2 id="forcing">
- Forcing a Garbage Collection Event
-</h2>
-
-<p>
- Normally, VMs perform garbage collection only when absolutely needed, since it’s expensive.
- However, it can be useful to force garbage collection in certain circumstances. For example, when
- locating memory leaks, if you want to determine whether a large object was successfully released
- already, you can initiate garbage collection much more aggressively than usual.
-</p>
-
-<p>
- To force a garbage collection event:
-</p>
-
-<ul>
- <li>While the <a href="#displaying">Memory Monitor is running</a>, click Initiate GC
- <img src="{@docRoot}images/tools/am-igc.png" style="vertical-align:sub;margin:0;height:17px"
- alt="Initiate GC icon" />.
- </li>
-</ul>
-
-<h2 id="snapshot">
- Taking a Snapshot of the Java Heap and Memory Allocation
-</h2>
-
-<p>
- You can take snapshots while the Memory Monitor is running or paused:
-</p>
-
-<ul>
- <li>To take and display a snapshot of the Java heap, see <a href=
- "{@docRoot}tools/help/am-hprof.html">HPROF Viewer and Analyzer</a>.
- </li>
- <li>To take and display a snapshot of memory allocation, see <a href=
- "{@docRoot}tools/help/am-allocation.html">Allocation Tracker</a>.
- </li>
-</ul>
-
+++ /dev/null
-page.title=Method Trace
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the CPU Monitor to perform a method trace on your app. View call stack and timing information in the method trace display.
-page.image=tools/help/thumbnails/am_methodtrace.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
-<li><a href="#display">Understanding the Method Trace Display</a></li>
- <li><a href="#trace">Performing a Method Trace in the CPU Monitor</a></li>
- <li><a href="#viewtrace">Viewing a Saved Method Trace</a></li>
- <li><a href="#sorttrace">Sorting Method Trace Data</a></li>
- <li><a href="#trace-files">Working with Method Trace Files</a></li>
-</ol>
-
-</div>
-</div>
-
-
-<p>
- You can start a method trace from the CPU Monitor. It lets you view the call stack and timing
- information for your app. This information can help you optimize and debug your app.
-</p>
-
-<h2 id="display">
- Understanding the Method Trace Display
-</h2>
-
-<p>
- The method trace looks similar to the following figure:
-</p>
-<img src="{@docRoot}images/tools/am-methodtrace.png" alt="Method Trace" />
-<p></p>
-
-<p>The display shows the following information:</p>
-
-<table>
- <tr>
- <th scope="col">Field</th>
- <th scope="col">Description</th>
- </tr>
-
- <tr>
- <td><strong>Name</strong></td>
- <td>The name of the method.</td>
- </tr>
-
- <tr>
- <td><strong>Invocation Count</strong></td>
- <td>How many times the method was called.</td>
- </tr>
-
- <tr>
- <td><strong>Inclusive Time (microseconds)</strong></td>
- <td>Time spent in the method and all of its children, either wall clock or thread time,
- depending on your selection in the <strong>x-axis</strong> menu.</td>
- </tr>
-
- <tr>
- <td><strong>Exclusive Time (microseconds)</strong></td>
- <td>Time spent just in the method (excluding time spent in its children), either wall clock
- or thread time, depending on your selection in the <strong>x-axis</strong> menu.</td>
- </tr>
-</table>
-
-<p class="note"><strong>Note:</strong> Running the method trace significantly affects CPU timings.
- Use the method trace to understand the flow of the program, but not for performance timings.</p>
-
-<h2 id="trace">
- Performing a Method Trace in the CPU Monitor
-</h2>
-
-<p>
- To perform a method trace:
-</p>
-
-<ol>
- <li>
- <a href="{@docRoot}tools/help/am-cpu.html#running">Display a running app in the CPU
- Monitor</a>.
- </li>
-
- <li>Start a trace by clicking Start Method Tracing <img src="{@docRoot}images/tools/am-imethodtrace.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Start Method Tracing icon" /> to
- select it.
- </li>
-
- <li>To stop the trace, click Stop Method Tracing <img src="{@docRoot}images/tools/am-imethodtrace.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Stop Method Tracing icon" /> to
- deselect it.
- </li>
-
-<p>
- The method trace appears in the Code Editor area.
-</p>
-
-<p>
- Android Studio creates the method trace file
- with the filename <code><em>package_yyyy.mm.dd_hh.mm.ss</em>.trace</code>
- using the activity package (or project) name, year, month, day, hour, minute, and second of
- the capture, for example,
- <code>com.android.calc_2015.11.17_14.58.48.trace</code>.
-</p>
- <li>Specify display options:
- <ul>
- <li>Select a <strong>Thread</strong>.
- </li>
-
- <li>Select an <strong>x-axis</strong> time for the graphic and the method list:
- </li>
-
- <ul>
- <li>
- <strong>Wall Clock Time</strong> - Total CPU time elapsed between the method call and
- return.
- </li>
-
- <li>
- <strong>Thread Time</strong> - Total time during which the JRE scheduled the
- thread during call processing. It’s less than or equal to the Wall Clock Time: less if
- the JRE interrupted the thread, and equal if it didn’t.
- The thread might not run continuously; when it’s not executing, that time is excluded.
- If threads are interrupted often and it’s not by design, the interruptions affect app
- performance. However, an example of a by-design use is synchronous operations that take
- a long time, such as file transfers and reads from disk, where the method could be the
- asynchronous wrapper for the synchronous reader.
- </li>
- </ul>
-
- <li>
- Optionally select <strong>Color by inclusive time</strong>.
- </li>
- </ul>
-
-
-
- <p>
- The graphic represents the wall clock or thread time for each method. Hover the cursor
- over the display to receive information about the method. This information also appears
- in the table.
- </p>
-</ol>
- <h2 id="viewtrace">
- Viewing a Saved Method Trace
- </h2>
-
- <p>
- After you do a method trace, Android Studio automatically stores it so you can view it
- again.</p>
-
- <p>To examine a saved method trace:
- </p>
-
- <ol>
- <li>Click
- <img src="{@docRoot}images/tools/am-icaptures.png"
- style="vertical-align:sub;margin:0;height:17px"
- alt="Captures icon" /> in the main window.
- </li>
- <p>Or select <strong>View</strong> > <strong>Tools Windows</strong> >
- <strong>Captures</strong>.</p>
-
- <p>
- The <em>Captures</em> window appears.
- </p>
-
- <li>Open the <strong>Methods Tracing</strong> folder.
- </li>
-
- <li>Double-click the file to view it.
- </li>
-</ol>
-
-<h2 id="sorttrace">
- Sorting Method Trace Data
-</h2>
-
-<p>
- You can sort the data by method name, count, inclusive time, and exclusive
- time.</p>
-
- <p>To sort method trace data:</p>
-
-
-<ul>
- <li>Click a column heading to sort the table by ascending or descending order.
- </li>
-</ul>
-
-<h2 id="trace-files">Working with Method Trace Files</h2>
-<p>You can rename, locate, and delete a method trace file from within Android
-Studio.</p>
-
-<h3 id="renametrace">
- Renaming a method trace file
-</h3>
-
-<p>
- Rename a method trace file from within Android Studio so it
- continues to appear in the <em>Captures</em> window.</p>
-
- <p>To rename a method trace file:
-</p>
-
-<ol>
- <li>In the <em>Captures</em> window, right-click the file and select <strong>Rename</strong>.
- </li>
-
- <li>In the dialog, specify the name of the file and click <strong>OK</strong>.
- </li>
-</ol>
-
-<h3 id="locatetrace">
- Locating a method trace file on disk
-</h3>
-
-<p>
- You can quickly discover where Android Studio stored method trace files on
- disk.</p>
-
- <p>To locate a method trace file on disk:
-</p>
-
-
-
-<ul>
- <li>In the <em>Captures</em> window, right-click a method trace file and
- select <strong>Show</strong> or <strong>Reveal</strong>.
- </li>
-
-<p>
- Android Studio opens an operating system file browser displaying the location where the file
- resides.
-</p>
-</ul>
-<p class="note">
- <strong>Note:</strong> If you move a method trace file, Android Studio no longer displays the file
- in the <em>Captures</em> window. To display it, use <strong>File</strong> >
- <strong>Open</strong>. Also, rename a file from the <em>Captures</em>
- window and not in the operating system file browser.
-</p>
-
-<h3 id="deletetrace">
- Deleting a method trace file
-</h3>
-
-<p>
- To delete a method trace file:
-</p>
-
-<ul>
- <li>In the <em>Captures</em> window, right-click a method trace file and select
- <strong>Delete</strong>.
- </li>
-</ul>
-
-<p>
- Android Studio deletes the file from the <em>Captures</em> dialog and from disk.
-</p>
\ No newline at end of file
+++ /dev/null
-page.title=Network Monitor
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Network Monitor to analyze network requests, including how and when your app transfers data. Preserve battery life by optimizing network use.
-page.image=tools/help/thumbnails/am-networkmon.png
-page.article=true
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#running">Displaying a Running App in the Network Monitor</a></li>
-</ol>
-
-<h2>Video</h2>
- <ol>
- <li><a href="https://www.youtube.com/watch?v=fEEulSk1kNY"
- class="external-link">Battery Drain and Networking</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>
- The Network Monitor makes it possible to track when your application is making network requests.
- Using this tool, you can monitor how and when your app transfers data, and optimize the underlying
- code appropriately.
-</p>
-
-<p>
- By monitoring the frequency of data transfers, and the amount of data transferred during each
- connection, you can identify areas of your app that can be made more efficient and use less
- battery power.
- Generally, you should look for short spikes that can be delayed, or that could cause a later
- transfer to be preempted.
-</p>
-
-
-<h2 id="running">
- Displaying a Running App in the Network Monitor
-</h2>
-
-<p>
- To display an app running on a particular device in the Network Monitor:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <p>Connect a hardware device; the Network Monitor doesn't monitor an emulator.
- </p>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on the hardware device.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
- <li>Click the <strong>Monitors</strong> tab and <a href=
- "{@docRoot}tools/help/am-basics.html#rearranging">display the Network Monitor</a>.
- </li>
-
- <li>Enable the Network Monitor by clicking Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> to deselect it.
- </li>
-
-<p>
- Any network traffic begins to appear in the Network Monitor:
-</p>
- <img src="{@docRoot}images/tools/am-networkmon2.png" style="vertical-align:sub;margin:0" />
-<p>
- The Network Monitor adds up the amount of time it takes for the device to transmit and receive
- kilobytes of data.
- The y-axis is in kilobytes per second. The x-axis starts with seconds, and then minutes and
- seconds, and so on.
-</p>
- <li>To stop the Network Monitor, click Pause <img src="{@docRoot}images/tools/am-ipause.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Pause icon" /> again to
- select it.
- </li>
-</ol>
\ No newline at end of file
+++ /dev/null
-page.title=Screen Capture
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Screen Capture tool to take a screenshot of the display on a hardware device or the emulator. Optionally display the screenshot within a graphic of a device.
-page.image=tools/help/thumbnails/am_screenshot.png
-page.article=true
-@jd:body
-
-
-<p>
- You can take a PNG screenshot of the display on a connected device or the emulator. You can use
- the images for your marketing materials as well as for debugging, for example.
-</p>
-
-
-<h2 id="screencapture">
- Taking a Screen Capture of the Device
-</h2>
-
-
-<p>
- To take a screen capture:
-</p>
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on
- a hardware device or emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
-
- <li>Interact with the display on the device or emulator to stage the image you want.
- </li>
-
- <li>Click Screen Capture <img src="{@docRoot}images/tools/am-iscreencapture.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Screen Capture icon" /> in the
- Android Monitor toolbar.
- </li>
- <p>The screenshot appears in a <em>Screenshot Editor</em> window.</p>
-
-<img src="{@docRoot}images/tools/am-screenshot.png" alt="Screen Capture" />
-
- <li>Optionally change the image:
- <ul>
- <li>
- <strong>Recapture</strong> - Click to take a new screenshot.
- </li>
-
- <li>
- <strong>Rotate</strong> - Click to rotate the image 90 degrees clockwise.
- </li>
-
- <li>
- <strong>Frame Screenshot</strong> - Select this option and choose a device to add an image
- of the device to the outside of the screenshot. Select <strong>Drop Shadow</strong>,
- <strong>Screen Glare</strong>, or both to add these effects to your image.
- </li>
-
- <li>
- <strong>Chessboard</strong> and <strong>Grid</strong> - Select an option to display these
- behind your image.
- </li>
-
- <li>
- <strong>Zoom In</strong>, <strong>Zoom Out</strong>, or <strong>Actual Size</strong> -
- Click these options to get different perspectives of your image without changing the image
- itself.
- </li>
- </ul>
- </li>
- <li>Click <strong>Save</strong> to save the image.
- </li>
- </li>
- <li>In the <em>Save as PNG</em> dialog, specify the location and filename,
- and then click <strong>OK</strong>.
- </li>
- <p>The screenshot file appears in the Code Editor area.</p>
-</ol>
-
-
-
+++ /dev/null
-page.title=System Information
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the System Information tool to capture <code>dumpsys</code> information about your app. View activity manager, package, memory usage, and graphics state information.
-page.image=tools/help/thumbnails/am_sysinfo.png
-page.article=true
-@jd:body
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#sysinfo">Examining System Information for a Running App</a></li>
- <li><a href="#viewsysinfo">Viewing Saved System Information</a></li>
- <li><a href="#sysinfo-files">Working with System Information Files</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>
- You can capture <code>dumpsys</code> output from within Android Monitor and
- display the file in the Code Editor. The <em>Captures</em> window lists the
- system information files so you can retrieve the information later for
- analysis.
-</p>
-
-
-
-<h2 id="sysinfo">
- Examining System Information for a Running App
-</h2>
-<p>
- To capture and view a snapshot of system information:
-</p>
-
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on
- a hardware device or emulator.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
-
- <li>In the toolbar of the Android Monitor main window, click System Information
- <img src="{@docRoot}images/tools/am-isysteminfo.png"
- style="vertical-align:sub;margin:0;height:17px" alt="System Information icon" />
- and then select a menu item.
- </li>
-
-<p>
- The menu items display different types of <code><a href=
- "https://source.android.com/devices/tech/debug/dumpsys.html">dumpsys</a></code>
- output:
-</p>
-
-<ul>
- <li>
- <strong>Activity Manager State</strong> - <code>dumpsys activity</code>
- </li>
-
- <li>
- <strong>Package Information</strong> - <code>dumpsys package</code>
- </li>
-
- <li>
- <strong>Memory Usage</strong> - <code><a href=
- "{@docRoot}tools/debugging/debugging-memory.html#ViewingAllocations">dumpsys
- meminfo</a></code>
- </li>
-
- <li>
- <strong>Memory Use Over Time</strong> - <code><a href=
- "http://android-developers.blogspot.com/2014/01/process-stats-understanding-how-your.html">dumpsys
- procstats</a></code>
- </li>
-
- <li>
- <strong>Graphics State</strong> - <code><a href=
- "{@docRoot}training/testing/performance.html">dumpsys gfxinfo</a></code>
- </li>
-</ul>
-
-<p>
- The information appears in an editable text file in the Code Editor.
-</p>
-<img src="{@docRoot}images/tools/am-sysinfo.png" alt="System Information" />
-<p>Android Studio creates the system information file with the
- filename <code><em>package_yyyy.mm.dd_hh.mm.ss</em>.txt</code> using the
- activity package (or project) name, year, month, day,
- hour, minute, and second of the capture, for example,
- <code>com.android.calc_2015.11.17_14.58.48.txt</code>.</p>
-</ol>
-
-<h2 id="viewsysinfo">
-Viewing Saved System Information
-</h2>
-
-<p>
-After you take a snapshot of system information, Android Studio automatically
-stores it so you can view it again.</p>
-
-<p>To examine a saved system information file:</p>
-
-<ol>
- <li>Click
- <img src="{@docRoot}images/tools/am-icaptures.png"
- style="vertical-align:sub;margin:0;height:17px"
- alt="Captures icon" /> in the main window.
- </li>
- <p>Or select <strong>View</strong> > <strong>Tools Windows</strong> >
- <strong>Captures</strong>.</p>
-
- <p>
- The <em>Captures</em> window appears.
- </p>
-
- <li>Open the <strong>System Information</strong> folder.
- </li>
-
- <li>Double-click the file to view it.
- </li>
-</ol>
-
-
-<h2 id="sysinfo-files">Working with System Information Files</h2>
-<p>You can rename, locate, and delete a system information file from within
-Android Studio.</p>
-
-<h3 id="renamesysinfo">
- Renaming a system information file
-</h3>
-
-<p>
- Rename a system information file from within Android Studio so it
- continues to appear in the <em>Captures</em> window.</p>
-
- <p>To rename a system information file:
-</p>
-
-<ol>
- <li>In the <em>Captures</em> window, right-click the file and select
- <strong>Rename</strong>.
- </li>
-
- <li>In the dialog, specify the name of the file and click <strong>OK</strong>.
- </li>
-</ol>
-
-<h3 id="locatesysinfo">
- Locating a system information file on disk
-</h3>
-
-<p>
- You can quickly discover where Android Studio stored system information files
- on disk.</p>
-
- <p>To locate a system information file on disk:
-</p>
-
-
-
-<ul>
- <li>In the <em>Captures</em> window, right-click a system information file and
- select <strong>Show</strong> or <strong>Reveal</strong>.
- </li>
-
-<p>
- Android Studio opens an operating system file browser displaying the location
- where the file resides.
-</p>
-</ul>
-<p class="note">
- <strong>Note:</strong> If you move a system information file, Android Studio
- no longer displays the file
- in the <em>Captures</em> window. To display it, use <strong>File</strong> >
- <strong>Open</strong>. Also, rename a file from the <em>Captures</em>
- window and not in the operating system file browser.
-</p>
-
-<h3 id="deletesysinfo">
- Deleting a system information file
-</h3>
-
-<p>
- To delete a system information file:
-</p>
-
-<ul>
- <li>In the <em>Captures</em> window, right-click a system information file
- and select <strong>Delete</strong>.
- </li>
-</ul>
-
-<p>
- Android Studio deletes the file from the <em>Captures</em> dialog and from
- disk.
-</p>
+++ /dev/null
-page.title=Video Capture
-parent.title=Android Monitor
-parent.link=android-monitor.html
-meta.tags="android, performance, profiling, tools, monitor"
-page.tags="android", "performance", "profiling", "tools", "monitor"
-page.metaDescription=Use the Video tool to make a video of the display on a hardware device.
-page.image=tools/help/thumbnails/am_video.png
-page.article=true
-@jd:body
-
-
-<p>
- Android Studio lets you record an MP4 video from your hardware device for a maximum of three
- minutes. You can use the video for your marketing materials as well as for debugging, for
- example.
-</p>
-<img src="{@docRoot}images/tools/am-video.png" width="230" alt="Device Video" />
-
-
-
-<h2 id="video">
- Recording a Video from the Screen
-</h2>
-
-<p>
- To record a video from a hardware device:
-</p>
-<ol>
- <li>Meet the <a href=
- "{@docRoot}tools/help/am-basics.html#byb">prerequisites and dependencies</a>.
- </li>
- <li>Open an app project.
- </li>
- <li><a href=
- "{@docRoot}tools/building/building-studio.html#RunningApp">Run the app</a> on
- a hardware device.
- </li>
- <li>
- <a href="{@docRoot}tools/help/am-basics.html#displaying">Display Android Monitor</a>.
- </li>
-
- <li>Interact with the display on the hardware device to stage the start of the video.
- </li>
-
- <li>Click Screen Record <img src="{@docRoot}images/tools/am-ivideo.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Screen Record icon" /> in the
- Android Monitor toolbar.
- </li>
- <p>The screenshot appears in a Screenshot Editor window.</p>
-
- <li>In the <em>Screen Recorder Options</em> dialog, optionally change the recording options:
- </li>
-<ul>
- <li>
- <strong>Bit Rate</strong> - Type a bit rate. The default is 4 Mbps.
- </li>
-
- <li>
- <strong>Resolution</strong> - Type a width and height value in pixels. The value must be a
- multiple of 16. The default is the resolution of the device.
- </li>
-</ul>
- <li>Click <strong>Start Recording</strong> to start the recording.
- </li>
-
- <li>Click <strong>Stop Recording</strong> to stop the recording.
- </li>
-
- <li>In the <em>Save As</em> dialog, save the MP4 file.
- </li>
-
- <li>In the <em>Screen Recorder</em> dialog, click one of the buttons to show the file location,
- open the recording in a player, or to dismiss the dialog.
- </li>
-</ol>
-
-
-
+++ /dev/null
-page.title=Android Monitor
-parent.title=Tools
-parent.link=index.html
-page.tags=monitor
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#logcat">Log Messages</a></li>
- <li><a href="#monitors">Performance Monitors</a></li>
- <li><a href="#data">Data Analysis</a></li>
- <li><a href="#shots">Screen and Video Captures</a></li>
- <li><a href="#getstarted">Get Started</a></li>
-</ol>
-
-
-
-
-
-</div>
-</div>
-
-<p>
- Android Monitor helps you to profile the performance of your apps so you can optimize, debug, and
- improve them. It lets you monitor the following aspects of your apps from a hardware device or
- the <a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a>:
-</p>
-
-<ul>
- <li>
- <a href="{@docRoot}reference/android/util/Log.html">Log</a> messages, either
- system- or user-defined
- </li>
-
- <li>Memory, CPU, and GPU usage
- </li>
-
- <li>Network traffic (hardware device only)
- </li>
-</ul>
-
-
-<p>Android Monitor provides various tools that provide real-time information about your app. It
- lets you capture data as your app runs and stores it in a file that you can analyze in various
- viewers. You can also capture screen shots and videos of your app as it runs.</p>
-
-<h2 id="logcat">Log Messages</h2>
-
-<p>View log messages — in real time and historically — which is useful for debugging.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/help/log"
- data-cardSizes="12x6"
- data-maxResults="6">
- </div>
-</div>
-
-
-<h2 id="monitors">Performance Monitors</h2>
-
-<p>Visualize the behavior and performance of your app.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/help/monitor"
- data-cardSizes="9x6"
- data-maxResults="6">
- </div>
-</div>
-
-<h2 id="data">Data Analysis</h2>
-
-<p>Android Monitor lets you capture various types of data about your app while it's running and
- stores it in a file, which you can access whenever is convenient.
- It lists these files in the <em>Captures</em> window.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/help/data"
- data-cardSizes="9x6"
- data-maxResults="6">
- </div>
-</div>
-
-<h2 id="shots">Screen and Video Captures</h2>
-
-<p>Create screen captures and videos of your app to help with marketing and debugging.
- </p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/help/shot"
- data-cardSizes="9x3"
- data-maxResults="2">
- </div>
-</div>
-
-<h2 id="getstarted">Get Started</h2>
-<p>To begin using Android Monitor, start with <a href=
- "{@docRoot}tools/help/am-basics.html">Android Monitor Basics</a>.
- </p>
-
-
+++ /dev/null
-page.title=android
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<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 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}tools/help/sdk-manager.html">SDK Manager</a>.</li>
- </ul>
-
-<p>If you are using Android Studio, 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>
-
- <h3>Global Options</h3>
-
- <dl>
- <dt><code>-s</code></dt>
-
- <dd>Silent mode: only errors are printed out</dd>
-
- <dt><code>-h</code></dt>
-
- <dd>Usage help</dd>
-
- <dt><code>-v</code></dt>
-
- <dd>Verbose mode: errors, warnings and informational messages are printed.</dd>
- </dl>
-
- <h3>AVD actions and options</h3>
-
- <table>
- <tr>
- <th width="15%">Action</th>
-
- <th width="20%">Option</th>
-
- <th width="30%">Description</th>
-
- <th>Comments</th>
- </tr>
-
- <tr>
- <td><code>avd</code></td>
-
- <td>None</td>
-
- <td>Launch the AVD Manager</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><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>
-
- <td>The name for the AVD.</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-t <targetID></code></td>
-
- <td>Target ID of the system image to use with the new AVD. To obtain a list of available
- targets, use <code>android list targets</code></td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-c <path>|<size>[K|M]</code></td>
-
- <td>The path to the SD card image to use with this AVD or the size of a new SD card image to
- create for this AVD. For example, <code>-c path/to/sdcard</code> or <code>-c
- 1000M</code>.</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-f</code></td>
-
- <td>Force creation of the AVD</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Path to the location at which to create the directory for this AVD's files.</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-s <name>|<width>-<height></code></td>
-
- <td>The skin to use for this AVD, identified by name or dimensions. The <code>android</code>
- tool scans for a matching skin by name or dimension in the <code>skins/</code> directory of
- the target referenced in the <code>-t <targetID></code> argument. For example, <code>-s
- HVGA-L</code></td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>delete avd</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name of the AVD to delete</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td rowspan="3"><code>move avd</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name of the AVD to move</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Path to the location at which to create the directory for this AVD's files.</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-r <new-name></code></td>
-
- <td>New name of the AVD if you want to rename it</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>update avd</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name of the AVD to move</td>
-
- <td>Required</td>
- </tr>
- </table>
-
- <h3>Project actions and options</h3>
-
- <table>
- <tr>
- <th width="15%">Action</th>
-
- <th width="20%">Option</th>
-
- <th width="30%">Description</th>
-
- <th>Comments</th>
- </tr>
-
- <tr>
- <td rowspan="5"><code>create project</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name for the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-t <targetID></code></td>
-
- <td>Target ID of the system image to use with the new AVD. To obtain a list of available
- targets, use <code>android list targets</code></td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-k <path>|<size>[K|M]</code></td>
-
- <td>Package namespace</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-a</code></td>
-
- <td>Name for the default Activity class</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Location of your project directory</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td rowspan="5"><code>update project</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name of the project to update</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Location path of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-l <library path></code></td>
-
- <td>Location path of an Android Library to add, relative to the main project</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-s <subprojects></code></td>
-
- <td>Update any projects in subfolders such as test projects</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-t <targetID></code></td>
-
- <td>Target id to set for the project</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td rowspan="3"><code>create test-project</code></td>
-
- <td><code>-n <name></code></td>
-
- <td>The name of the project</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Location path of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-m <main></code></td>
-
- <td>The name of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td rowspan="2"><code>update test-project</code></td>
-
- <td><code>-p <path></code></td>
-
- <td>Location path of the project to test, relative to the new project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-m <main></code></td>
-
- <td>The main class of the project to test</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td rowspan="4"><code>create lib-project</code></td>
-
- <td><code>-k <packageName></code></td>
-
- <td>(Required) Package name of the library project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Location path of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-t <targetID></code></td>
-
- <td>Target ID of the library project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-n <name></code></td>
-
- <td>The name of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td rowspan="3"><code>update lib-project</code></td>
-
- <td><code>-p <path></code></td>
-
- <td>Location path of the project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-l <libraryPath></code></td>
-
- <td>Location path of an Android Library to add, relative to the main project</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td><code>-t <name></code></td>
-
- <td>Target ID of the library project</td>
-
- <td></td>
- </tr>
-
- <tr>
- <td rowspan="3"><code>create uitest-project</code></td>
- <td><code>-n <name></code></td>
- <td>The name of the UI test project</td>
- <td></td>
- </tr>
-
- <tr>
- <td><code>-t <name></code></td>
-
- <td>Target ID of the UI test project</td>
-
- <td>Required</td>
- </tr>
-
- <tr>
- <td><code>-p <path></code></td>
-
- <td>Location path of the UI test project</td>
-
- <td>Required</td>
- </tr>
-
- </table>
-
- <h3>Update actions</h3>
- <dl>
- <dt><code>update adb</code></dt>
- <dd>Updates adb to support the USB devices declared in the SDK add-ons.</dd>
-
- <dt><code>update sdk</code></dt>
- <dd>Updates the SDK by suggesting new platforms to install if available.</dd>
+++ /dev/null
-page.title=Supporting URLs and App Indexing in Android Studio
-parent.title=Tools
-parent.link=index.html
-page.tags=app indexing
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#workflow">Typical Workflow</a></li>
- <li><a href="#intent">Adding an Intent Filter for URL Support and Google Search</a></li>
- <li><a href="#indexing">Adding App Indexing API Skeleton Code to an Activity</a></li>
- <li><a href="#testintent">Testing a URL</a></li>
- <li><a href="#testindexing">Viewing App Indexing API Messages in the logcat Monitor</a></li>
- <li><a href="#lint">Configuring Lint</a></li>
- <li><a href="#appindexingtest">Performing a Google App Indexing Test</a></li>
-
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="https://developers.google.com/app-indexing/introduction"
- class="external-link">App Indexing</a></li>
- <li><a href="{@docRoot}training/app-indexing/index.html"
- >Making Your App Content Searchable by Google</a></li>
- <li><a href="{@docRoot}training/app-links/index.html">Handling App Links</a></li>
- <li><a href="{@docRoot}tools/debugging/improving-w-lint.html"
- >Improving Your Code with lint</a></li>
- <li><a href="{@docRoot}tools/help/am-logcat.html">logcat Monitor</a></li>
- <li><a href="https://www.google.com/webmasters/tools/home"
- class="external-link">Google Search Console</a></li>
- <li><a href="https://developers.google.com/android/guides/overview"
- class="external-link">Google Play Services</a></li>
- </ol>
-
- <h2>Video</h2>
- <ol>
- <li><a href="https://www.youtube.com/watch?v=aISUYHTkTOU"
- class="external-link">DevBytes: App Indexing</a></li>
- </ol>
-
- <h2>Dependencies and prerequisites</h2>
- <ul>
- <li>Android 2.3 (API level 9) or higher</li>
- <li>Android Studio 1.5 or higher</li>
- <li>Google Play Services 8.1.0 or higher</li>
- </ul>
-
-</div>
-</div>
-
-<p>Android Studio helps you add support for URLs, app indexing, and search
-functionality to your apps.
- These features can help to drive more traffic to your
- app, discover which app content is used most, make it easier for users to find content in an
- installed app, and attract new users.</p>
-
-<h2 id="workflow">Typical Workflow</h2>
-
-<p>To use Android Studio to add support for URL, app indexing, and search
-features to your app:</p>
-
-<ol>
-<li>Add intent filters and code to handle incoming intents.</li>
-<li>Associate a website with your app.</li>
-<li>Add App Indexing API code.</li>
-</ol>
-
-<p>Intent filters and the App Indexing API are ways to implement URL support
-and app indexing, but
- there are other possible implementations as well. See
- <a href="https://developers.google.com/app-indexing/reference/deeplinks"
- class="external-link">Alternate Android Indexing Methods</a>
- for more information.</p>
-
-<h3 id="aboutintent">Intent filters for URLs</h3>
-
-<p>Android Studio can create a basic intent filter in your manifest that you can customize to
- define URLs for your app. You can then write Java code in an activity to handle the
- intent. This implementation lets users directly open the specified app activity by
- clicking a URL. Users can see the URLs in google.com in a browser, in the
- Google Search app, and in Google Now on Tap. </p>
-
-<h3 id="aboutassociation">Website association with URLs</h3>
-
-<p>After setting up URL support for your app, you can associate your website
-with your app by using
- the Google Search Console and Google Play Developer Console. Afterward, Google indexes your app
- for URLs defined in
- your intent filters and begins to include them in search results. In addition, you can optionally
- exclude app content from Google Search. After you associate a website with your app, features
- such as Now on Tap and enhanced search result display (like including your app icon)
- become available.</p>
-
-<p>As an alternative to associating your app with a website,
- for Android 6.0 (API level 23) and higher, you can add
- <a href="{@docRoot}training/app-links/index.html"
- >default handlers and verification for URLs</a>
- instead.</p>
-
-<p>Chrome displaying google.com serves search results with URLs that are accessible to both
- signed-in users and those who aren't. Google Search app users must be signed in to see URLs
- in their search results. </p>
-
-<h3 id="aboutapi">App Indexing API code in activities</h3>
-
-<p>Next, if you want to support additional search features, such as autocompletions, you can
- add App Indexing API code to your app. Android Studio can create skeleton code in an activity
- that you can then customize to support app indexing. The App Indexing API allows app indexing
- even if
- <a href="https://developers.google.com/app-indexing/reference/deeplinks#allow-access-by-googlebot-optional"
- class="external-link">Googlebot</a>
- can’t get content from your app.</p>
-
-<h3 id="abouttest">URL support and App Indexing API testing</h3>
-
-<p>Android Studio helps you test your code with the following features:</p>
-
-<ul>
-<li>URL support testing helps you verify that a specified URL can launch an app.
-</li>
-<li>The logcat Monitor helps you test App Indexing API calls in an activity. </li>
-<li>The Android Lint tool has warnings for certain issues involving URL support
-and the App Indexing
- API. These warnings and errors appear in the Code Editor and in Lint inspection results.</li>
- <li>A Google App Indexing test checks whether Google can index a URL by
- either crawling your app page or using the App Indexing API.</li>
-</ul>
-
-<p>The details for implementing URL support and app indexing are described next.
-
-
-<h2 id="intent">Adding an Intent Filter for URL Support and Google Search</h2>
-
-<p>To use Android Studio features to add an intent filter defining a URL:</p>
-
-<ol>
-<li>In the <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>
- of the <em>Project</em> window, double-click the <code>AndroidManifest.xml</code> file to open it
- in the Code Editor.</li>
-<li>Insert an intent filter in one of the following ways:</li>
-<ul>
-<li>In an <code><activity></code> element, click in the left column so the light bulb
- <img src="{@docRoot}images/tools/ai-ilightbulb.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Lightbulb icon" /> appears. Click
- <img src="{@docRoot}images/tools/ai-ilightbulb.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Lightbulb icon" />
- and select <strong>Create URL</strong>.</li>
-<li>Right-click in an <code><activity></code> element and select <strong>Generate</strong>
- > <strong>URL</strong>.</li>
-<li>Place your cursor in an activity, and then select <strong>Code</strong> >
- <strong>Generate</strong> > <strong>URL</strong>.</li>
-</ul>
-
-<p>The Code Editor adds skeleton code using the
- <a href="https://www.jetbrains.com/idea/help/intention-actions.html"
- class="external-link">intention action</a> and
- <a href="https://www.jetbrains.com/idea/help/generating-code.html"
- class="external-link">generate code</a> mechanisms.</p>
-
-<p>The Code Editor adds an intent filter similar to the following:</p>
-<pre>
-<!-- ATTENTION: This intent was auto-generated. Follow instructions at
- https://g.co/AppIndexing/AndroidStudio to publish your URLs. -->
-<intent-filter>
- <action android:name="android.intent.action.VIEW" />
-
- <category android:name="android.intent.category.DEFAULT" />
- <category android:name="android.intent.category.BROWSABLE" />
- <!-- ATTENTION: This data URL was auto-generated.
- We recommend that you use the HTTP scheme.
- TODO: Change the host or pathPrefix as necessary. -->
- <data
- android:host="www.example.com"
- android:pathPrefix="/gizmos"
- android:scheme="http" />
-</intent-filter>
-</pre>
-
-<li><a href="{@docRoot}training/app-indexing/deep-linking.html#adding-filters">Modify the
- <code><data></code> element</a>
- and optionally the <code><category></code> element, as needed.</li>
-
-
-<p>We recommend that you define a <code><data></code> element that supports URLs that you’ll
- add in the future. In the previous sample code, for example, Google will index any URLs starting
- with <code>http://www.example.com/gizmos</code>. Also, remember to
- include a URL for your app home screen so it’s included in search results. </p>
-
-<p>The URLs you specify in your intent filters can be the same as the URLs of
-the comparable pages on your website.</p>
-
-<li>In the corresponding activity,
- <a href="{@docRoot}training/app-indexing/deep-linking.html#handling-intents">add Java code</a>
- to read data from the intent filter and direct the app to respond accordingly. </li>
-<li><a href="#testintent">Test your URL</a>.</li>
-
-</ol>
-
-<p>To support Google Search for your URLs:</p>
-<ol>
-<li><a href="https://developers.google.com/app-indexing/android/app#declare-a-website-association"
- class="external-link">Define an association</a>
- between your app and your website.</li>
-<p>Alternatively, for Android 6.0 (API level 23) and higher, add
- <a href="{@docRoot}training/app-links/index.html">link default handling and verification</a>.</p>
-<li>Optionally
- <a href="https://developers.google.com/app-indexing/android/app#create-the-noindexxml-file"
- class="external-link">exclude certain URLs</a>
- from the Google index.</li>
-<li>Optionally <a href="#indexing">add App Indexing API code</a> to support additional search
- features.</li>
-</ol>
-
-
-<p>To test and debug your links, you can use the following Android Studio features:</p>
-<ul>
-<li><a href="#testintent">Launch your URL</a> in Android Studio to test that it works.</li>
-<li><a href="#lint">Enable the following Android Lint categories</a>:</li>
-<ul>
-<li><strong>Missing support for Google App Indexing</strong></li>
-<li><strong>URL not supported by app for Google App Indexing</strong></li>
-</ul>
-<li><a href="#appindexingtest">Perform a Google App Indexing Test</a>.</li>
-</ul>
-
-<p>In addition, you can
- <a href="https://developers.google.com/app-indexing/android/test#preview-your-apk-on-search-console"
- class="external-link">preview your APK in the Google Search Console</a>
- to test your URLs, whether the app is associated with a website or not. </p>
-
-
-
-<h2 id="indexing">Adding App Indexing API Skeleton Code to an Activity</h2>
-
-<p>After adding URL support to your app, you can add App Indexing API code to
-an activity to support additional search features. </p>
-
-<p>To add App Indexing API code to an activity:</p>
-<ol>
-<li>In <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>
- in the <em>Project</em> window, double-click the activity Java file to open it in the
- Code Editor.</li>
-<li>Insert skeleton code in one of the following ways:</li>
-<ul>
-<li>In an activity definition, click in the Java code so the light bulb
- <img src="{@docRoot}images/tools/ai-ilightbulb.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Lightbulb icon" /> appears.
- Click <img src="{@docRoot}images/tools/ai-ilightbulb.png"
- style="vertical-align:sub;margin:0;height:17px" alt="Lightbulb icon" />
- and select <strong>Insert App Indexing API Code</strong>.</li>
-<li>Right-click in an activity definition and select <strong>Generate</strong> >
- <strong>App Indexing API Code</strong>.</li>
-<li>Place the cursor in an activity, and then select <strong>Code</strong> >
- <strong>Generate</strong> >
- <strong>App Indexing API Code</strong>.</li>
-</ul>
-
-
-<p>The Code Editor adds skeleton code using the
- <a href="https://www.jetbrains.com/idea/help/intention-actions.html"
- class="external-link">intention action</a> and
- <a href="https://www.jetbrains.com/idea/help/generating-code.html"
- class="external-link">generate code</a>
- mechanisms.</p>
-
-<p>If you don’t see the <strong>App Indexing API Code</strong> menu item, make sure your cursor is
- within an activity, and check your code for App Indexing API methods. The Code Editor can insert
- skeleton Java code into an activity in the following circumstances:</p>
-
-<ul>
-<li>The activity doesn’t have an <code>onStart()</code> method, or the <code>onStart()</code>
- method doesn’t contain an <code>AppIndexApi.start()</code> or <code>AppIndexApi.view()</code>
- call.</li>
-<li>The activity doesn’t have an <code>onStop()</code> method, or the <code>onStop()</code>
- method doesn’t contain an <code>AppIndexApi.end()</code> or <code>AppIndexApi.viewEnd()</code>
- call.</li>
-</ul>
-
-
-<p>The Code Editor adds Java code similar to the following:</p>
-<pre>
- /**
- * ATTENTION: This was auto-generated to implement the App Indexing API.
- * See https://g.co/AppIndexing/AndroidStudio for more information.
- */
- private GoogleApiClient client;
-
- // ATTENTION: This was auto-generated to implement the App Indexing API.
- // See https://g.co/AppIndexing/AndroidStudio for more information.
- client = new GoogleApiClient.Builder(this).addApi(AppIndex.API).build();
- }
-
-
- @Override
- public void onStart() {
- super.onStart();
-
- // ATTENTION: This was auto-generated to implement the App Indexing API.
- // See https://g.co/AppIndexing/AndroidStudio for more information.
- client.connect();
- Action viewAction = Action.newAction(
- Action.TYPE_VIEW, // TODO: choose an action type.
- "Main Page", // TODO: Define a title for the content shown.
- // TODO: If you have web page content that matches
- // this app activity's content,
- // make sure this auto-generated web page URL is correct.
- // Otherwise, set the URL to null.
- Uri.parse("http://www.example.com/gizmos"),
- // TODO: Make sure this auto-generated app URL is correct.
- Uri.parse("android-app://com.example/http/www.example.com/gizmos")
- );
- AppIndex.AppIndexApi.start(client, viewAction);
- }
-
- @Override
- public void onStop() {
- super.onStop();
-
- // ATTENTION: This was auto-generated to implement the App Indexing API.
- // See https://g.co/AppIndexing/AndroidStudio for more information.
- Action viewAction = Action.newAction(
- Action.TYPE_VIEW, // TODO: choose an action type.
- "Main Page", // TODO: Define a title for the content shown.
- // TODO: If you have web page content that matches
- // this app activity's content,
- // make sure this auto-generated web page URL is correct.
- // Otherwise, set the URL to null.
- Uri.parse("http://www.example.com/gizmos"),
- // TODO: Make sure this auto-generated app URL is correct.
- Uri.parse("android-app://com.example/http/www.example.com/gizmos")
- );
- AppIndex.AppIndexApi.end(client, viewAction);
- client.disconnect();
- }
-}
-</pre>
-
-<p>For more information about the App Indexing API methods, see
- <a href="https://developers.google.com/app-indexing/reference/package-summary"
- class="external-link">Android API for App Indexing</a>.
- For information about the action types, see the
- <a href="https://developers.google.com/android/reference/com/google/android/gms/appindexing/Action#constant-summary"
- class="external-link">Action Class Constant Summary</a>.
-</p>
-
-<p>If your app isn’t already configured for the Google Play Services App Indexing API, the Code
- Editor also modifies your <code>build.gradle</code> and <code>AndroidManifest.xml</code> files
- to include it. If your app already depends on it but the version is lower than 8.1.0, your app
- is upgraded to version 8.1.0. For more information and to correct any issues, see
- <a href="https://developers.google.com/app-indexing/android/publish#add-google-play-services"
- class="external-link">Add Google Play Services</a>
- and <a href="https://developers.google.com/android/guides/setup"
- class="external-link">Setting Up Google Play Services</a>.
-</p>
-
-<li>Customize the skeleton code, as needed.</li>
-
-<p>Pay attention to the comments, which help you find areas that need work, such as setting the
- title and URLs. For more information, see
- <a href="https://developers.google.com/app-indexing/android/publish"
- class="external-link">Add the App Indexing API</a>.
-</p>
-<li><a href="#testindexing">Verify that your app indexing code is working</a> by using
- the logcat Monitor.</li>
-</ol>
-
-
-
-<p>To test and debug your App Indexing API code, you can use the following Android Studio
- features:</p>
-<ul>
-<li><a href="#testindexing">Examine logcat Monitor Messages</a>.</li>
-<li><a href="#lint">Enable the following Android Lint category</a>:
- <strong>Missing support for Google App Indexing API</strong></li>
-
-<li><a href="#appindexingtest">Perform a Google App Indexing Test</a>.</li>
-</ul>
-
-<p>In addition, you can
- <a href="https://developers.google.com/app-indexing/android/test#preview-your-apk-on-search-console"
- class="external-link">preview your APK in the Google Search Console</a>.</p>
-
-
-<h2 id="testintent">Testing a URL</h2>
-
-<p>When you run your app from Android Studio, you can specify a URL to launch so you can
- test it.</p>
-
-<p>To launch a URL from Android Studio:</p>
-<ol>
-<li>In Android Studio, open your project in
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>.</li>
-<li>After opening a project, select <strong>Run</strong> > <strong>Edit Configurations</strong>.
-</li>
-<li>In the <em>Run/Debug Configurations</em> dialog, beneath <strong>Android Application,</strong>
- select the module you want to test.</li>
-<li>Select the <strong>General</strong> tab. </li>
-<li>In the <strong>Launch</strong> field, select <strong>URL</strong>. </li>
-<li>In the <strong>URL</strong> field, click <strong>…</strong> to select from a list of
- defined URLs.</li>
-
-<p>Or type the URL you want to test, for example, <code>http://example.com/gizmos</code>. </p>
-<li>Click <strong>OK</strong>.</li>
-<li>Select <strong>Run</strong> > <strong>Run app</strong> or <strong>Debug app</strong>.</li>
-<li>If the <em>Select Deployment Target</em> dialog appears, select a connected device or an
- emulator, and click <strong>OK</strong>.</li>
-
-<p>If the link is successful, the app launches in the device or emulator, and displays the app at
- the specified activity. Otherwise, an error message appears in the <em>Run</em> window.</p>
-</ol>
-
-<p>For more information about creating run configurations at the project, default, and module
- levels, see
- <a href="{@docRoot}tools/building/building-studio.html">Building and Running from Android Studio</a>.
-</p>
-
-<p>You can view App Indexing API log messages while the app is running, as described next.</p>
-
-
-<h2 id="testindexing">Viewing App Indexing API Messages in the logcat Monitor</h2>
-
-<p>The logcat Monitor can display app indexing log messages to determine if your App Indexing API
- code is pushing the correct data to the cloud. For example, you can check the app title and the
- URL. The logcat Monitor is part of Android Monitor in Android Studio.</p>
-
-<p>To view App Indexing API messages in the logcat Monitor:</p>
-<ol>
-<li>Run your app in Android Studio so it <a href="#testintent">launches a URL</a>.</li>
-<li><a href="{@docRoot}tools/help/am-logcat.html#running">Display Android Monitor</a>
- and click the <strong>logcat</strong> tab.</li>
-<li><a href="{@docRoot}tools/help/am-logcat.html#level">Set the log level</a> to
- <strong>Verbose</strong>.</li>
-<li>In the filter menu, select <strong>No Filters</strong>.</li>
-<li><a href="{@docRoot}tools/help/am-logcat.html#searching">Search the log</a> for the string
- "appindex".</li>
-
-<p>App indexing log messages should appear. If they don’t, check the following items:</p>
-<ul>
-<li>Is Google Play Services installed on the device or emulator? You can check the settings on
- the device. </li>
-<li>Is the Google Play Services version on the device or emulator lower than the version specified
- in the <code>build.gradle</code> file? If so, it might be out-of-date and should be upgraded to
- a higher version. </li>
-</ul>
-
-<p>For more information, see the
- <a href="https://play.google.com/store/apps/details?id=com.google.android.gms&hl=en"
- class="external-link">Google Play Services Download</a>
- page and <a href="https://developers.google.com/android/guides/setup"
- class="external-link">Setting Up Google Play Services</a>.
-</p>
-<li>Visit app pages that trigger App Indexing API calls. </li>
-</ol>
-
-
-<h2 id="lint">Configuring Lint</h2>
-
-<p>You can use the Android Studio built-in Lint tool to check whether you have valid URLs
- defined in the manifest and have implemented the App Indexing API correctly in activities.</p>
-
-<p>You can view URL and app indexing warnings and errors in two ways: </p>
-<ul>
-<li>As pop-up text in the Code Editor. When Lint finds a problem, it highlights the problematic
- code in yellow, or underlines the code in red for more serious issues.</li>
-<li>In the Lint <em>Inspection Results</em> window after you select <strong>Analyze</strong> >
- <strong>Inspect Code</strong>.</li>
-</ul>
-
-
-
-<p>To set default Lint checks for URLs and the App Indexing API:</p>
-<ol>
-<li>In Android Studio, open your project in
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>.
-</li>
-<li>Select <strong>File</strong> > <strong>Other Settings</strong> >
- <strong>Default Settings</strong>.</li>
-<li>In the <em>Default Preferences</em> dialog, select <strong>Editor</strong> >
- <strong>Inspections</strong>. </li>
-<li>In the <strong>Profile</strong> field, select <strong>Default</strong> or
- <strong>Project Default</strong> to set the scope for Android Studio or just for this project,
- respectively. </li>
-<li>Expand the <strong>Android Lint</strong> category and change the Lint settings as needed:</li>
-<ul>
-<li><strong>Missing support for Google App Indexing</strong> - Reports a warning if the app hasn’t
- implemented URLs, which are used by Google Search. This warning setting is enabled by
- default.</li>
-<li><strong>Missing support for Google App Indexing API</strong> - Reports if an app hasn’t
- implemented the App Indexing API at all. This warning setting is disabled by default.</li>
-<li><strong>URL not supported by app for Google App Indexing</strong> - Reports URL
- errors in manifest code. This error setting is enabled by default.</li>
-</ul>
-
-<p>For example, the following Lint warning appears for the first setting:</p>
-<p><img src="{@docRoot}images/tools/ai-lint.png" alt="Lint warning" /></p>
-
-<li>Click <strong>OK</strong>.</li>
-</ol>
-
-
-
-<p>To produce a list of Lint checks displayed in the <em>Inspection Results</em> window:</p>
-<ol>
-<li>In Android Studio, open your project in
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>
- and select a portion of your project that you want to test.</li>
-<li>Select <strong>Analyze</strong> > <strong>Inspect Code</strong>.</li>
-<li>In the <em>Specify Inspection Scope </em>dialog, select the inspection scope and profile. </li>
-
-<p>The scope specifies the files you want to analyze, and the profile specifies the Lint checks
- you’d like to perform.</p>
-<li>If you want to change the Lint settings, click <strong>…</strong>. In the <em>Inspections</em>
- dialog, optionally click <strong>Manage</strong> to define a new profile, specify the Lint
- settings you want, and then click <strong>OK</strong>.</li>
-<p>In the <em>Inspections</em> dialog, you can search for the string "app indexing"
-to find the URL and App Indexing API Lint checks. Note that changing Lint settings for a
-profile in the <em>Inspections</em> dialog doesn’t change the default settings, as described in
-the previous procedure. It does change the settings for profiles displayed in the
-<em>Inspections</em> dialog, however.</p>
-<li>Click <strong>OK</strong>.</li>
-<p>The results appear in the <em>Inspection Results</em> window.</p>
-
-</ol>
-
-
-<h2 id="appindexingtest">Performing a Google App Indexing Test</h2>
-
-<p>You can use a Google App Indexing Test to check whether Google can index
-a URL by either crawling your app page or using the App Indexing API.
-Google can index the URL if your app supports at least one of the following:
-</p>
-<ul>
-<li>Googlebot can open and crawl the page identified by the URL.</li>
-<li>Your app sends the correct data by using the App Indexing API.</li>
-</ul>
-
-<p>To perform a Google App Indexing Test: </p>
-<ol>
-<li>Add <a href="#intent">URL</a> and
-<a href="#indexing">App Indexing API</a> support to your app.
-</li>
-<li>While your project is open in Android Studio, select <strong>Tools</strong>
-> <strong>Android</strong> > <strong>Google App Indexing Test</strong>.
-</li>
-<li>In the <em>Google App Indexing Test</em> dialog, select a
-<strong>Module</strong>, <strong>URL</strong>, and <strong>Language</strong>.
-</li>
-<li>Log in if you see a message asking you to log into a Google Cloud Platform
-account.</li>
-<li>In the <em>Google App Indexing Test</em> dialog, click <strong>OK</strong>.
-</li>
-
-<p>Android Studio builds the APK and starts the test. The test can take a few
-minutes to complete. The results appear in a new tab in the Code Editor.</p>
-<p><img src="{@docRoot}images/tools/ai-appindexingtest.png"
-alt="Google App Indexing Test results" /></p>
-
-<p>If the app preview on the right shows the screen that corresponds to the URL
-you're testing, then Googlebot can find the URL.</p>
-
-<li>Correct any issues the test identifies, and repeat the test as often as
-needed.</li>
-</li>
-</ol>
-
-<p>The following table lists common errors and warnings you might encounter.</p>
-
-<table>
- <tr>
- <th scope="col">Warning or Error</th>
- <th scope="col">Description</th>
- </tr>
-
- <tr>
- <td>Error: Google cannot index this page.</td>
- <td>Your app can't be crawled by Googlebot or using the App Indexing API,
- so Google isn't able to index this app.</td>
- </tr>
- <tr>
- <td>Warning: The App URL you sent by using the App Indexing API doesn't
- match the URL opened.</td>
- <td>When calling the App Indexing API, the URL specified in the app must
- match the opened URL.</td>
- </tr>
- <tr>
- <td>Warning: Google cannot index this page using the App Indexing API
- because the title is empty.</td>
- <td>When calling the App Indexing API, the title shouldn't be empty.</td>
- </tr>
- <tr>
- <td>Warning: Google can index this page using Googlebot crawling but
- identified blocked resources.</td>
- <td>The app references other resources, and some of them are blocked or
- temporarily unavailable. If these resources aren't critical, it might not
- matter. Check the preview on the right to see whether the content
- displays correctly. To fix this issue, make sure the resources aren't
- blocked by <a href="https://support.google.com/webmasters/answer/6062608"
- class="external-link"><code>robots.txt</code></a>.</td>
- </tr>
- <tr>
- <td>Warning: Google cannot index this page using the App Indexing API.</td>
- <td>Your app isn’t using the App Indexing API. We recommended adding App
- Indexing API support to your app.</td>
- </tr>
-
-</table>
-
+++ /dev/null
-page.title=AVD Manager
-@jd:body
-
-
-<p>The AVD Manager provides a graphical user interface in which you can create
-and manage Android Virtual Devices (AVDs), which are required by the
-<a href="{@docRoot}tools/help/emulator.html">Android Emulator</a>.</p>
-
-<p>You can launch the AVD Manager in one of the following ways:</p>
-<ul>
- <li>In Android Studio: select <strong>Tools > Android > AVD Manager</strong>, or click
- the AVD Manager icon in the toolbar.</li>
-
- <li>In other IDEs: Navigate to your SDK's <code>tools/</code> directory and execute
- <code>android avd</code>.</li>
-</ul>
-
-<p>For more information, see <a href="{@docRoot}tools/devices/managing-avds.html">Managing
-AVDs with AVD Manager</a>.
+++ /dev/null
-page.title=bmgr
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<!-- quickview box content here -->
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
- <ol>
-<li><a href="#backup">Forcing a Backup Operation</a></li>
-<li><a href="#restore">Forcing a Restore Operation</a></li>
-<li><a href="#other">Other Commands</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}guide/topics/data/backup.html">Data Backup</a></li>
- </ol>
-
-</div>
-</div>
-
-<!-- normal page content here -->
-
-<p><code>bmgr</code> is a shell tool you can use to interact with the Backup Manager
-on Android devices supporting API Level 8 or greater. It provides commands to induce backup
-and restore operations so that you don't need to repeatedly wipe data or take similar
-intrusive steps in order to test your application's backup agent. These commands are
-accessed via the <a href="{@docRoot}tools/help/adb.html">adb</a> shell.
-
-<p>For information about adding support for backup in your application, read <a
-href="{@docRoot}guide/topics/data/backup.html">Data Backup</a>, which includes a guide to testing
-your application using {@code bmgr}.</p>
-
-
-<h2 id="backup">Forcing a Backup Operation</h2>
-
-<p>Normally, your application must notify the Backup Manager when its data has changed, via {@link
-android.app.backup.BackupManager#dataChanged()}. The Backup Manager will then invoke your
-backup agent's {@link
-android.app.backup.BackupAgent#onBackup(ParcelFileDescriptor,BackupDataOutput,ParcelFileDescriptor)
-onBackup()} implementation at some time in the future. However, instead of calling {@link
-android.app.backup.BackupManager#dataChanged()}, you can invoke a backup request from the command
-line by running the <code>bmgr backup</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr backup <em><package></em></pre>
-
-<p><code><em><package></em></code> is the formal package name of the application you wish to
-schedule for
-backup. When you execute this backup command, your application's backup agent will be invoked to
-perform a backup operation at some time in the future (via your {@link
-android.app.backup.BackupAgent#onBackup(ParcelFileDescriptor,BackupDataOutput,ParcelFileDescriptor)
-onBackup()} method), though there is no guarantee when it will occur. However, you can force all
-pending backup operations to run immediately by using the <code>bmgr run</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr run</pre>
-
-<p>This causes a backup pass to execute immediately, invoking the backup agents of all applications
-that had previously called {@link android.app.backup.BackupManager#dataChanged()} since the
-last backup operation, plus any applications which had been manually scheduled for
-backup via <code>bmgr backup</code>.
-
-
-
-<h2 id="restore">Forcing a Restore Operation</h2>
-
-<p>Unlike backup operations, which are batched together and run on an occasional basis, restore
-operations execute immediately. The Backup Manager currently provides two kinds of restore
-operations. The first kind restores an entire device with the data that has been backed up. This
-is typically performed only when a device is first provisioned (to replicate settings and other
-saved state from the user's previous device) and is an operation that only the system can
-perform. The second kind of restore operation restores
-a single application to its "active" data set; that is, the application will abandon its current
-data and revert to the last-known-good data that is held in the current backup image. You can
-invoke this second restore operation with the {@link
-android.app.backup.BackupManager#requestRestore(RestoreObserver) requestRestore()} method. The
-Backup Manager will then invoke your backup agent's {@link
-android.app.backup.BackupAgent#onRestore(BackupDataInput,int,ParcelFileDescriptor)
-onRestore()} implementation.
-
-<p>While testing your application, you can immediately invoke the restore operation (bypassing the
-{@link android.app.backup.BackupManager#requestRestore(RestoreObserver) requestRestore()} method)
-for your application by using the <code>bmgr restore</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr restore <em><package></em></pre>
-
-<p><code><em><package></em></code> is the formal Java-style package name of the application
-participating in the backup/restore mechanism, which you would like to restore. The Backup
-Manager will immediately instantiate the application's backup agent and invoke it for restore. This
-will happen even if your application is not currently running.
-
-
-
-
-
-<h2 id="other">Other Commands</h2>
-
-<h3>Wiping data</h3>
-
-<p>The data for a single application can be erased from the active data set on demand. This is
-very useful while you're developing a backup agent, in case bugs lead you to write corrupt data
-or saved state information. You can wipe an application's data with the <code>bmgr wipe</code>
-command:
-
- <pre class="no-pretty-print">adb shell bmgr wipe <em><package></em></pre>
-
-<p><code><em><package></em></code> is the formal package name of the application whose data
-you wish to
-erase. The next backup operation that the application's agent processes will look as
-though the application had never backed anything up before.
-
-
-<h3>Enabling and disabling backup</h3>
-
-<p>You can see whether the Backup Manager is operational at all with the <code>bmgr
-enabled</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr enabled</pre>
-
-<p>This might be useful if your application's backup agent is never being invoked for backup, to
-verify whether the operating system thinks it should be performing such operations at all.</p>
-
-<p>You can also directly disable or enable the Backup Manager with this command:
-
- <pre class="no-pretty-print">adb shell bmgr enable <em><boolean></em></pre>
-
-<p><code><em><boolean></em></code> is either <code>true</code> or <code>false</code>.
-This is equivalent to disabling or enabling backup in the device's main Settings UI.</p>
-
-<p class="warning"><strong>Warning!</strong> When backup is disabled, the current backup transport
-will explicitly wipe
-the entire active data set from its backend storage. This is so that when a user says
-they do <em>not</em> want their data backed up, the Backup Manager respects that wish. No further
-data will be saved from the device, and no restore operations will be possible, unless the Backup
-Manager is re-enabled (either through Settings or through the above <code>bmgr</code> command).
-
-
-
-
-<!-- The following is not useful to applications, but may be some useful information some day...
-
-
-<h2 id="transports">Applying a Backup Transport</h2>
-
-<p>A "backup transport" is the code module responsible for moving backup and restore data
-to and from some storage location. A device can have multipe transports installed, though only
-one is active at any given time. Transports are identified by name. You can see what
-transports are available on your device or emulator by running the
-<code>bmgr list transports</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr list transports</pre>
-
-<p>The output of this command is a list of the transports available on the device. The currently
-active transport is flagged with a <code>*</code> character. Transport names may look like
-component names (for example, <code>android/com.android.internal.backup.LocalTransport</code>),
-but they need not be, and the strings are never used as direct class references. The use of
-a component-like naming scheme is simply for purposes of preventing name collisions.
-
-<p>You can change which transport is currently active from the command line as well:
-
- <pre class="no-pretty-print">adb shell bmgr transport <em><name></em></pre>
-
-<p><code><em><name></em></code> is one of the names as printed by the <code>bmgr list
-transports</code>
-command. From this point forward, backup and restore operations will be directed through the
-newly-selected transport. Backup state tracking is managed separately for each transport, so
-switching back and forth between them will not corrupt the saved state.
-
-
-
-
-<h2 id="restoresets">Viewing Restore Sets</h2>
-
-<p>All of the application data that a device has written to its backup transport is tracked
-as a group that is collectively called a "restore set," because each data set is
-most often manipulated during a restore operation. When a device is provisioned for the first
-time, a new restore set is established. You can get a listing of all the restore sets available to
-the current transport by running the <code>bmgr list sets</code> command:
-
- <pre class="no-pretty-print">adb shell bmgr list sets</pre>
-
-<p>The output is a listing of available restore sets, one per line. The first item on each line is
-a token (a hexadecimal value that identifies the restore set to the transport). Following
-the token is a string that briefly identifies the restore set.
-Only the token is used within the backup and restore mechanism.
-
-
--->
+++ /dev/null
-<html>
-<head>
-<meta http-equiv="refresh" content="0;url=http://developer.android.com/tools/debugging/ddms.html">
-<title>Redirecting...</title>
-</head>
-<body>
-<p>You should be redirected. Please <a
-href="http://developer.android.com/tools/debugging/ddms.html">click here</a>.</p>
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-page.title=Desktop Head Unit
-page.tags="auto", "car", "testing","dhu"
-@jd:body
-
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#launching-dhu">Launching the DHU</a></li>
- <li><a href="#dhu-commands">Issuing DHU Commands</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/auto/start/index.html#test-it-dhu">Run and Test Auto Apps</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<p>The Desktop Head Unit (DHU) enables your development machine to emulate an Android Auto
-head unit, so you can easily run and test Android Auto apps. The DHU runs on
-Windows, Mac, and Linux hosts and replaces previous Android Auto simulators,
-such as the Android Media Browser and Messaging
-simulators.</p>
-
-<p class="note"><strong>Note:</strong> For other information about testing Auto apps, see the
-training lesson
-<a href="{@docRoot}training/auto/start/index.html#test-it-dhu">Run and Test Auto Apps</a>. </p>
-
-
-<h2 id="launching-dhu">Launching the DHU</h2>
-
-<p>
- To launch the DHU, run the <code>desktop-head-unit.exe</code> (on Windows)
- or <code>desktop-head-unit</code> (on Mac or Linux) command, as described in
- <a href="{@docRoot}training/auto/start/index.html#connecting-dhu">Connecting
- the DHU to your mobile device</a>.
-</p>
-
-<p>
- By default, the DHU emulates the most common form of Android Auto-compatible
- head unit, which uses a touch screen user interface. You can simulate user
- touches by clicking the DHU with a mouse. To emulate head units which use
- a rotary controller for input, you can use the <code>-i controller</code> flag,
- as in this example:
-</p>
-
-<pre class="no-pretty-print">$ ./desktop-head-unit -i controller</pre>
-
-<p>
- When the DHU is in rotary-controller mode you can simulate controller
- operations by using keyboard shortcuts, as described in <a href=
- "#cmd-bindings">DHU commands and key bindings</a>. If the DHU is in rotary
- controller mode, it ignores mouse clicks; you must operate Android Auto with
- the simulated rotary controller operations.
-</p>
-
-<h2 id="dhu-commands">Issuing DHU Commands</h2>
-
-<p>
- DHU commands allow you to test your app with Android Auto features, such as
- playing voice input or switching between night and day display mode. You can issue commands to
- the DHU by running commands from the terminal window where you launched DHU.
- You can also issue commands by selecting the DHU window and
- using keyboard shortcuts. The DHU commands
- and key bindings for all controls are listed in <a href="#cmd-bindings">DHU
- commands and key bindings</a>.
-</p>
-
-
-<h3 id="day-night">Switching between day and night mode</h3>
-
-<p>
- Android Auto supports different color schemes for day and night. You should test your app in both
- day and night mode. You can switch between night and day mode in either of the
- following ways:
-</p>
-
-<ul>
- <li>Run the command <code>daynight</code> in the terminal where you launched the DHU.
- </li>
-
- <li>Select the DHU window and press the <strong>N</strong> key.
- </li>
-</ul>
-
-<h3>Microphone testing</h3>
-
-<p>The DHU supports using a microphone for voice input. You can also instruct the DHU to treat
-a pre-recorded voice track as input, as if the DHU had heard the track through the microphone.</p>
-
-<p>To use a pre-recorded sound file as input, enter this command: </p>
-<pre class="no-pretty-print">
-$ mic play <sound_file_path>/<sound_file>.wav
-</pre>
-
-<p>For your convenience, we have provided the following sound files for common
-voice commands. These sound files are installed in the
-<code><sdk>/extras/google/auto/voice/</code> directory.</p>
-
-<dl>
- <dt>
- <code>exitnav.wav</code>
- </dt>
-
- <dd>
- "Exit navigation."
- </dd>
-
- <dt>
- <code>navgoogle.wav</code>
- </dt>
-
- <dd>
- "Navigate to 1600 Amphitheatre Parkway, Mountain View."
- </dd>
-
- <dt>
- <code>navsoh.wav</code>
- </dt>
-
- <dd>
- "Navigate to Sydney Opera House."
- </dd>
-
- <dt>
- <code>nextturn.wav</code>
- </dt>
-
- <dd>
- "When is my next turn?"
- </dd>
-
- <dt>
- <code>showalternateroute.wav</code>
- </dt>
-
- <dd>
- "Show alternate routes.""
- </dd>
-
- <dt>
- <code>howlong.wav</code>
- </dt>
-
- <dd>
- "How long until I get there?"
- </dd>
-
- <dt>
- <code>navhome.wav</code>
- </dt>
-
- <dd>
- "Navigate to home."
- </dd>
-
- <dt>
- <code>navwork.wav</code>
- </dt>
-
- <dd>
- "Navigate to work.""
- </dd>
-
- <dt>
- <code>pause.wav</code>
- </dt>
-
- <dd>
- "Pause music."
- </dd>
-
- <dt>
- <code>showtraffic.wav</code>
- </dt>
-
- <dd>
- "Show traffic."
- </dd>
-</dl>
-<h3 id="cmd-bindings">DHU commands and key bindings</h3>
-
-<p>The DHU supports the following commands.</p>
-
-<p class="table-caption" id="table-commands"><strong>Table 1.</strong> Commands and key bindings</p>
-<table>
-<tr>
- <th>Category</th>
- <th>Command</th>
- <th>Subcommand</th>
- <th>Argument(s)</th>
- <th>Keyboard Shortcut(s)</th>
- <th>Description</th>
-</tr>
-
-<!--system-->
-
-<tr>
-<td rowspan="4">System</td>
-<td>help</td>
-<td></td>
-<td>[command]</td>
-<td></td>
-<td>Shows the full command set. Specifying a command name (for example, <code>help day</code>)
- causes the system to show help for that command.</td>
-</tr>
-
-<tr>
-
-<td>quit</td>
-<td></td>
-<td></td>
-<td>Alt+q</td>
-<td>Quits the head unit.</td>
-</tr>
-
-<tr>
-
-<td>sleep</td>
-<td></td>
-<td>[seconds]</td>
-<td></td>
-<td>Sleeps for one second. Specifying an argument (for example, <code>sleep 30</code>) causes the
-system to sleep the specified number of seconds. This command
-is useful if you are writing scripts for the DHU. (You can run a script by using I/O redirection
-from the command line: <code>./desktop-head-unit < script.txt</code> loads commands from the
-file <code>script.txt</code>.)</td>
-</tr>
-
-<tr>
-
-<td>screenshot</td>
-<td></td>
-<td>filename.png</td>
-<td></td>
-<td>Saves a screenshot to <code>filename.png</code>.</td>
-</tr>
-
-
-<!--microphone-->
-
-<tr>
-<td rowspan="3">Microphone</td>
-<td rowspan="3">mic</td>
-<td>begin</td>
-<td></td>
-<td>m </td>
-<td>Activates the microphone (equivalent to clicking the steering wheel's microphone button) and
-waits for input from the computer microphone.</td>
-</tr>
-
-<tr>
-
-
-<td>play</td>
-<td>filename.wav</td>
-<td></td>
-<td>Causes the DHU to treat <code>filename.wav</code> as voice input, as if it had heard that sound
- through the microphone. You do not hear the sound file being played, but you do hear
- the response from Android Auto.</td>
-</tr>
-
-<tr>
-
-
-<td>repeat</td>
-<td></td>
-<td></td>
-<td>Repeats the last <code>mic play</code> command, as if you had called <code>mic play</code>
- again with the same sound file parameter.</td>
-</tr>
-
-<!--Input-->
-
-<tr>
-<td rowspan="7">Input</td>
-<td rowspan="6">dpad</td>
-<td>up <br> down <br> left <br> right</td>
-<td></td>
-<td>Arrow keys</td>
-<td>Simulates moving the rotary controller.</td>
-</tr>
-
-<tr>
-
-
-<td>soft left <br> soft right</td>
-<td></td>
-<td>Shift+Arrow keys</td>
-<td>Simulates pressing the side buttons available on some rotary controllers.</td>
-</tr>
-
-<tr>
-
-
-<td>click</td>
-<td></td>
-<td>Return</td>
-<td>Simulates pressing the rotary controller.</td>
-</tr>
-
-<tr>
-
-
-<td>back</td>
-<td></td>
-<td>Backspace</td>
-<td>Simulates pressing the <strong>back</strong> button available below some rotary
- controllers.</td>
-</tr>
-
-<tr>
-
-
-<td>rotate left <br> rotate right</td>
-<td></td>
-<td>1 <br> 2</td>
-<td>Simulates rotating the rotary controller left (counter-clockwise) or right (clockwise).</td>
-</tr>
-
-<tr>
-
-
-<td>flick left <br> flick right</td>
-<td></td>
-<td>Shift+1 <br> Shift+2</td>
-<td>Simulates a fast spin of the rotary controller to the left (counter-clockwise) or right
- (clockwise).</td>
-</tr>
-
-<tr>
-
-<td>tap</td>
-<td></td>
-<td>x y</td>
-<td></td>
-<td>Simulates a touch event at the specified coordinates. For example, <code>tap 50 100</code></td>
-</tr>
-
-
-<!--Day/Night-->
-
-<tr>
-<td rowspan="3">Day/Night</td>
-<td>day</td>
-<td></td>
-<td></td>
-<td>Shift+n</td>
-<td>Activates day mode (high brightness, full color).</td>
-</tr>
-
-<tr>
-
-<td>night</td>
-<td></td>
-<td> </td>
-<td>Ctrl+n </td>
-<td>Activates night mode (low brightness, high contrast).</td>
-</tr>
-
-<tr>
-
-<td>daynight</td>
-<td></td>
-<td></td>
-<td>n </td>
-<td>Toggles current day/night mode.</td>
-</tr>
-
-</table>
-
-
-
-
-<h2 id="auto-simulators">Media Browser and Messaging Simulators</h2>
-
-<p class="caution"><strong>Important:</strong> Use of the Android Media Browser and Messaging
-Simulators for testing Android Auto apps is deprecated. Instead, we recommend using the
-Desktop Head Unit, which enables your development machine to act as if it were an Android Auto head
-unit.</p>
-
-<p>To get the simulators, open the
-<a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> and download
-them from <strong>Extras > Android Auto API Simulators</strong>.</p>
-
-<p>Before you begin testing, compile your app in your development environment.
-Install your app and the Android simulator for the features you want to test
-(that is, audio or messaging) on a physical or virtual device running Android
-5.0 (API level 21) or higher. To check the version of Android on the device, go
-to <strong>Settings > About phone</strong> (or <strong>About tablet</strong>)
-<strong>> Android Version</strong>.</p>
-
-<h3 id="testing-audio-apps">Testing audio apps</h3>
-<p>To run and test audio apps:</p>
-
-<ol>
-<li>Install the Android Media Browser simulator
-({@code <sdk>/extras/google/simulators/media-browser-simulator.apk}) on
-the test device. You can do this using
-the <a href="{@docRoot}tools/help/adb.html#move">adb</a> command line tool.</li>
-<li>Enable <a href="{@docRoot}tools/device.html#developer-device-options">
-developer options</a> on the test device.</li>
-<li>Install your app on the test device.</li>
-<li>Launch the Android Media Browser simulator to see how your audio app
-appears in Auto. If your app does not appear, stop the simulator from
-<strong>Settings > Apps</strong> and restart it.</li>
-</ol>
-
-
-<h3 id="testing-messaging-apps">Testing messaging apps</h3>
-<p>To run and test messaging apps:</p>
-
-<ol>
-<li>Install the Android Messaging simulator
- ({@code <sdk>/extras/google/simulators/messaging-simulator.apk})
-on the test device. You can do this using the
-<a href="{@docRoot}tools/help/adb.html#move">adb</a> command line tool.</li>
-<li>Enable the simulator to read notifications posted on the system:
-<ol type="a">
- <li>Enable <a href="{@docRoot}tools/device.html#developer-device-options">
-developer options</a> on the test device.</li>
- <li>Click <strong>Settings > Sounds & Notifications > Notification
- Access</strong> and check the box labeled
- <strong>Messaging Simulator</strong>.</li>
-</ol>
-<li>Install your app on the test device.</li>
-<li>Launch the Android Messaging Simulator to see how your messaging app appears
-in Auto. If your app does not appear, stop the simulator from
-<strong>Settings > Apps</strong> and restart it.</li>
-</ol>
-
-
-
-
+++ /dev/null
-page.title=dmtracedump
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-
- <p><code>dmtracedump</code> is a tool that gives you an alternate way of generating
- graphical call-stack diagrams from trace log files (instead of using Traceview).</p>
-
- <p>This document is a reference to the available command line options. For more information on generating trace
- logs, see <a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with
- Traceview and dmtracedump</a>.</p>
-
- <p>The usage for <code>dmtracedump</code> is:</p>
- <pre>
-dmtracedump [-ho] [-s sortable] [-d trace-base-name] [-g outfile] <trace-base-name>
-</pre>
-
- <p>The tool then loads trace log data from <code><trace-base-name>.data</code> and
- <trace-base-name>.key. The table below lists the options for dmtracedump.</p>
-
- <table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><nobr><code>-d <em><trace-base-name></em></code></nobr></td>
-
- <td>Diff with this trace name</td>
- </tr>
-
- <tr>
- <td><code>-g <em><outfile></em></code></td>
-
- <td>Generate output to <outfile></td>
- </tr>
-
- <tr>
- <td><code>-h</code></td>
-
- <td>Turn on HTML output</td>
- </tr>
-
- <tr>
- <td><code>-o</code></td>
-
- <td>Dump the trace file instead of profiling</td>
- </tr>
-
- <tr>
- <td><code>-d <em><trace-base-name></em></code></td>
-
- <td>URL base to the location of the sortable javascript file</td>
- </tr>
-
- <tr>
- <td><code>-t <percent></code></td>
-
- <td>Minimum threshold for including child nodes in the graph (child's inclusive time as a
- percentage of parent inclusive time). If this option is not used, the default threshold is
- 20%.</td>
- </tr>
- </table>
\ No newline at end of file
+++ /dev/null
-page.title=Draw 9-patch
-page.tags=NinePatch
-@jd:body
-
-<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 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, 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
- (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
- 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
- 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>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 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"
-/>
-
-<p>Optional controls include:</p>
-<ul>
- <li><strong>Zoom</strong>: Adjust the zoom level of the graphic in the drawing area.</li>
- <li><strong>Patch scale</strong>: Adjust the scale of the images in the preview area.</li>
- <li><strong>Show lock</strong>: Visualize the non-drawable area of the graphic on mouse-over.</li>
- <li><strong>Show patches</strong>: Preview the stretchable patches in the drawing area (pink is a
- stretchable patch).</li>
- <li><strong>Show content</strong>: Highlight the content area in the preview images
- (purple is the area in which content is allowed).</li>
- <li><strong>Show bad patches</strong>: Adds a red border around patch areas that may
- produce artifacts in the graphic when stretched. Visual coherence of your stretched
- image will be maintained if you eliminate all bad patches.</li>
-<ul>
+++ /dev/null
-page.title=Using Android Emulator Command-Line Features
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#starting">Starting and Stopping the Emulator</a></li>
- <li><a href="#apps">Installing Applications on the Emulator</a></li>
- <li><a href="#startup-options">Using Command Line Parameters</a></li>
- <li><a href="#acceleration">Using Hardware Acceleration</a>
- <ol>
- <li><a href="#accel-graphics">Configuring Graphics Acceleration</a></li>
- <li><a href="#accel-vm">Configuring Virtual Machine Acceleration</a></li>
- </ol>
- </li>
- <li><a href="#sdcard">Using SD Card Emulation</a>
- <ol>
- <li><a href="#sdcard-creating">Creating an SD card image</a></li>
- <li><a href="#sdcard-files">Copying files to an SD card image</a></li>
- <li><a href="#sdcard-loading">Loading an SD card image</a></li>
- </ol>
- </li>
- <li><a href="#diskimages">Working With Emulator Disk Images</a>
- <ol>
- <li><a href="#defaultimages">Default image files</a></li>
- <li><a href="#runtimeimages">Runtime images: user data and SD card</a></li>
- <li><a href="#temporaryimages">Temporary images</a></li>
- </ol>
- </li>
- <li><a href="#emulatornetworking">Setting Up Emulator Networking</a>
- <ol>
- <li><a href="#networkaddresses">Network Address Space</a></li>
- <li><a href="#networkinglimitations">Local Networking Limitations</a></li>
- <li><a href="#redirection">Using Network Redirection</a></li>
- <li><a href="#dns">Configuring the Emulator's DNS Settings</a></li>
- <li><a href="#proxy">Using the Emulator with a Proxy</a></li>
- <li><a href="#connecting">Interconnecting Emulator Instances</a></li>
- <li><a href="#calling">Sending a Voice Call or SMS to Another Emulator Instance</a></li>
- </ol>
- </li>
- <li><a href="#console">Using the Emulator Console</a>
- <ol>
- <li><a href="#portredirection">Port Redirection</a></li>
- <li><a href="#geo">Geo Location Provider Emulation</a></li>
- <li><a href="#events">Hardware Events Emulation</a></li>
- <li><a href="#power">Device Power Characteristics</a></li>
- <li><a href="#netstatus">Network Status</a></li>
- <li><a href="#netdelay">Network Delay Emulation</a></li>
- <li><a href="#netspeed">Network Speed Emulation</a></li>
- <li><a href="#telephony">Telephony Emulation</a></li>
- <li><a href="#sms">SMS Emulation</a></li>
- <li><a href="#vm">VM State</a></li>
- <li><a href="#window">Emulator Window</a></li>
- <li><a href="#terminating">Terminating an Emulator Instance</a></li>
- </ol>
- </li>
- <li><a href="#troubleshooting">Troubleshooting Emulator Problems</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/devices/emulator.html">Running Apps in the Android Emulator</a></li>
- <li><a href="{@docRoot}tools/devices/managing-avds.html">Managing AVDs with the AVD Manager</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<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>This page describes command line features that you can use with the
-Android Emulator.
-For information about using the Android Emulator UI, see
-<a href="{@docRoot}tools/devices/emulator.html">Using the Android Emulator</a>.
-</p>
-
-
-<h2 id="starting">Starting and Stopping the Emulator</h2>
-
-<p>During development and testing of your application, you install and run your
-application in the Android Emulator. You can launch the emulator as a standalone
-application from a command line, or you can run it from within your Android Studio
-development environment. In either case, you specify the AVD configuration to
-load and any startup options you want to use, as described in this document.
-</p>
-
-<p>You can run your application on a single instance of the emulator or,
-depending on your needs, you can start multiple emulator instances and run your
-application in more than one emulated device. You can use the emulator's
-built-in commands to simulate GSM phone calling or SMS between emulator
-instances, and you can set up network redirection that allows emulators to send
-data to one another. For more information, see <a href="#telephony">Telephony
-Emulation</a>, <a href="#sms">SMS Emulation</a>, and
-<a href="#emulatornetworking">Emulator Networking</a></p>
-
-<p>To start an instance of the emulator from the command line, navigate to the
-<code>tools/</code> folder of the SDK. Enter <code>emulator</code> command
-like this: </p>
-
-<pre>emulator -avd <avd_name> [<options>]</pre>
-
-<p>This initializes the emulator, loads an AVD configuration and displays the emulator
-window. For more information about command line options for the emulator, see the
-<a href="{@docRoot}tools/help/emulator.html">Android Emulator</a> tool reference.</p>
-
-<p class="note"><strong>Note:</strong> You can run multiple
-instances of the emulator concurrently, each with its own AVD configuration and
-storage area for user data, SD card, and so on.</p>
-
-<p>When you run your app from Android Studio, it installs and launches the
-app on your connected device or emulator (launching the emulator, if necessary).
-You can specify emulator startup options in the Run/Debug
-dialog, in the Target tab. When the emulator is running, you can issue
-console commands as described later in this document.</p>
-
-<p>If you are not working in Android Studio, see <a href="#apps">Installing Applications
-on the Emulator</a> for information about how to install your application.</p>
-
-<p>To stop an emulator instance, just close the emulator's window.</p>
-
-<p>For a reference of the emulator's startup commands and keyboard mapping, see
-the <a href="{@docRoot}tools/help/emulator.html">Android Emulator</a> tool
-reference.</p>
-
-
-<h2 id="apps">Installing Applications on the Emulator</h2>
-
-<p>If you don't have access to Android Studio, you can install your application on the
-emulator using the <a href="{@docRoot}tools/help/adb.html#move">adb</a> utility. Before
-installing the application, you need to build and package it into an <code>.apk</code> as described
-in <a href="{@docRoot}tools/building/index.html">Building and
-Running Apps</a>. Once the application is installed, you can start the emulator from the command
-line as described previously, using any startup options necessary.
-When the emulator is running, you can also connect to the emulator instance's
-<a href="#console">console</a> to issue commands as needed.</p>
-
-<p>As you update your code, you periodically package and install it on the emulator.
-The emulator preserves the application and its state data across restarts,
-in a user-data disk partition. To ensure that the application runs properly
-as you update it, you may need to delete the emulator's user-data partition.
-To do so, start the emulator with the <code>-wipe-data</code> option.
-For more information about the user-data partition and other emulator storage,
-see <a href="#diskimages">Working with Emulator Disk Images</a>.</p>
-
-<h2 id="startup-options">Using 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>
- <th width="20%" >Option</th>
- <th width="30%" >Description</th>
- <th width="40%" >Comments</th>
-</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}tools/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>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 {@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.
-
-<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.
- 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
- 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>-nocache</code></td>
- <td>Start the emulator without a cache partition.</td>
- <td>See also <code>-cache <file></code>.</td>
-</tr>
-<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>
-</tr>
-<tr>
- <td><code>-sdcard <filepath></code></td>
- <td>Use <file> as the SD card image.</td>
- <td>Default value is <code><system>/sdcard.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>
- <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
- 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>
- <td>See also <code>-initdata</code>.
- <p>For more information on disk images, use <code>-help-disk-images</code>.</p>
-</td>
-</tr>
-<tr>
- <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.
- Use <code>-help-debug-tags</code> to print a list of debug component names that you can use. </td>
-</tr>
-<tr>
- <td><code>-debug-<tag></code></td>
- <td>Enable/disable debug messages for the specified debug tag.</td>
- <td rowspan="2">Use <code>-help-debug-tags</code> to print a list of debug component names that you can use in <code><tag></code>. </td>
-</tr>
-<tr>
- <td><code>-debug-no-<tag></code></td>
- <td>Disable debug messages for the specified debug tag.</td>
-</tr>
-<tr>
- <td><code>-logcat <logtags></code></td>
- <td>Enable logcat output with given tags.</td>
- <td>If the environment variable ANDROID_LOG_TAGS is defined and not
- empty, its value will be used to enable logcat output by default.</td>
-</tr>
-<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.
- 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
- 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">http://wiki.qemu.org/download/qemu-doc.html</a>
- for a list of device types.
-
-<p>Here are some examples: </p>
-<ul>
- <li><code>-shell-serial stdio</code> is identical to <code>-shell</code></li>
- <li><code>-shell-serial tcp::4444,server,nowait</code> lets you communicate with the shell over TCP port 4444</li>
- <li><code>-shell-serial fdpair:3:6</code> lets a parent process communicate with the shell using fds 3 (in) and 6 (out)</li>
- <li><code>-shell-serial fdpair:0:1</code> uses the normal stdin and stdout fds, except that QEMU won't tty-cook the data.</li>
- </ul>
-</td>
-</tr>
-<tr>
- <td><code>-show-kernel <name></code></td>
- <td>Display kernel messages.</td>
- <td> </td>
-</tr>
-<tr>
- <td><code>-trace <name></code></td>
- <td>Enable code profiling (press F9 to start), written to a specified file.</td>
- <td> </td>
-</tr>
-<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:
-<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><code>ANDROID_VERBOSE=init,modem</code></p>
-<p>For more information about debug tags, use <code><-help-debug-tags></code>.</p>
-</td>
-</tr>
-<tr>
- <td rowspan="6">Media</td>
- <td><code>-audio <backend></code></td>
- <td>Use the specified audio backend.</td>
- <td> </td>
-</tr>
-<tr>
- <td><code>-audio-in <backend></code></td>
- <td>Use the specified audio-input backend.</td>
- <td> </td>
-</tr>
-<tr>
- <td><code>-audio-out <backend></code></td>
- <td>Use the specified audio-output backend.</td>
- <td> </td>
-</tr>
-<!--<tr>
- <td><code>-mic <device or file></code></td>
- <td>Use device or WAV file for audio input.</td>
- <td> </td>
-</tr>
--->
-<tr>
- <td><code>-noaudio</code></td>
- <td>Disable audio support in the current emulator instance.</td>
- <td> </td>
-</tr>
-<tr>
- <td><code>-radio <device></code></td>
- <td>Redirect radio modem interface to a host character device.</td>
- <td> </td></tr>
-<tr>
- <td><code>-useaudio</code></td>
- <td>Enable audio support in the current emulator instance.</td>
- <td>Enabled by default. </td>
-</tr>
-
-<tr>
- <td rowspan="7">Network</td>
- <td><code>-dns-server <servers></code></td>
- <td>Use the specified DNS server(s). </td>
- <td>The value of <code><servers></code> must be a comma-separated list of up to 4 DNS server names or
- IP addresses.</td>
-</tr>
-<tr>
- <td><code>-http-proxy <proxy></code></td>
- <td>Make all TCP connections through a specified HTTP/HTTPS proxy</td>
- <td>The value of <code><proxy></code> can be one of the following:<br>
- <code>http://<server>:<port></code><br>
- <code>http://<username>:<password>@<server>:<port></code>
- <p>The <code>http://</code> prefix can be omitted. If the <code>-http-proxy <proxy></code> command is not supplied,
- the emulator looks up the <code>http_proxy</code> environment variable and automatically uses any value matching
- the <code><proxy></code> format described above.</p></td>
-</tr>
-<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="{@docRoot}tools/devices/emulator.html#netdelay">Network Delay Emulation</a>
- for supported <code><delay></code> values. </td>
-</tr>
-<tr>
- <td><code>-netfast</code></td>
- <td>Shortcut for <code>-netspeed full -netdelay none</code></td>
- <td> </td></tr>
-<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="{@docRoot}tools/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
- 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
- before starting the emulation. </td>
- <td><code><socket></code> must use one of these formats:
-
-<p><code>tcp:<port>[,server][,max=<seconds>]</code></br>
-<code>unix:<port>[,server][,max=<seconds>]</code></p>
-
-<p>Use <code>-help-report-console</code></p> to view more information about this topic. </td>
-</tr>
-<tr>
- <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
-scale in direct relationship with <delay> values.</p>
-</td>
-</tr>
-<tr>
- <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://wiki.qemu.org/download/qemu-doc.html">http://wiki.qemu.org/download/qemu-doc.html</a>.
-</td>
-</tr>
-<tr>
- <td><code>-nojni</code></td>
- <td>Disable JNI checks in the Dalvik runtime.</td><td> </td></tr>
-<tr>
- <td><code>-qemu</code></td>
- <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}tools/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}tools/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://wiki.qemu.org/download/qemu-doc.html">http://wiki.qemu.org/download/qemu-doc.html</a>.
-</td>
-</tr>
-<tr>
- <td><code>-timezone <timezone></code></td>
- <td>Set the timezone for the emulated device to <timezone>, instead of the host's timezone.</td>
- <td><code><timezone></code> must be specified in zoneinfo format. For example:
-<p>"America/Los_Angeles"<br>
-"Europe/Paris"</p>
-</td>
-</tr>
-<tr>
- <td><code>-version</code></td>
- <td>Display the emulator's version number.</td>
- <td> </td>
-</tr>
-<tr>
- <td rowspan="12">UI</td>
- <td><code>-dpi-device <dpi></code></td>
- <td>Scale the resolution of the emulator to match the screen size
- of a physical device.</td>
- <td>The default value is 165. See also <code>-scale</code>.</td>
-</tr>
-<tr>
- <td><code>-no-boot-anim</code></td>
- <td>Disable the boot animation during emulator startup.</td>
- <td>Disabling the boot animation can speed the startup time for the emulator.</td>
-</tr>
-<tr>
- <td><code>-no-window</code></td>
- <td>Disable the emulator's graphical window display.</td>
- <td> </td>
-</tr>
-<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"
- tells the emulator to select the best window size.</td>
-</tr>
-<tr>
- <td><code>-raw-keys</code></td>
- <td>Disable Unicode keyboard reverse-mapping.</td>
- <td> </td></tr>
-<tr>
- <td><code>-noskin</code></td>
- <td>Don't use any emulator skin.</td>
- <td> </td></tr>
-<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.
- For more information, use <code>-help-keyset</code> to print information about this topic.
-</td>
-</tr>
-<tr>
- <td><code>-onion <image></code></td>
- <td>Use overlay image over screen.</td>
- <td>No support for JPEG. Only PNG is supported.</td></tr>
-<tr>
- <td><code>-onion-alpha <percent></code></td>
- <td>Specify onion skin translucency value (as percent).
- <td>Default is 50.</td>
-</tr>
-<tr>
- <td><code>-onion-rotation <position></code></td>
- <td>Specify onion skin rotation.
- <td><code><position></code> must be one of the values 0, 1, 2, 3.</td>
-</tr>
-<tr>
- <td><code>-skin <skinID></code></td>
- <td>This emulator option is deprecated. </td>
- <td>Please set skin options using AVDs, rather than by using this emulator
-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}tools/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>
-<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>
-
-
-<h2 id="acceleration">Using Hardware Acceleration</h2>
-
-<p>To make the Android emulator run faster and be more responsive, you can configure it to
-take advantage of hardware acceleration, using a combination of configuration options, specific
-Android system images and hardware drivers.</p>
-
-
-<h3 id="accel-graphics">Configuring Graphics Acceleration</h3>
-
-<p class="caution"><strong>Caution:</strong> As of SDK Tools Revision 17, the graphics
-acceleration feature for the emulator is experimental; be alert for incompatibilities and
-errors when using this feature. </p>
-
-<p>Graphics acceleration for the emulator takes advantage of your development computer's graphics
-hardware, specifically its graphics processing unit (GPU), to make screen drawing faster. To use
-the graphics acceleration feature, you must have the following versions of the Android development
-tools installed:</p>
-
-<ul>
- <li>Android SDK Tools, Revision 17 or higher</li>
- <li>Android SDK Platform API 15, Revision 3 or higher</li>
-</ul>
-
-<p>Use the <a href="{@docRoot}sdk/installing/index.html#AddingComponents">Android SDK
-Manager</a> to install these components:</p>
-
-<p class="note"><strong>Note:</strong> Not all applications are compatible with graphics hardware
-acceleration. In particular, the Browser application and applications using the {@link
-android.webkit.WebView} component are not compatible with graphics acceleration.</p>
-
-<p>To configure an AVD to use graphics acceleration:</p>
-
-<ol>
- <li>Make sure you have the required SDK components installed (listed above).</li>
- <li>Start the AVD Manager and create a new AVD with the <strong>Target</strong> value of
-<strong>Android 4.0.3 (API Level 15)</strong>, revision 3 or higher.</li>
- <li>If you want to have graphics acceleration enabled by default for this AVD, in the
-<strong>Hardware</strong> section, click <strong>New</strong>, select <strong>GPU emulation</strong>
-and set the value to <strong>Yes</strong>.
- <p class="note"><strong>Note:</strong> You can also enable graphics acceleration when you
-start an emulator using command line options as describe in the next section.</p>
- </li>
- <li>Name the AVD instance and select any other configuration options.
- <p class="caution"><strong>Caution:</strong> Do not select the <strong>Snapshot: Enabled</strong>
-option. Snapshots are not supported for emulators with graphics acceleration enabled.</p>
- </li>
- <li>Click <strong>Create AVD</strong> to save the emulator configuration.</li>
-</ol>
-
-<p>If you set <strong>GPU emulation</strong> to <strong>Yes</strong> for your AVD, then graphics
-acceleration is automatically enabled when you run it. If you did not enable <strong>GPU
-emulation</strong> when you created the AVD, you can still enable it at runtime.</p>
-
-<p>To enable graphics acceleration at runtime for an AVD:</p>
-
-<ul>
- <li>If you are running the emulator from the command line, just include the {@code -gpu on}
-option:
-<pre>emulator -avd <avd_name> -gpu on</pre>
- <p class="note"><strong>Note:</strong> You must specify an AVD configuration that uses
-Android 4.0.3 (API Level 15, revision 3) or higher system image target. Graphics acceleration is not
-available for earlier system images.</p>
- </li>
- <li>If you are running the emulator from Android Studio, run your Android application using an AVD
-with the {@code -gpu on} option enabled:
- <ol>
- <li>In Android Studio, click your Android application module folder and then select
- <strong>Run > Edit Configurations...</strong></li>
- <li>In the left panel of the <strong>Run/Debug Configurations</strong> dialog, select your Android
- run configuration or create a new configuration.</li>
- <li>Under the <strong>Target Device </strong> options,
- select the AVD you created in the previous procedure.</li>
- <li>In the <strong>Emulator</strong> tab, in the
- <strong>Additional command line options</strong> field, enter:<br>
- {@code -gpu on}</li>
- <li>Run your Android project using this run configuration.</li>
- </ol>
- </li>
-</ul>
-
-
-<h3 id="accel-vm">Configuring Virtual Machine Acceleration</h2>
-
-<p class="caution"><strong>Caution:</strong> As of SDK Tools Revision 17, the virtual machine
-acceleration feature for the emulator is experimental; be alert for incompatibilities and errors
-when using this feature.</p>
-
-<p>Many modern CPUs provide extensions for running virtual machines (VMs) more efficiently. Taking
-advantage of these extensions with the Android emulator requires some additional configuration of
-your development system, but can significantly improve the execution speed. Before attempting to use
-this type of acceleration, you should first determine if your development system’s CPU supports one
-of the following virtualization extensions technologies:</p>
-
-<ul>
- <li>Intel Virtualization Technology (VT, VT-x, vmx) extensions</li>
- <li>AMD Virtualization (AMD-V, SVM) extensions (only supported for Linux)</li>
-</ul>
-
-<p>The specifications from the manufacturer of your CPU should indicate if it supports
-virtualization extensions. If your CPU does not support one of these virtualization technologies,
-then you cannot use virtual machine acceleration.</p>
-
-<p class="note"><strong>Note:</strong> Virtualization extensions are typically enabled through
-your computer's BIOS and are frequently turned off by default. Check the documentation for your
-system's motherboard to find out how to enable virtualization extensions.</p>
-
-<p>Once you have determined that your CPU supports virtualization extensions, make sure you can work
-within these additional requirements of running an emulator inside an accelerated virtual
-machine:</p>
-
-<ul>
- <li><strong>x86 AVD Only</strong> - You must use an AVD that is uses an x86 system image target.
-AVDs that use ARM-based system images cannot be accelerated using the emulator configurations
-described here.</li>
- <li><strong>Not Inside a VM</strong> - You cannot run a VM-accelerated emulator inside another
-virtual machine, such as a VirtualBox or VMWare-hosted virtual machine. You must run the emulator
-directly on your system hardware.</li>
- <li><strong>Other VM Drivers</strong> - If you are running another virtualization technology on
-your system such as VirtualBox or VMWare, you may need to unload the driver for that virtual machine
-hosting software before running an accelerated emulator.</li>
- <li><strong>OpenGL® Graphics</strong> - Emulation of OpenGL ES graphics may not perform at the
-same level as an actual device.</li>
-</ul>
-
-<p>To use virtual machine acceleration with the emulator, you need the following version of Android
-development tools. Use the <a href="{@docRoot}sdk/installing/index.html#AddingComponents">Android SDK
-Manager</a> to install these components:</p>
-
-<ul>
- <li>Android SDK Tools, Revision 17 or higher</li>
- <li>Android x86-based system image</li>
-</ul>
-
-<p>If your development environment meets all of the requirements for running a VM-accelerated
-emulator, you can use the AVD Manager to create an x86-based AVD configuration:</p>
-
-<ol>
- <li>In the Android SDK Manager, make sure you have an x86-based <strong>System Image</strong>
- installed for your target Android version. If you do not have an x86 <strong>System
- Image</strong> installed, select one in the Android SDK Manager and install it.
- <p class="note"><strong>Tip:</strong> System images are listed under each API Level in the SDK
- Manager. An x86 system image may not be available for all API levels.</p>
- </li>
- <li>Start the AVD Manager and create a new AVD with an x86 value for the
-<strong>CPU/ABI</strong> field. You may need to select a specific <strong>Target</strong> value, or
-select a <strong>Target</strong> value and then select a specific <strong>CPU/ABI</strong>
-option.</li>
- <li>Name the emulator instance and select any other configuration options.</li>
- <li>Click <strong>Create AVD</strong> to save the emulator configuration.</li>
-</ol>
-
-<h4 id="vm-windows">Configuring VM Acceleration on Windows</h4>
-
-<p>Virtual machine acceleration for Windows requires the installation of the Intel Hardware
-Accelerated Execution Manager (Intel HAXM). The software requires an Intel CPU with
-Virtualization Technology (VT) support and one of the following operating systems:</p>
-
-<ul>
- <li>Windows 7 (32/64-bit)</li>
- <li>Windows Vista (32/64-bit)</li>
- <li>Windows XP (32-bit only)</li>
-</ul>
-
-<p>To install the virtualization driver:</p>
-
-<ol>
- <li>Start the Android SDK Manager, select <strong>Extras</strong> and then select <strong>Intel
-Hardware Accelerated Execution Manager</strong>.</li>
- <li>After the download completes, execute {@code
-<sdk>/extras/intel/Hardware_Accelerated_Execution_Manager/IntelHAXM.exe}.</li>
- <li>Follow the on-screen instructions to complete installation.</li>
- <li>After installation completes, confirm that the virtualization driver is operating correctly by
-opening a command prompt window and running the following command:
- <pre>sc query intelhaxm</pre>
- <p>You should see a status message including the following information:</p>
-<pre>
-SERVICE_NAME: intelhaxm
- ...
- STATE : 4 RUNNING
- ...
-</pre>
- </li>
-</ol>
-
-<p>To run an x86-based emulator with VM acceleration:</p>
-<ul>
- <li>If you are running the emulator from the command line, just specify an x86-based AVD:
-<pre>emulator -avd <avd_name></pre>
- <p class="note"><strong>Note:</strong> You must provide an x86-based AVD configuration
-name, otherwise VM acceleration will not be enabled.</p>
- </li>
- <li>If you are running the emulator from Android Studio, run your Android application with an x86-based
-AVD:
- <ol>
- <li>In Android Studio, click your Android project folder and then select <strong>Run > Edit
-Configurations...</strong></li>
- <li>In the left panel of the <strong>Run/Debug Configurations</strong> dialog, select your Android
-run configuration or create a new configuration.</li>
- <li>Under the <strong>Target Device</strong> options, select the x86-based AVD you created
-previously.</li>
- <li>Run your Android project using this run configuration.</li>
- </ol>
- </li>
-</ul>
-
-<p>You can adjust the amount of memory available to the Intel HAXM kernel extension by re-running
-its installer.</p>
-
-<p>You can stop using the virtualization driver by uninstalling it. Re-run the installer or use
-the Control Panel to remove the software.</p>
-
-
-<h4 id="vm-mac">Configuring VM Acceleration on Mac</h4>
-
-<p>Virtual machine acceleration on a Mac requires the installation of the Intel Hardware Accelerated
-Execution Manager (Intel HAXM) kernel extension to allow the Android emulator to make use of CPU
-virtualization extensions. The kernel extension is compatible with Mac OS X Snow Leopard (version
-10.6.0) and higher.</p>
-
-<p>To install the Intel HAXM kernel extension:</p>
-
-<ol>
- <li>Start the Android SDK Manager, select <strong>Extras</strong> and then select <strong>Intel
-Hardware Accelerated Execution Manager</strong>.
- <li>After the download completes, execute
- {@code <sdk>/extras/intel/Hardware_Accelerated_Execution_Manager/IntelHAXM.dmg}.</li>
- <li>Double click the <strong>IntelHAXM.mpkg</strong> icon to begin installation.</li>
- <li>Follow the on-screen instructions to complete installation.</li>
- <li>After installation completes, confirm that the new kernel extension is operating correctly by
-opening a terminal window and running the following command:
- <pre>kextstat | grep intel</pre>
- <p>You should see a status message containing the following extension name, indicating that the
- kernel extension is loaded:</p>
- <pre>com.intel.kext.intelhaxm</pre>
- </li>
-</ol>
-
-<p>To run an x86-based emulator with VM acceleration:</p>
-<ul>
- <li>If you are running the emulator from the command line, just specify an x86-based AVD:
-<pre>emulator -avd <avd_name></pre>
- <p class="note"><strong>Note:</strong> You must provide an x86-based AVD configuration
-name, otherwise VM acceleration will not be enabled.</p>
- </li>
- <li>If you are running the emulator from Andriod Studio, run your Android application with an x86-based
-AVD:
- <ol>
- <li>In Android Studio, click your Android module folder and then select <strong>Run > Edit
-Configurations...</strong></li>
- <li>In the left panel of the <strong>Run/Debug Configurations</strong> dialog, select your Android
-run configuration or create a new configuration.</li>
- <li>Under the <strong>Target Device</strong> options,
- select the x86-based AVD you created previously.</li>
- <li>Run your Android project using this run configuration.</li>
- </ol>
- </li>
-</ul>
-
-<p>You can adjust the amount of memory available to the Intel HAXM kernel extension by re-running
-the installer.</p>
-
-<p>You can stop using the virtualization kernel driver by uninstalling it. Before removing it, shut
-down any running x86 emulators. To unload the virtualization kernel driver, run the following
-command in a terminal window:</p>
-
-<pre>sudo /System/Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh</pre>
-
-<h4 id="vm-linux">Configuring VM Acceleration on Linux</h4>
-
-<p>Linux-based systems support virtual machine acceleration through the KVM software package. Follow
-<a href="https://www.google.com/?q=kvm+installation">instructions for installing KVM</a> on your
-Linux system, and verify that KVM is enabled. In addition to following the installation
-instructions, be aware of these configuration requirements:</p>
-
-<ul>
- <li>Running KVM requires specific user permissions, make sure you have sufficient permissions
-according to the KVM installation instructions.</li>
- <li>If you use another virtualization technology in your Linux platform, unload its kernel driver
-before running the x86 emulator. For example, the VirtualBox driver program is {@code vboxdrv}.</li>
-</ul>
-
-<p>To run an x86-based emulator with VM acceleration:</p>
-
-<ul>
- <li>If you are running the emulator from the command line, start the emulator with an x86-based
-AVD and include the KVM options:
-<pre>emulator -avd <avd_name> -qemu -m 512 -enable-kvm</pre>
- <p class="note"><strong>Note:</strong> You must provide an x86-based AVD configuration
-name, otherwise VM acceleration will not be enabled.</p>
- </li>
- <li>If you are running the emulator from Android Studio, run your Android application with an
- x86-based AVD and include the KVM options:
- <ol>
- <li>In Android Studio, click your Android module folder and then select <strong>Run > Edit
-Configurations...</strong></li>
- <li>In the left panel of the <strong>Run/Debug Configurations</strong> dialog, select your Android
-run configuration or create a new configuration.</li>
- <li>Under the <strong>Target Device</strong> options, select the x86-based AVD you created
-previously.</li>
- <li>In the <strong>Emulator</strong> tab, in the
- <strong>Additional command line options</strong> field, enter:
- <pre>-qemu -m 512 -enable-kvm</pre>
- </li>
- <li>Run your Android project using this run configuration.</li>
- </ol>
- </li>
-</ul>
-
-<p class="note"><strong>Important:</strong> When using the {@code -qemu} command line option, make sure
-it is the last parameter in your command. All subsequent options are interpreted as qemu-specific
-parameters.</p>
-
-
-<h2 id="sdcard">Using SD Card Emulation</h2>
-
-<p>You can create a disk image and then load it to the emulator at startup, to
-simulate the presence of a user's SD card in the device. To do this, you can specify
-an SD card image when you create an AVD, or you can use the mksdcard utility included
-in the SDK.</p>
-
-<p>The following sections describe how to create an SD card disk image, how to copy
-files to it, and how to load it in the emulator at startup. </p>
-
-<p>Note that you can only load a disk image at emulator startup. Similarly, you
-can not remove a simulated SD card from a running emulator. However, you can
-browse, send files to, and copy/remove files from a simulated SD card either
-with adb or the emulator. </p>
-
-<p>The emulator supports emulated SDHC cards, so you can create an SD card image
-of any size up to 128 gigabytes.</p>
-
-
-<h3 id="sdcard-creating">Creating an SD card image</h3>
-
-<p>There are several ways of creating an SD card image. The easiest way is to use the
-<strong>AVD Manager</strong> to create a new SD card by specifying a size when you create an AVD.
-You can also use the {@code android} command line tool when creating an AVD. Just add the
-<code>-c</code> option to your command: </p>
-
-<pre>android create avd -n <avd_name> -t <targetID> -c <size>[K|M]</pre>
-
-<p>The <code>-c</code> option can also be used to to specify a path to an SD card
-image for the new AVD. For more information, see <a
-href="{@docRoot}tools/devices/managing-avds-cmdline.html">Managing Virtual Devices
-from the Command Line</a>.
-</p>
-
-<p>You can also use the mksdcard tool, included in the SDK, to create a FAT32 disk
-image that you can load in the emulator at startup. You can access mksdcard in
-the tools/ directory of the SDK and create a disk image like this: </p>
-
-<pre>mksdcard <size> <file></pre>
-
-<p>For example:</p>
-
-<pre>mksdcard 1024M sdcard1.iso</pre>
-
-<p>For more information, see <a
-href="{@docRoot}tools/help/mksdcard.html"><code>mksdcard</code></a>.</p>
-
-
-<h3 id="sdcard-files">Copying files to an SD card image</h3>
-
-<p>Once you have created the disk image, you can copy files to it prior to
-loading it in the emulator. To copy files, you can mount the image as a loop
-device and then copy the files to it, or you can use a utility such as {@code mtools} to
-copy the files directly to the image. The {@code mtools} package is available for Linux,
-Mac, and Windows.</p>
-
-<p>Alternatively, you can use the {@code adb push} command to move files onto an SD card image
-while it is loaded in an emulator. For more information see the <a
-href="{@docRoot}tools/help/adb.html#copyfiles">{@code adb push}</a> documentation.</p>
-
-<h3 id="sdcard-loading">Loading an SD card image</h3>
-
-<p>By default, the emulator loads the SD card image that is stored with the active
-AVD (see the <code>-avd</code> startup option).</p>
-
-<p>Alternatively, you can start the emulator with the
-<code>-sdcard</code> flag and specify the name and path of your image (relative
-to the current working directory): </p>
-
-<pre>emulator -sdcard <filepath></pre>
-
-
-<h2 id="diskimages">Working With Emulator Disk Images</h2>
-
-<p>The emulator uses mountable disk images stored on your development machine to
-simulate flash (or similar) partitions on an actual device. For example, it uses a
-disk image containing an emulator-specific kernel, the Android system, a
-ramdisk image, and writeable images for user data and simulated SD card.</p>
-
-<p>To run properly, the emulator requires access to a specific set of disk image
-files. By default, the Emulator always looks for the disk images in the
-private storage area of the AVD in use. If no images exist there when
-the Emulator is launched, it creates the images in the AVD directory based on
-default versions stored in the SDK. </p>
-
-<p class="note"><strong>Note:</strong> The default storage location for
-AVDs is in <code>~/.android/avd</code> on OS X and Linux, <code>C:\Documents and
-Settings\<user>\.android\</code> on Windows XP, and
-<code>C:\Users\<user>\.android\</code>
-on Windows Vista.</p>
-
-<p>To let you use alternate or custom versions of the image files, the emulator
-provides startup options that override the default locations and filenames of
-the image files. When you use one of these options, the emulator searches for the image
-file under the image name or location that you specify; if it can not locate the
-image, it reverts to using the default names and location.</p>
-
-<p>The emulator uses three types of image files: default image files, runtime
-image files, and temporary image files. The sections below describe how to
-override the location/name of each type of file. </p>
-
-<h3 id="defaultimages">Default image files</h3>
-
-<p>When the emulator launches, but does not find an existing user data image in
-the active AVD's storage area, it creates a new one from a default version
-included in the SDK. The default user data image is read-only. The image
-files are read-only.</p>
-
-<p>The emulator provides the <code>-system <dir></code> startup option to
-let you override the location where the emulator looks for the default
-user data image. </p>
-
-<p>The emulator also provides a startup option that lets you override the name
-of the default user data image, as described in the following table. When you use the
-option, the emulator looks in the default directory, or in a custom location
-(if you specified <code>-system <dir></code>). </p>
-
-
-<table>
-<tr>
- <th width="10%" >Name</th>
- <th width="30%" >Description</th>
- <th width="40%" >Comments</th>
-</tr>
-
-<!--
-<tr>
- <td><code>kernel-qemu.img</code></td>
- <td>The emulator-specific Linux kernel image</td>
- <td>Override using <code>-kernel <file></code></td>
-</tr>
-
-<tr>
- <td><code>ramdisk.img</code></td>
- <td>The ramdisk image used to boot the system.</td>
- <td>Override using <code>-ramdisk <file></code></td>
-</tr>
-
-<tr>
- <td><code>system.img</code></td>
- <td>The <em>initial</em> Android system image.</td>
- <td>Override using <code>-image <file></code></td>
-</tr>
--->
-<tr>
- <td><code>userdata.img</code></td>
- <td>The <em>initial</em> user-data disk image</td>
- <td>Override using <code>-initdata <file></code>. Also see
-<code>-data <file></code>, below.</td>
-</tr>
-
-</table>
-
-<h3 id="runtimeimages">Runtime images: user data and SD card</h3>
-
-<p>At runtime, the emulator reads and writes data to two disk images: a
-user-data image and (optionally) an SD card image. These images emulate the user-data
-partition and removable storage media on actual device. </p>
-
-<p>The emulator provides a default user-data disk image. At startup, the emulator
-creates the default image as a copy of the system user-data image (user-data.img),
-described above. The emulator stores the new image with the files of the active AVD.</p>
-
-<!--
-<p>The emulator provides a startup option, <code>-datadir <dir></code>,
-that you can use to override the location under which the emulator looks for the runtime
-image files. </p>
--->
-
-<p>The emulator provides startup options to let you override the actual names and storage
-locations of the runtime images to load, as described in the following table. When you use one
-of these options, the emulator looks for the specified file(s) in the current working directory,
-in the AVD directory, or in a custom location (if you specified a path with the filename). </p>
-
-<table>
-<tr>
- <th width="10%" >Name</th>
- <th width="30%" >Description</th>
- <th width="40%" >Comments</th>
-</tr>
-<tr>
- <td><code>userdata-qemu.img</code></td>
- <td>An image to which the emulator writes runtime user-data for a unique user.</td>
- <td>Override using <code>-data <filepath></code>, where <code><filepath></code> is the
-path the image, relative to the current working directory. If you supply a filename only,
-the emulator looks for the file in the current working directory. If the file at <code><filepath></code> does
-not exist, the emulator creates an image from the default <code>userdata.img</code>, stores it under the name you
-specified, and persists user data to it at shutdown. </td>
-</tr>
-
-<tr>
- <td><code>sdcard.img</code></td>
- <td>An image representing an SD card inserted into the emulated device.</td>
- <td>Override using <code>-sdcard <filepath></code>, where <code><filepath></code> is the
-path the image, relative to the current working directory. If you supply a filename only,
-the emulator looks for the file in the current working directory. </td>
-</tr>
-
-</table>
-
-<h4>User-Data Image</h4>
-
-<p>Each emulator instance uses a writeable user-data image to store user- and
-session-specific data. For example, it uses the image to store a unique user's
-installed application data, settings, databases, and files. </p>
-
-<p>At startup, the emulator attempts to load a user-data image stored during
-a previous session. It looks for the file in the current working directory,
-in the AVD directory described in a previous section and at the custom location/name
-that you specified at startup. </p>
-
-<ul>
-<li>If it finds a user-data image, it mounts the image and makes it available
-to the system for reading and writing of user data. </li>
-<li>If it does not find one, it creates an image by copying the system user-data
-image (userdata.img), described above. At device power-off, the system persists
-the user data to the image, so that it will be available in the next session.
-Note that the emulator stores the new disk image at the location/name that you
-specify in <code>-data</code> startup option.</li>
-</ul>
-
-<p class="note"><strong>Note:</strong> Because of the AVD configurations used in the emulator,
-each emulator instance gets its own dedicated storage. There is no longer a need
-to use the <code>-d</code> option to specify an instance-specific storage area.</p>
-
-<h4>SD Card</h4>
-
-<P>Optionally, you can create a writeable disk image that the emulator can use
-to simulate removeable storage in an actual device. For information about how to create an
-emulated SD card and load it in the emulator, see <a href="#sdcard">SD Card Emulation</a></p>
-
-<p>You can also use the android tool to automatically create an SD Card image
-for you, when creating an AVD. For more information, see <a
-href="{@docRoot}tools/devices/managing-avds.html">Managing Virtual Devices with AVD
-Manager</a>.
-
-
-<h3 id="temporaryimages">Temporary Images</h3>
-
-<p>The emulator creates two writeable images at startup that it deletes at
-device power-off. The images are: </p>
-
-<ul>
- <li>A writable copy of the Android system image</li>
- <li>The <code>/cache</code> partition image</li>
-</ul>
-
-<p>The emulator does not permit renaming the temporary system image or
-persisting it at device power-off. </p>
-
-<p>The <code>/cache</code> partition image is initially empty, and is used by
-the browser to cache downloaded web pages and images. The emulator provides an
-<code>-cache <file></code>, which specifies the name of the file in which
-to persist the <code>/cache</code> image at device power-off. If <code><file>
-</code> does not exist, the emulator creates it as an empty file. </p>
-
-<p>You can also disable the use of the cache partition by specifying the
-<code>-nocache</code> option at startup. </p>
-
-
-<h2 id="emulatornetworking">Setting Up Emulator Networking</h2>
-
-<p>The emulator provides versatile networking capabilities that you can use to
-set up complex modeling and testing environments for your application. The
-sections below introduce the emulator's network architecture and capabilities.
-</p>
-
-<h3 id="networkaddresses">Network Address Space</h3>
-
-<p>Each instance of the emulator runs behind a virtual router/firewall service
-that isolates it from your development machine's network interfaces and settings
-and from the internet. An emulated device can not see your development machine
-or other emulator instances on the network. Instead, it sees only that it is
-connected through Ethernet to a router/firewall.</p>
-
-<p>The virtual router for each instance manages the 10.0.2/24 network address
-space — all addresses managed by the router are in the form of
-10.0.2.<xx>, where <xx> is a number. Addresses within this space are
-pre-allocated by the emulator/router as follows:</p>
-
-<table>
- <tr>
- <th>Network Address</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>10.0.2.1</td>
- <td>Router/gateway address </td>
- </tr>
- <tr>
- <td>10.0.2.2</td>
- <td>Special alias to your host loopback interface (i.e., 127.0.0.1 on your
-development machine)</td>
- </tr>
- <tr>
- <td>10.0.2.3</td>
- <td>First DNS server</td>
- </tr>
- <tr>
- <td>10.0.2.4 / 10.0.2.5 / 10.0.2.6</td>
- <td>Optional second, third and fourth DNS server (if any) </td>
- </tr>
- <tr>
- <td>10.0.2.15</td>
- <td>The emulated device's own network/ethernet interface</td>
- </tr>
- <tr>
- <td>127.0.0.1</td>
- <td>The emulated device's own loopback interface </td>
- </tr>
-</table>
-
-<p>Note that the same address assignments are used by all running emulator
-instances. That means that if you have two instances running concurrently on
-your machine, each will have its own router and, behind that, each will have an
-IP address of 10.0.2.15. The instances are isolated by a router and can
-<em>not</em> see each other on the same network. For information about how to
-let emulator instances communicate over TCP/UDP, see <a
-href="#connecting">Connecting Emulator Instances</a>.</p>
-
-<p>Also note that the address 127.0.0.1 on your development machine corresponds
-to the emulator's own loopback interface. If you want to access services running
-on your development machine's loopback interface (a.k.a. 127.0.0.1 on your
-machine), you should use the special address 10.0.2.2 instead.</p>
-
-<p>Finally, note that each emulated device's pre-allocated addresses are
-specific to the Android emulator and will probably be very different on real
-devices (which are also very likely to be NAT-ed, i.e., behind a
-router/firewall)</p>
-
-
-<h3 id="networkinglimitations">Local Networking Limitations</h3>
-
-<p>Android applications running in an emulator can connect to the network available on your
-workstation. However, they connect through the emulator, not directly to hardware, and the emulator
-acts like a normal application on your workstation. This means that the emulator, and thus your
-Android applications, are subject to some limitations:</p>
-
-<ul>
- <li>Communication with the emulated device may be blocked by a firewall
-program running on your machine.</li>
- <li>Communication with the emulated device may be blocked by another
-(physical) firewall/router to which your machine is connected.</li>
-</ul>
-
-<p>The emulator's virtual router should be able to handle all outbound TCP and
-UDP connections/messages on behalf of the emulated device, provided your
-development machine's network environment allows it to do so. There are no
-built-in limitations on port numbers or ranges except the one imposed by your
-host operating system and network.</p>
-
-<p>Depending on the environment, the emulator may not be able to support other
-protocols (such as ICMP, used for "ping") might not be supported. Currently, the
-emulator does not support IGMP or multicast. </p>
-
-<h3 id="redirection">Using Network Redirection</h3>
-
-<p>To communicate with an emulator instance behind its virtual router, you need
-to set up network redirection on the virtual router. Clients can then connect
-to a specified guest port on the router, while the router directs traffic
-to/from that port to the emulated device's host port. </p>
-
-<p>To set up the network redirection, you create a mapping of host and guest
-ports/addresses on the emulator instance. There are two ways to set up
-network redirection: using emulator console commands and using the ADB tool, as
-described below. </p>
-
-
-<h4 id="consoleredir">Setting up Redirection through the Emulator Console</h4>
-
-<p>Each emulator instance provides a control console the you can connect to, to
-issue commands that are specific to that instance. You can use the
-<code>redir</code> console command to set up redirection as needed for an
-emulator instance. </p>
-
-<p>First, determine the console port number for the target emulator instance.
-For example, the console port number for the first emulator instance launched is
-5554. Next, connect to the console of the target emulator instance, specifying
-its console port number, as follows: </p>
-
-<pre><code>telnet localhost 5554</code></pre>
-
-<p>Once connected, use the <code>redir</code> command to work with redirection.
-To add a redirection, use:</p>
-
-<pre><code>add <protocol>:<host-port>:<guest-port></code>
-</pre>
-
-<p>where <code><protocol></code> is either <code>tcp</code> or <code>udp</code>,
-and <code><host-port></code> and <code><guest-port></code> sets the
-mapping between your own machine and the emulated system, respectively. </p>
-
-<p>For example, the following command sets up a redirection that handles all
-incoming TCP connections to your host (development) machine on 127.0.0.1:5000
-and will pass them through to the emulated system's 10.0.2.15:6000.:</p>
-
-<pre>redir add tcp:5000:6000</pre>
-
-<p>To delete a redirection, you can use the <code>redir del</code> command. To
-list all redirection for a specific instance, you can use <code>redir
-list</code>. For more information about these and other console commands, see
-<a href="#console">Using the Emulator Console</a>. </p>
-
-<p>Note that port numbers are restricted by your local environment. this typically
-means that you cannot use host port numbers under 1024 without special
-administrator privileges. Also, you won't be able to set up a redirection for a
-host port that is already in use by another process on your machine. In that
-case, <code>redir</code> generates an error message to that effect. </p>
-
-<h4 id="adbredir">Setting Up Redirection through ADB</h4>
-
-<p>The Android Debug Bridge (ADB) tool provides port forwarding, an alternate
-way for you to set up network redirection. For more information, see <a
-href="{@docRoot}tools/help/adb.html#forwardports">Forwarding Ports</a> in the ADB
-documentation.</p>
-
-<p>Note that ADB does not currently offer any way to remove a redirection,
-except by killing the ADB server.</p>
-
-
-<h3 id="dns">Configuring the Emulator's DNS Settings</h3>
-
-<p>At startup, the emulator reads the list of DNS servers that your system is
-currently using. It then stores the IP addresses of up to four servers on this
-list and sets up aliases to them on the emulated addresses 10.0.2.3, 10.0.2.4,
-10.0.2.5 and 10.0.2.6 as needed. </p>
-
-<p>On Linux and OS X, the emulator obtains the DNS server addresses by parsing
-the file <code>/etc/resolv.conf</code>. On Windows, the emulator obtains the
-addresses by calling the <code>GetNetworkParams()</code> API. Note that this
-usually means that the emulator ignores the content of your "hosts" file
-(<code>/etc/hosts</code> on Linux/OS X, <code>%WINDOWS%/system32/HOSTS</code>
- on Windows).</P>
-
-<p>When starting the emulator at the command line, you can also use the
-<code>-dns-server <serverList></code> option to manually specify the
-addresses of DNS servers to use, where <serverList> is a comma-separated
-list of server names or IP addresses. You might find this option useful if you
-encounter DNS resolution problems in the emulated network (for example, an
-"Unknown Host error" message that appears when using the web browser).</p>
-
-
-<h3 id="proxy">Using the Emulator with a Proxy</h3>
-
-<p>If your emulator must access the Internet through a proxy server, you can use
-the <code>-http-proxy <proxy></code> option when starting the emulator, to
-set up the appropriate redirection. In this case, you specify proxy information
-in <code><proxy></code> in one of these formats:</p>
-
-<pre>http://<machineName>:<port></pre>
-
-<p>or</p>
-
-<pre>http://<username>:<password>@<machineName>:<port></pre>
-
-<p>The <code>-http-proxy</code> option forces the emulator to use the specified
-HTTP/HTTPS proxy for all outgoing TCP connections. Redirection for UDP is not
-currently supported.</p>
-
-<p>Alternatively, you can define the environment variable
-<code>http_proxy</code> to the value you want to use for
-<code><proxy></code>. In this case, you do not need to specify a value for
-<code><proxy></code> in the <code>-http-proxy</code> command — the
-emulator checks the value of the <code>http_proxy</code> environment variable at
-startup and uses its value automatically, if defined. </p>
-
-<p>You can use the <code>-verbose-proxy</code> option to diagnose proxy
-connection problems.</p>
-
-
-<h3 id="connecting">Interconnecting Emulator Instances</h3>
-
-<p>To allow one emulator instance to communicate with another, you must set up
-the necessary network redirection as illustrated below. </p>
-
-<p>Assume that your environment is</p>
-
-<ul>
- <li>A is you development machine</li>
- <li>B is your first emulator instance, running on A</li>
- <li>C is your second emulator instance, also running on A</li>
-</ul>
-
-<p>and you want to run a server on B, to which C will connect, here is how you
-could set it up: </p>
-
-<ol>
- <li>Set up the server on B, listening to
-<code>10.0.2.15:<serverPort></code></li>
- <li>On B's console, set up a redirection from
-<code>A:localhost:<localPort></code> to <code>
-B:10.0.2.15:<serverPort></code></li>
- <li>On C, have the client connect to <code>10.0.2.2:<localPort></code></li>
-</ol>
-
-<p>For example, if you wanted to run an HTTP server, you can select
-<code><serverPort></code> as 80 and <code><localPort></code> as
-8080:</p>
-
-<ul>
- <li>B listens on 10.0.2.15:80</li>
- <li>On B's console, issue <code>redir add tcp:8080:80</code></li>
- <li>C connects to 10.0.2.2:8080</li>
-</ul>
-
-<h3 id="calling">Sending a Voice Call or SMS to Another Emulator Instance</h3>
-
-<p>The emulator automatically forwards simulated voice calls and SMS messages from one instance to
-another. To send a voice call or SMS, use the dialer application or SMS application, respectively,
-from one of the emulators.</p>
-
-<p>To initiate a simulated voice call to another emulator instance:</p>
-<ol>
-<li>Launch the dialer application on the originating emulator instance.</li>
-<li>As the number to dial, enter the console port number of the instance you'd like to call. You can determine
- the console port number of the target instance by checking its window title, where the
- console port number is reported as "Android Emulator (<port>). </li>
-<li>Press "Dial". A new inbound call appears in the target emulator instance. </li>
-</ol>
-
-<p>To send an SMS message to another emulator instance, launch the SMS application (if available). Specify the console port number of the target emulator instance as as the SMS address, enter the message text, and send the message. The message is delivered to the target emulator instance. </p>
-
-<p>You can also connect to an emulator instance's console to simulate an incoming voice call or SMS. For more information, see <a href="#telephony">Telephony Emulation</a> and <a href="#sms">SMS Emulation</a>.
-
-
-<h2 id="console">Using the Emulator Console</h2>
-
-<p>Each running emulator instance provides a console that lets you query and control the emulated
-device environment. For example, you can use the console to manage port redirection, network
-characteristics, and telephony events while your application is running on the emulator. To
-access the console and enter commands, use telnet to connect to the console's port number.</p>
-
-<p>To connect to the console of any running emulator instance at any time, use this command: </p>
-
-<pre>telnet localhost <console-port></pre>
-
-<p>An emulator instance occupies a pair of adjacent ports: a console port and an {@code adb} port.
-The port numbers differ by 1, with the {@code adb} port having the higher port number. The console
-of the first emulator instance running on a given machine uses console port 5554 and {@code adb}
-port 5555. Subsequent instances use port numbers increasing by two — for example, 5556/5557,
-5558/5559, and so on. Up to 16 concurrent emulator instances can run a console facility. </p>
-
-<p>To connect to the emulator console, you must specify a valid console port. If multiple emulator instances are running, you need to determine the console port of the emulator instance you want to connect to. You can find the instance's console port listed in the title of the instance window. For example, here's the window title for an instance whose console port is 5554:</p>
-
-<p><code>Android Emulator (5554)</code></p>
-
-<p>Alternatively, you can use the <code>adb devices</code> command, which prints a list of running emulator instances and their console port numbers. For more information, see <a href="{@docRoot}tools/help/adb.html#devicestatus">Querying for Emulator/Device Instances</a> in the adb documentation.</p>
-
-<p class="note">Note: The emulator listens for connections on ports 5554-5587 and accepts connections only from localhost.</p>
-
-<p>Once you are connected to the console, you can then enter <code>help [command]</code> to see a list of console commands and learn about specific commands. </p>
-
-<p>To exit the console session, use <code>quit</code> or <code>exit</code>.</p>
-
-<p>The following sections below describe the major functional areas of the console.</p>
-
-
-<h3 id="portredirection">Port Redirection</h3>
-
-<p>You can use the console to add and remove port redirection while the emulator is running. After
-you connect to the console, manage port redirection by entering the following command:</p>
-
-<pre>redir <list|add|del> </pre>
-
-<p>The <code>redir</code> command supports the subcommands listed in the table below. </p>
-
-<table>
-<tr>
- <th width="25%" >Subcommand
- <th width="30%" >Description</th>
- <th width="35%">Comments</th>
-</tr>
-
- <tr>
- <td><code>list</code></td>
- <td>List the current port redirection.</td>
- <td> </td>
- </tr>
-
-
-<tr>
- <td><code>add <protocol>:<host-port>:<guest-port></code></td>
- <td>Add a new port redirection.</td>
-<td><ul><li><protocol> must be either "tcp" or "udp"</li>
-<li><host-port> is the port number to open on the host</li>
-<li><guest-port> is the port number to route data to on the emulator/device</li>
-</ul></td>
-</tr>
-<tr>
- <td><code>del <protocol>:<host-port></code></td>
- <td>Delete a port redirection.</td>
-<td>The meanings of <protocol> and <host-port> are listed in the previous row.</td>
-</tr>
-</table>
-
-
-<h3 id="geo">Geo Location Provider Emulation</h3>
-
-<p>You can use the console to set the geographic location reported to the applications running
-inside an emulator. Use the <code>geo</code> command to send a simple GPS fix to the
-emulator, with or without NMEA 1083 formatting:</p>
-
-<pre>geo <fix|nmea></pre>
-
-<p>The <code>geo</code> command supports the subcommands listed in the table below.</p>
-
-<table>
-<tr>
- <th width="25%">Subcommand</th>
- <th width="30%">Description</th>
- <th width="35%">Comments</th>
-</tr>
-
- <tr>
- <td><code>fix <longitude> <latitude> [<altitude>]</code></td>
- <td>Send a simple GPS fix to the emulator instance.</td>
- <td>Specify longitude and latitude in decimal degrees. Specify altitude in meters.</td>
- </tr>
-<tr>
- <td><code>nmea <sentence></code></td>
- <td>Send an NMEA 0183 sentence to the emulated device, as if it were sent from an emulated GPS modem.</td>
-<td><code><sentence></code> must begin with '$GP'. Only '$GPGGA' and '$GPRCM' sentences are currently supported.</td>
-</tr>
-</table>
-
-<p>You can issue the <code>geo</code> command as soon as an emulator instance is running. The
-emulator sets the location you enter by creating a mock location provider. This provider responds to
-location listeners set by applications, and also supplies the location to the {@link
-android.location.LocationManager}. Any application can query the location manager to obtain the
-current GPS fix for the emulated device by calling:
-
-<pre>LocationManager.getLastKnownLocation("gps")</pre>
-
-<p>For more information about the Location Manager, see {@link android.location.LocationManager}.
-</p>
-
-<h3 id="events">Hardware Events Emulation</h3>
-
-<p>The {@code event} console commands sends hardware events to the emulator. The syntax for this
-command is as follows:</p>
-
-<pre>event <send|types|codes|text></pre>
-
-<p>The <code>event</code> command supports the subcommands listed in the table below. </p>
-
-<table>
-<tr>
- <th width="25%" >Subcommand
- <th width="30%" >Description</th>
- <th width="35%">Comments</th>
-</tr>
-
- <tr>
- <td><code>send <type>:<code>:<value> [...]</code></td>
- <td>Send one or more events to the Android kernel. </td>
- <td>You can use text names or integers for <code><type></code> and <code><value></code>.</td>
- </tr>
-<tr>
- <td><code>types</code></td>
- <td>List all <code><type></code> string aliases supported by the <code>event</code> subcommands.</td>
-<td> </td>
-</tr>
-<tr>
- <td><code>codes <type></code></td>
- <td>List all <code><codes></code> string aliases supported by the <code>event</code>
- subcommands for the specified <code><type></code>.</td>
-<td> </td>
-</tr>
-<tr>
- <td><code>event text <message></code></td>
- <td>Simulate keypresses to send the specified string of characters as a message,</td>
-<td>The message must be a UTF-8 string. Unicode posts will be reverse-mapped according to the current device keyboard. Unsupported characters will be discarded silently.</td>
-</tr>
-</table>
-
-
-<h3 id="power">Device Power Characteristics</h3>
-
-<p>The {@code power} command controls the power state reported by the emulator to applications. The
-syntax for this command is as follows: </p>
-
-<pre>power <display|ac|status|present|health|capacity></pre>
-
-<p>The <code>event</code> command supports the subcommands listed in the table below. </p>
-
-<table>
-<tr>
- <th width="25%" >Subcommand </th>
- <th width="30%" >Description</th>
- <th width="35%">Comments</th>
-</tr>
-
- <tr>
- <td><code>display</code></td>
- <td>Display battery and charger state.</td>
- <td> </td>
- </tr>
-<tr>
- <td><code>ac <on|off></code></td>
- <td>Set AC charging state to on or off. </td>
-<td> </td>
-</tr>
-<tr>
- <td><code>status <unknown|charging|discharging|not-charging|full></code></td>
- <td>Change battery status as specified.</td>
-<td> </td>
-</tr>
-
-<tr>
- <td><code>present <true|false></code></td>
- <td>Set battery presence state.</td>
-<td> </td>
-</tr>
-<tr>
- <td><code>health <unknown|good|overheat|dead|overvoltage|failure></code></td>
- <td>Set battery health state.</td>
-<td> </td>
-</tr>
-<tr>
- <td><code>capacity <percent></code></td>
- <td>Set remaining battery capacity state (0-100).</td>
-<td> </td>
-</tr>
-</table>
-
-
-<h3 id="netstatus">Network Status</h3>
-
-<p>You can use the console to check the network status and current delay and speed characteristics. To do so, connect to the console and use the <code>netstatus</code> command. Here's an example of the command and its output. </p>
-
-<pre>network status
-</pre>
-
-
-<h3 id="netdelay">Network Delay Emulation</h3>
-
-<p>The emulator lets you simulate various network latency levels, so that you can test your
-application in an environment more typical of the actual conditions in which it will run. You can
-set a latency level or range at emulator startup or you can use the console to change the latency,
-while the application is running in the emulator. </p>
-
-<p>To set latency at emulator startup, use the <code>-netdelay</code> emulator option with a
-supported <code><delay></code> value, as listed in the table below. Here are some
-examples:</p>
-
-<pre>emulator -netdelay gprs
-emulator -netdelay 40 100</pre>
-
-<p>To make changes to network delay while the emulator is running, connect to the console and use
-the <code>netdelay</code> command with a supported <code><delay></code> value from the table
-below.</p>
-
-<pre>network delay gprs</pre>
-
-<p>The format of network <delay> is one of the following (numbers are milliseconds):</p>
-
-<table style="clear:right;width:100%;">
-<tr>
- <th width="30%" >Value</th>
- <th width="35%" >Description</th><th width="35%">Comments</th></tr>
-
- <tr><td><code>gprs</code></td><td>GPRS</td>
- <td>(min 150, max 550)</td>
- </tr>
-
-<tr><td><code>edge</code></td><td>EDGE/EGPRS</td>
-<td>(min 80, max 400)</td>
-</tr>
-<tr><td><code>umts</code></td><td>UMTS/3G</td>
-<td>(min 35, max 200)</td>
-</tr>
-<tr><td><code>none</code></td><td>No latency</td><td>(min 0, max 0)</td></tr>
-<tr><td><code><num></code></td>
-<td>Emulate an exact latency (milliseconds).</td>
-<td> </td></tr>
-<tr><td><code><min>:<max></code></td>
-<td>Emulate an specified latency range (min, max milliseconds).</td>
-<td> </td></tr>
-</table>
-
-
-<h3 id="netspeed">Network Speed Emulation</h3>
-
-<p>The emulator also lets you simulate various network transfer rates.
-You can set a transfer rate or range at emulator startup or you can use the console to change the
-rate, while the application is running in the emulator.</p>
-
-<p>To set the network speed at emulator startup, use the <code>-netspeed</code> emulator option with a supported
-<code><speed></code> value, as listed in the table below. Here are some examples:</p>
-
-<pre>emulator -netspeed gsm
-emulator -netspeed 14.4 80</pre>
-
-<p>To make changes to network speed while the emulator is running, connect to the console and use
-the <code>netspeed</code> command with a supported <code><speed></code> value from the table
-below.</p>
-
-<pre>network speed 14.4 80</pre>
-
-<p>The format of network <code><speed></code> is one of the following (numbers are
-kilobits/sec):</p>
-<table style="clear:right;width:100%;">
-<tbody>
-<tr>
- <th width="30%">Value</th>
- <th width="35%">Description</th><th width="35%">Comments</th></tr>
-
- <tr>
- <td><code>gsm</code></td>
- <td>GSM/CSD</td><td>(Up: 14.4, down: 14.4)</td></tr>
-<tr>
- <td><code>hscsd</code></td>
- <td>HSCSD</td><td>(Up: 14.4, down: 43.2)</td></tr>
-<tr>
- <td><code>gprs</code></td>
- <td>GPRS</td><td>(Up: 40.0, down: 80.0)</td></tr>
-<tr>
- <td><code>edge</code></td>
- <td>EDGE/EGPRS</td>
- <td>(Up: 118.4, down: 236.8)</td>
-</tr>
-<tr>
- <td><code>umts</code></td>
- <td>UMTS/3G</td><td>(Up: 128.0, down: 1920.0)</td></tr>
-<tr>
- <td><code>hsdpa</code></td>
- <td>HSDPA</td><td>(Up: 348.0, down: 14400.0)</td></tr>
-<tr>
- <td><code>full</code></td>
- <td>no limit</td><td>(Up: 0.0, down: 0.0)</td></tr>
-<tr>
- <td><code><num></code></td>
- <td>Set an exact rate used for both upload and download.</td><td></td></tr>
-<tr>
- <td><code><up>:<down></code></td>
- <td>Set exact rates for upload and download separately.</td><td></td></tr>
-</table>
-
-
-<h3 id="telephony">Telephony Emulation</h3>
-
-<p>The Android emulator includes its own GSM emulated modem that lets you simulate telephony
-functions in the emulator. For example, you can simulate inbound phone calls, establish data
-connections and terminate them. The Android system handles simulated calls exactly as it would
-actual calls. The emulator does not support call audio.</p>
-
-<p>You can use the {@code gsm} command to access the emulator's telephony functions after connecting
-to the console. The syntax for this command is as follows:</p>
-
-<pre>gsm <call|accept|busy|cancel|data|hold|list|voice|status> </pre>
-
-<p>The <code>gsm</code> command supports the subcommands listed in the table below. </p>
-<table>
- <tr>
- <th>Subcommand </th>
- <th width="25%">Description</th>
- <th>Comments</th>
- </tr>
- <tr>
- <td><code>call <phonenumber></code></td>
- <td>Simulate an inbound phone call from <phonenumber>.</td>
- <td> </td>
- </tr>
- <tr>
- <td><code>accept <phonenumber></code></td>
- <td>Accept an inbound call from <phonenumber> and change the call's state "active".</td>
- <td>You can change a call's state to "active" only if its current state is "waiting" or "held".</td>
- </tr>
- <tr>
- <td><code>busy <phonenumber></code></td>
- <td>Close an outbound call to <phonenumber> and change the call's state to "busy".</td>
- <td>You can change a call's state to "busy" only if its current state is "waiting".</td>
- </tr>
- <tr>
- <td><code>cancel <phonenumber></code></td>
- <td>Terminate an inbound or outbound phone call to/from <phonenumber>.</td>
- <td> </td>
- </tr>
- <tr>
- <td><code>data <state></code></td>
- <td>Change the state of the GPRS data connection to <state>.</td>
- <td>Supported <state> values are:<br />
- <ul>
- <li><code>unregistered</code> -- No network available</li>
- <li><code>home</code> -- On local network, non-roaming</li>
- <li><code>roaming</code> -- On roaming network</li>
- <li><code>searching</code> -- Searching networks</li>
- <li><code>denied</code> -- Emergency calls only</li>
- <li><code>off</code> -- Same as 'unregistered'</li>
- <li><code>on</code> -- same as 'home'</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><code>hold</code></td>
- <td>Change the state of a call to "held". </td>
- <td>You can change a call's state to "held" only if its current state is "active" or "waiting". </td>
- </tr>
- <tr>
- <td><code>list</code></td>
- <td>List all inbound and outbound calls and their states.</td>
- <td> </td>
- </tr>
- <tr>
- <td><code>voice <state></code></td>
- <td>Change the state of the GPRS voice connection to <state>.</td>
- <td>Supported <state> values are:<br />
- <ul>
- <li><code>unregistered</code> -- No network available</li>
- <li><code>home</code> -- On local network, non-roaming</li>
- <li><code>roaming</code> -- On roaming network</li>
- <li><code>searching</code> -- Searching networks</li>
- <li><code>denied</code> -- Emergency calls only</li>
- <li><code>off</code> -- Same as 'unregistered'</li>
- <li><code>on</code> -- Same as 'home'</li>
- </ul>
- </td>
- </tr>
-
- <tr>
- <td><code>status</code></td>
- <td>Report the current GSM voice/data state.</td>
- <td>Values are those described for the <code>voice</code> and <code>data</code> commands.</td>
- </tr>
-</table>
-
-
-<h3 id="sms">SMS Emulation</h3>
-
-<p>The Android emulator console lets you generate an SMS message and direct it to an emulator
-instance. Once you connect to an emulator instance, you can generate an emulated incoming SMS using
-the following command:</p>
-
-<pre>sms send <senderPhoneNumber> <textmessage></pre>
-
-<p>where <code><senderPhoneNumber></code> contains an arbitrary numeric string. </p>
-
-<p>The console forwards the SMS message to the Android framework, which passes it through to an application that handles that message type. </p>
-
-
-<h3 id="vm">VM State</h3>
-
-<p>You can use the <code>vm</code> command to control the VM on an emulator instance. The syntax for
-this command is as follows: </p>
-
-<pre>vm <start|stop|status></pre>
-
-<p>The <code>vm</code> command supports the subcommands listed in the table below. </p>
-
-<table>
-<tr>
- <th width="25%">Subcommand</th>
- <th width="30%">Description</th>
- <th width="35%">Comments</th>
-</tr>
-<tr>
- <td><code>start</code></td>
- <td>Start the VM on the instance. </td>
- <td> </td>
-</tr>
-<tr>
- <td><code>stop</code></td>
- <td>Stop the VM on the instance. </td>
- <td> </td>
-</tr>
-<tr>
- <td><code>start</code></td>
- <td>Display the current status of the VM (running or stopped). </td>
- <td> </td>
-</tr>
-</table>
-
-
-<h3 id="window">Emulator Window</h3>
-
-<p>You can use the <code>window</code> command to manage the emulator window. The syntax for this
-command is as follows: </p>
-
-<pre>window <scale></pre>
-
-<p>The <code>vm</code> command supports the subcommands listed in the table below. </p>
-
-<table>
-<tr>
- <th width="25%">Subcommand</th>
- <th width="30%">Description</th>
- <th width="35%">Comments</th>
-</tr>
-<tr>
- <td><code>scale <scale></code></td>
- <td>Scale the emulator window.</td>
- <td>A number between 0.1 and 3 that sets the 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>
-</table>
-
-
-<h3 id="terminating">Terminating an Emulator Instance</h3>
-
-<p>You can terminate an emulator instance through the console, using the <code>kill</code> command.</p>
-
-
-
-
-<h2 id="troubleshooting">Troubleshooting Emulator Problems</h2>
-
-<p>The {@code adb} utility sees the emulator as an actual physical device. For this reason, you
-might have to use the {@code -d} flag with some common {@code adb} commands, such as
-<code>install</code>. The {@code -d} flag lets you specify which of several connected devices to use
-as the target of a command. If you don't specify {@code -d}, the emulator targets the first
-device in its list. For more information about {@code adb}, see <a
-href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>.</p>
-
-<p>For emulators running on Mac OS X, if you see an error {@code Warning: No DNS servers found}
-when starting the emulator, check to see whether you have an <code>/etc/resolv.conf</code> file. If
-not, please run the following line in a command window:</p>
- <pre>ln -s /private/var/run/resolv.conf /etc/resolv.conf</pre>
-
-<p>See <a href="{@docRoot}resources/faq/index.html">Frequently Asked Questions</a> for more
-troubleshooting information. </p>
+++ /dev/null
-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
+++ /dev/null
-page.title=Tracer for OpenGL ES
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#running">Running Tracer</a></li>
- <li><a href="#generating">Generating a Trace</a></li>
- <li><a href="#analyzing">Analyzing a Trace</a></li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/index.html">Tools</a></li>
- </ol>
-</div>
-</div>
-
-<p>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.</p>
-
-<p class="note"><strong>Note:</strong> The Tracer tool requires a device running Android 4.1 (API
-Level 16) or higher.</p>
-
-
-<h2 id="running">Running Tracer</h2>
-
-
-<p>To run Tracer in Device Monitor:</p>
-
-<ol>
- <li>Start the <a href="monitor.html">Device Monitor</a> tool.</li>
- <li>Activate the perspective for Tracer by choosing <strong>Window > Open
-Perspective...</strong></li>
- <li>Select <strong>Tracer for OpenGL ES</strong> and click <strong>OK</strong>.</li>
-</ol>
-
-<h2 id="generating">Generating a Trace</h2>
-
-<p>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.</p>
-
-<img src="{@docRoot}images/gltracer/dialog-trace.png">
-<p class="img-caption"><strong>Figure 1.</strong> Trace capture dialog box.</p>
-
-<p>To capture an OpenGL ES trace for an Android application:</p>
-
-<ol>
- <li>Connect the Android device using a USB cable and make sure it is enabled for debugging. For
-more information, see <a href="{@docRoot}tools/device.html">Using Hardware Devices</a>.</li>
- <li>In the Device Monitor, activate the <strong>Tracer for OpenGL ES</strong>
-perspective.</li>
- <li>On the toolbar, click the trace capture button (<img
-src="{@docRoot}images/gltracer/icon-capture.png">).</li>
- <li>In the dialog box, select the <strong>Device</strong> to use for the trace.</li>
- <li>In the <strong>Application Package</strong> field, enter the full application package name
-containing the activity you want to trace, for example: {@code com.example.android.opengl}</li>
- <li>In the <strong>Activity to launch</strong> field, enter the class name of the activity you
-want to trace, for example: {@code OpenGLES20Complete}
- <p class="note"><strong>Note:</strong> If you are tracing the default activity for the
-application, you can leave this field blank.</p>
- </li>
- <li>Select the desired <strong>Data Collection Options</strong>.
- <p class="note"><strong>Note:</strong> If you want to capture progressive frame images for each
-drawing call, enable the <strong>Read back currently bound framebuffer on glDraw*()</strong> option.
-Be aware that using this option can result in large trace files.</p>
- </li>
- <li>Enter a <strong>Destination File</strong> for the trace output.</li>
- <li>Click <strong>Trace</strong> to start the trace capture.</li>
- <li>On the connected device, exercise the functions of your application you want to trace.</li>
- <li>In the dialog box, <strong>Stop Tracing</strong> to complete the tracing run.</li>
-</ol>
-
-<h2 id="analyzing">Analyzing a Trace</h2>
-
-<p>After you have generated a trace, you can load it for review and analysis.</p>
-
-<p>To review a captured trace:</p>
-
-<ol>
- <li>In Device Monitor, activate the <strong>Tracer for OpenGL ES</strong>
-perspective.</li>
- <li>On the toolbar, click the trace load button (<img
-src="{@docRoot}images/gltracer/icon-load-trace.png">).</li>
- <li>After loading a trace, select a frame and review the OpenGL ES calls. Drawing commands are
-highlighted in blue.</li>
-</ol>
+++ /dev/null
-page.title=Hierarchy Viewer
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<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>
-
-<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 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>
-
-
+++ /dev/null
-page.title=HPROF Converter
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<p>
-The <code>hprof-conv</code> tool 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. </p>
-
-<pre> hprof-conv [-z] <infile> <outfile></pre>
-
-<p>
-You can use "-" for <code><infile></code> or <code><outfile></code>
-to specify stdin or stdout.
-</p>
-
-<p>
-You can use "-z" to filter out zygote allocations shared by all applications.
-</p>
-
-<p class="note"><strong>Note:</strong> Android Studio provides integrated access to this conversion
-process. To convert a heap dump to standard HPROF format in Android Studio, right-click a heap
-snapshot in the <em>Captures</em> view and select <strong>Export to standard .hprof</strong>. </p>
-
-
+++ /dev/null
-page.title=Image Asset Studio
-parent.title=Tools
-parent.link=index.html
-page.tags=image asset
-@jd:body
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#access">Accessing Image Asset Studio</a></li>
- <li><a href="#creating">Creating Icons</a></li>
- <li><a href="#customizing">Customizing Icons</a></li>
- <li><a href="#saving">Saving Icons</a></li>
- <li><a href="#configure">Configuring Build Properties</a></li>
- <li><a href="#referincode">Referring to an Image Resource in Code</a></li>
- </ol>
-</div>
-</div>
-
-
-<p>Image Asset Studio helps you to generate custom icons for your Android applications from existing
- image, clipart, or text-string resources. It generates a set of icons at the appropriate resolution
- for each <a href ="{@docRoot}guide/practices/screens_support.html#range"> generalized screen
- density</a> that your app supports.
- The newly generated icons are placed in density-specific folders (for example, <code>mipmap-mdpi/
- </code> or <code>drawable-xxxhdpi/</code>), which
- reside in the application’s <code>res/</code> folder. At runtime, Android uses the appropriate
- resource based on the screen density of the device your application is running on. </p>
-
-<p>Image Asset Studio generates the following asset types:</p>
-<ul>
-<li>Launcher icons.</li>
-<li>Action bar and tab icons.</li>
-<li>Notification icons.</li>
-</ul>
-
-<p>This guide shows how to generate these assets using Image Asset Studio.</p>
-
-<h2 id="access">Accessing Image Asset Studio</h2>
-<p>Follow these steps to access Image Asset Studio:</p>
-<ol>
-<li>In Android Studio, open an Android app project.</li>
-<li>In the <a href= "{@docRoot}sdk/installing/create-project.html#enable-view">project-view-pane</a>
- on the left side of the screen, select <strong>Android</strong> from the dropdown menu. The Android
- project view appears in the pane.
-</li>
-<li>Right-click the <code>res/</code>folder and select <strong>New</strong> > <strong>Image
-Asset</strong>. The Image Asset Studio window appears.</li>
-</ol>
-
-
-<h2 id="creating">Creating Icons</h2>
-<p>You can generate icons from <a href="#launch_image">image</a>, <a href="#launch_clipart">clipart
-</a>, or <a href="#launch_text">text-string</a> resources. This section explains how to work with
-each of these resources.
-</p>
-
-
-<h3 id="launch_image">From an image resource</h3>
-<ol>
-<li>Open the <em>Asset Type</em> dropdown menu and select an icon type.</li>
-<li>From the available <em>Foreground</em> options, select <strong>Image</strong>.</li>
-<li>Specify the asset to use by entering a filename in the <em>Image file</em> field or by
- navigating to and selecting a file via the file browser. Image Asset Studio supports the following
- file types, in descending order of desirability: PNG, JPG, and GIF.
- <p>The icon to be generated appears in the <em>Preview</em> pane, displayed at sizes corresponding
- to different screen densities.</p>
-
-<p>The rest of the settings on this screen are optional.
-To learn how to customize your icons using these options,
- see <a href="#customizing">Customizing Icons</a>.</p></li>
-<li><a href="#saving">Save your icons</a> to the project folder.
-</li>
-</ol>
-
-
-<h3 id="launch_clipart">From a clipart resource</h3>
-<ol>
-<li>Open the <em>Asset Type</em> dropdown menu and select an icon type.</li>
-<li>From the available <em>Foreground</em> options, select <strong>Clipart</strong>. The <strong>
-Choose</strong> button appears.</li>
-<li>Click <strong>Choose</strong>. A window containing clipart resources appears.</li>
-<li> Select a clipart resource.
-<p>The icon to be generated appears in the <em>Preview</em> pane, displayed at sizes corresponding
-to different screen densities.</p>
-<p>The rest of the settings on this screen are optional.
- To learn how to customize your icons using these options,
- see <a href="#customizing">Customizing Icons</a>.</p></li>
-<li><a href="#saving">Save your icons</a> to the project folder.
-</li>
-</ol>
-
-
-
-<h3 id="launch_text"> From a text-string resource</h3>
-<ol>
-<li>Open the <em>Asset Type</em> dropdown menu and select an icon type.</li>
-<li>From the available <em>Foreground </em> options, select <strong>Text</strong>.</li>
-<li>Enter into the <em>Text</em> field the text you want to turn into an icon.
-<p>The icon to be generated appears in the <em> Preview</em> pane, displayed at sizes corresponding
-to different screen densities.</p></li>
-<li>To change the font, select a font from the <em>Font</em> dropdown menu.
-<p>The rest of the settings on this screen are optional.
-To learn how to customize your icons using these options,
-see <a href="#customizing">Customizing Icons</a>.</p></li>
-<li><a href="#saving">Save your icons</a> to the project folder.
-</li>
-</ol>
-
-
-<h2 id="customizing">Customizing Icons</h2>
-<p>Image Asset Studio lets you customize various visual effects for your icons. The following options
-are of particular note.</p>
-
-<ul>
-<li><em>Trim surrounding blank space</em>: This option allows you to adjust the margin between the
-icon graphic and border.
-<figure id="">
- <img src="{@docRoot}images/tools/trim.png"
- width="461">
- <figcaption><strong>Figure 1</strong>: An icon before and after trimming.</figcaption>
-</figure>
-<li><em>Additional Padding</em>: This option allows you to adjust the icon's padding on all four
-sides. Use the slider to select a value between 0 and 100 pixels. For example, for a 100px X 100px
-image with padding of 25px, the resulting image is 150px X 150px.</li>
- <li><em>Theme</em>: This option allows you to set a theme for your action bar and tab icons.
- You can tint icons using the HOLO_DARK or HOLO_LIGHT theme or create
- a custom theme using the color palette.</li>
- <li><em>Resource name</em>: This option allows you to specify a resource name other than the
- default one. If an asset with the specified resource name already exists, Image Asset Studio warns
- you that it is going to overwrite the existing asset with this one.</li></ul>
-
-
-<h2 id="saving">Saving Icons</h2>
- <p>This section explains how to save your icons to the <code>res/</code> folder. Do so by following
- these steps:</p>
- <ol>
- <li>From the initial screen that appeared when you opened Image Asset Studio, click
- <strong>Next</strong>. Image Asset Studio opens a new window.</li>
- <li>Confirm the target module and resource directory settings for the icon.
- If you don't want to use the default target module or resource directory, you can
- <a href="#configure">enter your own values</a> for them.
- </li>
- <li>Click <strong>Finish</strong>. The Image Asset Studio generates new icon files, in PNG format,
- according to the options you have chosen.
- </li>
- </ol>
-
- <p class="note"><strong>Note:</strong> Launcher icon files reside in a different location from that
- of other icons. They are located in the <code>mipmap/</code> folder. All other icon files reside
- in the <code>drawable/</code> folder of your project.</p>
-
-
-<h2 id="configure">Configuring Build Properties</h2>
-<p>To change the module and resource directory, follow these steps:</p>
-<ol>
-<li>In the <em>Target Module</em> field, select a module to add the resource to.
-For more information,
-see <a href="{@docRoot}sdk/installing/create-project.html#CreatingAModule">
-Creating an Android Module</a>.
- </li>
-<li>In the <em>Res Directory</em> field, select an option for where to place the image
- asset:
- <ul>
- <li><code>src/main/res</code>: This source set applies to all build variants, including debug
- and release.</li>
- <li><code>src/debug/res</code>, <code> src/release/res</code>: These source sets override the main
- source set and apply to one version of a build. The debug source set is for debugging only.
- </li>
- <li>User-defined: To define your own source set, select <strong>File</strong> > <strong>Project
- Structure</strong> > <strong>app</strong> > <strong>Build Types</strong>.
- For example, you could define a beta source set and create a version of an icon that includes the
- text "BETA” in the bottom right corner. For more information, see
- <a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">
- Work with build variants</a>.</li>
- </ul>
-</ol>
-
-
-
-
-<h2 id="referincode">Referring to an Image Resource in Code</h2>
-
-<p>After you have an image resource in the <code>res/</code>directory of your project, you can
- reference it from your Java code or your XML layout using its
- <a href="{@docRoot}guide/topics/resources/accessing-resources.html#ResourcesFromCode">
- resource ID</a>. </p>
-
-<p> For example, the following XML references the <code>ic_launcher icon</code> in the
-<code>mipmap/</code> folder.</p>
-<pre>
-<application android:name="ApplicationTitle"
- android:label="@string/app_label"
- android:icon="@mipmap/ic_launcher" ></pre>
-
-<p>The following Java code sets an
-<a href="{@docRoot}reference/android/widget/ImageView.html">ImageView</a> to use
- the <code>drawable/myimage.png</code> resource:</p>
-<pre>ImageView imageView = (ImageView) findViewById(R.id.myimageview);
-imageView.setImageResource(R.drawable.myimage);</pre>
+++ /dev/null
-page.title=Tools Help
-@jd:body
-
-
-<p>The Android SDK includes a variety of tools that help you develop mobile
-applications for the Android platform. The tools are classified into two groups: SDK tools
-and platform tools. SDK tools are platform independent and are required no matter which
-Android platform you are developing on. Platform tools are customized to support the features of the
-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 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>
-
-
-
-<h3 id="tools-virtual-device">Virtual Device Tools</h3>
-<dl>
-
- <dt><a href="{@docRoot}tools/help/avd-manager.html">Android Virtual Device Manager</a></dt>
- <dd>The AVD Manager provides a graphical user interface in which you can create
- and manage Android Virtual Devices (AVDs) that run in the Android Emulator. </dd>
-
- <dt><a href="{@docRoot}tools/help/emulator.html">Android Emulator (emulator)</a></dt>
- <dd>A QEMU-based device-emulation tool that you can use to debug and test
- your applications in an actual Android run-time environment.</dd>
-
- <dt><a href="{@docRoot}tools/help/mksdcard.html">mksdcard</a></dt>
- <dd>Helps you create a disk image that you can use with the emulator, to simulate the presence
- of an external storage card (such as an SD card).</dd>
-
-</dl>
-
-
-
-
-<h3 id="tools-development">Development Tools</h3>
-<dl>
- <dt><a href="{@docRoot}tools/help/android.html">android</a></dt>
- <dd>Lets you manage AVDs, projects, and the installed components of the SDK.</dd>
-
-
- <dt><a href="{@docRoot}tools/help/hierarchy-viewer.html">Hierarchy Viewer (hierarchyviewer)</a></dt>
- <dd>Provides a visual representation of the layout's View hierarchy with performance information
- for each node in the layout, and a magnified view of the display to closely examine the
- pixels in your layout.</dd>
-
- <dt><a href="{@docRoot}tools/help/lint.html">lint</a></dt>
- <dd>The Android {@code lint} tool is a static code analysis tool that checks your Android
- project source files for potential bugs and optimization improvements.</dd>
-
- <dt><a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a></dt>
- <dd>Lets you manage SDK packages, such as installed platforms and system images.</dd>
-
- <dt><a href="{@docRoot}tools/help/sqlite3.html">sqlite3</a></dt>
- <dd>Lets you access the SQLite data files created and used by Android applications.</dd>
-
-
-</dl>
-
-
-
-<h3 id="tools-debugging">Debugging Tools</h3>
-<dl>
-
- <dt><a href="{@docRoot}tools/help/android-monitor.html">Android Monitor</a></dt>
- <dd>Android Monitor is integrated into Android Studio and provides logcat, memory, CPU, GPU, and
- network monitors for app debugging and analysis.</dd>
-
- <dt><a href="{@docRoot}tools/help/adb.html">adb</a></dt>
- <dd>Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with
- an emulator instance or connected Android-powered device. It also provides access to the
- device shell.</dd>
-
- <dt><a href="{@docRoot}tools/help/shell.html">ADB Shell Commands</a></dt>
- <dd>Learn the commands available for advanced command-line operations.</dd>
-
- <dt><a href="{@docRoot}tools/debugging/ddms.html">Dalvik Debug Monitor Server (ddms)</a></dt>
- <dd>Lets you debug Android apps.</dd>
-
- <dt><a href="{@docRoot}tools/help/monitor.html">Device Monitor</a></dt>
- <dd>Android Device Monitor is a stand-alone tool that provides a graphical user interface for
- several Android application debugging and analysis tools.</dd>
-
- <dt><a href="{@docRoot}tools/help/dmtracedump.html">dmtracedump</a></dt>
- <dd>Generates graphical call-stack diagrams from trace log files. The tool uses the
-Graphviz Dot utility to create the graphical output, so you need to install Graphviz before
-running <code>dmtracedump</code>. For more information on using <code>dmtracedump</code>, see <a
-href="{@docRoot}tools/debugging/debugging-tracing.html#dmtracedump">Profiling
-with Traceview and dmtracedump</a></dd>
-
-
- <dt><a href="{@docRoot}tools/help/hprof-conv.html">hprof-conv</a></dt>
- <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/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>
-
- <dt><a href="{@docRoot}tools/help/traceview.html">traceview</a></dt>
- <dd>Provides a graphical viewer for execution logs saved by your application.</dd>
-
- <dt><a href="{@docRoot}tools/help/gltracer.html">Tracer for OpenGL ES</a></dt>
- <dd>Allows you to capture <a href="{@docRoot}guide/topics/graphics/opengl.html">OpenGL ES</a>
- commands and frame-by-frame images to help you understand how your app is executing
- graphics commands.</dd>
-
-</dl>
-
-
-<h3 id="tools-build">Build Tools</h3>
-<dl>
-
- <dt><a href="{@docRoot}tools/help/jobb.html">JOBB</a></dt>
- <dd>Allows you to build encrypted and unencrypted
- <a href="{@docRoot}google/play/expansion-files.html">APK expansion files</a> in Opaque
- Binary Blob (OBB) format.</dd>
-
- <dt><a href="{@docRoot}tools/help/proguard.html">ProGuard</a></dt>
- <dd>Shrinks, optimizes, and obfuscates your code by removing unused code and renaming
-classes, fields, and methods with semantically obscure names.</dd>
-
- <dt><a href="{@docRoot}tools/help/zipalign.html">zipalign</a></dt>
- <dd>Optimizes <code>.apk</code> files by ensuring that all uncompressed data starts with a
-particular alignment relative to the start of the file. This should always be used to align .apk
-files after they have been signed.</dd>
-
-</dl>
-
-
-<h3 id="tools-image">Image Tools</h3>
-<dl>
- <dt><a href="{@docRoot}tools/help/draw9patch.html">Draw 9-patch</a></dt>
- <dd>Allows you to easily create a {@link android.graphics.NinePatch} graphic using a
-WYSIWYG editor. It also previews stretched versions of the image, and highlights the area in which
-content is allowed.</dd>
-
- <dt><a href="{@docRoot}tools/help/etc1tool.html">etc1tool</a></dt>
- <dd>A command line utility that lets you encode PNG images to the ETC1 compression standard and
- decode ETC1 compressed images back to PNG.</dd>
-
-</dl>
-
-
-
-<h2 id="tools-platform">Platform Tools</h2>
-
-<p>The platform tools are typically updated every time you install a new SDK platform. Each update
-of the platform tools is backward compatible with older platforms. Usually, you directly use only
-one of the platform tools—the <a href="adb.html">Android Debug Bridge (<code>adb</code>)</a>.
-Android Debug Bridge is a versatile tool that lets you manage the state of an emulator instance or
-Android-powered device. You can also use it to install an Android application (.apk) file on a
-device.</p>
-
-<p>The other platform tools, such as <a href="{@docRoot}guide/components/aidl.html">aidl</a>,
-<code>aapt</code>, <code>dexdump</code>, and <code>dx</code>, are typically called by the Android
-build tools, so you rarely need to invoke these tools directly.
-As a general rule, you should rely on the build tools to call them as needed.</p>
-
-<p class="note"><strong>Note:</strong> The Android SDK provides additional shell tools that can
-be accessed through <code>adb</code>, such as <a href="{@docRoot}tools/help/bmgr.html">bmgr</a> and
-<a href="{@docRoot}tools/help/logcat.html">logcat</a>.</p>
-<dl>
- <dt><a href="{@docRoot}tools/help/bmgr.html">bmgr</a></dt>
- <dd>A shell tool you can use to interact with the Backup Manager on Android devices supporting
- API Level 8 or greater.</dd>
-
- <dt><a href="{@docRoot}tools/help/logcat.html">logcat</a></dt>
- <dd>Provides a mechanism for collecting and viewing system debug output.</dd>
-
-</dl>
+++ /dev/null
-page.title=JOBB
-@jd:body
-
-
-<p>The {@code jobb} tool allows you to build encrypted and unencrypted APK expansion files in
- Opaque Binary Blob (OBB) format. You can download and mount these expansion files in your
- application using {@link android.os.storage.StorageManager} on devices with Android 2.3 (API
- Level 9) or higher. OBB files are used to provide additional file assets for Android applications
- (such as graphics, sounds and video), separate from an application's APK file. For more
- information on using expansion files, see
- <a href="{@docRoot}google/play/expansion-files.html">APK Expansion Files</a>.</p>
-
-
-<h2 id="usage">Usage</h2>
-
-<p>The syntax for running {@code jobb} is as follows:</p>
-
-<pre>
-jobb [-d <directory>][-o <filename>][-pn <package>][-pv <version>] \
- [-k <key>][-ov][-dump <filename>][-v][-about]
-</pre>
-
-<p>You can use the {@code jobb} tool to create an OBB file or extract the contents of an
-existing OBB. The following example command creates an OBB file from source files.</p>
-
-<pre>
-$ jobb -d /temp/assets/ -o my-app-assets.obb -k secret-key -pn com.my.app.package -pv 11
-</pre>
-
-<p>This example shows how to dump (extract) the contents of an existing OBB file:</p>
-
-<pre>
-$ jobb -d /temp/obb-output/ -o my-app-assets.obb -k secret-key
-</pre>
-
-
-<h2 id="options">Options</h2>
-
-<p>The table below lists the command line options for the {@code jobb} tool.</p>
-
-<table>
- <tr>
- <th>Option</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>{@code -d <directory>}</td>
- <td>Set the input directory for creating an OBB file, or the output directory when extracting
- ({@code -dump}) an existing file. When creating an OBB file, the contents of the specified
- directory and all its sub-directories are included in the OBB file system.
- </td>
- </tr>
- <tr>
- <td>{@code -o <filename>}</td>
- <td>Specify the filename for the OBB file. This parameter is required when
- creating an OBB and extracting (dumping) its contents.</td>
- </tr>
- <tr>
- <td>{@code -pn <package>}</td>
- <td>Specify the package name for the application that mounts the OBB file, which corresponds
- to the {@code package} value specified in your application's manifest. This parameter is
- required when creating an OBB file.</td>
- </tr>
- <tr>
- <td>{@code -pv <version>}</td>
- <td>Set the minimum version for the application that can mount the OBB file, which corresponds
- to the {@code android:versionCode} value in your application's manifest. This parameter is
- required when creating an OBB file.</td>
- </tr>
- <tr>
- <td>{@code -k <key>}</td>
- <td>Specify a password for encrypting a new OBB file or decrypting an existing, encypted
- OBB file.</td>
- </tr>
- <tr>
- <td>{@code -ov}</td>
- <td>Create OBB file that is an overlay of an existing OBB file structure. This option allows
- the new package contents to be mounted into the same location as a previous package and is
- intended for creating patch versions of previously generated OBB files. Files within an
- overlay OBB file replace files that have the same path.</td>
- </tr>
- <tr>
- <td style="white-space: nowrap">{@code -dump <filename>}</td>
- <td><p>Extract the contents of the specified OBB file. When using this option, you must also
- specify the output directory for the contents using the {@code -d <directory>}
- parameter.</p>
-
- <p class="note"><strong>Note:</strong> When dumping an existing OBB file, you can omit the
- {@code -d <directory>} parameter to get a listing of the directories inside the file,
- without extracting the contents.</p>
- </td>
- </tr>
- <tr>
- <td>{@code -v}</td>
- <td>Set verbose output for the tool.</td>
- </tr>
- <tr>
- <td>{@code -about}</td>
- <td>Display version and help information for the {@code jobb} tool.</td>
- </tr>
-
-</table>
+++ /dev/null
-page.title=layoutopt
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-
-<p class="note"><strong>Note: </strong>The Android <code>layoutopt</code> tool has been replaced
-by the {@code lint} tool beginning in SDK Tools revision 16. The {@code lint} tool reports UI
-layout performance issues in a similar way as <code>layoutopt</code>, and detects additional problems.</p>
-<p>For more information about using {@code lint}, see
-<a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a> and the
-<a href="{@docRoot}tools/help/lint.html">lint reference documentation</a>.</p>
-
-<p><code>layoutopt</code> is a command-line tool that helps you optimize the
-layouts and layout hierarchies of your applications.<p>
-
-<p>This document is a reference to the available command line options. For more information and
-sample
-output of the tool, see <a
-href="{@docRoot}tools/debugging/debugging-ui.html#layoutopt">Optimizing layouts with
-layoutopt</a>.</p>
-
-<h3>Usage</h3>
-
-<p>To run <code>layoutopt</code> against a given list of layout resources:</p>
-
-<pre>layoutopt <file_or_directory> ...</pre>
-
-<p>For example:</p>
-
-<pre>$ layoutopt res/layout-land</pre>
-<pre>$ layoutopt res/layout/main.xml res/layout-land/main.xml</pre>
-
+++ /dev/null
-page.title=lint
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#syntax">Syntax</a></li>
- <li><a href="#options">Options</a></li>
- <li><a href="#config_keywords">Configuring Java and XML Source Files</a></li>
- </ol>
- </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>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.
-<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.
-<pre>lint --check MissingPrefix myproject</pre>
-
-You can create an HTML report for the issues that {@code lint} detects. For example, you can run the following command to scan the {@code myproject} directory and its subdirectories for accessibility issues, then generate an HTML report in the {@code accessibility_report.html} file.
-<pre>lint --check Accessibility --HTML accessibility_report.html myproject</pre>
-</p>
-
-<h2 id="options">Options</h2>
-<p>Table 1 describes the command-line options for {@code lint}.</p>
-<p class="table-caption" id="table1">
- <strong>Table 1.</strong> Command-line options for lint</p>
-<table>
-<tr>
- <th>Category</th>
- <th>Option</th>
- <th>Description</th>
- <th>Comments</th>
-</tr>
-
-<tr>
-<td rowspan="7">Checking</td>
-<td><nobr><code>--disable <list></code></nobr></td>
-<td>Disable checking for a specific list of issues.</td>
-<td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--enable <list></code></nobr></td>
-<td>Check for all the default issues supported by {@code lint} as well as the specifically enabled list of issues.</td>
-<td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--check <list></code></nobr></td>
-<td>Check for a specific list of issues.</td>
-<td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
-</tr>
-
-<tr>
-<td><nobr><code>-w</code> or <code>--nowarn</code></nobr></td>
-<td>Only check for errors and ignore warnings</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>-Wall</code></nobr></td>
-<td>Check for all warnings, including those that are disabled by default</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>-Werror</code></nobr></td>
-<td>Report all warnings as errors</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--config <filename></code></nobr></td>
-<td>Use the specified configuration file to determine if issues are enabled or disabled for {@code lint} checking</td>
-<td>If the project contains a {@code lint.xml} file, the {@code lint.xml} file will be used as the configuration file by default.</td>
-</tr>
-
-<tr>
-<td rowspan="9">Reporting</td>
-<td><nobr><code>--html <filename></code></nobr></td>
-<td>Generate an HTML report.</td>
-<td>The report is saved in the output file specified in the argument. The HTML output includes code snippets of the source code where {@code lint} detected an issue, a verbose description of the issue found, and links to the source file.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--url <filepath>=<url></code></nobr></td>
-<td>In the HTML output, replace a local path prefix <code><filepath></code> with a url prefix <code><url></code>.</td>
-<td>The {@code --url} option only applies when you are generating an HTML report with the {@code --html} option. You can specify multiple <filepath>=<url> mappings in the argument by separating each mapping with a comma.<p>To turn off linking to files, use {@code --url none}</p></td>
-</tr>
-
-<tr>
-<td><nobr><code>--simplehtml <filename></code></nobr></td>
-<td>Generate a simple HTML report</td>
-<td>The report is saved in the output file specified in the argument.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--xml <filename></code></nobr></td>
-<td>Generate an XML report</td>
-<td>The report is saved in the output file specified in the argument.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--fullpath</code></nobr></td>
-<td>Show the full file paths in the {@code lint} checking results.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--showall</code></nobr></td>
-<td>Don't truncate long messages or lists of alternate locations.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--nolines</code></nobr></td>
-<td>Don't include code snippets from the source files in the output.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--exitcode</code></nobr></td>
-<td>Set the exit code to 1 if errors are found.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--quiet</code></nobr></td>
-<td>Don't show the progress indicator.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td rowspan="4">Help</td>
-<td><nobr><code>--help</code></nobr></td>
-<td>List the command-line arguments supported by the {@code lint} tool.</td>
-<td>Use {@code --help <topic>} to see help information for a specific topic, such as "suppress".</td>
-</tr>
-
-<tr>
-<td><nobr><code>--list</code></nobr></td>
-<td>List the ID and short description for issues that can be checked by {@code lint}</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><nobr><code>--show</code></nobr></td>
-<td>List the ID and verbose description for issues that can be checked by {@code lint}</td>
-<td>Use {@code --show <ids>} to see descriptions for a specific list of {@code lint} issue IDs.</td>
-</tr>
-
-<tr>
-<td><nobr><code>--version</code></nobr></td>
-<td>Show the {@code lint} version</td>
-<td> </td>
-</tr>
-
-</table>
-
-
-<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 {@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 {@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>
+++ /dev/null
-page.title=logcat
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>See also</h2>
-
- <ol>
- <li><a href="{@docRoot}tools/help/android-monitor.html">Android Monitor</a></li>
- </ol>
- </div>
- </div>
-
- <p>The Android logging system provides a mechanism for collecting and viewing system debug
- output. Logs from various applications and portions of the system are collected in a series of
- circular buffers, which then can be viewed and filtered by the <code>logcat</code> command. You can use
- <code>logcat</code> from an ADB shell to view the log messages.</p>
-
- <p>For complete information about logcat options and filtering specifications, see
- <a href="{@docRoot}tools/debugging/debugging-log.html">Reading and Writing Logs</a>.</p>
-
- <p>For more information on accessing <code>logcat</code> from DDMS, instead of the command line, see
- <a href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a>. </p>
-
- <h3>Syntax</h3>
- <pre>
-[adb] logcat [<option>] ... [<filter-spec>] ...
-</pre>
-
- <p>You can run <code>logcat</code> as an adb command or directly in a shell prompt
- of your emulator or connected device. To view log output using adb, navigate to your SDK
- <code>platform-tools/</code> directory and execute:</p>
- <pre>
-$ adb logcat
-</pre>
-
- <p>You can create a shell connection to a device and execute:</p>
- <pre>
-$ adb shell
-# logcat
-</pre>
-
- <h3>Options</h3>
- <p>The following table describes the command line options of <code>logcat</code>.</p>
-
- <table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><code>-b <buffer></code></td>
-
- <td>Loads an alternate log buffer for viewing, such as <code>events</code> or
- <code>radio</code>. The <code>main</code> buffer is used by default. See <a href=
- "{@docRoot}tools/debugging/debugging-log.html#alternativeBuffers">Viewing Alternative Log Buffers</a>.</td>
- </tr>
-
- <tr>
- <td><code>-c</code></td>
-
- <td>Clears (flushes) the entire log and exits.</td>
- </tr>
-
- <tr>
- <td><code>-d</code></td>
-
- <td>Dumps the log to the screen and exits.</td>
- </tr>
-
- <tr>
- <td><code>-f <filename></code></td>
-
- <td>Writes log message output to <code><filename></code>. The default is
- <code>stdout</code>.</td>
- </tr>
-
- <tr>
- <td><code>-g</code></td>
-
- <td>Prints the size of the specified log buffer and exits.</td>
- </tr>
-
- <tr>
- <td><code>-n <count></code></td>
-
- <td>Sets the maximum number of rotated logs to <code><count></code>. The default value
- is 4. Requires the <code>-r</code> option.</td>
- </tr>
-
- <tr>
- <td><code>-r <kbytes></code></td>
-
- <td>Rotates the log file every <code><kbytes></code> of output. The default value is
- 16. Requires the <code>-f</code> option.</td>
- </tr>
-
- <tr>
- <td><code>-s</code></td>
-
- <td>Sets the default filter spec to silent.</td>
- </tr>
-
- <tr>
- <td><code>-v <format></code></td>
-
- <td>Sets the output format for log messages. The default is <code>brief</code> format. For a
- list of supported formats, see <a href="{@docRoot}tools/debugging/debugging-log.html#outputFormat">Controlling Log Output
- Format</a>.</td>
- </tr>
- </table>
+++ /dev/null
-page.title=mksdcard
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
- <p>The <code>mksdcard</code> tool lets you quickly create a FAT32 disk image that you can load in the
- emulator, to simulate the presence of an SD card in the device. Because you can specify an SD
- card while creating an AVD in the AVD Manager, you usually use that feature to create an SD card.
- This tool creates an SD card that is not bundled with an AVD, so it is useful for situations
- where you need to share a virtual SD card between multiple emulators.</p>
-
- <h3>Usage</h3>
- <pre>
-mksdcard -l <label> <size> <file>
-</pre>
-
- <h3>Options</h3>
- <p>The following table describes the command-line options of <code>mksdcard</code></p>
- <table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><code>-l</code></td>
-
- <td>A volume label for the disk image to create.</td>
- </tr>
-
- <tr>
- <td><code>size</code></td>
-
- <td>An integer that specifies the size (in bytes) of disk image to create. You can also
- specify size in kilobytes or megabytes, by appending a "K" or "M" to <size>. For
- example, <code>1048576K</code>, <code>1024M</code>.</td>
- </tr>
-
- <tr>
- <td><code>file</code></td>
-
- <td>The path/filename of the disk image to create.</td>
- </tr>
- </table>
-
- <p>Once you have created the disk image file, you can load it in the emulator at startup using
- the emulator's <code>-sdcard</code> option. For more information, see <a href=
- "{@docRoot}tools/help/emulator.html">Android Emulator</a>.</p>
-
- <p>The usage for the <code>-sdcard</code> option is as follows:</p>
- <pre>emulator -sdcard <file></pre>
-
-<h3>Example</h3>
-<pre>mksdcard -l mySdCard 1024M mySdCardFile.img</pre>
\ No newline at end of file
+++ /dev/null
-page.title=Device Monitor
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>See also</h2>
-
- <ol>
- <li><a href="{@docRoot}tools/debugging/debugging-memory.html"
- >Investigating Your RAM Usage</a></li>
- <li><a href="{@docRoot}tools/help/android-monitor.html">Android Monitor</a></li>
- </ol>
- </div>
- </div>
-
-
-<p>Android Device 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 an integrated development environment, such as Android Studio, and
-encapsulates the following tools:</p>
-
-<ul>
- <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a></li>
- <li><a href="gltracer.html">Tracer for OpenGL ES</a></li>
- <li><a href="hierarchy-viewer.html">Hierarchy Viewer</a></li>
- <li><a href="systrace.html">Systrace</a></li>
- <li><a href="traceview.html">Traceview</a></li>
- <li>Pixel Perfect magnification viewer</li>
-</ul>
-
-
-<h2 id="usage">Usage</h2>
-
-<p>To start Device Monitor:</p>
-
-<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=""/>.
- </li>
- <li>From the command line, in the SDK <code>tools/</code> directory, enter the following command:
- <pre>monitor</pre>
- </li>
-</ul>
-
-
-
-<p>Start an Android emulator or connect an Android device via USB cable, and connect Device
-Monitor to the device by selecting it in the <strong>Devices</strong> window.</p>
-
-<p class="note"><strong>Note:</strong> Only one debugger can be connected to your device at a time.</p>
+++ /dev/null
-page.title=UI/Application Exerciser Monkey
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<p>The Monkey is a program that runs on your
-<a href="{@docRoot}tools/help/emulator.html">emulator</a> 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.</p>
-
-<a name="overview"></a>
-<h2>Overview</h2>
-
-<p>The Monkey is a command-line tool that you can run on any emulator
-instance or on a device. It sends a pseudo-random stream of
-user events into the system, which acts as a stress test on the application software you are
-developing.</p>
-
-<p>The Monkey includes a number of options, but they break down into four primary
-categories:</p>
-
-<ul>
- <li>Basic configuration options, such as setting the number of events to attempt.</li>
- <li>Operational constraints, such as restricting the test to a single package.</li>
- <li>Event types and frequencies.</li>
- <li>Debugging options.</li>
-</ul>
-
-<p>When the Monkey runs, it generates events and sends them to the system. It also <i>watches</i>
-the system under test and looks for three conditions, which it treats specially:</p>
-
-<ul>
- <li>If you have constrained the Monkey to run in one or more specific packages, it
- watches for attempts to navigate to any other packages, and blocks them.</li>
- <li>If your application crashes or receives any sort of unhandled exception, the Monkey
- will stop and report the error.</li>
- <li>If your application generates an <i>application not responding</i> error, the Monkey
- will stop and report the error.</li>
-</ul>
-
-<p>Depending on the verbosity level you have selected, you will also see reports on the progress
-of the Monkey and the events being generated.</p>
-
-<a name="basics"></a>
-<h2>Basic Use of the Monkey</h2>
-
-<p>You can launch the Monkey using a command line on your development machine or from a script.
-Because the Monkey runs in the emulator/device environment, you must launch it from a shell in
-that environment. You can do this by prefacing <code>adb shell</code> to each command,
-or by entering the shell and entering Monkey commands directly.</p>
-<p>The basic syntax is: </p>
-
-<pre>$ adb shell monkey [options] <event-count></pre>
-
-<p>With no options specified, the Monkey will launch in a quiet (non-verbose) mode, and will send
-events to any (and all) packages installed on your target. Here is a more typical command line,
-which will launch your application and send 500 pseudo-random events to it:</p>
-
-<pre>$ adb shell monkey -p your.package.name -v 500</pre>
-
-<a name="reference"></a>
-<h2>Command Options Reference</h2>
-
-<p>The table below lists all options you can include on the Monkey command line.</p>
-
-<table>
-<tr>
- <th>Category</th>
- <th>Option</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td rowspan="2">General</td>
-<td><code>--help</code></td>
-<td>Prints a simple usage guide.</td>
-</tr>
-
-<tr>
-<td><code>-v</code></td>
-<td>Each -v on the command line will increment the verbosity level.
-Level 0 (the default) provides little information beyond startup notification, test completion, and
-final results.
-Level 1 provides more details about the test as it runs, such as individual events being sent to
-your activities.
-Level 2 provides more detailed setup information such as activities selected or not selected for
-testing.</td>
-</tr>
-
-<tr>
-<td rowspan="10">Events</td>
-<td><code>-s <seed></code></td>
-<td>Seed value for pseudo-random number generator. If you re-run the Monkey with the same seed
-value, it will generate the same sequence of events.</td>
-</tr>
-
-<tr>
-<td><code>--throttle <milliseconds></code></td>
-<td>Inserts a fixed delay between events. You can use this option to slow down the Monkey.
-If not specified, there is no delay and the events are generated as rapidly as possible.</td>
-</tr>
-
-<tr>
-<td><code>--pct-touch <percent></code></td>
-<td>Adjust percentage of touch events.
-(Touch events are a down-up event in a single place on the screen.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-motion <percent></code></td>
-<td>Adjust percentage of motion events.
-(Motion events consist of a down event somewhere on the screen, a series of pseudo-random
-movements, and an up event.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-trackball <percent></code></td>
-<td>Adjust percentage of trackball events.
-(Trackball events consist of one or more random movements, sometimes followed by a click.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-nav <percent></code></td>
-<td>Adjust percentage of "basic" navigation events.
-(Navigation events consist of up/down/left/right, as input from a directional input device.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-majornav <percent></code></td>
-<td>Adjust percentage of "major" navigation events.
-(These are navigation events that will typically cause actions within your UI, such as
-the center button in a 5-way pad, the back key, or the menu key.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-syskeys <percent></code></td>
-<td>Adjust percentage of "system" key events.
-(These are keys that are generally reserved for use by the system, such as Home, Back, Start Call,
-End Call, or Volume controls.)</td>
-</tr>
-
-<tr>
-<td><code>--pct-appswitch <percent></code></td>
-<td>Adjust percentage of activity launches. At random intervals, the Monkey will issue a startActivity() call, as a way of maximizing
-coverage of all activities within your package.</td>
-</tr>
-
-<tr>
-<td><code>--pct-anyevent <percent></code></td>
-<td>Adjust percentage of other types of events. This is a catch-all for all other types of events such as keypresses, other less-used
-buttons on the device, and so forth.</td>
-</tr>
-
-<tr>
-<td rowspan="2">Constraints</td>
-<td><code>-p <allowed-package-name></code></td>
-<td>If you specify one or more packages this way, the Monkey will <i>only</i> allow the system
-to visit activities within those packages. If your application requires access to activities in
-other packages (e.g. to select a contact) you'll need to specify those packages as well.
-If you don't specify any packages, the Monkey will allow the system to launch activities
-in all packages. To specify multiple packages, use the -p option multiple times — one -p
-option per package.</td>
-</tr>
-
-<tr>
-<td><code>-c <main-category></code></td>
-<td>If you specify one or more categories this way, the Monkey will <i>only</i> allow the
-system to visit activities that are listed with one of the specified categories.
-If you don't specify any categories, the Monkey will select activities listed with the category
-Intent.CATEGORY_LAUNCHER or Intent.CATEGORY_MONKEY. To specify multiple categories, use the -c
-option multiple times — one -c option per category.</td>
-</tr>
-
-<tr>
-<td rowspan="8">Debugging</td>
-<td><code>--dbg-no-events</code></td>
-<td>When specified, the Monkey will perform the initial launch into a test activity, but
-will not generate any further events.
-For best results, combine with -v, one or more package constraints, and a non-zero throttle to keep the Monkey
-running for 30 seconds or more. This provides an environment in which you can monitor package
-transitions invoked by your application.</td>
-</tr>
-
-<tr>
-<td><code>--hprof</code></td>
-<td>If set, this option will generate profiling reports immediately before and after
-the Monkey event sequence.
-This will generate large (~5Mb) files in data/misc, so use with care. See
-<a href="{@docRoot}tools/debugging/debugging-tracing.html" title="traceview">Traceview</a> for more information
-on trace files.</td>
-</tr>
-
-<tr>
-<td><code>--ignore-crashes</code></td>
-<td>Normally, the Monkey will stop when the application crashes or experiences any type of
-unhandled exception. If you specify this option, the Monkey will continue to send events to
-the system, until the count is completed.</td>
-</tr>
-
-<tr>
-<td><code>--ignore-timeouts</code></td>
-<td>Normally, the Monkey will stop when the application experiences any type of timeout error such
-as a "Application Not Responding" dialog. If you specify this option, the Monkey will continue to
-send events to the system, until the count is completed.</td>
-</tr>
-
-<tr>
-<td><code>--ignore-security-exceptions</code></td>
-<td>Normally, the Monkey will stop when the application experiences any type of permissions error,
-for example if it attempts to launch an activity that requires certain permissions. If you specify
-this option, the Monkey will continue to send events to the system, until the count is
-completed.</td>
-</tr>
-
-<tr>
-<td><code>--kill-process-after-error</code></td>
-<td>Normally, when the Monkey stops due to an error, the application that failed will be left
-running. When this option is set, it will signal the system to stop the process in which the error
-occurred.
-Note, under a normal (successful) completion, the launched process(es) are not stopped, and
-the device is simply left in the last state after the final event.</td>
-</tr>
-
-<tr>
-<td><code>--monitor-native-crashes</code></td>
-<td>Watches for and reports crashes occurring in the Android system native code. If --kill-process-after-error is set, the system will stop.</td>
-</tr>
-
-<tr>
-<td><code>--wait-dbg</code></td>
-<td>Stops the Monkey from executing until a debugger is attached to it.</td>
-</tr>
-
-</table>
-
-<!-- TODO: add a section called "debugging" that covers ways to use it,
-need to clear data, use of the seed, etc. -->
-
-<!-- TODO: add a section that lays down a contract for Monkey output so it can be
-scripted safely. -->
-
+++ /dev/null
-page.title=monkeyrunner
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li>
- <a href="#SampleProgram">A Simple monkeyrunner Program</a>
- </li>
- <li>
- <a href="#APIClasses">The monkeyrunner API</a>
- </li>
- <li>
- <a href="#RunningMonkeyRunner">Running monkeyrunner</a>
- </li>
- <li>
- <a href="#Help">monkeyrunner Built-in Help</a>
- </li>
- <li>
- <a href="#Plugins">Extending monkeyrunner with Plugins</a>
- </li>
- </ol>
- <h2>See Also</h2>
- <ol>
- <li>
- <a href="{@docRoot}tools/testing/testing_android.html">Testing Fundamentals</a>
- </li>
- </ol>
- </div>
-</div>
-<p>
- The monkeyrunner tool provides an API for writing programs that control an Android device
- or emulator from outside of Android code. With monkeyrunner, you can write a Python program
- that installs an Android application or test package, runs it, sends keystrokes to it,
- takes screenshots of its user interface, and stores screenshots on the workstation. The
- monkeyrunner tool is primarily designed to test applications and devices at the
- functional/framework level and for running unit test suites, but you are free to use it for
- other purposes.
-</p>
-<p>
- The monkeyrunner tool is not related to the
- <a href="{@docRoot}tools/help/monkey.html">UI/Application Exerciser Monkey</a>,
- also known as the <code>monkey</code> tool. The <code>monkey</code> tool runs in an
- <code><a href="{@docRoot}tools/help/adb.html">adb</a></code> shell directly on the
- device or emulator and generates pseudo-random streams of user and system events. In comparison,
- the monkeyrunner tool controls devices and emulators from a workstation by sending specific
- commands and events from an API.
-</p>
-<p>
- The monkeyrunner tool provides these unique features for Android testing:
-</p>
-<ul>
- <li>
- Multiple device control: The monkeyrunner API can apply one or more
- test suites across multiple devices or emulators. You can physically attach all the devices
- or start up all the emulators (or both) at once, connect to each one in turn
- programmatically, and then run one or more tests. You can also start up an emulator
- configuration programmatically, run one or more tests, and then shut down the emulator.
- </li>
- <li>
- Functional testing: monkeyrunner can run an automated start-to-finish test of an Android
- application. You provide input values with keystrokes or touch events, and view the results
- as screenshots.
- </li>
- <li>
- Regression testing - monkeyrunner can test application stability by running an application
- and comparing its output screenshots to a set of screenshots that are known to be correct.
- </li>
- <li>
- Extensible automation - Since monkeyrunner is an API toolkit, you can develop an entire
- system of Python-based modules and programs for controlling Android devices. Besides using
- the monkeyrunner API itself, you can use the standard Python
- <code><a href="http://docs.python.org/library/os.html">os</a></code> and
- <code><a href="http://docs.python.org/library/subprocess.html">subprocess</a></code>
- modules to call Android tools such as
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>.
- <p>
- You can also add your own classes to the monkeyrunner API. This is described
- in more detail in the section
- <a href="#Plugins">Extending monkeyrunner with plugins</a>.
- </p>
- </li>
-</ul>
-<p>
- The monkeyrunner tool uses <a href="http://www.jython.org/">Jython</a>, a
- implementation of Python that uses the Java programming language. Jython allows the
- monkeyrunner API to interact easily with the Android framework. With Jython you can
- use Python syntax to access the constants, classes, and methods of the API.
-</p>
-
-<h2 id="SampleProgram">A Simple monkeyrunner Program</h2>
-<p>
- Here is a simple monkeyrunner program that connects to a device, creating a
- <code><a href="{@docRoot}tools/help/MonkeyDevice.html">MonkeyDevice</a></code>
- object. Using the <code>MonkeyDevice</code> object, the program installs an Android application
- package, runs one of its activities, and sends key events to the activity.
- The program then takes a screenshot of the result, creating a
- <code><a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a></code> object.
- From this object, the program writes out a <code>.png</code> file containing the screenshot.
-</p>
-<pre>
-# Imports the monkeyrunner modules used by this program
-from com.android.monkeyrunner import MonkeyRunner, MonkeyDevice
-
-# Connects to the current device, returning a MonkeyDevice object
-device = MonkeyRunner.waitForConnection()
-
-# Installs the Android package. Notice that this method returns a boolean, so you can test
-# to see if the installation worked.
-device.installPackage('myproject/bin/MyApplication.apk')
-
-# sets a variable with the package's internal name
-package = 'com.example.android.myapplication'
-
-# sets a variable with the name of an Activity in the package
-activity = 'com.example.android.myapplication.MainActivity'
-
-# sets the name of the component to start
-runComponent = package + '/' + activity
-
-# Runs the component
-device.startActivity(component=runComponent)
-
-# Presses the Menu button
-device.press('KEYCODE_MENU', MonkeyDevice.DOWN_AND_UP)
-
-# Takes a screenshot
-result = device.takeSnapshot()
-
-# Writes the screenshot to a file
-result.writeToFile('myproject/shot1.png','png')
-</pre>
-
-<h2 id="APIClasses">The monkeyrunner API</h2>
-<p>
- The monkeyrunner API is contained in three modules in the package
- <code>com.android.monkeyrunner</code>:
-</p>
-<ul>
- <li>
- <code><a href="{@docRoot}tools/help/MonkeyRunner.html">MonkeyRunner</a></code>:
- A class of utility methods for monkeyrunner programs. This class provides a method for
- connecting monkeyrunner to a device or emulator. It also provides methods for
- creating UIs for a monkeyrunner program and for displaying the built-in help.
- </li>
- <li>
- <code><a href="{@docRoot}tools/help/MonkeyDevice.html">MonkeyDevice</a></code>:
- Represents a device or emulator. This class provides methods for installing and
- uninstalling packages, starting an Activity, and sending keyboard or touch events to an
- application. You also use this class to run test packages.
- </li>
- <li>
- <code><a href="{@docRoot}tools/help/MonkeyImage.html">MonkeyImage</a></code>:
- Represents a screen capture image. This class provides methods for capturing screens,
- converting bitmap images to various formats, comparing two MonkeyImage objects, and
- writing an image to a file.
- </li>
-</ul>
-<p>
- In a Python program, you access each class as a Python module. The monkeyrunner tool
- does not import these modules automatically. To import a module, use the
- Python <code>from</code> statement:
-</p>
-<pre>
-from com.android.monkeyrunner import <module>
-</pre>
-<p>
- where <code><module></code> is the class name you want to import. You can import more
- than one module in the same <code>from</code> statement by separating the module names with
- commas.
-</p>
-<h2 id="RunningMonkeyRunner">Running monkeyrunner</h2>
-<p>
- You can either run monkeyrunner programs from a file, or enter monkeyrunner statements in
- an interactive session. You do both by invoking the <code>monkeyrunner</code> command
- which is found in the <code>tools/</code> subdirectory of your SDK directory.
- If you provide a filename as an argument, the <code>monkeyrunner</code> command
- runs the file's contents as a Python program; otherwise, it starts an interactive session.
-</p>
-<p>
- The syntax of the <code>monkeyrunner</code> command is
-</p>
-<pre>
-monkeyrunner -plugin <plugin_jar> <program_filename> <program_options>
-</pre>
-<p>
-Table 1 explains the flags and arguments.
-</p>
-<p class="table-caption" id="table1">
- <strong>Table 1.</strong> <code>monkeyrunner</code> flags and arguments.</p>
-
-<table>
- <tr>
- <th>Argument</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>
- <nobr>
- <code>-plugin <plugin_jar></code>
- </nobr>
- </td>
- <td>
- (Optional) Specifies a <code>.jar</code> file containing a plugin for monkeyrunner.
- To learn more about monkeyrunner plugins, see
- <a href="#Plugins">Extending monkeyrunner with plugins</a>. To specify more than one
- file, include the argument multiple times.
- </td>
- </tr>
- <tr>
- <td>
- <nobr>
- <code><program_filename></code>
- </nobr>
- </td>
- <td>
- If you provide this argument, the <code>monkeyrunner</code> command runs the contents
- of the file as a Python program. If the argument is not provided, the command starts an
- interactive session.
- </td>
- </tr>
- <tr>
- <td>
- <code><program_options></code>
- </td>
- <td>
- (Optional) Flags and arguments for the program in <program_file>.
- </td>
- </tr>
-</table>
-<h2 id="Help">monkeyrunner Built-in Help</h2>
-<p>
- You can generate an API reference for monkeyrunner by running:
-</p>
-<pre>
-monkeyrunner help.py <format> <outfile>
-</pre>
-<p>
-The arguments are:
-</p>
- <ul>
- <li>
- <code><format></code> is either <code>text</code> for plain text output
- or <code>html</code> for HTML output.
- </li>
- <li>
- <code><outfile></code> is a path-qualified name for the output file.
- </li>
- </ul>
-<h2 id="Plugins">Extending monkeyrunner with Plugins</h2>
-<p>
- You can extend the monkeyrunner API with classes you write in the Java programming language
- and build into one or more <code>.jar</code> files. You can use this feature to extend the
- monkeyrunner API with your own classes or to extend the existing classes. You can also use this
- feature to initialize the monkeyrunner environment.
-</p>
-<p>
- To provide a plugin to monkeyrunner, invoke the <code>monkeyrunner</code> command with the
- <code>-plugin <plugin_jar></code> argument described in
- <a href="#table1">table 1</a>.
-</p>
-<p>
- In your plugin code, you can import and extend the the main monkeyrunner classes
- <code>MonkeyDevice</code>, <code>MonkeyImage</code>, and <code>MonkeyRunner</code> in
- <code>com.android.monkeyrunner</code> (see <a href="#APIClasses">The monkeyrunner API</a>).
-</p>
-<p>
- Note that plugins do not give you access to the Android SDK. You can't import packages
- such as <code>com.android.app</code>. This is because monkeyrunner interacts with the
- device or emulator below the level of the framework APIs.
-</p>
-<h3>The plugin startup class</h3>
-<p>
- The <code>.jar</code> file for a plugin can specify a class that is instantiated before
- script processing starts. To specify this class, add the key
- <code>MonkeyRunnerStartupRunner</code> to the <code>.jar</code> file's
- manifest. The value should be the name of the class to run at startup. The following
- snippet shows how you would do this within an <code>ant</code> build script:
-</p>
-<pre>
-<jar jarfile="myplugin" basedir="${build.dir}">
-<manifest>
-<attribute name="MonkeyRunnerStartupRunner" value="com.myapp.myplugin"/>
-</manifest>
-</jar>
-
-
-</pre>
-<p>
- To get access to monkeyrunner's runtime environment, the startup class can implement
- <code>com.google.common.base.Predicate<PythonInterpreter></code>. For example, this
- class sets up some variables in the default namespace:
-</p>
-<pre>
-package com.android.example;
-
-import com.google.common.base.Predicate;
-import org.python.util.PythonInterpreter;
-
-public class Main implements Predicate<PythonInterpreter> {
- @Override
- public boolean apply(PythonInterpreter anInterpreter) {
-
- /*
- * Examples of creating and initializing variables in the monkeyrunner environment's
- * namespace. During execution, the monkeyrunner program can refer to the variables "newtest"
- * and "use_emulator"
- *
- */
- anInterpreter.set("newtest", "enabled");
- anInterpreter.set("use_emulator", 1);
-
- return true;
- }
-}
-</pre>
+++ /dev/null
-page.title=Shrink Your Code and Resources
-parent.title=Tools
-parent.link=index.html
-page.metaDescription=Make your APK file smaller and more secure by shrinking your code and resources.
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#shrink-code">Shrink Your Code</a>
- <ol>
- <li><a href="#keep-code">Customize which code to keep</a></li>
- <li><a href="#decode-stack-trace">Decode an obfuscated stack trace</a></li>
- </ol>
- </li>
- <li><a href="#shrink-resources">Shrink Your Resources</a>
- <ol>
- <li><a href="#keep-resources">Customize which resources to keep</a></li>
- <li><a href="#strict-reference-checks">Enable strict reference checks</a></li>
- <li><a href="#unused-alt-resources">Remove unused alternative resources</a></li>
- <li><a href="#merge-resources">Merge duplicate resources</a></li>
- <li><a href="#troubleshoot-resource-shrink">Troubleshoot resource shrinking</a></li>
- </ol>
- </li>
-</ol>
-
- <h2>See also</h2>
- <ul>
- <li>
- <a class="external-link"
- href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard
- Manual</a>
- </li>
- </ul>
- </div>
- </div>
-
-
-
-<p>To make your APK file as small as possible, you should enable shrinking for
-your code and resources in your release build. This guide describes how to do
-both and how to specify what to keep or discard during a build.</p>
-
-<p>Code shrinking is available with ProGuard, which detects and removes unused
-classes, fields, methods, and attributes from your packaged app, including
-those from included code libraries (making it a valuable tool for working
-around the <a href="{@docRoot}tools/building/multidex.html">64k reference
-limit</a>). ProGuard also optimizes the bytecode, removes unused code
-instructions, and obfuscates the remaining classes, fields, and methods with
-short names. The obfuscated code makes your APK difficult to reverse engineer,
-which is especially valuable when your app uses security-sensitive features,
-such as <a href="{@docRoot}google/play/licensing/overview.html">licensing
-verification</a>.</p>
-
-<p>Resource shrinking is available with the Android Plugin for Gradle, which
-removes unused resources from your packaged app, including unused resources in
-code libraries. It works in conjunction with code shrinking such that once
-unused code has been removed, any resources no longer referenced can be safely
-removed as well.</p>
-
-
-<p>Features in this document depend on:</p>
-<ul>
-<li><a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools</a> 25.0.10
-or higher</li>
-<li><a href="{@docRoot}tools/revisions/gradle-plugin.html">Android Plugin
-for Gradle</a> 2.0.0 or higher</li>
-</ul>
-
-<h2 id="shrink-code">Shrink Your Code</h2>
-
-<p>To enable code shrinking with ProGuard, add <code>minifyEnabled true</code>
-to the appropriate build type in your <code>build.gradle</code> file.</p>
-
-<p>Be aware that code shrinking slows down the build time, so you should avoid
-using it on your debug build if possible. However, it's important that you
-do enable code shrinking on your final APK used for testing, because it might
-introduce bugs if you do not sufficiently <a href="#keep-code">customize which
-code to keep</a>.</p>
-
-<p>For example, the following snippet from a <code>build.gradle</code> file
-enables code shrinking for the release build:</p>
-
-<pre class="no-pretty-print">
-android {
- buildTypes {
- release {
- minifyEnabled true
- proguardFiles getDefaultProguardFile(‘proguard-android.txt'),
- 'proguard-rules.pro</a>'
- }
- }
- ...
-}
-</pre>
-
-<p class="note"><strong>Note</strong>: Android Studio disables ProGuard when
-using <a href=
-"{@docRoot}tools/building/building-studio.html#instant-run">Instant
-Run</a>.</p>
-
-<p>In addition to the <code>minifyEnabled</code> property, the
-<code>proguardFiles</code> property defines the ProGuard rules:</p>
-
-<ul>
-<li>The <code>getDefaultProguardFile(‘proguard-android.txt')</code> method gets
-the default ProGuard settings from the Android SDK <code>tools/proguard/</code>
-folder.
-<p><strong>Tip</strong>: For even more code shrinking, try the
-<code>proguard-android-optimize.txt</code> file that's in the same location. It
-includes the same ProGuard rules, but with other optimizations that perform
-analysis at the bytecode level—inside and across methods—to reduce your APK
-size further and help it run faster.</p>
-</li>
-<li>The <code>proguard-rules.pro</code> file is where you can add custom
-ProGuard rules. By default, this file is located at the root of the module
-(next to the <code>build.gradle</code> file).</li>
-</ul>
-
-<p>To add more ProGuard rules that are specific to each build variant, add
-another <code>proguardFiles</code> property in the corresponding
-<code>productFlavor</code> block. For example, the following Gradle file adds
-<code>flavor2-rules.pro</code> to the <code>flavor2</code> product flavor. Now
-<code>flavor2</code> uses all three ProGuard rules because those from the
-<code>release</code> block are also applied.</p>
-
-<pre class="no-pretty-print">
-android {
- ...
- buildTypes {
- release {
- minifyEnabled true
- proguardFiles getDefaultProguardFile('proguard-android.txt'),
- 'proguard-rules.pro'</span>
- }
- }
- productFlavors {
- flavor1 {
- }
- flavor2 {
- proguardFile 'flavor2-rules.pro'
- }
- }
-}
-</pre>
-
-<p>With each build, ProGuard outputs the following files:</p>
-<dl>
-<dt><code>dump.txt</code></dt>
-<dd>Describes the internal structure of all the class files in the APK.</dd>
-
-<dt><code>mapping.txt</code></dt>
-<dd>Provides a translation between the original and obfuscated class, method, and
-field names.</dd>
-
-<dt><code>seeds.txt</code></dt>
-<dd>Lists the classes and members that were not obfuscated.</dd>
-
-<dt><code>usage.txt</code></dt>
-<dd>Lists the code that was removed from the APK.</dd>
-</dl>
-
-<p>These files are saved at
-<code><module-name>/build/outputs/mapping/release/</code>.</p>
-
-
-<h3 id="keep-code">Customize which code to keep</h3>
-
-<p>For some situations, the default ProGuard configuration file
-(<code>proguard-android.txt</code>) is sufficient and ProGuard removes all—and
-only—the unused code. However, many situations are difficult for ProGuard to
-analyze correctly and it might remove code your app actually needs. Some
-examples of when it might incorrectly remove code include:</p>
-
-<ul>
-<li>When your app references a class only from the
-<code>AndroidManifest.xml</code> file</li>
-<li>When your app calls a method from the Java Native Interface (JNI)</li>
-<li>When your app manipulates code at runtime (such as with reflection or
-introspection)</li>
-</ul>
-
-<p>Testing your app should reveal any errors caused by inappropriately removed
-code, but you can also inspect what code was removed by reviewing the
-<code>usage.txt</code> output file saved in
-<code><module-name>/build/outputs/mapping/release/</code>.</p>
-
-<p>To fix errors and force ProGuard to keep certain code, add a <code><a
-href="https://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/usage.html"
->-keep</a></code> line in the ProGuard configuration file. For example:</p>
-
-<pre>
--keep public class MyClass
-</pre>
-
-<p>Alternatively, you can add the <code><a href=
-"{@docRoot}reference/android/support/annotation/Keep.html">@Keep</a></code>
-annotation to the code you want to keep. Adding <code>@Keep</code> on a class
-keeps the entire class as-is. Adding it on a method or field will keep the
-method/field (and it's name) as well as the class name intact. Note that this
-annotation is available only when using the <a href=
-"{@docRoot}tools/support-library/features.html#annotations">Annotations Support
-Library</a>.</p>
-
-
-<p>There are many considerations you should make when using the
-<code>-keep</code> option; for more information about customizing your
-configuration file, 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>. 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 outlines other common problems you might encounter
-when your code gets stripped away.</p>
-
-
-<h3 id="decode-stack-trace">Decode an obfuscated stack trace</h3>
-
-<p>After ProGuard shrinks your code, reading a stack trace is difficult (if not
-impossible) because the method names are obfuscated. Fortunately, ProGuard
-creates a <code>mapping.txt</code> file each time it runs, which shows the
-original class, method, and field names mapped to the obfuscated names.
-ProGuard saves the file in the app
-<code><module-name>/build/outputs/mapping/release/</code> directory.</p>
-
-
-<p>Be aware that the <code>mapping.txt</code> file is overwritten every time
-you create a release build with ProGuard, so you must carefully save a copy
-each time you publish a new release. By retaining a copy of the
-<code>mapping.txt</code> file for each release build, you'll be able to debug a
-problem if a user submits an obfuscated stack trace from an older version of
-your app.</p>
-
-<p>When publishing your app on Google Play, you can upload the
-<code>mapping.txt</code> file for each version of your APK. Then Google Play
-will deobfuscate incoming stack traces from user-reported issues so you can
-review them in the Google Play Developer Console. For more information, see the
-Help Center article about how to <a href=
-"https://support.google.com/googleplay/android-developer/answer/6295281">deobfuscate
-crash stack traces</a>.</p>
-
-<p>To convert an obfuscated stack trace to a readable one yourself, use the
-<code>retrace</code> script (<code>retrace.bat</code> on Windows;
-<code>retrace.sh</code> on Mac/Linux). It is located in the
-<code><sdk-root>/tools/proguard/</code> directory. The script takes the
-<code>mapping.txt</code> file and your stack trace, producing a new, readable
-stack trace. The syntax for using the retrace tool is:</p>
-
-<pre class="no-pretty-print">
-retrace.bat|retrace.sh [-verbose] mapping.txt [<stacktrace_file>]
-</pre>
-
-<p>For example:</p>
-
-<pre class="no-pretty-print">
-retrace.bat -verbose mapping.txt obfuscated_trace.txt
-</pre>
-
-<p>If you do not specify the stack trace file, the retrace tool reads from
-standard input.</p>
-
-<h2 id="shrink-resources">Shrink Your Resources</h2>
-
-<p>Resource shrinking works only in conjunction with code shrinking. After the
-code shrinker removes all unused code, the resource shrinker can identify which
-resources the app still uses. This is especially true when you add code
-libraries that include resources—you must remove unused library code so the
-library resources become unreferenced and, thus, removable by the resource
-shrinker.</p>
-
-<p>To enable resource shrinking, set the <code>shrinkResources</code> property
-to <code>true</code> in your <code>build.gradle</code> file (alongside
-<code>minifyEnabled</code> for code shrinking). For example:</p>
-
-<pre class="no-pretty-print">
-android {
- ...
- buildTypes {
- release {
- shrinkResources true
- minifyEnabled true
- proguardFiles getDefaultProguardFile('proguard-android.txt'),
- 'proguard-rules.pro'
- }
- }
-}
-</pre>
-
-<p>If you haven't already built your app using <code>minifyEnabled</code> for
-code shrinking, then try that before enabling <code>shrinkResources</code>,
-because you might need to edit your <code>proguard-rules.pro</code> file to
-keep classes or methods that are created or invoked dynamically before you
-start removing resources.</p>
-
-<p class="note"><strong>Note</strong>: The resource shrinker currently does not
-remove resources defined in a <code>values/</code> folder (such as strings,
-dimensions, styles, and colors). This is because the Android Asset Packaging
-Tool (AAPT) does not allow the Gradle Plugin to specify predefined versions for
-resources. For details, see <a href=
-"https://code.google.com/p/android/issues/detail?id=70869">issue 70869</a>.</p>
-
-
-<h3 id="keep-resources">Customize which resources to keep</h3>
-
-<p>If there are specific resources you wish to keep or discard, create an XML
-file in your project with a <code><resources></code> tag and specify each
-resource to keep in the <code>tools:keep</code> attribute and each resource to
-discard in the <code>tools:discard</code> attribute. Both attributes accept a
-comma-separated list of resource names. You can use the asterisk character as a
-wild card.</p>
-
-<p>For example:</p>
-
-<pre>
-<?xml version=1.0" encoding="utf-8"?>
-<resources xmlns:tools="http://schemas.android.com/tools"
- tools:keep="@layout/l_used*_c,@layout/l_used_a,@layout/l_used_b*"
- tools:discard="@layout/unused2" />
-</pre>
-
-<p>Save this file in your project resources, for example, at
-<code>res/raw/keep.xml</code>. The build does not package this file into your
-APK.</p>
-
-<p>Specifying which resources to discard might seem silly when you could
-instead delete them, but this can be useful when using build variants. For
-example, you might put all your resources into the common project directory,
-then create a different <code>keep.xml</code> file for each build variant when
-you know that a given resource appears to be used in code (and therefore not
-removed by the shrinker) but you know it actually won't be used for the given
-build variant.</p>
-
-<h3 id="strict-reference-checks">Enable strict reference checks</h3>
-
-<p>Normally, the resource shrinker can accurately determine whether a resource
-is used. However, if your code makes a call to {@link
-android.content.res.Resources#getIdentifier(String,String,String)
-Resources.getIdentifier()} (or if any of your libraries do that—the <a href=
-"{@docRoot}tools/support-library/features.html#v7-appcompat">AppCompat</a>
-library does), that means your code is looking up resource names based on
-dynamically-generated strings. When you do this, the resource shrinker behaves
-defensively by default and marks all resources with a matching name format as
-potentially used and unavailable for removal.</p>
-
-<p>For example, the following code causes all resources with the
-<code>img_</code> prefix to be marked as used.</p>
-
-<pre>
-String name = String.format("img_%1d", angle + 1);
-res = getResources().getIdentifier(name, "drawable", getPackageName());
-</pre>
-
-<p>The resource shrinker also looks through all the string constants in your
-code, as well as various <code>res/raw/</code> resources, looking for resource
-URLs in a format similar to
-<code>file:///android_res/drawable//ic_plus_anim_016.png</code>. If it finds
-strings like this or others that look like they could be used to construct URLs
-like this, it doesn't remove them.</p>
-
-<p>These are examples of the safe shrinking mode that is enabled by default.
-You can, however, turn off this "better safe than sorry" handling, and specify
-that the resource shrinker keep only resources that it's certain are used. To
-do this, set <code>shrinkMode</code> to <code>strict</code> in the
-<code>keep.xml</code> file, as follows:</p>
-
-<pre>
-<?xml version="1.0" encoding="utf-8"?>
-<resources xmlns:tools="http://schemas.android.com/tools"
- tools:shrinkMode="strict" />
-</pre>
-
-<p>If you do enable strict shrinking mode and your code also references
-resources with dynamically-generated strings, as shown above, then you must
-manually keep those resources using the <code>tools:keep</code> attribute.</p>
-
-<h3 id="unused-alt-resources">Remove unused alternative resources</h3>
-
-<p>The Gradle resource shrinker removes only resources that are not referenced
-by your app code, which means it will not remove <a href=
-"{@docRoot}guide/topics/resources/providing-resources.html#AlternativeResources">
-alternative resources</a> for different device configurations. If necessary,
-you can use the Android Gradle plugin's <code>resConfigs</code> property to
-remove alternative resource files that your app does not need.</p>
-
-<p>For example, if you are using a library that includes language resources
-(such as AppCompat or Google Play Services), then your APK includes all
-translated language strings for the messages in those libraries whether the
-rest of your app is translated to the same languages or not. If you'd like to
-keep only the languages that your app officially supports, you can specify
-those languages using the <code>resConfig</code> property. Any resources for
-languages not specified are removed.</p>
-
-<p>The following snippet shows how to limit your language resources to just
-English and French:</p>
-
-<pre class="no-pretty-print">
-android {
- defaultConfig {
- ...
- resConfigs "en", "fr"
- }
-}
-</pre>
-
-<p>To customize which screen density or ABI resources to include in your APK,
-instead use <a href=
-"http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits">APK
-splits</a> to build different APKs for different devices.</p>
-
-<h3 id="merge-resources">Merge duplicate resources</h3>
-
-<p>By default, Gradle also merges identically named resources, such as
-drawables with the same name that might be in different resource folders. This
-behavior is not controlled by the <code>shrinkResources</code> property and
-cannot be disabled, because it is necessary to avoid errors when multiple
-resources match the name your code is looking up.</p>
-
-<p>Resource merging occurs only when two or more files share an identical
-resource name, type, and qualifier. Gradle selects which file it considers to
-be the best choice among the duplicates (based on a priority order described
-below) and passes only that one resource to the AAPT for distribution in the
-APK file.</p>
-
-<p>Gradle looks for duplicate resources in the following locations:</p>
-
-<ul>
-<li>The main resources, associated with the main source set, generally
-located in <code>src/main/res/</code>.</li>
-<li>The variant overlays, from the build type and build flavors.</li>
-<li>The library project dependencies.</li>
-</ul>
-
-<p>Gradle merges duplicate resources in the following cascading priority order:</p>
-
-<p>Dependencies → Main → Build flavor → Build type</p>
-
-<p>For example, if a duplicate resource appears in both your main resources and
-a build flavor, Gradle selects the one in the build flavor.</p>
-
-<p>If identical resources appear in the same source set, Gradle cannot merge
-them and emits a resource merge error. This can happen if you define multiple
-source sets in the <code>sourceSet</code> property of your
-<code>build.gradle</code> file—for example if both <code>src/main/res/</code>
-and <code>src/main/res2/</code> contain identical resources.</p>
-
-<h3 id="troubleshoot-resource-shrink">Troubleshoot resource shrinking</h3>
-
-<p>When you shrink resources, the Gradle Console shows a summary of the
-resources that it removed from the app package. For example:</p>
-
-<pre class="no-pretty-print">
-:android:shrinkDebugResources
-Removed unused resources: Binary resource data reduced from 2570KB to 1711KB: Removed 33%
-:android:validateDebugSigning
-</pre>
-
-<p>Gradle also creates a diagnostic file named <code>resources.txt</code> in
-<code><module-name>/build/outputs/mapping/release/</code> (the same
-folder as ProGuard's output files). This file includes details such as which
-resources reference other resources and which resources are used or
-removed.</p>
-
-<p>For example, to find out why <code>@drawable/ic_plus_anim_016</code> is
-still in your APK, open the <code>resources.txt</code> file and search for that
-file name. You might find that it's referenced from another resource, as
-follows:</p>
-
-<pre class="no-pretty-print">
-16:25:48.005 [QUIET] [system.out] @drawable/add_schedule_fab_icon_anim : reachable=true
-16:25:48.009 [QUIET] [system.out] @drawable/ic_plus_anim_016
-</pre>
-
-<p>You now need to know why <code>@drawable/add_schedule_fab_icon_anim</code>
-is reachable—and if you search upwards you'll find that resource is listed
-under "The root reachable resources are:". This means there is a code reference
-to <code>add_schedule_fab_icon_anim</code> (that is, its R.drawable ID was
-found in the reachable code).</p>
-
-<p>If you are not using strict checking, resource IDs can be marked as reachable
-if there are string constants that look like they might be used to construct
-resource names for dynamically loaded resources. In that case, if you search
-the build output for the resource name, you might find a message like this:</p>
-
-<pre class="no-pretty-print">
-10:32:50.590 [QUIET] [system.out] Marking drawable:ic_plus_anim_016:2130837506
- used because it format-string matches string pool constant ic_plus_anim_%1$d.
-</pre>
-
-<p>If you see one of these strings and you are certain that the string is not
-being used to load the given resource dynamically, you can use the
-<code>tools:discard</code> attribute to inform the build system to remove it,
-as described in the section about how to <a href="#keep-resources"
->customize which resources to keep</a>.</p>
+++ /dev/null
-page.title=Project Structure Management
-parent.title=Tools
-parent.link=index.html
-page.tags="android studio,project structure,target sdk,minimum sdk"
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#dev-svc">Developer Services</a></li>
- <li><a href="#modules">Modules</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>
- You can use the <strong>Android Studio File > Project Structure</strong> dialog box to
- change configuration settings for your Android Studio project. This dialog
- box is useful if you need to change some of the settings you chose when you
- created the project.
-</p>
-
-<p>
- The Project Structure dialog box contains the following sections:
-</p>
-
-<ul>
- <li>
- <strong>SDK Location:</strong> Sets the location of the JDK, Android SDK,
- and Android NDK that the project uses.
- </li>
-
- <li>
- <strong>Project:</strong> Sets version information for <a
- href="{@docRoot}tools/building/plugin-for-gradle.html">Gradle</a> and for
- the <a href="{@docRoot}tools/building/plugin-for-gradle.html">Android plugin
- for Gradle</a>.
- </li>
-
- <li>
- <strong>Developer Services:</strong> Contains settings for Android Studio
- add-in components from Google or third parties.
- </li>
-
- <li>
- <strong>Modules:</strong> Used to set or change various module-specific
- build settings, including the target and minimum SDK, the app signature,
- and library dependencies. Most importantly, this is where you change
- the settings for your project's <em>app</em> module.
- </li>
-</ul>
-
-<p>
- The following two sections provide information on the <a href=
- "#dev-svc">Developer Services</a> and <a href="#modules">Modules</a>
- sections.
-</p>
-
-<h2 id="dev-svc">
- Developer Services
-</h2>
-
-<p>
- The <em>Developer Services</em> section of the <em>Project Structure</em>
- dialog box contains configuration pages
- for several services that you can be use with your app. This section
- contains the following pages:
-</p>
-
-<ul>
- <li>
- <strong>AdMob:</strong> Allows you to turn on Google's <a href=
- "https://developers.google.com/admob/" class="external-link">AdMob</a>
- component, which helps you understand your users and show them tailored
- advertisements.
- </li>
-
- <li>
- <strong>Analytics:</strong> Allows you to turn on <a href=
- "https://developers.google.com/analytics/" class="external-link">Google
- Analytics</a>, which helps you measure user interactions with your app
- across various devices and environments.
- </li>
-
- <li>
- <strong>Authentication:</strong> Allows users to use <a href=
- "https://developers.google.com/identity/sign-in/android/" class=
- "external-link">Google Sign-In</a> to sign in to your app with their Google
- accounts.
- </li>
-
- <li>
- <strong>Cloud:</strong> Allows you to turn on <a href=
- "https://www.firebase.com/" class="external-link">Firebase</a> cloud-based
- services for your app.
- </li>
-
- <li>
- <strong>Notifications:</strong> Allows you to use <a href=
- "https://developers.google.com/cloud-messaging/" class=
- "external-link">Google Cloud Messaging</a> to communicate between your app
- and your server.
- </li>
-</ul>
-
-<p>
- Turning on any of these services may cause Android Studio to add necessary
- dependencies and permissions to your app. Each configuration page lists these
- and other actions that Android Studio takes if you enable the associated service.
-</p>
-
-<h2 id="modules">
- Modules
-</h2>
-
-<p>
- The <em>Modules</em> settings section lets you change configuration
- options for each of your project's modules. This section contains one page
- for each module in your app. In many cases, the project has just a single
- module, named <em>app</em>. However, if your project targets multiple form
- factors, it might have several modules. For example, if your project contains
- both a tablet app and a wearable app, it might have two modules, named
- <em>mobile</em> and <em>wear</em>. For more information about project
- modules, see <a href=
- "{@docRoot}tools/projects/index.html#ApplicationModules">Android Application
- Modules</a>.
-</p>
-
-<p>
- Each module's settings page is divided into the following panes:
-</p>
-
-<ul>
- <li>
- <strong>Properties:</strong> Specifies the versions of the SDK and build
- tools to use to compile the module.
- </li>
-
- <li>
- <strong>Signing:</strong> Specifies the certificate to use to
- <a href="{@docRoot}tools/publishing/app-signing.html#sign-auto">sign your
- APK</a>.
- </li>
-
- <li>
- <strong>Flavors:</strong> Lets you create multiple build <em>flavors</em>, where
- each flavor specifies a set of configuration settings, such as the
- module's minimum and target SDK version, and the
- <a href="{@docRoot}tools/publishing/versioning.html">version code and
- version name</a>. For example, you might define one flavor that has a
- minimum SDK of 15 and a target SDK of 21, and another flavor that has a
- minimum SDK of 19 and a target SDK of 23.
- </li>
-
- <li>
- <strong>Build Types:</strong> Lets you create and modify build
- configurations, as described in <a href=
- "{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle
- Builds</a>. By default, every module has <em>debug</em> and
- <em>release</em> build types, but you can define more as needed.
- </li>
-
- <li>
- <strong>Dependencies:</strong> Lists the library, file, and module
- dependencies for this module. You can add, modify, and delete dependencies
- from this pane. For more information about module dependencies, see
- <a href="{@docRoot}tools/building/configuring-gradle.html#declareDeps">Declare
- dependencies</a> in <a href=
- "{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle
- Builds</a>.
- </li>
-</ul>
+++ /dev/null
-page.title=SDK Manager
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#updatecheck">Enabling Automatic Update Checking</a></li>
- <li><a href="#run">Running the SDK Manager</a></li>
- <li><a href="#Recommended">Recommended Packages</a></li>
- <li><a href="#AddingSites">Adding New Sites</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>The Android SDK Manager separates the SDK tools, platforms, and other components into packages
-for easy access and management. You can also customize which sites the SDK Manager checks for new
-or updated SDK packages and add-on tools. For example, you can configure the SDK Manager
-to automatically check for updates and notify you when updates are available.
-When you receive such a notification, you can then quickly decide whether to download the changes. </p>
-
-<h2 id="updatecheck">Enabling Automatic Update Checking</h2>
-<p>To enable automatic update checking: </p>
-<ol>
- <li>Choose <strong>File</strong> > <strong>Settings</strong>
- > <strong>Appearance & Behavior</strong> > <strong>System Settings</strong>
- > <strong>Updates</strong>. </li>
- <li>Select the <strong>Automatically check updates for</strong> checkbox and select an
- <ahref="{@docRoot}tools/studio/studio-config.html#update-channel">update channel</a>.</li>
-
-
- <li>Click <strong>OK</strong> or <strong>Apply</strong> to enable the update checking. </li>
-</ol>
-
-<h2 id="run">Running the SDK Manager</h2>
-<p>You can launch the SDK Manager in one of the following ways:</p>
-<ul>
- <li>From the Android Studio <strong>File</strong> menu: <strong>File</strong> >
- <strong>Settings</strong> > <strong>Appearance & Behavior</strong> >
- <strong>System Settings</strong> > <strong>Android SDK</strong>.</li>
- <li>From the Android Studio <strong>Tools</strong> menu: <strong>Tools</strong> >
- <strong>Android</strong> > <strong>SDK Manager</strong>.</li>
- <li>From the SDK Manager icon
- (<img src="{@docRoot}images/tools/sdk-manager-studio.png" style="vertical-align:sub;margin:0;height:17px" alt="" />)
- in the menu bar. </li>
-</ul>
-<p>The SDK Manager appears.</p>
-<img src="{@docRoot}images/tools/studio-sdk-manager-packages.png" alt="" />
-<p class="img-caption"><strong>Figure 1.</strong> The Android SDK Manager shows the
-SDK platforms and packages that are available and installed along with the SDK update sites.</p>
-
-<p class="note"><strong>Tip:</strong> The standalone SDK Manager is still available from the
-command line, but we recommend it for use with standalone SDK installations only.</p>
-
-<p>Click the checkbox next to
-each additional SDK platform and tool that you want to install. Clear the
-checkbox to uninstall an SDK platform or tool. Click <strong>Apply</strong> or <strong>OK</strong>
-to update the packages and tools. </p>
-
-<p class="note"><strong>Tip:</strong> When an update is available for an installed
-package, a hyphen (-) appears in the checkbox next to the package. A download icon
-(<img src="{@docRoot}images/tools/studio-sdk-dwnld-icon.png" style="vertical-align:sub;margin:0;height:17px" alt="" />)
-also appears next
-to the checkbox to indicate the pending update. An update icon
-(<img src="{@docRoot}images/tools/studio-sdk-removal-icon.png" style="vertical-align:sub;margin:0;height:17px" alt="" />) appears next to the checkbox to
-indicate pending removals.</p>
-
-<p>Click the <strong>SDK Update Sites</strong> tab to manage which SDK sites Android Studio checks for
-tool and add-on updates. </p>
-
-
-
-<p>There are several different packages available for the Android SDK. The following section describes
-most of the available packages and where they're located in your SDK directory
-after you download them.</p>
-
-
-
-<h2 id="Recommended">Recommended Packages</h2>
-
-<p>Here's an outline of the packages required and those we recommend you use:
-</p>
-
-<dl>
- <dt>SDK Tools</dt>
- <dd><strong>Required.</strong> Your new SDK installation installs the latest version. Be sure
- to respond to the Android Studio update prompts to keep your SDK Tools up-to-date.</dd>
- <dt>SDK Platform-tools</dt>
- <dd><strong>Required.</strong> Your new SDK installation installs the latest stable version.
- Be sure to respond to the Android Studio update prompts to keep your SDK Platform-tools
- up-to-date.</dd>
- <dt>SDK Platform</dt>
- <dd><strong>Required.</strong> At least one platform is required in your
-environment to be able to compile your application. To provide the best user experience
-on the latest devices, we recommend that you use the latest platform version as your build target.
-You'll still be able to run your app on older versions, but you must build against the latest
-version in order to use new features when running on devices with the latest version of Android.
- </dd>
- <dt>System Image</dt>
- <dd>Recommended. Although you might have one or more Android-powered devices on which to test
- your app, it's unlikely you have a device for every version of Android your app supports. It's
-a good practice to download system images for all versions of Android that your
-app supports and then test
-your app against these Android versions by using the
-<a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a>. Click <strong>Show Package Details</strong> to display the available
-system images for each available platform. You can also download system images when creating
-Android Virtual Devices (AVDs) in the
-<a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a>. </dd>
-
-
- <dt>Android Support Repository</dt>
- <dd>Recommended. Includes a local Maven repository for the Android Data
- Binding Library, Android Testing Support Library, and Android Support
- Libraries. The Android Support Libraries provide an extended set of
- APIs that are compatible with most versions of Android. They're required for
- products such as <a href="{@docRoot}wear/index.html">Android Wear</a>, <a
- href="{@docRoot}tv/index.html">Android TV</a>, and <a
- href="https://developers.google.com/cast/">Google Cast</a>. For more
- information about each of the libraries in the Android Support Repository,
- see <a href="{@docRoot}tools/data-binding/guide.html">Data Binding Guide</a>,
- <a href="{@docRoot}tools/testing-support-library/index.html">Testing Support
- Library</a>, and <a href="{@docRoot}tools/support-library/index.html">Support
- Library</a>.</dd>
-
- <dt>Google Play services</dt>
- <dd>Recommended. Includes the Google Play services client library, which
- provides a variety of features and services for your
- apps, such as <a
- href="https://developers.google.com/identity/sign-in/android/">Google
- sign-in</a>, <a
- href="https://developers.google.com/maps/documentation/android-api/">Google
- Maps</a>, <a href="https://developers.google.com/games/services/">Games
- achievements and leaderboards</a>, and much more.</dd>
-
- <dt>Google Repository</dt>
- <dd>Recommended. Includes local Maven repository for Google libraries.</dd>
-
-
-<p class="note"><strong>Tip:</strong> For easy access to the SDK tools from a command line, add the
-location of the SDK <code>tools/</code> and
-<code>platform-tools</code> to your <code>PATH</code> environment variable.</p>
-
-
-<p>The previous list is not comprehensive and you can <a
-href="#AddingSites">add new sites</a> to download additional packages from third parties.</p>
-
-<p>In some cases, an SDK package may require a specific minimum revision of
-another package or SDK tool. The SDK Manager automatically notifies you of any
-dependencies and downloads the required packages or tools.
-In addition, development tools notify you if there are dependencies that you need to
-address. </p>
-
-
-
-<h2 id="AddingSites">Adding New Sites</h2>
-
-<p>The <strong>SDK Update Sites</strong> tab displays the sites that Android Studio checks for Android SDK
-and third-party updates. You can add other sites that host their own Android SDK add-ons, and then
-download the SDK add-ons from those sites.</p>
-
-<p>For example, a mobile carrier or device manufacturer might offer additional
-API libraries that are supported by their own Android-powered devices.
-To develop using their libraries, you must install their Android SDK add-on, if it's not already
-available as a third-party add-on.</p>
-
-<p>If a carrier or device manufacturer has hosted an SDK add-on repository file
-on their website, follow these steps to add their site to the Android SDK Manager:</p>
-
-<ol>
- <li>Click the <strong>SDK Update Sites</strong> tab.</li>
- <li>Click <strong>Add</strong> <img src="{@docRoot}images/tools/sdk-iadd.png" style="vertical-align:sub;margin:0;height:17px" alt="" />. </li>
- <li>Type the name and URL of the
- add-on site, and then cick <strong>OK</strong>.</li>
- <li>Make sure the checkbox is selected in the <strong>Enabled</strong> column.</li>
-
-<p>Any SDK packages available from the site appear in the <strong>SDK Platforms</strong> or
-<strong>SDK Tools</strong> tabs.</p>
-</ol>
-
-
+++ /dev/null
-page.title=ADB Shell Commands
-parent.title=Tools
-parent.link=index.html
-page.tags=shell,adb,am,pm,screenrecord,screencap
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#shellcommands">Issuing Shell Commands</a>
- <li><a href="#am">Using activity manager (am)</a></li>
- <li><a href="#pm">Using package manager (pm)</a></li>
- <li><a href="#screencap">Taking a device screenshot</a></li>
- <li><a href="#screenrecord">Recording a device screen</a></li>
- <li><a href="#othershellcommands">Other shell commands</a></li>
- </li>
-</ol>
-
-</div>
-</div>
-
-<p>The <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a> (adb) provides a Unix shell
-that you can use to run a variety of commands on an emulator or connected device. The command
-binaries are stored in the file system of the emulator or device, at <code>/system/bin/...</code>
-</p>
-
-<h2 id="shellcommands">Issuing Shell Commands</h2>
-
-<p>You can use the <code>shell</code> command to issue commands, with or without entering
-the adb remote shell on the emulator/device. To issue a single command without entering a
-remote shell, use the <code>shell</code> command like this: </p>
-
- <pre class="no-pretty-print">adb [-d|-e|-s <serialNumber>] shell <shell_command></pre>
-
-<p>Or enter a remote shell on an emulator/device like this:</p>
-
- <pre class="no-pretty-print">adb [-d|-e|-s <serialNumber>] shell</pre>
-
-<p>When you are ready to exit the remote shell, press CTRL+D or type
-<code>exit</code>. </p>
-
-
-
-
-
-<h2 id="am">Using activity manager (am)</h2>
-
-<p>Within an adb shell, you can issue commands with the activity manager ({@code am}) tool to
-perform various system actions, such as start an activity, force-stop a process,
-broadcast an intent, modify the device screen properties, and more. While in a shell,
-the syntax is:</p>
-<pre class="no-pretty-print">
-am <command>
-</pre>
-
-<p>You can also issue an activity manager command directly from adb
-without entering a remote shell. For example:</p>
-<pre class="no-pretty-print">
-adb shell am start -a android.intent.action.VIEW
-</pre>
-
-
-<p class="table-caption"><strong>Table 2.</strong> Available activity manager commands</p>
-<table>
-<tr>
- <th>Command</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td><code>
-start [options] <INTENT>
-</code></td>
-<td>Start an {@link android.app.Activity} specified by {@code <INTENT>}. <p>See the
-<a href="#IntentSpec">Specification for <INTENT> arguments</a>.
-<p>Options are:
-<ul>
- <li>{@code -D}: Enable debugging.
- <li>{@code -W}: Wait for launch to complete.
- <li>{@code --start-profiler <FILE>}: Start profiler and send results to {@code <FILE>}.
- <li>{@code -P <FILE>}: Like <code>--start-profiler</code>,
- but profiling stops when the app goes idle.
- <li>{@code -R}: Repeat the activity launch {@code <COUNT>} times. Prior to each repeat,
- the top activity will be finished.
- <li>{@code -S}: Force stop the target app before starting the activity.
- <li>{@code --opengl-trace}: Enable tracing of OpenGL functions.
- <li>{@code --user <USER_ID> | current}: Specify which user to run as; if not
- specified, then run as the current user.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-startservice [options] <INTENT>
-</code></td>
-<td>Start the {@link android.app.Service} specified by {@code <INTENT>}. <p>See the
-<a href="#IntentSpec">Specification for <INTENT> arguments</a>.
-<p>Options are:
-<ul>
- <li>{@code --user <USER_ID> | current}: Specify which user to run as; if not
- specified, then run as the current user.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-force-stop <PACKAGE>
-</code></td>
-<td>Force stop everything associated with {@code <PACKAGE>} (the app's package name).
-</td>
-</tr>
-
-<tr>
-<td><code>
-kill [options] <PACKAGE>
-</code></td>
-<td> Kill all processes associated with {@code <PACKAGE>}
- (the app's package name). This command kills only
- processes that are safe to kill and that will not impact the user
- experience.
- <p>Options are:
- <ul>
- <li>{@code --user <USER_ID> | all | current}: Specify user whose processes to kill;
- all users if not specified.
- </ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-kill-all
-</code></td>
-<td>Kill all background processes.
-</td>
-</tr>
-
-<tr>
-<td><code>
-broadcast [options] <INTENT>
-</code></td>
-<td>Issue a broadcast intent. <p>See the
-<a href="#IntentSpec">Specification for <INTENT> arguments</a>.
-<p>Options are:
-<ul>
- <li>{@code [--user <USER_ID> | all | current]}: Specify which user to send to; if not
- specified then send to all users.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-instrument [options] <COMPONENT>
-</code></td>
-<td>Start monitoring with an {@link android.app.Instrumentation} instance.
- Typically the target {@code <COMPONENT>}
- is the form {@code <TEST_PACKAGE>/<RUNNER_CLASS>}. <p>Options are:
-<ul>
- <li>{@code -r}: Print raw results (otherwise decode
- {@code <REPORT_KEY_STREAMRESULT>}). Use with
- {@code [-e perf true]} to generate raw output for performance measurements.
-
- <li>{@code -e <NAME> <VALUE>}: Set argument {@code <NAME>} to {@code <VALUE>}.
- For test runners a common form is {@code
- -e <testrunner_flag> <value>[,<value>...]}.
-
- <li>{@code -p <FILE>}: Write profiling data to {@code <FILE>}.
-
- <li>{@code -w}: Wait for instrumentation to finish before returning. Required for
- test runners.
-
- <li>{@code --no-window-animation}: Turn off window animations while running.
- <li>{@code --user <USER_ID> | current}: Specify which user instrumentation runs in;
- current user if not specified.
-</ul>
-
-</td>
-</tr>
-
-<tr>
-<td><code>
-profile start <PROCESS> <FILE>
-</code></td>
-<td>Start profiler on {@code <PROCESS>}, write results to {@code <FILE>}.
-</td>
-</tr>
-
-<tr>
-<td><code>
-profile stop <PROCESS>
-</code></td>
-<td>Stop profiler on {@code <PROCESS>}.
-</td>
-</tr>
-
-<tr>
-<td style="white-space:nowrap"><code>
-dumpheap [options] <PROCESS> <FILE>
-</code></td>
-<td>Dump the heap of {@code <PROCESS>}, write to {@code <FILE>}. <p>Options are:
-<ul>
- <li>{@code --user [<USER_ID>|current]}: When supplying a process name,
- specify user of process to dump; uses current user if not specified.
- <li>{@code -n}: Dump native heap instead of managed heap.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-set-debug-app [options] <PACKAGE>
-</code></td>
-<td>Set application {@code <PACKAGE>} to debug. <p>Options are:
-<ul>
- <li>{@code -w}: Wait for debugger when application starts.
- <li>{@code --persistent}: Retain this value.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-clear-debug-app
-</code></td>
-<td>Clear the package previous set for debugging with {@code set-debug-app}.
-</td>
-</tr>
-
-<tr>
-<td><code>
-monitor [options]
-</code></td>
-<td>Start monitoring for crashes or ANRs. <p>Options are:
-<ul>
- <li>{@code --gdb}: Start gdbserv on the given port at crash/ANR.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-screen-compat [on|off] <PACKAGE>
-</code></td>
-<td>Control <a href="{@docRoot}guide/practices/screen-compat-mode.html">screen
-compatibility</a> mode of {@code <PACKAGE>}.</p>
-</td>
-</tr>
-
-<tr>
-<td><code>
-display-size [reset|<WxH>]
-</code></td>
-<td>Override emulator/device display size.
-This command is helpful for testing your app across different screen sizes by mimicking a small
-screen resolution using a device with a large screen, and vice versa.
-<p>Example:<br><code>am display-size 1280x800</code>
-</td>
-</tr>
-
-<tr>
-<td><code>
-display-density <dpi>
-</code></td>
-<td>Override emulator/device display density.
-This command is helpful for testing your app across different screen densities on high-density
-screen environment using a low density screen, and vice versa.
-<p>Example:<br><code>am display-density 480</code>
-</td>
-</tr>
-
-<tr>
-<td><code>
-to-uri <INTENT>
-</code></td>
-<td>Print the given intent specification as a URI. <p>See the
-<a href="#IntentSpec">Specification for <INTENT> arguments</a>.
-</td>
-</tr>
-
-<tr>
-<td><code>
-to-intent-uri <INTENT>
-</code></td>
-<td>Print the given intent specification as an {@code intent:} URI. <p>See the
-<a href="#IntentSpec">Specification for <INTENT> arguments</a>.
-</td>
-</tr>
-</table>
-
-
-
-
-
-<h3 id="IntentSpec">
- <a href="" class="expandable" onclick="toggleExpandable(this,'.intents');
-return false">Specification for <INTENT> arguments</a></h3>
-
-<div class="intents" style="display:none">
-
-<p>For activity manager commands that take a {@code <INTENT>} argument, you can
-specify the intent with the following options:</p>
-
-<dl>
- <dt>{@code -a <ACTION>}</dt>
- <dd>Specify the intent action, such as "android.intent.action.VIEW".
- You can declare this only once.
-
- <dt>{@code -d <DATA_URI>}</dt>
- <dd>Specify the intent data URI, such as "content://contacts/people/1".
- You can declare this only once.
-
- <dt>{@code -t <MIME_TYPE>}</dt>
- <dd>Specify the intent MIME type, such as "image/png".
- You can declare this only once.
-
- <dt>{@code -c <CATEGORY>}</dt>
- <dd>Specify an intent category, such as "android.intent.category.APP_CONTACTS".
-
- <dt>{@code -n <COMPONENT>}</dt>
- <dd>Specify the component name with package name prefix to create an explicit intent, such
- as "com.example.app/.ExampleActivity".
-
- <dt>{@code -f <FLAGS>}</dt>
- <dd>Add flags to the intent, as supported by {@link
- android.content.Intent#setFlags setFlags()}.
-
- <dt>{@code --esn <EXTRA_KEY>}</dt>
- <dd>Add a null extra. This option is not supported for URI intents.
-
- <dt>{@code -e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE>}</dt>
- <dd>Add string data as a key-value pair.
-
- <dt>{@code --ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>}</dt>
- <dd>Add boolean data as a key-value pair.
-
- <dt>{@code --ei <EXTRA_KEY> <EXTRA_INT_VALUE>}</dt>
- <dd>Add integer data as a key-value pair.
-
- <dt>{@code --el <EXTRA_KEY> <EXTRA_LONG_VALUE>}</dt>
- <dd>Add long data as a key-value pair.
-
- <dt>{@code --ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE>}</dt>
- <dd>Add float data as a key-value pair.
-
- <dt>{@code --eu <EXTRA_KEY> <EXTRA_URI_VALUE>}</dt>
- <dd>Add URI data as a key-value pair.
-
- <dt>{@code --ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>}</dt>
- <dd>Add a component name, which is converted and passed as
- a {@link android.content.ComponentName} object.
-
- <dt>{@code --eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]}</dt>
- <dd>Add an array of integers.
-
- <dt>{@code --ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]}</dt>
- <dd>Add an array of longs.
-
- <dt>{@code --efa <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE...]}</dt>
- <dd>Add an array of floats.
-
- <dt>{@code --grant-read-uri-permission}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_GRANT_READ_URI_PERMISSION}.
-
- <dt>{@code --grant-write-uri-permission}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_GRANT_WRITE_URI_PERMISSION}.
-
- <dt>{@code --debug-log-resolution}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_DEBUG_LOG_RESOLUTION}.
-
- <dt>{@code --exclude-stopped-packages}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_EXCLUDE_STOPPED_PACKAGES}.
-
- <dt>{@code --include-stopped-packages}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_INCLUDE_STOPPED_PACKAGES}.
-
- <dt>{@code --activity-brought-to-front}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_BROUGHT_TO_FRONT}.
-
- <dt>{@code --activity-clear-top}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_CLEAR_TOP}.
-
- <dt>{@code --activity-clear-when-task-reset}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET}.
-
- <dt>{@code --activity-exclude-from-recents}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS}.
-
- <dt>{@code --activity-launched-from-history}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_LAUNCHED_FROM_HISTORY}.
-
- <dt>{@code --activity-multiple-task}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK}.
-
- <dt>{@code --activity-no-animation}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_NO_ANIMATION}.
-
- <dt>{@code --activity-no-history}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_NO_HISTORY}.
-
- <dt>{@code --activity-no-user-action}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_NO_USER_ACTION}.
-
- <dt>{@code --activity-previous-is-top}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_PREVIOUS_IS_TOP}.
-
- <dt>{@code --activity-reorder-to-front}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_REORDER_TO_FRONT}.
-
- <dt>{@code --activity-reset-task-if-needed}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_RESET_TASK_IF_NEEDED}.
-
- <dt>{@code --activity-single-top}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_SINGLE_TOP}.
-
- <dt>{@code --activity-clear-task}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_CLEAR_TASK}.
-
- <dt>{@code --activity-task-on-home}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_ACTIVITY_TASK_ON_HOME}.
-
- <dt>{@code --receiver-registered-only}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_RECEIVER_REGISTERED_ONLY}.
-
- <dt>{@code --receiver-replace-pending}</dt>
- <dd>Include the flag {@link android.content.Intent#FLAG_RECEIVER_REPLACE_PENDING}.
-
- <dt>{@code --selector}</dt>
- <dd>Requires the use of {@code -d} and {@code -t} options to set the intent data and type.
-
- <dt>{@code <URI> <COMPONENT> <PACKAGE>}</dt>
- <dd>You can directly specify a URI, package name, and component name when not qualified
- by one of the above options. When an argument is unqualified, the tool assumes the argument
- is a URI if it contains a ":" (colon); it assumes the argument is a component name if it
- contains a "/" (forward-slash); otherwise it assumes the argument is a package name.
-
-</dl>
-</div><!-- end 'intents' -->
-<script>
- $(window).hashchange( function(){
- if ((location.hash == "#IntentSpec") && !($("#IntentSpec a").hasClass("expanded"))) {
- $("#IntentSpec a").click();
- }
- });
-</script>
-
-
-
-<h2 id="pm">Using package manager (pm)</h2>
-
-<p>Within an adb shell, you can issue commands with the package manager ({@code pm}) tool to
-perform actions and queries on application packages installed on the device. While in a shell,
-the syntax is:</p>
-<pre class="no-pretty-print">
-pm <command>
-</pre>
-
-<p>You can also issue a package manager command directly from adb
-without entering a remote shell. For example:</p>
-<pre class="no-pretty-print">
-adb shell pm uninstall com.example.MyApp
-</pre>
-
-<p class="table-caption"><strong>Table 3.</strong> Available package manager commands.</p>
-<table>
-<tr>
- <th>Command</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td><code>
-list packages [options] <FILTER>
-</code></td>
-<td>Prints all packages, optionally only
- those whose package name contains the text in {@code <FILTER>}. <p>Options:
-<ul>
- <li>{@code -f}: See their associated file.
- <li>{@code -d}: Filter to only show disabled packages.
- <li>{@code -e}: Filter to only show enabled packages.
- <li>{@code -s}: Filter to only show system packages.
- <li>{@code -3}: Filter to only show third party packages.
- <li>{@code -i}: See the installer for the packages.
- <li>{@code -u}: Also include uninstalled packages.
- <li>{@code --user <USER_ID>}: The user space to query.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-list permission-groups
-</code></td>
-<td>Prints all known permission groups.
-</td>
-</tr>
-
-<tr>
-<td><code>
-list permissions [options] <GROUP>
-</code></td>
-<td>Prints all known permissions, optionally only
- those in {@code <GROUP>}. <p>Options:
-<ul>
- <li>{@code -g}: Organize by group.
- <li>{@code -f}: Print all information.
- <li>{@code -s}: Short summary.
- <li>{@code -d}: Only list dangerous permissions.
- <li>{@code -u}: List only the permissions users will see.
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-list instrumentation
-</code></td>
-<td>List all test packages. <p>Options:
- <ul>
- <li>{@code -f}: List the APK file for the test package.
- <li>{@code <TARGET_PACKAGE>}: List test packages for only this app.
- </ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-list features
-</code></td>
-<td>Prints all features of the system.
-</td>
-</tr>
-
-<tr>
-<td><code>
-list libraries
-</code></td>
-<td>Prints all the libraries supported by the current device.
-</td>
-</tr>
-
-<tr>
-<td><code>
-list users
-</code></td>
-<td>Prints all users on the system.
-</td>
-</tr>
-
-<tr>
-<td><code>
-path <PACKAGE>
-</code></td>
-<td>Print the path to the APK of the given {@code <PACKAGE>}.
-</td>
-</tr>
-
-<tr>
-<td><code>
-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.
- <li>{@code -s}: Install package on the shared mass storage (such as sdcard).
- <li>{@code -f}: Install package on the internal system memory.
- <li>{@code -d}: Allow version code downgrade.
- <li>{@code -g}: Grant all permissions listed in the app manifest.
- </ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-uninstall [options] <PACKAGE>
-</code></td>
-<td>Removes a package from the system. <p>Options:
- <ul>
- <li>{@code -k}: Keep the data and cache directories around after package removal.
- </ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-clear <PACKAGE>
-</code></td>
-<td>Deletes all data associated with a package.
-</td>
-</tr>
-
-<tr>
-<td><code>
-enable <PACKAGE_OR_COMPONENT>
-</code></td>
-<td>Enable the given package or component (written as "package/class").
-</td>
-</tr>
-
-<tr>
-<td><code>
-disable <PACKAGE_OR_COMPONENT>
-</code></td>
-<td>Disable the given package or component (written as "package/class").
-</td>
-</tr>
-
-<tr>
-<td style="white-space:nowrap"><code>
-disable-user [options] <PACKAGE_OR_COMPONENT>
-</code></td>
-<td><p>Options:
- <ul>
- <li>{@code --user <USER_ID>}: The user to disable.
- </ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-grant <PACKAGE_NAME> <PERMISSION>
-</code></td>
-<td>Grant a permission to an app. On devices running Android 6.0 (API level 23)
-and higher, may be any permission declared in the app manifest. On devices
-running Android 5.1 (API level 22) and lower, must be an optional permission defined by the
-app.
-</td>
-</tr>
-
-<tr>
-<td><code>
-revoke <PACKAGE_NAME> <PERMISSION>
-</code></td>
-<td>Revoke a permission from an app. On devices running Android 6.0 (API level
-23) and higher, may be any permission declared in the app manifest. On devices
-running Android 5.1 (API level 22) and lower, must be an optional permission defined by the
-app.
-</td>
-</tr>
-
-<tr>
-<td><code>
-set-install-location <LOCATION>
-</code></td>
-<td>Changes the default install location. Location values:
-<ul>
- <li>{@code 0}: Auto—Let system decide the best location.
- <li>{@code 1}: Internal—install on internal device storage.
- <li>{@code 2}: External—install on external media.
-</ul>
-<p class="note"><strong>Note:</strong> This is only intended for debugging; using this can cause
- applications to break and other undesireable behavior.</p>
-</td>
-</tr>
-
-<tr>
-<td><code>
-get-install-location
-</code></td>
-<td>Returns the current install location. Return values:
-<ul>
- <li>{@code 0 [auto]}: Lets system decide the best location
- <li>{@code 1 [internal]}: Installs on internal device storage
- <li>{@code 2 [external]}: Installs on external media
-</ul>
-</td>
-</tr>
-
-<tr>
-<td><code>
-set-permission-enforced <PERMISSION> [true|false]
-</code></td>
-<td>Specifies whether the given permission should be enforced.
-</td>
-</tr>
-
-<tr>
-<td><code>
-trim-caches <DESIRED_FREE_SPACE>
-</code></td>
-<td>Trim cache files to reach the given free space.
-</td>
-</tr>
-
-<tr>
-<td><code>
-create-user <USER_NAME>
-</code></td>
-<td>Create a new user with the given {@code <USER_NAME>},
- printing the new user identifier of the user.
-</td>
-</tr>
-
-<tr>
-<td><code>
-remove-user <USER_ID>
-</code></td>
-<td>Remove the user with the given {@code <USER_IDENTIFIER>},
- deleting all data associated with that user
-</td>
-</tr>
-
-<tr>
-<td><code>
-get-max-users
-</code></td>
-<td>Prints the maximum number of users supported by the device.
-</td>
-</tr>
-
-</table>
-
-
-<h2 id="screencap">Taking a device screenshot</h2>
-
-<p>The {@code screencap} command is a shell utility for taking a screenshot of a device display.
-While in a shell, the syntax is:
-</p>
-
-<pre class="no-pretty-print">
-screencap <filename>
-</pre>
-
-
-<p>To use the {@code screencap} from the command line, type the following:
-
-<pre>
-$ adb shell screencap /sdcard/screen.png
-</pre>
-
-<p>Here's an example screenshot session, using the adb shell to capture the screenshot and the
-{@code pull} command to download the file from the device:<p>
-
-<pre>
-$ adb shell
-shell@ $ screencap /sdcard/screen.png
-shell@ $ exit
-$ adb pull /sdcard/screen.png
-</pre>
-
-
-<h2 id="screenrecord">Recording a device screen</h2>
-
-<p>The {@code screenrecord} command is a shell utility for recording the display of devices
- running Android 4.4 (API level 19) and higher. The utility records screen activity to an MPEG-4
- file.</p>
-
-<p class="note"><strong>Note:</strong> Audio is not recorded with the video file.</p>
-
-<p>A developer can use this file to create promotional or training videos. While in a shell, the syntax is:</p>
-
-<pre class="no-pretty-print">
-screenrecord [options] <filename>
-</pre>
-
-<p>To use {@code screenrecord} from the command line, type the following:
-
-<pre>
-$ adb shell screenrecord /sdcard/demo.mp4
-</pre>
-
-<p>Stop the screen recording by pressing Ctrl-C, otherwise the recording stops automatically
-at three minutes or the time limit set by {@code --time-limit}.</p>
-
-<p>To begin recording your device screen, run the {@code screenrecord} command to record
-the video. Then, run the {@code pull} command to download the video from the device to the host
-computer. Here's an example recording session:<p>
-
-<pre>
-$ adb shell
-shell@ $ screenrecord --verbose /sdcard/demo.mp4
-(press Ctrl-C to stop)
-shell@ $ exit
-$ adb pull /sdcard/demo.mp4
-</pre>
-
-<p>The {@code screenrecord} utility can record at any supported resolution and bit rate you
- request, while retaining the aspect ratio of the device display. The utility records at the native
- display resolution and orientation by default, with a maximum length of three minutes.</p>
-
-<p>There are some known limitations of the {@code screenrecord} utility that you should be aware
- of when using it:</p>
-
-<ul>
- <li>Some devices may not be able to record at their native display resolution.
- If you encounter problems with screen recording, try using a lower screen resolution.</li>
- <li>Rotation of the screen during recording is not supported. If the screen does rotate during
- recording, some of the screen is cut off in the recording.</li>
-</ul>
-
-
-<p class="table-caption"><strong>Table 4.</strong> {@code screenrecord} options</p>
-
-<table>
- <tr>
- <th>Options</th>
- <th>Description</th>
- </tr>
-
- <tr>
- <td><code>--help</code>
- </td>
- <td>Displays command syntax and options</td>
- </tr>
-
- <tr>
- <td style="white-space:nowrap">
- <code>--size <WIDTHxHEIGHT></code>
- </td>
- <td>Sets the video size: {@code 1280x720}. The default value is the device's native
- display resolution (if supported), 1280x720 if not. For best results, use a size supported
- by your device's Advanced Video Coding (AVC) encoder.</td>
- </tr>
-
- <tr>
- <td><code>--bit-rate <RATE></code></td>
- <td>Sets the video bit rate for the video, in megabits per second. The default value is 4Mbps.
- You can increase the bit rate to improve video quality, but doing so results in larger movie
- files. The following example sets the recording bit rate to 6Mbps:
- <pre>screenrecord --bit-rate 6000000 /sdcard/demo.mp4</pre>
- </td>
- </tr>
-
- <tr>
- <td><code>--time-limit <TIME></code></td>
- <td>Sets the maximum recording time, in seconds. The default and maximum value is 180
- (3 minutes).</td>
- </tr>
-
- <tr>
- <td><code>--rotate</code></td>
- <td>Rotates the output 90 degrees. This feature is experimental.</td>
- </tr>
-
- <tr>
- <td><code>--verbose</code></td>
- <td>Displays log information on the command-line screen. If you do not set this option,
- the utility does not display any information while running.</td>
- </tr>
-
-</table>
-
-
-<h2 id="othershellcommands">Other shell commands</h2>
-
-<p>For a list of all the available shell programs, use the following command:</p>
-
-<pre class="no-pretty-print">adb shell ls /system/bin</pre>
-
-<p>Help is available for most of the commands. </p>
-
-<p>Table 5 lists some of the more common adb shell commands.</p>
-
-<p class="table-caption"><strong>Table 5.</strong> Some other adb shell commands</p>
-<table>
-<tr>
- <th>Shell Command</th>
- <th>Description</th>
- <th>Comments</th>
-</tr>
-
-<tr>
-<td><code>dumpsys</code></td>
-<td>Dumps system data to the screen.</td>
-<td rowspan=4">The <a href="{@docRoot}tools/debugging/ddms.html">Dalvik Debug Monitor Server</a>
-(DDMS) tool offers an integrated debug environment that you may find easier to use.
-</td>
-</tr>
-
-<tr>
-<td><code>dumpstate</code></td>
-<td>Dumps state to a file.</td>
-</tr>
-
-<tr>
-<td><code>logcat [option]... [filter-spec]...</code></td>
-<td>Enables system and app logging and prints output to the screen. </td>
-</tr>
-
-<tr>
-<td><code>dmesg</code></td>
-<td>Prints kernel debugging messages to the screen. </td>
-</tr>
-
-<tr>
-<td><code>start</code></td>
-<td>Starts (restarts) an emulator/device instance.</td>
-<td> </td>
-</tr>
-
-<tr>
-<td><code>stop</code></td>
-<td>Stops execution of an emulator/device instance.</td>
-<td> </td>
-</tr>
-
-</table>
+++ /dev/null
-page.title=sqlite3
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
- <p>From a remote shell to your device or from your host machine, you can use the <a href=
- "http://www.sqlite.org/sqlite.html">sqlite3</a> command-line program to manage SQLite databases
- created by Android applications. The <code>sqlite3</code> tool includes many useful commands,
- such as <code>.dump</code> to print out the contents of a table and <code>.schema</code> to print
- the SQL CREATE statement for an existing table. The tool also gives you the ability to execute
- SQLite commands on the fly.</p>
-
- <p>To use <code>sqlite3</code> from a remote shell:</p>
-
- <ol>
- <li>Enter a remote shell by entering the following command:
- <pre>adb [-d|-e|-s {<serialNumber>}] shell</pre>
- </li>
-
- <li>From a remote shell, start the <code>sqlite3</code> tool by entering the following command:
- <pre>sqlite3</pre>
-
- <p>You can also optionally specify a full path to a database that you want to explore.
- Emulator/device instances store SQLite3 databases in the directory
- <code>/data/data/<package_name>/databases/</code>.</p>
- </li>
-
- <li>Once you invoke <code>sqlite3</code>, you can issue <code>sqlite3</code> commands in the
- shell. To exit and return to the adb remote shell, enter <code>exit</code> or press
- <code>CTRL+D</code>.</li>
- </ol>
-
-
- <p>Here's an example:</p>
- <pre>$ adb -s emulator-5554 shell
-# sqlite3 /data/data/com.example.google.rss.rssexample/databases/rssitems.db
-SQLite version 3.3.12
-Enter ".help" for instructions
-<em>.... enter commands, then quit...</em>
-# sqlite> .exit
-</pre>
-
- <p>To use <code>sqlite3</code> locally, instead of within a shell,
- pull the database file from the device and start {@code sqlite3}:</p>
-
- <ol>
- <li>Copy a database file from your device to your host machine:
- <pre>
-adb pull <database-file-on-device>
-</pre>
- </li>
-
- <li>Start the sqlite3 tool from the <code>/tools</code> directory, specifying the database
- file:
- <pre>
-sqlite3 <database-file-on-host>
-</pre>
- </li>
- </ol>
\ No newline at end of file
+++ /dev/null
-page.title=Systrace
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-
-<p>The Systrace tool helps analyze the performance of your application by capturing and
- displaying execution times of your applications processes and other Android system processes. The
- tool combines data from the Android kernel such as the CPU scheduler, disk activity, and
- application threads to generate an HTML report that shows an overall picture of an Android
- device’s system processes for a given period of time.</p>
-
-<p>The Systrace tool is particularly useful in diagnosing display problems where an
- application is slow to draw or stutters while displaying motion or animation. For more information
- on how to use Systrace, see <a href="{@docRoot}tools/debugging/systrace.html">Analyzing
- UI Performance with Systrace</a>.</p>
-
-<h2 id="requirements">Requirements</h2>
-
-<p>In order to run Systrace, you must have Android SDK Tools 20 or later installed. You must also
-have <a href="http://www.python.org/">Python</a> installed and included in your development
-computer's execution path. In order to generate a trace, you must connect a device running Android
-4.1 (API Level 16) or higher to your development system using a
-<a href="{@docRoot}tools/device.html#setting-up">USB debugging connection</a>.</p>
-
-<p>The Systrace tool can be run either from one of the Android SDK's graphical user interface
-tools, or from the command line. The following sections describe how to run the tool using either
-of these methods.</p>
-
-
-<h2 id="gui">User Interface</h2>
-
-<p>The Systrace tool can be run from
-<a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>
-or the Android <a href="{@docRoot}tools/help/monitor.html">Device Monitor</a>.
-
-<p>To run the Systrace capture user interface:</p>
-
-<div class="toggle-content closed">
-<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)">
- <img src="/assets/images/styles/disclosure_down.png" class="toggle-content-img" alt=""
- />Using Android Studio</a></p>
-
- <div class="toggle-content-toggleme">
- <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 > 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>
- <li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png"
- style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li>
- <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
- </ol>
- </div>
-</div>
-
-<div class="toggle-content closed">
-<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)">
- <img src="/assets/images/styles/disclosure_down.png" class="toggle-content-img" alt=""
- />Using Device Monitor</a></p>
-
- <div class="toggle-content-toggleme">
- <ol>
- <li>Navigate to your SDK {@code tools/} directory.</li>
- <li>Run the {@code monitor} program.</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>
- <li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png"
- style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li>
- <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
- </ol>
- </div>
-</div>
-
-
-<h2 id="options">Command Line Usage</h2>
-
-<p>The Systrace tool has different command line options for devices running Android 4.3 (API
-level 18) and higher versus devices running Android 4.2 (API level 17) and lower. The following
-sections describe the different command line options for each version.</p>
-
-<p>The general syntax for running Systrace from the command line is as follows.</p>
-
-<pre>
-$ python systrace.py [options] [category1] [category2] ... [categoryN]
-</pre>
-
-<p>See the sections below for example Systrace sessions.</p>
-
-
-<h3 id="options-4.3">Android 4.3 and higher options</h3>
-
-<p>When you use Systrace on devices running Android 4.3 and higher, you can omit trace category tags
-to get the defaults, or you may manually specify tags for inclusion. Here is an example execution
-run that sets trace tags and generates a trace from a connected device.</p>
-
-<pre>
-$ cd <em>android-sdk</em>/platform-tools/systrace
-$ python systrace.py --time=10 -o mynewtrace.html sched gfx view wm
-</pre>
-
-<p class="note">
- <strong>Tip:</strong> If you want to see the names of tasks in the trace output, you <em>must</em>
- include the {@code sched} category in your command parameters.
-</p>
-
-<p>The table below lists the Systrace command line options for devices running Android 4.3
-(API level 18) and higher.</p>
-
-<table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><nobr><code>-h, --help</code></nobr></td>
-
- <td>Show the help message.</td>
- </tr>
-
- <tr>
- <td><code>-o <<em>FILE</em>></code></td>
-
- <td>Write the HTML trace report to the specified file.</td>
- </tr>
-
- <tr>
- <td><code>-t N, --time=N</code></td>
-
- <td>Trace activity for <em>N</em> seconds. The default value is 5 seconds.</td>
- </tr>
-
- <tr>
- <td><code>-b N, --buf-size=N</code></td>
-
- <td>Use a trace buffer size of <em>N</em> kilobytes. This option lets you limit the total size
- of the data collected during a trace.</td>
- </tr>
-
- <tr>
- <td><code>-k <<em>KFUNCS</em>><br>
- --ktrace=<<em>KFUNCS</em>></code></td>
-
- <td>Trace the activity of specific kernel functions, specified in a comma-separated list.</td>
- </tr>
-
- <tr>
- <td><code>-l, --list-categories</code></td>
-
- <td>List the available tracing category tags. The available tags are:
-
- <ul>
- <li><code>gfx</code> - Graphics</li>
- <li><code>input</code> - Input</li>
- <li><code>view</code> - View</li>
- <li><code>webview</code> - WebView</li>
- <li><code>wm</code> - Window Manager</li>
- <li><code>am</code> - Activity Manager</li>
- <li><code>audio</code> - Audio</li>
- <li><code>video</code> - Video</li>
- <li><code>camera</code> - Camera</li>
- <li><code>hal</code> - Hardware Modules</li>
- <li><code>res</code> - Resource Loading</li>
- <li><code>dalvik</code> - Dalvik VM</li>
- <li><code>rs</code> - RenderScript</li>
- <li><code>sched</code> - CPU Scheduling</li>
- <li><code>freq</code> - CPU Frequency</li>
- <li><code>membus</code> - Memory Bus Utilization</li>
- <li><code>idle</code> - CPU Idle</li>
- <li><code>disk</code> - Disk input and output</li>
- <li><code>load</code> - CPU Load</li>
- <li><code>sync</code> - Synchronization Manager</li>
- <li><code>workq</code> - Kernel Workqueues</li>
- </ul>
-
- <p class="note"><strong>Note:</strong> Some trace categories are not supported on all
- devices.</p>
-
- <p class="note"><strong>Tip:</strong> If you want to see the names of tasks in the trace
- output, you <em>must</em> include the {@code sched} category in your command parameters.</p>
-
- </td>
- </tr>
-
- <tr>
- <td><code>-a <<em>APP_NAME</em>><br>
- --app=<<em>APP_NAME</em>></code></td>
-
- <td>Enable tracing for applications, specified as a comma-separated list of
- <a href="{@docRoot}guide/topics/manifest/manifest-element.html#package">package names</a>.
- The apps must contain tracing instrumentation calls from the {@link android.os.Trace} class.
- For more information, see <a href="{@docRoot}tools/debugging/systrace.html#app-trace">Analyzing
- UI Performance with Systrace</a>.
- </td>
- </tr>
-
- <tr>
- <td><code>--from-file=<<em>FROM_FILE</em>></code></td>
-
- <td>Create the interactive Systrace report from a file, instead of running a live trace.</td>
- </tr>
-
- <tr>
- <td style="white-space:nowrap">
- <code>-e <<em>DEVICE_SERIAL</em>><br>
- --serial=<<em>DEVICE_SERIAL</em>></code></td>
-
- <td>Conduct the trace on a specific connected device, identified by its
- <a href="{@docRoot}tools/help/adb.html#devicestatus">device serial number</a>.</td>
- </tr>
-
-</table>
-
-
-<h3 id="options-pre-4.3">Android 4.2 and lower options</h3>
-
-<p>Using Systrace on the command line with devices running Android 4.2 and lower is typically a
-two-step process. You must first set the trace tags you want to capture and then run the trace.
-Here is an example execution run that sets trace tags and generates a trace from a connected
-device.</p>
-
-<pre>
-$ cd <em>android-sdk</em>/platform-tools/systrace
-$ python systrace.py --set-tags gfx,view,wm
-$ adb shell stop
-$ adb shell start
-$ python systrace.py --disk --time=10 -o mynewtrace.html
-</pre>
-
-<p>The table below lists the Systrace command line options for devices running Android 4.2
-(API level 17) and lower.</p>
-
-<table>
- <tr>
- <th>Option</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><nobr><code>-h, --help</code></nobr></td>
-
- <td>Show the help message.</td>
- </tr>
-
- <tr>
- <td><code>-o <<em>FILE</em>></code></td>
-
- <td>Write the HTML trace report to the specified file.</td>
- </tr>
-
- <tr>
- <td><code>-t N, --time=N</code></td>
-
- <td>Trace activity for <em>N</em> seconds. The default value is 5 seconds.</td>
- </tr>
-
- <tr>
- <td><code>-b N, --buf-size=N</code></td>
-
- <td>Use a trace buffer size of <em>N</em> kilobytes. This option lets you limit the total size
- of the data collected during a trace.</td>
- </tr>
-
- <tr>
- <td><code>-d, --disk</code></td>
-
- <td>Trace disk input and output activity. This option requires root access on the device.</td>
- </tr>
-
- <tr>
- <td><code>-f, --cpu-freq</code></td>
-
- <td>Trace CPU frequency changes. Only changes to the CPU frequency are logged, so the initial
- frequency of the CPU when tracing starts is not shown.</td>
- </tr>
-
- <tr>
- <td><code>-i, --cpu-idle</code></td>
-
- <td>Trace CPU idle events.</td>
- </tr>
-
- <tr>
- <td><code>-l, --cpu-load</code></td>
-
- <td>Trace CPU load. This value is a percentage determined by the interactive CPU frequency
- governor.</td>
- </tr>
-
- <tr>
- <td><nobr><code>-s, --no-cpu-sched</code></nobr></td>
-
- <td>Prevent tracing of the CPU scheduler. This option allows for longer trace times by reducing
- the rate of data flowing into the trace buffer.</td>
- </tr>
-
- <tr>
- <td><nobr><code>-u, --bus-utilization</code></nobr></td>
-
- <td>Trace the bus utilization levels. This option requires root access on the device.</td>
- </tr>
-
- <tr>
- <td><code>-w, --workqueue</code></td>
-
- <td>Trace kernel work queues. This option requires root access on the device.</td>
- </tr>
-
- <tr>
- <td id="tags"><code>--set-tags=<<em>TAGS</em>></code></td>
-
- <td>Set the enabled trace tags in a comma separated list. The available tags are:
- <ul>
- <li><code>gfx</code> - Graphics</li>
- <li><code>input</code> - Input</li>
- <li><code>view</code> - View</li>
- <li><code>webview</code> - WebView</li>
- <li><code>wm</code> - Window Manager</li>
- <li><code>am</code> - Activity Manager</li>
- <li><code>sync</code> - Synchronization Manager</li>
- <li><code>audio</code> - Audio</li>
- <li><code>video</code> - Video</li>
- <li><code>camera</code> - Camera</li>
- </ul>
- <p class="note"><strong>Note:</strong> When setting trace tags from the command line, you
- must stop and restart the framework ({@code $ adb shell stop; adb shell start}) for the
- tag tracing changes to take effect.</p>
- </td>
- </tr>
-
-</table>
-
-<p>You can set the trace <a href="#tags">tags</a> for Systrace on
-your Android 4.2 and lower device by navigating to <strong>Settings > Developer options >
-Monitoring > Enable traces</strong>.</p>
-
-
-<h2 id="viewing-options">Trace Viewing Shortcuts</h2>
-
-<p>The table below lists the keyboard shortcuts that are available while viewing a Systrace
-trace HTML report.</p>
-
-<table>
- <tr>
- <th>Key</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><strong>w</strong></td>
-
- <td>Zoom into the trace timeline.</td>
- </tr>
-
- <tr>
- <td><strong>s</strong></td>
-
- <td>Zoom out of the trace timeline.</td>
- </tr>
-
- <tr>
- <td><strong>a</strong></td>
-
- <td>Pan left on the trace timeline.</td>
- </tr>
-
- <tr>
- <td><strong>d</strong></td>
-
- <td>Pan right on the trace timeline.</td>
- </tr>
-
- <tr>
- <td><strong>e</strong></td>
-
- <td>Center the trace timeline on the current mouse location.</td>
- </tr>
-
- <tr>
- <td><strong>g</strong></td>
-
- <td>Show grid at the start of the currently selected task.</td>
- </tr>
-
- <tr>
- <td><strong>Shift+g</strong></td>
-
- <td>Show grid at the end of the currently selected task.</td>
- </tr>
-
- <tr>
- <td><strong>Right Arrow</strong></td>
-
- <td>Select the next event on the currently selected timeline.</td>
- </tr>
-
- <tr>
- <td><strong>Left Arrow</strong></td>
-
- <td>Select the previous event on the currently selected timeline.</td>
- </tr>
-
-</table>
+++ /dev/null
-page.title=Theme Editor
-parent.title=Tools
-parent.link=index.html
-page.tags=theme
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#basics">Theme Editor Basics</a></li>
- <li><a href="#themes">Themes and Colors</a></li>
- <li><a href="#device">Device-Specific Configurations</a></li>
-</ol>
-
-
- <h2>Dependencies and Prerequisites</h2>
- <ul>
- <li>Android Studio 1.4.1 or higher</li>
- </ul>
-
-</div>
-</div>
-
-<p>
-The Theme Editor is a visual assistant that helps you:
-</p>
- <li>Create and modify
-<a href="{@docRoot}guide/topics/ui/themes.html">
-themes</a> for your app.</li>
- <li>Adjust themes for different resource classifiers.</li>
- <li>Visualize the effect of color changes on common UI elements.</li>
-
-<p>
-This page introduces the fundamental tasks that you can perform with the Theme
-Editor, and explains how to do so.
-</p>
-
-
-<h2 id="basics">Theme Editor Basics</h2>
-
-<p>
-This section describes how to access the Theme Editor, and how it is laid out.
-</p>
-
-<h3>Accessing the Theme Editor</h3>
-
-<p>There are two ways to open the Theme Editor:</p>
-
-<li>From an open {@code styles.xml} file, click <strong>Open editor</strong> near the top-right
-of the file window.</li>
-
-<li>From the <strong>Tools</strong> menu, select <strong>Android</strong> >
-<strong>Theme Editor</strong>.</p>
-
-<h3 id="layout">Navigating the Theme Editor</h3>
-<p>
-The Theme Editor's main screen is divided into two sections. The left side of the editor
-shows what specific UI elements, such as the app bar or a raised button, look like
-when you apply the current theme to them. The right side of the editor displays
-the settings for the color resources, such as <strong>Theme parent</strong> and
-<strong>colorPrimary</strong>, that comprise the current theme. You can modify design
-themes by changing these resource settings.
-</p>
-
-<h2 id="themes">Themes and Colors</h2>
-
-<p>
-The Theme Editor allows you to create new themes, modify existing ones, and manage the
-colors that make up the themes.
-</p>
-
-<h3 id="create">Creating New Themes</h3>
-
-<p>
-To create a theme, follow these steps:
-</p>
- <ol>
- <li>Open the <strong>Theme</strong> dropdown menu near the top of the right
-side of the Theme Editor.</li>
- <li>Select <strong>Create New Theme</strong>. The <em>New Theme</em> dialog appears.</li>
- <li>Enter a name for the new theme.</li>
- <li>In the <em>Parent theme name:</em> field, select the parent from which the theme
- inherits initial resources.</li>
- </ol>
-
-<h3 id="rename">Renaming Themes</h3>
-
-<p>
-To rename a theme, perform the following steps:
-</p>
- <ol>
- <li>Open the <strong>Theme</strong> dropdown menu near the top of the right
-side of the Theme Editor.</li>
- <li>Select <strong>Rename AppTheme</strong>. The <em>Rename</em> dialog appears.</li>
- <li>Enter a new name for the theme.</li>
- <li>(optional) To see how the changes will look, click <strong>Preview</strong>.</li>
- <li>To apply the changes, click <strong>Refactor</strong>.</li>
- </ol>
-
-<h3 id="changing">Changing Color Resources</h3>
-
-<p>To change an existing color resource, such as <strong>colorPrimary</strong>,
-follow these steps:
-</p>
-<ol>
-<li>Click the colored square next to the name of the resource you want to change.
-The <em>Resources</em> dialog appears, containing a color picker, material-color
-palette, and other settings and information.</li>
-<li>Change the color, opacity, and name of a theme's resources as desired.</p>
-<li>To ensure that your theme uses a color from the material
-palette, click <strong>CLOSEST MATERIAL COLOR</strong>, located next to <em>Custom
-color</em>. Android Studio changes the color you picked to the material color most like it,
-and replaces <em>Custom color</em> with the name of the color from the material palette.</li>
-</ol>
-
-<p>You can also directly select colors from the material palette, which the editor displays
-as two rows of colored squares beneath the color picker.</p>
-
-<h3 id="viewing">Viewing State Lists and Colors</h3>
-
-<p>
-The Theme Editor allows you to preview
-<a href="{@docRoot}guide/topics/resources/color-list-resource.html">
-colors associated with different states.</a> To do so, open the <em>Resource</em> dialog, and click
-the <em>State List</em> tab that appears at the top of the dialog.</p>
-
-<p>
-To more fully control the states themselves, you can directly view and edit their
-properties in the XML file,
-such as {@code colors.xml}, that defines them. For more information, see the
-documentation for the {@link android.content.res.ColorStateList} class.
-</p>
-
-<h2 id="device">Device-Specific Configurations</h2>
-
-<p>
-You can choose
-<a href="{@docRoot}guide/topics/resources/providing-resources.html#Compatibility">
-device-specific</a> configurations for your app to support. Perform
-the following steps to do so:
-</p>
-
-<ol>
-<li>Click the triangle next to <em>Location</em>, near the bottom of the <a href="#changing">
-<em>Resources</em></a> dialog. The <em>Location</em> section expands, revealing
-the name of the XML file containing the
-resource, as well as a list of configuration-specific directories in which to
-place that file.</li>
-<li>If necessary, change the XML file name.</li>
-<li>Check the boxes next to the directories corresponding to the
-device-specific configurations you wish to support. Any configuration
-for which you do not specify a directory defaults to using the
-{@code values} directory.</li>
-</ol>
-
-<p>For more information about the relationship
-between directory names and configurations, see
-<a href="{@docRoot}guide/practices/screens_support.html#ConfigurationExamples">
-Supporting Multiple Screens</a>. For more information about
-supported directory names, see
-<a href="{@docRoot}guide/topics/resources/providing-resources.html#ResourceTypes">
-Providing Resources</a>.
-</p>
-
-
+++ /dev/null
-page.title=Traceview
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<p>Traceview is a graphical viewer for execution logs saved by your application.
-Traceview can help you debug your application and profile its performance.</p>
-
-<p>To start the Traceview tool:</p>
-
-<ul>
- <li>Start the <a href="{@docRoot}tools/help/monitor.html">Android Device Monitor</a>. </li>
- <li>In the Android Device Monitor tool bar, click <strong>DDMS</strong> and select a process. </li>
- <li>Click the <strong>Start Method Profiling</strong> icon to start method profiling. </li>
- <li>After the profiling is complete, click the <strong>Stop Method Profiling</strong> icon to
- display the traceview. </li>
-</ul>
-
-
-<p>For more information on how to use Traceview, see
-<a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with Traceview and
-dmtracedump</a>.
-</p>
-
-<p class="note"><strong>Note:</strong> Running <code>traceview</code> from the command line
-has been deprecated. </p>
-
-
+++ /dev/null
-page.title=Translations Editor
-parent.title=Tools
-parent.link=index.html
-page.tags=translations
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#about">About the Translations Editor</a></li>
- <li><a href="#running">Running the Translations Editor</a></li>
- <li><a href="#managing">Managing String Resources</a></li>
- <li><a href="#ordering">Ordering Translation Services</a></li>
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/basics/supporting-devices/languages.html">Supporting Different
- Languages</a></li>
- <li><a href="{@docRoot}guide/topics/resources/localization.html">Localizing with Resources</a>
- </li>
- <li><a href="{@docRoot}guide/topics/resources/providing-resources.html">Providing Resources</a>
- </li>
- </ol>
-
-</div>
-</div>
-
-<p>
-If your application supports multiple languages, you need to properly manage your
-translated string resources. Android Studio provides the Translations Editor to make viewing and
-managing your translated resources easier.
-</p>
-
-<h2 id="about">About the Translations Editor</h2>
-
-<p>
-Translated resources are stored in multiple XML files in multiple directories in your project.
-Manually finding and editing resource files across many translations can be difficult. Because of
-this, your application might have missing translations that go unnoticed until after your
-application has been built and distributed to users.
-</p>
-
-<p>
-The Translations Editor lets you view and update all your string resources in one convenient
-place. The editor gives you a single view of all of your translated resources, making it easy to
-change or add translations, and even find missing translations.
-</p>
-
-<img src="{@docRoot}images/tools/studio-translations-editor.png" />
-<p class="img-caption"><strong>Figure 1.</strong> Manage locales and strings in the
-Translations Editor.</p>
-
-<h2 id="running">Running the Translations Editor</h2>
-
-<p>
-Follow these steps to start the Translations Editor:
-</p>
-
-<ol>
- <li>In Android Studio, open an Android app project.</li>
- <li>In the <em>Project</em> window, select the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>.</li>
- <li>Open the <strong>res</strong> folder, and then open the <strong>values</strong> folder.</li>
- <li>If a <strong>strings.xml</strong> folder is present, open this folder.</li>
- <li>Right-click the <code>strings.xml</code> file (not folder) and select <strong>Open
- Translations Editor</strong>.</li>
-</ol>
-
-<p>
-You can also access the Translations Editor by opening a <code>strings.xml</code> file for editing
-and clicking the <strong>Open editor</strong> link, or clicking the globe icon
-<img src="{@docRoot}images/tools/studio-globe-icon.png" alt=""/> in the Design layout view and
-choosing <strong>Edit Translations</strong>.
-</p>
-
-<h2 id="managing">Managing String Resources</h2>
-
-<p>
-The Translations Editor provides a view of all your string resources and current locale
-translations. The name of each resource is listed in the Key column, along with a default value
-for the key, a checkbox to mark the key as untranslatable, and values for each locale translation.
-</p>
-
-<p>
-Edit translations by double-clicking on the translation and editing the value directly
-in the list view, or selecting the translation and editing the <strong>Translation</strong> field
-value at the bottom of the editor. The default value can be edited by double-clicking on
-the default value or selecting the default value and updating the <strong>Default Value</strong>
-field.</p>
-
-<p>
-If a resource is missing a translation and isn't marked untranslatable, the key name is
-displayed in red. If you hover over a red resource, Android Studio displays details about the
-missing translations.
-</p>
-
-<h3 id="adding">Adding a new string resource</h3>
-
-<p>
-Add a new resource by clicking the add icon <img src="{@docRoot}images/tools/studio-add-icon.png"
- alt=""/>. Android Studio prompts you for a key name,
-default value, and resource folder that contains the <code>strings.xml</code> file where the new
-resource is added.
-</p>
-
-<h3 id="adding_locales">Adding additional locales</h3>
-
-<p>
-Add additional locales by pressing the globe icon
- <img src="{@docRoot}images/tools/studio-globe-icon.png" alt=""/> and selecting the locale you want
-to add. The Translations Editor adds the new locale column and creates the translation strings XML
-file in the appropriate project directory.
-</p>
-
-<p>
-The Translations Editor has
-<a class="external-link" href="https://tools.ietf.org/html/bcp47">BCP 47</a> support, and
-combines language and region codes into a single selection for targeted localizations.
-</p>
-
-<h2 id="ordering">Ordering Translation Services</h2>
-
-<p>
-Clicking the <strong>Order a translation</strong> link opens a page in your browser where you
-can upload string resource XML files and order translation services. App translation services are
-available from Google Play and other vendors. For more information about Google Play App
-Translation Services, see the <a class="external-link"
-href="http://android-developers.blogspot.com/2013/11/app-translation-service-now-available.html">
-Google Play App Translation Service</a> announcement.
-</p>
-
+++ /dev/null
-page.title=Configurator
-parent.title=uiautomator
-parent.link=index.html
-
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-
-<div id="api-info-block">
-<div class="api-level" style="margin:-95px 0 0;">
-Since <a href="/guide/topics/manifest/uses-sdk-element.html#ApiLevels">API level 18</a>
-</div>
-</div>
-
-<p>Allows you to set key parameters for running uiautomator tests. The new
-settings take effect immediately and can be changed any time during a test run.
-To modify parameters using <code><a href="#">Configurator</a></code>, first
-obtain an instance by calling <code><a href="#getInstance()">getInstance()</a></code>.
-As a best practice, make sure you always save the original value of any
-parameter that you are modifying. After running your tests with the modified
-parameters, make sure to also restore the original parameter values, otherwise
-this will impact other tests cases.</p>
-
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- long</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getActionAcknowledgmentTimeout()">getActionAcknowledgmentTimeout</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the current timeout for waiting for an acknowledgment of generic
- uiautomator actions, such as clicks, text setting, and menu presses.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
- static
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getInstance()">getInstance</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves a singleton instance of Configurator.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- long</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getKeyInjectionDelay()">getKeyInjectionDelay</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the current delay between key presses when injecting text input.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- long</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getScrollAcknowledgmentTimeout()">getScrollAcknowledgmentTimeout</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the timeout for waiting for an acknowledgement of an
- uiautomtor scroll swipe action.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- long</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getWaitForIdleTimeout()">getWaitForIdleTimeout</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the current timeout used for waiting for the user interface to go
- into an idle state.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- long</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getWaitForSelectorTimeout()">getWaitForSelectorTimeout</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the current timeout for waiting for a widget to become visible in
- the user interface so that it can be matched by a selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setActionAcknowledgmentTimeout(long)">setActionAcknowledgmentTimeout</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Sets the timeout for waiting for an acknowledgment of generic uiautomator
- actions, such as clicks, text setting, and menu presses.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setKeyInjectionDelay(long)">setKeyInjectionDelay</a></span>(long delay)</nobr>
-
- <div class="jd-descrdiv">Sets a delay between key presses when injecting text input.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setScrollAcknowledgmentTimeout(long)">setScrollAcknowledgmentTimeout</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Sets the timeout for waiting for an acknowledgement of an
- uiautomtor scroll swipe action.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setWaitForIdleTimeout(long)">setWaitForIdleTimeout</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Sets the timeout for waiting for the user interface to go into an idle
- state before starting a uiautomator action.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">Configurator</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Sets the timeout for waiting for a widget to become visible in the user
- interface so that it can be matched by a selector.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Object</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">clone</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">equals</span>(Object arg0)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">finalize</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- Class<?></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">getClass</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">hashCode</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notify</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notifyAll</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">toString</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0, int arg1)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0)</nobr>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<A NAME="getActionAcknowledgmentTimeout()"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- long
- </span>
- <span class="sympad">getActionAcknowledgmentTimeout</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the current timeout for waiting for an acknowledgment of generic
- uiautomator actions, such as clicks, text setting, and menu presses.
-
- The acknowledgment is an <a href="http://developer.android.com/reference/android/view/accessibility/AccessibilityEvent.html">AccessibilityEvent</a>,
- corresponding to an action, that lets the framework determine if the
- action was successful. Generally, this timeout should not be modified.
- See <code><a href="UiObject.html">UiObject</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>current timeout in milliseconds</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getInstance()"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
- static
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">getInstance</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves a singleton instance of Configurator.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>Configurator instance</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getKeyInjectionDelay()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- long
- </span>
- <span class="sympad">getKeyInjectionDelay</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the current delay between key presses when injecting text input.
- See <code><a href="UiObject.html#setText(java.lang.String)">setText(String)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>current delay in milliseconds</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="getScrollAcknowledgmentTimeout()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- long
- </span>
- <span class="sympad">getScrollAcknowledgmentTimeout</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the timeout for waiting for an acknowledgement of an
- uiautomtor scroll swipe action.
-
- The acknowledgment is an <a href="http://developer.android.com/reference/android/view/accessibility/AccessibilityEvent.html">AccessibilityEvent</a>,
- corresponding to the scroll action, that lets the framework determine if
- the scroll action was successful. Generally, this timeout should not be modified.
- See <code><a href="UiScrollable.html">UiScrollable</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>current timeout in milliseconds</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="getWaitForIdleTimeout()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- long
- </span>
- <span class="sympad">getWaitForIdleTimeout</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the current timeout used for waiting for the user interface to go
- into an idle state.
-
- By default, all core uiautomator objects except <code><a href="UiDevice.html">UiDevice</a></code> will perform
- this wait before starting to search for the widget specified by the
- object's <code><a href="UiSelector.html">UiSelector</a></code>. Once the idle state is detected or the
- timeout elapses (whichever occurs first), the object will start to wait
- for the selector to find a match.
- See <code><a href="#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout(long)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>Current timeout value in milliseconds</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="getWaitForSelectorTimeout()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- long
- </span>
- <span class="sympad">getWaitForSelectorTimeout</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the current timeout for waiting for a widget to become visible in
- the user interface so that it can be matched by a selector.
-
- Because user interface content is dynamic, sometimes a widget may not
- be visible immediately and won't be detected by a selector. This timeout
- allows the uiautomator framework to wait for a match to be found, up until
- the timeout elapses.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>Current timeout value in milliseconds</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setActionAcknowledgmentTimeout(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">setActionAcknowledgmentTimeout</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the timeout for waiting for an acknowledgment of generic uiautomator
- actions, such as clicks, text setting, and menu presses.
-
- The acknowledgment is an <a href="http://developer.android.com/reference/android/view/accessibility/AccessibilityEvent.html">AccessibilityEvent</a>,
- corresponding to an action, that lets the framework determine if the
- action was successful. Generally, this timeout should not be modified.
- See <code><a href="UiObject.html">UiObject</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>Timeout value in milliseconds</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>self</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setKeyInjectionDelay(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">setKeyInjectionDelay</span>
- <span class="normal">(long delay)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets a delay between key presses when injecting text input.
- See <code><a href="UiObject.html#setText(java.lang.String)">setText(String)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>delay</td>
- <td>Delay value in milliseconds</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>self</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setScrollAcknowledgmentTimeout(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">setScrollAcknowledgmentTimeout</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the timeout for waiting for an acknowledgement of an
- uiautomtor scroll swipe action.
-
- The acknowledgment is an <a href="http://developer.android.com/reference/android/view/accessibility/AccessibilityEvent.html">AccessibilityEvent</a>,
- corresponding to the scroll action, that lets the framework determine if
- the scroll action was successful. Generally, this timeout should not be modified.
- See <code><a href="UiScrollable.html">UiScrollable</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>Timeout value in milliseconds</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>self</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setWaitForIdleTimeout(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">setWaitForIdleTimeout</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the timeout for waiting for the user interface to go into an idle
- state before starting a uiautomator action.
-
- By default, all core uiautomator objects except <code><a href="UiDevice.html">UiDevice</a></code> will perform
- this wait before starting to search for the widget specified by the
- object's <code><a href="UiSelector.html">UiSelector</a></code>. Once the idle state is detected or the
- timeout elapses (whichever occurs first), the object will start to wait
- for the selector to find a match.
- See <code><a href="#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout(long)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>Timeout value in milliseconds</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>self</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setWaitForSelectorTimeout(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">Configurator</a>
- </span>
- <span class="sympad">setWaitForSelectorTimeout</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the timeout for waiting for a widget to become visible in the user
- interface so that it can be matched by a selector.
-
- Because user interface content is dynamic, sometimes a widget may not
- be visible immediately and won't be detected by a selector. This timeout
- allows the uiautomator framework to wait for a match to be found, up until
- the timeout elapses.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>Timeout value in milliseconds.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>self</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-
-
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-
-
-
-
+++ /dev/null
-page.title=IAutomationSupport
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-
-<h2>Class Overview</h2>
-<p>Provides auxiliary support for running test cases
-
-</p>
-
-<h2>Summary</h2>
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
- abstract
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#sendStatus(int, android.os.Bundle)">sendStatus</a></span>(int resultCode, Bundle status)
-
- <div class="jd-descrdiv">Allows the running test cases to send out interim status</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<a id="sendStatus(int, android.os.Bundle)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
- abstract
-
- void
- </span>
- <span class="sympad">sendStatus</span>
- <span class="normal">(int resultCode, Bundle status)</span>
- </h4>
-</div>
-
-<div class="jd-details-descr">
- <div class="jd-tagdata jd-tagdescr"><p>Allows the running test cases to send out interim status</p></div>
-</div>
-
+++ /dev/null
-page.title=UiAutomatorTestCase
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<h2>Class Overview</h2>
-<p>UI automation tests should extend this class. This class provides access
- to the following:
-<ul>
-<li><code><a href="UiDevice.html">UiDevice</a></code> instance</li>
-<li>Bundle for command line parameters</li>
-</ul>
-</p>
-
-<div class="jd-descr">
-
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
-
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#UiAutomatorTestCase()">UiAutomatorTestCase</a></span>()
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="IAutomationSupport.html">IAutomationSupport</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getAutomationSupport()">getAutomationSupport</a></span>()
-
- <div class="jd-descrdiv">Provides support for running tests to report interim status</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- Bundle
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getParams()">getParams</a></span>()
-
- <div class="jd-descrdiv">Get command line parameters.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiDevice.html">UiDevice</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getUiDevice()">getUiDevice</a></span>()
-
- <div class="jd-descrdiv">Get current instance of <code><a href="UiDevice.html">UiDevice</a></code>.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#sleep(long)">sleep</a></span>(long ms)
-
- <div class="jd-descrdiv">Calls <code><a href="null#sleep(long)">sleep(long)</a></code> to sleep</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-junit.framework.TestCase" class="jd-expando-trigger closed"
- ><img id="inherited-methods-junit.framework.TestCase-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- junit.framework.TestCase
-
-<div id="inherited-methods-junit.framework.TestCase">
- <div id="inherited-methods-junit.framework.TestCase-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-junit.framework.TestCase-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">countTestCases</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getName</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- TestResult
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">run</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">run</span>(TestResult arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">runBare</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">setName</span>(String arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">toString</span>()
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-junit.framework.Assert" class="jd-expando-trigger closed"
- ><img id="inherited-methods-junit.framework.Assert-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- junit.framework.Assert
-
-<div id="inherited-methods-junit.framework.Assert">
- <div id="inherited-methods-junit.framework.Assert-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-junit.framework.Assert-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(short arg0, short arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, int arg1, int arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, short arg1, short arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(char arg0, char arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, String arg1, String arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(int arg0, int arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, double arg1, double arg2, double arg3)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, long arg1, long arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(byte arg0, byte arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(Object arg0, Object arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(boolean arg0, boolean arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, float arg1, float arg2, float arg3)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, boolean arg1, boolean arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, String arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(float arg0, float arg1, float arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, byte arg1, byte arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(double arg0, double arg1, double arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, char arg1, char arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertEquals</span>(long arg0, long arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertFalse</span>(String arg0, boolean arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertFalse</span>(boolean arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNotNull</span>(String arg0, Object arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNotNull</span>(Object arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNotSame</span>(Object arg0, Object arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNotSame</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNull</span>(Object arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertNull</span>(String arg0, Object arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertSame</span>(Object arg0, Object arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertSame</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertTrue</span>(String arg0, boolean arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">assertTrue</span>(boolean arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">fail</span>(String arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">fail</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">failNotEquals</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">failNotSame</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">failSame</span>(String arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
- static
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">format</span>(String arg0, Object arg1, Object arg2)
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">equals</span>(Object arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- Class<?>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getClass</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">hashCode</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notify</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notifyAll</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">toString</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0, int arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0)
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-junit.framework.Test" class="jd-expando-trigger closed"
- ><img id="inherited-methods-junit.framework.Test-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From interface
-
- junit.framework.Test
-
-<div id="inherited-methods-junit.framework.Test">
- <div id="inherited-methods-junit.framework.Test-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-junit.framework.Test-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
- abstract
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">countTestCases</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
- abstract
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">run</span>(TestResult arg0)
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-
-<a id="UiAutomatorTestCase()"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiAutomatorTestCase</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<a id="getAutomationSupport()"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="IAutomationSupport.html">IAutomationSupport</a>
- </span>
- <span class="sympad">getAutomationSupport</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Provides support for running tests to report interim status</p></div>
-
- </div>
-</div>
-
-
-<a id="getParams()"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- Bundle
- </span>
- <span class="sympad">getParams</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Get command line parameters. On the command line when passing <code>-e key value</code>
- pairs, the Bundle will have the key value pairs conveniently available to the
- tests.
-</p></div>
-
- </div>
-</div>
-
-
-<a id="getUiDevice()"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiDevice.html">UiDevice</a>
- </span>
- <span class="sympad">getUiDevice</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Get current instance of <code><a href="UiDevice.html">UiDevice</a></code>. Works similar to calling the static
- <code><a href="UiDevice.html#getInstance()">getInstance()</a></code> from anywhere in the test classes.
-</p></div>
-
- </div>
-</div>
-
-
-<a id="sleep(long)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">sleep</span>
- <span class="normal">(long ms)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Calls <code><a href="null#sleep(long)">sleep(long)</a></code> to sleep</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>ms</th>
- <td>is in milliseconds.
-</td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
+++ /dev/null
-page.title=UiCollection
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>Used to enumerate a container's user interface (UI) elements for the purpose of counting,
- or targeting a sub elements by a child's text or description.
-</p>
-
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
-
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#UiCollection(com.android.uiautomator.core.UiSelector)">UiCollection</a></span>(<a href="UiSelector.html">UiSelector</a> selector)
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByDescription</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>
- selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getChildByInstance(com.android.uiautomator.core.UiSelector, int)">getChildByInstance</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, int instance)
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByText</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#getChildCount(com.android.uiautomator.core.UiSelector)">getChildCount</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern)
-
- <div class="jd-descrdiv">Counts child UI element instances matching the <code>childPattern</code>
- argument.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-com.android.uiautomator.core.UiObject" class="jd-expando-trigger closed"
- ><img id="inherited-methods-com.android.uiautomator.core.UiObject-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- <a href="UiObject.html">com.android.uiautomator.core.UiObject</a>
-
-<div id="inherited-methods-com.android.uiautomator.core.UiObject">
- <div id="inherited-methods-com.android.uiautomator.core.UiObject-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-com.android.uiautomator.core.UiObject-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#clearTextField()">clearTextField</a></span>()
-
- <div class="jd-descrdiv">Clears the existing text contents in an editable field.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#click()">click</a></span>()
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#clickAndWaitForNewWindow(long)">clickAndWaitForNewWindow</a></span>(long timeout)
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject and waits for window transitions.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#clickAndWaitForNewWindow()">clickAndWaitForNewWindow</a></span>()
-
- <div class="jd-descrdiv">See <code><a href="UiObject.html#clickAndWaitForNewWindow(long)">clickAndWaitForNewWindow(long)</a></code>
- This method is intended to reliably wait for window transitions that would typically take
- longer than the usual default timeouts.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#clickBottomRight()">clickBottomRight</a></span>()
-
- <div class="jd-descrdiv">Clicks the bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#clickTopLeft()">clickTopLeft</a></span>()
-
- <div class="jd-descrdiv">Clicks the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#exists()">exists</a></span>()
-
- <div class="jd-descrdiv">Check if UI element exists.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- Rect
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getBounds()">getBounds</a></span>()
-
- <div class="jd-descrdiv">Returns the UI element's <code>bounds</code> property.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getChild(com.android.uiautomator.core.UiSelector)">getChild</a></span>(<a href="UiSelector.html">UiSelector</a> selector)
-
- <div class="jd-descrdiv">Creates a new UiObject representing a child UI element of the element currently represented
- by this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getChildCount()">getChildCount</a></span>()
-
- <div class="jd-descrdiv">Counts the child UI elements immediately under the UI element currently represented by
- this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getContentDescription()">getContentDescription</a></span>()
-
- <div class="jd-descrdiv">Reads the <code>content_desc</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getFromParent(com.android.uiautomator.core.UiSelector)">getFromParent</a></span>(<a href="UiSelector.html">UiSelector</a> selector)
-
- <div class="jd-descrdiv">Creates a new UiObject representing a child UI element from the parent element currently
- represented by this object.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getPackageName()">getPackageName</a></span>()
-
- <div class="jd-descrdiv">Reads the UI element's <code>package</code> property</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- <a href="UiSelector.html">UiSelector</a>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getSelector()">getSelector</a></span>()
-
- <div class="jd-descrdiv">Debugging helper.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getText()">getText</a></span>()
-
- <div class="jd-descrdiv">Reads the <code>text</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- Rect
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#getVisibleBounds()">getVisibleBounds</a></span>()
-
- <div class="jd-descrdiv">Returns the visible bounds of the UI element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isCheckable()">isCheckable</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>checkable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isChecked()">isChecked</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>checked</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isClickable()">isClickable</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>clickable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isEnabled()">isEnabled</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>enabled</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isFocusable()">isFocusable</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>focusable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isFocused()">isFocused</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>focused</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isLongClickable()">isLongClickable</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>long-clickable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isScrollable()">isScrollable</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>scrollable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#isSelected()">isSelected</a></span>()
-
- <div class="jd-descrdiv">Check if the UI element's <code>selected</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#longClick()">longClick</a></span>()
-
- <div class="jd-descrdiv">Long clicks the center of the visible bounds of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#longClickBottomRight()">longClickBottomRight</a></span>()
-
- <div class="jd-descrdiv">Long clicks bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#longClickTopLeft()">longClickTopLeft</a></span>()
-
- <div class="jd-descrdiv">Long clicks on the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#setText(java.lang.String)">setText</a></span>(String text)
-
- <div class="jd-descrdiv">Sets the text in an editable field, after clearing the field's content.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#swipeDown(int)">swipeDown</a></span>(int steps)
-
- <div class="jd-descrdiv">Perform the action on the UI element that is represented by this object, Also see
- #scrollToBeginning(int), #scrollToEnd(int), #scrollBackward(),
- #scrollForward().</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#swipeLeft(int)">swipeLeft</a></span>(int steps)
-
- <div class="jd-descrdiv">Perform the action on the UI element that is represented by this object.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#swipeRight(int)">swipeRight</a></span>(int steps)
-
- <div class="jd-descrdiv">Perform the action on the UI element that is represented by this object.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#swipeUp(int)">swipeUp</a></span>(int steps)
-
- <div class="jd-descrdiv">Perform the action on the UI element that is represented by this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#waitForExists(long)">waitForExists</a></span>(long timeout)
-
- <div class="jd-descrdiv">Waits a specified length of time for a UI element to become visible.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="UiObject.html#waitUntilGone(long)">waitUntilGone</a></span>(long timeout)
-
- <div class="jd-descrdiv">Waits a specified length of time for a UI element to become undetectable.</div>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">equals</span>(Object arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- Class<?>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getClass</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">hashCode</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notify</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notifyAll</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">toString</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0, int arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0)
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-<a id="UiCollection(com.android.uiautomator.core.UiSelector)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiCollection</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-<a id="getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByDescription</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>
- selector.
-
- It looks for any child matching the <code>childPattern</code> argument that has
- a child UI element anywhere within its sub hierarchy that has content-description text.
- The returned UiObject will point at the <code>childPattern</code> instance that matched the
- search and not at the identifying child element that matched the content description.</p></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</th>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector of the child pattern to match and return</td>
- </tr>
- <tr>
- <th>text</th>
- <td>String of the identifying child contents of of the <code>childPattern</code></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> pointing at and instance of <code>childPattern</code></li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<a id="getChildByInstance(com.android.uiautomator.core.UiSelector, int)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByInstance</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, int instance)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>.
-
- It looks for any child matching the <code>childPattern</code> argument that has
- a child UI element anywhere within its sub hierarchy that is at the <code>instance</code>
- specified. The operation is performed only on the visible items and no scrolling is performed
- in this case.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</th>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector of the child pattern to match and return</td>
- </tr>
- <tr>
- <th>instance</th>
- <td>int the desired matched instance of this <code>childPattern</code></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> pointing at and instance of <code>childPattern</code>
-</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<a id="getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByText</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for child UI element within the constraints of this <code><a href="UiSelector.html">UiSelector</a></code>
- selector.
-
- It looks for any child matching the <code>childPattern</code> argument that has
- a child UI element anywhere within its sub hierarchy that has a text attribute equal to
- <code>text</code>. The returned UiObject will point at the <code>childPattern</code>
- instance that matched the search and not at the identifying child element that matched the
- text attribute.</p></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</th>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector of the child pattern to match and return</td>
- </tr>
- <tr>
- <th>text</th>
- <td>String of the identifying child contents of of the <code>childPattern</code></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> pointing at and instance of <code>childPattern</code></li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<a id="getChildCount(com.android.uiautomator.core.UiSelector)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
- int
- </span>
- <span class="sympad">getChildCount</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern)</span>
- </h4>
- <div class="api-level">
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Counts child UI element instances matching the <code>childPattern</code>
- argument. The method returns the number of matching UI elements that are
- currently visible. The count does not include items of a scrollable list
- that are off-screen.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</th>
- <td>a <code><a href="UiSelector.html">UiSelector</a></code> that represents the matching child UI
- elements to count</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>the number of matched childPattern under the current <code><a href="UiCollection.html">UiCollection</a></code>
-</li></ul>
- </div>
-
- </div>
-
+++ /dev/null
-page.title=UiDevice
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>Provides access to state information about the device. You can
-also use this class to simulate user actions on the device, such as pressing
-the d-pad or pressing the Home and Menu buttons.</p>
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clearLastTraversedText()">clearLastTraversedText</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clears the text from the last UI traversal event.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#click(int, int)">click</a></span>(int x, int y)</nobr>
-
- <div class="jd-descrdiv">Perform a click at arbitrary coordinates specified by the user</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#drag(int, int, int, int, int)">drag</a></span>(int startX, int startY, int endX, int endY, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a swipe from one coordinate to another coordinate.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#dumpWindowHierarchy(java.lang.String)">dumpWindowHierarchy</a></span>(String fileName)</nobr>
-
- <div class="jd-descrdiv">Helper method used for debugging to dump the current window's layout hierarchy.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#freezeRotation()">freezeRotation</a></span>()</nobr>
-
- <div class="jd-descrdiv">Disables the sensors and freezes the device rotation at its
- current rotation state.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getCurrentActivityName()">getCurrentActivityName</a></span>()</nobr>
-
- <div class="jd-descrdiv"><em>
- This method is deprecated.
- The results returned should be considered unreliable</em></div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getCurrentPackageName()">getCurrentPackageName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves the name of the last package to report accessibility events.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getDisplayHeight()">getDisplayHeight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the height of the display, in pixels.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getDisplayRotation()">getDisplayRotation</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the current rotation of the display, as defined in <code><a href="../../../../../reference/android/view/Surface.html">Surface</a></code></div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Point</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getDisplaySizeDp()">getDisplaySizeDp</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the display size in dp (device-independent pixel)
-
- The returned display size is adjusted per screen rotation.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getDisplayWidth()">getDisplayWidth</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the width of the display, in pixels.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
- static
-
- <a href="#">UiDevice</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getInstance()">getInstance</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves a singleton instance of UiDevice</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getLastTraversedText()">getLastTraversedText</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves the text from the last UI traversal event received.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getProductName()">getProductName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves the product name of the device.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#hasAnyWatcherTriggered()">hasAnyWatcherTriggered</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if any registered <code><a href="UiWatcher.html">UiWatcher</a></code> have triggered.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#hasWatcherTriggered(java.lang.String)">hasWatcherTriggered</a></span>(String watcherName)</nobr>
-
- <div class="jd-descrdiv">Checks if a specific registered <code><a href="UiWatcher.html">UiWatcher</a></code> has triggered.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isNaturalOrientation()">isNaturalOrientation</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the device is in its natural orientation.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isScreenOn()">isScreenOn</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks the power manager if the screen is ON.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#openNotification()">openNotification</a></span>()</nobr>
-
- <div class="jd-descrdiv">Opens the notification shade.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#openQuickSettings()">openQuickSettings</a></span>()</nobr>
-
- <div class="jd-descrdiv">Opens the Quick Settings shade.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressBack()">pressBack</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the BACK button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDPadCenter()">pressDPadCenter</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the CENTER button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDPadDown()">pressDPadDown</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the DOWN button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDPadLeft()">pressDPadLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the LEFT button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDPadRight()">pressDPadRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the RIGHT button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDPadUp()">pressDPadUp</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the UP button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressDelete()">pressDelete</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the DELETE key.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressEnter()">pressEnter</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the ENTER key.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressHome()">pressHome</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the HOME button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressKeyCode(int, int)">pressKeyCode</a></span>(int keyCode, int metaState)</nobr>
-
- <div class="jd-descrdiv">Simulates a short press using a key code.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressKeyCode(int)">pressKeyCode</a></span>(int keyCode)</nobr>
-
- <div class="jd-descrdiv">Simulates a short press using a key code.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressMenu()">pressMenu</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the MENU button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressRecentApps()">pressRecentApps</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the Recent Apps button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pressSearch()">pressSearch</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates a short press on the SEARCH button.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher</a></span>(String name, <a href="UiWatcher.html">UiWatcher</a> watcher)</nobr>
-
- <div class="jd-descrdiv">Registers a <code><a href="UiWatcher.html">UiWatcher</a></code> to run automatically when the testing framework is unable to
- find a match using a <code><a href="UiSelector.html">UiSelector</a></code>.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#removeWatcher(java.lang.String)">removeWatcher</a></span>(String name)</nobr>
-
- <div class="jd-descrdiv">Removes a previously registered <code><a href="UiWatcher.html">UiWatcher</a></code>.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#resetWatcherTriggers()">resetWatcherTriggers</a></span>()</nobr>
-
- <div class="jd-descrdiv">Resets a <code><a href="UiWatcher.html">UiWatcher</a></code> that has been triggered.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#runWatchers()">runWatchers</a></span>()</nobr>
-
- <div class="jd-descrdiv">This method forces all registered watchers to run.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setCompressedLayoutHeirarchy(boolean)">setCompressedLayoutHeirarchy</a></span>(boolean compressed)</nobr>
-
- <div class="jd-descrdiv">Enables or disables layout hierarchy compression.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setOrientationLeft()">setOrientationLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates orienting the device to the left and also freezes rotation
- by disabling the sensors.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setOrientationNatural()">setOrientationNatural</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates orienting the device into its natural orientation and also freezes rotation
- by disabling the sensors.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setOrientationRight()">setOrientationRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Simulates orienting the device to the right and also freezes rotation
- by disabling the sensors.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#sleep()">sleep</a></span>()</nobr>
-
- <div class="jd-descrdiv">This method simply presses the power button if the screen is ON else
- it does nothing if the screen is already OFF.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipe(android.graphics.Point[], int)">swipe</a></span>(Point[] segments, int segmentSteps)</nobr>
-
- <div class="jd-descrdiv">Performs a swipe between points in the Point array.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipe(int, int, int, int, int)">swipe</a></span>(int startX, int startY, int endX, int endY, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a swipe from one coordinate to another using the number of steps
- to determine smoothness and speed.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#takeScreenshot(java.io.File)">takeScreenshot</a></span>(File storePath)</nobr>
-
- <div class="jd-descrdiv">Take a screenshot of current window and store it as PNG
-
- Default scale of 1.0f (original size) and 90% quality is used
- The screenshot is adjusted per screen rotation</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#takeScreenshot(java.io.File, float, int)">takeScreenshot</a></span>(File storePath, float scale, int quality)</nobr>
-
- <div class="jd-descrdiv">Take a screenshot of current window and store it as PNG
-
- The screenshot is adjusted per screen rotation</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#unfreezeRotation()">unfreezeRotation</a></span>()</nobr>
-
- <div class="jd-descrdiv">Re-enables the sensors and un-freezes the device rotation allowing its contents
- to rotate with the device physical rotation.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#waitForIdle(long)">waitForIdle</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits for the current application to idle.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#waitForIdle()">waitForIdle</a></span>()</nobr>
-
- <div class="jd-descrdiv">Waits for the current application to idle.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#waitForWindowUpdate(java.lang.String, long)">waitForWindowUpdate</a></span>(String packageName, long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits for a window content update event to occur.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#wakeUp()">wakeUp</a></span>()</nobr>
-
- <div class="jd-descrdiv">This method simulates pressing the power button if the screen is OFF else
- it does nothing if the screen is already ON.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Object</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">clone</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">equals</span>(Object arg0)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">finalize</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- Class<?></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">getClass</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">hashCode</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notify</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notifyAll</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">toString</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0, int arg1)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0)</nobr>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<A NAME="clearLastTraversedText()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">clearLastTraversedText</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Clears the text from the last UI traversal event.
- See <code><a href="#getLastTraversedText()">getLastTraversedText()</a></code>.</p></div>
-
- </div>
-</div>
-
-
-<A NAME="click(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">click</span>
- <span class="normal">(int x, int y)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Perform a click at arbitrary coordinates specified by the user</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>x</td>
- <td>coordinate</td>
- </tr>
- <tr>
- <th>y</td>
- <td>coordinate</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the click succeeded else false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="drag(int, int, int, int, int)"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">drag</span>
- <span class="normal">(int startX, int startY, int endX, int endY, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a swipe from one coordinate to another coordinate. You can control
- the smoothness and speed of the swipe by specifying the number of steps.
- Each step execution is throttled to 5 milliseconds per step, so for a 100
- steps, the swipe will take around 0.5 seconds to complete.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>startX</td>
- <td>X-axis value for the starting coordinate</td>
- </tr>
- <tr>
- <th>startY</td>
- <td>Y-axis value for the starting coordinate</td>
- </tr>
- <tr>
- <th>endX</td>
- <td>X-axis value for the ending coordinate</td>
- </tr>
- <tr>
- <th>endY</td>
- <td>Y-axis value for the ending coordinate</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>is the number of steps for the swipe action</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if swipe is performed, false if the operation fails
- or the coordinates are invalid</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="dumpWindowHierarchy(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">dumpWindowHierarchy</span>
- <span class="normal">(String fileName)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Helper method used for debugging to dump the current window's layout hierarchy.
- The file root location is /data/local/tmp</p></div>
-
- </div>
-</div>
-
-
-<A NAME="freezeRotation()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">freezeRotation</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Disables the sensors and freezes the device rotation at its
- current rotation state.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getCurrentActivityName()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getCurrentActivityName</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
- <p>
- <p class="caution"><strong>
- This method is deprecated.</strong><br/>
- The results returned should be considered unreliable
- </p>
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves the last activity to report accessibility events.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>String name of activity</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getCurrentPackageName()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getCurrentPackageName</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves the name of the last package to report accessibility events.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>String name of package</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getDisplayHeight()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- int
- </span>
- <span class="sympad">getDisplayHeight</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the height of the display, in pixels. The size is adjusted based
- on the current orientation of the display.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>height in pixels or zero on failure</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getDisplayRotation()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- int
- </span>
- <span class="sympad">getDisplayRotation</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Returns the current rotation of the display, as defined in <code><a href="../../../../../reference/android/view/Surface.html">Surface</a></code></p></div>
-
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
-</div>
-
-
-<A NAME="getDisplaySizeDp()"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- Point
- </span>
- <span class="sympad">getDisplaySizeDp</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Returns the display size in dp (device-independent pixel)
-
- The returned display size is adjusted per screen rotation. Also this will return the actual
- size of the screen, rather than adjusted per system decorations (like status bar).</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>a Point containing the display size in dp
-</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="getDisplayWidth()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- int
- </span>
- <span class="sympad">getDisplayWidth</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the width of the display, in pixels. The width and height details
- are reported based on the current orientation of the display.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>width in pixels or zero on failure</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getInstance()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
- static
-
-
-
- <a href="#">UiDevice</a>
- </span>
- <span class="sympad">getInstance</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves a singleton instance of UiDevice</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiDevice instance</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getLastTraversedText()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getLastTraversedText</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves the text from the last UI traversal event received.
-
- You can use this method to read the contents in a WebView container
- because the accessibility framework fires events
- as each text is highlighted. You can write a test to perform
- directional arrow presses to focus on different elements inside a WebView,
- and call this method to get the text from each traversed element.
- If you are testing a view container that can return a reference to a
- Document Object Model (DOM) object, your test should use the view's
- DOM instead.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>text of the last traversal event, else return an empty string</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getProductName()"></A>
-
-<div class="jd-details api apilevel-17">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getProductName</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves the product name of the device.
-
- This method provides information on what type of device the test is running on. This value is
- the same as returned by invoking #adb shell getprop ro.product.name.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>product name of the device</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="hasAnyWatcherTriggered()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">hasAnyWatcherTriggered</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if any registered <code><a href="UiWatcher.html">UiWatcher</a></code> have triggered.
-
- See <code><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher(String, UiWatcher)</a></code>
- See <code><a href="#hasWatcherTriggered(java.lang.String)">hasWatcherTriggered(String)</a></code></p></div>
-
- </div>
-</div>
-
-
-<A NAME="hasWatcherTriggered(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">hasWatcherTriggered</span>
- <span class="normal">(String watcherName)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if a specific registered <code><a href="UiWatcher.html">UiWatcher</a></code> has triggered.
- See <code><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher(String, UiWatcher)</a></code>. If a UiWatcher runs and its
- <code><a href="UiWatcher.html#checkForCondition()">checkForCondition()</a></code> call returned <code>true</code>, then
- the UiWatcher is considered triggered. This is helpful if a watcher is detecting errors
- from ANR or crash dialogs and the test needs to know if a UiWatcher has been triggered.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if triggered else false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isNaturalOrientation()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isNaturalOrientation</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the device is in its natural orientation. This is determined by checking if the
- orientation is at 0 or 180 degrees.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is in natural orientation</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="isScreenOn()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isScreenOn</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks the power manager if the screen is ON.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the screen is ON else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="openNotification()"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">openNotification</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Opens the notification shade.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="openQuickSettings()"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">openQuickSettings</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Opens the Quick Settings shade.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="pressBack()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressBack</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the BACK button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDPadCenter()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDPadCenter</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the CENTER button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDPadDown()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDPadDown</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the DOWN button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDPadLeft()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDPadLeft</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the LEFT button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDPadRight()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDPadRight</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the RIGHT button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDPadUp()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDPadUp</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the UP button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressDelete()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressDelete</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the DELETE key.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressEnter()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressEnter</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the ENTER key.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressHome()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressHome</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the HOME button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressKeyCode(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressKeyCode</span>
- <span class="normal">(int keyCode, int metaState)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press using a key code.
-
- See <code><a href="../../../../../reference/android/view/KeyEvent.html">KeyEvent</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>keyCode</td>
- <td>the key code of the event.</td>
- </tr>
- <tr>
- <th>metaState</td>
- <td>an integer in which each bit set to 1 represents a pressed meta key</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressKeyCode(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressKeyCode</span>
- <span class="normal">(int keyCode)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press using a key code.
-
- See <code><a href="../../../../../reference/android/view/KeyEvent.html">KeyEvent</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressMenu()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressMenu</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the MENU button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressRecentApps()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressRecentApps</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the Recent Apps button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="pressSearch()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pressSearch</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates a short press on the SEARCH button.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful, else return false</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">registerWatcher</span>
- <span class="normal">(String name, <a href="UiWatcher.html">UiWatcher</a> watcher)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Registers a <code><a href="UiWatcher.html">UiWatcher</a></code> to run automatically when the testing framework is unable to
- find a match using a <code><a href="UiSelector.html">UiSelector</a></code>. See <code><a href="#runWatchers()">runWatchers()</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>name</td>
- <td>to register the UiWatcher</td>
- </tr>
- <tr>
- <th>watcher</td>
- <td><code><a href="UiWatcher.html">UiWatcher</a></code></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="removeWatcher(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">removeWatcher</span>
- <span class="normal">(String name)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Removes a previously registered <code><a href="UiWatcher.html">UiWatcher</a></code>.
-
- See <code><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher(String, UiWatcher)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>name</td>
- <td>used to register the UiWatcher</td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="resetWatcherTriggers()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">resetWatcherTriggers</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Resets a <code><a href="UiWatcher.html">UiWatcher</a></code> that has been triggered.
- If a UiWatcher runs and its <code><a href="UiWatcher.html#checkForCondition()">checkForCondition()</a></code> call
- returned <code>true</code>, then the UiWatcher is considered triggered.
- See <code><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher(String, UiWatcher)</a></code></p></div>
-
- </div>
-</div>
-
-
-<A NAME="runWatchers()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">runWatchers</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>This method forces all registered watchers to run.
- See <code><a href="#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">registerWatcher(String, UiWatcher)</a></code></p></div>
-
- </div>
-</div>
-
-
-<A NAME="setCompressedLayoutHeirarchy(boolean)"></A>
-
-<div class="jd-details api apilevel-18">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">setCompressedLayoutHeirarchy</span>
- <span class="normal">(boolean compressed)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Enables or disables layout hierarchy compression.
-
- If compression is enabled, the layout hierarchy derived from the Acessibility
- framework will only contain nodes that are important for uiautomator
- testing. Any unnecessary surrounding layout nodes that make viewing
- and searching the hierarchy inefficient are removed.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>compressed</td>
- <td>true to enable compression; else, false to disable</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setOrientationLeft()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">setOrientationLeft</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates orienting the device to the left and also freezes rotation
- by disabling the sensors.
-
- If you want to un-freeze the rotation and re-enable the sensors
- see <code><a href="#unfreezeRotation()">unfreezeRotation()</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setOrientationNatural()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">setOrientationNatural</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates orienting the device into its natural orientation and also freezes rotation
- by disabling the sensors.
-
- If you want to un-freeze the rotation and re-enable the sensors
- see <code><a href="#unfreezeRotation()">unfreezeRotation()</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setOrientationRight()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">setOrientationRight</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Simulates orienting the device to the right and also freezes rotation
- by disabling the sensors.
-
- If you want to un-freeze the rotation and re-enable the sensors
- see <code><a href="#unfreezeRotation()">unfreezeRotation()</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="sleep()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">sleep</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>This method simply presses the power button if the screen is ON else
- it does nothing if the screen is already OFF.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipe(android.graphics.Point[], int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipe</span>
- <span class="normal">(Point[] segments, int segmentSteps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a swipe between points in the Point array. Each step execution is throttled
- to 5ms per step. So for a 100 steps, the swipe will take about 1/2 second to complete</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>segments</td>
- <td>is Point array containing at least one Point object</td>
- </tr>
- <tr>
- <th>segmentSteps</td>
- <td>steps to inject between two Points</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on success</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipe(int, int, int, int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipe</span>
- <span class="normal">(int startX, int startY, int endX, int endY, int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a swipe from one coordinate to another using the number of steps
- to determine smoothness and speed. Each step execution is throttled to 5ms
- per step. So for a 100 steps, the swipe will take about 1/2 second to complete.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>is the number of move steps sent to the system</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>false if the operation fails or the coordinates are invalid</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="takeScreenshot(java.io.File)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">takeScreenshot</span>
- <span class="normal">(File storePath)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Take a screenshot of current window and store it as PNG
-
- Default scale of 1.0f (original size) and 90% quality is used
- The screenshot is adjusted per screen rotation</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>storePath</td>
- <td>where the PNG should be written to</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if screen shot is created successfully, false otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="takeScreenshot(java.io.File, float, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">takeScreenshot</span>
- <span class="normal">(File storePath, float scale, int quality)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Take a screenshot of current window and store it as PNG
-
- The screenshot is adjusted per screen rotation</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>storePath</td>
- <td>where the PNG should be written to</td>
- </tr>
- <tr>
- <th>scale</td>
- <td>scale the screenshot down if needed; 1.0f for original size</td>
- </tr>
- <tr>
- <th>quality</td>
- <td>quality of the PNG compression; range: 0-100</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if screen shot is created successfully, false otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="unfreezeRotation()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">unfreezeRotation</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Re-enables the sensors and un-freezes the device rotation allowing its contents
- to rotate with the device physical rotation. During a test execution, it is best to
- keep the device frozen in a specific orientation until the test case execution has completed.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="waitForIdle(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">waitForIdle</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits for the current application to idle.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>in milliseconds</td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="waitForIdle()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">waitForIdle</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits for the current application to idle.
- Default wait timeout is 10 seconds</p></div>
-
- </div>
-</div>
-
-
-<A NAME="waitForWindowUpdate(java.lang.String, long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">waitForWindowUpdate</span>
- <span class="normal">(String packageName, long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits for a window content update event to occur.
-
- If a package name for the window is specified, but the current window
- does not have the same package name, the function returns immediately.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>packageName</td>
- <td>the specified window package name (can be <code>null</code>).
- If <code>null</code>, a window update from any front-end window will end the wait</td>
- </tr>
- <tr>
- <th>timeout</td>
- <td>the timeout for the wait</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if a window update occurred, false if timeout has elapsed or if the current
- window does not have the specified package name</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="wakeUp()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">wakeUp</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>This method simulates pressing the power button if the screen is OFF else
- it does nothing if the screen is already ON.
-
- If the screen was OFF and it just got turned ON, this method will insert a 500ms delay
- to allow the device time to wake up and accept input.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th></td>
- <td>RemoteException</td>
- </tr>
- <tr>
- <th>RemoteException</td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-
-
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-
-
-
-
+++ /dev/null
-page.title=UiObject
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>A <code><a href="#">UiObject</a></code> is a representation of a view. It is
-not in any way directly bound to a view as an object reference. A <code><a href="#">UiObject</a></code>
-contains information to help it locate a matching view at runtime based on the
-<code><a href="#UiSelector.html">UiSelector</a></code> properties specified in
-its constructor. Once you create an instance of a UiObject, it can be reused for
-different views that match the selector criteria.</p>
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- =========== ENUM CONSTANT SUMMARY =========== -->
-<table id="constants" class="jd-sumtable"><tr><th colspan="12">Constants</th></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">int</td>
- <td class="jd-linkcol"><a href="#FINGER_TOUCH_HALF_WIDTH">FINGER_TOUCH_HALF_WIDTH</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">int</td>
- <td class="jd-linkcol"><a href="#SWIPE_MARGIN_LIMIT">SWIPE_MARGIN_LIMIT</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="#WAIT_FOR_EVENT_TMEOUT">WAIT_FOR_EVENT_TMEOUT</a></td>
- <td class="jd-descrcol" width="100%"><em>
- This constant is deprecated.
- use <code><a href="Configurator.html#setScrollAcknowledgmentTimeout(long)">setScrollAcknowledgmentTimeout(long)</a></code>
-</em></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="#WAIT_FOR_SELECTOR_POLL">WAIT_FOR_SELECTOR_POLL</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="#WAIT_FOR_SELECTOR_TIMEOUT">WAIT_FOR_SELECTOR_TIMEOUT</a></td>
- <td class="jd-descrcol" width="100%"><em>
- This constant is deprecated.
- use <code><a href="Configurator.html#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout(long)</a></code>
-</em></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="#WAIT_FOR_WINDOW_TMEOUT">WAIT_FOR_WINDOW_TMEOUT</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#UiObject(com.android.uiautomator.core.UiSelector)">UiObject</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Constructs a UiObject to represent a view that matches the specified
- selector criteria.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clearTextField()">clearTextField</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clears the existing text contents in an editable field.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#click()">click</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clickAndWaitForNewWindow(long)">clickAndWaitForNewWindow</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject and waits for window transitions.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clickAndWaitForNewWindow()">clickAndWaitForNewWindow</a></span>()</nobr>
-
- <div class="jd-descrdiv">Waits for window transitions that would typically take longer than the
- usual default timeouts.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clickBottomRight()">clickBottomRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clicks the bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clickTopLeft()">clickTopLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clicks the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#dragTo(com.android.uiautomator.core.UiObject, int)">dragTo</a></span>(<a href="#">UiObject</a> destObj, int steps)</nobr>
-
- <div class="jd-descrdiv">Drags this object to a destination UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#dragTo(int, int, int)">dragTo</a></span>(int destX, int destY, int steps)</nobr>
-
- <div class="jd-descrdiv">Drags this object to arbitrary coordinates.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#exists()">exists</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if view exists.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Rect</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getBounds()">getBounds</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the view's <code>bounds</code> property.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChild(com.android.uiautomator.core.UiSelector)">getChild</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Creates a new UiObject for a child view that is under the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildCount()">getChildCount</a></span>()</nobr>
-
- <div class="jd-descrdiv">Counts the child views immediately under the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getClassName()">getClassName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves the <code>className</code> property of the UI element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getContentDescription()">getContentDescription</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the <code>content_desc</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getFromParent(com.android.uiautomator.core.UiSelector)">getFromParent</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Creates a new UiObject for a sibling view or a child of the sibling view,
- relative to the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getPackageName()">getPackageName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the view's <code>package</code> property</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- <a href="UiSelector.html">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getSelector()">getSelector</a></span>()</nobr>
-
- <div class="jd-descrdiv">Debugging helper.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getText()">getText</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the <code>text</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Rect</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getVisibleBounds()">getVisibleBounds</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the visible bounds of the view.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isCheckable()">isCheckable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>checkable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isChecked()">isChecked</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>checked</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isClickable()">isClickable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>clickable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isEnabled()">isEnabled</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>enabled</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isFocusable()">isFocusable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>focusable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isFocused()">isFocused</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>focused</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isLongClickable()">isLongClickable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the view's <code>long-clickable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isScrollable()">isScrollable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the view's <code>scrollable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#isSelected()">isSelected</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>selected</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#longClick()">longClick</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks the center of the visible bounds of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#longClickBottomRight()">longClickBottomRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#longClickTopLeft()">longClickTopLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks on the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#performMultiPointerGesture(android.view.MotionEvent.PointerCoords[]...)">performMultiPointerGesture</a></span>(PointerCoords... touches)</nobr>
-
- <div class="jd-descrdiv">Performs a multi-touch gesture.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#performTwoPointerGesture(android.graphics.Point, android.graphics.Point, android.graphics.Point, android.graphics.Point, int)">performTwoPointerGesture</a></span>(Point startPoint1, Point startPoint2, Point endPoint1, Point endPoint2, int steps)</nobr>
-
- <div class="jd-descrdiv">Generates a two-pointer gesture with arbitrary starting and ending points.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pinchIn(int, int)">pinchIn</a></span>(int percent, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a two-pointer gesture, where each pointer moves diagonally
- toward the other, from the edges to the center of this UiObject .</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#pinchOut(int, int)">pinchOut</a></span>(int percent, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a two-pointer gesture, where each pointer moves diagonally
- opposite across the other, from the center out towards the edges of the
- this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setText(java.lang.String)">setText</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Sets the text in an editable field, after clearing the field's content.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipeDown(int)">swipeDown</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe down action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipeLeft(int)">swipeLeft</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe left action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipeRight(int)">swipeRight</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe right action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#swipeUp(int)">swipeUp</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe up action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#waitForExists(long)">waitForExists</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits a specified length of time for a view to become visible.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#waitUntilGone(long)">waitUntilGone</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits a specified length of time for a view to become undetectable.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="promethods" class="jd-sumtable"><tr><th colspan="12">Protected Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- AccessibilityNodeInfo</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#findAccessibilityNodeInfo(long)">findAccessibilityNodeInfo</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Finds a matching UI element in the accessibility hierarchy, by
- using the selector for this UiObject.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Object</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">clone</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">equals</span>(Object arg0)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">finalize</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- Class<?></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">getClass</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">hashCode</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notify</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notifyAll</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">toString</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0, int arg1)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0)</nobr>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- ========= ENUM CONSTANTS DETAIL ======== -->
-<h2>Constants</h2>
-
-
-
-
-<A NAME="FINGER_TOUCH_HALF_WIDTH"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- int
- </span>
- FINGER_TOUCH_HALF_WIDTH
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 20
- (0x00000014)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-<A NAME="SWIPE_MARGIN_LIMIT"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- int
- </span>
- SWIPE_MARGIN_LIMIT
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 5
- (0x00000005)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-<A NAME="WAIT_FOR_EVENT_TMEOUT"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- long
- </span>
- WAIT_FOR_EVENT_TMEOUT
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
- <p>
- <p class="caution"><strong>
- This constant is deprecated.</strong><br/>
- use <code><a href="Configurator.html#setScrollAcknowledgmentTimeout(long)">setScrollAcknowledgmentTimeout(long)</a></code>
-
- </p>
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 3000
- (0x0000000000000bb8)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-<A NAME="WAIT_FOR_SELECTOR_POLL"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- long
- </span>
- WAIT_FOR_SELECTOR_POLL
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 1000
- (0x00000000000003e8)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-<A NAME="WAIT_FOR_SELECTOR_TIMEOUT"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- long
- </span>
- WAIT_FOR_SELECTOR_TIMEOUT
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
- <p>
- <p class="caution"><strong>
- This constant is deprecated.</strong><br/>
- use <code><a href="Configurator.html#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout(long)</a></code>
-
- </p>
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 10000
- (0x0000000000002710)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-<A NAME="WAIT_FOR_WINDOW_TMEOUT"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
- static
- final
- long
- </span>
- WAIT_FOR_WINDOW_TMEOUT
- </h4>
- <div class="api-level">
-
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
-
- <div class="jd-tagdata">
- <span class="jd-tagtitle">Constant Value: </span>
- <span>
-
- 5500
- (0x000000000000157c)
-
- </span>
- </div>
-
- </div>
-</div>
-
-
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-
-<A NAME="UiObject(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiObject</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Constructs a UiObject to represent a view that matches the specified
- selector criteria.</p></div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<A NAME="clearTextField()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- void
- </span>
- <span class="sympad">clearTextField</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Clears the existing text contents in an editable field.
-
- The <code><a href="UiSelector.html">UiSelector</a></code> of this object must reference a UI element that is editable.
-
- When you call this method, the method first sets focus at the start edge of the field.
- The method then simulates a long-press to select the existing text, and deletes the
- selected text.
-
- If a "Select-All" option is displayed, the method will automatically attempt to use it
- to ensure full text selection.
-
- Note that it is possible that not all the text in the field is selected; for example,
- if the text contains separators such as spaces, slashes, at symbol etc.
- Also, not all editable fields support the long-press functionality.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="click()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">click</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true id successful else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="clickAndWaitForNewWindow(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">clickAndWaitForNewWindow</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject and waits for window transitions.
-
- This method differ from <code><a href="#click()">click()</a></code> only in that this method waits for a
- a new window transition as a result of the click. Some examples of a window transition:
- <li>launching a new activity</li>
- <li>bringing up a pop-up menu</li>
- <li>bringing up a dialog</li></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>timeout before giving up on waiting for a new window</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the event was triggered, else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="clickAndWaitForNewWindow()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">clickAndWaitForNewWindow</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits for window transitions that would typically take longer than the
- usual default timeouts.
- See <code><a href="#clickAndWaitForNewWindow(long)">clickAndWaitForNewWindow(long)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the event was triggered, else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="clickBottomRight()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">clickBottomRight</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Clicks the bottom and right corner of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on success</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="clickTopLeft()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">clickTopLeft</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Clicks the top and left corner of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on success</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="dragTo(com.android.uiautomator.core.UiObject, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">dragTo</span>
- <span class="normal">(<a href="#">UiObject</a> destObj, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Drags this object to a destination UiObject.
- The number of steps specified in your input parameter can influence the
- drag speed, and varying speeds may impact the results. Consider
- evaluating different speeds when using this method in your tests.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>destObj</td>
- <td>the destination UiObject.</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>usually 40 steps. You can increase or decrease the steps to change the speed.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="dragTo(int, int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">dragTo</span>
- <span class="normal">(int destX, int destY, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Drags this object to arbitrary coordinates.
- The number of steps specified in your input parameter can influence the
- drag speed, and varying speeds may impact the results. Consider
- evaluating different speeds when using this method in your tests.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>destX</td>
- <td>the X-axis coordinate.</td>
- </tr>
- <tr>
- <th>destY</td>
- <td>the Y-axis coordinate.</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>usually 40 steps. You can increase or decrease the steps to change the speed.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="exists()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">exists</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if view exists.
-
- This methods performs a <code><a href="#waitForExists(long)">waitForExists(long)</a></code> with zero timeout. This
- basically returns immediately whether the view represented by this UiObject
- exists or not. If you need to wait longer for this view, then see
- <code><a href="#waitForExists(long)">waitForExists(long)</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the view represented by this UiObject does exist</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getBounds()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- Rect
- </span>
- <span class="sympad">getBounds</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Returns the view's <code>bounds</code> property. See <code><a href="#getVisibleBounds()">getVisibleBounds()</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>Rect</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChild(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiObject</a>
- </span>
- <span class="sympad">getChild</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Creates a new UiObject for a child view that is under the present UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>selector</td>
- <td>for child view to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>a new UiObject representing the child view</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildCount()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- int
- </span>
- <span class="sympad">getChildCount</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Counts the child views immediately under the present UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>the count of child views.</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getClassName()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getClassName</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Retrieves the <code>className</code> property of the UI element.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>class name of the current node represented by this UiObject</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td>if no match was found</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="getContentDescription()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getContentDescription</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Reads the <code>content_desc</code> property of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>value of node attribute "content_desc"</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getFromParent(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiObject</a>
- </span>
- <span class="sympad">getFromParent</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Creates a new UiObject for a sibling view or a child of the sibling view,
- relative to the present UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>selector</td>
- <td>for a sibling view or children of the sibling view</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>a new UiObject representing the matched view</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getPackageName()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getPackageName</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Reads the view's <code>package</code> property</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getSelector()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
- final
-
-
- <a href="UiSelector.html">UiSelector</a>
- </span>
- <span class="sympad">getSelector</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Debugging helper. A test can dump the properties of a selector as a string
- to its logs if needed. <code>getSelector().toString();</code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiSelector.html">UiSelector</a></code></li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getText()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">getText</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Reads the <code>text</code> property of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>text value of the current node represented by this UiObject</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td>if no match could be found</td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getVisibleBounds()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- Rect
- </span>
- <span class="sympad">getVisibleBounds</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Returns the visible bounds of the view.
-
- If a portion of the view is visible, only the bounds of the visible portion are
- reported.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>Rect</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">See Also</h5>
- <ul class="nolist"><li><code><a href="#getBounds()">getBounds()</a></code></li>
- </ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="isCheckable()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isCheckable</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if the UI element's <code>checkable</code> property is currently true.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isChecked()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isChecked</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the UI element's <code>checked</code> property is currently true</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isClickable()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isClickable</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if the UI element's <code>clickable</code> property is currently true.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isEnabled()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isEnabled</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if the UI element's <code>enabled</code> property is currently true.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isFocusable()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isFocusable</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the UI element's <code>focusable</code> property is currently true.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isFocused()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isFocused</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the UI element's <code>focused</code> property is currently true</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isLongClickable()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isLongClickable</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the view's <code>long-clickable</code> property is currently true</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isScrollable()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isScrollable</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Check if the view's <code>scrollable</code> property is currently true</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="isSelected()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">isSelected</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Checks if the UI element's <code>selected</code> property is currently true.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if it is else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="longClick()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">longClick</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Long clicks the center of the visible bounds of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if operation was successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="longClickBottomRight()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">longClickBottomRight</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Long clicks bottom and right corner of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if operation was successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="longClickTopLeft()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">longClickTopLeft</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Long clicks on the top and left corner of the UI element</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if operation was successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="performMultiPointerGesture(android.view.MotionEvent.PointerCoords[]...)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">performMultiPointerGesture</span>
- <span class="normal">(PointerCoords... touches)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a multi-touch gesture. You must specify touch coordinates for
- at least 2 pointers. Each pointer must have all of its touch steps
- defined in an array of <code><a href="../../../../../reference/android/view/MotionEvent.PointerCoords.html">MotionEvent.PointerCoords</a></code>. You can use this method to
- specify complex gestures, like circles and irregular shapes, where each
- pointer may take a different path.
-
- To create a single point on a pointer's touch path:
- <code>
- PointerCoords p = new PointerCoords();
- p.x = stepX;
- p.y = stepY;
- p.pressure = 1;
- p.size = 1;
- </code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>touches</td>
- <td>represents the pointers' paths. Each <code><a href="../../../../../reference/android/view/MotionEvent.PointerCoords.html">MotionEvent.PointerCoords</a></code>
- array represents a different pointer. Each <code><a href="../../../../../reference/android/view/MotionEvent.PointerCoords.html">MotionEvent.PointerCoords</a></code> in an
- array element represents a touch point on a pointer's path.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code>true</code> if all touch events for this gesture are injected successfully,
- <code>false</code> otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="performTwoPointerGesture(android.graphics.Point, android.graphics.Point, android.graphics.Point, android.graphics.Point, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">performTwoPointerGesture</span>
- <span class="normal">(Point startPoint1, Point startPoint2, Point endPoint1, Point endPoint2, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Generates a two-pointer gesture with arbitrary starting and ending points.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>startPoint1</td>
- <td>start point of pointer 1</td>
- </tr>
- <tr>
- <th>startPoint2</td>
- <td>start point of pointer 2</td>
- </tr>
- <tr>
- <th>endPoint1</td>
- <td>end point of pointer 1</td>
- </tr>
- <tr>
- <th>endPoint2</td>
- <td>end point of pointer 2</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>the number of steps for the gesture. Steps are injected
- about 5 milliseconds apart, so 100 steps may take around 0.5 seconds to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code>true</code> if all touch events for this gesture are injected successfully,
- <code>false</code> otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="pinchIn(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pinchIn</span>
- <span class="normal">(int percent, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a two-pointer gesture, where each pointer moves diagonally
- toward the other, from the edges to the center of this UiObject .</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>percent</td>
- <td>percentage of the object's diagonal length for the pinch gesture</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>the number of steps for the gesture. Steps are injected
- about 5 milliseconds apart, so 100 steps may take around 0.5 seconds to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code>true</code> if all touch events for this gesture are injected successfully,
- <code>false</code> otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="pinchOut(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">pinchOut</span>
- <span class="normal">(int percent, int steps)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a two-pointer gesture, where each pointer moves diagonally
- opposite across the other, from the center out towards the edges of the
- this UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>percent</td>
- <td>percentage of the object's diagonal length for the pinch gesture</td>
- </tr>
- <tr>
- <th>steps</td>
- <td>the number of steps for the gesture. Steps are injected
- about 5 milliseconds apart, so 100 steps may take around 0.5 seconds to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code>true</code> if all touch events for this gesture are injected successfully,
- <code>false</code> otherwise</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="setText(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">setText</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the text in an editable field, after clearing the field's content.
-
- The <code><a href="UiSelector.html">UiSelector</a></code> selector of this object must reference a UI element that is editable.
-
- When you call this method, the method first simulates a <code><a href="#click()">click()</a></code> on
- editable field to set focus. The method then clears the field's contents
- and injects your specified text into the field.
-
- If you want to capture the original contents of the field, call <code><a href="#getText()">getText()</a></code> first.
- You can then modify the text and use this method to update the field.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>string to set</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if operation is successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipeDown(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipeDown</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs the swipe down action on the UiObject.
- The swipe gesture can be performed over any surface. The targeted
- UI element does not need to be scrollable.
- See also:
- <ul>
- <li><code><a href="UiScrollable.html#scrollToBeginning(int)">scrollToBeginning(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollToEnd(int)">scrollToEnd(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollBackward()">scrollBackward()</a></code></li>
- <li><code><a href="UiScrollable.html#scrollForward()">scrollForward()</a></code></li>
- </ul></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>indicates the number of injected move steps into the system. Steps are
- injected about 5ms apart. So a 100 steps may take about 1/2 second to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipeLeft(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipeLeft</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs the swipe left action on the UiObject.
- The swipe gesture can be performed over any surface. The targeted
- UI element does not need to be scrollable.
- See also:
- <ul>
- <li><code><a href="UiScrollable.html#scrollToBeginning(int)">scrollToBeginning(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollToEnd(int)">scrollToEnd(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollBackward()">scrollBackward()</a></code></li>
- <li><code><a href="UiScrollable.html#scrollForward()">scrollForward()</a></code></li>
- </ul></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>indicates the number of injected move steps into the system. Steps are
- injected about 5ms apart. So a 100 steps may take about 1/2 second to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipeRight(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipeRight</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs the swipe right action on the UiObject.
- The swipe gesture can be performed over any surface. The targeted
- UI element does not need to be scrollable.
- See also:
- <ul>
- <li><code><a href="UiScrollable.html#scrollToBeginning(int)">scrollToBeginning(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollToEnd(int)">scrollToEnd(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollBackward()">scrollBackward()</a></code></li>
- <li><code><a href="UiScrollable.html#scrollForward()">scrollForward()</a></code></li>
- </ul></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>indicates the number of injected move steps into the system. Steps are
- injected about 5ms apart. So a 100 steps may take about 1/2 second to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="swipeUp(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">swipeUp</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs the swipe up action on the UiObject.
- See also:
- <ul>
- <li><code><a href="UiScrollable.html#scrollToBeginning(int)">scrollToBeginning(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollToEnd(int)">scrollToEnd(int)</a></code></li>
- <li><code><a href="UiScrollable.html#scrollBackward()">scrollBackward()</a></code></li>
- <li><code><a href="UiScrollable.html#scrollForward()">scrollForward()</a></code></li>
- </ul></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>indicates the number of injected move steps into the system. Steps are
- injected about 5ms apart. So a 100 steps may take about 1/2 second to complete.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true of successful</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="waitForExists(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">waitForExists</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits a specified length of time for a view to become visible.
-
- This method waits until the view becomes visible on the display, or
- until the timeout has elapsed. You can use this method in situations where
- the content that you want to select is not immediately displayed.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>the amount of time to wait (in milliseconds)</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the view is displayed, else false if timeout elapsed while waiting</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="waitUntilGone(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">waitUntilGone</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Waits a specified length of time for a view to become undetectable.
-
- This method waits until a view is no longer matchable, or until the
- timeout has elapsed.
-
- A view becomes undetectable when the <code><a href="UiSelector.html">UiSelector</a></code> of the object is
- unable to find a match because the element has either changed its state or is no
- longer displayed.
-
- You can use this method when attempting to wait for some long operation
- to compete, such as downloading a large file or connecting to a remote server.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>time to wait (in milliseconds)</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the element is gone before timeout elapsed, else false if timeout elapsed
- but a matching element is still found.</li></ul>
- </div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-
-<h2>Protected Methods</h2>
-
-
-
-<A NAME="findAccessibilityNodeInfo(long)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
-
-
-
-
- AccessibilityNodeInfo
- </span>
- <span class="sympad">findAccessibilityNodeInfo</span>
- <span class="normal">(long timeout)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Finds a matching UI element in the accessibility hierarchy, by
- using the selector for this UiObject.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>timeout</td>
- <td>in milliseconds</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>AccessibilityNodeInfo if found else null</li></ul>
- </div>
-
- </div>
-
-
-
-
-
-
+++ /dev/null
-page.title=UiObjectNotFoundException
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>Generated in test runs when a <code><a href="UiSelector.html">UiSelector</a></code> selector could not be matched
- to any UI element displayed.
-</p>
-
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
-
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#UiObjectNotFoundException(java.lang.String)">UiObjectNotFoundException</a></span>(String msg)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
-
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#UiObjectNotFoundException(java.lang.String, java.lang.Throwable)">UiObjectNotFoundException</a></span>(String detailMessage, Throwable throwable)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
-
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#UiObjectNotFoundException(java.lang.Throwable)">UiObjectNotFoundException</a></span>(Throwable throwable)
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Throwable" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Throwable-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Throwable
-
-<div id="inherited-methods-java.lang.Throwable">
- <div id="inherited-methods-java.lang.Throwable-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Throwable-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
- synchronized
-
-
-
- Throwable
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">fillInStackTrace</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- Throwable
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getCause</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getLocalizedMessage</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getMessage</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- StackTraceElement[]
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getStackTrace</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
- synchronized
-
-
-
- Throwable
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">initCause</span>(Throwable arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">printStackTrace</span>(PrintWriter arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">printStackTrace</span>(PrintStream arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">printStackTrace</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">setStackTrace</span>(StackTraceElement[] arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">toString</span>()
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api apilevel-" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">equals</span>(Object arg0)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- Class<?>
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">getClass</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- int
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">hashCode</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notify</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">notifyAll</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
-
-
-
- String
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">toString</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>()
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0, int arg1)
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
-
-
- final
-
-
- void
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad">wait</span>(long arg0)
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-
-<a id="UiObjectNotFoundException(java.lang.String)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiObjectNotFoundException</span>
- <span class="normal">(String msg)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-<a id="UiObjectNotFoundException(java.lang.String, java.lang.Throwable)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiObjectNotFoundException</span>
- <span class="normal">(String detailMessage, Throwable throwable)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-<a id="UiObjectNotFoundException(java.lang.Throwable)"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiObjectNotFoundException</span>
- <span class="normal">(Throwable throwable)</span>
- </h4>
- <div class="api-level">
- <div>
-
-</div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
+++ /dev/null
-page.title=UiScrollable
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>A <code><a href="UiCollection.html">UiCollection</a></code>
-that supports searching for items in scrollable layout elements. This class can
-be used with horizontally or vertically scrollable controls.</p>
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- =========== ENUM CONSTANT SUMMARY =========== -->
-<table id="inhconstants" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Constants</div></th></tr>
-
-
-
-
-<tr class="api" >
-<td colspan="12">
-
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-constants-com.android.uiautomator.core.UiObject" class="jd-expando-trigger closed"
- ><img id="inherited-constants-com.android.uiautomator.core.UiObject-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>From class
-<a href="UiObject.html">com.android.uiautomator.core.UiObject</a>
-<div id="inherited-constants-com.android.uiautomator.core.UiObject">
- <div id="inherited-constants-com.android.uiautomator.core.UiObject-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-constants-com.android.uiautomator.core.UiObject-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
- <tr class="api" >
- <td class="jd-typecol">int</td>
- <td class="jd-linkcol"><a href="UiObject.html#FINGER_TOUCH_HALF_WIDTH">FINGER_TOUCH_HALF_WIDTH</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">int</td>
- <td class="jd-linkcol"><a href="UiObject.html#SWIPE_MARGIN_LIMIT">SWIPE_MARGIN_LIMIT</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="UiObject.html#WAIT_FOR_EVENT_TMEOUT">WAIT_FOR_EVENT_TMEOUT</a></td>
- <td class="jd-descrcol" width="100%"><em>
- This constant is deprecated.
- use <code><a href="Configurator.html#setScrollAcknowledgmentTimeout(long)">setScrollAcknowledgmentTimeout(long)</a></code>
-</em></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="UiObject.html#WAIT_FOR_SELECTOR_POLL">WAIT_FOR_SELECTOR_POLL</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="UiObject.html#WAIT_FOR_SELECTOR_TIMEOUT">WAIT_FOR_SELECTOR_TIMEOUT</a></td>
- <td class="jd-descrcol" width="100%"><em>
- This constant is deprecated.
- use <code><a href="Configurator.html#setWaitForSelectorTimeout(long)">setWaitForSelectorTimeout(long)</a></code>
-</em></td>
- </tr>
-
-
- <tr class="api" >
- <td class="jd-typecol">long</td>
- <td class="jd-linkcol"><a href="UiObject.html#WAIT_FOR_WINDOW_TMEOUT">WAIT_FOR_WINDOW_TMEOUT</a></td>
- <td class="jd-descrcol" width="100%"></td>
- </tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-
-</table>
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#UiScrollable(com.android.uiautomator.core.UiSelector)">UiScrollable</a></span>(<a href="UiSelector.html">UiSelector</a> container)</nobr>
-
- <div class="jd-descrdiv">Constructor.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#flingBackward()">flingBackward</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a backwards fling action with the default number of fling
- steps (5).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#flingForward()">flingForward</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a forward fling with the default number of fling steps (5).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#flingToBeginning(int)">flingToBeginning</a></span>(int maxSwipes)</nobr>
-
- <div class="jd-descrdiv">Performs a fling gesture to reach the beginning of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#flingToEnd(int)">flingToEnd</a></span>(int maxSwipes)</nobr>
-
- <div class="jd-descrdiv">Performs a fling gesture to reach the end of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)">getChildByDescription</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text, boolean allowScrollSearch)</nobr>
-
- <div class="jd-descrdiv">Searches for a child element in the present scrollable container.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByDescription</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</nobr>
-
- <div class="jd-descrdiv">Searches for a child element in the present scrollable container.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildByInstance(com.android.uiautomator.core.UiSelector, int)">getChildByInstance</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, int instance)</nobr>
-
- <div class="jd-descrdiv">Searches for a child element in the present scrollable container that
- matches the selector you provided.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)">getChildByText</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text, boolean allowScrollSearch)</nobr>
-
- <div class="jd-descrdiv">Searches for a child element in the present scrollable container.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByText</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</nobr>
-
- <div class="jd-descrdiv">Searches for a child element in the present scrollable
- container.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getMaxSearchSwipes()">getMaxSearchSwipes</a></span>()</nobr>
-
- <div class="jd-descrdiv">Gets the maximum number of scrolls allowed when performing a
- scroll action in search of a child element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- double</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#getSwipeDeadZonePercentage()">getSwipeDeadZonePercentage</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the percentage of a widget's size that's considered as a no-touch
- zone when swiping.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollBackward(int)">scrollBackward</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a backward scroll.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollBackward()">scrollBackward</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a backward scroll with the default number of scroll steps (55).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollDescriptionIntoView(java.lang.String)">scrollDescriptionIntoView</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Performs a forward scroll action on the scrollable layout element until
- the content-description is found, or until swipe attempts have been exhausted.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollForward()">scrollForward</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a forward scroll with the default number of scroll steps (55).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollForward(int)">scrollForward</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a forward scroll.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollIntoView(com.android.uiautomator.core.UiSelector)">scrollIntoView</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Perform a scroll forward action to move through the scrollable layout
- element until a visible item that matches the selector is found.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollIntoView(com.android.uiautomator.core.UiObject)">scrollIntoView</a></span>(<a href="UiObject.html">UiObject</a> obj)</nobr>
-
- <div class="jd-descrdiv">Perform a forward scroll action to move through the scrollable layout element until
- a visible item that matches the <code><a href="UiObject.html">UiObject</a></code> is found.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollTextIntoView(java.lang.String)">scrollTextIntoView</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Performs a forward scroll action on the scrollable layout element until
- the text you provided is visible, or until swipe attempts have been exhausted.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollToBeginning(int)">scrollToBeginning</a></span>(int maxSwipes)</nobr>
-
- <div class="jd-descrdiv">Scrolls to the beginning of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollToBeginning(int, int)">scrollToBeginning</a></span>(int maxSwipes, int steps)</nobr>
-
- <div class="jd-descrdiv">Scrolls to the beginning of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollToEnd(int, int)">scrollToEnd</a></span>(int maxSwipes, int steps)</nobr>
-
- <div class="jd-descrdiv">Scrolls to the end of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollToEnd(int)">scrollToEnd</a></span>(int maxSwipes)</nobr>
-
- <div class="jd-descrdiv">Scrolls to the end of a scrollable layout element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiScrollable</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setAsHorizontalList()">setAsHorizontalList</a></span>()</nobr>
-
- <div class="jd-descrdiv">Set the direction of swipes to be horizontal when performing scroll actions.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiScrollable</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setAsVerticalList()">setAsVerticalList</a></span>()</nobr>
-
- <div class="jd-descrdiv">Set the direction of swipes to be vertical when performing scroll actions.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiScrollable</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setMaxSearchSwipes(int)">setMaxSearchSwipes</a></span>(int swipes)</nobr>
-
- <div class="jd-descrdiv">Sets the maximum number of scrolls allowed when performing a
- scroll action in search of a child element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiScrollable</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#setSwipeDeadZonePercentage(double)">setSwipeDeadZonePercentage</a></span>(double swipeDeadZonePercentage)</nobr>
-
- <div class="jd-descrdiv">Sets the percentage of a widget's size that's considered as no-touch
- zone when swiping.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="promethods" class="jd-sumtable"><tr><th colspan="12">Protected Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#exists(com.android.uiautomator.core.UiSelector)">exists</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Used privately when performing swipe searches to decide if an element has become
- visible or not.</div>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-com.android.uiautomator.core.UiCollection" class="jd-expando-trigger closed"
- ><img id="inherited-methods-com.android.uiautomator.core.UiCollection-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- <a href="UiCollection.html">com.android.uiautomator.core.UiCollection</a>
-
-<div id="inherited-methods-com.android.uiautomator.core.UiCollection">
- <div id="inherited-methods-com.android.uiautomator.core.UiCollection-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-com.android.uiautomator.core.UiCollection-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiCollection.html#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByDescription</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</nobr>
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this UiCollection <code><a href="UiSelector.html">UiSelector</a></code>
- selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiCollection.html#getChildByInstance(com.android.uiautomator.core.UiSelector, int)">getChildByInstance</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, int instance)</nobr>
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this UiCollection <code><a href="UiSelector.html">UiSelector</a></code>
- selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiCollection.html#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByText</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</nobr>
-
- <div class="jd-descrdiv">Searches for child UI element within the constraints of this UiCollection <code><a href="UiSelector.html">UiSelector</a></code>
- selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiCollection.html#getChildCount(com.android.uiautomator.core.UiSelector)">getChildCount</a></span>(<a href="UiSelector.html">UiSelector</a> childPattern)</nobr>
-
- <div class="jd-descrdiv">Counts child UI element instances matching the <code>childPattern</code>
- argument.</div>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-com.android.uiautomator.core.UiObject" class="jd-expando-trigger closed"
- ><img id="inherited-methods-com.android.uiautomator.core.UiObject-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- <a href="UiObject.html">com.android.uiautomator.core.UiObject</a>
-
-<div id="inherited-methods-com.android.uiautomator.core.UiObject">
- <div id="inherited-methods-com.android.uiautomator.core.UiObject-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-com.android.uiautomator.core.UiObject-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#clearTextField()">clearTextField</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clears the existing text contents in an editable field.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#click()">click</a></span>()</nobr>
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#clickAndWaitForNewWindow(long)">clickAndWaitForNewWindow</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element represented
- by this UiObject and waits for window transitions.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#clickAndWaitForNewWindow()">clickAndWaitForNewWindow</a></span>()</nobr>
-
- <div class="jd-descrdiv">Waits for window transitions that would typically take longer than the
- usual default timeouts.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#clickBottomRight()">clickBottomRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clicks the bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#clickTopLeft()">clickTopLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Clicks the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#dragTo(com.android.uiautomator.core.UiObject, int)">dragTo</a></span>(<a href="UiObject.html">UiObject</a> destObj, int steps)</nobr>
-
- <div class="jd-descrdiv">Drags this object to a destination UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#dragTo(int, int, int)">dragTo</a></span>(int destX, int destY, int steps)</nobr>
-
- <div class="jd-descrdiv">Drags this object to arbitrary coordinates.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#exists()">exists</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if view exists.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- AccessibilityNodeInfo</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#findAccessibilityNodeInfo(long)">findAccessibilityNodeInfo</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Finds a matching UI element in the accessibility hierarchy, by
- using the selector for this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Rect</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getBounds()">getBounds</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the view's <code>bounds</code> property.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getChild(com.android.uiautomator.core.UiSelector)">getChild</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Creates a new UiObject for a child view that is under the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getChildCount()">getChildCount</a></span>()</nobr>
-
- <div class="jd-descrdiv">Counts the child views immediately under the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getClassName()">getClassName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Retrieves the <code>className</code> property of the UI element.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getContentDescription()">getContentDescription</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the <code>content_desc</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="UiObject.html">UiObject</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getFromParent(com.android.uiautomator.core.UiSelector)">getFromParent</a></span>(<a href="UiSelector.html">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Creates a new UiObject for a sibling view or a child of the sibling view,
- relative to the present UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getPackageName()">getPackageName</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the view's <code>package</code> property</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- <a href="UiSelector.html">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getSelector()">getSelector</a></span>()</nobr>
-
- <div class="jd-descrdiv">Debugging helper.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getText()">getText</a></span>()</nobr>
-
- <div class="jd-descrdiv">Reads the <code>text</code> property of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Rect</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#getVisibleBounds()">getVisibleBounds</a></span>()</nobr>
-
- <div class="jd-descrdiv">Returns the visible bounds of the view.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isCheckable()">isCheckable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>checkable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isChecked()">isChecked</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>checked</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isClickable()">isClickable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>clickable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isEnabled()">isEnabled</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>enabled</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isFocusable()">isFocusable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>focusable</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isFocused()">isFocused</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the UI element's <code>focused</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isLongClickable()">isLongClickable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the view's <code>long-clickable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isScrollable()">isScrollable</a></span>()</nobr>
-
- <div class="jd-descrdiv">Check if the view's <code>scrollable</code> property is currently true</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#isSelected()">isSelected</a></span>()</nobr>
-
- <div class="jd-descrdiv">Checks if the UI element's <code>selected</code> property is currently true.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#longClick()">longClick</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks the center of the visible bounds of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#longClickBottomRight()">longClickBottomRight</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks bottom and right corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#longClickTopLeft()">longClickTopLeft</a></span>()</nobr>
-
- <div class="jd-descrdiv">Long clicks on the top and left corner of the UI element</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#performMultiPointerGesture(android.view.MotionEvent.PointerCoords[]...)">performMultiPointerGesture</a></span>(PointerCoords... touches)</nobr>
-
- <div class="jd-descrdiv">Performs a multi-touch gesture.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#performTwoPointerGesture(android.graphics.Point, android.graphics.Point, android.graphics.Point, android.graphics.Point, int)">performTwoPointerGesture</a></span>(Point startPoint1, Point startPoint2, Point endPoint1, Point endPoint2, int steps)</nobr>
-
- <div class="jd-descrdiv">Generates a two-pointer gesture with arbitrary starting and ending points.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#pinchIn(int, int)">pinchIn</a></span>(int percent, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a two-pointer gesture, where each pointer moves diagonally
- toward the other, from the edges to the center of this UiObject .</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#pinchOut(int, int)">pinchOut</a></span>(int percent, int steps)</nobr>
-
- <div class="jd-descrdiv">Performs a two-pointer gesture, where each pointer moves diagonally
- opposite across the other, from the center out towards the edges of the
- this UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#setText(java.lang.String)">setText</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Sets the text in an editable field, after clearing the field's content.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#swipeDown(int)">swipeDown</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe down action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#swipeLeft(int)">swipeLeft</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe left action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#swipeRight(int)">swipeRight</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe right action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#swipeUp(int)">swipeUp</a></span>(int steps)</nobr>
-
- <div class="jd-descrdiv">Performs the swipe up action on the UiObject.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#waitForExists(long)">waitForExists</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits a specified length of time for a view to become visible.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="UiObject.html#waitUntilGone(long)">waitUntilGone</a></span>(long timeout)</nobr>
-
- <div class="jd-descrdiv">Waits a specified length of time for a view to become undetectable.</div>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Object</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">clone</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">equals</span>(Object arg0)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">finalize</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- Class<?></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">getClass</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">hashCode</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notify</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notifyAll</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">toString</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0, int arg1)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0)</nobr>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-
-<A NAME="UiScrollable(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiScrollable</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> container)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Constructor.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>container</td>
- <td>a <code><a href="UiSelector.html">UiSelector</a></code> selector to identify the scrollable
- layout element.</td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<A NAME="flingBackward()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">flingBackward</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a backwards fling action with the default number of fling
- steps (5). If the swipe direction is set to vertical,
- then the swipe will be performed from top to bottom. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- left to right. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, and false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="flingForward()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">flingForward</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a forward fling with the default number of fling steps (5).
- If the swipe direction is set to vertical, then the swipes will be
- performed from bottom to top. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- right to left. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="flingToBeginning(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">flingToBeginning</span>
- <span class="normal">(int maxSwipes)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a fling gesture to reach the beginning of a scrollable layout element.
- The beginning can be at the top-most edge in the case of vertical controls, or
- the left-most edge for horizontal controls. Make sure to take into
- account devices configured with right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="flingToEnd(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">flingToEnd</span>
- <span class="normal">(int maxSwipes)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a fling gesture to reach the end of a scrollable layout element.
- The end can be at the bottom-most edge in the case of vertical controls, or
- the right-most edge for horizontal controls. Make sure to take into
- account devices configured with right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled, else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByDescription</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text, boolean allowScrollSearch)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for a child element in the present scrollable container.
- The search first looks for a child element that matches the selector
- you provided, then looks for the content-description in its children elements.
- If both search conditions are fulfilled, the method returns a {@ link UiObject}
- representing the element matching the selector (not the child element in its
- subhierarchy containing the content-description).</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> for a child in a scollable layout element</td>
- </tr>
- <tr>
- <th>text</td>
- <td>Content-description to find in the children of
- the <code>childPattern</code> match (may be a partial match)</td>
- </tr>
- <tr>
- <th>allowScrollSearch</td>
- <td>set to true if scrolling is allowed</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> representing the child element that matches the search conditions</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByDescription</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for a child element in the present scrollable container.
- The search first looks for a child element that matches the selector
- you provided, then looks for the content-description in its children elements.
- If both search conditions are fulfilled, the method returns a {@ link UiObject}
- representing the element matching the selector (not the child element in its
- subhierarchy containing the content-description). By default, this method performs a
- scroll search.
- See <code><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)">getChildByDescription(UiSelector, String, boolean)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> for a child in a scollable layout element</td>
- </tr>
- <tr>
- <th>text</td>
- <td>Content-description to find in the children of
- the <code>childPattern</code> match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> representing the child element that matches the search conditions</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildByInstance(com.android.uiautomator.core.UiSelector, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByInstance</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, int instance)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for a child element in the present scrollable container that
- matches the selector you provided. The search is performed without
- scrolling and only on visible elements.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> for a child in a scollable layout element</td>
- </tr>
- <tr>
- <th>instance</td>
- <td>int number representing the occurance of
- a <code>childPattern</code> match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> representing the child element that matches the search conditions</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByText</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text, boolean allowScrollSearch)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for a child element in the present scrollable container. The
- search first looks for a child element that matches the
- selector you provided, then looks for the text in its children elements.
- If both search conditions are fulfilled, the method returns a {@ link UiObject}
- representing the element matching the selector (not the child element in its
- subhierarchy containing the text).</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector for a child in a scrollable layout element</td>
- </tr>
- <tr>
- <th>text</td>
- <td>String to find in the children of the <code>childPattern</code> match</td>
- </tr>
- <tr>
- <th>allowScrollSearch</td>
- <td>set to true if scrolling is allowed</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> representing the child element that matches the search conditions</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="UiObject.html">UiObject</a>
- </span>
- <span class="sympad">getChildByText</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> childPattern, String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Searches for a child element in the present scrollable
- container. The search first looks for a child element that matches the
- selector you provided, then looks for the text in its children elements.
- If both search conditions are fulfilled, the method returns a {@ link UiObject}
- representing the element matching the selector (not the child element in its
- subhierarchy containing the text). By default, this method performs a
- scroll search.
- See <code><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String, boolean)">getChildByText(UiSelector, String, boolean)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>childPattern</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector for a child in a scrollable layout element</td>
- </tr>
- <tr>
- <th>text</td>
- <td>String to find in the children of the <code>childPattern</code> match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li><code><a href="UiObject.html">UiObject</a></code> representing the child element that matches the search conditions</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
-
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getMaxSearchSwipes()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- int
- </span>
- <span class="sympad">getMaxSearchSwipes</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Gets the maximum number of scrolls allowed when performing a
- scroll action in search of a child element.
- See <code><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByDescription(UiSelector, String)</a></code> and
- <code><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByText(UiSelector, String)</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>max the number of search swipes to perform until giving up</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="getSwipeDeadZonePercentage()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- double
- </span>
- <span class="sympad">getSwipeDeadZonePercentage</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Returns the percentage of a widget's size that's considered as a no-touch
- zone when swiping. The no-touch zone is set as a percentage of a widget's total
- width or height, denoting a margin around the swipable area of the widget.
- Swipes must start and end inside this margin. This is important when the
- widget being swiped may not respond to the swipe if started at a point
- too near to the edge. The default is 10% from either edge.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>a value between 0 and 1</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollBackward(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollBackward</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a backward scroll. If the swipe direction is set to vertical,
- then the swipes will be performed from top to bottom. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- left to right. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>number of steps. Use this to control the speed of the scroll action.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollBackward()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollBackward</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a backward scroll with the default number of scroll steps (55).
- If the swipe direction is set to vertical,
- then the swipes will be performed from top to bottom. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- left to right. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, and false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollDescriptionIntoView(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollDescriptionIntoView</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a forward scroll action on the scrollable layout element until
- the content-description is found, or until swipe attempts have been exhausted.
- See <code><a href="#setMaxSearchSwipes(int)">setMaxSearchSwipes(int)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>content-description to find within the contents of this scrollable layout element.</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if item is found; else, false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollForward()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollForward</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a forward scroll with the default number of scroll steps (55).
- If the swipe direction is set to vertical,
- then the swipes will be performed from bottom to top. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- right to left. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollForward(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollForward</span>
- <span class="normal">(int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a forward scroll. If the swipe direction is set to vertical,
- then the swipes will be performed from bottom to top. If the swipe
- direction is set to horizontal, then the swipes will be performed from
- right to left. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>number of steps. Use this to control the speed of the scroll action</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if scrolled, false if can't scroll anymore</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollIntoView(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollIntoView</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Perform a scroll forward action to move through the scrollable layout
- element until a visible item that matches the selector is found.
-
- See <code><a href="#scrollDescriptionIntoView(java.lang.String)">scrollDescriptionIntoView(String)</a></code> and <code><a href="#scrollTextIntoView(java.lang.String)">scrollTextIntoView(String)</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>selector</td>
- <td><code><a href="UiSelector.html">UiSelector</a></code> selector</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the item was found and now is in view; else, false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollIntoView(com.android.uiautomator.core.UiObject)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollIntoView</span>
- <span class="normal">(<a href="UiObject.html">UiObject</a> obj)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Perform a forward scroll action to move through the scrollable layout element until
- a visible item that matches the <code><a href="UiObject.html">UiObject</a></code> is found.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>obj</td>
- <td><code><a href="UiObject.html">UiObject</a></code></td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if the item was found and now is in view else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollTextIntoView(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollTextIntoView</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Performs a forward scroll action on the scrollable layout element until
- the text you provided is visible, or until swipe attempts have been exhausted.
- See <code><a href="#setMaxSearchSwipes(int)">setMaxSearchSwipes(int)</a></code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>test to look for</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if item is found; else, false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollToBeginning(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollToBeginning</span>
- <span class="normal">(int maxSwipes)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Scrolls to the beginning of a scrollable layout element. The beginning
- can be at the top-most edge in the case of vertical controls, or the
- left-most edge for horizontal controls. Make sure to take into account
- devices configured with right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollToBeginning(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollToBeginning</span>
- <span class="normal">(int maxSwipes, int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Scrolls to the beginning of a scrollable layout element. The beginning
- can be at the top-most edge in the case of vertical controls, or the
- left-most edge for horizontal controls. Make sure to take into account
- devices configured with right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>use steps to control the speed, so that it may be a scroll, or fling</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollToEnd(int, int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollToEnd</span>
- <span class="normal">(int maxSwipes, int steps)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Scrolls to the end of a scrollable layout element. The end can be at the
- bottom-most edge in the case of vertical controls, or the right-most edge for
- horizontal controls. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>steps</td>
- <td>use steps to control the speed, so that it may be a scroll, or fling</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="scrollToEnd(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- boolean
- </span>
- <span class="sympad">scrollToEnd</span>
- <span class="normal">(int maxSwipes)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Scrolls to the end of a scrollable layout element. The end can be at the
- bottom-most edge in the case of vertical controls, or the right-most edge for
- horizontal controls. Make sure to take into account devices configured with
- right-to-left languages like Arabic and Hebrew.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true on scrolled, else false</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Throws</h5>
- <table class="jd-tagtable">
- <tr>
- <th><a href="UiObjectNotFoundException.html">UiObjectNotFoundException</a></td>
- <td></td>
- </tr>
- </table>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="setAsHorizontalList()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiScrollable</a>
- </span>
- <span class="sympad">setAsHorizontalList</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the direction of swipes to be horizontal when performing scroll actions.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>reference to itself</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="setAsVerticalList()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiScrollable</a>
- </span>
- <span class="sympad">setAsVerticalList</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the direction of swipes to be vertical when performing scroll actions.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>reference to itself</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="setMaxSearchSwipes(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiScrollable</a>
- </span>
- <span class="sympad">setMaxSearchSwipes</span>
- <span class="normal">(int swipes)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the maximum number of scrolls allowed when performing a
- scroll action in search of a child element.
- See <code><a href="#getChildByDescription(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByDescription(UiSelector, String)</a></code> and
- <code><a href="#getChildByText(com.android.uiautomator.core.UiSelector, java.lang.String)">getChildByText(UiSelector, String)</a></code>.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>swipes</td>
- <td>the number of search swipes to perform until giving up</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>reference to itself</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="setSwipeDeadZonePercentage(double)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiScrollable</a>
- </span>
- <span class="sympad">setSwipeDeadZonePercentage</span>
- <span class="normal">(double swipeDeadZonePercentage)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Sets the percentage of a widget's size that's considered as no-touch
- zone when swiping.
- The no-touch zone is set as percentage of a widget's total width or height,
- denoting a margin around the swipable area of the widget. Swipes must
- always start and end inside this margin. This is important when the
- widget being swiped may not respond to the swipe if started at a point
- too near to the edge. The default is 10% from either edge.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>swipeDeadZonePercentage</td>
- <td>is a value between 0 and 1</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>reference to itself</li></ul>
- </div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-
-<h2>Protected Methods</h2>
-
-
-
-<A NAME="exists(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
-
-
-
-
- boolean
- </span>
- <span class="sympad">exists</span>
- <span class="normal">(<a href="UiSelector.html">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Used privately when performing swipe searches to decide if an element has become
- visible or not.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true if found else false</li></ul>
- </div>
-
- </div>
-
-
-
-
-
+++ /dev/null
-page.title=UiSelector
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-<p>Specifies the elements in the layout hierarchy for tests to target, filtered
-by properties such as text value, content-description, class name, and state
-information. You can also target an element by its location in a layout
-hierarchy.</p>
-<h2>Summary</h2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<!-- ======== CONSTRUCTOR SUMMARY ======== -->
-<table id="pubctors" class="jd-sumtable"><tr><th colspan="12">Public Constructors</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- </nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#UiSelector()">UiSelector</a></span>()</nobr>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#checkable(boolean)">checkable</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are checkable.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#checked(boolean)">checked</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that
- are currently checked (usually for checkboxes).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#childSelector(com.android.uiautomator.core.UiSelector)">childSelector</a></span>(<a href="#">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Adds a child UiSelector criteria to this selector.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#className(java.lang.String)">className</a></span>(String className)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the class property
- for a widget (for example, "android.widget.Button").</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
- <T>
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#className(java.lang.Class<T>)">className</a></span>(Class<T> type)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the class property
- for a widget (for example, "android.widget.Button").</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#classNameMatches(java.lang.String)">classNameMatches</a></span>(String regex)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the class property
- for a widget, using a regular expression.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#clickable(boolean)">clickable</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are clickable.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#description(java.lang.String)">description</a></span>(String desc)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the content-description
- property for a widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#descriptionContains(java.lang.String)">descriptionContains</a></span>(String desc)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the content-description
- property for a widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#descriptionMatches(java.lang.String)">descriptionMatches</a></span>(String regex)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the content-description
- property for a widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#descriptionStartsWith(java.lang.String)">descriptionStartsWith</a></span>(String desc)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the content-description
- property for a widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#enabled(boolean)">enabled</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are enabled.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#focusable(boolean)">focusable</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are focusable.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#focused(boolean)">focused</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that have focus.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#fromParent(com.android.uiautomator.core.UiSelector)">fromParent</a></span>(<a href="#">UiSelector</a> selector)</nobr>
-
- <div class="jd-descrdiv">Adds a child UiSelector criteria to this selector which is used to
- start search from the parent widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#index(int)">index</a></span>(int index)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the widget by its node
- index in the layout hierarchy.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#instance(int)">instance</a></span>(int instance)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the
- widget by its instance number.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#longClickable(boolean)">longClickable</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are long-clickable.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#packageName(java.lang.String)">packageName</a></span>(String name)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the package name
- of the application that contains the widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#packageNameMatches(java.lang.String)">packageNameMatches</a></span>(String regex)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the package name
- of the application that contains the widget.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#resourceId(java.lang.String)">resourceId</a></span>(String id)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the given resource ID.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#resourceIdMatches(java.lang.String)">resourceIdMatches</a></span>(String regex)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the resource ID
- of the widget, using a regular expression.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#scrollable(boolean)">scrollable</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that are scrollable.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#selected(boolean)">selected</a></span>(boolean val)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match widgets that
- are currently selected.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#text(java.lang.String)">text</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the visible text displayed
- in a widget (for example, the text label to launch an app).</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#textContains(java.lang.String)">textContains</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the visible text in a widget
- where the visible text must contain the string in your input argument.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#textMatches(java.lang.String)">textMatches</a></span>(String regex)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match the visible text displayed in a layout
- element, using a regular expression.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#textStartsWith(java.lang.String)">textStartsWith</a></span>(String text)</nobr>
-
- <div class="jd-descrdiv">Set the search criteria to match visible text in a widget that is
- prefixed by the text parameter.</div>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#toString()">toString</a></span>()</nobr>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="promethods" class="jd-sumtable"><tr><th colspan="12">Protected Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- <a href="#">UiSelector</a></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad"><a href="#cloneSelector()">cloneSelector</a></span>()</nobr>
-
- </td></tr>
-
-
-
-</table>
-
-
-
-
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="inhmethods" class="jd-sumtable"><tr><th>
- <a href="#" class="toggle-all" onclick="return toggleAllInherited(this, null)">[Expand]</a>
- <div style="clear:left;">Inherited Methods</div></th></tr>
-
-
-<tr class="api" >
-<td colspan="12">
- <a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" class="jd-expando-trigger closed"
- ><img id="inherited-methods-java.lang.Object-trigger"
- src="../../../../../assets/images/styles/disclosure_down.png"
- class="jd-expando-trigger-img" /></a>
-From class
-
- java.lang.Object
-
-<div id="inherited-methods-java.lang.Object">
- <div id="inherited-methods-java.lang.Object-list"
- class="jd-inheritedlinks">
- </div>
- <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
- <table class="jd-sumtable-expando">
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- Object</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">clone</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- boolean</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">equals</span>(Object arg0)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">finalize</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- Class<?></nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">getClass</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- int</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">hashCode</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notify</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">notifyAll</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
-
-
-
- String</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">toString</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>()</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0, int arg1)</nobr>
-
- </td></tr>
-
-
-
- <tr class="api" >
- <td class="jd-typecol"><nobr>
-
-
- final
-
-
- void</nobr>
- </td>
- <td class="jd-linkcol" width="100%"><nobr>
- <span class="sympad">wait</span>(long arg0)</nobr>
-
- </td></tr>
-
-
-</table>
- </div>
-</div>
-</td></tr>
-
-
-</table>
-
-
-</div><!-- jd-descr (summary) -->
-
-<!-- Details -->
-
-
-
-
-
-
-
-
-<!-- XML Attributes -->
-
-
-<!-- Enum Values -->
-
-
-<!-- Constants -->
-
-
-<!-- Fields -->
-
-
-<!-- Public ctors -->
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<h2>Public Constructors</h2>
-
-
-
-<A NAME="UiSelector()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
-
- </span>
- <span class="sympad">UiSelector</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= CONSTRUCTOR DETAIL ======== -->
-<!-- Protected ctors -->
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-
-
-<A NAME="checkable(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">checkable</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are checkable.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="checked(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">checked</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that
- are currently checked (usually for checkboxes).
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="childSelector(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">childSelector</span>
- <span class="normal">(<a href="#">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Adds a child UiSelector criteria to this selector.
-
- Use this selector to narrow the search scope to
- child widgets under a specific parent widget.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with this added search criterion</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="className(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">className</span>
- <span class="normal">(String className)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the class property
- for a widget (for example, "android.widget.Button").</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>className</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="className(java.lang.Class<T>)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">className</span>
- <span class="normal">(Class<T> type)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the class property
- for a widget (for example, "android.widget.Button").</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>type</td>
- <td>type</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="classNameMatches(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">classNameMatches</span>
- <span class="normal">(String regex)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the class property
- for a widget, using a regular expression.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>regex</td>
- <td>a regular expression</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="clickable(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">clickable</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are clickable.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="description(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">description</span>
- <span class="normal">(String desc)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the content-description
- property for a widget.
-
- The content-description is typically used
- by the Android Accessibility framework to
- provide an audio prompt for the widget when
- the widget is selected. The content-description
- for the widget must match exactly
- with the string in your input argument.
-
- Matching is case-sensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>desc</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="descriptionContains(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">descriptionContains</span>
- <span class="normal">(String desc)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the content-description
- property for a widget.
-
- The content-description is typically used
- by the Android Accessibility framework to
- provide an audio prompt for the widget when
- the widget is selected. The content-description
- for the widget must contain
- the string in your input argument.
-
- Matching is case-insensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>desc</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="descriptionMatches(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">descriptionMatches</span>
- <span class="normal">(String regex)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the content-description
- property for a widget.
-
- The content-description is typically used
- by the Android Accessibility framework to
- provide an audio prompt for the widget when
- the widget is selected. The content-description
- for the widget must match exactly
- with the string in your input argument.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>regex</td>
- <td>a regular expression</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="descriptionStartsWith(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">descriptionStartsWith</span>
- <span class="normal">(String desc)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the content-description
- property for a widget.
-
- The content-description is typically used
- by the Android Accessibility framework to
- provide an audio prompt for the widget when
- the widget is selected. The content-description
- for the widget must start
- with the string in your input argument.
-
- Matching is case-insensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>desc</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="enabled(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">enabled</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are enabled.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="focusable(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">focusable</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are focusable.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="focused(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">focused</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that have focus.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="fromParent(com.android.uiautomator.core.UiSelector)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">fromParent</span>
- <span class="normal">(<a href="#">UiSelector</a> selector)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Adds a child UiSelector criteria to this selector which is used to
- start search from the parent widget.
-
- Use this selector to narrow the search scope to
- sibling widgets as well all child widgets under a parent.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with this added search criterion</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="index(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">index</span>
- <span class="normal">(int index)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the widget by its node
- index in the layout hierarchy.
-
- The index value must be 0 or greater.
-
- Using the index can be unreliable and should only
- be used as a last resort for matching. Instead,
- consider using the <code><a href="#instance(int)">instance(int)</a></code> method.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>index</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="instance(int)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">instance</span>
- <span class="normal">(int instance)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the
- widget by its instance number.
-
- The instance value must be 0 or greater, where
- the first instance is 0.
-
- For example, to simulate a user click on
- the third image that is enabled in a UI screen, you
- could specify a a search criteria where the instance is
- 2, the <code><a href="#className(java.lang.String)">className(String)</a></code> matches the image
- widget class, and <code><a href="#enabled(boolean)">enabled(boolean)</a></code> is true.
- The code would look like this:
- <code>
- new UiSelector().className("android.widget.ImageView")
- .enabled(true).instance(2);
- </code></p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>instance</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="longClickable(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">longClickable</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are long-clickable.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="packageName(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">packageName</span>
- <span class="normal">(String name)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the package name
- of the application that contains the widget.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>name</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="packageNameMatches(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">packageNameMatches</span>
- <span class="normal">(String regex)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the package name
- of the application that contains the widget.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>regex</td>
- <td>a regular expression</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="resourceId(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">resourceId</span>
- <span class="normal">(String id)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the given resource ID.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>id</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="resourceIdMatches(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">resourceIdMatches</span>
- <span class="normal">(String regex)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the resource ID
- of the widget, using a regular expression.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>regex</td>
- <td>a regular expression</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 18</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="scrollable(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">scrollable</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that are scrollable.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="selected(boolean)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">selected</span>
- <span class="normal">(boolean val)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match widgets that
- are currently selected.
-
- Typically, using this search criteria alone is not useful.
- You should also include additional criteria, such as text,
- content-description, or the class name for a widget.
-
- If no other search criteria is specified, and there is more
- than one matching widget, the first widget in the tree
- is selected.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>val</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="text(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">text</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the visible text displayed
- in a widget (for example, the text label to launch an app).
-
- The text for the element must match exactly with the string in your input
- argument. Matching is case-sensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="textContains(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">textContains</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the visible text in a widget
- where the visible text must contain the string in your input argument.
-
- The matching is case-sensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="textMatches(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">textMatches</span>
- <span class="normal">(String regex)</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match the visible text displayed in a layout
- element, using a regular expression.
-
- The text in the widget must match exactly with the string in your
- input argument.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>regex</td>
- <td>a regular expression</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
- </div>
-</div>
-
-
-<A NAME="textStartsWith(java.lang.String)"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">textStartsWith</span>
- <span class="normal">(String text)</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>Set the search criteria to match visible text in a widget that is
- prefixed by the text parameter.
-
- The matching is case-insensitive.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Parameters</h5>
- <table class="jd-tagtable">
- <tr>
- <th>text</td>
- <td>Value to match</td>
- </tr>
- </table>
- </div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>UiSelector with the specified search criteria</li></ul>
- </div>
-
- </div>
-</div>
-
-
-<A NAME="toString()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
-
-
- String
- </span>
- <span class="sympad">toString</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
- <div></div>
-
-
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p></p></div>
-
- </div>
-</div>
-
-
-
-
-
-<!-- ========= METHOD DETAIL ======== -->
-
-<h2>Protected Methods</h2>
-
-
-
-<A NAME="cloneSelector()"></A>
-
-<div class="jd-details api">
- <h4 class="jd-details-title">
- <span class="normal">
- protected
-
-
-
-
- <a href="#">UiSelector</a>
- </span>
- <span class="sympad">cloneSelector</span>
- <span class="normal">()</span>
- </h4>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Since</h5>
- <ul class="nolist"><li>Android API Level 17</li></ul>
- </div>
-
- </div>
-
-
-
-
-
-
+++ /dev/null
-page.title=UiWatcher
-parent.title=uiautomator
-parent.link=index.html
-@jd:body
-<style>
- h4.jd-details-title {background-color: #DEE8F1;}
-</style>
-
-<p>Represents a conditional watcher on the target device. To learn how to register a conditional
- watcher, see <code><a href="UiDevice.html#registerWatcher(java.lang.String, com.android.uiautomator.core.UiWatcher)">UiDevice.registerWatcher()</a></code>.
-</p>
-<h2>Summary</h2>
-
-<!-- ========== METHOD SUMMARY =========== -->
-<table id="pubmethods" class="jd-sumtable"><tr><th colspan="12">Public Methods</th></tr>
-
-
-
-
- <tr class="api" >
- <td class="jd-typecol">
- abstract
-
-
-
-
- boolean
- </td>
- <td class="jd-linkcol" width="100%">
- <span class="sympad"><a href="#checkForCondition()">checkForCondition</a></span>()
-
- <div class="jd-descrdiv">The testing framework calls this handler method automatically when the framework
- is unable to find a match using the <code><a href="UiSelector.html">UiSelector</a></code>.</div>
-
- </td></tr>
-
-</table>
-
-</div><!-- jd-descr (summary) -->
-
-
-<!-- ========= METHOD DETAIL ======== -->
-<!-- Public methdos -->
-
-<h2>Public Methods</h2>
-
-<a id="checkForCondition()"></a>
-
-<div class="jd-details api ">
- <h4 class="jd-details-title">
- <span class="normal">
- public
-
-
- abstract
-
- boolean
- </span>
- <span class="sympad">checkForCondition</span>
- <span class="normal">()</span>
- </h4>
- <div class="api-level">
-
- </div>
- <div class="jd-details-descr">
-
- <div class="jd-tagdata jd-tagdescr"><p>The testing framework calls this handler method automatically when the framework is unable to find a match using the <code><a href="UiSelector.html">UiSelector</a></code>. When a match is not found after a predetermined time has elapsed, the framework calls the checkForCondition() method of all registered watchers on the device. You can use this method to handle known blocking issues that are preventing the test from proceeding. For example, you can check if a dialog appeared that is blocking the the test, then close the dialog or perform some other appropriate action to allow the test to continue.</p></div>
- <div class="jd-tagdata">
- <h5 class="jd-tagtitle">Returns</h5>
- <ul class="nolist"><li>true to indicate a matched condition, or false if no matching condition is found
-</li></ul>
- </div>
-
- </div>
+++ /dev/null
-page.title=uiautomator
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ul>
- <li><a href="#syntax">Syntax</a></li>
- <li><a href="#options">Options</a></li>
- <lI><a href="#api">uiautomator API</a>
- <ul>
- <li><a href="#classes">Classes</a></li>
- <li><a href="#interfaces">Interfaces</a></li>
- <li><a href="#exceptions">Exceptions</a></li>
- </ul>
- </lI>
- </ul>
- </div>
-</div>
-
-<p>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.</p>
-<p>For more information on testing with the {@code uiautomator} framework, see <a href="{@docRoot}tools/testing/testing_ui.html">UI Testing</a>.</p>
-
-<h2 id="syntax">Syntax</h2>
-<p>To run your testcases on the target device, you can use the {@code adb shell} command to invoke the {@code uiautomator} tool. The syntax is:
-<pre>
-adb shell uiautomator runtest <JARS> -c <CLASSES> [options]
-</pre>
-</p>
-<p>Here’s an example:</p>
-<pre>adb shell uiautomator runtest LaunchSettings.jar -c com.uia.example.my.LaunchSettings</pre>
-
-<h2 id="options">Command-line Options</h2>
-<p>The following table describes the subcommands and options for {@code uiautomator}.</p>
-
-<p class="table-caption" id="table1">
-<strong>Table 1.</strong> Command-line options for {@code uiautomator}</p>
-<table>
-<tr>
- <th>Subcommand</th>
- <th>Option</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td rowspan="7"><code>runtest</code></td>
-<td><nobr>{@code <JARS>}</nobr></td>
-<td><strong>Required</strong>. The {@code <JARS>} argument is the name of one or more JAR files that you deployed to the target device which contain your uiautomator testcases. You can list more than one JAR file by using a space as a separator.</td>
-</tr>
-
-<tr>
-<td><nobr><code>-c <CLASSES> </code></nobr></td>
-<td><strong>Required (API 17 or lower)</strong>.The {@code <CLASSES>}
-argument is a list of test classes or test methods in {@code <JARS>} to run.
-<p>Each class or method must be fully
-qualified with the package name, in one of these formats:
-<ul>
-<li>{@code package_name.class_name}</li>
-<li>{@code package_name.class_name#method_name}</li>
-</ul>
-You can list multiple classes or methods by using a space as a separator.</p>
-<p class="note"><strong>Note:</strong>This argument is not required for API 18
-and higher. If not specified, all test cases in {@code <JARS>} will be run.
-</p>
-</td>
-</tr>
-
-<tr>
-<td><nobr><code>--nohup</code></nobr></td>
-<td>Runs the test to completion on the device even if its parent process is terminated (for example, if the device is disconnected).</td>
-</tr>
-
-<tr>
-<td><nobr><code>-e <NAME> <VALUE></code></nobr></td>
-<td><p>Specify other name-value pairs to be passed to test classes. May be repeated.</p><p class="note"><strong>Note: </strong>The {@code -e} options cannot be combined; you must prefix each option with a separate {@code -e} flag. </p></td>
-</tr>
-
-<tr>
-<td><nobr><code>-e debug [true|false]</code></nobr></td>
-<td>Wait for debugger to connect before starting.</td>
-</tr>
-
-<tr>
-<td><code>dump [file]</code></td>
-<td>Generate an XML file with a dump of the current UI hierarchy. If a filepath is not specified, by default, the generated dump file is stored on the device in this location {@code /storage/sdcard0/window_dump.xml}.</td>
-</tr>
-
-<tr>
-<td><nobr><code>-e outputFormat simple | -s</code></nobr></td>
-<td>Enables less verbose JUnit style output.</td>
-</tr>
-
-<tr>
-<td><code>events</code></td>
-<td> </td>
-<td>Prints out accessibility events to the console until the connection to the device is terminated</td>
-</tr>
-</table>
-
-<h2 id="api">uiautomator API</h2>
-<p>The {@code uiautomator} API is bundled in the {@code uiautomator.jar} file under the {@code <android-sdk>/platforms/} directory. The API includes these key classes, interfaces, and exceptions that allow you to capture and manipulate UI components on the target app:</p>
-
-<h3 id="classes">Classes</h3>
-<table>
-<tr>
- <th>Class</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiCollection.html">{@code com.android.uiautomator.core.UiCollection}</a></nobr></td>
-<td>Used to enumerate a container's user interface (UI) elements for the purpose of counting, or targeting a sub elements by a child's text or description.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiDevice.html">{@code com.android.uiautomator.core.UiDevice}</a></nobr></td>
-<td>Provides access to state information about the device. You can also use this class to simulate user actions on the device, such as pressing the d-pad hardware button or pressing the Home and Menu buttons.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiObject.html">{@code com.android.uiautomator.core.UiObject}</a></nobr></td>
-<td>Represents a user interface (UI) element.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiScrollable.html">{@code com.android.uiautomator.core.UiScrollable}</a></nobr></td>
-<td>Provides support for searching for items in a scrollable UI container.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiSelector.html">{@code com.android.uiautomator.core.UiSelector}</a></nobr></td>
-<td>Represents a query for one or more target UI elements on a device screen. </td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/Configurator.html">{@code com.android.uiautomator.core.Configurator}</a></nobr></td>
-<td>Allows you to set key parameters for running uiautomator tests.</td>
-</tr>
-
-</table>
-
-<h3 id="interfaces">Interfaces</h3>
-
-<table>
-<tr>
- <th>Interface</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiWatcher.html">{@code com.android.uiautomator.core.UiWatcher}</a></nobr></td>
-<td>Represents a conditional watcher on the target device.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/IAutomationSupport.html">{@code com.android.uiautomator.testrunner.IAutomationSupport}</a></nobr></td>
-<td>Provides auxiliary support for running test cases.</td>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiAutomatorTestCase.html">{@code com.android.uiautomator.testrunner.UiAutomatorTestCase}</a></nobr></td>
-<td>Defines an environment for running multiple tests. All {@code uiautomator} test cases should extend this class.</td>
-</tr>
-
-</table>
-
-<h3 id="exceptions">Exceptions</h3>
-
-<table>
-<tr>
- <th>Exception</th>
- <th>Description</th>
-</tr>
-
-<tr>
-<td><nobr><a href="{@docRoot}tools/help/uiautomator/UiObjectNotFoundException.html">{@code com.android.uiautomator.core.UiObjectNotFoundException}</a></nobr></td>
-<td>Indicates when a a <a href="{@docRoot}tools/help/uiautomator/UiSelector.html">{@code UiSelector}</a> could not be matched to any UI element displayed.</td>
-</tr>
-
-</table>
-
-
-
-
-
-
+++ /dev/null
-page.title=Vector Asset Studio
-parent.title=Tools
-parent.link=index.html
-page.tags=vector
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>In this document</h2>
-<ol>
- <li><a href="#about">About Vector Asset Studio</a></li>
- <li><a href="#running">Running Vector Asset Studio</a></li>
- <li><a href="#importing">Importing a Vector Graphic</a></li>
- <li><a href="#layout">Adding a Vector Drawable to a Layout</a></li>
- <li><a href="#referring">Referring to a Vector Drawable in Code</a></li>
- <li><a href="#code">Modifying XML Code Generated by Vector Asset Studio</a></li>
- <li><a href="#delete">Deleting a Vector Asset from a Project</a></li>
- <li><a href="#apk">Delivering an App Containing Vector Drawables</a></li>
-</ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/material/drawables.html#VectorDrawables">Create Vector Drawables</a></li>
- <li><a href="https://www.google.com/design/icons" class="external-link">Material Icons</a></li>
- <li><a href="{@docRoot}reference/android/graphics/drawable/Drawable.html">Drawable Class</a></li>
- <li><a href="{@docRoot}reference/android/graphics/drawable/VectorDrawable.html">VectorDrawable Class</a></li>
- <li><a href="https://android-developers.blogspot.com/2016/02/android-support-library-232.html" class="external-link">Android Support Library 23.2</a></li>
- </ol>
-
- <h2>Videos</h2>
- <ol>
- <li><a href="http://www.youtube.com/watch?t=126&v=wlFVIIstKmA" class="external-link">DevBytes: Android Vector Graphics</a></li>
- <li><a href="http://www.youtube.com/watch?v=8e3I-PYJNHg" class="external-link">Android Studio Support for Vector Graphics</a></li>
- </ol>
-
- <h2>Dependencies and Prerequisites</h2>
- <ul>
- <li><a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin for Gradle</a> 1.5.0 or higher</li>
- </ul>
-
-</div>
-</div>
-
-<p>Vector Asset Studio helps you add material icons
-and import Scalable Vector Graphic (SVG) files into your app project as a drawable resource.
-Compared to raster images, vector drawables can reduce the size of your app and be resized without
-loss of image quality. They help you to more easily support different Android devices with varying
-screen sizes and resolutions because you can display one vector drawable on all of them. </p>
-
-<h2 id="about">About Vector Asset Studio</h2>
-
-<p>Vector Asset Studio adds a vector graphic to the project as an XML file that describes the image.
-Maintaining one XML file can be easier than updating multiple raster graphics at various
-resolutions.</p>
-
-<p>Android 4.4 (API level 20) and lower doesn't support vector drawables. If
-your minimum API level is set at one of these API levels, you have two options
-when using Vector Asset Studio:
-generate Portable Network Graphic (PNG) files (the default) or use the Support
-Library.</p>
-
-<p>For backward-compatibility, Vector Asset Studio generates
-raster images of the vector drawable. The vector and raster drawables are
-packaged together in the APK. You can refer to vector assets as
-{@link android.graphics.drawable.Drawable} in Java code or
-<code>@drawable</code> in XML code; when your app runs, the corresponding vector
-or raster image displays automatically depending on the API level.</p>
-
-<p>To instead use Android Support Library 23.2 or higher, you must add
-some statements to your <code>build.gradle</code> file. This technique uses
-vector drawables only.</p>
-
-
-
-<h3 id="types">Supported vector graphic types</h3>
-
-<p>The Google material design specification provides <a href="http://www.google.com/design/icons" class="external-link">material icons</a>
-that you can use in your Android apps. Vector
-Asset Studio helps you choose, import, and size material icons, as well as
-define opacity and the
-Right-to-Left (RTL) mirroring setting.</p>
-
-<p>Vector Asset Studio also helps you to import your own SVG files. SVG is an XML-based open
-standard of the World Wide Web Consortium (W3C). Vector Asset Studio supports the essential
-standard, but not all features. When you specify an SVG file, Vector Asset Studio gives immediate
-feedback about whether the graphics code is supported or not. If the SVG code is supported, it
-converts the file into an XML file containing {@link
-android.graphics.drawable.VectorDrawable} code.</p>
-
-<p>For Android 5.0 (API level 21) and higher, you can use the {@link
-android.graphics.drawable.AnimatedVectorDrawable} class to animate the properties of {@link
-android.graphics.drawable.VectorDrawable}. For more information, see
-<a href="{@docRoot}training/material/animations.html#AnimVector">Animating Vector Drawables</a>.</p>
-
-<h3 id="when">Considerations for SVG files</h3>
-
-<p>A vector drawable is appropriate for simple icons. The
-<a href="http://www.google.com/design/icons" class="external-link">material icons</a> provide good
-examples of the types
-of images that work well as vector drawables in an app. In contrast, many app launch icons do have
-many details, so they work better as raster images.</p>
-
-<p>The initial loading of a vector graphic can cost more CPU cycles than the corresponding raster
-image. Afterward, memory use and performance are similar between the two. We recommend that you
-limit a vector image to a maximum of 200 x 200 dp; otherwise, it can take too long to draw.</p>
-
-<p>Although vector drawables do support one or more colors, in many cases it makes sense to color
-icons black (<code>android:fillColor="#FF000000"</code>). Using this approach, you can add a
-<a href="{@docRoot}training/material/drawables.html#DrawableTint">tint</a> to the vector drawable
-that you placed in a layout, and the icon color changes to the tint color. If the icon color
-isn't black, the icon color might instead blend with the tint color.</p>
-
-<h3 id="apilevel">Vector drawable backward-compatibility solutions</h3>
-
-<p>The following table summarizes the two techniques you can use for
-backward-compatibility with Android 4.4 (API level 20) and lower:</p>
-
-
-<table>
- <tr>
- <th scope="col">Technique</th>
- <th scope="col">Drawables in APK</th>
- <th scope="col">VectorDrawable XML Elements</th>
- <th scope="col">Android Plugin for Gradle</th>
- <th scope="col">Build Flags</th>
- <th scope="col">App Code</th>
- </tr>
-
- <tr>
- <td><strong>PNG generation</strong></td>
- <td>Vector and raster</td>
- <td><a href="#apilevel">Subset supported</a></td>
- <td>1.5.0 or higher</td>
- <td>Default</td>
- <td>Variety of coding techniques supported</td>
- </tr>
- <tr>
- <td><strong>Support Library 23.2 or higher</strong></td>
- <td>Vector</td>
- <td>Full support</td>
- <td>2.0 or higher</td>
- <td>Support Library statements required</td>
- <td><a href="https://android-developers.blogspot.com/2016/02/android-support-library-232.html" class="external-link">Subset of coding techniques supported</a></td>
- </tr>
-
-</table>
-
-<p>Using vector graphics can produce a smaller APK, but the initial loading
-of vector graphics can take longer.</p>
-
-<h4 id="pngoption">PNG generation</h4>
-
-<p>Android 5.0 (API level 21) and higher provides vector drawable support. If your app has a
-minimum API level that is lower, Vector Asset Studio adds the vector drawable file to your
-project; also, at build time, Gradle creates PNG raster images at various
-resolutions. Gradle generates the PNG densities specified by the Domain Specific Language (DSL)
-<a href="http://google.github.io/android-gradle-dsl/1.4/com.android.build.gradle.internal.dsl.ProductFlavor.html#com.android.build.gradle.internal.dsl.ProductFlavor:generatedDensities" class="external-link">generatedDensities</a> property
-in a <code>build.gradle</code> file. To generate PNGs, the build system requires Android
-Plugin for Gradle 1.5.0 or higher.</p>
-
-<p>For Android 5.0 (API level 21) and higher, Vector Asset Studio supports all of the {@link
-android.graphics.drawable.VectorDrawable} elements. For backward compatibility with Android 4.4 (API
-level 20) and lower, Vector Asset Studio supports the following XML elements:</p>
-
-<div class="wrap">
- <div class="cols">
- <div class="col-1of3">
-
-<p><code><vector></code></p>
-<ul>
- <li><code>android:width</code></li>
- <li><code>android:height</code></li>
- <li><code>android:viewportWidth</code></li>
- <li><code>android:viewportHeight</code></li>
- <li><code>android:alpha</code></li>
-</ul>
-
-</div>
-
-<div class="col-1of3">
-
-<p><code><group></code></p>
-<ul>
- <li><code>android:rotation</code></li>
- <li><code>android:pivotX</code></li>
- <li><code>android:pivotY</code></li>
- <li><code>android:scaleX</code></li>
- <li><code>android:scaleY</code></li>
- <li><code>android:translateX</code></li>
- <li><code>android:translateY</code></li>
-</ul>
-
-</div>
-
-
-<div class="col-1of3">
-
-<p><code><path></code></p>
-<ul>
- <li><code>android:pathData</code></li>
- <li><code>android:fillColor</code></li>
- <li><code>android:strokeColor</code></li>
- <li><code>android:strokeWidth</code></li>
- <li><code>android:strokeAlpha</code></li>
- <li><code>android:fillAlpha</code></li>
- <li><code>android:strokeLineCap</code></li>
- <li><code>android:strokeLineJoin</code></li>
- <li><code>android:strokeMiterLimit</code></li>
-</ul>
-
-</div>
-
-</div>
-</div>
-
-<p>Only Android 5.0 (API level 21) and higher supports dynamic attributes, for example, <code>android:fillColor="?android:attr/colorControlNormal"</code>.</p>
-
-<p>You can change the XML code that Vector Asset Studio generates, although it’s not a best practice.
-Changing the values in the code should not cause any issues, as long as they’re valid and static. If
-you want to add XML elements, you need to make sure that they’re supported based on your minimum API
-level.</p>
-
-<h4 id="sloption">Support Library</h4>
-
-<p>This technique requires Android Support Library 23.2 or higher and Android
-Plugin for Gradle 2.0 or higher, and uses vector drawables only. Before using
-Vector Asset Studio, you must add a statement to your
-<code>build.gradle</code> file:</p>
-
-<pre>
-android {
- defaultConfig {
- vectorDrawables.useSupportLibrary = true
- }
-}
-
-dependencies {
- compile 'com.android.support:appcompat-v7:23.2.0'
-}
- </pre>
-
- <p>You must also use coding techniques that are compatible with the Support
- Library. For more information, see
- <a href="https://android-developers.blogspot.com/2016/02/android-support-library-232.html"
- class="external-link">Android Support Library 23.2</a>.</p>
-
-<h2 id="running">Running Vector Asset Studio</h2>
-
-<p>To start Vector Asset Studio:</p>
-
-<ol>
- <li>In Android Studio, open an Android app project.</li>
- <li>In the <em>Project</em> window, select the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>.</li>
- <li>Right-click the <strong>res</strong> folder and select <strong>New</strong> >
- <strong>Vector Asset</strong>.</li>
- <p>Some other project views and folders have this menu item as well.</p>
- <p>Vector Asset Studio appears.</p>
- <img src="{@docRoot}images/tools/vas-materialicon.png" />
- <li>If a <em>Need newer Android plugin for Gradle</em> dialog appears instead, correct
- your Gradle version as follows:</li>
- <ol type="a">
- <li>Select <strong>File</strong> > <strong>Project Structure</strong>.</li>
- <li>In the <em>Project Structure</em> dialog, select <strong>Project</strong>.</li>
- <li>In the <strong>Android Plugin Version</strong> field, change the Android Plugin for Gradle
- version to <strong>1.5.0</strong> or higher, and click <strong>OK</strong>.</li>
- <p>Gradle syncs the project.</p>
- <li>In the <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a>
- of the <em>Project</em> window, right-click the <strong>res</strong> folder and select
- <strong>New</strong> > <strong>Vector Asset</strong>.</li>
- <p>Vector Asset Studio appears.</p>
- </ol>
- <li>Continue with <a href="#importing">Importing a Vector Graphic</a>.</li>
-</ol>
-
-<h2 id="importing">Importing a Vector Graphic</h2>
-
-<p>Vector Asset Studio helps you to import a vector graphics file into your app project. Follow one
- of the following procedures:</p>
-<ul>
- <li><a href="#materialicon">Adding a material icon</a></li>
- <li><a href="#svg">Importing an SVG file</a></li>
-</ul>
-
-<h3 id="materialicon">Adding a material icon</h3>
-
-<p>After you <a href="#running">open Vector Asset Studio</a>, you can add a material icon as
-follows:</p>
-
-<ol>
- <li>In Vector Asset Studio, select <strong>Material Icon</strong>.</li>
- <li>Click <strong>Choose</strong>.</li>
- <li>Select a material icon and click <strong>OK</strong>.</li>
- <p>The icon appears in the <strong>Vector Drawable Preview</strong>.</p>
- <li>Optionally change the resource name, size, opacity, and Right-To-Left (RTL) mirroring setting:
- <ul>
- <li><strong>Resource name</strong> - Type a new name if you don’t want to use the default name.
- Vector Asset Studio automatically creates a unique name (adds a number to the end of the name)
- if that resource name already exists in the project. The name can contain lowercase
- characters, underscores, and digits only.</li>
- <li><strong>Override default size from material design</strong> - Select this option if you
- want to adjust the size of the image. When you type a new size, the change appears in the
- preview area.</li>
- <p>The default is 24 x 24 dp, which is defined in the
- <a href="http://www.google.com/design/icons" class="external-link">material design</a>
- specification. Deselect the checkbox to return to the default.</p>
- <li><strong>Opacity</strong> - Use the slider to adjust the opacity of the image. The change
- appears in the preview area.</li>
- <li><strong>Enable auto mirroring for RTL layout</strong> - Select this option if you want a
- mirror image to display when the layout is right to left, instead of left to right. For
- example, some languages are read right to left; if you have an arrow icon, you might want to
- display a mirror image of it in this case. Note that if you’re working with an older project,
- you might also
- need to add <code>android:supportsRtl="true"</code> to your app manifest. Auto-mirroring is
- supported on Android 5.0 (API level 21) and higher, and the Support Library.</li>
- </ul>
- <li>Click <strong>Next</strong>.</li>
- <li>Optionally change the module and resource directory:</li>
- <ul>
- <li><strong>Target Module</strong> - Select a module in the project where you want to add the
- resource. For more information, see
- <a href="{@docRoot}sdk/installing/create-project.html#CreatingAModule">Creating an Android Module</a>.</li>
- <li><strong>Res Directory</strong> - Select the resource source set where you want to add the
- vector asset: <code>src/main/res</code>, <code>src/debug/res</code>,
- <code>src/release/res</code>,
- or a user-defined source set. The main source set applies to all build variants, including
- debug and release. The debug and release source sets override the main source set and apply
- to one version of a build. The debug source set is for debugging only. To define a new source
- set, select <strong>File</strong> > <strong>Project Structure</strong> > <strong>app</strong> >
- <strong>Build Types</strong>. For example, you could define a beta source set and create a
- version of an icon that includes the text "BETA” in the bottom right corner.
- For more information, see
- <a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">Working with Build Variants</a>.</li>
- </ul>
- <p>The <strong>Output Directories</strong> area displays the vector image and the directory
- where it will appear.</p>
- <li>Click <strong>Finish</strong>.</li>
- <p>Vector Asset Studio adds an XML file defining the vector drawable to the project in the
- <code>app/src/main/res/drawable/</code> folder. From the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a> of the
- <em>Project</em>
- window, you can view the generated vector XML file in the <strong>drawable</strong> folder.</p>
- <li>Build the project.</li>
- <p>If the minimum API level is Android 4.4 (API level 20) and lower, and you
- haven't enabled the Support Library technique, Vector Asset Studio generates
- PNG files. From the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Project view</a>
- of the <em>Project</em> window, you can view the generated PNG and XML files in the
- <code>app/build/generated/res/pngs/debug/</code> folder.</p>
- <p>You should not edit these generated raster files, but instead work with the vector XML file.
- The
- build system regenerates the raster files automatically when needed so you don’t need to maintain
- them.</p>
-</ol>
-
-<h3 id="svg">Importing a Scalable Vector Graphic (SVG)</h3>
-
-<p>After you <a href="#running">open Vector Asset Studio</a>, you can import an SVG file as
-follows:</p>
-
-<ol>
- <li>In Vector Asset Studio, select <strong>Local SVG file</strong>.</li>
- <p>The file must be on a local drive. If it’s located on the network, for example, you need to
- download it to a local drive first.</p>
- <li>Specify an <strong>Image file</strong> by clicking <strong>…</strong> .</li>
- <p>The image appears in the <strong>Vector Drawable Preview</strong>.</p>
- <p>However, if the SVG file contains unsupported features, an error appears at the bottom left of
- Vector Asset Studio, as shown in the following figure.</p>
- <img src="{@docRoot}images/tools/vas-svgerror.png" />
- <p>In this case, you can’t use Vector Asset Studio to add the graphics file. Click
- <strong>More</strong> to view the errors. For a list of supported elements, see
- <a href="#apilevel">Vector Drawable Support at Different API Levels</a>.</p>
- <li>Optionally change the resource name, size, opacity, and Right-To-Left (RTL) mirroring
- setting:</li>
- <ul>
- <li><strong>Resource name</strong> - Type a new name if you don’t want to use the default
- name. Vector Asset Studio automatically creates a unique name (adds a number to the end of the
- name) if that resource name already exists in the project. The name can contain lowercase
- characters, underscores, and digits only.</li>
- <li><strong>Override default size from material design</strong> - Select this option if you
- want to adjust the size of the image. After you select it, the size changes to the size of the
- image itself. Whenever you change the size, the change appears in the preview area.</li>
- <p>The default is 24 x 24 dp, which is defined in the
- <a href="http://www.google.com/design/icons" class="external-link">material design</a>
- specification. Deselect the checkbox to return to the default.</p>
- <li><strong>Opacity</strong> - Use the slider to adjust the opacity of the image. The change
- appears in the preview area.</li>
- <li><strong>Enable auto mirroring for RTL layout</strong> - Select this option if you want a
- mirror image to display when the layout is right to left, instead of left to right. For
- example, some languages are read right to left; if you have an arrow icon, you might want to
- display a mirror image of it in this case. Note that if you’re working with an older project,
- you might
- need to add <code>android:supportsRtl="true"</code> to your app manifest. Auto-mirroring is
- supported on Android 5.0 (API level 21) and higher, and the Support Library.</li>
- </ul>
- <li>Click <strong>Next</strong>.</li>
- <li>Optionally change the module and resource directory:</li>
- <ul>
- <li><strong>Target Module</strong> - Select a module in the project where you want to add the
- resource. For more information, see
- <a href="{@docRoot}sdk/installing/create-project.html#CreatingAModule">Creating an Android Module</a>.</li>
- <li><strong>Res Directory</strong> - Select the resource source set where you want to add the
- vector asset: <code>src/main/res</code>, <code>src/debug/res</code>, <code>src/release/res</code>,
- or a user-defined source set. The main source set applies to all build variants, including
- debug and release. The debug and release source sets override the main source set and apply
- to one version of a build. The debug source set is for debugging only. To define a new source
- set, select <strong>File</strong> > <strong>Project Structure</strong> > <strong>app</strong> >
- <strong>Build Types</strong>. For example, you could define a beta source set and create a
- version of an icon that includes the text "BETA” in the bottom right corner.
- For more information, see
- <a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">Working with Build Variants</a>.</li>
- </ul>
- <p>The <strong>Output Directories</strong> area displays the vector image and the directory
- where it will appear.</p>
- <li>Click <strong>Finish</strong>.</li>
- <p>Vector Asset Studio adds an XML file defining the vector drawable to the project in the
- <code>app/src/main/res/drawable/</code> folder. From the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a> of the
- <em>Project</em>
- window, you can view the generated vector XML file in the <strong>drawable</strong> folder.</p>
- <li>Build the project.</li>
- <p>If the minimum API level is Android 4.4 (API level 20) and lower, and you
- haven't enabled the Support Library technique, Vector Asset Studio generates
- PNG files. From the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Project view</a>
- of the <em>Project</em> window, you can view the generated PNG and XML files in the
- <code>app/build/generated/res/pngs/debug/</code> folder.</p>
- <p>You should not edit these generated raster files, but instead work with the vector XML file.
- The
- build system regenerates the raster files automatically when needed so you don’t need to maintain
- them.</p>
-</ol>
-
-<h2 id="layout">Adding a Vector Drawable to a Layout</h2>
-
-<p>In a layout file, you can set any icon-related widget, such as {@link android.widget.ImageButton},
-{@link android.widget.ImageView}, and so on, to point to a vector asset. For example, the following
-layout shows a vector asset displayed on a button:</p>
-
-<img src="{@docRoot}images/tools/vas-layout.png" />
-
-<p>To display a vector asset on a widget, as shown in the figure:</p>
-
-<ol>
- <li>Open a project and <a href="#running">import a vector asset</a>.</li>
- <li>In the <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Android view</a> of
- the <em>Project</em> window, double-click a layout XML file, such as
- <code>content_main.xml</code>.</li>
- <li>Click the <strong>Design</strong> tab to display the
- <a href="{@docRoot}sdk/installing/studio-layout.html">Layout Editor</a>.</li>
- <li>Drag the {@link
-android.widget.ImageButton} widget from the <em>Palette</em> window onto the Layout Editor.</li>
- <li>In the <em>Properties</em> window, locate the <strong>src</strong> property of the
- <code>ImageButton</code> instance and click <strong>…</strong> .</li>
- <li>In the <em>Resources</em> dialog, select the <strong>Project</strong> tab, navigate to the
- <strong>Drawable</strong> folder, and select a vector asset. Click <strong>OK</strong>.</li>
- <p>The vector asset appears on the <code>ImageButton</code> in the layout.</p>
- <li>To change the color of the image to the accent color defined in the theme, locate the
- <strong>tint</strong> property in the <em>Properties</em> window and click <strong>…</strong> .
- </li>
- <li>In the <em>Resources</em> dialog, select the <strong>Project</strong> tab, navigate to the
- <strong>Color</strong> folder, and select <strong>colorAccent</strong>. Click <strong>OK</strong>.
- </li>
- <p>The color of the image changes to the accent color in the layout.</p>
-</ol>
-
-<p>If you're not using the Support Library technique, the
-<code>ImageButton</code> code should be similar to the following:</p>
-
-<pre>
-<ImageButton
- android:id="@+id/imageButton"
- android:src="@drawable/ic_build_24dp"
- android:tint="@color/colorAccent"
- android:layout_width="wrap_content"
- android:layout_height="wrap_content"
- android:layout_below="@+id/textView2"
- android:layout_marginTop="168dp" />
-</pre>
-
-<h2 id="referring">Referring to a Vector Drawable in Code</h2>
-
-<p>You can normally refer to a vector drawable resource in a generic way in your code, and when
-your app runs, the corresponding vector or raster image displays automatically depending on the API
-level:</p>
-
-<ul>
- <li>In most cases, you can refer to vector assets as <code>@drawable</code> in XML code or
- {@link android.graphics.drawable.Drawable} in Java code. </li>
- <p>For example, the following layout XML code applies the image to a view:</p>
-<pre>
-<ImageView
- android:layout_height="wrap_content"
- android:layout_width="wrap_content"
- android:src="@drawable/myimage" />
-</pre>
- <p>The following Java code retrieves the image as a {@link android.graphics.drawable.Drawable}:</p>
-<pre>
-Resources res = {@link android.content.Context#getResources()};
-Drawable drawable = res.{@link android.content.res.Resources#getDrawable(int) getDrawable}(R.drawable.myimage);
-</pre>
- <li>Occasionally, you might need to typecast the drawable resource to its exact class, such as
- when you need to use specific features of the {@link android.graphics.drawable.VectorDrawable}
- class. To do so, you could use Java code such as the following:</li>
-<pre>
-if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
- VectorDrawable vectorDrawable = (VectorDrawable) drawable;
-} else {
- BitmapDrawable bitmapDrawable = (BitmapDrawable) drawable;
-}
-</pre>
-</ul>
-
-<p>For the Support Library technique, you must use coding techniques that are
-compatible with the Support Library. For more information, see
- <a href="https://android-developers.blogspot.com/2016/02/android-support-library-232.html"
- class="external-link">Android Support Library 23.2</a>.</p>
-
-
-<h2 id="code">Modifying XML Code Generated by Vector Asset Studio</h2>
-
-<p>You can modify the vector asset XML code, but not the PNGs and corresponding XML code generated
-at build time. However, we don't recommended it.</p>
-
-<p>When using the PNG generation technique, Vector Asset Studio makes sure that the vector
-drawable and the PNGs match, and that the manifest contains the proper code. If you add code that's
-<a href="#apilevel">not supported</a> on Android 4.4 (API level 20) and lower, your vector and PNG
-images might differ. You also need to make sure that the manifest contains the code to support your
-changes.</p>
-
-<p>To modify the vector XML file when you're not using the Support Library
-technique:</p>
-
-<ol>
- <li>In the <em>Project</em> window, double-click the generated vector XML file in the
- <strong>drawable</strong> folder.</li>
- <p>The XML file appears in the editor and <em>Preview</em> windows.</p>
-
- <img src="{@docRoot}images/tools/vas-codepreview.png" />
-
- <li>Edit the XML code based on what’s supported by the minimum API level:</li>
- <ul>
- <li>Android 5.0 (API level 21) and higher - Vector Asset Studio supports all of the
- {@link android.graphics.drawable.Drawable} and
- {@link android.graphics.drawable.VectorDrawable} elements. You can add XML elements and
- change values.</li>
- <li>Android 4.4 (API level 20) and lower - Vector Asset Studio supports all of the
- {@link android.graphics.drawable.Drawable} elements and a subset of the
- {@link android.graphics.drawable.VectorDrawable} elements. See
- <a href="#apilevel">Support at Different API Levels</a> for a list. You can change values in
- the generated code and add XML elements that are supported. Dynamic attributes aren't
- supported.</li>
- </ul>
- <p>For example, if you didn’t select the RTL option in Vector Asset Studio but realize you now
- need it, you can add the
- <a href="{@docRoot}reference/android/R.attr.html#autoMirrored">autoMirrored</a>
- attribute later. To view the RTL version, select <strong>Preview Right-to-Left Layout</strong> in
- the <img src="{@docRoot}images/tools/vas-rtlmenu.png" style="vertical-align:sub;margin:0;height:17px" alt="" />
- menu of the <em>Preview</em> window. (Select <strong>None</strong> to remove the RTL preview.)</p>
-<img src="{@docRoot}images/tools/vas-rtl.png" />
- <p class="note"><strong>Note:</strong> If you’re working with an older project, you might need to
- add <code>android:supportsRtl="true"</code> to your app manifest. Also, because
- <code>autoMirrored</code> is a dynamic attribute, it's supported on Android 5.0 (API level 21) and
- higher only.</p>
- <li>Build the project and check that the vector and raster images look the same.</li>
- <p>Remember that the generated PNGs could display differently in the <em>Preview</em> window than
- in the app due to different rendering engines and any changes made to the vector drawable before a
- build. If you add code to the vector XML file created by Vector Asset Studio, any features
- unsupported in Android 4.4 (API level 20) and lower don't appear in the generated PNG files. As a
- result, when you add code, you should always check that the generated PNGs match the vector
- drawable. To do so, you could double-click the PNG in the
- <a href="{@docRoot}sdk/installing/create-project.html#ProjectView">Project view</a> of the
- <em>Project</em>
- window; the left margin of the code editor also displays the PNG image when your code refers to
- the drawable.</p>
- <img src="{@docRoot}images/tools/vas-imageincode.png" />
-</ol>
-
-
-<h2 id="delete">Deleting a Vector Asset from a Project</h2>
-
-<p>To remove a vector asset from a project:</p>
-
-<ol>
- <li>In the <em>Project</em> window, delete the generated vector XML file by selecting the file and
- pressing the <strong>Delete</strong> key (or select <strong>Edit</strong> >
- <strong>Delete</strong>).</li>
- <p>The <em>Safe Delete</em> dialog appears.</p>
- <li>Optionally select options to find where the file is used in the project, and click
- <strong>OK</strong>.</li>
- <p>Android Studio deletes the file from the project and the drive. However, if you chose to search
- for places in the project where the file is used and some usages are found, you can view them and
- decide whether to delete the file.</p>
- <li>Select <strong>Build</strong> > <strong>Clean Project</strong>.</li>
- <p>Any auto-generated PNG and XML files corresponding to the deleted vector
- asset are removed from the project and the drive.</p>
-</ol>
-
-<h2 id="apk">Delivering an App Containing Vector Drawables</h2>
-
-<p>If you used the Support Library technique or your minimum API level is
-Android 5.0 (API level 21) or higher, your APK will contain the vector images
-that you added with Vector Asset Studio.
-These APKs will be smaller than if the vector images were converted to PNGs.
-</p>
-
-
-<p>When your minimum API level includes Android 4.4 (API level 20) or lower,
- and you have corresponding vector and raster images in your project,
- you have two options for delivering your APK files:</p>
-
-<ul>
- <li>Create one APK that includes both the vector images and the corresponding
- raster representations. This solution is the simplest to implement.</li>
- <li>Create separate APKs for different API levels. When you don’t include the
- corresponding raster images in the APK for Android 5.0 (API level 21) and
- higher, the APK can be much smaller in size. For more information, see
- <a href="{@docRoot}google/play/publishing/multiple-apks.html">Multiple APK Support</a>.
- </li>
-</ul>
+++ /dev/null
-page.title=zipalign
-parent.title=Tools
-parent.link=index.html
-@jd:body
-
-<p>zipalign is an archive alignment tool that provides important
-optimization to Android application (.apk) files.
-The purpose is to ensure that all uncompressed data starts
-with a particular alignment relative to the start of the file. Specifically,
-it causes all uncompressed data within the .apk, such as images or raw files,
-to be aligned on 4-byte boundaries. This
-allows all portions to be accessed directly with {@code mmap()} even if they
-contain binary data with alignment restrictions.
-The benefit is a reduction in the amount of RAM consumed
-when running the application.</p>
-
-<p>This tool should always be used to align your .apk file before
-distributing it to end-users. The Android build tools can handle
-this for you. Android Studio automatically aligns your .apk after it signs it with your
-private key.
-The build scripts used
-when compiling your application with Gradle also align your .apk,
-as long as you have provided the path to your keystore and the key alias in
-your project {@code gradle.properties} file, so that the build tools
-can sign the package first.</p>
-
-<p class="caution"><strong>Caution:</strong> zipalign must only be performed
-<strong>after</strong> the .apk file has been signed with your private key.
-If you perform zipalign before signing, then the signing procedure will undo
-the alignment. Also, do not make alterations to the aligned package.
-Alterations to the archive, such as renaming or deleting entries, will
-potentially disrupt the alignment of the modified entry and all later
-entries. And any files added to an "aligned" archive will not be aligned.</p>
-
-<p>The adjustment is made by altering the size of
-the "extra" field in the zip Local File Header sections. Existing data
-in the "extra" fields may be altered by this process.</p>
-
-<p>For more information about how to use zipalign when building your
-application, please read <a href="{@docRoot}tools/publishing/app-signing.html">Signing
-Your Application</a>.</p>
-
-
-<h3>Usage</h3>
-
-<p>To align {@code infile.apk} and save it as {@code outfile.apk}:</p>
-
-<pre>zipalign [-f] [-v] <alignment> infile.apk outfile.apk</pre>
-
-<p>To confirm the alignment of {@code existing.apk}:</p>
-
-<pre>zipalign -c -v <alignment> existing.apk</pre>
-
-<p>The {@code <alignment>} is an integer that defines the byte-alignment boundaries.
-This must always be 4 (which provides 32-bit alignment) or else it effectively
-does nothing.</p>
-
-<p>Flags:</p>
-
-<ul>
- <li>{@code -f} : overwrite existing outfile.zip</li>
- <li>{@code -v} : verbose output</li>
- <li>{@code -c} : confirm the alignment of the given file</li>
-</ul>
-
-
-
+++ /dev/null
-page.title=Allocation Tracker Walkthrough
-meta.tags="android, performance, profiling, tools, memoryleaks, memoryheap"
-page.tags="android", "performance", "profiling", "tools", "memoryleaks", "memoryheap"
-page.metaDescription=Record you app's memory allocations with their call stack to identify code that allocates and frees objects unnecessarily.
-page.image=tools/performance/thumbnails/tools_allocation_tracker.png
-page.article=true
-
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithAllocationTracker">Working with Allocation Tracker</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/heap-viewer/index.html">
- Heap Viewer Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/memory-monitor/index.html">
- Memory Monitor Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/comparison.html">
- Comparison: Memory Monitor, Heap Viewer, Allocation Tracker</a>
- <li><a href="{@docRoot}tools/performance/traceview/index.html">
- Traceview Walkthrough</a></li>
-</ul>
-
-</div>
-
-
- <p>This walkthrough shows the basic usage and workflow for the Allocation Tracker tool in Android
- Studio. Allocation Tracker records an app's memory allocations and lists all
- allocated objects for the profiling cycle with their call stack, size, and allocating code.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Identifying where many similar object types, from roughly the same call stack, are
- allocated and deallocated over a very short period of time.</li>
-
- <li>Finding the places in your code that may contribute to inefficient memory use.</li>
- </ul>
-
- <p>Before using Allocation Tracker, profile your code with the
- <a href="{@docRoot}tools/performance/memory-monitor/index.html">Memory
- Monitor Tool</a>. If you see many garbage collection events in a short amount of time, use
- <a href="{@docRoot}tools/performance/heap-viewer/index.html">Heap
- Viewer</a> to identify candidate object types, and Allocation Tracker to determine where this is
- happening in your code.</p>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
-
- <li>Application code. Use your own code, or the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
- <h2 id="WorkingWithAllocationTracker">Working with Allocation Tracker</h2>
-
- <p>Allocation Tracker records each memory allocation that your app performs during the profiling
- cycle. You tell Allocation Tracker to start recording and it logs allocations
- until you tell it to stop.</p>
-
-<hr>
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/allocation-tracker/gettingstarted_image01.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Steps for starting Allocation Tracker in Android DDMS.
- </p>
- </div>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>Open your application in Android Studio, build the source, and run it on your device or
- emulator.</li>
-
- <li>Click the <b>Android</b> button at the bottom of your Android Studio window.</li>
-
- <li>If you are using the Android Device Monitor, click the RECORD button
- <img src="{@docRoot}images/tools/performance/allocation-tracker/gettingstarted_image02.png">
- (Start Allocation Tracking tooltip) in the Android DDMS tool bar. If you are using Android
- Studio, click the
- <img src="{@docRoot}images/tools/performance/allocation-tracker/gettingstarted_image02.png">
- icon in the <a href="{@docRoot}tools/studio/index.html#mem-cpu">Memory Monitor</a> tool
- bar. </li>
-
- <li>Interact with your application.</li>
-
- <li>Click the (same) STOP button (Stop Allocation Tracking tooltip).</li>
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="7">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/allocation-tracker/gettingstarted_image03.png"
- alt=""
- width="440px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Example of Allocation Tracker output in Android DDMS.
- </p>
- </div>
-
- <li>After a few seconds, a pane with your recorded data opens.
-
- <p>Note that allocations are logged on
- the device, and the data file is transferred to the host computer, parsed for information, and
- displayed.</p></li>
-
- <li>The pane populates with a table.
-
- <ul>
- <li>Each row represents a memory allocation event.</li>
-
- <li>Each column represents information about the allocation, such as the object type,
- the thread, and its size. </li>
-
- <li>The columns are movable, resizable, and sortable.</li>
- </ul>
-
- <p>Use the Filter to show only allocations from your app.</li>
-
- <li>Click on an object to see its full stack trace.</li>
- </ol>
-</div></li>
-</ul>
+++ /dev/null
-page.title=Battery Historian Charts
-meta.tags="android, performance, profiling, tools, battery, historian, batterydrain
-page.tags="android", performance", "profiling", "tools", "battery", "historian" "batterydrain"
-page.metaDescription=Examine and interpret the collected battery usage data in your browser.
-page.image=tools/performance/thumbnails/tools_battery_historian.png
-page.article=true
-
-@jd:body
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#BatteryHistorianCharts">Battery Historian Charts</a></li>
- <li><a href="#FilteringBatterystats">Filtering batterystats output</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/batterystats-battery-historian/index.html">
- Batterystats & Battery Historian Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/systrace/index.html">
- Systrace Walkthrough</a></li>
-</ul>
-
-</div>
-
-
- <p id="BatteryHistorianCharts">
- The Battery Historian chart graphs power-relevant events over time.</p>
-
- <p>Each row shows a colored bar segment when a system component is active
- and thus drawing current from the battery. The chart does <i>not</i> show <i>how much</i> battery was used by the
- component, only that the app was active. Charts are organized by category.</p>
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/batterystats-battery-historian/gettingstarted_image02.png"
- alt=""
- height="" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Example of Battery Historian output.
- </p>
- </div>
-
- <h3>Battery usage categories</h3>
-
- <ul>
- <li><b>battery_level</b>: When the battery level was recorded and logged.
- Reported in percent, where 093 is 93%. Provides an overall measure of how fast the battery
- is draining.</li>
-
- <li><b>top</b>: The application running at the top; usually, the application that is visible to
- the user. If you want to measure battery drain while your app is active, make sure
- it's the top app. If you want to measure battery drain while your app is in
- the background, make sure it's <i>not</i> the top app.</li>
-
- <li><b>wifi_running</b>: Shows that the Wi-Fi network connection was active.</li>
-
- <li><b>screen</b>: Screen is turned on.</li>
-
- <li><b>phone_in_call</b>: Recorded when the phone is in a call.</li>
-
- <li><b>wake_lock</b>: App wakes up, grabs a lock, does small work, then goes back to sleep.
- This is one of the most important pieces of information. Waking up the phone is expensive, so
- if you see lots of short bars here, that might be a problem.</li>
-
- <li><b>running</b>: Shows when the CPU is awake. Check whether it is awake and asleep
- when you expect it to be.</li>
-
- <li><b>wake_reason</b>: The last thing that caused the kernel to wake up. If
- it's your app, determine whether it was necessary.</li>
-
- <li><b>mobile_radio</b>: Shows when the radio was on. Starting the radio is battery expensive.
- Many narrow bars close to each other can indicate opportunities for
- batching and other optimizations.</li>
-
- <li><b>gps</b>: Indicates when the GPS was on. Make sure this is what you expect.</li>
-
- <li><b>sync:</b> Shows when an app was syncing with a backend. The sync bar also shows which
- app did the syncing. For users, this can show apps where they might turn syncing off to save
- battery. Developers should sync as little as possible and only as often as necessary.</li>
- </ul>
-
-
- <p class="note"><strong>Note:</strong>
- Not every chart will show every category.</p>
-
- <h2 id="FilteringBatterystats">Filtering batterystats output</h2>
-
- <p>You can gather additional information from the <code>batterystats.txt</code> file
- where you saved the output from the batterystats command.</p>
-
- <div class="figure" style="">
-<img src="{@docRoot}images/tools/performance/batterystats-battery-historian/gettingstarted_image03.png"
- alt=""
- width="340px" />
- <p class="img-caption">
- <strong>Figure 2.</strong>Example of filtered batterystats output.
- </p>
- </div>
-
- <p>Open the file in a text editor and search for:</p>
-
- <ol>
- <li><b><code>Battery History</code></b>: A time series of power-relevant events, such as
- screen, Wi-Fi, and app launch. These are also visible through Battery Historian.</li>
-
- <li><b><code>Per-PID Stats</code></b>: How long each process ran.</li>
-
- <li><b><code>Statistics since last charge</code></b>: System-wide statistics, such as
- cell signal levels and screen brightness. Provides an overall picture of what's happening
- with the device. This information is especially useful
- to make sure no external events are affecting your experiment.</li>
-
- <li><b><code>Estimated power use (mAh)</code></b> by UID and peripheral: This is currently an
- extremely rough estimate and should not be considered experiment data.</li>
-
- <li><b><code>Per-app mobile ms per packet</code></b>: Radio-awake-time divided by packets sent.
- An efficient app will transfer all its traffic in batches, so the lower this number the
- better.</li>
-
- <li><b><code>All partial wake locks</code></b>: All app-held wakelocks, by aggregate
- duration and count.</li>
- </ol>
+++ /dev/null
-page.title=Batterystats & Battery Historian Walkthrough
-meta.tags="android, performance, profiling, tools, battery, batterystats, historian, batterydrain
-page.tags="android", "performance", "profiling", "tools", "battery", "batterystats", "historian", "batterydrain"
-page.metaDescription=Collect battery usage data from your device and display it graphically in your browser.
-page.image=tools/performance/thumbnails/tools_battery_historian.png
-page.article=true
-
-
-@jd:body
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/batterystats-battery-historian/charts.html">
- Battery Historian Charts</a></li>
- <li><a href="{@docRoot}tools/performance/systrace/index.html">
- Systrace Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows the basic usage and workflow for the Batterystats tool and the Battery
- Historian script.</p>
-
- <p>Batterystats collects battery data from your device, and Battery Historian converts that data
- into an HTML visualization that you can view in your Browser. Batterystats is part of the Android
- framework, and Battery Historian is open-sourced and available on GitHub at <a href=
- "https://github.com/google/battery-historian">https://github.com/google/battery-historian</a>.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Showing you where and how processes are drawing current from the battery.</li>
-
- <li>Identifying tasks in your app that could be deferred or even removed to improve battery
- life.</li>
- </ul>
-
- <h2>Prerequisites</h2>
-
- <ul>
- <li>A mobile device with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled running Android 5.0 or higher.</li>
- </ul>
-
- <h2>Working with Batterystats & Battery Historian</h2>
-
- <div class="sidebox-wrapper" style="width:400px;">
- <div class="sidebox" style="width:350px;">
- <h2>Summary</h2>
- <code>
- <p><b>https://github.com/google/battery-historian</b></p>
- <p>> adb kill-server</p>
- <p>> adb devices</p>
- <p>> adb shell dumpsys batterystats --reset</p>
- <p><disconnect and play with app>...<reconnect></p>
- <p>> adb devices</p>
- <p>>adb shell dumpsys batterystats > batterystats.txt</p>
- <p>> python historian.py batterystats.txt > batterystats.html</p>
- </code>
- </div>
- </div>
-
- <ol>
-
- <li>Download the open-source Battery Historion Python script from GitHub (<a href=
- "https://github.com/google/battery-historian">https://github.com/google/battery-historian</a>).
- </li>
-
- <li>Unzip the file to extract the Battery Historian folder. Inside the folder,
- find the <code>historian.py</code> file
- and move it to the Desktop or another <em>writable</em> directory.</li>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>On your computer, open a Terminal window.</li>
-
- <li>Change to the directory where you've saved <code>historian.py</code>,
- <br>for example:
- <code>cd ~/Desktop</code></li>
-
- <li>Shut down your running adb server.
- <br><code>> adb kill-server</code></li>
-
- <li>Restart adb and check for connected devices.
- <br><code>> adb devices</code>
- <br><img src="{@docRoot}images/tools/performance/batterystats-battery-historian/gettingstarted_image01.png">
- <br>If you don't see any devices, make sure your phone is connected, and USB Debugging
- is turned on, and then kill and restart adb.</li>
-
- <li>Reset battery data gathering.
- <br><code>> adb shell dumpsys batterystats --reset</code>
- <p>Resetting erases old battery collection data; otherewise, the output will be huge.</p>
- </li>
-
- <li>Disconnect your device from your computer so that you are only drawing current from the
- device's battery.</li>
-
- <li>Play with your app for a short time.</li>
-
- <li>Reconnect your phone.</li>
-
- <li>Make sure your phone is recognized: <code>> adb devices</code></li>
-
- <li>Dump all battery data. This can take a while:
- <br><code>> adb shell dumpsys batterystats > batterystats.txt</code></li>
-
- <li>Create a HTML version of the data dump for Battery Historian:
- <br><code>> python historian.py batterystats.txt > batterystats.html</code></li>
-
- <li>Open the <code>batterystats.htm</code> file in your browser.</li>
-
- <li>Continue with <a href="{@docRoot}tools/performance/batterystats-battery-historian/charts.html">
- Battery Historian Charts</a>.
- </li>
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/batterystats-battery-historian/gettingstarted_image02.png"
- alt=""
- <p class="img-caption">
- <strong>Figure 1. </strong>Battery Historian output.
- </p>
- </div>
- </ol>
-
-
-
+++ /dev/null
-page.title=Memory Profilers
-meta.tags="android, performance, profiling, tools, memory, memoryleaks, garbagecollection"
-page.tags="android", "performance", "profiling", "tools", "memory", "memoryleaks", "garbagecollection"
-page.metaDescription=Heap Viewer, Memory Monitor, and Allocation Tracker are complementary tools that visualize the memory your app uses.
-page.image=tools/performance/thumbnails/tools_memory_monitor.png
-page.article=true
-
-@jd:body
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#MemoryMonitor">Memory Monitor</a></li>
- <li><a href="#HeapViewer">Heap Viewer</a></li>
- <li><a href="#AllocationTracker">Allocation Tracker</a></li>
-
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/memory-monitor/index.html">
- Memory Monitor Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/heap-viewer/index.html">
- Heap Viewer Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/allocation-tracker/index.html">
- Allocation Tracker Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>Heap Viewer, Memory Monitor, and Allocation Tracker are complementary tools that visualize the
- memory your app uses.</p>
-
- <ol>
- <li>Use the
- <a href="{@docRoot}tools/performance/memory-monitor/index.html">
- Memory Monitor Tool</a> to find out whether undesirable garbage collection (GC) event patterns might
- be causing your performance problems.</li>
-
- <li>Run
- <a href="{@docRoot}tools/performance/heap-viewer/index.html">
- Heap Viewer</a> to identify object types that get or stay allocated
- unexpectedely or unecessarily.</li>
-
- <li>Use
- <a href="{@docRoot}tools/performance/allocation-tracker/index.html">
- Allocation Tracker</a> to identify where in your code the problem might be.</li>
- </ol>
-
- <h2 id="MemoryMonitor">Memory Monitor</h2>
-
-<div>
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/compare_MemoryMonitor.png"
- alt=""
- height="" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Memory Monitor.
- </p>
- </div>
-
- <ul>
- <li>Shows available and used memory as they both change over time <i>for your app</i> in a
- graph, with dips indicating Garbage Collection (GC) events.</li>
-
- <li>Provides a quick way to test whether app slowness might be related
- to excessive GC events.</li>
-
- <li>Provides a quick way to see whether app crashes might be related
- to running out of memory.</li>
-
- <li>Runs live on your application and updates about once a second.</li>
-
- <li>Helps quickly identify the potential of memory leaks.</li>
-
- <li>Helps identify GC patterns for your application and determine whether
- they are healthy and what you expect.</li>
-
- <li>Is easy to use, and it is easy to interpret what you see.</li>
-
- <li>However, Memory Monitor does not tell you which objects are the cause
- of your problems, or where in your code it might be.</li>
- </ul>
-
- <h2 id="HeapViewer">Heap Viewer</h2>
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/studio-hprof-viewer.png"
- alt=""
- height="" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Heap Viewer.
- </p>
- </div>
-
-
- <ul>
- <li>Shows snapshots of a number of objects allocated by type.</li>
-
- <li>Samples data every time a garbage collection event occurs
- naturally or triggered by you.</li>
-
- <li>Helps identify which object types might be involved in memory leaks.</li>
-
- <li>However, you have to look for changes over time yourself by tracking what's
- happening in the graph.</li>
- <br><br><br><br>
- </ul>
-
- <h2 id="AllocationTracker">Allocation Tracker</h2>
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/studio-allocation-tracker.png"
- alt=""ge
- height="" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Allocation Tracker.
- </p>
- </div>
-
- <ul>
- <li>Shows when and where your code allocates object types, their size, allocating thread, and
- stack traces.</li>
-
- <li>Helps recognize memory churn through recurring allocation/deallocation patterns.</li>
-
- <li>Can be used in combination with Heap Viewer to track down memory leaks. For example, if you
- see a bitmap object resident on the heap, you can find its allocation location with Allocation
- Tracker.</li>
-
- <li>However, it takes time and experience to learn to interpret the output from this tool.</li>
-
- </ul>
+++ /dev/null
-page.title=Debug GPU Overdraw Walkthrough
-meta.tags="android, performance, profiling, tools, rendering, overdraw"
-page.tags="android", "performance", "profiling", "tools", "rendering", "overdraw"
-page.metaDescription=Use color-coding to show how many times each pixel is redrawn on the screen to reduce rendering overhead.
-page.image=tools/performance/thumbnails/tools_debug_gpu_overdraw.png
-page.article=true
-
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#VisualizingOverdraw">Visualizing Overdraw</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/profile-gpu-rendering/index.html">
- Profile GPU Rendering Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/index.html">
- Hierarchy Viewer Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows how to visualize overdraw on your mobile device by color-coding
- interface elements based on how often they are drawn underneath.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Showing where an app might be doing more rendering work than necessary.</li>
-
- <li>Helping you see where you might be able to reduce rendering overhead.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
- </ul>
-
-
- <h2 id="VisualizingOverdraw">Visualizing Overdraw on your Mobile Device</h2>
-
- <ul class="no-bullet">
- <!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img
- src="{@docRoot}images/tools/performance/debug-gpu-overdraw/gettingstarted_image01.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Steps for turning on Debug GPU Overdraw.
- </p>
- </div>
-
- <li>On your mobile device, go to <b>Settings</b> and tap <b>Developer Options</b>.</li>
-
- <li>In the <em>Hardware accelerated rendering</em> section,
- select <b>Debug GPU Overdraw</b>.</li>
-
- <li>In the <b>Debug GPU overdraw</b> popup, select <b>Show overdraw areas</b>.</li>
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="5">
-
- <div class="figure" style="padding-right:100px">
- <img
- src="{@docRoot}images/tools/performance/debug-gpu-overdraw/gettingstarted_image02.png"
- alt=""
- width="180px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Example of<br>Debug GPU Overdraw output.
- </p>
- </div>
-
- <li>Don't panic as your screen turns into a delirium of colors.
- The coloring is provided to help you diagnose your app's display behavior.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="6">
-
- <div class="figure" style="">
- <img
- src="{@docRoot}images/tools/performance/debug-gpu-overdraw/gettingstarted_image03.png"
- alt=""
- width="300px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Color key for Debug GPU Overdraw output.
- </p>
- </div>
-
- <br><br>
- <li>The colors are hinting at the amount of overdraw on your screen for each pixel, as
- follows:
-
- <ul>
- <li><b>True color:</b> No overdraw</li>
- <li><b>Blue:</b> Overdrawn once</li>
- <li><b>Green:</b> Overdrawn twice</li>
- <li><b>Pink:</b> Overdrawn three times</li>
- <li><b>Red:</b> Overdrawn four or more times</li>
- </ul>
- </li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="7">
-
- <div class="figure" style="">
- <img
- src="{@docRoot}images/tools/performance/debug-gpu-overdraw/gettingstarted_image04.png"
- alt=""
- width="300px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Examples of undesirable and desirable
- <br>Debug GPU Overdraw output.
- </p>
- </div>
-
- <br><br><br>
- <li>Some overdraw is unavoidable. As you are tuning your app's
- user interface, the goal is to arrive at a visualization that shows mostly true
- colors and 1X overdraw in blue.</li>
-
- </ol>
-</div></li>
-</ul>
+++ /dev/null
-page.title=Heap Viewer Walkthrough
-meta.tags="android, performance, profiling, tools, memory, memoryleaks, memoryheap"
-page.tags="android", "performance", "profiling", "tools", "memory", "memoryleaks", "memoryheap"
-page.metaDescription=Report in real-time how many objects of what types and sizes your application is allocating and find memory leaks.
-page.image=tools/performance/thumbnails/tools_heap_viewer.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithHeapViewer">Working with Heap Viewer</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/memory-monitor/index.html">
- Memory Monitor Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/allocation-tracker/index.html">
- Allocation Tracker Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/comparison.html">
- Comparison: Memory Monitor, Heap Viewer, Allocation Tracker</a>
- <li><a href="{@docRoot}tools/performance/traceview/index.html">
- Traceview Walkthrough</a></li>
-</ul>
-
-</div>
-
-
- <p>This walkthrough shows the basic usage and workflow for the Heap Viewer tool. Heap Viewer
- reports in real-time what <i>types</i> of objects your application has allocated, how many, and
- their sizes on the heap.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Getting a sense of how your app allocates and frees memory.</li>
-
- <li>Identifying memory leaks.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device running Android 5.0 or higher with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
-
- <li>Application code. Use your own code, or the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
- <h2 id="WorkingWithHeapViewer">Working with Heap Viewer</h2>
-
- <ul class="no-bullet">
- <!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/heap-viewer/gettingstarted_image01.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Starting Memory Monitor.
- </p>
- </div>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>Open your application in Android Studio, build the source, and run it on your device or
- emulator.</li>
-
- <li>Start the Android Device Monitor from Android Studio: <strong>Tools -> Android
- -> Android Device Monitor</strong>.
-
- <p>You can also start the <a href="{@docRoot}tools/studio/index.html#mem-cpu">Memory Monitor</a>
- in Android Studio: Click the <em>Android</em> tab in the lower-left corner of the application
- window. The CPU and Memory Monitor views appear.</p> </li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="4">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/heap-viewer/gettingstarted_image02.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Steps for Using Heap Viewer.
- </p>
- </div>
-
- <li>In the device and application drop-downs, select the app you want to monitor.</li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="8">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/heap-viewer/gettingstarted_image03.png"
- alt=""
- width="300px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Update Heap button.
- </p>
- </div>
-
- <li>To save a heap dump, click the Dump Java Heap icon. The heap snapshot file
- with the filename <code>Snapshot-yyyy.mm.dd-hh.mm.ss.hprof</code> appears in the
- <em>Captures</em> tab.</li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="9">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/heap-viewer/gettingstarted_image04.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Triggering GC (Garbage Collection).
- </p>
- </div>
-
- <li>Note the <em>Heap updates will happen
- after every GC for this client.</em> message.</li>
-
- <li>Click the <strong>Initiate CG</strong> icon to
- trigger a garbage collection event.
- </li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="11">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/heap-viewer/gettingstarted_image05.png"
- alt=""
- width="480px" />
- <p class="img-caption">
- <strong>Figure 5. </strong>Example Heap Viewer output.
- </p>
- </div>
-
- <li>Double-click the heap snapshot file to open the heap viewer and see detailed information
- about the current allocations on the heap.</li>
-
- </ol>
-</div></li>
-
- </ul>
+++ /dev/null
-page.title=Hierarchy Viewer Walkthrough
-meta.tags="android, performance, profiling, tools, rendering, hierarchyviewer"
-page.tags="android", "performance", "profiling", "tools", "rendering", "hierarchyviewer"
-page.metaDescription=Visualize your app's view hierarchy to help you simplify your layouts.
-page.image=tools/performance/thumbnails/tools_hierarchy_viewer.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithHierarchyViewer">Working with Hierarchy Viewer</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/setup.html">
- Device Setup for Hierarchy Viewer</a></li>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/profiling.html">
- Profiling with Hierarchy Viewer</a></li>
- <li><a href=
- "http://developer.android.com/tools/debugging/debugging-ui.html#viewhierarchy">Hierarchy Viewer
- </a></li>
- <li><a href="/guide/topics/ui/overview.html#Layout">View Hierarchies</a></li>
- <li><a href="{@docRoot}tools/performance/importing-legacy-apps.html">
- Importing Legacy Apps into Android Studio<a></li>
- <li><a href="{@docRoot}tools/device.html">Using Hardware Devices</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows the basic usage and workflow for the Hierarchy Viewer tool.</p>
-
- <p>The Hierarchy Viewer tool visualizes your app's <a href=
- "http://developer.android.com/guide/topics/ui/overview.html#Layout">view hierarchy</a> and
- profiles the relative rendering speed for each view.
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Simplifying your view hierarchy to reduce overdraw, and make it easier to manage.</li>
-
- <li>Finding potential rendering performance bottlenecks related to the structure and shape of your
- view hierarchy.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device set up to work with Hierarchy Viewer:</li>
-
- <li style="list-style: none; display: inline">
- <ol>
- <li>You must have <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer
- Options</a> enabled on your mobile device. You must use a physical device to get
- accurate measurements.</li>
-
- <li>Set an {@code ANDROID_HVPROTO} environment variable on the desktop machine
- that is connected to your device. For more information, see
- <a href="{@docRoot}tools/performance/hierarchy-viewer/setup.html">Device Setup for Hierarchy Viewer</a>.</li>
- </ol>
- </li>
-
- <li>Debuggable app code with a view hierarchy. Use your own code, or the code for the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
- <h2 id="WorkingWithHierarchyViewer">Working with Hierarchy Viewer</h2>
-
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image001.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Starting Android Device Monitor.
- </p>
- </div>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>Open your application in Android Studio, build the source, and run it on your device.</li>
-
- <li>From Android Studio, start the Android Device Monitor: <b>Tools > Android >
- Android Device Monitor</b>.</li>
-
- <li>Allow <b>USB Debugging</b> on your phone (if asked).</li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="6">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image005.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Android Device Monitor.
- </p>
- </div>
-
- <li>Figure 2 illustrates what is initially shown in the Device Monitor tool. This varies
- depending on your setup.
- <p>Make sure your device
- and the package for your application are showing in the Devices (DDMS mode) or Windows
- (Hierarchy Viewer mode) tab. You can choose <b>Window > Reset Perspective</b> to get
- back to the default arrangement.</p>
- <p>If the app does not appear, make sure you
- followed the <a href="{@docRoot}tools/performance/hierarchy-viewer/setup.html"> device
- setup instructions</a>, then start over at step 1.</p></li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="7">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image002.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Changing Perspective to Hierarchy Viewer.
- </p>
- </div>
-
- <li>In Android Device Monitor (ADM), in the menu bar, choose <b>Window > Open
- Perspective</b>, and in the popup click <b>Hierarchy View</b>.<br>
-
- <p>OR</p>
- <p> Click the <b>Hierarchy View</b> button if it's already visible.<br>
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image003.png">
- </p></li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="9">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image006.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Hierarchy Viewer layout.
- </p>
- </div>
-
- <li>If not already open, the Hierarchy View panes open.<br>
- The example screen in Figure 4 shows an example of these panes.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="10">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image004.png"
- alt=""
- width="240px" />
- <p class="img-caption">
- <strong>Figure 5. </strong>Resetting the Perspective.
- </p>
- </div>
-
- <li>If you see a different window arrangement, in Android Device Manager, use
- <b>Window > Reset Perspective</b> to return to the default layout for this tutorial.
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="11">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image007.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 6. </strong>Populated Hierarchy Viewer.
- </p>
- </div>
-
- <li>Double-click your application in the Windows tab. This populates the panes with the
- view hierarchy of your application.
- This display is a static representation of the complete view hierarchy defined for the
- app.</li>
-
- <li>You can adjust the sizes of the panes and ADM will preserve your
- arrangement in future sessions.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="13">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image008.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 7. </strong>Hierarchy Viewer panes.
- </p>
- </div>
-
- <li>If necessary, click the <b>Layout View</b> tab to hide the Console and show a wireframe of
- your layout. The outline of the currently selected view is red. Click an outline to select
- it.</li>
-
- <li>The rest of the panes:
-
- <ul>
- <li>The <b>Tree Overview</b> in the upper right gives you a bird's-eye view of your
- app's complete <a href=
- "http://developer.android.com/guide/topics/ui/overview.html#Layout">View</a> <a href=
- "http://developer.android.com/guide/topics/ui/overview.html#Layout">Hierarchy</a>.</li>
-
- <li>In the <b>Tree Overview</b>, move the gray viewport rectangle to change what section of
- your hierarchy shows in the <b>Tree View</b> pane (in the center).</li>
-
- <li>In the <b>Tree View</b>, you can drag and zoom the tree using your mouse.</li>
- </ul>
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="15">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image009.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 7. </strong>Parts of the View node display.
- </p>
- </div>
-
- <li>Click on a View node to display details. Here is an annotated close-up of a node
- and its details.</li>
-
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="16">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image010.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 8. </strong>Location of View Properties tab.
- </p>
- </div>
-
- <li>Click the <b>View Properties</b> tab at the top right (next to the Windows tab) to see
- properties of the selected View node.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="17">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image011.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 9. </strong>Rendering a view in a popup.
- </p>
- </div>
-
- <li>Double-click a View node in the Tree View to render it in a popup window.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="18">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image012.png"
- alt=""
- width="240px" />
- <p class="img-caption">
- <strong>Figure 10. </strong>Node with its type and id.
- </p>
- </div>
-
- <li>Nodes in the Tree View show a Type, which indicates the View class,
- and an id, which is the view identifier in your code.</li>
-
- </ol>
-</div></li>
-</ul>
+++ /dev/null
-page.title=Profiling with Hierarchy Viewer
-meta.tags="android, performance, profiling, tools, rendering, hierarchyviewer
-page.tags="android", "performance", "profiling", "tools", "rendering", "hierarchyviewer"
-page.metaDescription=Profile the relative rendering speed for each view.
-page.image=tools/performance/thumbnails/tools_hierarchy_viewer_profiling.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#ProfilingWithHierarchyViewer">Profiling with Hierarchy Viewer</a></li>
- <li><a href="#InterpretingResults">Interpreting Profiling Results</a></li>
-
-</ul>
-</div>
-
-<p>This walkthrough shows you how to profile your app's view hiearchy with
- Hierarchy Viewer, and how to interpret the results.</p>
-
-<h2 id="WhatYouNeed">Prerequisites</h2>
-
-<ul>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/setup.html">
- Device Setup for Hierarchy Viewer</a></li>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/index.html">
- Hierarchy Viewer Walkthrough</a></li>
-</ul>
-
-<h2 id="ProfilingWithHierarchyViewer">Profiling Steps</h2>
-
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
-
- <ol class="padded">
-
- <div class="figure" style="">
-<img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image014.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>View hierarchy after profiling.
- </p>
- </div>
-
- <li>Start Hierarchy Viewer for your app.</li>
-
- <li>In the <b>Tree View</b> or the <b>Layout View</b>, click on the View node whose
- children you want to profile.</li>
-
- <li>To start profiling, click the small button with three circles
-<img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image013.png">
- at the top of the Tree View.
-
- </li>
-
- <li>For large view hierarchies, profiling may take a few seconds.</li>
-
- <li>Each view in your subtree gets three dots, which can be green, yellow, or red.
-
- <ul>
- <li>The left dot represents the Draw Process of the rendering pipeline.</li>
- <li>The middle dot represents the Layout Phase.</li>
- <li>The right dot represents the Execute Phase.</li>
- </ul>
- </li>
-
-</ol></div>
-
-</li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="5">
-
- <div class="figure" style="">
-<img src="{@docRoot}images/tools/performance/hierarchy-viewer/gettingstarted_image015.png"
- alt=""
- width="240px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>How the colored dots relate<br>to the rendering pipeline.
- </p>
- </div>
-
- <li>These dots roughly correspond to the Measure,
- Layout, and Draw
- phases of the processing pipeline.</li>
-
- <li>The color of the dots indicates the relative performance
- of this node in respect to all other profiled nodes.
-
- <ul>
- <li><strong>Green</strong> means the view renders faster than at least
- half of the other views.</li>
-
- <li><strong>Yellow</strong> means the view renders faster than the bottom
- half of the other views.</li>
-
- <li><strong>Red</strong> means the view is among the slowest
- half of views.</li>
- </ul>
- </li>
-
- </ol>
-</div></li>
-</ul>
-
- <h2 id="InterpretingResults">Interpreting Hierarchy Viewer Profiling Results</h2>
-
- <p>Hierarchy Viewer measures the <em>relative performance</em> of a
- node</b>, so there are always red nodes in a profile, and it
- doesn't necessarily mean that view is too slow for the users of
- your app.</p>
-
- <p>Hierarchy Viewer software rasterizes your Activity to acquire the timing
- information. Rasterization is the process of taking a high-level primitive, such as a
- circle or a vector font, and turning it into pixels on the screen. Typically,
- rasterization is done by the GPU on your device, but in the case of
- software rasterization, rendering is done on the CPU with
- ordinary software. This means that the absolute
- reported timings are correct relative to each other, but are bloated and vary
- depending on the overall and changing CPU workload on your device and PC. Profile
- several times to get a feel for the average measurements.</p>
-
- <p>The following are guidelines for interpreting Hierarchy Viewer profiling output.</p>
-
- <p>A red node is a potential problem in any situation where your app has
- unexpectedly slow performance. In a relative setting, there is always a
- slowest node; make sure it is the node you expect.
- The following examples illustrate how to interpret red dots.</p>
-
- <ul>
- <li>Look for red dots in leaf nodes or view groups with only a few children. This
- might point to a problem. Your app may not be slow, or it may not be slow on your
- device, but you need to be aware of why that dot is red.
- <a href="{@docRoot}tools/performance/systrace/index.html"> Systrace</a> or
- <a href="{@docRoot}tools/performance/traceview/index.html"> Traceview</a>
- can give you additional information. </li>
-
- <li>If you have a view group with many children and a red measure phase, take a
- look at the children to see how they are performing.</li>
-
- <li>A view with yellow or even red dots might not be performing slowly on the
- device. That's where the actual numbers are helpful.
- <a href="{@docRoot}tools/performance/systrace/index.html"> Systrace</a> or
- <a href="{@docRoot}tools/performance/traceview/index.html"> Traceview</a>
- can give you additional information.</li>
-
- <li>If the root view of a hierarchy has a red measure phase, red layout phase, and
- yellow draw phase, this is somewhat typical, because it's the
- parent of all the other views.</li>
-
- <li>If a leaf node in a tree with 20+ views has a red draw phase, this <i>is</i> a
- problem. Check your OnDraw method for code that shouldn't be
- there.</li>
- </ul>
+++ /dev/null
-page.title=Device Setup for Hierarchy Viewer
-meta.tags="android, performance, profiling, tools, rendering, hierarchyviewer"
-page.tags="android", "performance", "profiling", "tools", "rendering", "hierarchyviewer"
-page.metaDescription=Set up your mobile device to work with Hierarchy Viewer.
-page.image=tools/performance/thumbnails/tools_hierarchy_viewer.png
-page.article=true
-
-@jd:body
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/index.html">
- Hierarchy Viewer Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/profiling.html">
- Profiling with Hierarchy Viewer</a></li>
-</ul>
-
-</div>
-
- <p>To run Hierarchy Viewer, you must enable Developer Options on your mobile device and perform
- some setup on your computer.</p>
-
- <h2>Configuring Devices</h2>
-
- <ol>
- <li><p>Enable <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- on your mobile device.</p></li>
-
- <li>Depending on the type of device you have, do one of the following:
- <ul>
- <li>If you have a locked device running Android 4.0 or lower, follow the instructions
- for <a href=
- "https://github.com/romainguy/ViewServer">installing and configuring ViewServer</a>.
- </li>
- <li>If you have an unlocked device running Android 4.0 or lower,
- no further configuration is needed.</li>
- <li>If you have a device running Android 4.1 or higher, you must set an environment
- variable on your development machine. For more information,
- see <a href="#hvproto-variable">Setting the ANDROID_HVPROTO variable</a>
- </ul>
- </li>
- </ol>
-
-
- <h2 id="hvproto-variable">Setting the ANDROID_HVPROTO variable</h2>
-
- <h3>Windows</h3>
-
- <ol>
- <li>Click <b>My Computer > Property > Advanced > Environment Variables.</b></li>
-
- <li>Click <b>New.</b></li>
-
- <li>In variables name put: <code>ANDROID_HVPROTO</code></li>
-
- <li>In variable value put: <code>ddm</code></li>
-
- <li>Click <b>OK</b><./li>
- </ol>
-
- <h3>Mac</h3>
-
- <ol>
- <li>Edit <code>~/.bash_profile</code></li>
-
- <li>Add:
- <br><code>#Hierarchy Viewer Variable
- <br>export ANDROID_HVPROTO=ddm</code>
- </li>
-
- <li><code>source ~/.bash_profile</code></li>
- </ol>
-
- <h3>Linux</h3>
-
- <ol>
- <li>Edit <code>~/.bash_profile</code></li>
-
- <li>Add:
-
- <br><code>#Hierarchy Viewer Variable
- <br>export ANDROID_HVPROTO=ddm</code>
- </li>
-
- <li><code>source ~/.bash_profile</code></li>
- </ol>
+++ /dev/null
-page.title=Importing Legacy Apps into Android Studio
-meta.tags="android, performance, profiling, tools"
-page.tags="android", "performance", "profiling", "tools"
-page.metaDescription=Required changes when importing legacy apps into Android Studio.
-page.article=true
-
-@jd:body
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#StepsForImporting">Steps for Importing</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="/tools/device.html">Using Hardware Devices</a></li>
- <li><a href="/tools/help/index.html">Tools</a></li>
-</ul>
-
-</div>
-
-
- <p>Importing some pre-Android-1.0 projects into Android 1.0 or newer can trigger a series of
- errors. This document shows you how to resolve them, using a version of the Sunshine app used in
- the <a href="https://www.udacity.com/course/ud853">Android Fundamentals Udacity Course</a> as an
- example.</p>
-
- <p><b>CAVEAT:</b> As with all documentation of this kind, the details are likely to vary for each
- application and each update of Android Studio.</p>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>The latest version of <a href="http://developer.android.com/sdk/index.html">Android
- Studio</a> (this document uses version 1.1).</li>
-
- <li>It helps to know how to <a href="https://developer.android.com/training/index.html">build
- and run apps from Android Studio</a> on your device.</li>
-
- <li>To use Sunshine, you need to download code from <a href=
- "https://github.com/">github.com</a>. More info at <a href=
- "https://help.github.com/">help.github.com</a>.</li>
- </ul>
-
- <h2 id="StepsForImporting">Steps for Importing Sunshine into Android Studio 1.1.0</h2>
-
- <ol>
- <li>Download Sunshine ZIP from GitHub: <a href=
- "https://github.com/udacity/sunshine/tree/6.10-update-map-intent">https://github.com/udacity/sunshine/tree/6.10-update-map-intent</a>.
- (If you are having any problems with Android Studio or the app, use the following version, or
- your own app, to follow along with the example.<a href=
- "https://github.com/udacity/sunshine/tree/3.13-add-share-action-provider">https://github.com/udacity/sunshine/tree/3.13-add-share-action-provider</a>)
-
- <li>Unzip the application to extract the code folder.</li>
-
- <li>Start Android Studio. (This works best if you close all projects, then restart.)</li>
-
- <li>Click <b>Import</b> <b>project (Eclipse ADT, Gradle, etc.)</b>.
- <br><img src="{@docRoot}images/tools/performance/import_image001.png">
- </li>
-
- <li>In the popup, find and select the Sunshine-6-10-updated-map-intent folder and click
- <b>OK</b>.
- <br><img src="{@docRoot}images/tools/performance/import_image002.png">
- </li>
-
- <li>If prompted, choose a destination folder for your project. If prompted to choose a build
- system, choose Gradle. (These prompts vary, depending on your project and Android Studio
- version.) If you need more guidance, see this <a href=
- "http://www.lynda.com/articles/eclipse-into-android-studio">Lynda tutorial</a>.</li>
-
- <li>Wait for the import to complete. If you see no errors, you are now ready to work with your
- app.
-
- <p><b>If you get a Gradle error:</b></p>
-
- <li>If you get a Gradle error, you have some extra work to do.(Because the Import
- didn(t finish, at this point, you may only see the <b>Gradle
- Scripts</b> directory in your Project view.)</li>
-
- <li>You may see the link <b>Install missing platform(s) and sync
- project</b>, or a link to install missing build tools.
- Click whatever link and
- proceed.</li>
-
- <li>The next time through, your build will fail with:
- <br><img src="{@docRoot}images/tools/performance/import_image003.png">
- </li>
-
- <li>Click the <b>Fix plugin version and re-import project</b> link
- in the error message. This will rebuild the app and present you with new of errors.
- <br><img src="{@docRoot}images/tools/performance/import_image004.png">
- </li>
-
- <li>Click the <b>Gradle Settings</b> link in the error message.</li>
-
- <li>Check the <b>Use auto-import</b> and click <b>OK</b>.
- <br><img src="{@docRoot}images/tools/performance/import_image005.png">
- </li>
-
- <li>Expand the project hierarchy and find the <b>build.gradle file</b>.The file you are looking
- for is not the one showing at the top level, but the one inside <b>Sunshine</b> <b>></b>
- <b>app > build.gradle</b>, as shown below.
- <br><img src="{@docRoot}images/tools/performance/import_image006.png">
- </li>
-
- <li>Double-click the <code>build.gradle</code> file.</li>
-
- <li>Make the following changes to the file:</li>
- <ul>
- <li>Set <code>compileSdkVersion 21</code></li>
-
- <li>Set <code>targetSdkVersion 21</code></li>
-
- <li>Replace <code>runProguard</code> with <code>minifyEnabled</code></li>
- </ul>
-
- <p>Your file should look like this: </p>
- <img src="{@docRoot}images/tools/performance/import_image007.png">
- </li>
-
- <li>Save (Ctrl-S).</li>
-
- <p>For the following two messages (Steps 18/19), what you see might vary. You might see either
- message or both messages in sequence. Click the appropriate links to continue until the Language
- Level Changed dialog opens.</p>
-
- <li>In the code view bar, click the <b>Try again</b> link.
- <br><img src="{@docRoot}images/tools/performance/import_image008.png">
- </li>
-
- <li>If you see these warnings, click the <b>Sync now</b> link.
- <br><img src="{@docRoot}images/tools/performance/import_image009.png">
- </li>
-
- <li>In the Language Level Changed dialog, click <b>Yes</b>. And if you get the Gradle Running
- dialog, <b>Yes</b> again.
- <br><img src="{@docRoot}images/tools/performance/import_image010.png">
- </li>
-
- <li>After the project reloads, run the app on your device. (If it crashes the first time, try
- again, and it will run.)
- <br><img src="{@docRoot}images/tools/performance/import_image011.png">
- </li>
- </ol>
-
+++ /dev/null
-page.title=Performance Profiling Tools
-meta.tags="android, develop, performance, profiling, tools, gather"
-page.tags="android", "develop", "performance", "profiling", "tools" "gather"
-page.metaDescription=Android Studio profiling tools for evaluating your app's performance.
-page.article=true
-
-@jd:body
-
- <p>Putting pixels on the screen involves four primary pieces of hardware.
- To greatly simplify, the CPU computes display lists, the GPU renders images to
- the display, the memory stores images and data, and the battery provides
- electrical power. Each of these pieces of hardware has constraints; pushing
- or exceeding those constraints causes your app to be slow, have
- bad display performance, or exhaust the battery.
-
- <p>To discover what causes your specific performance problems, you need to
- take a look under the hood, use tools to collect data about your app's
- execution behavior, surface that data as lists and
- graphics, understand and analyze what you see, and improve your code.</p>
-
- <p>Android Studio and your device provide profiling tools to record and
- visualize the rendering, compute, memory, and battery performance of your
- app.</p>
-
-<p class="note">
- <strong>Note:</strong> While profiling an app, you should <a href=
- "{@docRoot}tools/building/building-studio.html#disable-ir">disable Instant
- Run</a>. There is a small performance impact when <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">using Instant
- Run</a> and a slightly larger impact when updating methods. This
- performance impact could interfere with information provided by performance
- profiling tools. Additionally, the stub methods generated while using the
- feature can complicate stack traces.
-</p>
-
-<h2 id="rendering-tools">Rendering Analysis Tools</h2>
-
-<p>Visualize the rendering behavior and performance of your app.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/performance/rendering"
- data-cardSizes="9x3"
- data-maxResults="6">
- </div>
-</div>
-
-<h2 id="memory-tools">Memory Analysis Tools</h2>
-
-<p>Visualize the memory behavior and performance of your app.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/performance/memory"
- data-cardSizes="9x3"
- data-maxResults="6">
- </div>
-</div>
-
-<h2 id="cpu-tools">Compute Analysis Tools</h2>
-
-<p>Visualize the CPU behavior and performance of your app.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/performance/cpu"
- data-cardSizes="9x3"
- data-maxResults="4">
- </div>
-</div>
-
-<h2 id="battery-tools">Battery Analysis Tools</h2>
-
-<p>Visualize the battery behavior and performance of your app.</p>
-
-<div class="dynamic-grid">
- <div class="resource-widget resource-flow-layout landing col-12"
- data-query="collection:tools/performance/battery"
- data-cardSizes="9x3"
- data-maxResults="4">
- </div>
-</div>
-
-
+++ /dev/null
-page.title=Memory Monitor Walkthrough
-meta.tags="android, performance, profiling, tools, memory, memoryleaks, garbagecollection, memorymonitor"
-page.tags="android", "performance", "profiling", "tools", "memory", "memoryleaks", "garbagecollection", "memorymonitor"
-page.metaDescription=Graph memory usage and garbage collection events for your app in real-time.
-page.image=tools/performance/thumbnails/tools_memory_monitor.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithMemoryMonitor">Working with Memory Monitor</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/heap-viewer/index.html">
- Heap Viewer Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/allocation-tracker/index.html">
- Allocation Tracker Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/comparison.html">
- Comparison: Memory Monitor, Heap Viewer, Allocation Tracker</a>
- <li><a href="{@docRoot}tools/performance/traceview/index.html">
- Traceview Walkthrough</a></li>
-</ul>
-
-</div>
-
-
- <p>This walkthrough shows the basic usage and workflow for the Memory Monitor tool in Android
- Studio. Memory Monitor reports in real-time how your app allocates memory.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Showing available and used memory in a graph, and garbage collection events over time.</li>
-
- <li>Quickly testing whether app slowness might be related
- to excessive garbage collection events.</li>
-
- <li>Quickly testing whether app crashes may be related to running out of
- memory.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
-
- <li>An Application with USB Debugging enabled. Use your own, or the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
- <h2 id="WorkingWithMemoryMonitor">Working with Memory Monitor</h2>
-
- <ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/memory-monitor/gettingstarted_image001.png"
- alt=""
- width="300px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Enable ADB Integration.
- </p>
- </div>
-
- <li>If you're using a mobile device, connect it to your computer.</li>
-
- <li>Open your application in Android Studio, build the source,
- and run it on your device or emulator.</li>
-
- <li>In Android Studio, choose <strong>Tools > Android > Enable ADB Integration</strong>.
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="4">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/memory-monitor/gettingstarted_image001b.png"
- alt=""
- width="240px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>The Android Monitor tab.
- </p>
- </div>
-
- <li>Click the <strong>Android Monitor</strong> tab at the bottom of the runtime window.</li>
-
- <li>Click the <strong>Memory</strong> tab to show the Memory Monitor tool.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="6">
-
- <div class="figure" style="">
- <img src="/images/tools/performance/memory-monitor/gettingstarted_image002.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>The Memory Monitor pane.
- </p>
- </div>
-
- <li>Choose your device from the drop-down menu at the top left of the pane.
- </li>
-
- <li>Choose the Activity to monitor from the drop-down menu at the top right of the pane.
- </li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="8">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/memory-monitor/gettingstarted_image003.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Allocated and free memory in Memory Monitor.
- </p>
- </div>
-
- <li>Once Memory Monitor starts tracking your device, a stacked graph appears,
- tracking memory usage over time.
-
- <p>Dark blue: Amount of memory that your app
- is currently using.</p>
-
- <p>Light blue: Available, unallocated memory.</p>
- </li>
-
- <li>Over time, this graph updates, showing changes in memory usage.</li>
-
- <li>As your app allocates and frees memory, the allocated amount shown in the
- graph changes.</li>
-
- <li>When you see the allocated memory drop by a large amount, a garbage
- collection (GC) event has occurred.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="12">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/memory-monitor/gettingstarted_image005.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 5. </strong>Forcing a GC (Garbage Collection) event.
- </p>
- </div>
-
- <li>You can force a garbage collection event by clicking on the garbage truck
- icon
-<img src="{@docRoot}images/tools/performance/memory-monitor/gettingstarted_image004.png">.
- </li>
-
- </ol>
-</div></li>
-</ul>
-
-
+++ /dev/null
-page.title=Profiling GPU Rendering Walkthrough
-meta.tags="android, performance, profiling, tools, rendering, gpu"
-page.tags="android", "performance", "profiling", "tools", "rendering", "gpu"
-page.metaDescription=Overlay a graph on your device, showing how long it takes to render UI elements relative to the 16-ms-per-frame benchmark.
-page.image=tools/performance/thumbnails/tools_profile_gpu_rendering.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#ProfileGPURendering">Profile GPU Rendering</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/debug-gpu-overdraw/index.html">
- Debug GPU Overdraw Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/hierarchy-viewer/index.html">
- Hierarchy Viewer Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows how to use Profile GPU Rendering on your mobile device.</p>
-
- <p>Profile GPU Rendering gives you a quick visual representation of how much time it takes to
- render the frames of a UI window relative to the 16-ms-per-frame benchmark.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Quickly seeing how a UI window performs against the 16-ms-per-frame target.</li>
-
- <li>Identifying whether any part of the rendering pipeline stands out in using processing
- time.</li>
-
- <li>Looking for spikes in frame rendering time associated with user or program actions.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device running at least Android 4.1 with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
- </ul>
-
-<h2 id="ProfileGPURendering">Working with Profile GPU Rendering</h2>
-
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img
-src="{@docRoot}images/tools/performance/profile-gpu-rendering/gettingstarted_image001.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Turning on Profile GPU Rendering.
- </p>
- </div>
-
- <li>On your mobile device, go to <b>Settings ></b> <b>Developer Options</b>.</li>
-
- <li>In the <em>Monitoring</em> section, select <b>Profile GPU Rendering</b>.</li>
-
- <li>In the Profile GPU Rendering popup, choose <b>On screen as bars</b> to overlay the graphs
- on the screen of your mobile device.</li>
-
- <li>Go to the app that you want to profile.</li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
-
- <div class="figure" style="">
- <img
-src="{@docRoot}images/tools/performance/profile-gpu-rendering/gettingstarted_image002.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Screen when Profile GPU Rendering is on.
- </p>
- </div>
-
- <h3>What you see:</h3>
-
- <ul>
- <li>For each visible application, the tool displays a graph.</li>
-
- <li>The horizontal axis shows time elapsing, and the vertical axis time per frame in
- milliseconds.</li>
-
- <li>As you interact with your application, vertical bars show up on your screen, appearing
- from left to right, graphing frame performance over time.</li>
-
- <li>Each vertical bar represents one frame of rendering.
- The taller the bar, the longer it took to render.</li>
-
- <li>The green line marks the 16 millisecond target. Every time a frame crosses the green line,
- your app is missing a frame, and your users may see this as stuttering images.
- </ul>
-
-</div></li>
-
-<li style="list-style-type:none;><!-- fix issue with visible disc -->
-<div style="overflow:hidden">
-<hr>
-
- <h3>The Profile GPU Rendering Graph</h3>
-
- <img
-src="{@docRoot}images/tools/performance/profile-gpu-rendering/gettingstarted_image003.png"
- alt=""
- height="" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Enlarged Annotated Profile GPU Rendering graph.
- </p>
-
- <p>In this enlarged image of the Profile GPU Rending graph you can see the colored sections
- of the graph, and what phase of the rendering pipeline each color represents.</p>
-
- <ul>
- <li>The <b>green line</b> represents 16 milliseconds. To achieve 60 frames per second,
- the vertical bar for each frame needs
- to stay below this 16 ms mark. Any time a bar pushes above this line, there may be pauses in
- the animations.</li>
-
- <li>Each bar has a blue, purple (only for Android version 4.0 and higher),
- red, and orange component.</p>
-
- <li>The <b>blue</b> section of the bar represents the time used to create and update the
- View's display lists. If this part of the bar is tall, there may be a
- lot of custom view drawing, or a lot of work in onDraw methods.</li>
-
- <li>Android 4.0 and higher: The <b>purple</b> section of the bar represents the time spent
- transferring resources to the render thread.</li>
-
- <li>The <b>red</b> section of the bar represents the time spent by
- Android's 2D renderer issuing commands to OpenGL to draw and redraw
- display lists. The height of this bar is directly proportional to the sum of the time it takes each
- display list to execute—more display lists equals a taller red bar.</li>
-
- <li>The <b>orange</b> section of the bar represents the time the CPU is waiting for the GPU to
- finish its work. If this bar gets tall, it means the app is doing too much work on the GPU.
- </li>
- </ul>
-
- <p class="note"><strong>Note:</strong>
- While this tool is named Profile GPU Rendering, all monitored processes actually
- occur in the CPU. Rendering happens by submitting commands to the GPU, and the GPU renders the
- screen asynchronously. In certain situations, the GPU can have too much work to do,
- and your CPU will have to wait before it can submit new commands.
- When this happens, you'll see spikes in the Process (orange bar) and Execute (red bar)
- stages, and the command submission will block until more room is made on the
- GPU command queue.
- </p>
-
- </div></li>
-</ul>
-
-
-
-
+++ /dev/null
-page.title=Systrace Walkthrough
-meta.tags="android, performance, profiling, tools, compute, systrace"
-page.tags="android", "performance", "profiling", "tools", "compute", "systrace"
-page.metaDescription=Collect system and application process execution data to identify performance bottlenecks.
-page.image=tools/performance/thumbnails/tools_systrace.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithSystrace">Working with Systrace</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/traceview/index.html">
- Traceview Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/allocation-tracker/index.html">
- Allocation Tracker Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows the basic usage and workflow for the Systrace tool in the Android
- Device Monitor.</p>
-
- <p>Systrace collects system and application process execution data and generates detailed,
- interactive reports from devices running Android 4.1 and higher.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Evaluating container performance.</li>
-
- <li>Finding performance bottlenecks in the execution of your code.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>Android SDK Tools 20.</li>
-
- <li><a href="http://www.python.org/">Python</a> installed and included in your development
- computer's execution path.</li>
-
- <li>A mobile device running at least Android 4.1 with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- and USB Debugging enabled in Developer Options.</li>
-
- <li>Application code. Use your own code, or the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
- <h2 id="WorkingWithSystrace">Working with Systrace</h2>
-
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/systrace/gettingstarted_image001.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Starting Android Device Monitor.
- </p>
- </div>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>Open your application in Android Studio, build the source, and run it on your device.</li>
-
- <li>From Android Studio, start the Android Device Monitor: <b>Tools -> Android -> Android
- Device</b> <b>Monitor</b>.
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="4">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/systrace/gettingstarted_image003.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Steps for starting Systrace.
- </p>
- </div>
-
- <li>Make sure your
- device and the package for your application are showing in the Devices (DDMS mode) or
- Windows (Hierarchy Viewer mode) tab.
-
- <p>You can choose <b>Window > Reset Perspective</b> to
- get back to the default arrangement.</p>
- </li>
-
- <li>Click the <b>DDMS</b> button, because Systrace is one of the DDMS tools.</li>
-
- <li>Click the <b>Systrace</b> button
- <img src="{@docRoot}images/tools/performance/systrace/gettingstarted_image002.png">.</li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="7">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/systrace/gettingstarted_image004.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Steps for creating a trace.
- </p>
- </div>
-
- <li>In the <b>Android System Trace</b> popup, choose your settings for the trace.
-
- <ul>
- <li><b>Destination File:</b> Where the trace is stored as an HTML file. Default is in
- your home directory as <code>trace.html</code>.</li>
-
- <li><b>Trace Duration:</b> Default is 5 seconds,
- and 30 seconds is a good time to choose.</li>
-
- <li><b>Trace Buffer size:</b> Default is unlimited.</li>
-
- <li><b>Enable Application Traces from:</b> Make sure your app is selected.</li>
-
- <li><b>Select tags to enable:</b> Choose at least one value to trace, for example Graphics
- and View System.</li>
- </ul>
- </li>
-
- <li>Click <b>OK</b> to start tracing.</li>
-
- <li>Interact with your app.</li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="10">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/systrace/gettingstarted_image005.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Example systrace output in browser.
- </p>
- </div>
-
- <li>When the trace is done, you are automatically returned to Android Device Monitor.</li>
-
- <li>Go to your home directory, or the directory you chose as the file destination.</li>
-
- <li>Open the <code>trace.html</code> file in your browser.</li>
-
- </ol>
-</div></li>
-</ul>
-
-
+++ /dev/null
-page.title=Traceview Walkthrough
-meta.tags="android, performance, profiling, tools, compute, traceview"
-page.tags="android", "performance", "profiling", "tools", "compute", "traceview"
-page.metaDescription=Log method execution over time and inspect execution data, per-thread timelines, and call stacks to track down performance issues in your source code.
-page.image=tools/performance/thumbnails/tools_traceview.png
-page.article=true
-
-@jd:body
-
-<style>
- .no-bullet {
- list-style-type: none;
- }
- .padded {
- padding-left: 10px;
- }
-</style>
-
-<div id="tb" style="margin-left: 7px; margin-bottom: 5px;">
-
-<h2>In this document</h2>
-<ul>
- <li><a href="#WhatYouNeed">Prerequisites</a></li>
- <li><a href="#WorkingWithTraceview">Working with Traceview</a></li>
-</ul>
-
-<h2>You should also read</h2>
-<ul>
- <li><a href="{@docRoot}tools/performance/heap-viewer/index.html">
- Heap Viewer Walkthrough</a></li>
- <li><a href="{@docRoot}tools/performance/systrace/index.html">
- Systrace Walkthrough</a></li>
-</ul>
-
-</div>
-
- <p>This walkthrough shows the basic usage and workflow for the Traceview tool. Traceview logs
- method execution over time and shows execution data, per-thread timelines, and call stacks.</p>
-
- <p>What it's good for:</p>
-
- <ul>
- <li>Tracking down performance problems in your source code.</li>
- </ul>
-
- <h2 id="WhatYouNeed">Prerequisites</h2>
-
- <ul>
- <li>A mobile device with <a href=
- "http://developer.android.com/tools/device.html#developer-device-options">Developer Options</a>
- enabled.</li>
-
- <li>Application code. Use your own code, or the <a href=
- "https://github.com/udacity/Sunshine-Version-2">Sunshine</a> sample app from the <a href=
- "https://www.udacity.com/course/ud853">Android Fundamentals Udacity course</a>.</li>
- </ul>
-
-<h2 id="WorkingWithTraceview">Working with Traceview</h2>
-
-<ul class="no-bullet">
-<!-- this also hides bullet, by default outside box -->
- <li><div style="overflow:hidden">
- <ol class="padded">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image001.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 1. </strong>Steps for starting Android Device Monitor.
- </p>
- </div>
-
- <li>Connect your mobile device to your computer.</li>
-
- <li>Open your application in Android Studio, build the source, and run it on your device.</li>
-
- <li>Start the Android Device Monitor from Android Studio: <b>Tools -> Android -> Android
- Device</b> <b>Monitor</b>.
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="4">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image002.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 2. </strong>Steps for starting Traceview.
- </p>
- </div>
-
- <li>Make sure your device
- and the package for your application are showing in the <b>Devices</b> (DDMS mode) or
- <b>Windows</b> (Hierarchy Viewer mode) tab.
-
- <p>If necessary choose <b>Window > Reset
- Perspective</b> to get back to the default pane arrangement.</p></li>
-
- <li>Click the <b>DDMS</b> button, because Traceview is one of the DDMS tools.</li>
-
- <li>Select the app you want to profile.
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="7">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image004.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 3. </strong>Starting profiling.
- </p>
- </div>
-
- <li>Click the Start method profiling
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image003.png">
- button.
- </li>
-
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="8">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image005.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 4. </strong>Choosing profiling options.
- </p>
- </div>
-
- <li>In the <b>Profiling Options</b> popup:
-
- <ul>
- <li>Choose <b>Sample based profiling</b></li>
-
- <li>Keep the default sampling rate of 1000 microseconds.</li>
-
- <li>Click <b>OK</b>.</li>
- </ul>
- </li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="9">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image007.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 5. </strong>Stopping profiling.
- </p>
- </div>
-
-
- <li>Interact with your application. If you are aware of performance issues that
- your users experience, perform those actions.</li>
-
- <li>Click the Stop method profiling
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image006.png">
- button.</li>
-
- <li>Wait for the trace to load. This may take a few seconds if you recorded for a
- long time.</li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="12">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image008.png"
- alt=""
- width="440px" />
- <p class="img-caption">
- <strong>Figure 6. </strong>Traceview output panes.
- </p>
- </div>
-
- <li>Traceview has two panels: <b>Timeline</b> pane and <b>Profile</b> pane, which
- are described below.</li>
-
- <li>Use the <b>Find</b> box at the bottom to filter your profile results. For
- example, if you are interested in finding the running time for a function, you can
- search for it, and the tool will highlight it in the timeline.
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="14">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image009.png"
- alt=""
- width="400px" />
- <p class="img-caption">
- <strong>Figure 7. </strong>Annotated timeline panel.
- </p>
- </div>
-
- <li>The <b>Timeline</b> pane visualizes how your code executes over time.
-
- <ul>
- <li>Each row shows a thread.</li>
-
- <li>Each bar on the timeline is a method executing.</li>
-
- <li>Each color is for a different method; every time a method executes, you see
- a the same color bar.</li>
-
- <li>The width of its bar indicates how long the method takes to execute.</li>
- </ul>
- </li>
-
- <li>When you are zoomed out, a bar indicates when a method is executing.</li>
-
- </ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="16">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image010.png"
- alt=""
- width="300px" />
- <p class="img-caption">
- <strong>Figure 8. </strong>Segment for method on the timeline.
- </p>
- </div>
-
- <li>Zoom into the graph, and the bar for each method expands into a colored
- U-shape, where the left side of the U indicates the start, and the right side
- the end of the method's execution.</li>
-</ol>
-</div></li>
-
-<li><div style="overflow:hidden">
-<hr>
- <ol class="padded" start="17">
-
- <div class="figure" style="">
- <img src="{@docRoot}images/tools/performance/traceview/gettingstarted_image011.png"
- alt=""
- width="440px" />
- <p class="img-caption">
- <strong>Figure 9. </strong>Traceview Profiling pane with callstack.
- </p>
- </div>
-
- <li>The <b>Profiling</b> pane shows a list of methods.
-
- <ul>
- <li>Select a method to see who called it (Parent) and who it's
- calling (Children).</li>
-
- <li>The selected method is also highlighted in the <b>Timeline</b> pane.</li>
-
- <li>The columns show exclusive and inclusive CPU and real times, percentages,
- ratios, and how often a method was called.</li>
-
- <li>The <em>exclusive time</em> is the time spent just in the method itself, which can
- help you find issues within that specific method.</li>
-
- <li>The <em>inclusive time</em> is for the method and all methods it calls, which
- can help you find problems with your call tree.</li>
-
- <li>The <b>Calls+Rec</b> column shows how many times a method was called recursively,
- which can help you track down performance issues.</li>
- </ul>
- </li>
- </ol>
-</div></li>
-</ul>
+++ /dev/null
-page.title=Managing Projects Overview
-meta.tags="project, mipmap"
-page.tags="project", "mipmap"
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li><a href="#ProjectFiles">Android Project Files</a></li>
- <li><a href="#ApplicationModules">Android Application Modules</a></li>
- <ol>
- <li><a href="#mipmap">Managing Launcher Icons as mipmap Resources</a></li>
- </ol>
- <li><a href="#LibraryModules">Library Modules</a>
- <ol>
- <li><a href="#considerations">Development considerations</a></li>
- </ol>
- </li>
-
- <li><a href="#TestModules">Test Modules</a></li>
-
- <li><a href="#testing">Testing a Library Module</a></li>
- </ol>
- </div>
- </div>
-
- <p>An Android <em>project</em> contains everything that defines your Android app, from app
- source code to build configurations and test code. The SDK tools require that your projects
- follow a specific structure so it can compile and package your application correctly.
- If you're using Android Studio, it takes care of all this for you.</p>
-
- <p>A <em>module</em> is the first level of containment within a project that encapsulates
- specific types of source code files and resources. There are several types of modules
- with a project:</p>
-
- <dl>
-
- <dt><strong>Android Application Modules</strong></dt>
-
- <dd>An Android Application Module is the container for your application's source code, resource
- files, and application level settings, such as the module-level build file, resource files, and
- Android Manifest file. The application module contents are eventually
- built into the <code>.apk</code> file that gets installed on a device.</dd>
-
- <dt><strong>Test Modules</strong></dt>
-
- <dd>These modules contain code to test your application projects and are built into
- test applications that run on a device. By default, Android Studio creates the
- <em>androidTest</em> module for inserting JUnit tests. </dd>
-
- <dt><strong>Library Modules</strong></dt>
-
- <dd>These modules contain shareable Android source code and resources that you can reference
- in Android projects. This is useful when you have common code that you want to reuse.
- Library modules cannot be installed onto a device, however, they are
- pulled into the <code>.apk</code> file at build time.</dd>
-
-
- <dt><strong>App Engine Modules</strong></dt>
-
- <dd>Android Studio lets you easily add a cloud backend to your application. A backend allows you
- to implement functionality such as backing up user data to the cloud, serving content to client
- apps, real-time interactions, sending push notifications through Google Cloud Messaging for
- Android (GCM), and more. App Engine modules are App Engine java Servlet Module for backend
- development, App Engine java Endpoints Module to convert server-side Java code annotations into
- RESTful backend APIs, and App Engine Backend with Google Cloud Messaging to send push notifications
- from your server to your Android devices. </dd>
-
- </dl>
-
- <p>When you use the Android development tools to create a new project and the module, the essential files
- and folders will be created for you. There are only a handful of files and folders generated for you,
- and some of them depend on whether you use Android Studio or the {@code android} tool to
- generate your module. As your application grows in complexity, you might require new kinds of
- resources, directories, and files.</p>
-
-<p class="note"><strong>Note:</strong> Project folders and files apply across the entire Android
-project and override similar module file settings.</p>
-
-
-
-
- <h2 id="ProjectFiles">Android Project Files</h2>
-
- <p>Android Studio project files and settings provide project-wide settings that apply across all
- modules in the project. </p>
-
- <dl>
- <dt><code>.idea</code></dt>
-
- <dd>Directory for IntelliJ IDEA settings.</dd>
-
-
- <dt><code>app</code></dt>
-
- <dd>Application module directories and files. </dd>
-
-
- <dt><code>build</code></dt>
-
- <dd>This directory stores the build output for all project modules.</dd>
-
-
- <dt><code>gradle</code></dt>
-
- <dd>Contains the gradler-wrapper files. </dd>
-
-
- <dt><code>.gitignore</code></dt>
-
- <dd>Specifies the untracked files that Git should ignore.</dd>
-
-
- <dt><code>build.gradle</code></dt>
-
- <dd>Customizable properties for the build system. You can edit this file to specify the default
- build settings used by the application modules and also set the location of your keystore and key alias
- so that the build tools can sign your application when building in release mode. This file is
- integral to the project, so maintain it in a source revision control system. </dd>
-
- <dt><code>gradle.properties</code></dt>
-
- <dd>Project-wide Gradle settings.</dd>
-
-
- <dt><code>gradlew</code></dt>
-
- <dd>Gradle startup script for Unix.</dd>
-
-
- <dt><code>gradlew.bat</code></dt>
-
- <dd>Gradle startup script for Windows. </dd>
-
- <dt><code>local.properties</code></dt>
-
- <dd>Customizable computer-specific properties for the build system, such as the path to the SDK
- installation. Because the content of the file is specific to the local installation of the SDK,
- the <code>local.properties</code> should not be maintained in a source revision control system. </dd>
-
-
- <dt><code><project>.iml</code></dt>
-
- <dd>Module file created by the IntelliJ IDEA to store module information.</dd>
-
- <dt><code>settings.gradle</code></dt>
-
- <dd>Specifies the sub-projects to build.</dd>
-
- </dl>
-
-
- <h2 id="ApplicationModules">Android Application Modules</h2>
-
- <p>Android Application Modules are the modules that eventually get built into the <code>.apk</code>
- files based on your build settings. They contain things such as application source code and resource
- files. Most code and resource files are generated for you by default, while others should be created if
- required. The following directories and files comprise an Android application module:</p>
-
- <dl>
-
- <dt><code>build/</code></dt>
-
- <dd>Contains build folders for the specified build variants. Stored in the main application module.</dd>
-
-
- <dt><code>libs/</code></dt>
-
- <dd>Contains private libraries. Stored in the main application module.</dd>
-
-
-
-
- <dt><code>src/</code></dt>
-
- <dd>Contains your stub Activity file, which is stored at
- <code>src<em>/main/java/<namespace.appname>/<ActivityName></em>.java</code>. All
- other source code files (such as <code>.java</code> or <code>.aidl</code> files) go here as
- well.</dd>
-
- <dl>
- <dt><code>androidTest/</code></dt>
-
- <dd>Contains the instrumentation tests. For more information, see the
- <a href="{@docRoot}tools/testing/index.html">Android Test documentation</a>.</dd>
-
- <dt><code>main/java/com.<project>.<app></code></dt>
-
- <dd>Contains Java code source for the app activities.</dd>
-
- <dt><code>main/jni/</code></dt>
-
- <dd>Contains native code using the Java Native Interface (JNI). For more information, see the
- <a href="{@docRoot}tools/sdk/ndk/index.html">Android NDK documentation</a>.</dd>
-
- <dt><code>main/gen/</code></dt>
-
- <dd>Contains the Java files generated by Android Studio, such as your <code>R.java</code> file and
- interfaces created from AIDL files.</dd>
-
- <dt><code>main/assets/</code></dt>
-
- <dd>This is empty. You can use it to store raw asset files. Files that you save here are
- compiled into an <code>.apk</code> file as-is, and the original filename is preserved. You can
- navigate this directory in the same way as a typical file system using URIs and read files as a
- stream of bytes using the {@link android.content.res.AssetManager}. For example, this is a good
- location for textures and game data.</dd>
-
- <dt><code>main/res/</code></dt>
-
- <dd>Contains application resources, such as drawable files, layout files, and string values
- in the following directories. See
- <a href="{@docRoot}guide/topics/resources/index.html">Application Resources</a> for more
- information.
-
- <dl>
- <dt><code>anim/</code></dt>
-
- <dd>For XML files that are compiled into animation objects. See the <a href=
- "{@docRoot}guide/topics/resources/animation-resource.html">Animation</a> resource
- type.</dd>
-
- <dt><code>color/</code></dt>
-
- <dd>For XML files that describe colors. See the <a href=
- " {@docRoot}guide/topics/resources/color-list-resource.html">Color Values</a> resource
- type.</dd>
-
- <dt><code>drawable/</code></dt>
-
- <dd>For bitmap files (PNG, JPEG, or GIF), 9-Patch image files, and XML files that describe
- Drawable shapes or Drawable objects that contain multiple states (normal, pressed, or
- focused). See the <a href=
- "{@docRoot}guide/topics/resources/drawable-resource.html">Drawable</a> resource type.</dd>
-
-
- <dt><code>mipmap/</code></dt>
-
- <dd>For app launcher icons. The Android system retains the resources in this folder
- (and density-specific folders such as mipmap-xxxhdpi) regardless of the screen resolution
- of the device where your app is installed. This behavior allows launcher apps to pick
- the best resolution icon for your app to display on the home screen. For more information
- about using the <code>mipmap</code> folders, see
- <a href="#mipmap">Managing Launcher Icons as mipmap Resources</a>. </p>
-
-
- <dt><code>layout/</code></dt>
-
- <dd>XML files that are compiled into screen layouts (or part of a screen). See the <a href=
- "{@docRoot}guide/topics/resources/layout-resource.html">Layout</a> resource type.</dd>
-
- <dt><code>menu/</code></dt>
-
- <dd>For XML files that define application menus.
- See the <a href="{@docRoot}guide/topics/resources/menu-resource.html">Menus</a>
- resource type.</dd>
-
- <dt><code>raw/</code></dt>
-
- <dd>For arbitrary raw asset files. Saving asset files here is essentially the same as
- saving them in the <code>assets/</code> directory. The only difference is how you
- access them. These files
- are processed by aapt and must be referenced from the application using a resource
- identifier in the {@code R} class. For example, this is a good place for media, such as MP3
- or Ogg files.</dd>
-
- <dt><code>values/</code></dt>
-
- <dd>For XML files that define resources by XML element type. Unlike other resources in
- the <code>res/</code> directory, resources written to XML files in this folder are not
- referenced by the file name. Instead, the XML element type controls how the resources
- defined within the XML files are placed into the {@code R} class.</dd>
-
- <dt><code>xml/</code></dt>
-
- <dd>For miscellaneous XML files that configure application components. For example, an XML
- file that defines a {@link android.preference.PreferenceScreen}, {@link
- android.appwidget.AppWidgetProviderInfo}, or
- <a href="{@docRoot}reference/android/app/SearchManager.html#SearchabilityMetadata">
- Searchability Metadata</a>. See
- <a href="{@docRoot}guide/topics/resources/index.html">Application Resources</a>
- for more information about configuring these application components.</dd>
-
- </dl>
-
- <dt><code>AndroidManifest.xml</code></dt>
-
- <dd>The control file that describes the nature of the application and each of its components.
- For instance, it describes: certain qualities about the activities, services, intent receivers,
- and content providers; what permissions are requested; what external libraries are needed; what
- device features are required, what API Levels are supported or required; and others. See the
- <a href="{@docRoot}guide/topics/manifest/manifest-intro.html">AndroidManifest.xml</a>
- documentation for more information</dd>
-
- </dl>
-
- <dt><code>.gitignore/</code></dt>
-
- <dd>Specifies the untracked files ignored by git.</dd>
-
- <dt><code>app.iml/</code></dt>
-
- <dd>IntelliJ IDEA module</dd>
-
- <dt><code>build.gradle</code></dt>
-
- <dd>Customizable properties for the build system. You can edit this file to override default
- build settings used by the manifest file and also set the location of your keystore and key alias
- so that the build tools can sign your application when building in release mode. This file is
- integral to the project, so maintain it in a source revision control system. </dd>
-
- <dt><code>proguard-rules.pro</code></dt>
-
- <dd>ProGuard settings file. </dd>
-
-
- </dl>
-
-
-
-<h2 id="mipmap">Managing Launcher Icons as mipmap Resources</h2>
-
-<p>Different home screen launcher apps on different devices show app launcher icons at various
-resolutions. When app resource optimization techniques remove resources for unused
-screen densities, launcher icons can wind up looking fuzzy because the launcher app has to upscale
-a lower-resolution icon for display. To avoid these display issues, apps should use the
-<code>mipmap/</code> resource folders for launcher icons. The Android system
-preserves these resources regardless of density stripping, and ensures that launcher apps can
-pick icons with the best resolution for display. </p>
-
-<p>Make sure launcher apps show a high-resolution icon for your app by moving all densities of your
-launcher icons to density-specific <code>res/mipmap/</code> folders
-(for example <code>res/mipmap-mdpi/</code> and <code>res/mipmap-xxxhdpi/</code>). The
-<code>mipmap/</code> folders replace the <code>drawable/</code> folders for launcher icons. For
-xxhpdi launcher icons, be sure to add the higher resolution xxxhdpi versions of the
-icons to enhance the visual experience of the icons on higher resolution devices.</p>
-
-<p class="note"><strong>Note:</strong> Even if you build a single APK for all devices, it is still
-best practice to move your launcher icons to the <code>mipmap/</code> folders.</p>
-
-
-<h3>Manifest update</h3>
-
-<p>When you move your launcher icons to the <code>mipmap-[density]</code> folders, change the
-launcher icon references in the <code>AndroidManifest.xml</code> file so your manifest references
-the <code>mipmap/</code> location. This example changes the manifest file to reference the
-<code>ic_launcher</code> icon in the <code>mipmap/</code> folder. </p>
-
-<pre>
-...
-<application android:name="ApplicationTitle"
- android:label="@string/app_label"
- android:icon="@mipmap/ic_launcher" >
- ...
-</pre>
-
-
-
-
-
- <h2 id="LibraryModules">Library Module</h2>
-
- <div class="sidebox-wrapper">
- <div class="sidebox">
- <h2>Library module example code</h2>
-
- <p>The SDK includes an example application called <code>TicTacToeMain</code> that shows how a
- dependent application can use code and resources from an Android Library module. The TicTacToeMain
- application uses code and resources from an example library module called TicTacToeLib.</p>
-
- <p>To download the sample applications and run them as modules in
- your environment, use the <em>Android SDK Manager</em> to download the "Samples for
- SDK API 8" (or later) module into your SDK.</p>
-
- <p>For more information and to browse the code of the samples, see
- the <a href="{@docRoot}resources/samples/TicTacToeMain/index.html">TicTacToeMain
- application</a>.</p>
- </div>
- </div>
-
- <p>An Android <em>library module</em> is a development module that holds shared Android
- source code and resources. Other Android application modules can reference the library module
- and, at build time, include its compiled sources in their <code>.apk</code> files. Multiple
- application modules can reference the same library module and any single application module
- can reference multiple library modules.</p>
-
- <p class="note"><strong>Note:</strong> You need SDK Tools r14 or newer to use the new library
- module feature that generates each library module into its own JAR file.
- You can download the tools and platforms using the
- <em>Android SDK Manager</em>, as described in
- <a href="{@docRoot}tools/help/sdk-manager.html">SDK tools help</a>.</p>
-
- <p>If you have source code and resources that are common to multiple Android projects, you
- can move them to a library module so that it is easier to maintain across applications and
- versions. Here are some common scenarios in which you could make use of library modules:</p>
-
- <ul>
- <li>If you are developing multiple related applications that use some of the same components,
- you move the redundant components out of their respective application module and create a
- single, reusable set of the same components in a library module.</li>
-
- <li>If you are creating an application that exists in both free and paid versions. You move
- the part of the application that is common to both versions into a library module. The two
- dependent modules, with their different package names, will reference the library module
- and provide only the difference between the two application versions.</li>
- </ul>
-
- <p>Structurally, a library module is similar to a standard Android application module. For
- example, it includes a manifest file at the module root, as well as <code>src/</code>,
- <code>res/</code> and similar directories. The module can contain the same types of source
- code and resources as a standard Android module, stored in the same way. For example, source
- code in the library module can access its own resources through its <code>R</code> class.</p>
-
- <p>However, a library module differs from a standard Android application module in that you
- cannot compile it directly to its own <code>.apk</code> and run it on an Android device.
- Similarly, you cannot export the library module to a self-contained JAR file, as you would do
- for a true library. Instead, you must compile the library indirectly, by referencing the
- library in the dependent application and building that application.</p>
-
- <p>When you build an application that depends on a library module, the SDK tools compile the
- library into a temporary JAR file and use it in the main module, then uses the
- result to generate the <code>.apk</code>. In cases where a resource ID is defined in both the
- application and the library, the tools ensure that the resource declared in the application gets
- priority and that the resource in the library module is not compiled into the application
- <code>.apk</code>. This gives your application the flexibility to either use or redefine any
- resource behaviors or values that are defined in any library.</p>
-
- <p>To organize your code further, your application can add references to multiple library
- modules, then specify the relative priority of the resources in each library. This lets you
- build up the resources actually used in your application in a cumulative manner. When two
- libraries referenced from an application define the same resource ID, the tools select the
- resource from the library with higher priority and discard the other.</p>
-
- <p>Once you have added references to library modules to your Android application module,
- you can set their relative priority. At build time, the
- libraries are merged with the application one at a time, starting from the lowest priority to
- the highest.</p>
-
- <p>Library modules can reference other library modules and can import an external library
- (JAR) in the normal way.</p>
-
- <h3 id="considerations">Development considerations</h3>
-
- <p>As you develop your library modules and dependent applications, keep the points listed below
- in mind:</p>
-
- <ul>
- <li><p><strong>Resource conflicts</strong></p>
- <p>Since the tools merge the resources of a library module with those of a dependent application
- module, a given resource ID might be defined in both modules. In this case, the tools select
- the resource from the application, or the library with highest priority, and discard the other
- resource. As you develop your applications, be aware that common resource IDs are likely to be
- defined in more than one project and will be merged, with the resource from the application or
- highest-priority library taking precedence.</p>
- </li>
-
- <li><p><strong>Use prefixes to avoid resource conflicts</strong></p>
-
- <p>To avoid resource conflicts for common resource IDs, consider using a prefix or other
- consistent naming scheme that is unique to the module (or is unique across all project modules).</p></li>
-
- <li><p><strong>You cannot export a library module to a JAR file</strong></p>
-
- <p>A library cannot be distributed as a binary file (such as a JAR file). This will be added in a
- future version of the SDK Tools.</p></li>
-
- <li><p><strong>A library module can include a JAR library</strong></p>
-
- <p>You can develop a library module that itself includes a JAR library; however you need to
- manually edit the dependent application modules's build path and add a path to the JAR file.</p></li>
-
- <li><p><strong>A library module can depend on an external JAR library</strong></p>
-
- <p>You can develop a library module that depends on an external library (for example, the Maps
- external library). In this case, the dependent application must build against a target that
- includes the external library (for example, the Google APIs Add-On). Note also that both the
- library module and the dependent application must declare the external library in their manifest
- files, in a <a href=
- "{@docRoot}guide/topics/manifest/uses-library-element.html"><code><uses-library></code></a>
- element.</p></li>
-
- <li> <p><strong>Library modules cannot include raw assets</strong></p>
-
- <p>The tools do not support the use of raw asset files (saved in the <code>assets/</code> directory)
- in a library module. Any asset resources
- used by an application must be stored in the <code>assets/</code> directory of the application
- module itself. However, resource files saved in the <code>res/</code> directory are supported.</p></li>
-
- <li><p><strong>Platform version must be lower than or equal to the Android module</strong></p>
-
- <p>A library is compiled as part of the dependent application module, so the API used in the
- library module must be compatible with the version of the Android library used to compile the
- application module. In general, the library module should use an <a href=
- "{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API level</a> that is the same as — or lower
- than — that used by the application. If the library module uses an API level that is
- higher than that of the application, the application module will not compile. It is
- perfectly acceptable to have a library that uses the Android 1.5 API (API level 3) and that is
- used in an Android 1.6 (API level 4) or Android 2.1 (API level 7) module, for instance.</p></li>
-
- <li> <p><strong>No restriction on library module names</strong></p>
-
- <p>There is no requirement for the package name of a library to be the same as that of
- applications that use it.</p></li>
-
- <li><p><strong>Each library module creates its own R class </strong></p>
-
- <p>When you build the dependent application modules, library modules are compiled and
- merged with the application module. Each library has its own <code>R</code> class, named according
- to the library's package name. The <code>R</code> class generated from main
- module and the library module is created in all the packages that are needed including the main
- module's package and the libraries' packages.</p></li>
-
- <li><p><strong>Library module storage location</strong></p>
-
- <p>There are no specific requirements on where you should store a library module, relative to a
- dependent application module, as long as the application module can reference the library
- module by a relative link. What is important is that the main
- module can reference the library module through a relative link.</p></li>
- </ul>
-
- <h2 id="TestProjects">Test Projects</h2>
-
- <p>Test projects contain Android applications that you write using the
- <a href="{@docRoot}tools/testing/index.html">Testing and
- Instrumentation framework</a>. The framework is an extension of the JUnit test framework and adds
- access to Android system objects. </p>
-
- <p>The test projects are now automatically part of the app source folder. When a new application
- module is created, Android Studio creates the <code>src/androidTest</code> source set. This
- source set contains tests for the default configuration and is combined with the <em>debug</em>
- build type to generate a test application. </p>
-
- <img src="{@docRoot}images/tools/studio-androidtest-folder.png">
- <p class="img-caption"><strong>Figure 1.</strong> androidTest Folder.</p>
-
- <p class="note"><strong>Note:</strong> The <code>src/androidTest</code> source set may not be
- created for every type of available module template. If this source set is not created, you
- can just create it for that module.</p>
-
- <p>For each product flavor, create a test folder specific to that product flavor. </p>
-
- <dl>
- <dt><code>src/main/</code></dt>
- <dd><code>src/androidTest/</code></dt>
-
- <dt><code>src/productFlavor1/</code></dt>
- <dd><code>src/testproductFlavor1/</code></dd>
-
- <dt><code>src/productFlavor2/</code></dt>
- <dd><code>src/testproductFlavor2/</code></dd>
-
- </dl>
-
- <p>The test manifests are always generated so a manifest in a test source set is optional.</p>
-
- <p>The test applications run against the <em>debug</em> build type. This can be configured
- using the <code>testBuildType</code> property in the build file.</p>
-
-
- <p>For more information, see the
- <a href="{@docRoot}tools/testing/index.html">Testing</a> section.</p>
-
-
- <h2 id="testing">Testing a Library Module</h2>
-
- <p>There are two recommended ways of setting up testing on code and resources in a library
- module:</p>
-
- <ul>
- <li>You can set up a <a href="{@docRoot}tools/testing/testing_otheride.html">test
- module</a> that instruments an application module that depends on the library module. You
- can then add tests to the module for library-specific features.</li>
-
- <li>You can set up a standard application module that depends on the library and put
- the instrumentation in that module. This lets you create a self-contained module that
- contains both the tests/instrumentations and the code to test.</li>
- </ul>
+++ /dev/null
-page.title=Managing Projects from the Command Line
-parent.title=Managing Projects
-parent.link=index.html
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li><a href="#CreatingAProject">Creating an Android Project</a></li>
- <li><a href="#UpdatingAProject">Updating a Project</a></li>
- <li><a href="#SettingUpLibraryProject">Setting up a Library Project</a>
- <ol>
- <li><a href="#CreatingManifestFile">Creating the manifest file</a></li>
- <li><a href="#UpdatingLibraryProject">Updating a library project</a></li>
- </ol>
- </li>
- <li><a href="#ReferencingLibraryProject">Referencing a Library Project</a>
- <ol>
- <li><a href="#DeclaringLibrary">Declaring library components in the manifest
-file</a></li>
- <li><a href="#depAppBuild">Building a dependent application</a></li>
- </ol>
- </li>
- </ol>
-
- <h2>See also</h2>
-
- <ol>
- <li><a href=
- "{@docRoot}tools/testing/testing_otheride.html#CreateTestProjectCommand">Testing
- from Other IDEs</a></li>
- </ol>
- </div>
- </div>
-
- <p>The <code>android</code> tool provides you with commands to create all three types of
- projects. An Android project contains all of the files and resources that are needed to build a
- project into an .apk file for installation.
-
- <ul>
- <li>An Android project contains all of the files and resources that are needed to build a project into
- an .apk file for installation. You need to create an Android project for any application that you
- want to eventually install on a device.</li>
-
- <li>You can also designate an Android project as a library project, which allows it to be shared
- with other projects that depend on it. Once an Android project is designated as a library
- project, it cannot be installed onto a device.</li>
-
- <li>Test projects extend JUnit test functionality to include Android specific functionality. For
- more information on creating a test project, see <a href=
- "{@docRoot}tools/testing/testing_otheride.html">Testing from other IDEs</a>.</li>
- </ul>
-
-
- <h2 id="CreatingAProject">Creating an Android Project</h2>
-
- <p>To create an Android project, you must use the <code>android</code> tool. When you create a
- new project with <code>android</code>, it will generate a project directory with some default
- application files, stub files, configuration files and a build file.</p>
-
- <p>To create a new Android project, open a command-line, navigate to the <code>tools/</code>
- directory of your SDK and run:</p>
- <pre>
-android create project \
---target <target_ID> \
---name <your_project_name> \
---path path/to/your/project \
---activity <your_activity_name> \
---package <your_package_namespace>
-</pre>
-
- <ul>
- <li><code>target</code> is the "build target" for your application. It corresponds to an
- Android platform library (including any add-ons, such as Google APIs) that you would like to
- build your project against. To see a list of available targets and their corresponding IDs,
- execute: <code>android list targets</code>.</li>
-
- <li><code>name</code> is the name for your project. This is optional. If provided, this name
- will be used for your .apk filename when you build your application.</li>
-
- <li><code>path</code> is the location of your project directory. If the directory does not
- exist, it will be created for you.</li>
-
- <li><code>activity</code> is the name for your default {@link android.app.Activity} class. This
- class file will be created for you inside
- <code><em><path_to_your_project></em>/src/<em><your_package_namespace_path></em>/</code>
- . This will also be used for your .apk filename unless you provide a <code>name</code>.</li>
-
- <li><code>package</code> is the package namespace for your project, following the same rules as
- for packages in the Java programming language.</li>
- </ul>
-
- <p>Here's an example:</p>
- <pre>
-android create project \
---target 1 \
---name MyAndroidApp \
---path ./MyAndroidAppProject \
---activity MyAndroidAppActivity \
---package com.example.myandroid
-</pre>
-
- <p>Once you've created your project, you're ready to begin development. You can move your project
- folder wherever you want for development, but keep in mind that you must use the <a href=
- "{@docRoot}tools/help/adb.html">Android Debug Bridge</a> (adb) — located in the
- SDK <code>platform-tools/</code> directory — to send your application to the emulator (discussed
- later). So you need access between your project solution and the <code>platform-tools/</code> folder.</p>
-
- <p class="note"><strong>Tip:</strong> Add the <code>platform-tools/</code> as well as the <code>tools/</code> directory
- to your <code>PATH</code> environment variable.</p>
-
- <p class="caution"><strong>Caution:</strong> You should refrain from moving the location of the
- SDK directory, because this will break the SDK location property located in <code>local.properties</code>.
- If you need to update the SDK location, use the <code>android update project</code> command.
- See <a href="#UpdatingAProject">Updating a Project</a> for more information.</p>
-
- <h2 id="UpdatingAProject">Updating a Project</h2>
-
- <p>If you're up grading a project from an older version of the Android SDK or want to create a new
- project from existing code, use the <code>android update project</code> command to update the
- project to the new development environment. You can also use this command to revise the build
- target of an existing project (with the <code>--target</code> option) and the project name (with
- the <code>--name</code> option). The <code>android</code> tool will generate any files and
- folders (listed in the previous section) that are either missing or need to be updated, as needed
- for the Android project.</p>
-
- <p>To update an existing Android project, open a command-line and navigate to the
- <code>tools/</code> directory of your SDK. Now run:</p>
- <pre>
-android update project --name <project_name> --target <target_ID>
---path <path_to_your_project>
-</pre>
-
- <ul>
- <li><code>target</code> is the "build target" for your application. It corresponds to an
- Android platform library (including any add-ons, such as Google APIs) that you would like to
- build your project against. To see a list of available targets and their corresponding IDs,
- execute: <code>android list targets</code>.</li>
-
- <li><code>path</code> is the location of your project directory.</li>
-
- <li><code>name</code> is the name for the project. This is optional—if you're not
- changing the project name, you don't need this.</li>
- </ul>
-
- <p>Here's an example:</p>
- <pre>
-android update project --name MyApp --target 2 --path ./MyAppProject
-</pre>
-
- <h2 id="SettingUpLibraryProject">Setting up a Library Project</h2>
-
- <p>A library project is a standard Android project, so you can create a new one in the same way
- as you would a new application project. Specifically, you can use the <code>android</code> tool
- to generate a new library project with all of the necessary files and folders.</p>
-
- <p>To create a new library project, navigate to the <code><sdk>/tools/</code> directory and
- use this command:</p>
- <pre class="no-pretty-print">
-android create lib-project --name <your_project_name> \
---target <target_ID> \
---path path/to/your/project \
---package <your_library_package_namespace>
-</pre>
-
- <p>The <code>create lib-project</code> command creates a standard project structure that includes
- preset property that indicates to the build system that the project is a library. It does this by
- adding this line to the project's <code>project.properties</code> file:</p>
- <pre class="no-pretty-print">
-android.library=true
-</pre>
-
- <p>Once the command completes, the library project is created and you can begin moving source
- code and resources into it, as described in the sections below.</p>
-
- <p>If you want to convert an existing application project to a library project, so that other
- applications can use it, you can do so by adding a the <code>android.library=true</code> property
- to the application's <code>project.properties</code> file.</p>
-
- <h3 id="CreatingManifestFile">Creating the manifest file</h3>
-
- <p>A library project's manifest file must declare all of the shared components that it includes,
- just as would a standard Android application. For more information, see the documentation for
- <a href="{@docRoot}guide/topics/manifest/manifest-intro.html">AndroidManifest.xml</a>.</p>
-
- <p>For example, the <a href=
- "{@docRoot}resources/samples/TicTacToeLib/AndroidManifest.html">TicTacToeLib</a> example library
- project declares the Activity <code>GameActivity</code>:</p>
- <pre>
-<manifest>
- ...
- <application>
- ...
- <activity android:name="GameActivity" />
- ...
- </application>
-</manifest>
-</pre>
-
- <h3 id="UpdatingLibraryProject">Updating a library project</h3>
-
- <p>If you want to update the build properties (build target, location) of the library project,
- use this command:</p>
- <pre>
-android update lib-project \
---target <em><target_ID></em> \
---path <em>path/to/your/project</em>
-</pre>
-
- <h2 id="ReferencingLibraryProject">Referencing a Library Project</h2>
-
- <p>If you are developing an application and want to include the shared code or resources from a
- library project, you can do so easily by adding a reference to the library project in the
- application project's build properties.</p>
-
- <p>To add a reference to a library project, navigate to the <code><sdk>/tools/</code>
- directory and use this command:</p>
- <pre>
-android update project \
---target <em><target_ID></em> \
---path <em>path/to/your/project</em>
---library <em>path/to/library_projectA</em>
-</pre>
-
- <p>This command updates the application project's build properties to include a reference to the
- library project. Specifically, it adds an <code>android.library.reference.<em>n</em></code>
- property to the project's <code>project.properties</code> file. For example:</p>
- <pre class="no-pretty-print">
-android.library.reference.1=path/to/library_projectA
-</pre>
-
- <p>If you are adding references to multiple libraries, note that you can set their relative
- priority (and merge order) by manually editing the <code>project.properties</code> file and
- adjusting the each reference's <code>.<em>n</em></code> index as appropriate. For example, assume
- these references:</p>
- <pre class="no-pretty-print">
-android.library.reference.1=path/to/library_projectA
-android.library.reference.2=path/to/library_projectB
-android.library.reference.3=path/to/library_projectC
-</pre>
-
- <p>You can reorder the references to give highest priority to <code>library_projectC</code> in
- this way:</p>
- <pre class="no-pretty-print">
-android.library.reference.2=path/to/library_projectA
-android.library.reference.3=path/to/library_projectB
-android.library.reference.1=path/to/library_projectC
-</pre>
-
- <p>Note that the <code>.<em>n</em></code> index in the references must begin at "1" and increase
- uniformly without "holes". References appearing in the index after a hole are ignored.</p>
-
- <p>At build time, the libraries are merged with the application one at a time, starting from the
- lowest priority to the highest. Note that a library cannot itself reference another library and
- that, at build time, libraries are not merged with each other before being merged with the
- application.</p>
-
- <h3 id="DeclaringLibrary">Declaring library components in the manifest file</h3>
-
- <p>In the manifest file of the application project, you must add declarations of all components
- that the application will use that are imported from a library project. For example, you must
- declare any <code><activity></code>, <code><service></code>,
- <code><receiver></code>, <code><provider></code>, and so on, as well as
- <code><permission></code>, <code><uses-library></code>, and similar elements.</p>
-
- <p>Declarations should reference the library components by their fully-qualified package names,
- where appropriate.</p>
-
- <p>For example, the <a href=
- "{@docRoot}resources/samples/TicTacToeMain/AndroidManifest.html">TicTacToeMain</a> example
- application declares the library Activity <code>GameActivity</code> like this:</p>
- <pre>
-<manifest>
- ...
- <application>
- ...
- <activity android:name="com.example.android.tictactoe.library.GameActivity" />
- ...
- </application>
-</manifest>
-</pre>
-
- <p>For more information about the manifest file, see the documentation for
- <a href="{@docRoot}guide/topics/manifest/manifest-intro.html">AndroidManifest.xml</a>.</p>
-
- <h3 id="depAppBuild">Building a dependent application</h3>
-
- <p>To build an application project that depends on one or more library projects, you can use the
- standard Gradle build commands and compile modes, as described in <a href=
- "{@docRoot}tools/building/index.html">Building and Running</a>. The tools
-compile and merge all libraries referenced by the application as part of
- compiling the dependent application project. No additional commands or steps are necessary.</p>
-
+++ /dev/null
-page.title=Using Code Templates
-page.image=images/cards/card-using-code-templates_16x9_2x.png
-page.metaDescription=Quickly create Android app projects with various UI or functional components.
-page.tags=studio,templates,firstapp
-@jd:body
-
- <div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
-
- <ol>
- <li><a href="#app-templates">Application Templates</a>
- <ol>
- <li><a href="#blank-activity">BlankActivity Template</a></li>
- <li><a href="#full-screen-activity">Full Screen Activity Template</a></li>
- <li><a href="#master-detail-activity">Master Detail Flow Template</a></li>
- </ol>
- </li>
-
- <li><a href="#activity-templates">Activity Templates</a>
- <ol>
- <li><a href="#login-activity">Login Activity Template</a></li>
- <li><a href="#settings-activity">Settings Activity Template</a></li>
- </ol>
- </li>
- <li><a href="#object-templates">Other Templates</a></li>
- </ol>
-
- </div>
- </div>
-
-<p>The SDK tools provide templates for quickly creating Android application projects with the basic
- structure or for adding components to your existing application modules. The code templates
- provided by the Android SDK follow the Android design and development guidelines to get you on the
- right track to creating a beautiful, functional application.</p>
-
-<p>There are several types of Android code templates, which can create anything from an entire
- application down to specific application components. The main categories of code templates are as
- follows:</p>
-
-<ul>
- <li><a href="#app-templates">Application Templates</a></li>
- <li><a href="#activity-templates">Activity Templates</a></li>
- <li><a href="#object-templates">Other Templates</a></li>
-</ul>
-
-<p>
- The templates use <a href=
- "{@docRoot}tools/support-library/features.html">support library</a> objects
- if such objects are available. The support library objects make new features
- available on the widest range of platforms. For example, since the templates
- use the <a href=
- "{@docRoot}tools/support-library/features.html#v7-appcompat">appcompat
- library</a>, apps based on the templates use <a href=
- "{@docRoot}design/material/index.html">material design</a> user interface
- principles even if they are running on older Android devices that do not
- directly support material design.
-</p>
-
-<h2 id="app-templates">Application Templates</h2>
-
-<p>Application templates create basic Android application modules that you can immediately run and test
- on your Android device. These templates are available when you create a new Android module,
- though you can also use these templates to <a href="#activity-templates">add new activities</a>
- to an existing module.</p>
-
-<p>To use Android application templates:</p>
-
-<ol>
- <li>In Android Studio, select <strong>File > New > Module</strong>.</li>
- <li>Enter the settings for your application, including <strong>Application Name</strong>,
- <strong>Company Domain</strong>, <strong>Package name</strong>, and <strong>minimum SDK</strong>,
- then click <strong>Next</strong>.</li>
- <li>Select an application template to use, then click <strong>Next</strong>. For example,
- <ul>
- <li><a href="#blank-activity">BlankActivity</a></li>
- <li><a href="#full-screen-activity">FullScreenActivity</a></li>
- <li><a href="#master-detail-activity">MasterDetailFlow</a></li>
-
- </ul>
- </li>
- <li>Enter the settings for your activity, including <strong>Activity Name</strong>,
- <strong>layout Name</strong>, <strong>Title</strong>, and <strong>Menu Resource Name</strong>,
- then click <strong>Finish</strong>.</li>
-</ol>
-
-<p class="note">
- <strong>Note:</strong> The other activity template options also create applications, however these
- applications require further modification before they can be launched on an Android device.
-</p>
-
-
-<h3 id="blank-activity">Blank Activity Template</h3>
-
-<table>
- <tr>
- <th width="206px">Example</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/ba-no-navigation.png" alt="" />
- </td>
-
- <td><p>The <strong>BlankActivity</strong> template with the <strong>Navigation Type:
- None</strong> option creates a simple application that follows the
- <a href="{@docRoot}design/index.html">Android Design</a> guidelines. Use this template to
- create a basic, minimal app as a starting point for your project.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>{@link android.app.ActionBar}</li>
- <li>Action overflow</li>
- <li>Basic layout</li>
- </ul>
- </td>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/ba-tabs.png" alt="" />
- </td>
-
- <td><p>The <strong>BlankActivity</strong> template with the <strong>Navigation Type:
- Tabs</strong> or <strong>Tabs + Swipe</strong> option creates an application with
- three sections based on the {@link android.app.Fragment} class and a tabbed user
- interface.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>{@link android.app.ActionBar} for tab controls</li>
- <li>{@link android.app.Fragment} objects for section content</li>
- <li>Optional swipe gesture support based on the
- <a href="{@docRoot}design/patterns/swipe-views.html">swipe view</a> design pattern,
- which extends {@link android.support.v4.app.FragmentPagerAdapter} to manage section
- fragments</li>
- </ul>
- </td>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/ba-title-strip.png" alt="" />
- </td>
-
- <td><p>The <strong>BlankActivity</strong> template with the <strong>Navigation Type:
- Swipe Views + Title Strip</strong> option creates an application with three
- {@link android.app.Fragment} sections, a compact title strip header (known as
- <a href="{@docRoot}design/building-blocks/tabs.html#scrollable">Scrollable Tabs</a> in the
- <a href="{@docRoot}design/index.html">Android Design</a> guide) and swipe navigation between
- the sections, based on the <a href="{@docRoot}design/patterns/swipe-views.html">swipe
- view</a> design pattern.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>{@link android.support.v4.view.PagerTitleStrip} for section titles</li>
- <li>{@link android.app.Fragment} objects for section content</li>
- <li>{@link android.support.v4.app.FragmentPagerAdapter} to manage section fragments</li>
- </ul>
- </td>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/ba-dropdown.png" alt="" />
- </td>
-
- <td><p>The <strong>BlankActivity</strong> template with the <strong>Navigation Type:
- Dropdown</strong> option creates an application that extends
- {@link android.support.v4.app.FragmentActivity}, containing three
- {@link android.app.Fragment} sections, with an {@link android.app.ActionBar} using list mode
- navigation.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>{@link android.app.ActionBar} for list mode navigation</li>
- <li>{@link android.app.Fragment} objects for section content</li>
- </ul>
- </td>
- </tr>
-</table>
-
-
-<h3 id="full-screen-activity">Full Screen Activity Template</h3>
-
-<table>
- <tr>
- <th width="240px">Example</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/full-screen-activity.png" alt="" />
- </td>
-
- <td><p>This template provides an implementation of an activity which alternates between a
- primary, full screen view and a view with standard user interface controls, including the
- notification bar and application title bar. The full screen view is the default and a user
- can activate the standard view by touching the device screen.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>{@code SystemUiHider} implementation that manages hiding of the system user interface
- using a version-compatible approach</li>
- <li>Basic layout</li>
- </ul>
- </td>
- </tr>
-</table>
-
-
-<h3 id="master-detail-activity">Master Detail Flow Template</h3>
-
-<table>
- <tr>
- <th width="350px">Example</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/master-detail-flow.png" alt=""/>
- </td>
-
- <td><p>This template creates an adaptive layout for a set of items and associated details. On a
- tablet device, the item list and item details are displayed on the same screen. On a smaller
- device, the list and details are displayed on separate screens.</p>
-
- <p class="note">
- <strong>Note:</strong> This template follows the recommendations of the
- <a href="{@docRoot}training/multiscreen/index.html">Designing for Multiple Screens</a>
- Android training.
- </p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>Adaptive layout using
- <a href="{@docRoot}guide/topics/resources/providing-resources.html#AlternativeResources"
- >alternative resource</a> XML files</li>
- <li>{@link android.support.v4.app.FragmentActivity}, {@link android.app.Fragment} and
- {@link android.support.v4.app.ListFragment} implementations</li>
- </ul></td>
- </tr>
-</table>
-
-
-<h2 id="activity-templates">Activity Templates</h2>
-
-<p>Android activity templates provide options to add new activities to your existing
- application.</p>
-
-<p>To use Android activity templates:</p>
-
-<ol>
- <li>Right click the project folder of the Android application where you want to add an
- activity.</li>
- <li>Select <strong>New > Other...</strong></li>
- <li>Select <strong>Android > Android Activity</strong>, then click <strong>Next</strong>.</li>
- <li>Select an activity template, then follow the instructions to add it to your existing
- application.
- <ul>
- <li><a href="#login-activity">LoginActivity</a></li>
- <li><a href="#settings-activity">SettingsActivity</a></li>
- <li><a href="#blank-activity">BlankActivity</a></li>
- <li><a href="#full-screen-activity">FullScreenActivity</a></li>
- <li><a href="#master-detail-activity">MasterDetailFlow</a></li>
- </ul>
- </li>
-</ol>
-
-<p>These templates create the same type of activity as they do when used as an application template,
-however the following templates create activities which are specifically intended to be used as part
-of an existing application.</p>
-
-
-<h3 id="login-activity">Login Activity Template</h3>
-
-<table>
- <tr>
- <th width="206px">Example</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/login-activity.png" alt="" />
- </td>
-
- <td><p>This activity template provides input fields and a sample implementation of
- an {@link android.os.AsyncTask} that asks users to login or register with their credentials.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>Recommended user interface for requesting login information</li>
- <li>{@link android.os.AsyncTask} implementation for handing network operations separately
- from the main user interface thread</li>
- <li>Progress indicator during network operations</li>
- </ul>
- </td>
- </tr>
-</table>
-
-
-<h3 id="settings-activity">Settings Activity Template</h3>
-
-<table>
- <tr>
- <th width="206px">Example</th>
-
- <th>Description</th>
- </tr>
-
- <tr>
- <td><img src="{@docRoot}images/code_templates/settings-activity.png" alt="" />
- </td>
-
- <td><p>This template extends the {@link android.preference.PreferenceActivity} class and uses an
- XML file to create preference settings. This template also demonstrates how to implement
- several data types for settings.</p>
-
- <p>This template includes:</p>
-
- <ul>
- <li>Activity extending {@link android.preference.PreferenceActivity}</li>
- <li>Preference values defined using XML files added to the {@code res/xml/} directory of
- your project.</li>
- </ul>
- </td>
- </tr>
-</table>
-
-
-<h2 id="object-templates">Other Templates</h2>
-
-<p>Android object templates provide options to add new components to your existing application,
-including the previously mentioned activities as well as the following additional items:</p>
-
-<p>To use Android object templates:</p>
-
-<ol>
- <li>Right-click the module folder of the Android application where you want to add a code
- component.</li>
- <li>Select <strong>New</strong></li>
- <li>Select the object type and template, then follow the instructions to add it to your existing
- application.
- <ul>
- <li>AIDL</li>
- <li>Activity</li>
- <li>Folder</li>
- <li>Fragment</li>
- <li>Google</li>
- <li>Other</li>
- <li>Service</li>
- <li>UI Component</li>
- <li>Wear</li>
- <li>Widget</li>
- <li>XML</li>
- </ul>
- </li>
-</ol>
+++ /dev/null
-page.title=Signing Your Applications
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
-<h2>In this document</h2>
-
-<ol>
-<li><a href="#overview">Signing Overview</a>
- <ol>
- <li><a href="#debug-mode">Signing in Debug Mode</a></li>
- <li><a href="#release-mode">Signing in Release Mode</a></li>
- <li><a href="#wear-apps">Signing Android Wear Apps</a></li>
- </ol>
-</li>
-<li><a href="#studio">Signing Your App in Android Studio</a>
- <ol>
- <li><a href="#sign-auto">Automatically Signing Your App</a></li>
- </ol>
-</li>
-<li><a href="#studio">Signing Your App with Android Studio</a></li>
-<li><a href="#considerations">Signing Considerations</a></li>
-<li><a href="#secure-key">Securing Your Private Key</a></li>
-<li><a href="#expdebug">Expiry of the Debug Certificate</a></li>
-<li><a href="#signing-manually">Signing Your App Manually</a></li>
-</ol>
-
-<h2>See also</h2>
-
-<ol>
-<li><a href="{@docRoot}tools/publishing/versioning.html">Versioning Your Applications</a></li>
-<li><a href="{@docRoot}tools/publishing/preparing.html">Preparing to Publish</a></li>
-</ol>
-
-</div>
-</div>
-
-
-<p>Android requires that all apps be digitally signed with a certificate before they can be
-installed. Android uses this certificate to identify the author of an app, and the certificate
-does not need to be signed by a certificate authority. Android apps often use self-signed
-certificates. The app developer holds the certificate's private key.</p>
-
-
-<h2 id="overview">Signing Overview</h2>
-
-<p>You can sign an app in debug or release mode. You sign your app in debug mode during development
-and in release mode when you are ready to distribute your app. The Android SDK generates a
-certificate to sign apps in debug mode. To sign apps in release mode, you need to generate
-your own certificate.</p>
-
-<h3 id="debug-mode">Signing in Debug Mode</h3>
-
-<p>In debug mode, you sign your app with a debug certificate generated by the Android SDK tools.
-This certificate has a private key with a known password, so you can run and debug your app
-without typing the password every time you make a change to your project.</p>
-
-<p>Android Studio signs your app in debug mode automatically when
-you run or debug your project from the IDE.</p>
-
-<p>You can run and debug an app signed in debug mode on the emulator and on devices connected
-to your development machine through USB, but you cannot distribute an app signed in debug
-mode.</p>
-
-<p>By default, the <em>debug</em> configuration uses a debug keystore, with a known
-password and a default key with a known password.
-The debug keystore is located in <code>$HOME/.android/debug.keystore</code>, and
-is created if not present.
-The debug build type is set to use this debug <code>SigningConfig</code> automatically.</p>
-
-<p>For more information about how to build and run apps in debug mode, see
-<a href="{@docRoot}tools/building/index.html">Building and Running</a>.</p>
-
-<h3 id="release-mode">Signing in Release Mode</h3>
-
-<p>In release mode, you sign your app with your own certificate:</p>
-
-<ol>
-<li><em>Create a keystore.</em> A <strong>keystore</strong> is a binary file that contains a
-set of private keys. You must keep your keystore in a safe and secure place.</li>
-<li><em>Create a private key.</em> A <strong>private key</strong> represents the entity to
-be identified with the app, such as a person or a company.</li>
-<li><p>Add the signing configuration to the build file for the <code>app</code> module:</p>
-
-<pre>
-...
-android {
- ...
- defaultConfig { ... }
- signingConfigs {
- release {
- storeFile file("myreleasekey.keystore")
- storePassword "password"
- keyAlias "MyReleaseKey"
- keyPassword "password"
- }
- }
- buildTypes {
- release {
- ...
- signingConfig signingConfigs.release
- }
- }
-}
-...
-</pre>
- </li>
-<li>Invoke the <code>assembleRelease</code> build task from Android Studio.</li>
-</ol>
-
-<p>The package in <code>app/build/apk/app-release.apk</code> is now signed with your release
-key.</p>
-
-<p class="note"><strong>Note:</strong> Including the passwords for your release key and keystore
-inside the build file is not a good security practice. Alternatively, you can configure the build
-file to obtain these passwords from environment variables or have the build process prompt you
-for these passwords.</p>
-
-<p>To obtain these passwords from environment variables:</p>
-
-<pre>
-storePassword System.getenv("KSTOREPWD")
-keyPassword System.getenv("KEYPWD")
-</pre>
-
-<p>To have the build process prompt you for these passwords if you are invoking the build from
-the command line:</p>
-
-<pre>
-storePassword System.console().readLine("\nKeystore password: ")
-keyPassword System.console().readLine("\nKey password: ")
-</pre>
-
-
-<p>After you complete this process, you can distribute your app and publish it on Google Play.</p>
-
-<p class="warning"><strong>Warning:</strong> Keep your keystore and private key in a safe and
-secure place, and ensure that you have secure backups of them. If you publish an app to Google
-Play and then lose the key with which you signed your app, you will not be able to publish
-any updates to your app, since you must always sign all versions of your app with the same
-key.</p>
-
-<p>The rest of this document provides detailed instructions about how to generate a private
-key and sign your apps in release mode with Android Studio.</p>
-
-<h3 id="wear-apps">Signing Android Wear Apps</h3>
-
-<p>When publishing Android Wear apps, you package the wearable app inside of a handheld app,
-because users cannot browse and install apps directly on the wearable. Both apps must be signed.
-For more information on packaging and signing Android Wear apps, see
-<a href="{@docRoot}training/wearables/apps/packaging.html">Packaging Wearable Apps</a>.</p>
-
-
-<h2 id="studio">Signing Your App in Android Studio</h2>
-
-<p>To sign your app in release mode in Android Studio, follow these steps:</p>
-
-<ol>
-<li>On the menu bar, click <strong>Build</strong> > <strong>Generate Signed APK</strong>.</li>
-<li><p>On the <em>Generate Signed APK Wizard</em> window, click <strong>Create new</strong> to
-create a new keystore.</p>
-<p>If you already have a keystore, go to step 4.</p></li>
-<li><p>On the <em>New Key Store</em> window, provide the required information as shown
-in figure 1.</p>
-<p>Your key should be valid for at least 25 years, so you can sign app updates
-with the same key through the lifespan of your app.</p>
-<img src="{@docRoot}images/tools/signstudio2.png" alt=""
- width="416" height="364" style="margin-top:15px"/>
-<p class="img-caption"><strong>Figure 1</strong>. Create a new keystore in Android Studio.</p>
-</li>
-<li><p>On the <em>Generate Signed APK Wizard</em> window, select a keystore, a private key, and
-enter the passwords for both. Then click <strong>Next</strong>.</p>
-<img src="{@docRoot}images/tools/signstudio1.png" alt=""
- width="349" height="232" style="margin-top:15px"/>
-<p class="img-caption"><strong>Figure 2</strong>. Select a private key in Android Studio.</p>
-</li>
-<li><p>
- On the next window, select a destination for the signed APK(s), select the
- build type, (if applicable) choose the product flavor(s), and click
- <strong>Finish</strong>.</p>
-<img src="{@docRoot}images/tools/signstudio3.png" alt=""
- width="350" height="175" style="margin-top:15px"/>
-<p class="img-caption">
- <strong>Figure 3</strong>. Generate signed APKs for the selected product
- flavors.
-</p>
-<p class="note">
- <strong>Note:</strong> If your project uses product flavors, you can select
- multiple product flavors while holding down the <strong>Ctrl</strong> key on
- Windown/Linux, or the <strong>Command</strong> key on Mac OSX. Android Studio
- will generate a separate APK for each selected product flavor.
-</p>
-
-</li>
-</ol>
-
-<h3 id="sign-auto">Automatically Signing Your App</h3>
-
-<p>In Android Studio, you can configure your project to sign your release APK automatically
-during the build process:</p>
-
-<ol>
-<li>On the project browser, right click on your app and select <strong>Open Module
-Settings</strong>.</li>
-<li>On the <em>Project Structure</em> window, select your app's module under <em>Modules</em>.</li>
-<li>Click on the <strong>Signing</strong> tab.</li>
-<li><p>Select your keystore file, enter a name for this signing configuration (as you may create
-more than one), and enter the required information.</p>
-<img src="{@docRoot}images/tools/signstudio10.png" alt=""
- width="623" height="372" style="margin-top:15px"/>
-<p class="img-caption"><strong>Figure 4</strong>. Create a signing configuration in Android
-Studio.</p>
-</li>
-<li>Click on the <strong>Build Types</strong> tab.</li>
-<li>Select the <strong>release</strong> build.</li>
-<li><p>Under <em>Signing Config</em>, select the signing configuration you just created.</p>
-<img src="{@docRoot}images/tools/signstudio11.png" alt=""
- width="623" height="372" style="margin-top:15px"/>
-<p class="img-caption"><strong>Figure 5</strong>. Select a signing configuration in Android
-Studio.</p>
-</li>
-<li>Click <strong>OK</strong>.</li>
-</ol>
-
-<p>You can also specify your signing settings in Gradle configuration files. For more information,
-see <a href="{@docRoot}tools/building/configuring-gradle.html#configureSigning">Configuring Gradle
-Builds</a>.</p>
-
-
-
-<h2 id="considerations">Signing Considerations</h2>
-
-<p>You should sign all of your apps with the same certificate throughout the expected lifespan
-of your applications. There are several reasons why you should do so:</p>
-
-<ul>
-<li>App upgrade: When the system is installing an update to an app, it compares the certificate(s)
-in the new version with those in the existing version. The system allows the update if the
-certificates match. If you sign the new version with a different certificate, you must assign a
-different package name to the application—in this case, the user installs the new version as
-a completely new application.</li>
-<li>App modularity: Android allows apps signed by the same certificate to run in the same process,
-if the applications so requests, so that the system treats them as a single application. In this
-way you can deploy your app in modules, and users can update each of the modules independently.</li>
-<li>Code/data sharing through permissions: Android provides signature-based permissions
-enforcement, so that an app can expose functionality to another app that is signed with a
-specified certificate. By signing multiple apps with the same certificate and using
-signature-based permissions checks, your apps can share code and data in a secure manner.</li>
-</ul>
-
-<p>If you plan to support upgrades for an app, ensure that your key has a validity
-period that exceeds the expected lifespan of that app. A validity period of 25 years or more is
-recommended. When your key's validity period expires, users will no longer be able to seamlessly
-upgrade to new versions of your application.</p>
-
-<p>If you plan to publish your apps on Google Play, the key you use to sign these apps must have
-a validity period ending after 22 October 2033. Google Play enforces this requirement to ensure
-that users can seamlessly upgrade apps when new versions are available.</p>
-
-
-<h2 id="secure-key">Securing Your Private Key</h2>
-
-<p>Maintaining the security of your private key is of critical importance, both to you and to
-the user. If you allow someone to use your key, or if you leave your keystore and passwords in
-an unsecured location such that a third-party could find and use them, your authoring identity
-and the trust of the user are compromised.</p>
-
-<p>If a third party should manage to take your key without your knowledge or permission, that
-person could sign and distribute apps that maliciously replace your authentic apps or corrupt
-them. Such a person could also sign and distribute apps under your identity that attack
-other apps or the system itself, or corrupt or steal user data.</p>
-
-<p>Your private key is required for signing all future versions of your app. If you lose or
-misplace your key, you will not be able to publish updates to your existing appn. You cannot
-regenerate a previously generated key.</p>
-
-<p>Your reputation as a developer entity depends on your securing your private key properly, at
-all times, until the key is expired. Here are some tips for keeping your key secure:</p>
-
-<ul>
-<li>Select strong passwords for the keystore and key.</li>
-<li>Do not give or lend anyone your private key, and do not let unauthorized persons know your
-keystore and key passwords.</li>
-<li>Keep the keystore file containing your private key in a safe, secure place.</li>
-</ul>
-
-<p>In general, if you follow common-sense precautions when generating, using, and storing
-your key, it will remain secure.</p>
-
-
-<h2 id="expdebug">Expiry of the Debug Certificate</h2>
-
-<p>The self-signed certificate used to sign your application in debug mode has an expiration date
-of 365 days from its creation date. When the certificate expires, you will get a build error.</p>
-
-<p>To fix this problem, simply delete the <code>debug.keystore</code> file. The default storage
-location is in <code>~/.android/</code> on OS X and Linux, in <code>C:\Documents and
-Settings\<user>\.android\</code> on Windows XP, and in
-<code>C:\Users\<user>\.android\</code> on Windows Vista and Windows 7.</p>
-
-<p>The next time you build and run your app, the build tools will regenerate a
- new keystore and debug key. Note that you must run your app, building alone
- does not regenerate the keystore and debug key.</p>
-
-
-<h2 id="signing-manually">Signing Your App Manually</h2>
-
-<p>You do not need Android Studio to sign your app. You can sign
-your app from the command line using standard tools from the Android SDK and the JDK. To sign
-an app in release mode from the command line:</p>
-
-<ol>
-<li>
- <p>Generate a private key using
- <code><a href="http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html"
- >keytool</a></code>.
- For example:</p>
-<pre class="no-pretty-print">
-$ keytool -genkey -v -keystore my-release-key.keystore
--alias alias_name -keyalg RSA -keysize 2048 -validity 10000
-</pre>
- <p>This example prompts you for passwords for the keystore and key, and to provide the
- Distinguished Name fields for your key. It then generates the keystore as a file called
- <code>my-release-key.keystore</code>. The keystore contains a single key, valid for 10000 days.
- The alias is a name that you will use later when signing your app.</p>
-</li>
-<li style="margin-top:18px">
- <p>Compile your app in release mode to obtain an unsigned APK.</p>
-</li>
-<li style="margin-top:18px">
- <p>Sign your app with your private key using
- <code><a href="http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html">jarsigner</a></code>:
- </p>
-<pre class="no-pretty-print">
-$ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1
--keystore my-release-key.keystore my_application.apk alias_name
-</pre>
- <p>This example prompts you for passwords for the keystore and key. It then modifies the APK
- in-place to sign it. Note that you can sign an APK multiple times with different keys.</p>
-</li>
-<li style="margin-top:18px">
- <p>Verify that your APK is signed. For example:</p>
-<pre class="no-pretty-print">
-$ jarsigner -verify -verbose -certs my_application.apk
-</pre>
-</li>
-<li style="margin-top:18px">
- <p>Align the final APK package using
- <code><a href="{@docRoot}tools/help/zipalign.html">zipalign</a></code>.</p>
-<pre class="no-pretty-print">
-$ zipalign -v 4 your_project_name-unaligned.apk your_project_name.apk
-</pre>
- <p><code>zipalign</code> ensures that all uncompressed data starts with a particular byte
- alignment relative to the start of the file, which reduces the amount of RAM consumed by an
- app.</p>
-</li>
-</ol>
+++ /dev/null
-page.title=Preparing for Release
-page.metaDescription=Developer documentation on how to build the signed, release-ready APK. This process is the same for all Android apps.
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>Quickview</h2>
- <ul>
- <li>Learn which resources you'll need to release your app.</li>
- <li>Find out how to configure and build your app for release.</li>
- <li>Learn best practices for releasing your app.</li>
- </ul>
- <h2>In this document</h2>
- <ol>
- <li><a href="#publishing-intro">Introduction</a></li>
- <li><a href="#publishing-gather">Gathering Materials and Resources</a></li>
- <li><a href="#publishing-configure">Configuring Your Application</a></li>
- <li><a href="#publishing-build">Building Your Application</a></li>
- <li><a href="#publishing-resources">Preparing External Servers and Resources</a></li>
- <li><a href="#publishing-test">Testing Your Application for Release</a></li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing Overview</a></li>
- <li><a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a></li>
- <li><a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist for Google Play</a></li>
- </ol>
- </div>
-</div>
-
-<p>Before you distribute your Android application to users you need to prepare it for release. The
-preparation process is a required <a href="{@docRoot}tools/workflow/index.html">development
-task</a> for all Android applications and is the first step in the publishing process (see figure
-1).</p>
-
-<p>When you prepare your application for release, you configure, build, and test a release
-version of your application. The configuration tasks are straightforward, involving basic code
-cleanup and code modification tasks that help optimize your application. The build process is
-similar to the debug build process and can be done using JDK and Android SDK tools. The testing
-tasks serve as a final check, ensuring that your application performs as expected under real-world
-conditions. When you are finished preparing your application for release you have a signed
-<code>.apk</code> file, which you can distribute directly to users or distribute through an
-application marketplace such as Google Play.</p>
-
-<p>This document summarizes the main tasks you need to perform to prepare your application for
-release. The tasks that are described in this document apply to all Android applications regardless
-how they are released or distributed to users. If you are releasing your application through Google
-Play, you should also read <a href="{@docRoot}distribute/tools/launch-checklist.html">Publishing
-Checklist for Google Play</a> to be sure your release-ready application satisfies all Google Play
-requirements.</p>
-
-<p class="note"><strong>Note:</strong> As a best practice, your application should meet all of your
-release criteria for functionality, performance, and stability before you perform the tasks outlined
-in this document.</p>
-
-<img src="{@docRoot}images/publishing/publishing_overview_prep.png"
- alt="Shows how the preparation process fits into the development process"
- height="190"
- id="figure1" />
-<p class="img-caption">
- <strong>Figure 1.</strong> Preparing for release is a required <a
-href="{@docRoot}tools/workflow/index.html">development
-task</a> and is the first step in the publishing process.
-</p>
-
-<h2 id="publishing-intro">Introduction</h2>
-
-<p>To release your application to users you need to create a release-ready package that users can
-install and run on their Android-powered devices. The release-ready package contains the same
-components as the debug <code>.apk</code> file — compiled source code, resources, manifest
-file, and so on — and it is built using the same build tools. However, unlike the debug
-<code>.apk</code> file, the release-ready <code>.apk</code> file is signed with your own certificate
-and it is optimized with the zipalign tool.</p>
-
-<div class="figure" style="width:331px">
- <img src="{@docRoot}images/publishing/publishing_preparing.png"
- alt="Shows the five tasks you perform to prepare your app for release"
- height="450" />
- <p class="img-caption">
- <strong>Figure 2.</strong> You perform five main tasks to prepare your application for
- release.
- </p>
-</div>
-
-<p>The signing and optimization tasks are usually seamless if you are building your application with
-Android Studio. For example, you can use Android Studio with the Gradle build files to compile, sign,
-and optimize your application all at once. You can also configure the Gradle build files to do the
-same when you build from the command line. For more details about using the Gradle build files, see
-the <a href="{@docRoot}sdk/installing/studio-build.html">Build System</a> guide.</p>
-
-<p>To prepare your application for release you typically perform five main tasks (see figure 2).
-Each main task may include one or more smaller tasks depending on how you are releasing your
-application. For example, if you are releasing your application through Google Play you may want
-to add special filtering rules to your manifest while you are configuring your application for
-release. Similarly, to meet Google Play publishing guidelines you may have to prepare screenshots
-and create promotional text while you are gathering materials for release.</p>
-
-<p>You usually perform the tasks listed in figure 2 after you have throroughly debugged and tested
-your application. The Android SDK contains several tools to help you test and debug your Android
-applications. For more information, see the <a
-href="{@docRoot}tools/debugging/index.html">Debugging</a> and <a
-href="{@docRoot}tools/testing/index.html">Testing</a> sections in the Dev Guide.</p>
-
-<h2 id="publishing-gather">Gathering Materials and Resources</h2>
-
-<p>To begin preparing your application for release you need to gather several supporting items. At a
-minimum this includes cryptographic keys for signing your application and an application icon. You
-might also want to include an end-user license agreement.</p>
-
-<h4 id="publishing-keys">Cryptographic keys</h4>
-
-<p>The Android system requires that each installed application be digitally signed with a
-certificate that is owned by the application's developer (that is, a certificate for which the
-developer holds the private key). The Android system uses the certificate as a means of identifying
-the author of an application and establishing trust relationships between applications. The
-certificate that you use for signing does not need to be signed by a certificate authority; the
-Android system allows you to sign your applications with a self-signed certificate. To learn about
-certificate requirements, see <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your
-Applications</a>.</p>
-
-<p class="caution"><strong>Important:</strong> Your application must be signed with a cryptographic
-key whose validity period ends after 22 October 2033.</p>
-
-<p>You may also have to obtain other release keys if your application accesses a service or uses a
-third-party library that requires you to use a key that is based on your private key. For example,
-if your application uses the <a
-href="http://code.google.com/android/add-ons/google-apis/reference/com/google/android/maps/MapView.html">MapView</a>
-class, which is part of the <a
-href="http://code.google.com/android/add-ons/google-apis/maps-overview.html">Google Maps external
-library</a>, you will need to register your application with the Google Maps service and obtain
-a Maps API key. For information about getting a Maps API key, see <a
-href="http://code.google.com/android/add-ons/google-apis/mapkey.html"> Obtaining a Maps API
-key</a>.</p>
-
-<h4>Application Icon</h4>
-
-<p>Be sure you have an application icon and that it meets the recommended <a
-href="{@docRoot}guide/practices/ui_guidelines/icon_design_launcher.html">icon guidelines</a>. Your
-application's icon helps users identify your application on a device's Home
-screen and in the Launcher window. It also appears in Manage Applications, My Downloads, and
-elsewhere. In addition, publishing services such as Google Play display your icon to users.</p>
-
-<p class="note"><strong>Note:</strong> If you are releasing your application on Google Play, you
-need to create a high resolution
- version of your icon. See <a
-href="https://www.google.com/support/androidmarket/developer/bin/answer.py?answer=1078870">Graphic
-Assets for your Application</a> for more information.</p>
-
-<h4>End-user License Agreement</h4>
-
-<p>Consider preparing an End User License Agreement (EULA) for your application. A EULA can help
-protect your person, organization, and intellectual property, and we recommend that you provide one
-with your application.</p>
-
-<h4>Miscellaneous Materials</h4>
-
-<p>You might also have to prepare promotional and marketing materials to publicize your application.
-For example, if you are releasing your application on Google Play you will need to prepare some
-promotional text and you will need to create screenshots of your application. For more
-information, see
-<a href="https://www.google.com/support/androidmarket/developer/bin/answer.py?answer=1078870">
-Graphic Assets for your Application</a></p>
-
-<h2 id="publishing-configure">Configuring Your Application for Release</h2>
-
-<p>After you gather all of your supporting materials you can start configuring your application
-for release. This section provides a summary of the configuration changes we recommend that you make
-to your source code, resource files, and application manifest prior to releasing your application.
-Although most of the configuration changes listed in this section are optional, they are
-considered good coding practices and we encourage you to implement them. In some cases,
-you may have already made these configuration changes as part of your development process.</p>
-
-<h4>Choose a good package name</h4>
-
-<p>Make sure you choose a package name that is suitable over the life of your application. You
-cannot change the package name after you distribute your application to users. You can set the
-package name in application's manifest file. For more information, see the <a
-href="{@docRoot}guide/topics/manifest/manifest-element.html#package">package</a> attribute
-documentation.</p>
-
-<h4>Turn off logging and debugging</h4>
-
-<p>Make sure you deactivate logging and disable the debugging option before you build your
-application for release. You can deactivate logging by removing calls to
-{@link android.util.Log} methods in your source files. You can disable debugging by removing the
-<code>android:debuggable</code> attribute from the <code><application></code> tag in your
-manifest file, or by setting the <code>android:debuggable</code> attribute to
-<code>false</code> in your manifest file. Also, remove any log files or static test files that
-were created in your project.</p>
-
-<p>Also, you should remove all {@link android.os.Debug} tracing calls that you
-added to your code, such as {@link android.os.Debug#startMethodTracing()} and
-{@link android.os.Debug#stopMethodTracing()} method calls.</p>
-
-<p class="caution"><strong>Important:</strong> Ensure that you disable debugging for
-your app if using {@link android.webkit.WebView} to display paid for content or if using JavaScript
-interfaces, since debugging allows users to inject scripts and extract content using Chrome
-DevTools. To disable debugging, use the
-{@link android.webkit.WebView#setWebContentsDebuggingEnabled(boolean) WebView.setWebContentsDebuggingEnabled()}
-method.</p>
-
-<h4>Clean up your project directories</h4>
-
-<p>Clean up your project and make sure it conforms to the directory structure described in <a
-href="{@docRoot}tools/projects/index.html#ApplicationProjects">Android Projects</a>.
-Leaving stray or orphaned files in your project can prevent your application from compiling and
-cause your application to behave unpredictably. At a minimum you should do the following cleanup
-tasks:</p>
-
-<ul>
- <li>Review the contents of your <code>jni/</code>, <code>lib/</code>, and <code>src/</code>
- directories. The <code>jni/</code> directory should contain only source files associated with the
- <a href="{@docRoot}tools/sdk/ndk/index.html">Android NDK</a>, such as
- <code>.c</code>, <code>.cpp</code>, <code>.h</code>, and <code>.mk</code> files. The
- <code>lib/</code> directory should contain only third-party library files or private library
- files, including prebuilt shared and static libraries (for example, <code>.so</code> files). The
- <code>src/</code> directory should contain only the source files for your application
- (<code>.java</code> and <code>.aidl</code> files). The <code>src/</code> directory should not
- contain any <code>.jar</code> files.</li>
- <li>Check your project for private or proprietary data files that your application does not use
- and remove them. For example, look in your project's <code>res/</code> directory for old
- drawable files, layout files, and values files that you are no longer using and delete them.</li>
- <li>Check your <code>lib/</code> directory for test libraries and remove them if they are no
- longer being used by your application.</li>
- <li>Review the contents of your <code>assets/</code> directory and your <code>res/raw/</code>
- directory for raw asset files and static files that you need to update or remove prior to
- release.</li>
-</ul>
-
-<h4>Review and update your manifest and Gradle build settings</h4>
-
-<p>Verify that the following manifest and build files items are set correctly:</p>
-
-<ul>
- <li><a href="{@docRoot}guide/topics/manifest/uses-permission-element.html">
- <uses-permission></a> element
- <p>You should specify only those permissions that are relevant and required for your application.</p>
- </li>
- <li><code>android:icon</code> and <code>android:label</code> attributes
- <p>You must specify values for these attributes, which are located in the
- <a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a>
- element.</p>
- </li>
- <li><code>android:versionCode</code> and <code>android:versionName</code> attributes.
- <p>We recommend that you specify values for these attributes, which are located in the
- <a href="{@docRoot}guide/topics/manifest/manifest-element.html"><manifest></a>
- element. For more information see
- <a href="{@docRoot}tools/publishing/versioning.html">Versioning your Application</a>.</p>
- </li>
-</ul>
-
-<p>There are several additional manifest or build file elements that you can set if you are releasing your
-application on Google Play. For example, the <code>android:minSdkVersion</code> and
-<code>android:targetSdkVersion</code> attributes, which are located in the <a
-href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"> <uses-sdk></a> element. For more
-information about these and other Google Play settings, see <a
-href="{@docRoot}google/play/filters.html">Filters on Google Play</a>.</p>
-
-<h4>Address compatibility issues</h4>
-
-<p>Android provides several tools and techniques to make your application compatible with a wide
-range of devices. To make your application available to the largest number of users, consider
-doing the following:</p>
-
-<ul>
- <li><strong>Add support for multiple screen configurations</strong>
- <p>Make sure you meet the
- <a href="{@docRoot}guide/practices/screens_support.html#screen-independence">
- best practices for supporting multiple screens</a>. By supporting multiple screen configurations
- you can create an application that functions properly and looks good on any of the screen sizes
- supported by Android.</p>
- </li>
- <li><strong>Optimize your application for Android tablet devices.</strong>
- <p>If your application is designed for devices older than Android 3.0, make it compatible
- with Android 3.0 devices by following the guidelines and best practices described in
- <a href="{@docRoot}guide/practices/optimizing-for-3.0.html">Optimizing Apps for Android 3.0
- </a>.</p>
- </li>
- <li><strong>Consider using the Support Library</strong>
- <p>If your application is designed for devices running Android 3.x, make your application
- compatible with older versions of Android by adding the
- <a href="{@docRoot}tools/support-library/index.html">Support Library</a> to your
- application project. The Support Library provides static support libraries that you can add to
- your Android application, which enables you to use APIs that are either not available on
- older platform versions or use utility APIs that are not part of the framework APIs.</p>
- </li>
-</ul>
-
-<h4>Update URLs for servers and services</h4>
-
-<p>If your application accesses remote servers or services, make sure you are using the production
-URL or path for the server or service and not a test URL or path.</p>
-
-<h4>Implement Licensing (if you are releasing on Google Play)</h4>
-
-<p>If you are releasing a paid application through Google Play, consider adding support for
-Google Play Licensing. Licensing lets you control access to your application based on whether the
-current user has purchased it. Using Google Play Licensing is optional even if you are
-releasing your app through Google Play.</p>
-
-<p>For more information about Google Play Licensing Service and how to use it in your
-application, see <a href="{@docRoot}google/play/licensing/index.html">Application Licensing</a>.</p>
-
-<h2 id="publishing-build">Building Your Application for Release</h2>
-
-<p>After you finish configuring your application you can build it into a release-ready
-<code>.apk</code> file that is signed and optimized. The JDK includes the tools for signing the
-<code>.apk</code> file (Keytool and Jarsigner); the Android SDK includes the tools for compiling and
-optimizing the <code>.apk</code> file. If you are using Android Studio or you are using
-the Gradle build system from the command line, you can automate the entire build process.
-For more information about configuring Gradle builds, see
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>.</p>
-
-<h3>Building with Android Studio</h3>
-
-<p>You can use the Gradle build system, integrated with Android Studio to build a release-ready
-<code>.apk</code> file that is signed with your private key and optimized. To learn how to setup and
-run builds from Android Studio, see
-<a href="{@docRoot}tools/building/building-studio.html">Building and Running from Android Studio</a>.</p>
-
-<p>The build process assumes that you have a certificate and private key
-suitable for signing your application. If you do not have a suitable certificate and private key,
-Android Studio can help you generate one. For more information about the signing process, see
-<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
-
-
-<h2 id="publishing-resources">Preparing External Servers and Resources</h2>
-
-<p>If your application relies on a remote server, make sure the server is secure and that it is
-configured for production use. This is particularly important if you are implementing <a
-href="{@docRoot}google/play/billing/index.html">in-app billing</a> in your application and you are
-performing the signature verification step on a remote server.</p>
-
-<p>Also, if your application fetches content from a remote server or a real-time service (such as a
-content feed), be sure the content you are providing is up to date and production-ready.</p>
-
-<h2 id="publishing-test">Testing Your Application for Release</h2>
-
-<p>Testing the release version of your application helps ensure that your application runs properly
-under realistic device and network conditions. Ideally, you should test your application on at least
-one handset-sized device and one tablet-sized device to verify that your user interface elements are
-sized correctly and that your application's performance and battery efficiency are acceptable.</p>
-
-<p>As a starting point for testing, see
-<a href="{@docRoot}tools/testing/what_to_test.html">What to Test</a>. This article provides
-a summary of common Android situations that you should consider when you are testing. When you are
-done testing and you are satisfied that the release version of your application
-behaves correctly, you can release your application to users. For more information, see
-<a href="{@docRoot}tools/publishing/publishing_overview.html#publishing-release">Releasing Your
-Application to Users</a>. If you are publishing your application on Google Play, see
-<a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist
-for Google Play</a>.</p>
-
-
+++ /dev/null
-page.title=Publishing Overview
-page.metaDescription=Start here for an overview of publishing options for Android apps.
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>Quickview</h2>
- <ul>
- <li>Learn how to publish Android apps.</li>
- <li>Find out how to prepare apps for release.</li>
- <li>Learn how to release apps to users.</li>
- </ul>
- <h2>In this document</h2>
- <ol>
- <li><a href="#publishing-prepare">Preparing Your Application for Release</a></li>
- <li><a href="#publishing-release">Releasing Your Application to Users</a>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}distribute/tools/launch-checklist.html">Publishing on Google Play</a></li>
- </ol>
-</div>
-</div>
-
-<p>Publishing is the general process that makes your Android applications available to users. When you
-publish an Android application you perform two main tasks:</p>
-
-<ul>
- <li>You prepare the application for release.
- <p>During the preparation step you build a release version of your application, which users can
- download and install on their Android-powered devices.</p>
- </li>
- <li>You release the application to users.
- <p>During the release step you publicize, sell, and distribute the release version of your
- application to users.</p>
- </li>
-</ul>
-
-<p>Usually, you release your application through an application marketplace, such as <a href="{@docRoot}distribute/googleplay/index.html">Google Play</a>.
-However, you can also release applications by sending them directly to users or by letting users
-download them from your own website.</p>
-
-<p>Figure 1 shows how the publishing process fits into the overall Android <a
-href="{@docRoot}tools/workflow/index.html">application development process</a>.
-The publishing process is typically performed after you finish testing your application in a debug
-environment. Also, as a best practice, your application should meet all of your release criteria for
-functionality, performance, and stability before you begin the publishing process.</p>
-
-<img src="{@docRoot}images/publishing/publishing_overview.png" alt="Shows where the publishing
- process fits into the overall development process" height="86" id="figure1" />
-<p class="img-caption">
- <strong>Figure 1.</strong> Publishing is the last phase of the Android <a
-href="{@docRoot}tools/workflow/index.html">application development process</a>.
-</p>
-
-<h2 id="publishing-prepare">Preparing Your Application for Release</h2>
-
-<p>Preparing your application for release is a multi-step process that involves the following
-tasks:</p>
-
-<ul>
- <li>Configuring your application for release.
- <p>At a minimum you need to remove {@link android.util.Log} calls and remove the
- <a href="{@docRoot}guide/topics/manifest/application-element.html#debug">android:debuggable</a>
- attribute from your manifest file. You should also provide values for the
- <code>android:versionCode</code> and <code>android:versionName</code> attributes, which are
- located in the
- <a href="{@docRoot}guide/topics/manifest/manifest-element.html"><manifest></a>
- element. You may also have to configure several other settings to meet Google Play
- requirements or accomodate whatever method you're using to release your application.</p>
- <p>If you are using Gradle build files, you can use the <em>release</em> build type to set
- your build settings for the published version of your app. </p>
- </li>
- <li>Building and signing a release version of your application.
- <p>You can use the Gradle build files with the <em>release</em> build type to build and sign a
- release version of your application. See
- <a href="{@docRoot}tools/building/building-studio.html">Building and Running from Android
- Studio</a>.</p>
- </li>
- <li>Testing the release version of your application.
- <p>Before you distribute your application, you should thoroughly test the release version on at
- least one target handset device and one target tablet device.</p>
- </li>
- <li>Updating application resources for release.
- <p>You need to be sure that all application resources such as multimedia files and graphics
- are updated and included with your application or staged on the proper production servers.</p>
- </li>
- <li>Preparing remote servers and services that your application depends on.
- <p>If your application depends on external servers or services, you need to be sure they
- are secure and production ready.</p>
- </li>
-</ul>
-
-<p>You may have to perform several other tasks as part of the preparation process. For example, you
-will need to get a private key for signing your application, and you may need to get a Maps API
-release key if you are using the <a
-href="http://code.google.com/android/add-ons/google-apis/maps-overview.html">Google Maps external
-library</a>. You will also need to create an icon for your application, and you may want to prepare
-an End User License Agreement (EULA) to protect your person, organization, and intellectual
-property.</p>
-
-<p>When you are finished preparing your application for release you will have a signed
-<code>.apk</code> file that you can distribute to users.</p>
-
-<p>To learn how to prepare your application for release, see <a
-href="{@docRoot}tools/publishing/preparing.html">Preparing for Release</a> in the Dev Guide. This
-topic provides step-by-step instructions for configuring and building a release version of your
-application.</p>
-
-<h2 id="publishing-release">Releasing Your Application to Users</h2>
-
-<p>You can release your Android applications several ways. Usually, you release applications
-through an application marketplace such as Google Play, but you can also release applications
-on your own website or by sending an application directly to a user.
-
-<h3 id="publishing-marketplace">Releasing through an App Marketplace</h3>
-
-<p>If you want to distribute your apps to the broadest possible audience, releasing through
-an app marketplace such as Google Play is ideal. </p>
-
-<p>Google Play is the premier marketplace for Android apps and is particularly
-useful if you want to distribute your applications to a large global audience.
-However, you can distribute your apps through any app marketplace you want or
-you can use multiple marketplaces.</p>
-
-
-<h4 id="publishing-market">Releasing Your Applications on Google Play</h4>
-
-<p>Google Play is a robust publishing platform that helps you publicize, sell, and distribute
-your Android applications to users around the world. When you release your applications through
-Google Play you have access to a suite of developer tools that let you analyze your sales,
-identify market trends, and control who your applications are being distributed to. You also have
-access to several revenue-enhancing features such as <a
-href="{@docRoot}google/play/billing/index.html">in-app billing</a> and <a
-href="{@docRoot}google/play/licensing/index.html">application licensing</a>. The rich array of tools
-and features, coupled with numerous end-user community features, makes Google Play the premier
-marketplace for selling and buying Android applications.</p>
-
-<p>Releasing your application on Google Play is a simple process that involves three basic
- steps:</p>
-
-<ul>
- <li>Preparing promotional materials.
- <p>To fully leverage the marketing and publicity capabilities of Google Play, you need to
- create promotional materials for your application, such as screenshots, videos, graphics, and
- promotional text.</p>
- </li>
- <li>Configuring options and uploading assets.
- <p>Google Play lets you target your application to a worldwide pool of users and devices.
- By configuring various Google Play settings, you can choose the countries you want to
- reach, the listing languages you want to use, and the price you want to charge in each
- country. You can also configure listing details such as the application type, category, and
- content rating. When you are done configuring options you can upload your promotional materials
- and your application as a draft (unpublished) application.</p>
- </li>
- <li>Publishing the release version of your application.
- <p>If you are satisfied that your publishing settings are correctly configured and your
- uploaded application is ready to be released to the public, you can simply click
- <strong>Publish</strong > in the developer console and within minutes your application will be
- live and available for download around the world.</p>
- </li>
-</ul>
-
-<p>For information complete information, see <a href="{@docRoot}distribute/googleplay/index.html">Google Play</a>.</p>
-
-
-<h3 id="publishing-email">Releasing your application through email</h3>
-
-<div class="figure" style="width:246px">
- <img src="{@docRoot}images/publishing/publishing_via_email.png"
- alt="Screenshot showing the graphical user interface users see when you send them an app"
- style="width:240px;" />
- <p class="img-caption">
- <strong>Figure 1.</strong> Users can simply click <strong>Install</strong> when you send them
- an application via email.
- </p>
-</div>
-
-<p>The easiest and quickest way to release your application is to send it to a user through
-email. To do this, you prepare your application for release and then attach it to an email
-and send it to a user. When the user opens your email message on their Android-powered device
-the Android system will recognize the APK and display an <strong>Install Now</strong>
-button in the email message (see figure 1). Users can install your application by touching the
-button.</p>
-
-<p class="note"><strong>Note:</strong> The <strong>Install Now</strong> button
-shown in Figure 1 appears only if a user has configured their device to allow
-installation from <a href="#unknown-sources">unknown sources</a> and has opened your
-email with the native Gmail application.</p>
-
-<p>Distributing applications through email is convenient if you are sending your application to
-only a few trusted users, but it provides few protections from piracy and unauthorized
-distribution; that is, anyone you send your application to can simply forward it to someone else.</p>
-
-<h2 id="publishing-website">Releasing through a web site</h2>
-
-<p>If you do not want to release your app on a marketplace like Google Play, you
-can make the app available for download on your own website or server, including
-on a private or enterprise server. To do this, you must first prepare your
-application for release in the normal way. Then all you need to do is host the
-release-ready APK file on your website and provide a download link to users.
-</p>
-
-<p>When users browse to the download link from their Android-powered devices,
-the file is downloaded and Android system automatically starts installing it on
-the device. However, the installation process will start automatically only if
-the user has configured their Settings to allow the installation of apps from
-<a href="#unknown-sources">unknown sources</a>.</p>
-
-<p>Although it is relatively easy to release your application on your own
-website, it can be inefficient. For example, if you want to monetize your
-application you will have to process and track all financial transactions
-yourself and you will not be able to use Google Play's <a
-href="{@docRoot}google/play/billing/index.html">In-app Billing service</a>
-to sell in-app products. In addition, you will not be able to use the <a
-href="{@docRoot}google/play/licensing/index.html">Licensing service</a> to
-help prevent unauthorized installation and use of your application.</p>
-
-
-<h2 id="unknown-sources">User Opt-In for Apps from Unknown Sources</h2>
-
-<div class="figure" style="width:246px;margin-top:0;">
- <img src="{@docRoot}images/publishing/publishing_unknown_sources_sm.png"
- alt="Screenshot showing the setting for accepting download and install of
- apps from unknown sources." style="width:240px;" />
- <p class="img-caption">
- <strong>Figure 2.</strong> Users must enable the <strong>Unknown sources</strong>
- setting before they can install apps not downloaded from Google Play.
- </p>
-</div>
-
-<p>Android protects users from inadvertent download and install of apps from
-locations other than Google Play (which is trusted). It blocks such installs
-until the user opts-in <strong>Unknown sources</strong> in
-Settings <strong>></strong> Security, shown in Figure 2. To allow
-the installation of applications from other sources, users need to enable the
-Unknown sources setting on their devices, and they need to make this
-configuration change <em>before</em> they download your application to their
-devices.</p>
-
-<p class="note">Note that some network providers do not allow users to install
-applications from unknown sources.</p>
+++ /dev/null
-page.title=Versioning Your Applications
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
-<h2>Quickview</h2>
-
-<ul>
-<li>Your application <em>must</em> be versioned</a></li>
-<li>You set the version in the application's manifest file</li>
-<li>How you version your applications affects how users upgrade </li>
-<li>Determine your versioning strategy early in the development process, including considerations for future releases.</li>
-</ul>
-
-<h2>In this document</h2>
-
-<ol>
-<li><a href="#appversioning">Setting Application Version</a></li>
-<li><a href="#minsdkversion">Specifying Your Application's System API Requirements</a>
-</ol>
-
-
-<h2>See also</h2>
-
-<ol>
-<li><a href="{@docRoot}tools/publishing/preparing.html">Preparing to Publish Your Application</a></li>
-<li><a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist for Google Play</a></li>
-<li><a href="{@docRoot}guide/topics/manifest/manifest-intro.html">The AndroidManifest.xml File</a></li>
-</ol>
-
-</div>
-</div>
-
-<p>Versioning is a critical component of your application upgrade and maintenance
-strategy. Versioning is important because:</p>
-
-<ul>
-<li>Users need to have specific information about the application version that
-is installed on their devices and the upgrade versions available for
-installation. </li>
-<li>Other applications — including other applications that you publish as
-a suite — need to query the system for your application's version, to
-determine compatibility and identify dependencies.</li>
-<li>Services through which you will publish your application(s) may also need to
-query your application for its version, so that they can display the version to
-users. A publishing service may also need to check the application version to
-determine compatibility and establish upgrade/downgrade relationships.</li>
-</ul>
-
-<p>The Android system does not use app version information to enforce
-restrictions on upgrades, downgrades, or compatibility of third-party apps. Instead, you (the
-developer) are responsible for enforcing version restrictions within your application or by
-informing users of the version restrictions and limitations. The Android system does, however,
-enforce system version compatibility as expressed by the <code>minSdkVersion</code> attribute in the
-manifest. This attribute allows an application to specify the minimum system API with which it is
-compatible. For more information see <a href="#minsdkversion">Specifying Minimum System API
-Version</a>.</p>
-
-<h2 id="appversioning">Setting Application Version</h2>
-<p>To define the version information for your application, you set attributes in
-the application's manifest file. Two attributes are available, and you should
-always define values for both of them: </p>
-
-<ul>
-<li><code>android:versionCode</code> — An integer value that represents
-the version of the application code, relative to other versions.
-
-<p>The value is an integer so that other applications can programmatically
-evaluate it, for example to check an upgrade or downgrade relationship. You can
-set the value to any integer you want, however you should make sure that each
-successive release of your application uses a greater value. The system does not
-enforce this behavior, but increasing the value with successive releases is
-normative. </p>
-
-<p>Typically, you would release the first version of your application with
-versionCode set to 1, then monotonically increase the value with each release,
-regardless whether the release constitutes a major or minor release. This means
-that the <code>android:versionCode</code> value does not necessarily have a
-strong resemblance to the application release version that is visible to the
-user (see <code>android:versionName</code>, below). Applications and publishing
-services should not display this version value to users.</p>
-
-<p class="warning">
- <strong>Warning:</strong> The greatest possible value for <code>
- android:versionCode</code> is <code>MAXINT</code> (2147483647). However, if
- you upload an app with this value, your app can't ever be updated.
-</p>
-
-</li>
-<li><code>android:versionName</code> — A string value that represents the
-release version of the application code, as it should be shown to users.
-<p>The value is a string so that you can describe the application version as a
-<major>.<minor>.<point> string, or as any other type of
-absolute or relative version identifier. </p>
-
-<p>As with <code>android:versionCode</code>, the system does not use this value
-for any internal purpose, other than to enable applications to display it to
-users. Publishing services may also extract the <code>android:versionName</code>
-value for display to users.</p>
-</li>
-</ul>
-
-<p>You define both of these version attributes in the
-<code><manifest></code> element of the manifest file or the Gradle build file. See
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>.</p>
-
-<p>Here's an example manifest that shows the <code>android:versionCode</code>
-and <code>android:versionName</code> attributes in the
-<code><manifest></code> element. </p>
-
-<pre>
-<?xml version="1.0" encoding="utf-8"?>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.example.package.name"
- android:versionCode="2"
- android:versionName="1.1">
- <application android:icon="@drawable/icon" android:label="@string/app_name">
- ...
- </application>
-</manifest>
-</pre>
-
-<p>In this example, note that <code>android:versionCode</code> value indicates
-that the current .apk contains the second release of the application code, which
-corresponds to a minor follow-on release, as shown by the
-<code>android:versionName</code> string. </p>
-
-<p>The Android framework provides an API to let applications query the system
-for version information about your application. To obtain version information,
-applications use the
-{@link android.content.pm.PackageManager#getPackageInfo(java.lang.String, int)}
-method of {@link android.content.pm.PackageManager PackageManager}. </p>
-
-<h2 id="minsdkversion">Specifying Your Application's System API Requirements</h2>
-
-<p>If your application requires a specific minimum version of the Android
-platform, or is designed only to support a certain range of Android platform
-versions, you can specify those version requirements as API Level identifiers
-in the application's manifest file. Doing so ensures that your
-application can only be installed on devices that
-are running a compatible version of the Android system. </p>
-
-<p>To specify API Level requirements, add a <code><uses-sdk></code>
-element in the application's manifest, with one or more of these attributes: </p>
-
-<ul>
-<li><code>android:minSdkVersion</code> — The minimum version
-of the Android platform on which the application will run, specified
-by the platform's API Level identifier. </li>
-<li><code>android:targetSdkVersion</code> — Specifies the API Level
-on which the application is designed to run. In some cases, this allows the
-application to use manifest elements or behaviors defined in the target
-API Level, rather than being restricted to using only those defined
-for the minimum API Level.</li>
-<li><code>android:maxSdkVersion</code> — The maximum version
-of the Android platform on which the application is designed to run,
-specified by the platform's API Level identifier. <strong>Important:</strong> Please read the <a
-href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code><uses-sdk></code></a>
-documentation before using this attribute. </li>
-</ul>
-
-<p>When preparing to install your application, the system checks the value of this
-attribute and compares it to the system version. If the
-<code>android:minSdkVersion</code> value is greater than the system version, the
-system aborts the installation of the application. Similarly, the system
-installs your application only if its <code>android:maxSdkVersion</code>
-is compatible with the platform version.</p>
-
-<p>If you do not specify these attributes in your manifest, the system assumes
-that your application is compatible with all platform versions, with no
-maximum API Level. </p>
-
-<p>To specify a minimum platform version for your application, add a
-<code><uses-sdk></code> element as a child of
-<code><manifest></code>, then define the
-<code>android:minSdkVersion</code> as an attribute. </p>
-
-<p>For more information, see the <a
-href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code><uses-sdk></code></a>
-manifest element documentation and the <a
-href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API Levels</a> document. For
-Gradle build settings, see
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>.</p>
+++ /dev/null
-page.title=SDK Build Tools Release Notes
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>See Also</h2>
- <ol>
- <li><a href="{@docRoot}tools/building/index.html">Building and Running</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>Build Tools is a component of the Android SDK required for building Android
- application code. The latest version of these tools is included in the
- <a href="{@docRoot}sdk/index.html">SDK starter package</a> and installed in the
- <code><sdk>/build-tools/</code> directory.</p>
-
-<p>You should always keep your Build Tools component updated by downloading the latest version
- using the <a href="{@docRoot}tools/help/sdk-manager.html">Android SDK Manager</a>. By default,
- the Android SDK uses the most recent downloaded version of the Build Tools. If your projects
- depend on older versions of the Build Tools, the SDK Manager allows you to download and maintain
- separate versions of the tools for use with those projects.</p>
-
-<p>To use a specific version of the Build Tools in your application project:</p>
-
-
- <ol>
- <li>In the root folder of your application project, find the {@code build.gradle}
- file.</li>
- <li>Open the file and specify the Build Tools version by adding a {@code buildToolsVersion}
- property to the {@code android} section:
-<pre>
-android {
- ...
- buildToolsVersion "17.0.0"
- ...
-}
-</pre>
- </li>
- </ol>
-
-
-<h2 id="notes">Revisions</h2>
-
-<p>The sections below provide notes about releases of the Build Tools. To determine which
-revisions of the Build Tools are available in your SDK, refer to the <em>Installed Packages</em>
-listing in the Android SDK Manager.</p>
-
-<div class="toggle-content opened">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 23.0.3</a> <em>(March 2016)</em>
- </p>
- <div class="toggle-content-toggleme">
- <ul>
- <li>Fix issues in the <a href="{@docRoot}guide/topics/renderscript/compute.html">RenderScript</a>
- Support Library on arm64 devices.</li>
- <li>Fix issues in the <a href="{@docRoot}guide/topics/renderscript/compute.html">RenderScript</a>
- Support Library on certain Jelly Bean devices.</li>
- <li>Support <code>renderscriptTargetAPI 21+</code> when using Android
- Plugin for Gradle, Revision 2.1.0 and above .</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content opened">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 23.0.2</a> <em>(November 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <ul>
- <li>Improved the merging performance of the <code>dx</code> tool.</li>
- <li>Fixed issues in the <a href="{@docRoot}guide/topics/renderscript/compute.html">RenderScript</a>
- compiler for Windows.</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 23.0.1</a> <em>(October 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixed issues in the RenderScript tools.</p>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 23.0.0</a> <em>(August 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Added support for the Android 6.0 (API level 23) release.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 22.0.1</a> <em>(March 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixed compatibility issues with
- <a href="{@docRoot}guide/topics/renderscript/compute.html">RenderScript</a> kernels on
- Android 4.4 (API level 19) to Android 4.1 (API level 16) devices.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 22.0.0</a> <em>(March 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Added support for Android 5.1 (API level 22).</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.1.2</a> <em>(February 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixed problem with building data layouts in 32-bit mode.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.1.1</a> <em>(November 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixed multidex script issues.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.1</a> <em>(October 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Added multidex file support for APKs and Jack support to address the 64K method reference
- limit.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.0.2</a> <em>(October 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Complete updates for Eclipse ADT to solve instability issues on Windows platforms.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.0.1</a> <em>(October 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Initial updates for Eclipse ADT on Windows. Please use Revision 21.0.2.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 21.0.0</a> <em>(October 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android 5.0 (API level 21).</li>
- <li>RenderScript now supports seamless 32/64-bit operation for API level 21 and higher.</li>
- <li>Fixed issue with the Gradle build system when using the JaCoCo plugin.
- (<a href="http://b.android.com/69174">Issue 69174</a>)</li>
- <li>Added an <em>input-list</em> option for use with long command lines on Windows.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 20.0.0</a> <em>(June 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android Wear.</li>
- </ul>
- </dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 19.1.0</a> <em>(May 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added <code>zipalign</code> to the Build Tools.</li>
- <li>Modified <code>aapt</code> to ignore XML files that fail to compile.</li>
- </ul>
- </dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 19.0.3</a> <em>(March 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Fixed an issue with RenderScript support.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 19.0.2</a> <em>(February 2014)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Fixed RenderScript build issues:</dt>
- <dd>
- <ul>
- <li>Fixed a problem with RenderScript bitcode encoding.
- (<a href="http://b.android.com/64775">Issue 64775</a>)
- </li>
- <li>Fixed a problem with RenderScript missing math symbols
- (<a href="http://b.android.com/64110">Issue 64110</a>)
- </li>
- </ul>
- </dd>
- </dl>
- <p></p>
-
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 19.0.1</a> <em>(December 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Fixed miscellaneous build issues:</dt>
- <dd>
- <ul>
- <li>Fixed support for compiling RenderScript in NDK mode with Gradle.</li>
- <li>Fixed {@code BufferOverflowException} problem in the dx build.
- (<a href="http://b.android.com/61710">Issue 61710</a>)
- </li>
- </ul>
- </dd>
- </dl>
- <p></p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 19</a> <em>(October 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Added support for Android 4.4 (API level 19) build targets.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 18.1.1</a> <em>(September 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Fixed several minor build issues.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 18.1.0</a> <em>(September 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Fixed issue with RenderScript support mode.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 18.0.1</a> <em>(July 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Added support for Android 4.3 (API level 18) build targets.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Build Tools, Revision 17</a> <em>(May 2013)</em>
- </p>
- <div class="toggle-content-toggleme">
-
- <p>Initial release.</p>
-
- <dl>
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Included support for Android 4.2 (API level 17) build targets.</li>
- <li>Decoupled the build-specific components of the Android SDK from the platform-tools
- component, so that the build tools can be updated independently of the integrated
- development environment (IDE) components.</li>
- </ul>
- </dd>
- </dl>
-
- </div>
-</div>
+++ /dev/null
-page.title=Android Plugin for Gradle Release Notes
-
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>
- In this document
- </h2>
-
- <ol>
- <li>
- <a href="#updating-plugin">Updating the Android Plugin for Gradle
- Version</a>
- </li>
-
- <li>
- <a href="#updating-gradle">Updating the Gradle Version</a>
- </li>
-
- <li>
- <a href="#revisions">Revisions</a>
- </li>
- </ol>
-
- <h2>
- See also
- </h2>
-
- <ol>
- <li>
- <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/">Android Plugin DSL
- Reference</a>
- </li>
-
- <li>
- <a href="{@docRoot}sdk/installing/studio-build.html">Build System
- Overview</a>
- </li>
-
- <li>
- <a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin
- for Gradle</a>
- </li>
- </ol>
- </div>
-</div>
-
-<p>
- The Android build system uses the Android Plugin for Gradle to support
- building Android applications with the <a href=
- "http://www.gradle.org/">Gradle</a> build toolkit. The plugin runs
- independent of Android Studio so the plugin and the Gradle build system can
- be updated independently of Android Studio.
-</p>
-
-<h2 id="updating-plugin">
- Updating the Android Plugin for Gradle
-</h2>
-
-<p>
- When you update Android Studio, you may receive a prompt to automatically
- update the Android Plugin for Gradle to the latest available version. You
- can choose to accept the update or manually specify a version based on
- your project's build requirements.
-</p>
-
-<p>
- You can specify the <a href=
- "{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin for
- Gradle</a> version in either the <strong>File</strong> > <strong>Project
- Structure</strong> > <strong>Project</strong> menu in Android Studio, or
- the top-level <code>build.gradle</code> file. The plugin version applies to
- all modules built in that Android Studio project. The following example sets
- the Android Plugin for Gradle to version 2.1.0 from the
- <code>build.gradle</code> file:
-</p>
-
-<pre>
-buildscript {
- ...
- dependencies {
- classpath 'com.android.tools.build:gradle:2.1.0'
- }
-}
-</pre>
-<p class="caution">
- <strong>Caution:</strong> You should not use dynamic dependencies in version
- numbers, such as <code>'com.android.tools.build:gradle:2.+'</code>. Using
- this feature can cause unexpected version updates and difficulty resolving
- version differences.
-</p>
-
-<p>
- If the specified plugin version has not been downloaded, Gradle downloads it
- the next time you build your project or click <strong>Tools</strong> >
- <strong>Android</strong> > <strong>Sync Project with Gradle Files</strong>
- from the Android Studio main menu.
-</p>
-
-<h2 id="updating-gradle">
- Updating Gradle
-</h2>
-
-<p>
- When you update Android Studio, you may receive a prompt to automatically
- update Gradle to the latest available version. You can choose to accept the
- update or manually specify a version based on your project's build
- requirements.
-</p>
-
-<p>
- You can specify the Gradle version in either the <strong>File</strong> >
- <strong>Project Structure</strong> > <strong>Project</strong> menu in
- Android Studio, or by editing the Gradle distribution reference in the
- <code>gradle/wrapper/gradle-wrapper.properties</code> file. The following
- example sets the Gradle version to 2.10 in the
- <code>gradle-wrapper.properties</code> file.
-</p>
-
-<pre>
-...
-distributionUrl = https\://services.gradle.org/distributions/gradle-2.10-all.zip
-...
-</pre>
-
-<h2 id="revisions">
- Revisions
-</h2>
-
-<p>
- For a summary of known issues in Android Plugin for Gradle, visit the
- <a class="external-link" href="http://tools.android.com/knownissues">Android
- Tools Project Site</a>.
-</p>
-
-<div class="toggle-content opened">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 2.1.0</a> <em>(April 2016)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.10 or higher.
- </li>
-
- <li>
- <a href="{@docRoot}tools/revisions/build-tools.html">Build Tools 23.0.2</a>
- or higher.
- </li>
- </ul>
- </dd>
-
- <dt>New:</dt>
- <dd>
- <ul>
- <li>Added support for the N Developer Preview, JDK 8, and <a href=
- "{@docRoot}preview/j8-jack.html">Java 8 language features</a> using the Jack
- toolchain. To find out more, read the <a href=
- "{@docRoot}preview/overview.html">N Preview guide</a>.
-
- <p class="note">
- <strong>Note:</strong> <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">Instant
- Run</a> does not currently work with Jack and will be disabled while
- using the new toolchain. You only need to use Jack if you are developing
- for the N Preview and want to use the supported Java 8 language features.
- </p>
- </li>
-
- <li>Added default support for incremental Java compilation to reduce
- compilation time during development. It does this by only recompiling
- portions of the source that have changed or need to be recompiled. To disable
- this feature, add the following code to your module-level
- <code>build.gradle</code> file:
-
-<pre>
-android {
- ...
- compileOptions {
- incremental false
- }
-}
-</pre>
- </li>
-
- <li>
- <p>
- Added support for dexing-in-process which performs dexing within the build
- process rather than in a separate, external VM processes. This not only makes
- incremental builds faster, but also speeds up full builds. The feature is
- enabled by default for projects that have set the Gradle daemon's maximum heap
- size to at least 2048 MB. You can do this by including the following in your
- project's <code>gradle.properties</code> file:
-
-<pre>
-org.gradle.jvmargs = -Xmx2048m
-</pre>
- </p>
-
- <p>
- If you have defined a value for <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html#com.android.build.gradle.internal.dsl.DexOptions:javaMaxHeapSize">
- <code>javaMaxHeapSize</code></a> in your module-level <code>build.gradle</code>
- file, you need to set <code>org.gradle.jvmargs</code> to the value of
- <code>javaMaxHeapSize</code> + 1024 MB. For example, if you have set
- <code>javaMaxHeapSize</code> to "2048m", you need to add the following to your
- project's <code>gradle.properties</code> file:
-
-<pre>
-org.gradle.jvmargs = -Xmx3072m
-</pre>
- </p>
-
- <p>
- To disable dexing-in-process, add the following code to your module-level
- <code>build.gradle</code> file:
-
-<pre>
-android {
- ...
- dexOptions {
- dexInProcess false
- }
-}
-</pre>
- </p>
- </li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 2.0.0</a> <em>(April 2016)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.10 or higher.
- </li>
-
- <li>
- <a href="{@docRoot}tools/revisions/build-tools.html">Build Tools 21.1.1</a>
- or higher.
- </li>
- </ul>
- </dd>
-
- <dt>New:</dt>
- <dd>
- <ul>
- <li>Enables <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">Instant Run</a> by
- supporting bytecode injection, and pushing code and resource updates to a
- running app on the emulator or a physical device.
- </li>
-
- <li>Added support for incremental builds, even when the app isn’t running.
- Full build times are improved by pushing incremental changes through the
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a> to the
- connected device.
- </li>
-
- <li>Added <a class="external-link" href=
- "http://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.DexOptions.html#com.android.build.gradle.internal.dsl.DexOptions:maxProcessCount">
- <code>maxProcessCount</code></a> to control how many slave dex processes can be
- spawned concurrently. The following code, in the module-level
- <code>build.gradle</code> file, sets the maximum number of concurrent processes
- to 4:
-<pre>
-android {
- ...
- dexOptions {
- maxProcessCount = 4 // this is the default value
- }
-}
-</pre>
- </li>
-
- <li>Added an experimental code shrinker to support pre-dexing and reduce re-dexing
- of dependencies, which are not supported with Proguard. This improves the build
- speed of your debug build variant. Because the experimental shrinker does not
- support optimization and obfuscation, you should enable Proguard for your
- release builds. To enable the experimental shrinker for your debug builds, add
- the following to your module-level <code>build.gradle</code> file:
-
-<pre>
-android {
- ...
- buildTypes {
- debug {
- minifyEnabled true
- useProguard false
- }
- release {
- minifyEnabled true
- useProguard true // this is a default setting
- }
- }
-}
-</pre>
- </li>
-
- <li>Added logging support and improved performance for the resource shrinker.
- The resource shrinker now logs all of its operations into a <code>resources.txt</code>
- file located in the same folder as the Proguard log files.
- </li>
- </ul>
- </dd>
-
- <dt>Changed behavior:</dt>
- <dd>
- <ul>
- <li>When <code>minSdkVersion</code> is set to 18 or higher, APK signing uses
- SHA256.
- </li>
-
- <li>DSA and ECDSA keys can now sign APK packages.
-
- <p class="note">
- <strong>Note:</strong> The <a href=
- "{@docRoot}training/articles/keystore.html">Android keystore</a> provider no
- longer supports <a href=
- "{@docRoot}about/versions/marshmallow/android-6.0-changes.html#behavior-keystore">
- DSA keys on Android 6.0</a> (API level 23) and higher.
- </p>
-
- </li>
- </ul>
- </dd>
-
- <dt>Fixed issues:</dt>
- <dd>
- <ul>
- <li>Fixed an issue that caused duplicate AAR dependencies in both
- the test and main build configurations.
- </li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.5.0</a> <em>(November 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Integrated the Data Binding Plugin into the Android Plugin for Gradle. To enable it, add
- the following code to each per-project <code>build.gradle</code> file that uses the
- plugin:</li>
-<pre>
-android {
- dataBinding {
- enabled = true
- }
-}
-</pre>
- <li>Added a new <a href="http://google.github.io/android-gradle-dsl/javadoc/1.5/" class="external-link">Transform API</a>
- to allow third-party plugins to manipulate compiled <code>.class</code> files before they’re
- converted to <code>.dex</code> files. The Transform API simplifies injecting custom class
- manipulations while offering more flexibility regarding what you can manipulate. To insert a
- transform into a build, create a new class implementing one of the <code>Transform</code>
- interfaces, and register it with <code>android.registerTransform(theTransform)</code> or
- <code>android.registerTransform(theTransform, dependencies)</code>. There’s no need to
- wire tasks together. Note the following about the Transform API:</li>
- <ul>
- <li>A transform can apply to one or more of the following: the current project, subprojects,
- and external libraries.</li>
- <li>A transform must be registered globally, which applies them to all variants.</li>
- <li>Internal code processing, through the Java Code Coverage Library (JaCoCo), ProGuard,
- and MultiDex, now uses the Transform API. However, the Java Android Compiler Kit
- (Jack) doesn’t use this API: only the <code>javac/dx</code> code path does.</li>
- <li>Gradle executes the transforms in this order: JaCoCo, third-party plugins, ProGuard.
- The execution order for third-party plugins matches the order in which the transforms are
- added by the third party plugins; third-party plugin developers can't control the execution
- order of the transforms through an API.</li>
- </ul>
- <li>Deprecated the <code>dex</code> getter from the <code>ApplicationVariant</code> class.
- You can't access the <code>Dex</code> task through the variant API anymore because it’s now
- accomplished through a transform. There's
- currently no replacement for controlling the dex process.</li>
- <li>Fixed incremental support for assets.</li>
- <li>Improved MultiDex support by making it available for test projects, and
- tests now automatically have the <code>com.android.support:multidex-instrumentation</code>
- dependency.</li>
- <li>Added the ability to properly fail a Gradle build and report the underlying error cause
- when the Gradle build invokes asynchronous tasks and there’s a failure in the worker
- process.</li>
- <li>Added support for configuring a specific Application Binary Interface (ABI) in variants
- that contain multiple ABIs.</li>
- <li>Added support for a comma-separated list of device serial numbers for the
- <code>ANDROID_SERIAL</code> environment variable when installing or running tests.</li>
- <li>Fixed an installation failure on devices running Android 5.0 (API level 20) and higher
- when the APK name contains a space.</li>
- <li>Fixed various issues related to the Android Asset Packaging Tool (AAPT) error output.</li>
- <li>Added JaCoCo incremental instrumentation support for faster incremental builds. The
- Android Plugin for Gradle now invokes the JaCoCo instrumenter directly. To force a newer
- version of the JaCoCo instrumenter, you need to add it as a build script dependency.</li>
- <li>Fixed JaCoCo support so it ignores files that aren’t classes.</li>
- <li>Added vector drawable support for generating PNGs at build time for backward-compatibility.
- Android Plugin for Gradle generates PNGs for every vector drawable found in a resource
- directory that doesn’t specify an API version or specifies an
- <code>android:minSdkVersion</code> attribute of 20 or lower in the
- <code><uses-sdk></code> element in the app manifest. You can set PNG densities by
- using the <code>generatedDensities</code> property in the <code>defaultConfig</code> or
- <code>productFlavor</code> sections of a <code>build.gradle</code> file.</li>
- <li>Added sharing of the mockable <code>android.jar</code>, which the plugin generates only
- once and uses for unit testing. Multiple modules, such as <code>app</code> and
- <code>lib</code>, now share it. Delete <code>$rootDir/build</code> to regenerate it. </li>
- <li>Changed the processing of Java resources to occur before the obfuscation tasks instead of
- during the packaging of the APK. This change allows the obfuscation tasks to have a chance
- to adapt the Java resources following packages obfuscation.</li>
- <li>Fixed an issue with using Java Native Interface (JNI) code in the experimental library
- plugin.</li>
- <li>Added the ability to set the platform version separately from the
- <code>android:compileSdkVersion</code> attribute in the experimental library
- plugin.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.3.1</a> <em>(August 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed the <a href="{@docRoot}tools/help/zipalign.html">ZipAlign</a> task to properly
- consume the output of the previous task when using a customized filename. </li>
- <li>Fixed <a href="{@docRoot}guide/topics/renderscript/compute.html">Renderscript</a>
- packaging with the <a href="{@docRoot}tools/sdk/ndk/index.html">NDK</a>. </li>
- <li>Maintained support for the <code>createDebugCoverageReport</code> build task. </li>
- <li>Fixed support for customized use of the <code>archiveBaseName</code> property
- in the <code>build.gradle</code> build> file. </li>
- <li>Fixed the <code>Invalid ResourceType</code>
- <a href="{@docRoot}tools/help/lint.html">lint</a> warning caused by parameter method
- annotation lookup when running
- <a href="{@docRoot}tools/help/lint.html">lint</a> outside of Android Studio.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.3.0</a> <em>(July 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for the <code>com.android.build.threadPoolSize</code> property to control
- the <code>Android</code> task thread pool size from the <code>gradle.properties</code> file
- or the command line. The following example sets this property to 4.
-<pre>
--Pcom.android.build.threadPoolSize=4
-</pre>
- </li>
- <li>Set the default build behavior to exclude <code>LICENSE</code> and <code>LICENSE.txt</code>
- files from APKs. To include these files in an APK, remove these files from the
- <code>packagingOptions.excludes</code> property in the <code>build.gradle</code> file.
- For example:
-<pre>
-android {
- packagingOptions.excludes = []
- }
-</pre>
- </li>
- <li>Added the <code>sourceSets</code> task to inspect the set of all available source sets. </li>
- <li>Enhanced unit test support to recognize multi-flavor and
- <a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">
- build variant</a> source folders. For example, to test an app with multi-flavors
- <code>flavor1</code> and <code>flavorA</code> with the <code>Debug</code> build type,
- the test source sets are:
- <ul>
- <li>test </li>
- <li>testFlavor1 </li>
- <li>testFlavorA </li>
- <li>testFlavor1FlavorA </li>
- <li>testFlavor1FlavorADebug </li>
- </ul>
- <p>Android tests already recognized multi-flavor source folders. </p> </li>
- <li>Improved unit test support to:</p>
- <ul>
- <li>Run <code>javac</code> on main and test sources, even if the <code>useJack</code>
- property is set to <code>true</code> in your build file. </li>
- <li>Correctly recognize dependencies for each build type. </li>
- </ul>
- </li>
- <li>Added support for specifying instrumentation test-runner arguments from the command line.
- For example:
-<pre>
-./gradlew connectedCheck \
- -Pandroid.testInstrumentationRunnerArguments.size=medium \
- -Pandroid.testInstrumentationRunnerArguments.class=TestA,TestB
-</pre>
- </li>
- <li>Added support for arbitrary additional Android Asset Packaging Tool (AAPT) parameters
- in the <code>build.gradle</code> file. For example:
-<pre>
-android {
- aaptOptions {
- additionalParameters "--custom_option", "value"
- }
-}
-</pre>
- </li>
-
- <li>Added support for a <a href="{@docRoot}tools/studio/studio-features.html#test-module">
- test APK module</a> as a separate test module, using the
- <code>targetProjectPath</code> and <code>targetVariant</code> properties to set the APK
- path and target variant.
- <p class="note"><strong>Note:</strong> A test APK module does not support product
- flavors and can only target a single variant. Also, Jacoco is not supported yet.</p>
- </li>
- <li>Added resource name validation before merging resources. </li>
- <li>When building an AAR (Android ARchive) package for library modules, do not provide an
- automatic <code>@{applicationId}</code> placeholder in the
- <a href="{@docRoot}tools/building/manifest-merge.html">manifest merger</a> settings.
- Instead, use a different placeholder, such as <code>@{libApplicationId}</code> and
- provide a value for it if you want to include application Ids in the archive library. </li>
-
- </ul>
- </dd>
- </div>
-</div>
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.2.0</a> <em>(April 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Enhanced support for running unit tests with Gradle. </li>
- <ul>
- <li>Added support to include Java-style resources in the classpath when running unit
- tests directly from Gradle.
- </li>
- <li>Added unit test dependency support for Android ARchive (AAR) artifacts.
- </li>
- <li>Added support for the <code>unitTestVariants</code> property so unit test variants
- can be manipulated using the <code>build.gradle</code> file.
- </li>
- <li>Added the <code>unitTest.all</code> code block under <code>testOptions</code> to
- configure customized tasks for unit test. The following sample code shows how to add
- unit test configuration settings using this new option:
-<pre>
-android {
- testOptions {
- unitTest.all {
- jvmArgs '-XX:MaxPermSize=256m' // Or any other gradle option.
- }
- }
-}
-</pre>
- </li>
- <li>Fixed the handling of enums and public instance fields in the packaging of the
- <code>mockable-android.jar</code> file.
- </li>
- <li>Fixed library project task dependencies so test classes recompile after changes.
- </li>
- </ul>
- <li>Added the <code>testProguardFile</code> property to apply
- <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> files when minifying a test APK.
- </li>
- <li>Added the <code>timeOut</code> property to the <code>adbOptions</code> code block
- for setting the maximum recording time for
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a> screen recording.
- </li>
- <li>Added support for 280 dpi resources.
- </li>
- <li>Improved performance during project evaluation.
- </li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.1.3</a> <em>(March 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with duplicated dependencies on a test app that triggered a ProGuard failure. </li>
- <li>Fixed Comparator implementation which did not comply with the JDK Comparator contract and
- generated a JDK 7 error.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.1.2</a> <em>(February 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Normalized path when creating a mockable JAR for unit testing. </li>
- <li>Fixed the <code>archivesBaseName</code> setting in the <code>build.gradle</code> file. </li>
- <li>Fixed the unresolved placeholder failure in manifest merger when building a library
- test application.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.1.1</a> <em>(February 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Modified build variants so only variants that package a
- <a href="{@docRoot}training/wearables/apps/index.html">Wear</a> app trigger Wear-specific
- build tasks. </li>
- <li>Changed dependency related issues to fail at build time rather than at debug time.
- This behavior allows you to run diagnostic diagnostic tasks (such as 'dependencies') to help
- resolve the conflict. </li>
- <li>Fixed the <code>android.getBootClasspath()</code> method to return a value. </li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.1.0</a> <em>(February 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 or higher.</li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added new unit test support</li>
- <ul>
- <li>Enabled
- <a href="{@docRoot}training/activity-testing/activity-unit-testing.html">unit tests</a> to
- run on the local JVM against a special version of the <code>android.jar</code> file that is
- compatible with popular mocking frameworks, for example Mockito. </li>
- <li>Added new test tasks <code>testDebug</code>, <code>testRelease</code>, and
- <code>testMyFlavorDebug</code> when using product flavors. </li>
- <li>Added new source folders recognized as unit tests: <code>src/test/java/</code>,
- <code>src/testDebug/java/</code>, <code>src/testMyFlavor/java/</code>.
- <li>Added new configurations in the <code>build.gradle</code> file for declaring test-only
- dependencies, for example, <code>testCompile 'junit:junit:4.11'</code>,
- <code>testMyFlavorCompile 'some:library:1.0'</code>.
- <p class="note"><strong>Note:</strong> Test-only dependencies are not currently compatible
- with Jack (Java Android Compiler Kit). </p>
- </li>
- <li>Added the <code>android.testOptions.unitTests.returnDefaultValues</code> option to
- control the behaviour of the mockable android.jar. </li>
- </ul>
- <li>Replaced <code>Test</code> in test task names with <code>AndroidTest</code>.
- For example, the <code>assembleDebugTest</code> task is now
- <code>assembleDebugAndroidTest</code> task. Unit test tasks still have <code>UnitTest</code>
- in the task name, for example <code>assembleDebugUnitTest</code>. </li>
- <li>Modified <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> configuration files to
- no longer apply to the test APK. If minification is enabled, ProGuard processes the test APK
- and applies only the mapping file that is generated when minifying the main APK. </li>
- <li>Updated dependency management</li>
- <ul>
- <li>Fixed issues using <code>provided</code> and <code>package</code> scopes.
- <p class="note"><strong>Note:</strong> These scopes are incompatible with AAR
- (Android ARchive) packages and will cause a build with AAR packages to fail.</p>
- </li>
- <li>Modified dependency resolution to compare the dependencies of an app under test and the
- test app. If an artifact with the same version is found for both apps, it's not included with
- the test app and is packaged only with the app under test. If an artifact with a different
- version is found for both apps, the build fails.</li>
- </ul>
-
- <li>Added support for <code>anyDpi</code>
- <a href="{@docRoot}guide/topics/resources/providing-resources.html"> resource qualifier</a>
- in resource merger. </li>
- <li>Improved evaluation and IDE sync speeds for projects with a large number of
- Android <a href="{@docRoot}sdk/installing/create-project.html#CreatingAModule"> modules</a>. </li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.0.1</a> <em>(January 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 up to 2.3.x.
- <p class="note"><strong>Note:</strong> This version of the Android Plugin for Gradle is
- not compatible with Gradle 2.4 and higher. </p>
- </li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with Gradle build failure when accessing the
- <code>extractReleaseAnnotations</code> module.
- (<a href="http://b.android.com/81638">Issue 81638</a>).</li>
- <li>Fixed issue with <code>Disable</code> passing the
- <code>--no-optimize</code> setting to the Dalvik Executable (dex) bytecode.
- (<a href="http://b.android.com/82662">Issue 82662</a>).</li>
- <li>Fixed manifest merger issues when importing libraries with a
- <code>targetSdkVersion</code> less than 16.</li>
- <li>Fixed density ordering issue when using Android Studio with JDK 8.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Plugin for Gradle, Revision 1.0.0</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Gradle 2.2.1 up to 2.3.x.
- <p class="note"><strong>Note:</strong> This version of the Android Plugin for Gradle is
- not compatible with Gradle 2.4 and higher. </p>
- </li>
- <li>Build Tools 21.1.1 or higher.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Initial plugin release.</li>
- </ul>
- </dd>
- </div>
-</div>
\ No newline at end of file
+++ /dev/null
-page.title=Revisions
-page.noplus=1
-@jd:body
-
-<p>The Android SDK is composed of individual packages that may undergo
-an update at their own schedule, so some have their own set of release notes. You can
-find information about some of the packages in this section, including the core <a
-href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools</a> and the latest <a
-href="{@docRoot}tools/revisions/platforms.html">SDK Platforms</a>. Release notes are also available
-for Android developer tools, such as
-<a href="{@docRoot}tools/revisions/studio.html">Android Studio</a> and the
-<a href="{@docRoot}tools/revisions/gradle-plugin.html">Android Plugin for Gradle</a>.
-</p>
+++ /dev/null
-page.title=SDK Platforms Release Notes
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
-
-<h2>See Also</h2>
-<ol>
- <li><a href="{@docRoot}about/versions/kitkat.html">KitKat
-Highlights and APIs</a></li>
- <li><a href="{@docRoot}about/versions/jelly-bean.html">Jelly Bean
-Highlights and APIs</a></li>
- <li><a href="{@docRoot}about/versions/android-4.0-highlights.html">Ice Cream Sandwich
-Highlights and APIs</a></li>
-</ol>
-
-</div>
-</div>
-
-
-
-<p>This document provides release information about the SDK Platform packages required
-for app development. If you want details about the features and APIs added in each Android
-version, instead read the highlights in the <a href="{@docRoot}about/index.html">About</a>
-section.</p>
-
-<p>To compile your application against a particular version of Android, you must use the
-<a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> to download and install the SDK
-Platform for that release. If you want to test your application on an emulator, you must also
-download at least one System Image for that Android version.</p>
-
-
-<p>Each platform release includes system images that support a specific processor architecture,
-such as ARM EABI, Intel x86 or MIPS. Platform releases also include a system image that contains
-Google APIs. The <a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> lists available
-platform system images under each platform version header, for example:</p>
-
-<ul>
- <li>ARM EABI v7a System Image</li>
- <li>Intel x86 Atom System Image</li>
- <li>MIPS System Image</li>
- <li>Google APIs</li>
-</ul>
-
-<p>To determine what revisions of an Android platform you have installed, refer to the
-<em>Packages</em> listing in the Android
-<a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>.</p>
-
-<p class="caution"><strong>Important:</strong> To download the most recent Android
-system components from the Android SDK Manager, you must first update the SDK Tools to the
-most recent release and restart the SDK Manager. If you do not, the latest Android system
-packages may not be available for download.</p>
-
-
-<h2 id="6.0">Android 6.0</h2>
-
-<div class="toggle-content opened">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(November 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Fixed bugs in the layout rendering library used by Android Studio.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r23 or higher is required.</li>
- <li>Android SDK Tools 24.3.4 or higher is required.</li>
- </ul>
- </div>
-
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(August 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release for Android 6.0 (API level 23). For more information, see the
- <a href="{@docRoot}preview/api-overview.html">M Preview API Overview</a>.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r23 or higher is required.</li>
- <li>Android SDK Tools 24.3.4 or higher is required.</li>
- </ul>
- </div>
-
-</div>
-
-
-<h2 id="5.1">Android 5.1</h2>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(March 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release for Android 5.1 (API level 22). For more information, see the
- <a href="{@docRoot}about/versions/android-5.1.html">Android 5.1 API Overview</a>.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r22 or higher is required.</li>
- <li>Android SDK Tools 23.0.5 or higher is required.</li>
- </ul>
- </div>
-
-</div>
-
-
-<h2 id="5.0">Android 5.0</h2>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Updated layouts in the Support Library and fixed various issues.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r21 or higher is required.</li>
- <li>Android SDK Tools 23.0.5 or higher is required.</li>
- </ul>
- </div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release for Android 5.0 (API level 21). For more information, see the
- <a href="{@docRoot}about/versions/android-5.0.html">Android 5.0 API Overview</a>.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r21 or higher is required.</li>
- <li>Android SDK Tools 23.0.5 or higher is required.</li>
- </ul>
- </div>
-
- <h3>Device Definitions</h3>
-
- <p>The platform includes the following new device definitions for use in creating
- Android Virtual Devices in the <a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a>:</p>
-
- <ul>
- <li>Nexus 6 (5.96", 1440 x 2560, Normal 560dpi screen) </li>
- <li>Nexus 9 (8.9", 2048 x 1536, X-Large xhdpi screen) </li>
- </ul>
-
-</div>
-
-
-<h2 id="4.4">Android 4.4W</h2>
-
-<div class="toggle-content open">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Updated the rendering library.</p>
-
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r20 or higher is required.</li>
- <li>Android SDK Tools 23.0 or higher is required.</li>
- </ul>
- </div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(June 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release for Android Wear.</p>
- <p>Dependencies:</p>
- <ul>
- <li>Android SDK Platform-tools r20 or higher is required.</li>
- <li>Android SDK Tools 23.0 or higher is required.</li>
- </ul>
- </div>
-
- <h3>Device Definitions</h3>
-
- <p>The platform includes the following device definitions for use in creating Android Virtual
- Devices in the <a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a>:</p>
-
- <ul>
- <li>Android Wear Round (320 x 320, hdpi)</li>
- <li>Android Wear Square (320 x 320, hdpi)</li>
- </ul>
-</div>
-
-<h2 id="4.4">Android 4.4</h2>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(December 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance release. The system version is 4.4.2. For more information, see the
- <a href="{@docRoot}about/versions/android-4.4.html">Android 4.4 API Overview</a>.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>Android SDK Platform-tools r19 or higher is required.</dd>
- <dd>Android SDK Tools 22.3 or higher is recommended.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(October 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. The system version is 4.4. For more information, see the
- <a href="{@docRoot}about/versions/android-4.4.html">Android 4.4 API Overview</a>.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>Android SDK Platform-tools r19 or higher is required.</dd>
- <dd>Android SDK Tools 22.3 or higher is recommended.</dd>
- </dl>
-
- </div>
-</div>
-
-
-
-<h3 id="gsi-4.4">Google APIs System Image</h3>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 4</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.3,
- allowing you to test your application in an emulator using the latest Google Play services.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 3</a> <em>(February 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.2.42,
- allowing you to test your application in an emulator using the latest Google Play services.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(December 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.0.33.</p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(October 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.0.30.
- </p>
-
- </div>
-</div>
-
-
-
-<h2 id="4.3">Android 4.3</h2>
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(August 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.3.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>Android SDK Platform-tools r18 or higher is required.</dd>
- <dd>Android SDK Tools 22.0.4 or higher is recommended.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. The system version is 4.3.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>Android SDK Platform-tools r18 or higher is required.</dd>
- <dd>Android SDK Tools 22.0.4 or higher is recommended.</dd>
- </dl>
-
- </div>
-</div>
-
-<h3 id="gsi-4.3">Google APIs System Image</h3>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 3</a> <em>(September 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.65.
- </p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(August 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.25.
- </p>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. This release includes
- <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.1.58.</p>
-
- </div>
-</div>
-
-
-
-
-<h2 id="4.2">Android 4.2</h2>
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(February 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.2.2.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r21 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(November 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. The system version is 4.2.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r20 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<h3>Device Definitions</h3>
-
-<p>The platform includes the following device definitions for use in creating Android Virtual
-Devices in the <a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a>:</p>
-
-<ul>
- <li>
- Nexus 7 (7.3", 800 x 1280, Large tvdpi screen)
- </li>
- <li>
- Galaxy Nexus (4.7", 720 x 1280, Normal xhdpi screen)
- </li>
- <li>
- Nexus S (4.0", 480 x 800, Normal hdpi screen)
- </li>
- <li>
- Nexus One (3.7", 480 x 720, Normal hdpi screen)
- </li>
- <li>
- 10.1" WXGA Tablet (1280 x 800, X-Large mdpi screen)
- </li>
- <li>
- 7.0" WSVGA Tablet (1024 x 600, Large mdpi screen)
- </li>
- <li>
- 5.4" FWVGA (480 x 854, Large mdpi screen)
- </li>
- <li>
- 5.1" WVGA (480 x 800, Large mdpi screen)
- </li>
- <li>
- 4.7" WXGA (1280 x 720, Normal xhdpi screen)
- </li>
- <li>
- 4.65" 720p (720 x 1280, Normal xhdpi screen)
- </li>
- <li>
- 4.0" WVGA (480 x 800, Normal hdpi screen)
- </li>
- <li>
- 3.7" WVGA (480 x 800, Normal hdpi screen)
- </li>
- <li>
- 3.7" FWVGA slider (480 x 854, Normal hdpi screen)
- </li>
- <li>
- 3.4" WQVGA (240 x 432, Normal ldpi screen)
- </li>
- <li>
- 3.3" WQVGA (240 x 400, Normal ldpi screen)
- </li>
- <li>
- 3.2" QVGA ADP2 (320 x 480, Normal mdpi screen)
- </li>
- <li>
- 3.2" HVGA slider ADP1 (320 x 480, Normal mdpi screen)
- </li>
- <li>
- 2.7" QVGA slider (240 x 320, Small ldpi screen)
- </li>
- <li>
- 2.7" QVGA (240 x 320, Small ldpi screen)
- </li>
-</ul>
-
-
-
-<h2 id="4.1">Android 4.1</h2>
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 3</a> <em>(October 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.1.2.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r20 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(July 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.1.1.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r20 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed" >
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(June 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. The system version is 4.1.0.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r20 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skins:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
- <li>
- WXGA720 (1280x720, extra-high density, normal screen)
- </li>
- <li>
- WSVGA (1024x600, medium density, large screen)
- </li>
- <li>
- WXGA800-7in (1280x800, high density, large screen) <span class="new">new</span>
- </li>
- <li>
- WXGA800 (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-<p>To test your application on an emulator that represents the <a
-href="http://play.google.com/nexus7">Nexus 7</a> tablet device, you can create an AVD with
-the new WXGA800-7in skin. For best performance, make sure to enable <a
-href="{@docRoot}tools/devices/emulator.html#accel-graphics">graphics acceleration</a> in the
-emulator configuration.</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="4.0.3">Android 4.0.3</h2>
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 3</a> <em>(March 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.0.4.</p>
- <p class="note"><strong>Note:</strong> This system image includes support for emulator
-hardware graphics acceleration when used with SDK Tools r17 or higher.
-(<a href="{@docRoot}tools/devices/emulator.html#accel-graphics">more info</a>)</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r17 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed" >
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 2</a> <em>(January 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Maintenance update. The system version is 4.0.3.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r14 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<div class="toggle-content closed" >
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Revision 1</a> <em>(December 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p>Initial release. The system version is 4.0.3.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r14 or higher is required.</dd>
- </dl>
-
- </div>
-</div>
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skins:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
- <li>
- WXGA720 (1280x720, extra-high density, normal screen)
- </li>
- <li>
- WSVGA (1024x600, medium density, large screen)
- </li>
- <li>
- WXGA (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="4.0">Android 4.0</h2>
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 4.0, Revision 2</a> <em>(December 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Maintenance update. The system version is 4.0.2.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r14 or higher is required.</dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 4.0, Revision 1</a> <em>(October 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Initial release. The system version is 4.0.1.</p>
- <dl>
- <dt>Dependencies:</dt>
- <dd>SDK Tools r14 or higher is required.</dd>
- </dl>
- </div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skins:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
- <li>
- WXGA720 (1280x720, extra-high density, normal screen) <span class="new">new</span>
- </li>
- <li>
- WSVGA (1024x600, medium density, large screen) <span class="new">new</span>
- </li>
- <li>
- WXGA (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-<p>To test your application on an emulator that represents the latest Android device, you can create
-an AVD with the new WXGA720 skin (it's an xhdpi, normal screen device). Note that the emulator
-currently doesn't support the new on-screen navigation bar for devices without hardware navigation
-buttons, so when using this skin, you must use keyboard keys <em>Home</em> for the Home button,
-<em>ESC</em> for the Back button, and <em>F2</em> or <em>Page-up</em> for the Menu button.</p>
-
-<p>However, due to performance issues in the emulator when running high-resolution screens such as
-the one for the WXGA720 skin, we recommend that you primarily use the traditional WVGA800 skin
-(hdpi, normal screen) to test your application.</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="3.2">Android 3.2</h2>
-
-
-
-<div class="toggle-content closed">
-
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 3.2, Revision 1</a> <em>(July 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
-<dl>
-<dt>Initial release. SDK Tools r12 or higher is recommended.</dt>
-</dl>
-
- </div>
-</div>
-
-
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skin:</p>
-
-<ul>
- <li>
- WXGA (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-<p>For more information about how to develop an application that displays
-and functions properly on all Android-powered devices, see <a
-href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple
-Screens</a>.</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="3.1">Android 3.1</h2>
-
-
-<div class="toggle-content closed">
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 3.1, Revision 3</a> <em>(July 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r12</a> or
-higher.</p>
-</dd>
-<dt>Notes:</dt>
-<dd>
-<p>Improvements to the platform's rendering library to support the visual layout editor in the ADT
-Eclipse plugin. This revision allows for more drawing features in ADT and fixes several
-bugs in the previous rendering library. It also unlocks several editor features that were added in
-ADT 12.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 3.1, Revision 2</a> <em>(May 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r11</a> or
-higher.</p>
-</dd>
-<dt>Notes:</dt>
-<dd>
-<p>Fixes an issue with the visual layout editor rendering library that prevented Android 3.1 from
-running in ADT.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 3.1, Revision 1</a> <em>(May 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r11</a> or
-higher.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skin:</p>
-
-<ul>
- <li>
- WXGA (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-<p>For more information about how to develop an application that displays
-and functions properly on all Android-powered devices, see <a
-href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple
-Screens</a>.</p>
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="3.0">Android 3.0</h2>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 3.0, Revision 2</a> <em>(July 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r12</a> or
-higher.</p>
-</dd>
-<dt>Notes:</dt>
-<dd>
-<p>Improvements to the platform's rendering library to support the visual layout editor in the ADT
-Eclipse plugin. This revision allows for more drawing features in ADT and fixes several
-bugs in the previous rendering library. It also unlocks several editor features that were added in
-ADT 12.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt="" />Android 3.0, Revision 1</a> <em>(February 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r10</a> or higher.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes the following emulator skin:</p>
-
-<ul>
- <li>
- WXGA (1280x800, medium density, xlarge screen)
- </li>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="2.3.4">Android 2.3.4</h2>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt="" />Android 2.3.4, Revision 1</a> <em>(May 2011)</em>
-</p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <p>Requires SDK Tools r11 or higher.</p>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes a set of emulator skins that you can use
-for modeling your application in different screen sizes and resolutions. The
-emulator skins are:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="2.3.3">Android 2.3.3</h2>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 2.3.3, Revision 2</a> <em>(July 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r12</a> or
-higher.</p>
-</dd>
-<dt>Notes:</dt>
-<dd>
-<p>Improvements to the platform's rendering library to support the visual layout editor in the ADT
-Eclipse plugin. This revision allows for more drawing features in ADT and fixes several
-bugs in the previous rendering library. It also unlocks several editor features that were added in
-ADT 12.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android 2.3.3, Revision 1</a> <em>(February 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires SDK Tools r9 or higher.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes a set of emulator skins that you can use
-for modeling your application in different screen sizes and resolutions. The
-emulator skins are:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-
-<h2 id="2.3">Android 2.3</h2>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt="" />Android 2.3, Revision 1</a> <em>(December 2010)</em>
-</p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <p>Requires SDK Tools r8 or higher.</p>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes a set of emulator skins that you can use
-for modeling your application in different screen sizes and resolutions. The
-emulator skins are:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA400 (240x400, low density, normal screen)
- </li>
- <li>
- WQVGA432 (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
-</ul>
-
-
-
-
-
-
-
-
-
-<h2 id="2.2">Android 2.2</h2>
-
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android {@sdkPlatformVersion}, Revision 3</a> <em>(July 2011)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r12</a> or
-higher.</p>
-</dd>
-<dt>Notes:</dt>
-<dd>
-<p>Improvements to the platform's rendering library to support the visual layout editor in the ADT
-Eclipse plugin. This revision allows for more drawing features in ADT and fixes several
-bugs in the previous rendering library. It also unlocks several editor features that were added in
-ADT 12.</p>
-</dd>
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed" >
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android {@sdkPlatformVersion}, Revision 2</a> <em>(July 2010)</em>
-</p>
-
-<div class="toggle-content-toggleme">
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires SDK Tools r6 or higher.</p>
-</dd>
-
-<dt>System Image:</dt>
-<dd>
-<ul>
-<li>Adds default Search Widget.</li>
-<li>Includes proper provisioning for the platform's Backup Manager. For more information about how
-to use the Backup Manager, see <a href="{@docRoot}guide/topics/data/backup.html">Data
-Backup</a>.</li>
-<li>Updates the Android 2.2 system image to FRF91.</li>
-</ul>
-</dd>
-
-</dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
-
-<p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png"
-class="toggle-content-img" alt="" />Android {@sdkPlatformVersion}, Revision 1</a> <em>(May 2010)</em></p>
-
-<div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>Requires SDK Tools r6 or higher.</p>
-</dd>
-
-<dt>Tools:</dt>
-<dd>
-<p>Adds support for building with Android library projects. See <a href="{@docRoot}tools/sdk/tools-notes.html">SDK
-Tools, r6</a> for information.</p>
-</dd>
-
-</dl>
- </div>
-</div>
-
-
-<h3>Emulator Skins</h3>
-
-<p>The downloadable platform includes a set of emulator skins that you can use
-for modeling your application in different screen sizes and resolutions. The
-emulator skins are:</p>
-
-<ul>
- <li>
- QVGA (240x320, low density, small screen)
- </li>
- <li>
- WQVGA (240x400, low density, normal screen)
- </li>
- <li>
- FWQVGA (240x432, low density, normal screen)
- </li>
- <li>
- HVGA (320x480, medium density, normal screen)
- </li>
- <li>
- WVGA800 (480x800, high density, normal screen)
- </li>
- <li>
- WVGA854 (480x854 high density, normal screen)
- </li>
-</ul>
+++ /dev/null
-page.title=Android Studio Release Notes
-
-@jd:body
-
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/index.html">Installing Android Studio</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<p>Android Studio is the official IDE for Android development, and with a single download includes
-everything you need to begin developing Android apps:</p>
-
-<ul>
- <li>IntelliJ IDE + Android Studio plugin
- </li>
-
- <li>Android SDK Tools
- </li>
-
- <li>Android Platform-tools
- </li>
-
- <li>A version of the Android platform
- </li>
-
- <li>Android Emulator with an Android system image including Google Play
- Services
- </li>
-</ul>
-
-<p>For an introduction to Android Studio, read the
-<a href="{@docRoot}tools/studio/index.html">Android Studio</a> guide.</p>
-
-<p>Periodic updates are pushed to Android Studio without requiring you to update your Android
-project. To manually check for updates, select <strong>Help > Check for update</strong> (on Mac,
-select <strong>Android Studio > Check for updates</strong>).</p>
-
-
-<h2 id="Revisions">Revisions</h2>
-
-<p>The sections below provide notes about successive releases of
-Android Studio, as denoted by revision number. </p>
-
-
-<div class="toggle-content open">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png" class="toggle-content-img"
- alt=""/>Android Studio v2.1.0</a> <em>(April 2016)</em>
- </p>
- <div class="toggle-content-toggleme">
-
-<p>The primary changes in this update provide support for development with the
-<a href="{@docRoot}preview/index.html">Android N Preview</a>.</p>
-
-<p>The Android N platform adds support for <a
-href="{@docRoot}preview/j8-jack.html">Java 8 language features</a>, which
-require a new experimental compiler called Jack. The latest version of Jack is
-currently supported only in Android Studio 2.1. So if you want to use Java 8
-language features, you need to use Android Studio 2.1 to build your app.</p>
-
-<p class="note"><strong>Note:</strong> <a
-href="{@docRoot}tools/building/building-studio.html#instant-run">Instant Run</a>
-is disabled when you enable the Jack compiler because they currently are not
-compatible.</p>
-
-<p>Although Android Studio 2.1 is now stable, the Jack compiler is still
-experimental and you must enable it with <a
-href="{@docRoot}preview/j8-jack.html#configuration">the <code>jackOptions</code>
-property</a> in your <code>build.gradle</code> file.</p>
-
-<p>Other than the changes to support the N Preview, Android Studio 2.1
-includes minor bug fixes and the following enhancements:</p>
- <ul>
- <li>The Java-aware C++ debugger is now enabled by default when you're
-using an N device or emulator and select <strong>Native</strong> debugger mode
-(in the <strong>Debugger</strong> tab for your run/debug configuration).</li>
- </ul>
- <p>For other build enhancements, including incremental Java compilation
- and dexing-in-process, update your <a
-href="{@docRoot}tools/revisions/gradle-plugin.html">Android Plugin for
-Gradle</a> to version 2.1.0.</p>
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v2.0.0</a> <em>(April 2016)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <p class="note">
- <strong>Note:</strong> If you are developing for the N Developer Preview, you
- should use Android Studio 2.1 Preview. Android Studio 2.0 does not support
- all the features required to target the N Preview. To learn more, read about
- how to properly <a href="{@docRoot}preview/setup-sdk.html">set up your
- developer environment</a> for the N Preview.
- </p>
-
- <p>
- <strong>Instant Run</strong>:
- </p>
-
- <ul>
- <li>Android Studio now deploys clean builds faster than ever before.
- Additionally, pushing incremental code changes to the emulator or a physical
- device is now almost instantaneous. Review your updates without redeploying a
- new debug build or, in many cases, without restarting the app.
- </li>
-
- <li>Instant Run supports pushing the following changes to a running app:
- <ul>
- <li>Changes to the implementation of an existing instance method or
- static method
- </li>
-
- <li>Changes to an existing app resource
- </li>
-
- <li>Changes to structural code, such as a method signature or a static
- field (requires a target device running API level 21 or higher).
- </li>
- </ul>
- </li>
-
- <li>Read the documentation to learn more <a href=
- "{@docRoot}tools/building/building-studio.html#instant-run">about Instant
- Run</a>.
- <p class="note">
- <strong>Note:</strong> Instant Run is supported only when you deploy the
- debug build variant, use <a href=
- "{@docRoot}tools/revisions/gradle-plugin.html#revisions">Android Plugin for
- Gradle version 2.0.0</a> or higher, and configure your app's module-level
- <code>build.gradle</code> file for <code>minSdkVersion 15</code> or higher.
- For the best performance, configure your app for <code>minSdkVersion
- 21</code> or higher.
- </p>
- </li>
- </ul>
-
-<p><strong>New additions to Lint:</strong></p>
- <ul>
- <li>Inspection of {@code switch} statements using {@link
- android.support.annotation.IntDef @IntDef} annotated integers to make sure
- all constants are handled. To quickly add any missing statements, use the the
- intention action drop-down menu and select <b>Add Missing @IntDef
- Constants</b>.
- </li>
-
- <li>Flags for incorrect attempts to use string interpolation to insert
- version numbers in the {@code build.gradle} file.
- </li>
-
- <li>Flags for anonymous classes that extend the {@link android.app.Fragment
- Fragment} class.
- </li>
-
- <li>Flags for native code in unsafe locations, such as the {@code res/} and {@code
- asset/} folders. This flag encourages storing native code in the {@code libs/}
- folder, which is then securely packaged into the application’s {@code
- data/app-lib/} folder at install time. <a class="external-link" href=
- "https://android-review.googlesource.com/#/c/169950/">AOSP: #169950</a>
- </li>
-
- <li>Flags for unsafe calls to {@link java.lang.Runtime#load(java.lang.String)
- Runtime.load()} and {@link java.lang.System#load(java.lang.String)
- System.load()} calls. <a class="external-link" href=
- "https://android-review.googlesource.com/#/c/179980/">AOSP: #179980</a>
- </li>
-
- <li>Find and remove any unused resources by selecting <b>Refactor > Remove
- Unused Resources</b> from the menu bar. Unused resource detection now
- supports resources only referenced by unused resources, references in raw
- files such as {@code .html} image references, and {@code tools:keep} and
- {@code tools:discard} attributes used by the Gradle resource shrinker, while
- considering inactive source sets (such as resources used in other build
- flavors) and properly handling static field imports.
- </li>
-
- <li>Checks that implicit API references are supported on all platforms
- targeted by {@code minSdkVersion}.
- </li>
-
- <li>Flags improper usage of {@link android.support.v7.widget.RecyclerView}
- and {@link android.os.Parcelable}.
- </li>
-
- <li>{@link android.support.annotation.IntDef @IntDef}, {@link
- android.support.annotation.IntRange @IntRange}, and {@link
- android.support.annotation.Size @Size} inspections are now also checked for
- {@code int} arrays and varargs.
- </li>
- </ul>
-
-<p><strong>Additional Improvements</strong>:</p>
- <ul>
- <li>Optimized for Android Emulator 2.0, which is faster than ever before,
- supports a wider range of virtual devices, and features a drastically
- improved UI. To learn more about the new emulator, read the <a href=
- "{@docRoot}tools/sdk/tools-notes.html#notes">SDK Tools release notes</a>.
- </li>
-
- <li>Improvements to the <a href=
- "{@docRoot}tools/devices/managing-avds.html">Android Virtual Device
- Manager</a>:
- <ul>
- <li>System images are now categorized under the following tabs:
- <em>Recommended</em>, <em>x86</em>, and <em>Other</em>.
- </li>
-
- <li>Under advanced settings, you can enable multi-core support and
- specify the number of cores the emulator can use.
- </li>
-
- <li>Under advanced settings, you can determine how graphics are rendered
- on the emulator by selecting one of the following options:
- <ul>
- <li>
- <strong>Hardware:</strong> use you computer's graphics card for
- faster rendering.
- </li>
-
- <li>
- <strong>Software:</strong> use software-based rendering.
- </li>
-
- <li>
- <strong>Auto:</strong> let the emulator decide the best option. This
- is the default setting.
- </li>
- </ul>
- </li>
- </ul>
- </li>
-
- <li>Improved AAPT packaging times by specifying deploy target before the app
- is built. This allows Android Studio to efficiently package only the
- resources required by the specified device.
- </li>
-
- <li>Added Cloud Test Lab integration to provide on-demand app testing with
- the convenience and scalability of a cloud service. Learn more about how you
- can <a href="{@docRoot}training/testing/start/index.html#run-ctl">use Cloud
- Test Lab with Android Studio</a>.
- </li>
-
- <li>Added a preview of the new <a class="external-link" href=
- "//tools.android.com/tech-docs/gpu-profiler">GPU Debugger</a>. For graphics
- intensive applications, you can now visually step through your OpenGL ES code
- to optimize your app or game.
- </li>
-
- <li>Added Google App Indexing Test. Add support for URLs, app
- indexing, and search functionality to your apps to help drive more
- traffic to your app, discover which app content is used most, and attract
- new users. Test and validate URLs in your app all within Android
- Studio. See <a href=
- "{@docRoot}tools/help/app-link-indexing.html">Supporting URLs and App Indexing in Android Studio</a>.
- </li>
-
- <li>Upgrades from the latest IntelliJ 15 release, including improved code
- analysis and performance. See <a class="external-link" href=
- "https://www.jetbrains.com/idea/whatsnew">What's New in IntelliJ</a> for a
- complete description of the new features and enhancements.
- </li>
-
- <li>XML editor auto-complete now adds quotations marks when completing
- attributes. To check if this option is enabled, open the <b>Setting</b> or
- <b>Preferences</b> dialogue, navigate to <b>Editor > General > Smart
- Keys</b>, and check the box next to <b>Add quotes for attribute value on
- attribute completion</b>. <a class="external-link" href=
- "//b.android.com/195113">Issue: 195113</a>
- </li>
-
- <li>The XML editor now supports code completion for <a href=
- "{@docRoot}tools/data-binding/guide.html#layout_details">data binding</a>
- expressions.
- </li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.5.1</a> <em>(December 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Fixed a rendering failure issue in the Layout Editor.
- <a href="http://b.android.com/194612">Issue: 194612</a> </li>
- <li>Added the ability to vary <code>description</code> manifest attributes by configuration.
- <a href="http://b.android.com/194705">Issue: 194705</a>
- </li>
- <li>Improved the contrast of the Android Studio Darcula appearance theme in Vector Asset Studio.
- <a href="http://b.android.com/191819">Issue: 191819</a>
- </li>
- <li>Added <em>Help</em> button support to Vector Asset Studio.
- </li>
- <li>Added support for the <code>%</code> operator for data binding. <a href="http://b.android.com/194045">Issue: 194045</a>
- </li>
- <li>Fixed a case where launching an app for debugging resulted in the debugger connecting to the
- wrong device. <a href="http://b.android.com/195167">Issue: 195167</a>
- </li>
- <li>Fixed a null pointer exception that could occur when attempting to run an app in
- certain scenarios.
- </li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.5.0</a> <em>(November 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Added new Memory Monitor analysis abilities to Android Monitor. When you view an HPROF file
- captured from this monitor, the display is now more helpful so you can more quickly locate
- problems, such as memory leaks. To use this monitor, click <strong>Android Monitor</strong> at
- the bottom of the main window. In Android Monitor, click the <strong>Memory</strong> tab. While
- the monitor is running, click the <strong>Dump Java Heap</strong> icon, and then click
- <strong>Captures</strong> in the main window and double-click the file to view it. Click
- <em>Capture Analysis</em> on the right. (The
- Android Device Monitor can't be running at the same time as Android Monitor.)</li>
- <li>Added new deep link and app link support. The Code Editor can automatically create an
- intent filter for deep linking in the <code>AndroidManifest.xml</code> file. It can also
- generate code to help you integrate with the
- <a href="http://developers.google.com/app-indexing/android/publish" class="external-link">App Indexing API</a>
- in an activity in a Java file. A deep link testing feature
- helps you verify that a specified deep link can launch an app. In the <strong>General</strong>
- tab of the <em>Run/Debug Configurations</em> dialog, you can specify deep link launch
- options. You can also test App Indexing API calls in an activity by using the Android Monitor
- <strong>logcat</strong> display. The Android <code>lint</code> tool now has warnings for
- certain issues involving deep links and the App Indexing API.
- </li>
- <li>Added the ability to use short names when code-completing custom views in the Code Editor.
- </li>
- <li>Added support for more {@link android.graphics.drawable.VectorDrawable} elements to
- <a href="{@docRoot}tools/help/vector-asset-studio.html">Vector Asset Studio</a>
- for backward-compatibility. Vector Asset Studio can use these elements to convert vector
- drawables into PNG raster images to use with Android 4.4 (API level 20) and lower.
- </li>
- <li>Added new <code>lint</code> checks for Android TV and Android Auto to give you
- immediate, actionable feedback in Android Studio, along with several quick fixes. For example,
- for Android TV, it can report and provide a quick fix for permissions, unsupported hardware,
- <code>uses-feature</code> element, and missing banner issues. For Android Auto, it can
- validate the correct usage in the descriptor file referred from your
- <code>AndroidManifest.xml</code> file, report if there isn't an intent filter for the
- <code>MediaBrowserService</code> class, and identify certain voice actions issues.
- </li>
- <li>Added new <code>lint</code> checks for insecure broadcast receivers,
- <code>SSLCertificateSocketFactory</code> and <code>HostnameVerifier</code> class uses, and
- <code>File.setReadable()</code> and <code>File.setWritable()</code> calls. It also detects
- invalid manifest resource lookups, especially for resources that vary by configuration.
- </li>
- <li>Fixed a number of stability issues.
- </li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.4.1</a> <em>(October 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Fixed a Gradle model caching issue that could lead to excessive Gradle syncing when the IDE
- was restarted.
- </li>
- <li>Fixed a native debugging deadlock issue.
- </li>
- <li>Fixed an issue blocking users of the Subversion 1.9 version control system.
- </li>
- <li>Fixed a <em>Device Chooser</em> dialog problem where after connecting a device that was
- unauthorized you could no longer select the emulator. <a href="http://b.android.com/189658">Issue: 189658</a>
- </li>
- <li>Fixed incorrect translation error reporting for locales that have a region qualifier and a
- translation in the region (but not in the base locale). <a href="http://b.android.com/188577">Issue: 188577</a>
- </li>
- <li>Fixed a deadlock issue in the Theme Editor related to its interaction with the Layout
- Editor. <a href="http://b.android.com/188070">Issue: 188070</a>
- </li>
- <li>Fixed a Theme Editor reload and edit conflict causing attributes to not properly update.
- <a href="http://b.android.com/187726">Issue: 187726</a>
- </li>
- <li>Improved Theme Editor performance.
- </li>
- <li>Fixed an issue where the <code>android:required</code> attribute was ignored in the manifest.
- <a href="http://b.android.com/187665">Issue: 187665</a>
- </li>
- </ul>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.4.0</a> <em>(September 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Added the <a href="{@docRoot}tools/help/vector-asset-studio.html">Vector Asset Studio</a>
- tool for importing vector graphics, such as material icons
- and SVG files. To use this tool, in the Android view of the Project window, right-click the
- <strong>res</strong> folder and select <strong>New</strong> > <strong>Vector Asset</strong>.
- </li>
- <li>Added new Android Monitor functions, GPU and Network. To use these monitors, click
- <strong>Android Monitor</strong> at the bottom of the main window. The Android Device Monitor
- can't be running at the same time as Android Monitor.
- </li>
- <li>Added an early preview of the new Theme Editor. To use this feature, select
- <strong>Tools</strong> > <strong>Android</strong> > <strong>Theme Editor</strong>.
- </li>
- <li>Updated the Android templates for the Design Support Library. Templates now include support
- for the Material Design specification, as well as the <code>appcompat</code> Support Library
- for backwards compatibility.
- </li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.3.2</a> <em>(August 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Added support for Android 6.0 (API level 23), including new icons and AVD Manager
- support for creating devices with new screen densities.</li>
- <li>Fixed an exception that was occuring during update checks.
- <a href="http://b.android.com/183068">Issue: 183068</a></li>
- <li>Fixed problem where unresolved view coordinates could cause the layout editor to crash.
- <a href="http://b.android.com/178690">Issue: 178690</a></li>
- <li>Fixed issue with invalid resource type warnings.
- <a href="http://b.android.com/182433">Issue: 182433</a></li>
- <li>Fixed lint check that was incorrectly flagging resources as private.
- <a href="http://b.android.com/183120">Issue: 183120</a></li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.3.1</a> <em>(August 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Fixed support for creating an Android Wear Android Virtual Device (AVD) on Windows. </li>
- <li>Updated the <em>Project Wizard</em> to use the entered project name. </li>
- <li>Added support to allow the Android SDK to be stored in a read-only directory. </li>
- <li>Updated Android Plugin for Gradle version to 1.3.0. </li>
- <li>Fixed issues with launching a debug session from the Android Debug Bridge (adb) Unix
- shell. </li>
- <li>Fixed the Java package renaming message to show the correct package name. </li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.3.0</a> <em>(July 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Added options to enable
- <a href="{@docRoot}tools/studio/studio-features.html#dev-services">developer services</a>,
- such as <a href="https://developers.google.com/admob/">AdMob</a> and
- <a href="{@docRoot}distribute/analyze/start.html">Analytics</a>, in your app from within
- Android Studio. </li>
- <li>Added additional <a href="{@docRoot}tools/debugging/annotations.html">annotations</a>,
- such as <code>@RequiresPermission</code>, <code>@CheckResults</code>, and
- <code>@MainThread</code>. </li>
- <li>Added the capability to generate Java heap dumps and analyze thread allocations from the
- <a href="{@docRoot}tools/studio/index.html#mem-cpu">Memory Monitor</a>. You can also
- convert Android-specific HPROF binary format files to standard HPROF format from within
- Android Studio. </li>
- <li>Integrated the <a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>
- into Android Studio to simplify package and tools access and provide update notifications.
- <p class="note"><strong>Note:</strong> The standalone SDK Manager is still available from
- the command line, but is recommended for use only with standalone SDK
- installations. </p> </li>
- <li>Added the <code>finger</code> command in the emulator console to simulate
- <a href="{@docRoot}tools/studio/studio-features.html#finger-print">fingerprint</a>
- authentication. </li>
- <li>Added a <code><public></code> resource declaration to designate library
- resources as
- <a href="{@docRoot}tools/studio/studio-features.html#private-res">public and private</a>
- resources.
- <p class="note"><strong>Note:</strong> Requires
- <a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin for Gradle</a>
- version 1.3 or higher. </p> </li>
- <li>Added <a href="{@docRoot}tools/data-binding/guide.html">data binding</a> support to
- create declarative layouts that bind your application logic to layout elements. </li>
- <li>Added support for a separate
- <a href="{@docRoot}tools/studio/studio-features.html#test-module">test APK module</a>
- to build test APKs in Android Studio. </li>
- <li>Updated the <a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a> with HAXM
- optimizations and improved notifications. </li>
- <li>Added 64-bit ARM and MIPS emulator support for
- <a class="external-link" href="http://wiki.qemu.org/Main_Page">QEMU</a> 2.1. </li>
- <li>Simplified the resolution of <a href="{@docRoot}tools/help/lint.html">lint</a> warnings
- by adding quick fixes, such as the automatic generation of
- <a href="{@docRoot}reference/android/os/Parcelable.html">Parcelable</a>
- implementation.</li>
- <li>Added <a href="{@docRoot}sdk/installing/studio-tips.html#live-templates">live template</a>
- support for quick insertion of code snippets. </li>
- </ul>
- </div>
-</div>
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.2.2</a> <em>(June 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Fixed build issues that were blocking builds from completing. </li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.2.1</a> <em>(May 2015)</em>
- </p>
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Fixed minor performance and feature issues. </li>
- </ul>
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.2.0</a> <em>(April 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Fixes and enhancements:</p>
- <ul>
- <li>Updated the Android runtime window to include the
- <a href="{@docRoot}tools/studio/index.html#mem-cpu">Memory Monitor</a> tool
- and added a tab for CPU performance monitoring.</li>
- <li>Added a <em>Captures</em> tab in the left margin to display the captured memory and CPU
- performance data files, such as CPU method tracking and memory heap snapshots.</li>
- <li>Expanded <a href="{@docRoot}tools/debugging/annotations.html">annotation</a>
- support with additional metadata annotations and inferred nullability. </li>
- <li>Enhanced the Translations Editor with additional support for Best Current Practice
- (BCP) 47, which uses 3-letter language and region codes.</li>
- <li>Integrated IntelliJ 14 and 14.1 features for improved code analysis and performance:</li>
- <ul>
- <li>Enhanced debugging to show inline values for variables and referring objects,
- as well as perform inline evaluation of lambda and operator expressions. </li>
- <li>Added code style detection for tab and indent sizes. </li>
- <li>Added scratch files for code experiments and prototyping without project files.</li>
- <li>Added the simultaneous insertion of opening and closing tags in HTML and XML files.</li>
- <li>Added a built-in Java class decompiler so you can look at what’s inside a library
- for which the source code is not available. </li>
- </ul>
- <p>See
- <a class="external-link" href="https://www.jetbrains.com/idea/whatsnew">What's New in IntelliJ</a>
- for a complete description of the new features and enhancements.</p>
- </li>
- <li>Added additional <a href="{@docRoot}tools/studio/index.html#project-view">Project Views</a>
- for <em>Scratches</em>, <em>Project Files</em>, <em>Problems</em>, <em>Production</em>,
- and <em>Tests</em> to enhance project management and access. </li>
- <li>Enhanced the <strong>File > Settings</strong> menu and dialogs for improved settings
- access and management. </li>
- <li>Added support for high-density displays for Windows and Linux. </li>
- <li>Added support for 280 dpi resources in the <code>res/drawable-280dpi/</code> folder.
- </ul>
- </ul>
- </div>
-</div>
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.1.0</a> <em>(February 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Various fixes and enhancements:</p>
- <ul>
- <li>Added support for the <a href="{@docRoot}design/wear/index.html">Android Wear</a> watch
- template. </li>
- <li>Modified new project and module creation to include
- <a href="{@docRoot}tools/projects/index.html#mipmap"><code>res/mipmap</code></a> folders for
- density-specific launcher icons. These <code>res/mipmap</code> folders replace the
- <a href="{@docRoot}guide/topics/resources/drawable-resource.html"><code>res/drawable</code></a>
- folders for launcher icons. </li>
- <li>Updated launcher icons to have a
- <a href="{@docRoot}design/material/index.html">Material Design</a> look and added an
- <code>xxxhdpi</code> launcher icon. </li>
- <li>Added and enhanced <a href="{@docRoot}tools/help/lint.html"><code>lint</code></a> checks
- for region and language combinations, launcher icons, resource names, and other common
- code problems.</li>
- <li>Added support for Best Current Practice (BCP) language tag 47. </li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.0.1</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Various fixes and enhancements:</p>
- <ul>
- <li>Fixed AVD Manager and <strong>device.xml</strong> file lock issue. </li>
- <li>Fixed the emulator log on Windows systems. </li>
- <li>Fixed issue with creating AVDs with Android Studio and Android SDK installed on different
- drives on Windows systems.</li>
- <li>Sets the default update channel for new downloads to <strong>Stable</strong>. If you
- installed the 1.0.0 version of Android Studio and would like stable, production-ready version
- updates, use <strong>File > Settings > Updates</strong> to change to the <strong>Stable</strong>
- update channel.
- </li>
- </ul>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v1.0</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Initial release of Android Studio.</p>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.8.14</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>See
- <a href="http://tools.android.com/recent/androidstudio0814inbetachannel">tools.android.com</a>
- for a full list of changes.</p>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.8.6</a> <em>(August 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</p>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.8.0</a> <em>(June 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p>Added support for Android Wear projects.</p>
- <p>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</p>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.5.2</a> <em>(May 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.4.6</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.4.2</a> <em>(Jan 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.3.2</a> <em>(Oct 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>See <a href="http://tools.android.com/recent">tools.android.com</a> for a full list of changes.</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.2.x</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>Merged in the latest IntelliJ codebase changes. Includes fixes for issues reported by Studio users such as tweaks to Linux font sizes and font rendering.</li>
- <li>Android Gradle plug-in updated to 0.5.0.
- <p class="caution"><strong>Caution:</strong> This new version is not backwards compatible.
- When opening a project that uses an older version of the plug-in, Studio will show an error
- stating <strong>Gradle <project_name> project refresh failed.</strong></p>
- <p>The updated Gradle plug-in includes the following changes:</p>
- <ul>
- <li>Fixed IDE model to contain the output file even if it's customized through the DSL. Also
- fixed the DSL to get/set the output file on the variant object so that it's not necessary to
- use <code>variant.packageApplication or variant.zipAlign</code></li>
- <li>Fixed dependency resolution so that we resolved the combination of (default config,
- build types, flavor(s)) together instead of separately.</li>
- <li>Fixed dependency for tests of library project to properly include all the dependencies
- of the library itself.</li>
- <li>Fixed case where two dependencies have the same leaf name.</li>
- <li>Fixed issue where Proguard rules file cannot be applied on flavors.</li>
- </ul>
- <p>All Gradle plugin release notes are available are here: <a href=
- "http://tools.android.com/tech-docs/new-build-system"
- >http://tools.android.com/tech-docs/new-build-system</a>.</p>
- </li>
- <li>Gradle errors from aapt no longer point to merged output files in the build/ folder, they
- point back to the real source locations.</li>
- <li>Parallel Builds. It's now possible to use Gradle's parallel builds. Please be aware that
- parallel builds are in "incubation" (see <a
- href="http://www.gradle.org/docs/current/userguide/gradle_command_line.html">Gradle's
- documentation</a>.) This feature is off by default. To enable it, go to
- <strong>Preferences</strong> > <strong>Compiler</strong> and check the box <em>Compile
- independent modules in parallel</em>.</li>
- <li>Further work on the new resource repository used for layout rendering, resource
- folding in the editor, and more:
- <ul>
- <li>Basic support for .aar library dependencies (e.g. using a library without a local copy of
- the sources). Still not working for resource XML validation and navigation in source editors.
- </li>
- <li>Cycle detection in resource references.</li>
- <li>Quick Documentation (F1), which can show all translations of the string under the caret,
- will now also show all resource overlays from the various Gradle flavors and build types, as
- well as libraries. They are listed in reverse resource overlay order, with strikethrough on
- the versions of the string that are masked.</li>
- <li>Fixes to handle updating the merged resources when the set of module dependencies
- change.</li>
- <li>XML rendering fixes to properly handle character entity declarations and XML and unicode
- escapes.</li>
- </ul>
- <li>Save screenshot support for the layout preview and layout editor windows.</li>
- <li>Template bug fixes.</li>
- <li>Lint bug fixes.</li>
- <li>Various fixes for crash reports. Thank you, and keep filing crash reports!</li>
- </ul>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>Android Studio v0.1.x</a> <em>(May 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <ul>
- <li>Various bug fixes, including a fix for a common Windows installation issue.
- </ul>
- </div>
-</div>
-
-<p> </p>
-
-
-<h2 id="Troubleshooting">Troubleshooting</h2>
-
-<p>If you encounter problems in Android Studio, look at the following page
-for possible resolutions to known issues: <a href="http://tools.android.com/knownissues"
->http://tools.android.com/knownissues</a>.</p>
-
-
-
-</div><!-- end main content -->
-
-
-
-
-</div><!-- end relative position wrapper -->
-
-
-
+++ /dev/null
-page.title=ADT Plugin Release Notes
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/installing-adt.html">Installing the Eclipse
-Plugin</a></li>
- </ol>
-
-</div>
-</div>
-
-<p>Android Development Tools (ADT) is a plugin for the Eclipse IDE
-that extends the capabilities of Eclipse to let you quickly set up new Android
-projects, create an application UI, add packages based on the Android
-Framework API, debug your applications using the Android SDK tools, and even
-export signed (or unsigned) {@code .apk} files in order to distribute your application.</p>
-
-<p class="note"><strong>Note:</strong>
-If you have been using Eclipse with ADT, be aware that <a
-href="{@docRoot}tools/studio/index.html">Android Studio</a> is now the official IDE
-for Android, so you should migrate to Android Studio to receive all the
-latest IDE updates. For help moving projects,
-see <a href="/sdk/installing/migrate.html">Migrating to Android
-Studio</a>.</p>
-
-<p>Note that
-before you can install or use ADT, you must have compatible versions of both the
-Eclipse IDE and the Android SDK installed. For details, make sure to read <a
-href="{@docRoot}sdk/installing/installing-adt.html">Installing the Eclipse
-Plugin</a>. </p>
-
-
-<p>For information about the features provided by the ADT plugin, such as code
-editor features, SDK tool integration, and the graphical layout editor (for drag-and-drop layout
-editing), see the <a href="{@docRoot}tools/help/adt.html">Android Developer Tools</a>
-document.</p>
-
-
-<h2 id="notes">Revisions</h2>
-
-<p>The sections below provide notes about successive releases of
-the ADT Plugin, as denoted by revision number. </p>
-
-<p>For a summary of all known issues in ADT, see <a
-href="http://tools.android.com/knownissues">http://tools.android.com/knownissues</a>.</p>
-
-
-<div class="toggle-content opened">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_up.png" class="toggle-content-img"
- alt=""/>ADT 23.0.7</a> <em>(August 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r24.1.2</a>.
- If you haven't already installed SDK Tools r24.1.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issues with the rendering library for the visual layout editor.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 23.0.6</a> <em>(March 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r24.1.2</a>.
- If you haven't already installed SDK Tools r24.1.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issues with the rendering library for the visual layout editor.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 23.0.4</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.4</a>.
- If you haven't already installed SDK Tools r23.0.4 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed duplicate devices in AVD for Wear and TV.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 23.0.3</a> <em>(August 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.2</a>.
- If you haven't already installed SDK Tools r23.0.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed an issue where ADT displayed a <code>NullPointerException</code> warning dialog
- when a valid SDK was not configured. (<a href="http://b.android.com/73313">Issue
- 73313</a>)</li>
- <li>Fixed a minor issue with RenderScript support.</li>
- <li>Disabled APK compression.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 23.0.2</a> <em>(July 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.2</a>.
- If you haven't already installed SDK Tools r23.0.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>ADT Bundle shows the Java perspective by default.</li>
- <li>ADT Bundle 23.0.0 and prior versions would not allow updating the ADT plugins
- due to conflicting dependencies. This version fixes that bug and should allow
- updating to future versions of the ADT plugins.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 23.0.0</a> <em>(June 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 7 or higher is required if you are targeting Android 5.0 and higher.</li>
- <li>Java 1.6 or higher is required if you are targeting other releases.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.0</a>.
- If you haven't already installed SDK Tools r23.0.0 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added the Android Wear tools and system images.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.6.3</a> <em>(April 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.6.3</a>.
- If you haven't already installed SDK Tools r22.6.3 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the AVD manager allowed creating Android Wear virtual devices
- with a target API Level lower than 19.</li>
- <li>Fixed the description of Android Wear system images in the SDK Manager.</li>
- </ul>
- </dd>
-
- <dt>Known Issues:</dt>
- <dd>
- <p>When you create an Android Wear virtual device in the AVD manager, a target API Level
- lower than 19 may be selected by default. Make sure you select the target API Level 19
- when creating Android Wear virtual devices.</p>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.6.2</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.6.2</a>.
- If you haven't already installed SDK Tools r22.6.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li><p>Changed the URL for the Android Developer Tools update site to require HTTPS.</p>
- <p class="note"><strong>Note:</strong> If you are
- <a href="{@docRoot}sdk/installing/installing-adt.html">updating ADT</a>, make sure
- you use HTTPS in the URL for the Android Developer Tools update site.</p>
- </li>
- <li>Fixed a problem where Eclipse was non-responsive for a few seconds after opening
- an XML file. (<a href="http://b.android.com/67084">Issue 67084</a>)</li>
- <li>Fixed a problem where the SDK Manager threw a <code>NullPointerException</code> after
- removing a virtual device that was created using the Android Wear
- system image. (<a href="http://b.android.com/67588">Issue 67588</a>)</li>
- <li>Fixed a problem where the layout preview for large screens in Eclipse showed the
- resources from the <code>drawable-*</code> directories instead of those from the
- <code>drawable-large-*</code> directories.</li>
- <li>Fixed a problem with Nexus 5 Android virtual devices created from the command line
- where the SD card file system was read-only.</li>
- </ul>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.6.1</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.6.1</a>.
- If you haven't already installed SDK Tools r22.6.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the Android Virtual Device Manager could not create new
- virtual devices. (<a href="http://b.android.com/66661">Issue 66661</a>)</li>
- <li><p>Fixed a problem with virtual devices created using ADT 22.3 or earlier.</p>
- <p>If you created an Android Virtual Device using ADT 22.3 or earlier, the
- AVD may be listed as <em>broken</em> in the AVD Manager in 22.6.1. To fix
- this problem, select the virtual device on the AVD Manager and click
- <strong>Repair</strong>.</p>
- </li>
- <li>Fixed a problem with the command line tools when creating virtual devices.
- (<a href="http://b.android.com/66740">Issue 66740</a>)</li>
- <li>Fixed a problem with the command line <code>lint</code> script.</li>
- </ul>
- </dd>
-
- <dt>Known Issues:</dt>
- <dd>
- <p>When you create an Android virtual device using the Nexus 5 device definition,
- you must enable the <em>Use Host GPU</em> option, otherwise the virtual device
- will not start.</p>
- </dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.6.0</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.6</a>.
- If you haven't already installed SDK Tools r22.6 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li><p>Added support for Java 7 language features like multi-catch, try-with-resources,
- and the diamond operator. These features require version 19 or higher
- of the Build Tools. Try-with-resources requires <code>minSdkVersion</code>
- 19; the rest of the new language features require
- <code>minSdkVersion</code> 8 or higher.</p>
- <p>To use the new language features after installing ADT 22.6.0, ensure
- that you run Eclipse on JDK 7 and change your application project settings
- to use JDK 7.</p>
- </li>
- <li>Added new lint checks:
- <ul>
- <li>Security:
- <ul>
- <li>Look for code potentially affected by a <code>SecureRandom</code>
- vulnerability.</li>
- <li>Check that calls to <code>checkPermission</code> use the return
- value.</li>
- </ul>
- </li>
- <li>Check that production builds do not use mock location providers.</li>
- </ul>
- </li>
- <li>Updated the New Project templates to include the
- <a href="{@docRoot}tools/support-library/features.html#v7-appcompat">
- v7 appcompat Support Library</a>.</li>
- <li>Updated the Android tools libraries to include the rendering sandbox,
- improvements for converting resource XML string declarations to layout
- strings, and other updates.</li>
- <li>Improved the Gradle export wizard. Note that the new importer in Android
- Studio is the preferred way to migrate existing projects to Gradle.</li>
- <li>Fixed a deadlock during startup.</li>
- <li>Fixed an issue with RenderScript support. Using RenderScript support mode
- now requires version 19.0.3 of the Build Tools.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.3.0</a> <em>(October 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.3</a>.
- If you haven't already installed SDK Tools r22.3 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android 4.4 (API level 19).</li>
- <li>Fixed problem with parsing view hierarchies containing classes in the java.*
- name space.</li>
- <li>Fixed problem importing Android projects that have the same name as an existing
- project.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.2.1</a> <em>(September 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.2.1</a>.
- If you haven't already installed SDK Tools r22.2.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed problem with templates that causes the new project wizard to hang.
- (<a href="http://b.android.com/60149">Issue 60149</a>)</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.2</a> <em>(September 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.2</a>.
- If you haven't already installed SDK Tools r22.2 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Updated build tools to allow use of RenderScript on older versions of Android
- using new features in the
- <a href="{@docRoot}tools/support-library/features.html#v8">Support Library</a>.</li>
- <li>Reverted signing changes that sometimes trigger a signing verification problem on older
- platforms.</li>
- <li>Fixed problem with gradle export function for the Windows platform.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.0.5</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.0.5</a>.
- If you haven't already installed SDK Tools r22.0.5 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed RenderScript compilation issue for Windows platforms.</li>
- <li>Updated <a href="{@docRoot}tools/help/systrace.html">Systrace</a> report generation
- in the Monitor and DDMS perspectives.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.0.4</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.0.4</a>.
- If you haven't already installed SDK Tools r22.0.4 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed problem with compiling RenderScript code.</li>
- <li>Improved Gradle export with better workflow and error reporting.</li>
- <li>Improved Gradle multi-module export feature.</li>
- <li>Updated build logic to force exporting of the classpath containers unless you are using
- the Maven plugin.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.0.1</a> <em>(May 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.0.1</a>.
- If you haven't already installed SDK Tools r22.0.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with Lint ServiceCast check and fully qualified class names.
- (<a href="http://code.google.com/p/android/issues/detail?id=55403">Issue 55403</a>)</li>
- <li>Fixed crash issue with Lint ArraySizeDetector check.
- (<a href="http://code.google.com/p/android/issues/detail?id=54887">Issue 54887</a>)</li>
- <li>Fixed problem with the Gradle export feature.</li>
- <li>Fixed version check issue for the ADT Plugin.</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 22.0.0</a> <em>(May 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22</a>.
- If you haven't already installed SDK Tools r22 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Updated tools to allow libraries to share the same package name as the applications
- that use them.</li>
- <li>Added new Lint checks, including checks for layout consistency,
- {@link android.widget.RelativeLayout} siblings, {@link android.os.Parcel} creator,
- JavaScript interfaces, {@link android.app.Service} casting, quantity strings, manifest
- typos, orientation tags in layouts, overlapping names for 9-patches and images, and class
- existence checks.</li>
- <li>Updated build tools to sign applications using the BouncyCastle library instead of
- relying on Sun JVM specific APIs.</li>
- <li>Added an experimental Gradle build export feature for moving projects into the
- <a href="{@docRoot}sdk/installing/studio.html">Android Studio</a> environment or for
- setting up command-line builds with Gradle.
- (<a href="http://tools.android.com/tech-docs/new-build-system">more info</a>)</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 21.1.0</a> <em>(February 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r21.1</a>.
- If you haven't already installed SDK Tools r21.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added new <a href="{@docRoot}tools/projects/templates.html">code templates</a> for
- notifications, blank fragments and list fragments.</li>
- <li>Added support for resource rename refactoring. Renaming a resource XML file, drawable
- icon, an {@code R.} field name or ID in the layout editor invokes a refactoring routine
- to update all resource references.</li>
- <li>Added more than 15 new Lint checks, including checks for overriding older APIs, XML
- resource problems, graphic asset issues and manifest tags.
- <li>Updated XML Editor to respond to refactoring shortcut keys such as <strong>Refactor
- > Rename</strong>.</li>
- <li>Updated XML Editor to improve double click handling.</li>
- <li>Added code completion improvements for custom views, theme references and class
- references. For example, code completion in a {@code <fragment android:name="" >} tag
- now suggests completion with a list of fragment classes. Similarly, code completion in the
- manifest now offers implementations suitable for the given tag.</li>
- <li>Updated the <strong>Project Import</strong> dialog so that it shows a table for all
- imported projects where you can edit the name of the imported project.</li>
- <li>Added support for layout aliases in the Layout Editor.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed issued with refactoring support for renaming and moving classes and packages.
- </li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 21.0.1</a> <em>(December 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r21.0.1</a>.
- If you haven't already installed SDK Tools r21.0.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Build
- <ul>
- <li>Updated build to detect and handle package name conflicts between an application and
- the libraries it depends on. Libraries cannot share package names unless all of them
- share the same package name.
- (<a href="http://code.google.com/p/android/issues/detail?id=40152">Issue 40152</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=40273">Issue 40273</a>)
- </li>
- <li>Added a flag to disable dex merging to deal with cases where merging could generate
- a broken dex file. If this happens to your project, add the following setting to your
- {@code project.properties} file: {@code dex.disable.merger=true} This setting
- causes the build system to revert to the older, slower dex processing that does not
- pre-dex libraries.</li>
- </ul>
- </li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Lint
- <ul>
- <li>Corrected check for {@code 0px} values in style XML elements.
- (<a href="http://code.google.com/p/android/issues/detail?id=39601">Issue 39601</a>)
- </li>
- <li>Fixed incorrect flagging of formatting strings.
- (<a href="http://code.google.com/p/android/issues/detail?id=39758">Issue 39758</a>)
- </li>
- <li>Fixed problem where {@code tools:ignore} directive in the manifest file was ignored
- by the Lint tool.
- (<a href="http://code.google.com/p/android/issues/detail?id=40136">Issue 40136</a>)
- </li>
- <li>Fixed problem with flagging a wakelock release inside a conditional.
- (<a href="http://code.google.com/p/android/issues/detail?id=40424">Issue 40424</a>)
- </li>
- <li>Fixed incorrect reporting of missing {@code layout_width} and {@code layout_height}
- XML fields.
- (<a href="http://code.google.com/p/android/issues/detail?id=38958">Issue 38958</a>)
- </li>
- <li>Fixed handling of custom namespace attributes.</li>
- <li>Added fixes for filtering out library project warnings.</li>
- <li>Removed warnings about missing classes before a build.</li>
- </ul>
- </li>
-
- <li>Android Virtual Device Manager
- <ul>
- <li>Fixed handling of {@code devices.xml} file in other locales.
- (<a href="http://code.google.com/p/android/issues/detail?id=39704">Issue 39704</a>)
- </li>
- <li>Fixed problem where the AVD Manager would not allow you to create a new AVD using
- the <strong>4.0" WVGA</strong> or <strong> 4.65" 720p</strong> device definitions.
- (<a href="http://code.google.com/p/android/issues/detail?id=39939">Issue 39939</a>)
- </li>
- <li>Fixed problem where deleted device definitions were not removed.</li>
- <li>Fixed incorrect screen resolution setting for the Nexus One device definition.</li>
- <li>Fixed problem where writing of an AVD settings file does not properly escape
- {@code \\} path characters.</li>
- </ul>
- </li>
-
- <li>Layout Editor
- <ul>
- <li>Fixed problem where layout cannot render strings starting with {@code \@}.
- (<a href="http://code.google.com/p/android/issues/detail?id=40222">Issue 40222</a>)
- </li>
- <li>Fixed preview error when using the {@code android:numColumns} attribute in a layout.
- (<a href="http://code.google.com/p/android/issues/detail?id=21296">Issue 21296</a>)
- </li>
- <li>Fixed compatibility issue with IntelliJ layout preview caused by layout editor
- deleting the {@code .android/devices.xml} file.</li>
- <li>Added fixes to editor for {@link android.widget.GridLayout}.</li>
- </ul>
- </li>
-
- <li>Added support for {@code ldrtl} and {@code ldltr} resource qualifiers.</li>
- <li>Fixed problem where Android XML resources mistakenly get compiled into {@code *.out.xml}
- output files, causing project errors.
- (<a href="http://code.google.com/p/android/issues/detail?id=3767">Issue 3767</a>)</li>
- <li>Fixed error which caused resource refresh operations to fail.
- (<a href="http://code.google.com/p/android/issues/detail?id=39213">Issue 39213</a>)</li>
- <li>Updated the Custom View code template handle to library projects properly.</li>
- <li>Fixed support for library string resources ({@code strings.xml}) when exporting an
- application that references a library with string resources.
- (<a href="http://code.google.com/p/android/issues/detail?id=39751">Issue 39751</a>)</li>
- <li>Fixed problem where bad AVD setting files caused Device Manager and graphical XML editors
- to crash.
- (<a href="http://code.google.com/p/android/issues/detail?id=40400">Issue 40400</a>)</li>
- </ul>
- </dd>
-
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 21.0.0</a> <em>(November 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r21</a>.
- If you haven't already installed SDK Tools r21.0.0 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General improvements:</dt>
- <dd>
- <ul>
- <li>Layout Editor
- <ul>
- <li>Added multi-configuration editing feature that was previewed at Google I/O
- developer tools talk in June. For an overview, see the
- <a href="https://www.youtube.com/watch?v=Erd2k6EKxCQ">session recording</a>
- (starting at: 20:30).</li>
- <li>Modified the layout logic so that setting a {@link android.app.Fragment} layout or
- a {@link android.widget.ListView} preview layout is now applied not
- only to the current layout but to all other configurations of the same layout.</li>
- <li>Updated the editor to include resources from library projects in the resource chooser,
- XML code completion, Go To Declaration and other editing contexts.</li>
- <li>Updated the editor so that it no longer forces all variations of a single
- layout into a single editor. You can, for example, open both the landscape and portrait
- versions of a layout as separate editors and quickly switch between them, or even
- re-dock your editors to edit them simultaneously. If you prefer the previous behavior,
- set the new option in <strong>Preferences > Android > Editors</strong> to use the
- old behavior.</li>
- <li>Improved the handling of {@link android.widget.RelativeLayout} in the layout editor,
- so that dragging widgets around and deleting them should now result in the layout
- working more intuitively. In particular, deleting a widget causes the constraints
- flowing through the deleted widgets to be intelligently adjusted, and when moving
- widgets the constraints are preserved whenever possible.</li>
- <li>Added the ability to specify a default action in Layout Editor views, which you can
- invoke with the <em>F2</em> key. For example, after dropping a button or text view,
- you can press <em>F2</em> to edit its text.</li>
- <li>Added renaming of an ID (changing the {@code android:id} attribute) by invoking the
- <strong>Rename</strong> shortcut.</li>
- <li>Adding a new locale is now easier with the new <strong>Add Locale...</strong> action
- in the locale menu. In addition to creating the new values folder, it lets you edit an
- initial set of translations for the new locale.</li>
- <li>Updated the editor so that when a custom view (or incorrectly configured view)
- throws an exception during initialization or painting, part of the relevant stack trace
- is shown inline in the layout editor, and you can click on the stack frames to jump to
- the relevant location</li>
- <li>Improved the editor error display to show the relevant part of a stack trace
- when a custom view throws exceptions during rendering or construction, and provides
- hyperlinks to the stack frames.</li>
- <li>Improved the stack trace display for exceptions for custom views that are generated
- during rendering.</li>
- <li>Updated the configuration chooser so that it shows full language and region names (not
- just 2-letter codes) in menus, in the configuration dialog and other editing contexts.
- </li>
- <li>Improved the device menu in the configuration chooser.</li>
- </ul>
- </li>
- <li>Lint
- <ul>
- <li>Added over 25 new lint rules for resources, locale settings, layout
- files, incorrect use of {@link android.util.SparseArray} and
- {@link android.os.PowerManager.WakeLock} and manifest issues.</li>
- <li>Improved the XML export function to support the
- <a href="https://wiki.jenkins-ci.org/display/JENKINS/Android+Lint+Plugin">Jenkins Lint
- plugin</a>.
- </li>
- </ul>
- </li>
- <li>Editors
- <ul>
- <li>Modified the plugin to remember which editor mode (text or graphical) you were last
- using for each type of editor (layout, manifest or values) and uses that mode for newly
- opened files. This means that if you prefer to work with just XML, the editors start
- showing you XML text editors after you have switched to them for each type of editor.</li>
- <li>Updated XML code completion so that it completes (and shows documentation for) theme
- references, such as {@code ?android:attr/dividerHeight}.</li>
- </ul>
- </li>
- <li>Android Virtual Devices (AVD)
- <ul>
- <li>Added new <strong>Device Definitions</strong> tab in the AVD Manager for configuring
- standard size and Nexus virtual devices.</li>
- <li>Improved emulators so that they launch with a skin that is dynamically generated and
- reflects the actual hardware configured in the AVD Manager.</li>
- </ul>
- </li>
- <li>Improved the new template mechanism, cleaned up the existing templates and added
- several new templates</li>
- <li>Added ability to export images and frames in the Tracer for OpenGL ES tool.</li>
- <li>Integrated the Systrace tool into the DDMS perspective.</li>
- <li>Improved the JUnit test runner to allow a test to be run on all connected devices
- simultaneously.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed the editors so that attributes and resources specified by XML files in the
- {@code /values} directory are validated when files are saved.</li>
- <li>Added a workaround for a bug in Eclipse on Mac OS X 10.8 where the Property Sheet was not
- working properly.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 20.0.3</a> <em>(August 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r20.0.3</a>.
- If you haven't already installed SDK Tools r20.0.3 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with keyboard shortcuts for editors in Eclipse Juno (Version 4.x).</li>
- <li>Fixed problem with cached download lists in SDK Manager.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 20.0.2</a> <em>(July 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r20.0.1</a>.
- If you haven't already installed SDK Tools r20.0.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed keybindings in various XML editors for Eclipse 4.x.</li>
- <li>Fixed a bug that occurs when you try to create layout configurations that already
- exist.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 20.0.1</a> <em>(July 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r20.0.1</a>.
- If you haven't already installed SDK Tools r20.0.1 into your SDK, use the
- Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed issue in the New Project Wizard related to installation of the Support Library.</li>
- <li>Fixed several issues with New Project Wizard related to templates.</li>
- <li>Fixed issue with the text-based launcher icon in New Project Wizard.</li>
- <li>Fixed issue with sticky error markers in Java files.</li>
- <li>Fixed problem with manifest merger when exporting release {@code .apk} files.</li>
- <li>Fixed NDK support to automatically find include path on Windows.</li>
- <li>Fixed editor startup exception for new configurations where editor would come up blank.</li>
- <li>Added support for {@code xxhdpi} density, which was included in API Level 16.</li>
- <li>Fixed a bug in the {@code lint} check for unprotected broadcast receivers to ignore
-unprotected receivers for default Android actions.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 20.0.0</a> <em>(June 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}sdk/tools-notes.html">SDK Tools r20</a>.
- If you haven't already installed SDK Tools r20 into your SDK, use the Android SDK
- Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General improvements:</dt>
- <dd>
- <ul>
- <li>Application Templates
- <ul>
- <li>Added Android application templates to allow developers to create specific types of
-applications faster, using Android-recommended best practices.</li>
- </ul>
- </li>
- <li>Performance
- <ul>
- <li>Improved overall ADT performance and fixed memory issues. Loading SDK data
-should be up to 30% faster.</li>
- </ul>
- </li>
- <li>Tracer for GLES
- <ul>
- <li>Added new perspective view and tools for tracing OpenGL calls for an application and
-track the visual results of each call. (<a href="{@docRoot}tools/help/gltracer.html">more info</a>)</li>
- </ul>
- </li>
- <li>Lint
- <ul>
- <li>Added new Lint rules for manifest registrations, duplicate activity
-registrations, security checking, correct use of Toast, missing SharedPreferences commit()
-calls, Fragment class instantiation, and handler leaks.</li>
- <li>Created tighter integration of lint with the layout editor. (<a
-href="http://tools.android.com/recent/lintfeedback">more info</a>)</li>
- <li>Added execution of Lint tool on save option for Java files. (<a
-href="http://tools.android.com/recent/lintonsave">more info</a>)</li>
- </ul>
- </li>
- <li>Layout Editor (<a href="http://tools.android.com/recent/newlayouteditorpropertysheet">more
-info</a>)
- <ul>
- <li>Added highlighting (in bold) for important attributes, inline preview of colors and
-images, including the corresponding resource name.</li>
- <li>Added display of default values, when available.</li>
- <li>Added completion of resource values and enum and flag constants.</li>
- <li>Added support for displaying advanced properties, and nested properties for better
-categorization, for example, layout params are listed first as a single nested property.</li>
- <li>Display Tooltips over the attribute names, not values, so they never obscure the value
-column.</li>
- <li>Provided checkbox support for boolean values.</li>
- <li>Added support for switching between alphabetical and natural sort orders.</li>
- <li>Improved layout editor tool's window management for more usable editing views.</li>
- <li>Improved the layout editor's configuration chooser header user interface.</li>
- </ul>
- </li>
- <li>XML Editing
- <ul>
- <li>Added go to declaration support for theme references (?android:attr, ?attr:).</li>
- <li>Improved code completion in style definitions.</li>
- <li>Improved code completion for the {@code minSdkVersion} and {@code targetSdkVersion}
-attributes in manifest files so that version descriptions are displayed for each of the API
-levels</li>
- <li>Provided support for code completion of custom attributes for custom views,
-including current edits to the style files.</li>
- <li>Improved synchronization of text and graphic editors with the XML outline view,
-including outline changes and display of current selection.</li>
- </ul>
- </li>
- <li>Build System
- <ul>
- <li>Added automatic merging of library project manifest files into the including
-project's manifest. Enable this feature with the {@code manifestmerger.enabled} property.</li>
- <li>Added automatic ProGuard support for the {@code aapt -G} flag. This change causes
-the build system to generate a temporary ProGuard keep-rules file containing classes that
-are referenced from XML files (such as custom views) and pass this to ProGuard at shrink-time. This
-can make the resulting APK much smaller when using just a small portion of a large library project
-(such as the Android Support library), since the catch-all rules to keep all custom views from the
-default ProGuard configuration file have also been removed.</li>
- </ul>
- </li>
- <li>Added support building and debugging NDK-based Android projects.</li>
- </li>
- <li>Added support to the Asset Studio Wizard for padding and turning off background
-shapes.</li>
- <li>Improved LogCat to allow developers to set colors for different priorities.</li>
- <li>Improved app Run functionality to allow running on multiple devices with a single launch.
-The target tab in the launch configuration dialog includes an option to allow launching on all
-connected devices, with the option to further narrow the list to just physical devices or just
-emulators. (This feature is available only for Run configurations, and not for Debug or JUnit
-tests.)</li>
- <ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed a number of issues where Lint incorrectly reported code errors or failed to
-flag code issues.</li>
- <li>Fixed several bugs in the layout editor.</li>
- <li>Fixed compatibility issues with Eclipse 4.x (Juno), including cut/copy/paste
-functions.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 18.0.0</a> <em>(April 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r18</a>.
- If you haven't already installed SDK Tools r18 into your SDK, use the Android SDK
- Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed problem where exporting release package does not recompile libraries in release
- mode.
- (<a href="http://code.google.com/p/android/issues/detail?id=27940">Issue 27940</a>)</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 17.0.0</a> <em>(March 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Java 1.6 or higher is required.</li>
- <li>Eclipse Helios (Version 3.6.2) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r17</a>.
- If you haven't already installed SDK Tools r17 into your SDK, use the Android SDK
- Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General improvements:</dt>
- <dd>
- <ul>
- <li>New build features
- <ul>
- <li>Added feature to automatically setup JAR dependencies. Any {@code .jar} files in the
- {@code /libs} folder are added to the build configuration (similar to how the Ant build
- system works). Also, {@code .jar} files needed by library projects are also automatically
- added to projects that depend on those library projects.
- (<a href="http://tools.android.com/recent/dealingwithdependenciesinandroidprojects">more
- info</a>)</li>
- <li>Added a feature that allows you to run some code only in debug mode. Builds now
-generate a class called {@code BuildConfig} containing a {@code DEBUG} constant that is
-automatically set according to your build type. You can check the ({@code BuildConfig.DEBUG})
-constant in your code to run debug-only functions.</li>
- <li>Added support for custom views with custom attributes in libraries. Layouts using
-custom attributes must use the namespace URI {@code http://schemas.android.com/apk/res-auto} instead
-of the URI that includes the app package name. This URI is replaced with the app specific one at
-build time.</li>
- </ul>
- </li>
- <li>Improved Lint features. See the <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r17</a>
-release notes.</li>
- <li>Improved the Lint user interface
- <ul>
- <li>Added <strong>Run Lint</strong> toolbar action with a dropdown menu for selecting
-specific (or all) projects, clearing results and other actions.</li>
- <li>Updated the results window to be organized as a tree rather than a flat list. Each
-issue type has a single top level item, which makes it easier to quickly scan through the reported
-issues and narrow down to the issues you are most interested in.</li>
- <li>Added many new toolbar actions to the results window, including expand/collapse,
-ignore in file, ignore in project, ignore everywhere, show options, and configure columns.</li>
- <li>Added new column options for the <strong>Lint Warnings</strong> tab, such as
-category, priority, project, file and line. The column selection (as well as the column sizes) are
-persisted. You can also click on columns to sort by those values.</li>
- <li>Added Enable All and Disable All buttons to the Lint Options dialog, and a search
-filter textbox to filter by issue id, summary and severity.</li>
- </ul>
- </li>
- <li>Added Quick Outline for XML editors (Ctrl-O, Command-O). This feature shows the structure
-of the current file including icons and ids, lets you filter and quickly jump to specific ids.</li>
- <li>Updated the resource chooser to shows the resolved value for resources. For example,
-when selecting {@code @string/hello} the chooser displays a resolved value such as "Hello World").
-The resource chooser also now allows you to edit the chosen value directly.</li>
- <li>Updated Layout Editor so that it does not assign default ids to layouts, includes and
-merge tags. This behavior tended to pollute the namespace with a lot of unused resources since
-layouts are not usually manipulated via code, or referenced from XML. (The RelativeLayout editor
-automatically assigns ids to views without ids when pointing to them.)</li>
- <li>Added ability to export screenshots from the Layout Editor</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed problem using Layout Editor with {@link android.widget.SlidingDrawer} which could
- not be dragged into the layout on some platforms.</li>
- <li>Fixed preview rendering for {@link android.widget.SlidingDrawer} and
- {@link android.widget.TabHost}.
- (<a href="http://code.google.com/p/android/issues/detail?id=23022">Issue 23022</a>).</li>
- <li>Fixed issues that could prevent layout rendering due to unresolvable resources.
- (<a href="http://code.google.com/p/android/issues/detail?id=21046">Issue 21046</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=21051">Issue 21051</a>)</li>
- <li>Fixed a bug in resource chooser which made some types of framework resources impossible to
-select. (<a href="http://code.google.com/p/android/issues/detail?id=20589">Issue 20589</a>)</li>
- <li>Fixed a bug in the formatter where a certain whitespace pattern could result in a
- non-space character getting deleted.
- (<a href="http://code.google.com/p/android/issues/detail?id=23940">Issue 23940</a>)</li>
- <li>Fixed a locale bug affecting Turkish locales in particular.
- (<a href="http://code.google.com/p/android/issues/detail?id=23747">Issue 23747</a>)</li>
- <li>Fixed an issue where dex complains about duplicate classes in cases where a Library
- Project depends on the same jar files or Java-only projects.</li>
- <li>Fixed an issue where test projects had to independently reference the library projects
- used by an app project. Now referencing only the app project is enough.</li>
- </ul>
- </dd>
-
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 16.0.1</a> <em>(December 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Eclipse Helios (Version 3.6) or higher is required.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r16</a>.
- If you haven't already installed SDK Tools r16 into your SDK, use the Android SDK
- Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed build issue where the 9-patch could be packaged as normal bitmap in some cases.</li>
- <li>Fixed minor issues in the <a href="http://tools.android.com/recent/lint">Lint</a>
- tool.</li>
- <li>Fixed minor issues in the SDK Manager.</li>
- </ul>
- </dd>
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 16.0.0</a> <em>(December 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Eclipse Helios (Version 3.6) or higher is required for ADT 16.0.0.</li>
- <li>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r16</a>.
- If you haven't already installed SDK Tools r16 into your SDK, use
- the Android SDK Manager to do so.</li>
- </ul>
- </dd>
-
- <dt>General improvements:</dt>
- <dd>
- <ul>
- <li>Added Lint tool to detect common errors in Android projects. (<a
-href="http://tools.android.com/recent/lint">more info</a>)</li>
- </ul>
- </dd>
-</dl>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 15.0.1</a> <em>(November 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
- <dt>Dependencies:</dt>
-
- <dd>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r15</a>.
- If you haven't already installed SDK Tools r15 into your SDK, use the Android SDK Manager to
- do so.</dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed how source files are attached to library project <code>.jar</code> files.</li>
- <li>Fixed how the <code>bin/</code> folder for library projects are refreshed. This ensures that parent projects pick up changes in library projects.</li>
- <li>Fixed how a parent project's library container is updated when a library project is recompiled. This ensures that parent projects are
- recompiled when code in a library project changes.</li>
- <li>Fixed how <code>res/</code> folders are checked in library projects. This ensures that all <code>res</code> folders are properly included
- even if Eclipse is not aware of them due to refresh issues.</li>
- <li>Fixed issue that prevented <code>aapt</code> from running when editing certain XML files.</li>
- <li>Fixed minor XML formatting issues.</li>
- </ul>
- </dd>
-</dl>
-
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 15.0.0</a> <em>(October 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r15</a>.
- If you haven't already installed SDK Tools r15 into your SDK, use the Android SDK Manager to
- do so.</dd>
-
-<dt>Bug fixes:</dt>
-<dd>
-<ul>
- <li>Fixed build issue when using RenderScript in projects that target API levels 11-13
- (<a href="http://code.google.com/p/android/issues/detail?id=21006">Issue 21006</a>).</li>
- <li>Fixed issue when creating projects from existing source code.</li>
- <li>Fixed issues in the SDK Manager
- (<a href="http://code.google.com/p/android/issues/detail?id=20939">Issue 20939</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=20607">Issue 20607</a>).</li>
- <li>Fixed a scrolling issue in the new Logcat panel of DDMS.</li>
-</ul>
-</dd>
-</dl>
-
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 14.0.0</a> <em>(October 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with
- <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r14</a>.
- If you haven't already installed SDK Tools r14 into your SDK, use the Android SDK Manager to
- do so.</dd>
-
-<dt>Build system:</dt>
-<dd>
- <ul>
- <li>Changed <code>default.properties</code> to <code>project.properties</code> and
- <code>build.properties</code> to <code>ant.properties</code>. ADT automatically
- renames these files, if necessary, when you open a project in Eclipse.</li>
- <li>Changed how library projects are built in Eclipse.</a></li>
- <li>Changed output of <code>javac</code> from <code>bin/</code> to <code>bin/classes</code>
- in Eclipse.</li>
- <li>Improved incremental builds so that resource compilation runs less frequently. Builds no
- longer run when you edit strings or layouts (unless you add a new <code>id</code>) and no longer
- run once for each library project.</li>
- <li>Introduced a "PNG crunch cache" that only runs on modified PNG files, instead of
- crunching all existing PNG files, all the time.</li>
- <li>Modified resource compilation so it no longer happens for normal save operations. It only
- happens when running or debugging (the build option that lets you disable the packaging
- step, which was introduced in ADT 12, is now on by default.)</li>
- </ul>
-<p>For a complete overview of the build system changes and what you need to do to support them,
-see the <a href="http://tools.android.com/recent/buildchangesinrevision14">Android Tools Project
-site</a>.</p>
-</dd>
-
-<dt>General improvements:</dt>
-<dd>
- <ul>
-
-
-<li>Added a Welcome Wizard to help with the initial setup of the Android
-development environment (<a href="http://tools.android.com/recent/welcomewizard">more
-info</a>).</li>
-<li>Integrated the Android Asset Studio, which helps you create icons for things
-like the launcher, menus, and tabs. (<a
-href="http://tools.android.com/recent/assetstudiointegration">more
-info</a>).</li>
-<li>Revamped the Logcat view and added support to display and filter logs by
- application names as well as PIDs (<a
- href="http://tools.android.com/recent/updatedlogcatviewer">more info</a>).</li>
-<li>Revamped the SDK Manager UI (<a href="http://tools.android.com/recent/newsdkmanager">more
-info</a>).</li>
-<li>Revamped the New Project and the New XML File wizards to have
-multiple pages. Sample projects are now copied into the workspace such that they can be modified
-and deleted without affecting the master copy
-(<a href="http://tools.android.com/recent/revampedwizards">more info</a>).</li>
-<li>Removed the dependency on Eclipse GEF.</li>
-</ul>
-</dd>
-
-<dt>XML and Java editors:</dt>
-<dd>
- <ul>
- <li>Added a new XML formatter that formats all XML files according to the
- standard Android coding style. The formatter can also reorder
- attributes to follow a recommended order and processes any changes made in the Layout editor.
-(<a href="http://tools.android.com/recent/xmlformatter">more info</a>).</li>
- <li>Added the "Go to Matching" (Ctrl-Shift-P) feature, which lets you jump
-between opening and closing tags in XML files.</li>
- <li>Added support for the "Select Enclosing Element" feature on Mac.</li>
- <li>Added a Quickfix for extracting Strings when the caret is inside a String (<a href="">see
-more</a>).</li>
- <li>Improved "smart indent", which allows automatic indentation and un-indentation
- when pressing the Return key in XML editors (<a
-href="http://tools.android.com/recent/xmleditingimprovements">more info</a>).</li>
-
- </ul>
-</dd>
-
-<dt>Layout editor:</dt>
-<dd>
- <ul>
- <li>Added tooltip feedback for dragging and resizing operations. For
- example, when dragging in a relative layout, the proposed
- constraints are shown. When resizing, the new dimensions are
- shown (<a href="http://tools.android.com/recent/layouteditorfeedbacktooltips">more
-info</a>).</li>
- <li>Added the ability to suppress rendering fidelity warnings (<a
-href="http://tools.android.com/recent/suppressrenderwarnings">more info</a>).</li>
- <li>Added "Remove Container" visual refactoring that removes the
- children of a container up to the top level and transfers
- namespace and layout attributes if necessary (<a
-href="http://tools.android.com/recent/removecontainervisualrefactoring">more info</a>).</li>
- <li>Added pull-right menus to the context menu for accessing
- properties of the parents, which is useful when the children fully
- cover the parent and make it hard to select on their own.</li>
- <li>Improved access to properties in the context menu. The most
- frequently set attributes for each view are listed at the top of
- the menu. The Properties menu offers access to the most
- recently set attributes, attributes organized by their defining
- view, and layout attributes only or all attributes alphabetically (<a
-href="http://tools.android.com/recent/layouteditorcontextmenuimprovements">more info</a>).</li>
- </ul>
-</dd>
-
-<dt>Bug fixes:</dt>
-<dd>Fixed many bugs and added <a
-href="http://tools.android.com/recent/miscellaneousrecentfixes">minor improvements</a>, in
-particular some <a href="http://tools.android.com/recent/linuxfixes">critical bug fixes on
-Linux</a>.</dd>
-
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 12.0.0</a> <em>(July 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with
-<a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r12</a>. If you haven't
-already installed SDK Tools r12 into your SDK, use
-the Android SDK Manager to do so.</dd>
-
-<dt>Visual Layout Editor:</dt>
-<dd>
-<ul>
- <li>New RelativeLayout drop support with guideline suggestions for
- attachments and cycle prevention
- (<a href="http://tools.android.com/recent/revampedrelativelayoutsupport">more info</a>).</li>
- <li>Resize support in most layouts along with
- guideline snapping to the sizes dictated by <code>wrap_content</code> and <code>match_parent</code>.
- In LinearLayout, sizes are mapped to weights instead of pixel widths.
- (<a href="http://tools.android.com/recent/resizesupport">more info</a>).</li>
- <li>Previews of drawables and colors in the resource chooser dialogs
- (<a href="http://tools.android.com/recent/imageandcolorpreviews">more info</a>).</li>
- <li>Improved error messages and links for rendering errors including
- detection of misspelled class names
- (<a href="http://tools.android.com/recent/improvedrenderingerrordiagnostics">more info</a>).</li>
-</ul>
-</dd>
-
-<dt>Build system:</dt>
-<dd>
-<ul>
- <li id="build-option">A new option lets you disable the packaging step in the automatic
- builders. This improves performance when saving files by not
- performing a full build, which can take a long time for large projects.
- If the option is enabled, the APK is packaged when the
- application is deployed to a device or emulator or when the
- release APK is exported (<a href="http://tools.android.com/recent/finercontroloveradtbuildprocess">more info</a>).</li>
-</ul>
-</dd>
-
-<dt>Bug fixes:</dt>
-<dd>Many bug fixes are part of this release
-(<a href="http://tools.android.com/recent/adt12bugfixroundup">more info</a>).</dd>
-
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 11.0.0</a> <em>(June 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with SDK Tools r11. If you haven't
-already installed SDK Tools r11 into your SDK, use the Android SDK Manager to do
-so.</dd>
-
-<dt>Visual Refactoring:</dt>
-<dd>
- <ul>
- <li>"Extract Style" feature pulls out style-related attributes from your layout and extracts
-them as a new style defined in {@code styles.xml} (<a
-href="http://tools.android.com/recent/extractstylerefactoring">more info</a>).</li>
- <li>"Wrap in Container" feature lets you select a group of views then surround them
- in a new layout (a new view group, such as a LinearLayout), and transfers namespace and layout
- parameters to the new parent (<a
-href="http://tools.android.com/recent/newrefactoringswrapinchangelayoutchangewidget">more
-info</a>).</li>
- <li>"Change Layout" feature changes layouts from one type
- to another, and can also flatten a layout hierarchy (<a
-href="http://tools.android.com/recent/newrefactoringswrapinchangelayoutchangewidget">more
-info</a>).</li>
- <li>"Change Widget Type" feature changes the type of the
- selected views to a new type. Also, a new selection context menu
- in the visual layout editor makes it easy to select siblings as
- well as views anywhere in the layout that have the same type (<a
-href="http://tools.android.com/recent/newrefactoringswrapinchangelayoutchangewidget">more
-info</a>).</li>
- <li>"Extract as Include" feature finds identical collections of views
- in other layouts and offers to combine them into a single layout that you can then include in
- each layout (<a
-href="http://tools.android.com/recent/extractasincludeimprovements">more info</a>).</li>
- <li>Quick Assistant in Eclipse can be invoked
- from the XML editor (with Ctrl-1) to apply any of the above
- refactorings (and Extract String) to the current selection (<a
-href="http://tools.android.com/recent/refactoringquickassistant">more info</a>).</li>
- </ul>
-</dd>
-
-<dt>Visual Layout Editor:</dt>
-<dd>
- <ul>
- <li>This is the update to the layout editor you've been waiting for! It includes (almost) all
-the goodies demonstrated at Google I/O. <a href="http://www.youtube.com/watch?v=Oq05KqjXTvs">Watch
-the video</a> on YouTube.</li>
- <li>The palette now supports different configurations for supported widgets. That is, a single
-view is presented in various different configurations that you can drag into your layout. For
-example, there is a <em>Text Fields</em> palette category where you can drag an {@link
-android.widget.EditText} widget in as a password field, an e-mail field, a phone field, or other
-types of text boxes. Similarly, {@link android.widget.TextView} widgets are preconfigured
-with large, normal and small theme sizes, and {@link android.widget.LinearLayout} elements are
-preconfigured in horizontal and vertical configurations (<a
-href="http://tools.android.com/recent/multipletextfieldandlayouttypes">more info</a>).</li>
- <li>The palette supports custom views. You can pick up any custom
- implementations of the View class you've created in your project or from included libraries and
-drag them into your layout (<a
-href="http://tools.android.com/recent/customviewsinthepalette">more info</a>).</li>
- <li>Fragments are available in the palette for placement in your layout. In the tool, you can
-choose which layout to show rendered for a given fragment tag. Go to declaration works for fragment
-classes (<a href="http://tools.android.com/recent/fragmentsupport">more info</a>).</li>
- <li>The layout editor automatically applies a "zoom to fit" for newly
- opened files as well as on device size and orientation changes to
- ensure that large layouts are always fully visible unless you
- manually zoom in.</li>
- <li>You can drop in an {@code <include>} element from the palette, which will pop up
- a layout chooser. When you select the layout to include, it is added with an {@code
-<include>}. Similarly, dropping images or image buttons will pop up image
- resource choosers (<a
-href="http://tools.android.com/recent/includetagdropsupport">more info</a>).</li>
- <li>The configuration chooser now applies the "Render Target" and
- "Locale" settings project wide, making it trivial to check the
- layouts for different languages or render targets without having
- to configure these individually for each layout.</li>
- <li>The layout editor is smarter about picking a default theme to
- render a layout with, consulting factors like theme registrations
- in the manifest, the SDK version, and other factors.</li>
- <li>The layout editor is smarter about picking a default configuration to render a layout
-with, defaulting to the currently visible configuration in the previous file. It also considers the
-SDK target to determine whether to default to a tablet or phone screen size.</li>
- <li>Basic focus support. The first text field dropped in a layout is assigned focus, and there
-are <strong>Request Focus</strong> and <strong>Clear Focus</strong> context menu items on text
-fields to change the focus.</li>
- </ul>
-</dd>
-
-<dt>XML editors:</dt>
-<dd>
-<ul>
- <li>Code completion has been significantly improved. It now works
- with {@code <style>} elements, completes dimensional units,
- sorts resource paths in values based on the attribute name, and more. There are also many fixes to
-handle text replacement (<a
-href="http://tools.android.com/recent/xmlcodecompletionimprovements">more info</a>).</li>
- <li>AAPT errors are handled better. They are now underlined for the
- relevant range in the editor, and a new quickfix makes it trivial
- to create missing resources.</li>
- <li>Code completion for drawable, animation and color XML files (<a
-href="http://tools.android.com/recent/codecompletionfordrawablescolorsandanimationfiles">more
-info</a>).</li>
-</ul>
-</dd>
-
-<dt>DDMS:</dt>
-<dd>
-<ul>
- <li>"New Folder" action in the File Explorer.</li>
- <li>The screenshot dialog will add timestamps to the filenames and preserve the orientation on
-snapshot refresh.</li>
-</ul>
-</dd>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>TraceView supports zooming with the mouse-wheel in the timeline.</li>
- <li>The New Android Project wizard now supports Eclipse working sets.</li>
- </ul>
-</dd>
-</dl>
-<p>More information about tool changes are available on the <a
-href="http://tools.android.com/recent">Android Tools Project Site</a>.</p>
-</div>
-</div>
-
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 10.0.1</a> <em>(March 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with SDK Tools r10. If you haven't
-already installed SDK Tools r10 into your SDK, use the Android SDK Manager to do
-so.</dd>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>Temporary work-around to resolve the rare cases in which the layout editor will
-not open.</li>
- <li>Fixed an issue in which ADT 10.0.0 would install on Eclipse 3.4 and lower, even though ADT
-requires Eclipse 3.5 or higher (as of 10.0.0).</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 10.0.0</a> <em>(February 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with SDK Tools r10. If you haven't
-already installed SDK Tools r10 into your SDK, use the Android SDK Manager to do
-so.</dd>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>The tools now automatically generate Java Programming Language source files (in the <code>gen/</code> directory) and
- bytecode (in the <code>res/raw/</code> directory) from your <code>.rs</code> files.</li>
- <li>A Binary XML editor has been added (<a href="http://tools.android.com/recent/binaryxmleditor">details</a>).</li>
- <li>Traceview is now integrated into the Eclipse UI (<a href="http://tools.android.com/recent/traceviewineclipse">details</a>).</li>
- <li>The "Go To Declaration" feature for XML and <code>.java</code> files quickly show all the matches in the project
- and allows you jump to specific items such as string translations or <code>onClick</code> handlers
- (<a href="http://tools.android.com/recent/gotodeclarationimprovements">details</a>).</li>
- <li>The Resource Chooser can create items such as dimensions, integers, ids, and booleans
- (<a href="http://tools.android.com/recent/resourcechoosercannowcreatearbitraryvalues">details</a>).</li>
- <li>Improvements to the Visual Layout Editor:
- <ul>
- <li>A new Palette with categories and rendering previews
- (<a href="http://tools.android.com/recent/newpalette">details</a>).</li>
- <li>A Layout Actions bar that provides quick access to common layout operations
- (<a href="http://tools.android.com/recent/layoutactionsbar">details</a>).</li>
- <li>When the Android 3.0 rendering library is selected, layouts render more like they do on devices.
- This includes rendering of status and title bars to more accurately reflect the actual
- screen space available to applications
- (<a href="http://tools.android.com/recent/systembarandactionbar">details</a>).</li>
- <li>Zoom improvements such as fit to view, persistent scale, and keyboard access.
- (<a href="http://tools.android.com/recent/zoomimprovements">details</a>).</li>
- <li>Further improvements to <code><merge></code> layouts, as well as layouts with gesture overlays
- (<a href="http://tools.android.com/recent/improvedsupportformergetags">details</a>).</li>
- <li>Improved rendering error diagnostics.</li>
- </ul>
- </li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 9.0.0</a> <em>(January 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd>This version of ADT is designed for use with SDK Tools r9. If you haven't
-already installed SDK Tools r9 into your SDK, use the Android SDK Manager to do
-so.</dd>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>"Go To Declaration" hyperlink support: You can jump directly from code references (such as
- <code>R.id.main</code>) to the corresponding XML declaration, or from XML attributes (such as
- <code>@string</code>) to the corresponding resource definition, or from manifest XML
- registrations to activities and services.</li>
- <li>Improvements were made to name refactoring.</li>
- <li>AVDs now automatically save their state, so they can restart almost instantly. You can enable this feature when
- creating an AVD or by editing an AVD with the AVD Manager.</li>
- <li>Improvements to the Visual Layout Editor:
- <ul>
- <li>Support for rendering targets: You can now choose an arbitrary Android platform to
- render the current page, regardless of the project's minimum platform. This makes it
- easy to verify the layout and appearance of your activity on different versions of
- the platform.
- </li>
- <li>Improved support for empty and nested layouts: Dragging items over nested and
- invisible layouts automatically enlarges and highlights these layouts, so that they
- can receive drops.
- </li>
- <li>XML formatting improvements: The editor generates cleaner XML and you can now enable
- XML auto-formatting in the <strong>Preferences</strong> menu.</li>
- <li>Improved Outline labels: The Outline tab now displays additional information about each
- View. Textual Views display a snippet of the actual text. Views with a source
- (such as ImageView) displays the resource name. Included Views display the name of the View.
- </li>
- <li>When you right click a View in the Layout Editor,
- the context menu now contains <strong>Edit ID...</strong> and <strong>Edit Text...</strong>
- items. The <strong>Properties...</strong> context menus now list all of the properties and
- provide a way to edit them
- (<a href="http://tools.android.com/recent/editidtextandotherpropertiesviamenu">Details</a>).
- </li>
- <li>The layout editor now properly handles
- <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element"><code><include></code></a>
- and <a href="{@docRoot}guide/topics/resources/layout-resource.html#merge-element"><code><merge></code></a>
- tags (<a href="http://tools.android.com/recent/supportforincludeandmerge">Details</a>).</li>
- <li>"Extract as Include" refactoring: The Layout Editor has a new refactoring that allows
- you to select one or more views in a layout, and extract it into a separate layout
- (<a href="http://tools.android.com/recent/extractasincluderefactoring">Details</a>).</li>
- <li>Improved diagnostics for class loading and rendering errors: Class loading and rendering
- error messages are more useful and provide better information about the root cause of the
- error.</li>
- <li>Improved error handling to prevent drag and reordering operations from adding children
- into an {@link android.widget.AdapterView}.</li>
- <li>Outline reordering: Reordering your views in the Outline tab is much easier
- (<a href="http://tools.android.com/recent/outlineimprovements">Details</a>).</li>
- <li>Fix for keybinding bug where keyboard shortcuts did not work (Issues
- <a href="http://code.google.com/p/android/issues/detail?id=13231">13231</a> and
- <a href="http://code.google.com/p/android/issues/detail?id=13134">13134</a>).</li>
- <li>Fix for problems with Custom layout attribute menu (Issue
- <a href="http://code.google.com/p/android/issues/detail?id=13134">13134</a>).</li>
- <li>Automatic configuration for various view types: Certain views have properties configured
- by default. For example, the width of an {@link android.widget.EditText} object is set to
- <code>match_parent</code> when added to a vertical {@link android.widget.LinearLayout}
- or a default image is added to an {@link android.widget.ImageButton}.</li>
- <li>Previews during dragging: Dragging from the palette or dragging within the layout editor
- now shows live previews of the dragged item.</li>
- <li>Navigation improvements: In the Layout Editor, double-clicking Views jumps to the
- corresponding XML element. In the Outline view, double-clicking opens the Properties view.</li>
- <li>The editor has Honeycomb style animation preview support.</li>
- <li>Improved rendering support for various Views (such as TabHosts and SlidingDrawers) in
- Honeycomb (Issues <a href="http://code.google.com/p/android/issues/detail?id=3162">3162</a>
- and <a href="http://code.google.com/p/android/issues/detail?id=13092">13092</a>).</li>
- <li>Included layouts can be rendered and edited in the context of the layouts that include
- them. From a layout using an <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element">
- <code><include></code></a> tag, double-clicking on the
- <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element">
- <code><include></code></a> element edits the referenced layout in the context of the
- current layout. Additionally, when editing a layout that is included by other layouts,
- you can quickly change between context layouts, by right clicking in the editor and choosing
- <strong>Show included in...</strong>. This feature is only available in Honeycomb.</li>
- </ul>
- </li>
- <li>This release fixes many other bugs, but the most important ones are listed below:
- <ul>
- <li>Fixed issue that prevented launching debug builds on productions devices when
- <code>debuggable=true</code> was not set in the Android manifest.</li>
- <li>The LogCat view in DDMS properly handles UTF-8 characters.</li>
- <li>The SDK Manager is more reliable on Windows
- (<a href="http://tools.android.com/recent/sdkmanagerfixes">Details</a>).</li>
- <li>A JUnit initialization bug that prevented you from working with JUnit tests was fixed
- (Issue <a href="http://code.google.com/p/android/issues/detail?id=12411">12411</a>).</li>
- </ul>
-</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 8.0.1</a> <em>(December 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<p>This version of ADT is designed for use with SDK Tools r8. If you haven't
-already installed SDK Tools r8 into your SDK, use the Android SDK Manager to do
-so.</p></dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
- <li>This is a quick follow-up to ADT 8.0.0 to fix some bugs.</li>
- <li>Fixes an issue in which projects failed to compile, citing a dex error.</li>
- <li>Better ProGuard error reporting when exporting applications for release.</li>
-</ul>
-<p>Also see the recent release notes for 8.0.0, below.</p>
-</dd>
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 8.0.0</a> <em>(December 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<p>This version of ADT is designed for use with SDK Tools r8. If you haven't
-already installed SDK Tools r8 into your SDK, use the Android SDK Manager to do
-so.</p></dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
- <li>New version number scheme that follows the SDK Tools revision number. The major version
-number for your ADT plugin should now always match the revision number of your SDK Tools. For
-example, ADT 8.x is for SDK Tools r8.</li>
- <li>Support for true debug build. You no longer need to change the value of the
- <code>debuggable</code> attribute in the Android Manifest.
- <p>Incremental builds automatically insert <code>debuggable="true"</code>, but if you perform
- "export signed/unsigned application package", ADT does <em>not</em> insert it.
- If you manually set <code>debuggable="true"</code> in the manifest file, then release builds will
- actually create a debug build (it does not remove it if you placed it there).</p></li>
- <li>Automatic <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> support in
- release builds. For it to work, you need to have a <code>proguard.config</code>
- property in the <code>default.properties</code> file that points to a ProGuard config file.</li>
- <li>Completely rewritten Visual Layout Editor. (This is still a work in progress.) Now includes:
- <ul>
- <li>Full drag and drop from palette to layout for all Layout classes.</li>
- <li>Move widgets inside a Layout view, from one Layout view to another and from one layout file to another.</li>
- <li>Contextual menu with enum/flag type properties.</li>
- <li>New zoom controls.</li>
- </ul></li>
- <li>New HierarchyViewer plugin for Eclipse.</li>
- <li>Android launch configurations no longer recompile the whole workspace on launch.</li>
- <li>The location of <code>android.jar</code> source and javadoc can now be configured.</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.9</a> <em>(September 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd><p>ADT 0.9.9 replaces ADT 0.9.8 and is designed for use with SDK Tools r7
-and later. ADT 0.9.9 includes the ADT 0.9.8 features as well as an important
-bugfix, so we recommend that you upgrade as soon as possible. If you haven't
-already installed SDK Tools r7 into your SDK, use the Android SDK Manager to do
-so.</p></dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>Fixes a problem in project import, in which source files were deleted in some cases.</li>
-<li>Includes all other ADT 0.9.8 features (see below).</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.8</a> <em>(September 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-</ul>
-</dd>
-
-<dl>
-
-<dt>Dependencies:</dt>
-
-<dd><p>ADT 0.9.8 is now deprecated. Please use ADT 0.9.9 instead.</p></dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>Adds a new Action, "Rename Application Package", to the Android Tools
-contextual menu. The Action does a full application package refactoring.
-<li>Adds support for library projects that don't have a source folder
-called <code>src/</code>. There is now support for any number of source folders,
-with no name restriction. They can even be in subfolder such as
-<code>src/java</code>. If you are already working with library projects created
-in ADT 0.9.7, see <a
-href="{@docRoot}tools/projects/index.html#libraryMigrating">Migrating
-library projects to ADT 0.9.8</a> for important information about moving
-to the new ADT environment.</li>
-<li>Adds support for library projects that depend on other library
-projects.</li>
-<li>Adds support for additional resource qualifiers:
-<code>car</code>/<code>desk</code>, <code>night</code>/<code>notnight</code> and
-<code>navexposed</code>/<code>navhidden</code>.</li>
-<li>Adds more device screen types in the layout editor. All screen
-resolution/density combinations listed in the <a
-href="{@docRoot}guide/practices/screens_support.html#range">Supporting
-Multiple Screens</a> are now available.</li>
-<li>Fixes problems with handling of library project names that
-contain characters that are incompatible with the Eclipse path variable.
-Now it properly sets up the link between the main project and the library
-project.</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.7</a> <em>(May 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Library projects:</dt>
-<dd>
-<p>The ADT Plugin now supports the use of <em>library projects</em> during
-development, a capability that lets you store shared Android application
-code and resources in a separate development project. You can then reference the
-library project from other Android projects and, at build time, the tools
-compile the shared code and resources as part of the dependent applications.
-More information about this feature is available in the <a
-href="{@docRoot}tools/projects/index.html#LibraryProjects">Creating and Managing Projects</a> document. </p>
-<p>If you are not developing in Eclipse, <a
-href="tools-notes.html">SDK Tools r6</a> provides the equivalent library
-project support through the Ant build system.</p>
-</dd>
-</dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.6</a> <em>(March 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-
-<dd><p>This version of ADT is designed for use with SDK Tools r5 and later. Before
-updating to ADT 0.9.6, we highly recommend that you use the Android SDK Manager to install SDK
-Tools r5 into your SDK.</p></dd>
-
-<dt>General Notes:</dt>
-<dd>
-<ul>
-<li>Editing <code>default.properties</code> outside of Eclipse will now
-automatically update the project.</li>
-<li>Loads the SDK content only when a project requires it. This will make
-Eclipse use less resources when the SDK contains many versions of Android.</li>
-<li>Resolves potential deadlock between modal dialogs, when launching ADT the
-first time with the SDK Usage panel.</li>
-<li>Fixes issues with the New Project Wizard when selecting samples.</li>
-</ul>
-</dd>
-<dt>AVD/SDK Manager:</dt>
-<dd>
-<ul>
-<li>Adds support for platform samples packages.</li>
-<li>Improves support for dependency between packages.</li>
-<li>AVDs now sorted by API level.</li>
-<li>The AVD creation dialog now enforces a minimum SD card size of 9MB.</li>
-<li>Prevents deletion of running AVDs.</li>
-</ul>
-</dd>
-<dt>DDMS:</dt>
-<dd>
-<ul>
-<li>DDMS plug-in now contains the Allocation Tracker view.</li>
-<li>New action in the Logcat view: "Go to problem" lets you go directly from an
-exception trace output to the code.</li>
-</ul>
-</dd>
-<dt>Editors:</dt>
-<dd>
-<ul>
-<li>Explode mode in the Visual Layout Editor adds a margin to all layout objects
-so that it's easier to see embedded or empty layouts.</li>
-<li>Outline mode in the Visual Layout Editor draws layout outline to make it
-easier to see layout objects.</li>
-<li>Several fixes in the configuration selector of the Visual Layout
-Editor.</li>
-</ul>
-</dd>
-<dt>Application launching:</dt>
-<dd>
-<ul>
-<li>Applications launched from ADT now behave as if they were clicked from the
-Home screen.</li>
-<li>Fixes an issue where add-ons without an optional library would not show up as valid
-targets for application launches.</li>
-<li>Resolves a possible crash when launching applications.</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.5</a> <em>(December 2009)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-
-<dd><p>This version of ADT requires features provided in SDK Tools r4 or higher. If you install
-ADT 0.9.5, which is highly recommended, you should use the Android SDK
-Manager to download the latest SDK Tools into your SDK. For more information,
-see <a href="{@docRoot}sdk/exploring.html">Exploring the SDK</a>.</p>
-</dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>The AVD Launch dialog now allows you to set the scale value.</li>
-<li>Fixes a potential NullPointerException in the SDK Manager when you launch an AVD that does not
- have a skin name specified.</li>
-<li>Fixes an XML validation issue in older Java versions.</li>
-<li>.apk packaging now properly ignores vi swap files as well as hidden files.</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>ADT 0.9.4</a> <em>(October 2009)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-
-<dd><p>This version of ADT requires features provided in SDK Tools r3 or higher. If you install
-ADT 0.9.4, which is highly recommended, you should use the Android SDK
-Manager to download the latest SDK Tools into your SDK. For more information,
-see <a href="{@docRoot}sdk/exploring.html">Exploring the SDK</a>.</p>
-</dd>
-
-<dt>Project Creation Wizard:</dt>
-<dd>
-<ul>
-<li>New option to create a project from a sample by choosing it from a list.</li>
-</ul>
-</dd>
-
-<dt>Layout Editor:</dt>
-<dd>
-<ul>
-<li>Improved Configuration selector that lets you see how your layout will
-render on different devices. Default device descriptions include ADP1
-and Google Ion, while SDK add-ons can also provide new descriptions.
-A new UI allows you to create custom descriptions.</li>
-<li>Adds a new clipping toggle, to let you see your full layout even if it's
-bigger than the screen.</li>
-</ul>
-</dd>
-
-<dt>DDMS integration:</dt>
-<dd>
-<ul>
-<li>Includes the improvements from the standalone DDMS, revision 3.</li>
-<li>Adds an option to open HPROF files into eclipse instead of writing them on
-disk. If a profiler such as MAT (<a href="http://eclipse.org/mat">Memory Analyzer
-Tool</a>) is installed, it'll open the file.</li>
-</ul>
-</dd>
-
-<dt>Android SDK and AVD Manager integration:</dt>
-<dd>
-<ul>
-<li>Includes the improvements from the standalone Android SDK and AVD Manager,
-revision 3.</li>
-</ul>
-</dd>
-</dl>
- </div>
-</div>
+++ /dev/null
-page.title=Android 1.5 NDK, Release 1
-sdk.redirect=true
-sdk.redirect.path=ndk/index.html
-excludeFromSuggestions=true
-
-@jd:body
-
+++ /dev/null
-page.title=Android 1.6 NDK, Release 1
-sdk.redirect=true
-sdk.redirect.path=ndk/index.html
-excludeFromSuggestions=true
-
-@jd:body
+++ /dev/null
-page.title=Android NDK
-@jd:body
-
-
-
- <p>The NDK is a toolset that allows you to implement parts
- of your app using native-code languages such as C and C++. Typically, good use cases for the NDK
- are CPU-intensive applications such as game engines, signal processing, and physics simulation.
- </p>
-
- <p>Before downloading the NDK, you should understand that <strong>the NDK
- will not benefit most apps</strong>. As a developer, you need to balance its benefits
- against its drawbacks. Notably, using native code on Android
- generally does not result in a noticable performance improvement,
- but it always increases your app complexity. In general, you should only use the NDK
- if it is essential to your app—never because you simply prefer to program in C/C++.
- When examining whether or not you should develop in native code, think about your requirements and
- see if the Android framework APIs provide the functionality that you need.</p>
-
- <a class="dac-hero-cta" href="{@docRoot}ndk/index.html">
- <span class="dac-sprite dac-auto-chevron"></span> NDK Documentation and Downloads</a>
+++ /dev/null
-excludeFromSuggestions=true
-@jd:body
-
-<script type="text/javascript">
- document.location=toRoot+"about/versions/android-3.0.html"
-</script>
-
-<p>You should have already been redirected by your browser. Please go to the
-<a href="{@docRoot}about/versions/android-3.0.html">Android 3.0 Platform</a>.</p>
\ No newline at end of file
+++ /dev/null
-sdk.redirect=true
-page.template=sdk
-excludeFromSuggestions=true
-@jd:body
+++ /dev/null
-excludeFromSuggestions=true
-@jd:body
-
-<script type="text/javascript">
- document.location=toRoot+"sdk/installing/index.html"
-</script>
-
-<p>You should have already been redirected by your browser. Please go to
-<a href="{@docRoot}sdk/installing/index.html">Installing the SDK</a>.</p>
\ No newline at end of file
+++ /dev/null
-excludeFromSuggestions=true
-@jd:body
-
-<script type="text/javascript">
- document.location=toRoot+"sdk/requirements.html"
-</script>
-
-<p>You should have already been redirected by your browser. Please go to the
-<a href="{@docRoot}sdk/requirements.html">SDK System Requirements</a>.</p>
\ No newline at end of file
+++ /dev/null
-excludeFromSuggestions=true
-@jd:body
-
-<script type="text/javascript">
- document.location=toRoot+"sdk/index.html"
-</script>
-
-<p>You should have already been redirected by your browser. Please go to
-<a href="{@docRoot}sdk/index.html">the Android SDK</a>.</p>
\ No newline at end of file
+++ /dev/null
-page.title=SDK Tools Release Notes
-excludeFromSuggestions=true
-@jd:body
-
-<p>SDK Tools is a downloadable component for the Android SDK. It includes the
-complete set of development and debugging tools for the Android SDK. It is included
-with <a href="{@docRoot}tools/studio/index.html">Android Studio</a>.</p>
-
-<p>If you are already using the SDK and you want to update to the latest version
-of the SDK Tools, use the <a
-href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> to get the
-update.</p>
-
-
-<h2 id="notes">Revisions</h2>
-
-<p>The sections below provide notes about successive releases of
-the SDK Tools, as denoted by revision number. To determine what revision of the SDK
-Tools you are using, refer to the "Installed Packages" listing in the Android SDK Manager. </p>
-
-<p>
- For a summary of all known issues in SDK Tools, visit <a class=
- "external-link" href="http://tools.android.com/knownissues">the Android Tools
- Project Site</a>.
-</p>
-
-<div class="toggle-content opened">
- <p>
- <a href="#" onclick="return toggleContent(this)"><img src=
- "{@docRoot}assets/images/styles/disclosure_up.png" class=
- "toggle-content-img" alt="">SDK Tools, Revision 25.0.0</a>
- <em>(April 2016)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>
- <strong>Android Emulator 2.0</strong>:
- </dt>
-
- <dd>
- <ul>
- <li>Performance improvements:
- </li>
- <ul>
- <li>Emulator now uses CPU acceleration on x86 emulator system images by
- default.
- </li>
-
- <li>Added <a href="{@docRoot}training/articles/smp.html">SMP</a> support
- to take advantage of host multi-core architecture when emulating Android
- 6.0 (API level 23) or higher, resulting in much better performance and
- speed than the physical counterpart. Also with SMP support, you can test
- apps that specifically target multi-core Android devices.
- </li>
-
- <li>Improved data and APK push-pull protocol between the the <a href=
- "{@docRoot}tools/help/adb.html">Android Debug Bridge</a> and devices
- running Android 5.0 (API level 21) or higher. See speed improvements up
- to five times faster than using a physical device.
- </li>
- </ul>
-
- <li>Extended UI controls and a floating toolbar provide easy access to features
- previously available only through the command line, such as taking screen
- captures, adjusting the battery level, rotating the screen, and managing
- virtual calls.
- </li>
-
- <li>Upload KML and GPX files to play back a set of custom location points.
- </li>
-
- <li>Dynamically resize the emulator by dragging a corner or zoom into the
- emulator window.
- </li>
-
- <li>Install APKs or add media files to the emulator’s internal SD card by
- dragging and dropping files into the emulator window.
- </li>
-
- <li>Simulate multi-touch input. While interacting with the emulator screen,
- enter multi-touch mode by holding down the <strong>Ctrl</strong> key on
- Windown/Linux, or <strong>Command</strong> key on Mac OSX.
- </li>
-
- <li>The Android Emulator works best with Android Studio 2.0. To find out more
- about what's included in the newest version of the official Android IDE,
- <a href="{@docRoot}tools/revisions/studio.html#Revisions">read the release
- notes</a>.
- </li>
-
- <li>Read the documentation to find out more about <a href=
- "{@docRoot}tools/devices/emulator.html">using the Android Emulator</a>.
- </li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p>
- <a href="#" onclick="return toggleContent(this)"><img src=
- "{@docRoot}assets/images/styles/disclosure_down.png" class=
- "toggle-content-img" alt="">SDK Platform-tools, Revision 23.1.0</a>
- <em>(December 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>
- General Notes:
- </dt>
-
- <dd>
- <ul>
- <li>Changed Linux requirements for Android SDK Platform-tools
- revision 23.1.0 and later: it now requires 64-bit Linux.
- </li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.4.1</a> <em>(October 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 23 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the emulator title bar was hidden off screen.
- (<a href="http://code.google.com/p/android/issues/detail?id=178344">Issue 178344</a>)</li>
- <li>Enabled the emulator to resize the user data partition by including e2fsprogs binaries.
- (<a href="http://code.google.com/p/android/issues/detail?id=189030">Issue 189030</a>)</li>
- <li>Fixed a regression on the 32-bit Windows OS where the emulator fails to boot Android 6.0
- (API level 23) through Android 5.0 (API level 21) system images.
- (<a href="http://code.google.com/p/android/issues/detail?id=188326">Issue 188326</a>)</li>
- </ul>
- </dd>
-
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.4.0</a> <em>(October 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 23 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Updated the emulator so it can display an upgrade notification when a new version is
- available.</li>
- <li>Added the ability for the emulator to send basic crash reports. You <em>must</em> opt-in
- through Android Studio preferences to enable crash report transmission.</li>
- </ul>
- </dd>
-
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.3.4</a> <em>(August 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 23 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android 6.0 (API level 23) platform.</li>
- </ul>
- </dd>
-
- <dt>Emulator:</dt>
- <dd>
- <ul>
- <li>Improved emulator performance on multi-core Windows desktops.
- (<a href="http://b.android.com/101040">Issue 101040</a>)</li>
- <li>Added support for GPU emulation on Windows and Linux platforms using the
- {@code -gpu mesa} command line option.</li>
- <li>Enabled support for running emulators with GPU emulation through remote desktop
- services, including Chrome Remote Desktop, Windows Terminal Services, and NoMachine.</li>
- <li>Added support for emulators with 280 dpi and 360 dpi screen resolutions.</li>
- <li>Improved support for GLES 2.0 extensions.</li>
- <li>Fixed several issues with GPU emulation support.</li>
- <li>Added support for setting the storage size on emulators using Android 4.4 (API level 19)
- and higher.
- (<a href="http://b.android.com/75141">Issue 75141</a>)</li>
- <li>Fixed problem with sending long SMS messages between emulators.
- (<a href="http://b.android.com/3539">Issue 3539</a>)</li>
- <li>Fixed issue with emulator getting incorrect time from location objects.
- (<a href="http://b.android.com/27272">Issue 27272</a>)</li>
- <li>Added handling for unusual characters in paths and file names when starting emulators.
- (<a href="http://b.android.com/35889">Issue 35889</a>)</li>
- </ul>
- </dd>
-
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.3.3</a> <em>(June 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issues with using Ant build tasks with the Eclipse ADT build structure. </li>
- <li>Fixed the emulator boot problem on Mac OS X 10.8.5.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.3.2</a> <em>(June 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issues with the ARM 64-bit emulator.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.3.1</a> <em>(June 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with the <code>root/</code> and <code>lib/</code> folders. </li>
- </ul>
- <p class="caution"><strong>Caution:</strong> This release is known to contain issues which
- prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2
- as soon as possible. </p>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.3.0</a> <em>(June 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed several minor emulator issues.</li>
- </ul>
- <p class="caution"><strong>Caution:</strong> This release is known to contain issues which
- prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2
- as soon as possible. </p>
- </dd>
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.2.0</a> <em>(May 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed several minor emulator issues.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.1.2</a> <em>(February 2015)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed boot failures of MIPS system images on Mac OS X.</li>
- <li>Fixed AVD screen capture issues when using GPU emulation.</li>
- <li>Fixed memory leaks in emulator system.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.0.2</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with creating projects and activities from templates using Eclipse ADT.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.0.1</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed Java detection issue on 32-bit Windows systems.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 24.0.0</a> <em>(December 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android Studio 1.0 and emulator enhancements.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 23.0.5</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 23.0.4 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.4.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed Windows 32-bit compilation issue.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 23.0.4</a> <em>(October 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 23.0.4 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.4.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed duplicate devices in AVD for Wear and TV.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 23.0.2</a> <em>(July 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 23.0.2 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.2.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added ProGuard <code>.bat</code> files that were missing.</li>
- <li>Added the <code>proguard-android.txt</code> file that was missing.</li>
- <li>Renamed the <code>lombok-ast-0.2.2.jar</code> file to <code>lombok-ast.jar</code>,
- which should allow running lint from the command line.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 23.0.0</a> <em>(June 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 19 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 23.0.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added the Android Wear tools and system images.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.6.4</a> <em>(June 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.6.3 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.3.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed an issue with the x86 emulator that caused Google Maps to crash.
- (<a href="http://b.android.com/69385">Issue 69385</a>)</li>
- <li>Fixed minor OpenGL issues.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.6.3</a> <em>(April 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.6.3 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.3.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the AVD manager allowed creating Android Wear virtual devices
- with a target API Level lower than 19.</li>
- <li>Fixed the description of Android Wear system images in the SDK Manager.</li>
- </ul>
- </dd>
-
- <dt>Known Issues:</dt>
- <dd>
- <p>When you create an Android Wear virtual device in the AVD manager, a target API Level
- lower than 19 may be selected by default. Make sure you select the target API Level 19
- when creating Android Wear virtual devices.</p>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.6.2</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.6.2 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.2.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the SDK Manager threw a <code>NullPointerException</code> after
- removing a virtual device that was created using the Android Wear
- system image. (<a href="http://b.android.com/67588">Issue 67588</a>)</li>
- <li>Fixed a problem with Nexus 5 Android virtual devices created from the command line
- where the SD card file system was read-only.</li>
- </ul>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.6.1</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
-
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.6.1 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.1.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed a problem where the Android Virtual Device Manager could not create new virtual
- devices. (<a href="http://b.android.com/66661">Issue 66661</a>)</li>
- <li><p>Fixed a problem with virtual devices created using ADT 22.3 or earlier.</p>
- <p>If you created an Android Virtual Device using ADT 22.3 or earlier, the
- AVD may be listed as <em>broken</em> in the AVD Manager in 22.6.1. To fix
- this problem, select the virtual device on the AVD Manager and click
- <strong>Repair</strong>.</p>
- </li>
- <li>Fixed a problem with the command line tools when creating virtual devices.
- (<a href="http://b.android.com/66740">Issue 66740</a>)</li>
- <li>Fixed a problem with the command line <code>lint</code> script.</li>
- </ul>
- </dd>
-
- <dt>Known Issues:</dt>
- <dd>
- <p>When you create an Android virtual device using the Nexus 5 device definition,
- you must enable the <em>Use Host GPU</em> option, otherwise the virtual device
- will not start.</p>
- </dd>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.6</a> <em>(March 2014)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.6.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li><p>The command line <code>lint</code> script (<code>tools\lint.bat</code> on
- Windows platforms, <code>tools/lint</code> on other platforms) and the
- <code>lint</code> target on <code>ant</code> builds fail with the following
- error:</p>
- <p><code>Exception in thread "main" java.lang.NoClassDefFoundError:
- lombok/ast/AstVisitor</code></p>
- <p>As a temporary workaround, rename the file
- <code>tools\lib\lombok-ast-0.2.2.jar</code> to
- <code>tools\lib\lombok-ast.jar</code>.
- We will release an updated version of the tools with a fix for
- this issue as soon as possible.</p>
- </li>
- <li>Added support for Java 7 language features like multi-catch, try-with-resources,
- and the diamond operator. These features require version 19 or higher
- of the Build Tools. Try-with-resources requires <code>minSdkVersion</code>
- 19; the rest of the new language features require
- <code>minSdkVersion</code> 8 or higher.</li>
- <li>Added new lint checks:
- <ul>
- <li>Security:
- <ul>
- <li>Look for code potentially affected by a <code>SecureRandom</code>
- vulnerability.</li>
- <li>Check that calls to <code>checkPermission</code> use the return value.</li>
- </ul>
- </li>
- <li>Check that production builds do not use mock location providers.</li>
- <li>Look for manifest values that are overwritten by values from Gradle build
- scripts.</li>
- </ul>
- </li>
- <li>Fixed a number of minor issues in the SDK and build system.</li>
- <li>Emulator:
- <ul>
- <li>Fixed a problem with the emulator shutting down immediately for Android 1.5
- on the Nexus One and Nexus S devices.
- (<a href="http://b.android.com/64945">Issue 64945</a>)</li>
- <li>Fixed a problem with port numbers longer than four digits.
- (<a href="http://b.android.com/60024">Issue 60024</a>)</li>
- <li>Fixed battery errors for the Nexus One and Nexus S devices.
- (<a href="http://b.android.com/39959">Issue 39959</a>)</li>
- <li>Fixed a problem with paths or arguments that contain
- spaces on Windows platforms.
- (<a href="http://b.android.com/18317">Issue 18317</a>)</li>
- <li>Fixed a problem with long path values on Windows platforms.
- (<a href="http://b.android.com/33336">Issue 33336</a>)</li>
- <li>Fixed a problem with the {@code -snapshot-list} command line
- option on 64-bit systems.
- (<a href="http://b.android.com/34233">Issue 34233</a>)</li>
- </ul>
- </li>
- <li>Fixed an issue with RenderScript support. Using RenderScript support mode
- now requires version 19.0.3 of the Build Tools.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.3</a> <em>(October 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 18 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.3.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.3.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Added support for Android 4.4 (API level 19).</li>
- <li>Fixed a number of minor bugs in the SDK and build system.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.2.1</a> <em>(September 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.2.1 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.2.1.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed problem with templates that causes the new project wizard to hang.
- (<a href="http://b.android.com/60149">Issue 60149</a>)</li>
- <li>Fixed crash when using the lint command line tool because of mis-matched library
- dependency. (<a href="http://b.android.com/60190">Issue 60190</a>)</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.2</a> <em>(September 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.2 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.2.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Updated build tools to allow use of RenderScript on older versions of Android
- using new features in the
- <a href="{@docRoot}tools/support-library/features.html#v8">Support Library</a>.</li>
- <li>Moved the Systrace tool to the {@code >sdk</platform-tools/} directory. </li>
- <li>Modified <a href="{@docRoot}tools/help/gltracer.html">Tracer for OpenGL ES</a> to
- support OpenGL ES 3.0.</li>
- <li>Lint
- <ul>
- <li>Fixed problem with lint not detecting custom namespaces.
- (<a href="http://b.android.com/55673">Issue 55673</a>)</li>
- <li>Fixed problem with the XML report including invalid characters.
- (<a href="http://b.android.com/56205">Issue 56205</a>)</li>
- <li>Fixed command-line execution of lint to work in headless mode to support execution
- by build servers. (<a href="http://b.android.com/55820">Issue 55820</a>)</li>
- </ul>
- </li>
- <li>Improved support for path names with spaces in the Windows command-line tools.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.0.5</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with the
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a>, note that this version of
- SDK Tools is designed for use with ADT 22.0.5 and later. If you haven't already, update
- ADT to 22.0.5.</li>
- <li>If you are using <a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>,
- note that this version of the SDK Tools is designed to work with Android Studio
- 0.2.x and later.</li>
- <li>If you are developing without an integrated development environment (IDE), you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed RenderScript compilation issue for Windows platforms with ant.</li>
- <li>Updated <a href="{@docRoot}tools/help/systrace.html">Systrace</a> to work with the
- Android 4.3 platform image.</li>
- <li>Fixed packaging of RenderScript compiler.</li>
- <li>Build tools 18.0.0 is obsolete and 18.0.1 should be used instead.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.0.4</a> <em>(July 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with the
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a>, note that this version of
- SDK Tools is designed for use with ADT 22.0.4 and later. If you haven't already, update
- ADT to 22.0.4.</li>
- <li>If you are using <a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>,
- note that this version of the SDK Tools is designed to work with Android Studio
- 0.2.x and later.</li>
- <li>If you are developing without an integrated development environment (IDE), you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed problem with compiling RenderScript code.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22.0.1</a> <em>(May 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.0.1 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.0.1.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Fixed issue with Lint ServiceCast check and fully qualified class names.
- (<a href="http://code.google.com/p/android/issues/detail?id=55403">Issue 55403</a>)</li>
- <li>Fixed crash issue with Lint ArraySizeDetector check.
- (<a href="http://code.google.com/p/android/issues/detail?id=54887">Issue 54887</a>)</li>
- <li>Fixed a problem with the monkeyrunner tool failing to import standard python classes.
- (<a href="http://code.google.com/p/android/issues/detail?id=55632">Issue 55632</a>)</li>
- <li>Fixed a problem with DDMS monitor not opening heap and network statistics views due to
- a class not found exception.
- (<a href="http://code.google.com/p/android/issues/detail?id=55394">Issue 55394</a>)</li>
- </ul>
-
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 22</a> <em>(May 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 22.0.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Changed the structure of the SDK by adding a new build tool SDK Component, which is
- based on the existing platform-tools component. This change decouples the build tools
- versions from the IDE versions, allowing updates to the tools without requiring an
- IDE update.</li>
- <li>Updated tools to allow libraries to share the same package name as the applications
- that use them.</li>
- <li>Updated {@code draw9patch} tool to allow easier changing of markers.</li>
- <li>Added new Lint checks, including checks for layout consistency,
- {@link android.widget.RelativeLayout} siblings, {@link android.os.Parcel} creator,
- JavaScript interfaces, {@link android.app.Service} casting, quantity strings, manifest
- typos, orientation tags in layouts, overlapping names for 9-patches and images, and class
- existence checks.</li>
- <li>Updated build tools to sign applications using the BouncyCastle library instead of
- relying on Sun JVM specific APIs.</li>
- <li>Released some of the Android tools into <a href="http://www.maven.org">Maven
- Central</a> to assist third-party tool developers. The following tools are available
- in the repository: {@code manifest-merger}, {@code common/sdk_common}, {@code ddmlib},
- {@code dvlib}, {@code layoutlib_api}, {@code sdklib}, and {@code lint}.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed a number of minor bugs in the SDK and build system.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 21.1</a> <em>(February 2013)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 21.1.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 21.1.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Improved error reporting in {@code dx} when dex merging fails in the build
- system.</li>
- <li>Added more than 15 new Lint checks, including checks for overriding older APIs, XML
- resource problems, graphic asset issues and manifest tags.</li>
- <li>Added new aapt feature to compile resources.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 21.0.1</a> <em>(December 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
- designed for use with ADT 21.0.1 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 21.0.1.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Build
- <ul>
- <li>Updated build to detect and handle package name conflicts between an application and
- the libraries it depends on. Libraries cannot share package names unless all of them
- share the same package name.
- (<a href="http://code.google.com/p/android/issues/detail?id=40152">Issue 40152</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=40273">Issue 40273</a>)
- </li>
- <li>Added a flag to disable dex merging to deal with cases where merging could generate
- a broken dex file. If this happens to your project, add the following setting to your
- {@code project.properties} file: {@code dex.disable.merger=true} This setting
- causes the build system to revert to the older, slower dex processing that does not
- pre-dex libraries.</li>
- </ul>
- </li>
-
- <li>RenderScript
- <ul>
- <li>Added support for
- <a href="{@docRoot}guide/topics/renderscript/compute.html#filterscript">Filterscript</a>
- compilation.</li>
- <li>Added new project setting to control the RenderScript compilation target separately
- from an Android project. Adding the following line to a {@code project.properties}
- file causes RenderScript code to be compiled for Android API Level 17, while the
- containing application can target a different (lower) API level:
- <pre>renderscript.target = 17</pre>
- Previously, the RenderScript compilation target was tied to the
- {@code android:minSdkVersion} setting in the manifest.
- (<a href="http://code.google.com/p/android/issues/detail?id=40487">Issue 40487</a>)
- </li>
- </ul>
- </li>
-
- </ul>
- </dd>
-
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Lint
- <ul>
- <li>Corrected check for {@code 0px} values in style XML elements.
- (<a href="http://code.google.com/p/android/issues/detail?id=39601">Issue 39601</a>)
- </li>
- <li>Fixed incorrect flagging of formatting strings.
- (<a href="http://code.google.com/p/android/issues/detail?id=39758">Issue 39758</a>)
- </li>
- <li>Fixed problem where {@code tools:ignore} directive in the manifest file was ignored
- by the Lint tool.
- (<a href="http://code.google.com/p/android/issues/detail?id=40136">Issue 40136</a>)
- </li>
- <li>Fixed problem with flagging a wakelock release inside a conditional.
- (<a href="http://code.google.com/p/android/issues/detail?id=40424">Issue 40424</a>)
- </li>
- <li>Fixed incorrect reporting of missing {@code layout_width} and {@code layout_height}
- XML fields.
- (<a href="http://code.google.com/p/android/issues/detail?id=38958">Issue 38958</a>)
- </li>
- <li>Fixed handling of custom namespace attributes.</li>
- <li>Added fixes for filtering out library project warnings.</li>
- <li>Removed warnings about missing classes before a build.</li>
- </ul>
- </li>
-
- <li>Fixed problem with UI Automator Viewer execution script where Android tools directory
- is not set.</li>
- <li>Fixed problem with the SDK Manager so that it auto-selects the most recently released
- platform on startup.</li>
- <li>Fixed Java finding script to look for the currently supported version of Java (1.6 or
- higher).</li>
- <li>Fixed the SDK Manager launcher in the ADT bundle so that it can properly launch the
- SDK Manager program when it is placed at the root of the bundle.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 21</a> <em>(November 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 16 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed
- for use with ADT 21.0.0 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 21.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
-
- <dt>General Notes:</dt>
- <dd>
- <ul>
- <li>Build System
- <ul>
- <li>Added a flag that sets <em>jumbo mode</em> for DEX files, which allows a larger
- number of strings in the DEX files. Enable this mode by adding the following line to
- the {@code project.properties} file of your project:
- <pre>dex.force.jumbo=true</pre></li>
- <li>Improved the build time by pre-dexing libraries (both JAR files and library
- projects).</li>
- <li>Updated the build to generate {@code R} resource classes for library projects
- with only the IDs needed by the libraries, reducing the risk of hitting DEX file
- limits for fields and methods.</li>
- <li>Improved the build so that several editing features (code completion, resource
- chooser, go to declaration) properly handle library project resources.</li>
- </ul>
- </li>
- <li>Lint
- <ul>
- <li>Added over 25 new lint rules for resources, locale settings, layout
- files, incorrect use of {@link android.util.SparseArray} and
- {@link android.os.PowerManager.WakeLock} and manifest issues.</li>
- <li>Updated reporting to include errors in library projects if the library project is
- in the list of projects to be checked.</li>
- <li>Added a new {@code lint} target to the Ant build system for easier
- integration with continuous build systems.</li>
- <li>Added new {@code --sources} and {@code --classpath} arguments to point to sources
- with different directory structures.</li>
- <li>Improved the XML export function to support the <a
- href="https://wiki.jenkins-ci.org/display/JENKINS/Android+Lint+Plugin">Jenkins Lint
- plugin</a>.
- </li>
- <li>Added support for class file flow analysis.</li>
- </ul>
- </li>
- <li>Android Virtual Devices (AVD)
- <ul>
- <li>Added new <strong>Device Definitions</strong> tab in the AVD Manager for configuring
- standard size and Nexus virtual devices.</li>
- <li>Improved emulators so that they launch with a skin that is dynamically generated and
- reflects the actual hardware configured in the AVD Manager.</li>
- <li>Improved support for developing Android apps on MIPS-based devices with new MIPS
- System Images for Android Virtual Devices.</li>
- </ul>
- </li>
- <li>Added {@code jobb} tool for creating and encrypting
- <a href="{@docRoot}google/play/expansion-files.html">APK Expansion Files</a>.
- (<a href="{@docRoot}tools/help/jobb.html">more info</a>)
- <li>Improved the Android JUnit test runner to allow a test to be run on all connected
- devices simultaneously.</li>
- </ul>
- </dd>
-
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed manifest merger to properly adapt library classes in the merged manifest.</li>
- </ul>
- </dd>
-
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 20.0.3</a> <em>(August 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 12 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed
- for use with ADT 20.0.3 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 20.0.3.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed problem with cached download lists in SDK Manager.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 20.0.1</a> <em>(July 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 12 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed
- for use with ADT 20.0.1 and later. If you haven't already, update your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 20.0.1.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed wrong check on build state that forced repetitive Java code recompilation.</li>
- <li>Fixed problems with running more than one emulator and running multiple emulators
-with GPU acceleration.</li>
- <li>Improved resize algorithm for better rendering on scaled emulator windows.</li>
- <li>Fixed a bug in the {@code lint} check for unprotected broadcast receivers to ignore
-unprotected receivers for default Android actions.</li>
- <li>Fixed build issue for projects using RenderScript.</li>
- <li>Fixed memory leak in the emulator.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 20</a> <em>(June 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 12 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for
- use with ADT 20.0.0 and later. If you haven't already, we highly recommend updating your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 20.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>General notes:</dt>
- <dd>
- <ul>
- <li>Added new Device Monitor application, grouping Android debugging tools into a
-single application, including ddms, traceview, hierarchyviewer and Tracer for GLES. (<a
-href="{@docRoot}tools/help/gltracer.html">more info</a>)</li>
- <li>Added new System Trace new tool for tracing Android system activity. This tool allow you
-to capture a slice of system activity, plus additional information tagged from the <strong>Settings
-> Developer Options > Monitoring: Enable traces</strong> or with specific calls added to your
-application code.</li>
- </li>
- <li>Build System
- <ul>
- <li>Added automatic merging of library project manifest files into the including
-project's manifest. Enable this feature with the {@code manifestmerger.enabled} property.</li>
- <li>Added automatic ProGuard support for the {@code aapt -G} flag. This change causes
-the build system to generate a temporary ProGuard {@code keep-rules} file containing classes that
-are referenced from XML files (such as custom views) and pass this to ProGuard at shrink time. This
-can make the resulting APK much smaller when using just a small portion of a large library project
-(such as the Android Support library), since the catch-all rules to keep all custom views from the
-default ProGuard configuration file have also been removed.</li>
- <li>Added two ProGuard configuration files for use in projects: {@code
-proguard-android-optimize.txt} which enables optimizations and {@code proguard-android.txt} which
-disables them.</li>
- </ul>
- </li>
- <li>SDK Manager
- <ul>
- <li>Improved caching to reduce downloading of repository definitions.</li>
- <li>Added <strong>Tools > Manage Add-on Sites</strong> option to improve performance by
- allowing temporary deactivation of third-party sites if they are loading slowly.</li>
- <li>Added settings for the SDK Manager download cache (<strong>SDK Manager > Tools >
-Options</strong>).</li>
- </ul>
- </li>
- </ul>
- </dd>
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Build
- <ul>
- <li>Fixed problem where test projects did not have access to the full classpath of tested
-projects, including Library Projects and third-party jars.</li>
- <li>Fixed deployment logic so that applications with embedded tests can now be deployed
-and tested like test applications, including code coverage information.</li>
- <li>Fixed Ant support for testing projects with libraries.</li>
- </ul>
- </li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 19</a> <em>(April 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="note"><strong>Note:</strong> This update of SDK Tools is only available through
-the <a href="{@docRoot}sdk/exploring.html">Android SDK Manager</a>. Use this tool to
-download and install this update.</p>
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 9 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for
- use with ADT 18.0.0 and later. If you haven't already, we highly recommend updating your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 18.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed an issue that prevented some developers from running the emulator with GPU
-acceleration.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 18</a> <em>(April 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="caution"><strong>Important:</strong> To download the new Android
- 4.0 system components from the Android SDK Manager, you must first update the
- SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not,
- the Android 4.0 system components will not be available for download.</p>
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 9 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for
- use with ADT 18.0.0 and later. If you haven't already, we highly recommend updating your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 18.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>General notes:</dt>
- <dd>
- <ul>
- <li>Updated the SdkController app to encapsulate both sensor and multitouch emulation
- functionality.</li>
- </ul>
- </dd>
- <dt>Bug fixes:</dt>
- <dd>
- <ul>
- <li>Fixed Ant issues where some jar libraries in the {@code libs/} folder are not picked up
-in some cases.</li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 17</a> <em>(March 2012)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="caution"><strong>Important:</strong> To download the new Android
- 4.0 system components from the Android SDK Manager, you must first update the
- SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not,
- the Android 4.0 system components will not be available for download.</p>
-
- <dl>
- <dt>Dependencies:</dt>
- <dd>
- <ul>
- <li>Android SDK Platform-tools revision 9 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for
- use with ADT 17.0.0 and later. If you haven't already, we highly recommend updating your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 17.0.0.</li>
- <li>If you are developing outside Eclipse, you must have
- <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li>
- </ul>
- </dd>
- <dt>General notes:</dt>
- <dd>
- <ul>
- <li>Emulator
- <ul>
- <li>Added support for hardware accelerated graphics rendering. This feature requires an
-API Level 15, Revision 3 or later system image.
-(<a href="{@docRoot}tools/devices/emulator.html#accel-graphics">more info</a>)
- </li>
- <li>Added support for running Android x86 system images in virtualization mode on
-Windows and Mac OS X.
-(<a href="{@docRoot}tools/devices/emulator.html#accel-vm">more info</a>)
- <p class="note"><strong>Note:</strong> Use the Android SDK Manager to download and
-install x86 system images. Android x86 system images are not available for all API levels.</p>
- </li>
- <li>Added experimental support for multi-touch input by enabing the emulator to receive
- touch input from a USB-tethered physical Android device.
- (<a href="http://tools.android.com/tips/hardware-emulation">more info</a>)</li>
- </ul>
- </li>
- <li>Added viewing of live detailed network usage of an app in DDMS. (<a
- href="http://tools.android.com/recent/detailednetworkusageinddms">more info</a>)</li>
- <li>ProGuard
- <ul>
- <li>Updated the bundled ProGuard tool to version 4.7. In addition to many new features,
-this update fixes the {@code Conversion to Dalvik format failed with error 1} error some users have
-experienced.</li>
- <li>Updated the default {@code proguard.cfg} file with better default flags for
- Android.</li>
- <li>Split the ProGuard configuration file has been in half, with project specific flags
-kept in project and the generic Android flags distributed (and updated) with the tools
-themselves.</li>
- </ul>
- </li>
- <li>Build
- <ul>
- <li>Added a feature that allows you to run some code only in debug mode. Builds now
-generate a class called {@code BuildConfig} containing a {@code DEBUG} constant that is
-automatically set according to your build type. You can check the ({@code BuildConfig.DEBUG})
-constant in your code to run debug-only functions.</li>
- <li>Fixed issue when a project and its libraries include the same jar file in their libs
- folder. (<a href="http://tools.android.com/recent/dealingwithdependenciesinandroidprojects">more
- info</a>)</li>
- <li>Added support for custom views with custom attributes in libraries. Layouts using
-custom attributes must use the namespace URI {@code http://schemas.android.com/apk/res-auto} instead
-of the URI that includes the app package name. This URI is replaced with the app specific one at
-build time.</li>
- </ul>
- </li>
- <li>Lint
- <ul>
- <li>Updated Lint to check Android application code. Lint rules which previously
-performed pattern based searches in the application code (such as the unused resource check) have
-been rewritten to use the more accurate Java-style parse trees.</li>
- <li>Added support for checking library projects. This change means that rules such as
-the unused resource check properly handle resources declared in a library project and referenced in
-a downstream project.</li>
- <li>Added ability to suppress Lint warnings in Java code with the new
-{@code @SuppressLint} annotation, and in XML files with the new tools: namespace and
-ignore attribute. (<a
- href="http://tools.android.com/recent/ignoringlintwarnings">more info</a>)</li>
- <li>New Lint checks:
- <ul>
- <li>Added check for Android API calls that require a version of Android higher than
- the minimum supported version. You can use the new {@code @TargetApi} annotation
- to suppress warnings when the code is wrapped in a system version condition.
- (<a href="http://tools.android.com/recent/lintapicheck">more info</a>)</li>
- <li>Added over 20 new Lint rules, including checks for
- <a href="http://tools.android.com/recent/lintperformancechecks">performance</a>,
- XML layouts, manifest and file handling.</li>
- </ul>
- </li>
- </ul>
- </li>
- </ul>
- </dd>
- </dl>
- </div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 16</a> <em>(December 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="caution"><strong>Important:</strong> To download the new Android
- 4.0 system components from the Android SDK Manager, you must first update the
- SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not,
- the Android 4.0 system components will not be available for download.</p>
-
-<dl>
-<dt>Dependencies:</dt>
-<dd>
- <ul>
- <li>Android SDK Platform-tools revision 9 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use
- with ADT 16.0.0 and later. If you haven't already, we highly recommend updating your
- <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 16.0.0.</li>
- <li>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
- Ant</a> 1.8 or later.</li>
-</ul>
-</dd>
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>Added Lint tools to detect common errors in Android projects.
- (<a href="http://tools.android.com/recent/lint">more info</a>)</li>
- <li>Added sensor emulation support, which allows the emulator to read sensor data from a
- physical Android device.
- (<a href="http://tools.android.com/recent/sensoremulation">more info</a>)</li>
- <li>Added support for using a webcam to emulate a camera on Mac OS X.</li>
- </ul>
-</dd>
-<dt>Bug fixes:</dt>
-<dd>
- <ul>
- <li>Snapshots now work for Android 4.0 system images.</li>
- <li>Fixed several small issues for the build file.
- (<a href="http://code.google.com/p/android/issues/detail?id=21023">Issue 21023</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=21267">Issue 21267</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=21465">Issue 21465</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=21525">Issue 21525</a>).</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 15</a> <em>(October 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="caution"><strong>Important:</strong> To download the new Android
- 4.0 system components from the Android SDK Manager, you must first update the
- SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not,
- the Android 4.0 system components will not be available for download.</p>
- <dl>
-<dt>Dependencies:</dt>
-<dd>
- <ul><li>Android SDK Platform-tools revision 9 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use
- with ADT 15.0.0 and later. If you haven't already, we highly recommend updating your <a
- href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 15.0.0.</li>
- <li>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
- Ant</a> 1.8 or later.</li>
-</ul>
-
-<dt>Bug fixes:</dt>
-<dd>
- <ul>
- <li>Fixed emulator crash on Linux due to improper webcam detection
- (<a href="http://code.google.com/p/android/issues/detail?id=20952">Issue 20952</a>).</li>
- <li>Fixed emulator issue when using the <code>-wipe-data</code> argument.</li>
- <li>Fixed build issue when using RenderScript in projects that target API levels 11-13
- (<a href="http://code.google.com/p/android/issues/detail?id=21006">Issue 21006</a>).</li>
- <li>Fixed issue when creating an AVD using the GoogleTV addon
- (<a href="http://code.google.com/p/android/issues/detail?id=20963">Issue 20963</a>).</li>
- <li>Fixed <code>ant test</code>
- (<a href="http://code.google.com/p/android/issues/detail?id=20979">Issue 20979</a>).</li>
- <li>Fixed <code>android update project</code>
- (<a href="http://code.google.com/p/android/issues/detail?id=20535">Issue 20535</a>).</li>
- <li>Fixed scrolling issue in the new Logcat panel of DDMS.</li>
- <li>Fixed issue with MonkeyRunner
- (<a href="http://code.google.com/p/android/issues/detail?id=20964">Issue 20964</a>).</li>
- <li>Fixed issues in the SDK Manager
- (<a href="http://code.google.com/p/android/issues/detail?id=20939">Issue 20939</a>,
- <a href="http://code.google.com/p/android/issues/detail?id=20607">Issue 20607</a>).</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 14</a> <em>(October 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <p class="note"><strong>Important:</strong> To download the new Android
- 4.0 system components from the Android SDK Manager, you must first update the
- SDK tools to revision 14 and restart the Android SDK Manager. If you do not,
- the Android 4.0 system components will not be available for download.</p>
- <dl>
-<dt>Dependencies:</dt>
-<dd>
- <ul><li>Android SDK Platform-tools revision 8 or later.</li>
- <li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use
- with ADT 14.0.0 and later. If you haven't already, we highly recommend updating your <a
- href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 14.0.0.</li>
- <li>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
- Ant</a> 1.8 or later.</li>
-</ul>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>Added webcam support to Android 4.0 or later platforms to emulate rear-facing cameras when
- one webcam is present, and to emulate both rear-facing and front-facing cameras when two
- webcams are present. Webcam support is for Windows and Linux only.
- Mac support will come in a later release.</li>
- <li>Changed <code>default.properties</code> to <code>project.properties</code> and
- <code>build.properties</code> to <code>ant.properties</code>. Any existing
- projects that you build with Ant must be updated with the <code>android update project</code>
- command.</li>
- <li>Changed Ant <code>build.xml</code> file to support improvements to the
- build system and added and modified Ant commands to support these changes. For a list of Ant
-commands, see the
-<a href="{@docRoot}tools/building/building-cmdline.html#AntReference">Ant Command
-Reference</a>.</li>
- <li>Changed how library projects are built.</li>
- <li>Improved incremental builds, so that resource compilation runs less frequently. Builds no
- longer run when you edit strings or layouts (unless you add a new <code>id</code>) and no longer
- run once for each library project.</li>
- <li>Introduced a "PNG crunch cache" that only runs on modified PNG files, instead of
- crunching all existing PNG files, all the time.</li>
- <li>Revamped the SDK Manager UI (<a href="http://tools.android.com/recent/newsdkmanager">more
-info</a>).</li>
- </ul>
- <p>For a complete overview of the build system changes and what you need to do to support them,
-see the <a href="http://tools.android.com/recent/buildchangesinrevision14">Android Tools Project
-site</a>.</p>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 13</a> <em>(September 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with
-ADT 12.0.0 and later. If you haven't already, we highly recommend updating your <a
-href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 12.0.0.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>Fix compilation issue in Ant (<code>dex</code> step) when paths have spaces.</li>
- <li>Fix issue in emulator installation when paths have spaces.</li>
- <li>Fix issue when AVD paths have spaces.</li>
- <li>Fix rendering issue when using emulator scaling (<a href="http://code.google.com/p/android/issues/detail?id=18299">see more</a>).</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 12</a> <em>(July 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with
-ADT 12.0.0 and later. If you haven't already, we highly recommend updating your <a
-href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 12.0.0.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>The AVD manager and emulator can now use system images
- compiled for ARM v7 and x86 CPUs.</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 11</a> <em>(May 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with
-ADT 10.0.1 and later. If you haven't already, we highly recommend updating your <a
-href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 10.0.1.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>Miscellaneous emulator changes to support Android 3.1.</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 10</a> <em>(February 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 10.0.0 and later. After installing SDK Tools r10, we
-highly recommend updating your ADT Plugin to 10.0.0.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>The tools now automatically generate Java Programming Language source files (in the
-<code>gen</code> directory) and
- bytecode (in the <code>res/raw</code> directory) from your native <code>.rs</code> files</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 9</a> <em>(January 2011)</em>
- </p>
-
- <div class="toggle-content-toggleme">
- <dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 9.0.0 and later. After installing SDK Tools r9, we
-highly recommend updating your ADT Plugin to 9.0.0.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<dt>Upgrading to SDK Tools r9:</dt>
-<dd>
-<p>If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed location
-for the <code>adb</code> tool has changed from <code><<em>SDK</em>>/tools/adb</code> to
-<code><<em>SDK</em>>/platform-tools/adb</code>. This means that you should
-add the new location to your PATH and modify any custom build scripts to
-reference the new location. Copying the <code>adb</code> executable from the new
-location to the old is not recommended, since subsequent updates to the SDK
-Tools will delete the file.</p>
-</dd>
-
-<dt>General notes:</dt>
-<dd>
- <ul>
- <li>The default ProGuard configuration, <code>proguard.cfg</code>, now ignores the following classes:
- <ul>
- <li>classes that extend {@link android.preference.Preference}</li>
- <li>classes that extend {@link android.app.backup.BackupAgentHelper}</li>
- </ul>
- </li>
- <li>Ant lib rules now allow you to override <code>java.encoding</code>, <code>java.source</code>,
- and <code>java.target</code> properties.</li>
- <li>The default encoding for the <code>javac</code> Ant task is now UTF-8.</li>
- <li>The LogCat view in DDMS now properly displays UTF-8 characters.</li>
- <li>The SDK Manager is more reliable on Windows. For details on the improvements, see the
- <a href="http://tools.android.com/recent/sdkmanagerfixes">Android Tools Project Site</a>. </li>
- <li>Early look at the new snapshot feature: To improve startup time for the emulator, you can
-enable snapshots for the system state. The emulator will then restore to the state when it last
-closed almost instantly. <strong>Note:</strong> The snapshot feature is still under active
-development and might not always perform as expected.</li>
- <li>Fixed the missing JAR file error that prevented <code>draw9patch</code> from running.</li>
- <li>Fixed the Windows launch scripts <code>hierarchyviewer</code> and <code>ddms</code> to support
- the new location of <code>adb</code>.</li>
- <li>Known issues with emulator performance: Because the Android emulator must simulate the ARM
-instruction set architecture on your computer, emulator performance is slow. We're working hard to
-resolve the performance issues and it will improve in future releases.</li>
- </ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 8</a> <em>(December 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 8.0.0 and later. After installing SDK Tools r8, we
-highly recommend updating your ADT Plugin to 8.0.0.</p>
-
-<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache
-Ant</a> 1.8 or later.</p>
-
-<p>Also note that SDK Tools r8 requires a new SDK component called
-<em>Platform-tools</em>. The new Platform-tools component lets all SDK platforms
-(Android 2.1, Android 2.2, and so on) use the same (latest) version of build
-tools such as <code>adb</code>, <code>aapt</code>, <code>aidl</code>, and
-<code>dx</code>. To download the Platform-tools component, use the Android SDK
-Manager, as described in <a href="{@docRoot}sdk/exploring.html">Exploring the
-SDK</a></p>
-
-<dt>Upgrading from SDK Tools r7:</dt>
-<dd>
-<p>If you are upgrading to SDK Tools r8 from an earlier version, note that the
-the default installed location for the <code>adb</code> tool has changed from
-<code><<em>SDK</em>>/tools/adb</code> to
-<code><<em>SDK</em>>/platform-tools/adb</code>. This means that you should
-add the new location to your PATH and modify any custom build scripts to
-reference the new location. Copying the <code>adb</code> executable from the new
-location to the old is not recommended, since subsequent updates to the SDK
-Tools will delete the file.</p>
-</dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>All SDK platforms now support Library Projects.</li>
-<li>Support for a true debug build. Developers no longer need to add the
-<code>android:debuggable</code> attribute to the
-<code><application></code> tag in the manifest — the build tools add
-the attribute automatically. In Eclipse/ADT, all incremental builds are assumed
-to be debug builds, so the tools insert <code>android:debuggable="true"</code>.
-When exporting a signed release build, the tools do not add the attribute. In
-Ant, a <code>ant debug</code> command automatically inserts the
-<code>android:debuggable="true"</code> attribute, while <code>ant release</code>
-does not. If <code>android:debuggable="true"</code> is manually set, then
-<code>ant release</code> will actually do a debug build, rather than a release
-build.</li>
-<li>Automatic ProGuard support in release builds. Developers generate a ProGuard
-configuration file using the <code>android</code> tool — the build tools
-then automatically run ProGuard against the project sources during the build.
-For more information, see the <a
-href="{@docRoot}tools/help/proguard.html">ProGuard</a>
-documentation. </li>
-<li>New overridable Ant javac properties: <code>java.encoding</code>,
-<code>java.source</code>, and <code>java.target</code> (default values are
-"ascii", "1.5", and "1.5", respectively).</li>
-<li>New UI for the HierarchyViewer tool.</li>
-</ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 7</a> <em>(September 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 0.9.8 and later. After installing SDK Tools r7, we
-highly recommend updating your ADT Plugin to 0.9.8.</p>
-</dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>Added support for library projects that depend on other library projects.</li>
-<li>Adds support for aidl files in library projects.</li>
-<li>Adds support for extension targets in Ant build to perform tasks between the
-normal tasks: <code>-pre-build</code>, <code>-pre-compile</code>, and
-<code>-post-compile</code>.</li>
-<li>Adds support for "headless" SDK update. See <code>android -h update sdk</code>
-for more information.</li>
-<li>Fixes location control in DDMS to work in any locale not using '.' as a
-decimal point.</li>
-</ul>
-</ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 6</a> <em>(May 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd>
-<p>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 0.9.7 and later. After installing SDK Tools r6, we
-highly recommend updating your ADT Plugin to 0.9.7.</p>
-</dd>
-
-<dt>Library projects:</dt>
-<dd>
-<p>The SDK Tools now support the use of <em>library projects</em> during
-development, a capability that lets you store shared Android application
-code and resources in a separate development project. You can then reference the
-library project from other Android projects and, at build time, the tools
-compile the shared code and resources as part of the dependent applications.
-More information about this feature is available in the <a
-href="{@docRoot}tools/projects/index.html#LibraryProjects">Creating and Managing Projects</a> document.</p>
-<p>If you are developing in Eclipse, <a href="eclipse-adt.html">ADT</a>
-provides the equivalent library project support.</p>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 5</a> <em>(March 2010)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd><ul>
-<li>If you are developing in Eclipse with ADT, note that this version of SDK Tools is
-designed for use with ADT 0.9.6 and later. After installing SDK Tools r5, we
-highly recommend updating your ADT Plugin to 0.9.6.</li>
-<li>For Mac OS platforms, OS X 10.4.x (Tiger) is no longer
-officially supported. </li>
-</ul>
-</dd>
-
-<dt>SDK and AVD Manager:</dt>
-<dd>
-<ul>
-<li>Fixes SSL download for the standalone version of the SDK Updater.</li>
-<li>Fixes issue with 64-bit JVM on Windows.</li>
-<li>Adds support for platform samples components.</li>
-<li>Improves support for dependency between components.</li>
-<li>AVDs now sorted by API level.</li>
-<li>The AVD creation dialog now enforces a minimum SD card size of 9MB.</li>
-<li>Prevents deletion of running AVDs.</li>
-<li>Settings are now automatically saved, no need to click "Apply".</li>
-</ul>
-</dd>
-
-<dt>Emulator:</dt>
-<dd>
-<ul>
-<li>Emulator now requires SD card to be 9MB or more.</li>
-</ul>
-</dd>
-
-<dt>Layoutopt:</dt>
-<dd>
-<ul>
-<li>Fixes <code>layoutopt.bat</code> to execute correctly on Windows.</li>
-</ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 4</a> <em>(December 2009)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd><p>This version of SDK Tools is compatible with ADT 0.9.5 and later, but not
-compatible with earlier versions. If you are developing in Eclipse with ADT, you
-<strong>must</strong> update your ADT plugin to version 0.9.5 or higher if you
-install SDK Tools r4 in your SDK. </p></dd>
-
-<dt>General notes:</dt>
-<dd>
-<ul>
-<li>Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix a
-compatibility issue between GTK and SWT.</li>
-</ul>
-</dd>
-
-<dt>Android SDK and AVD Manager:</dt>
-<dd>
-<ul>
-<li>AVD Launch dialog now shows scale value.</li>
-<li>Fixes potential NPE in SDK Manager on AVD launch, for older AVD with no
-skin name specified.</li>
-<li>Fixes XML validation issue in on older Java versions.</li>
-<li>No longer forces the use of Java 1.5 on Mac OS X.</li>
-</ul>
-</dd>
-
-<dt>Emulator:</dt>
-<dd>
-<ul>
-<li>No longer limits the size of the system partition.</li>
-</ul>
-</dd>
-
-<dt>Ant build tools:</dt>
-<dd>
-<ul>
-<li>.apk packaging now properly ignores vi swap files as well as hidden files.</li>
-</ul>
-</dd>
-</dl>
-</div>
-</div>
-
-<div class="toggle-content closed">
- <p><a href="#" onclick="return toggleContent(this)">
- <img src="{@docRoot}assets/images/styles/disclosure_down.png" class="toggle-content-img"
- alt=""/>SDK Tools, Revision 3</a> <em>(October 2009)</em>
- </p>
-
- <div class="toggle-content-toggleme">
-<dl>
-<dt>Dependencies:</dt>
-<dd><p>This version of SDK Tools is compatible with ADT 0.9.4 and later, but not
-compatible with earlier versions. If you are developing in Eclipse with ADT, you
-<strong>must</strong> update your ADT plugin to version 0.9.4 or higher if you
-install SDK Tools r3 in your SDK.</p>
-</dd>
-
-<dt>Android tool:</dt>
-<dd>
-<ul>
-<li>Adds new <code>android create test-project</code> and <code>android update
-test-project</code> commands to allow for greater flexibility in the location of the
-main and test projects.</li>
-</ul>
-</dd>
-
-<dt>DDMS:</dt>
-<dd>
-<ul>
-<li>Adds a button to dump HPROF file for running applications (app must be able
-to write to the sdcard).</li>
-<li>Button to start/stop profiling of a running application (app must be able to
-write to the sdcard). Upon stop, Traceview will automatically be launched to
-display the trace.</li>
-<li>Fixed DDMS, Traceview, and the AVD Mananger/SDK Updater to run on Mac OS X
-10.6.</li>
-<li>Fixed screenshot support for devices running 32-bit framebuffer.</li>
-</ul>
-</dd>
-
-<dt>Android SDK and AVD Manager:</dt>
-<dd>
-<ul>
-<li>Provides a new UI that lets you set options for controlling
-the emulator skin, screen size/density, and scale factor used when launching
-an AVD.</li>
-<li>Provides improved AVD creation UI, which lets you customize the hardware
-properties of your AVDs.</li>
-<li>Now enforces dependencies between platforms and tools components, and
-between SDK add-ons and platforms.</li>
-</ul>
-</dd>
-
-<dt>Layoutopt, a new tool for optimizing layouts:</dt>
-
-<dd><p>The SDK Tools r3 package includes <code>layoutopt</code>, a new command-line
-tool that helps you optimize your layout hierarchies. When run against your
-layout files, the tool analyzes their hierarchies and notifies you of
-inefficiencies and other potential issues. The tool also provides simple
-solutions for the issues it finds. For usage, see <a
-href="/tools/help/layoutopt.html">layoutopt</a>.</p>
-</dd>
-</dl>
-</div>
-</div>
+++ /dev/null
-page.title=Android Studio Code Tools
-
-@jd:body
-
-<p>
- Android Studio provides a number of coding features to assist with writing and building your
- app. These tools help you write code faster and improve quality.
-</p>
-
-<dl>
- <dt><a href="{@docRoot}tools/debugging/improving-w-lint.html">Lint</a></dt>
- <dd>The Lint tool is a static code analysis tool that checks your Android
- project source files for potential bugs and optimization improvements.</dd>
-
- <dt><a href="{@docRoot}tools/debugging/annotations.html">Code Annotations</a></dt>
- <dd>Annotations help you improve code readability and improve code inspector output,
- by allowing you to more clearly define method parameter requirements.
- </dd>
-
- <dt><a href="{@docRoot}tools/help/app-link-indexing.html">URL and App Indexing
- Support</a></dt>
- <dd>Android Studio helps you add support for URLs, app indexing, and search
- functionality to your apps. These features can help to drive more traffic
- to your app, discover which app content is used most, make it easier for
- users to find content in an installed app, and attract new users.
- </dd>
-
-</dl>
-
-
+++ /dev/null
-page.title=Transition Guide for Eclipse ADT
-@jd:body
-
-
-<div id="qv-wrapper">
-<div id="qv">
-
-<h2>In this document</h2>
- <ol>
- <li><a href="#project-structure">Project Structure</a></li>
- <li><a href="#manifest-settings">Manifest Settings</a></li>
- <li><a href="#dependencies">Dependencies</a></li>
- <li><a href="#build-process">Gradle-based Build Process</a></li>
- <li><a href="#debug-inspect">Debugging and Code Inspections</a></li>
- <li><a href="#resource-optimization">Resource Optimization</a></li>
- <li><a href="#signing">App Signing</a></li>
- <li><a href="#support-lib">Android Support Repository and Google Play services Repository</a></li>
- <li><a href="#app-package">App Packaging</a></li>
- <li><a href="#software-updates">Software Updates </a></li>
- <li><a href="#version-control">Version Control</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a class="external-link"
- href="http://confluence.jetbrains.com/display/IntelliJIDEA/FAQ+on+Migrating+to+IntelliJ+IDEA">
- IntelliJ FAQ on migrating to IntelliJ IDEA</a></li>
- <li><a class="external-link"
- href="https://confluence.jetbrains.com/display/IntelliJIDEA/IntelliJ+IDEA+for+Eclipse+Users">
- IntelliJ IntelliJ for Eclipse Users</a></li>
- <li><a href="{@docRoot}tools/studio/index.html">Android Studio Overview</a> </li>
- </ol>
-
-</div>
-</div>
-
-
-<p>This document describes the differences between Eclipse ADT and Android Studio, including project
- structure, build system, debugging, and application packaging. This guide is intended to help you
- transition to using Android Studio as your development environment.</p>
-
-<h2 id="project-structure">Project Structure </h2>
-<p>Eclipse provides workspaces as a common area for grouping related projects, configurations, and
-settings. In Android Studio, each instance of Android Studio contains a top-level project with one
-or more app modules. Each app module folder contains the equivalent to an Eclipse
-project, the complete source sets for that module, including {@code src/main} and
-{@code src/androidTest} directories, resources, build file, and the Android manifest. In general,
-to update and build your app you modify the files under each module's
-{@code src/main} directory for source code updates, the <code>gradle.build</code> file for
-build specification, and the files under {@code src/androidTest} directory for test case creation. </p>
-
-<p>You can also customize the view of the project files in Android Studio to focus on specific
-aspects of your app development: </p>
-
-<ul>
- <li><em>Packages</em> </li>
- <li><em>Project Files</em> </li>
- <li><em>Scratches</em> </li>
- <li><em>Problems</em> </li>
- <li><em>Production</em> </li>
- <li><em>Tests</em> </li>
-</ul>
-
-
-<p>The following table shows the general mapping of the Eclipse ADT project structure and file
-locations to Android Studio.</p>
-
-<p class="table-caption" id="table-project-structure-mapping">
- <strong>Table 1.</strong> Project structure mapping.</p>
-
-<table>
- <tr>
- <th scope="col">Eclipse ADT</th>
- <th scope="col">Android Studio</th>
- </tr>
-
- <tr>
- <td>Workspace </td>
- <td>Project </td>
- </tr>
-
- <tr>
- <td>Project </td>
- <td>Module </td>
- </tr>
-
- <tr>
- <td>Project-specific JRE </td>
- <td>Module JDK </td>
- </tr>
-
- <tr>
- <td>Classpath variable </td>
- <td>Path variable</td>
- </tr>
-
- <tr>
- <td>Project dependency</td>
- <td>Module dependency</td>
- </tr>
-
- <tr>
- <td>Library Module</td>
- <td>Library </td>
- </tr>
-
- <tr>
- <td><code>AndroidManifest.xml</code></td>
- <td><code>app/src/main/AndroidManifest.xml</code> </td>
- </tr>
- <tr>
- <td><code>assets/</code></td>
- <td><code>app/src/main/assets</code> </td>
- </tr>
- <tr>
- <td><code>res/</code></td>
- <td><code>app/src/main/res/</code> </td>
- </tr>
- <tr>
- <td><code>src/</code></td>
- <td><code>app/src/main/java/ </code> </td>
- </tr>
- <tr>
- <td><code>tests/src/</code></td>
- <td><code>app/src/androidTest/java/</code> </td>
- </tr>
-
- </table>
-
-
-
-<p>Table 2 shows Eclipse ADT and Android Studio project views. </p>
-
-<p class="table-caption" id="table2">
- <strong>Table 2.</strong> Comparing project views.</p>
-<table>
- <tbody><tr>
- <th>Eclipse ADT</th>
- <th>Android Studio Project View</th>
- <th>Android Studio Android View</th>
- </tr>
- <tr>
- <td><img src="{@docRoot}images/tools/eclipse-notepad-pre-import--structure.png"/> </td>
- <td><img src="{@docRoot}images/tools/studio-import-project-structure-project.png"/> </td>
- <td><img src="{@docRoot}images/tools/studio-import-project-structure-android.png"/> </td>
- </tr>
- </tbody>
-</table>
-
-
-<p class="note"><strong>Note:</strong> Multiple instances of Android Studio can be used to develop
-independent projects. </p>
-
-
-
-
-<h2 id="manifest-settings">Manifest Settings</h2>
-<p>Android Studio and <a href="http://www.gradle.org">Gradle</a>-based builds support
-<a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants"> build variants</a>,
-which are combinations of <code>productFlavor</code> and <code>buildTypes</code>, to customize
-your build outputs. To support these custom builds, several elements in the
-<code>AndroidManifest.xml</code> file are now properties in the <code>defaultConfig</code> and
-<code>productFlavors</code> blocks in the <code>build.gradle</code> file. The import process
-copies these manifest settings to the properties in the <code>build.gradle</code> file.
-These properties overwrite the settings in any other manifest files as shown in table 3. </p>
-
-<p class="table-caption" id="table-manifest-gradle-settings">
- <strong>Table 3.</strong> Manifest and Gradle property settings.</p>
-<table>
- <tr>
- <th scope="col">Manifest Setting</th>
- <th scope="col">build.gradle Setting</th>
- </tr>
- <tr>
- <td><code><uses-sdk</code> <br>
- <p><code>android:minSdkVersion</code></p>
- <p><code>android:targetSdkVersion /></code></p>
- </td>
- <td> <br>
- <p><code>minSdkVersion</code></p>
- <p><code>targetSdkVersion</code></p> </td>
- </tr>
- <tr>
- <td><code><manifest</code>
- <p>package (Required in the default manifest file.) </p>
- <p><code>android:versionCode</code></p>
- <p><code>android:versionName /></code></p>
- </td>
- <td> <br>
- <p><code>applicationId</code> (See
- <a href="{@docRoot}tools/studio/index.html#app-id"> Application ID
- for Package Identification</a>)</p>
- <p><code>versionCode</code></p>
- <p><code>versionName</code></p> </td>
- </tr>
-
- </table>
-
-
-<p>Although these settings may no longer appear in the default app manifest file, they are still
-valid manifest entries and may still appear in manifests from older projects, imported projects,
-dependencies, and libraries.</p>
-
-<p>The <code>package</code> element must still be specified in the manifest file. It is used in
-your source code to refer to your <code>R</code> class and to resolve any relative activity/service
-registrations. </p>
-
-<p class="note"><strong>Note:</strong> When multiple manifests are present in your app, for
-example a library manifest and a <code>src/main/</code> manifest, the build process combines
-the manifest settings into a single merged manifest based on the manifest priority and
-manifest merge settings. For more information about the manifest merge process and merge settings,
-see
-<a href="{@docRoot}tools/building/manifest-merger.html"> Manifest Merger</a>. </p>
-
-
-<h2>Application ID for package identification </h2>
-<p>With the Android build system, the <code>applicationId</code> attribute is used to
-uniquely identify application packages for publishing. The application ID is set in the
-<code>android</code> section of the <code>build.gradle</code> file. This field is populated in the
-build file as part of the migration process. </p>
-
-<pre>
-apply plugin: 'com.android.application'
-
-android {
- compileSdkVersion 19
- buildToolsVersion "19.1"
-
- defaultConfig {
- <strong>applicationId "com.example.my.app"</strong>
- minSdkVersion 15
- targetSdkVersion 19
- versionCode 1
- versionName "1.0"
- }
- ...
-</pre>
-
-<p class="note"><strong>Note:</strong> The <code>applicationId</code> is specified only in your
-<code>build.gradle</code> file, and not in the <code>AndroidManifest.xml</code> file.</p>
-
-<p><a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants">Build variants</a>
-enable you to uniquely identify different
-packages for each product flavor and build type. The application ID in the build type setting can
-be added as a suffix to the ID specified for the product flavors. The following example adds the
-<code>.debug</code> suffix to the application ID of the <code>pro</code> and <code>free</code>
-product flavors: </p>
-
-<pre>
-productFlavors {
- pro {
- applicationId = "com.example.my.pkg.pro"
- }
- free {
- applicationId = "com.example.my.pkg.free"
- }
-}
-
-buildTypes {
- debug {
- applicationIdSuffix ".debug"
- }
-}
-....
-</pre>
-
-
-
-<h2 id="dependencies">Dependencies</h2>
-<p>During the import process, Android Studio imports the current Eclipse ADT dependencies and
-downloads any project libraries as Android Studio modules. The dependency declarations are added to
-the <code>build.gradle</code> file. The declarations include a
-<a href="#scopes">dependency scope</a>, such as
-<code>compile</code>, to specify in which builds the dependency is included. </p>
-
-<p>The following example shows how to add an external library JAR dependency so it's included in
-each compile:</p>
-
-<pre>
-dependencies {
- compile files('libs/*.jar')
-}
-
-android {
- ...
-}
-</pre>
-
-<p class="note"><strong>Note:</strong> Android Studio supports the Android ARchive (AAR) format
-for the distribution of Android library projects as dependencies. For more information, see
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>. </p>
-
-
-<p>The import process replaces any well-known source libraries, binary libraries, and JAR files
-that have known Maven coordinates with Maven dependencies, so you no longer need to
-maintain these dependencies manually. </p>
-
-<p>Android Studio enables access to Maven, JCenter, and Ivy repositories with the
-<code>repositories</code> block in the <code>build.gradle</code> as a shortcut to specifying
-the URL of the repository.
-
-<p>If there are required repositories not declared in the <code>build.gradle</code> file, first add
-the repository to the <code>repositories</code> block, and then declare the dependencies in a way
-that Maven, JCenter, or Ivy declare their artifacts. The following example shows how to add the
-Maven repository with the guava 11.0.2 dependency using the <code>mavenCentral()</code> property: </p>
-
-<pre>
-repositories {
- mavenCentral()
-}
-
-android {
- ...
-}
-
-dependencies {
- compile 'com.google.guava:guava:11.0.2'
- instrumentationtestCompile 'com.squareup.fast-android:1:0.4'
-}
-
-</pre>
-
-<p>The Android Studio project created during the import process can also re-use any
-dependencies on other components. These components can be external binary packages or other
-<a href="http://www.gradle.org">Gradle</a> projects. If a dependency has dependencies of its own,
-those dependencies are also included in the new Android Studio project. </p>
-
-
-<p class="note"><strong>Note:</strong> If there were references to Eclipse ADT workspace library
-files in the <code>project.properties</code> or <code>.classpath</code> files
-that were not imported from the Eclipse project, you can now add dependencies to these library files
-in the <code>build.gradle</code> file. For more information, see
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>. </p>
-
-
-<h3 id="scopes">Dependency and compilation scopes </h3>
-<p>Android Studio supports compilation scopes to customize which dependencies get
-included in each build, for example assigning different dependencies to different
-<a href="{@docRoot}tools/building/configuring-gradle.html#workBuildVariants"> build variants</a>.</p>
-
-<p>This list shows the Android Studio scope names and definitions: </p>
-
-<ul>
- <li>compile - <code>compile</code> </li>
- <li>run time - <code>package</code></li>
- <li>testCompile - <code>AndroidTestCompile</code></li>
- <li>testRuntime - <code>AndroidTestRunPackage</code></li>
- <li>buildTypeCompile - <code>buildTypeCompile</code> </li>
- <li>productFlavorCompile - <code>productFlavorCompile</code> </li>
-</ul>
-
-<p class="note"><strong>Note:</strong> Dependencies for library projects must be added with the
-<code>compile</code> scope. </p>
-
-
-<p>With the <a href="http://www.gradle.org">Gradle</a>-based DSL, you can also add custom
-dependency scopes, such as <code>betaCompile file('libs/protobug.jar')</code> to define a beta
-build dependency. </p>
-
-<p>The scope and compilation configuration in the build file determine the
-components compiled into the app, added to the compilation classpath, and packaged in the final
-APK file. Based on the dependency and compilation scope, different compilation configurations
-can be specified to include the dependencies and classpaths, for example: </p>
-
-<ul>
-<li><code>compile</code> - for the main application. </li>
-<li><code>androidTestCompile</code> - for the test application. </li>
-<li><code>debugCompile</code> - for the debug buildType application.</li>
-<li><code>releaseCompile</code> - for the release buildType application. </li>
-</ul>
-
-<p class="note"><strong>Note:</strong> Because it’s not possible to build an APK that does not
-have an associated <code>buildType</code>, the APK built from your app is always configured with
-at least two dependency and compile configurations: <code>compile</code> and
-<code>debugCompile</code>. </p>
-
-<p>Unlike Eclipse ADT, by default Android Studio does not compile your code when there are changes.
-Use the <strong>File > Settings > Build, Execution, Deployment Compiler</strong> option
-to enable automatic compilation. </p>
-
-
-
-<h2 id="build-process">Gradle-based Build Process </h2>
-<p>Android Studio imports the Eclipse ADT Ant-based
-build tasks and converts the tasks to <a href="http://www.gradle.org">Gradle</a>-based build tasks.
-These new build tasks include the
-main <code>assemble</code> task and at least two outputs based on the default build types:
-a <code>debug</code> APK and a
-<code>release</code> APK. Each of these build tasks has its own Android build system anchor task
-to facilitate building them independently: </p>
-<ul>
- <li><code>assemble</code></li>
- <li><code>assembleDebug</code></li>
- <li><code>assembleRelease</code></li>
-</ul>
-
-<p>In Android Studio, you can view all the supported build tasks in the
-<em>Gradle</em> project tab. </p>
-
-<p>With the <a href="http://www.gradle.org">Gradle</a>-based build system, Android Studio uses a
-<a href="http://www.gradle.org">Gradle</a> wrapper to fully integrate the
-Android Plugin for Gradle. The Android Plugin for Gradle also
-runs independent of Android Studio. This means that with Android Studio build system your build
-output is always the same, whether you build your Android apps from Android Studio, from the
-command line on your machine, or on machines where Android Studio is not installed (such as
-continuous integration servers). </p>
-
-<p>Unlike Eclipse ADT with dependent plugin and build updates, the <code>build.gradle</code>
-files allow you to customize the build settings for each Android Studio module and build variant,
-so the build versions can be set independently, and are not dependent on the Android Studio
-or build tools versions. This makes it easy to maintain and build legacy apps along with your
-current app, using build variants to generate different APKs from the same app modules, but
-built with different build versions and build chains. </p>
-
-<p>For more details about the Android Studio build system, see
-<a href="{@docRoot}sdk/installing/studio-build.html">Build System Overview</a>.</p>
-
-<h3>Using the Android Studio build system's declarative logic </h3>
-<p>In contrast with the XML statements in Ant build files, the Android build system and
-<a href="http://www.gradle.org">Gradle</a> DSL provide a declarative build language so you can
-easily extend the Gradle-based build process beyond the typical XML build tasks. For example,
-this build file shows how to define a custom function to inject a dynamic <code>versionCode</code>
-in build outputs: </p>
-
-<pre>
-def getVersionCode) {
- def code = …
- return code
-}
-
-android {
- defaultConfig {
- versionCode getVersionCode()
- …
- }
-}
-</pre>
-
-<p>This example shows how to append <em>debug</em> to your package and version names used in the
-<code>debug</code> build variant of your app: </p>
-
-<pre>
-android {
- buildTypes {
- debug {
- packageNameSuffix ‘.debug’
- versionNameSuffix ‘-DEBUG’
- }
- beta {
- …
- }
- }
-}
-</pre>
-
-
-<p>You can also use the declarative DSL in the Android build system to generate custom build
-versions, for example a debuggable version of your release APK. This examples adds the
-<code>debuggable true</code> property to the <code>release</code> build type in the
-<code>build.gradle</code> file to build an identical debuggable version of the release package. </p>
-
-<pre>
-android {
- buildTypes {
- debugRelease.initWith(buildTypes.release)
- debugRelease {
- debuggable true
- packageNameSuffix '.debugrelease'
- signingConfig signingConfigs.debug
- }
-
- }
- sourceSets.debugRelease.setRoot('src/release')
-}
-</pre>
-
-
-
-
-
-
-<h2 id="debug-inspect">Debugging and Code Inspections</h2>
-<p>Using code inspection tools such as <a href="{@docRoot}tools/help/lint.html">lint</a> is a
-standard part of Android development. Android Studio extends
-<a href="{@docRoot}tools/help/lint.html">lint</a> support with additional
-<a href="{@docRoot}tools/help/lint.html">lint</a> checks and supports Android
-<a href="{@docRoot}tools/debugging/annotations.html">annotations</a> that
-allow you to help detect more subtle code problems, such as null pointer exceptions and resource
-type conflicts. Annotations are added as metadata tags that you attach to variables, parameters,
-and return values to inspect method return values, passed parameters, and local variables and
-fields. </p>
-
-<p>For more information on enabling <a href="{@docRoot}tools/help/lint.html">lint</a> inspections
-and running <a href="{@docRoot}tools/help/lint.html">lint</a>,
-see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.
-For more information about using annotations, see
-<a href="{@docRoot}tools/debugging/annotations.html#annotations">Improving your Code with
-Annotations</a>. </p>
-
-<p>In addition to code inspection, Android Studio provides an integrated
-<a href="{@docRoot}tools/studio/index.html#mem-cpu">memory and CPU monitor</a> view so you
-can more easily monitor your app's performance and memory usage to track CPU usage, find
-deallocated objects, locate memory leaks, and track the amount of memory the connected device is
-using. </p>
-
-
-
-<h2 id="resource-optimization">Resource Optimization </h2>
-<p>After importing and building your app, Android Studio supports several
-<a href="http://www.gradle.org">Gradle</a>-based properties to help you minimize your app's
-resource utilization. </p>
-
-
-<h3>Resource shrinking</h3>
-<p>In Android Studio, resource shrinking enables the automatic removal of unused resources from
-your packaged app and also removes resources from library dependencies if the resources are not
-actually used by your app.</p>
-
-<p>Use the <code>shrinkResources</code> attribute in the <code>buildType</code> block in your
-<code>build.gradle</code> file to enable resource shrinking. For example, if your application is
-using <a href="{@docRoot}google/play-services/index.html">Google Play services</a>
-to access Google Drive functionality, and you are not currently using
-<a href="{@docRoot}google/play-services/plus.html">Google+ Sign In</a>, then
-this setting removes the various drawable assets for the <code>SignInButton</code> buttons. </p>
-
-<p class="note"><strong>Note:</strong> Resource shrinking works in conjunction with code shrinking
-tools, such as <a href="{@docRoot}tools/help/proguard.html">ProGuard</a>. </p>
-
-<p>To enable resource shrinking, update the <code>buildTypes</code> block in the
-<code>build.gradle</code> file to include <code>minifyEnabled true</code>,
-<code>shrinkResources true</code>, and <code>proguardFiles</code> settings as shown in the
-following example <a href="http://www.gradle.org">Gradle</a> build file.</p>
-
-<pre>
-android {
- ...
-
- buildTypes {
- release {
- minifyEnabled true
- shrinkResources true
- proguardFiles getDefaultProguardFile('proguard-android.txt'),
- 'proguard-rules.pro'
- }
- }
-}
-</pre>
-
-
-
-<h3>Filtering language resources</h3>
-<p>Use the <code>resConfig</code> attribute in your <code>build.gradle</code> file
-to filter the locale resources included in your packaged app. This filtering can be especially
-useful when library dependencies such as <code>appcompat-v7</code> and other libraries such as
-<code>google-play-services_lib</code> are included in your app. </p>
-
-<p>The following example limits the locale resources to three language settings: <code>en</code>,
-<code>de</code>, and <code>es</code>:</p>
-
-<pre>
-apply plugin: 'android'
-
-android {
- compileSdkVersion 22
- buildToolsVersion "22.0.1"
-
- defaultConfig {
- minSdkVersion 8
- targetSdkVersion 22
- versionCode 1
- versionName "1.0"
- resConfigs "en", "de", "es" //Define the included language resources.
- }
-...
-
-</pre>
-
-
-
-<h4>Filtering bundled resources</h4>
-<p>You can also use the <code>resConfig</code> build setting to limit the bundled resources
-in any resource folder. For example, you could also add <code>resConfigs</code>
-settings for density folders, such as <code>mdpi</code> or <code>hdpi</code> to limit the drawable
-resources that are packaged in your <code>APK</code> file. This example limits the app's
-bundled resources to medium-density (MDPI) and high-density (HDPI) resources. </p>
-
-<pre>
-android {
- defaultConfig {
- ...
- resConfigs "mdpi", "hdpi"
- }
-}
-</pre>
-
-For more information about screen and resource densities, see
-<a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>
-and <a href="{@docRoot}training/multiscreen/screendensities.html">Supporting Different Densities</a>.
-
-
-<h3>Resource merging </h3>
-<p>With Android Studio, identical resources, such as copies of launcher and menu icons, may end up
-in different resource folders throughout your app. To reduce resource duplication and improve
-the performance of your app, Android Studio merges resources with an identical resource name, type,
-and qualifier into a single resource and passes the single, merged resource to the Android Asset
-Packaging Tool (AAPT) for distribution in the APK file. </p>
-
-<p>The resource merging process looks for identical resources in the following <code>/res/</code>
-folders: </p>
-<ul>
- <li>AAR bundles of library project dependencies</li>
- <li><code>src/main/</code> </li>
- <li><code>src/<em>productFlavor</em>/</code> </li>
- <li><code>src/<em>buildType</em>/</code> </li>
-</ul>
-
-<p>Identical resources are merged in the following low to high priority order: </p>
-<pre>
-dependencies --> src/main/ --> src/productFlavor/ --> src/buildType/
-</pre>
-
-<p>For example, if the <code>res/ic_menu.png</code> file is included in both the
-<code>src/main/res/</code> and <code>src/productFlavor/res/</code> folders, the resources are merged
-so only the file with the higher priority, in this case the <code>src/productFlavor/res/</code>
-file, is included in the APK file. </p>
-
-<p class="note"><strong>Note:</strong> Identical resources in the same source set are not merged
-and instead generate a resource merge error. This can happen if the <code>sourceSet</code> property
-in the <code>build.gradle</code> file is used to define multiple source sets, for example
-<code>src/main/res/</code> and <code>src/main/res2/</code>, and these folders contain identical
-resources. </p>
-
-
-
-
-<h2 id="signing">App Signing and ProGuard </h2>
-<p>Based on the imported Eclipse ADT app settings, Android Studio automatically sets up your app
-signing and maintains any ProGuard settings. </p>
-
-<h3>App Signing</h3>
-<p>If your app used a debug certificate in Eclipse ADT, Android Studio continues to reference that
-certificate. Otherwise, the <code>debug</code> configuration uses the Android Studio generated
-debug keystore, with a known password and a default key with a known password located in
-<code>$HOME/.android/debug.keystore</code>. The <code>debug</code> build type is set to use this
-debug <code>SigningConfig</code> automatically when you run or debug your project
-from Android Studio. </p>
-
-<p>In release mode, Android Studio applies the release certificate used in Eclipse ADT. If no
-release certificate was located during the import process, add the release signing configuration to
-the <code>build.gradle</code> file or use the <strong> Build > Generate Signed APK</strong> menu
-option to open the Generate Signed APK Wizard. For more information about signing your app, see
-<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>. </p>
-
-
-<h3>ProGuard</h3>
-<p>If the <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> option is specified in the
-<code>project.properties</code> file in the Eclipse ADT project, Android Studio imports the
-<a href="{@docRoot}tools/help/proguard.html">ProGuard</a> files and adds the
-<a href="{@docRoot}tools/help/proguard.html">ProGuard</a> settings to the
-<code>build.gradle</code> file. <a href="{@docRoot}tools/help/proguard.html">ProGuard</a> is
-supported through the <code>minifyEnabled</code> property as shown in this example. </p>
-
-<pre>
-android {
- buildTypes {
- release {
- minifyEnabled true
- proguardFile getDefaultProguardFile('proguard-android.txt')
- }
- }
-
- productFlavors {
- flavor1 {
- }
- flavor2 {
- proguardFile 'some-other-rules.txt'
- }
- }
-}
-
-</pre></p>
-
-
-
-
-<h2 id="support-lib">Android Support Repository and Google Play services Repository</h2>
-<p>While Eclipse ADT uses the Android <a href="{@docRoot}tools/support-library/index.html">Support
-Library</a> and Google Play services Library, Android Studio replaces these libraries during the
-import process with the Android Support Repository and Google Repository to maintain
-compatible functionality and support new Android features. Android Studio adds these dependencies
-as Maven dependencies using the known Maven coordinates, so these dependencies do not require
-manual updates. </p>
-
-<p>In Eclipse, in order to use a
-<a href="{@docRoot}tools/support-library/index.html">Support Library</a>, you must modify your
-project's classpath dependencies within your development environment for each
-<a href="{@docRoot}tools/support-library/index.html">Support Library</a> you want to use. In
-Android Studio, you no longer need to copy library sources into your
-own projects, you can simply declare a dependency and the library is automatically downloaded and
-merged into your project. This includes automatically merging in resources, manifest entries,
-<a href="{@docRoot}tools/help/proguard.html">ProGuard</a> exclusion rules, and custom lint rules
-at build time. </p>
-
-<p>Android Studio also supports binary library Android ARchives (AARs). AARs are a library project's
-main output as a combination of compiled code (as a jar file and/or native .so files) and
-resources (manifest, res, assets). <p/>
-
-
-<h2 id="app-package">App Packaging</h2>
-<p>The Android build system introduces the use of the <code>applicationId</code> attribute to
-uniquely identify application packages for publishing. The application ID is set in the
-<code>android</code> section of the <code>build.gradle</code> file. </p>
-
-<p>The <code>applicationId</code> is specified only in your <code>build.gradle</code> file, and
-not in the
-<code>AndroidManifest.xml</code> file. The Gradle-based build system enables you
-to uniquely identify different packages for each build variant based on product flavors and build
-types. You can also add the <code>applicationIdSuffix</code> property to the build type in the
-<code>build.gradle</code> file to append an identifier, such as '.debug', to the application ID
-generated for each product flavor. </p>
-
-
-
-<h2 id="software-updates">Software Updates</h2>
-<p>Android Studio provides several levels of update and maintenance to help you keep Android Studio
-up-to-date based on your code-level preference: </p>
-
-<ul>
- <li><strong>Canary channel</strong>: Canary builds provide bleeding edge releases and are updated
- about weekly. These builds do get tested, but are still subject to bugs, as these are
- early releases. This is not recommended for production.</li>
- <li><strong>Dev channel</strong>: Dev builds are canary builds that passed initial testing and
- usage. They are updated roughly bi-weekly or monthly.</li>
- <li><strong>Beta channel</strong>: Beta builds provide beta-quality releases for final testing
- and feedback before a production release.</li>
- <li><strong>Stable channel</strong>: Stable builds provide stable, production-ready release
- versions.</li>
-</ul>
-
-
-
-<h2 id="version-control">Version Control </h2>
-<p>Eclipse ADT supports version control through the use of plugins, such as the EGit and Subversive
-plug-ins. </p>
-
-<p>Android Studio supports a variety of version control systems (Git, GitHub, CVS, Mercurial,
-Subversion, and Google Cloud) so version control operations can continue from within Android
-Studio. </p>
-
-<p>After importing your Eclipse ADT app into Android Studio, use the
-Android Studio <em>VCS</em> menu options to enable VCS support for the desired version control
-system, create a repository, import the new files into version control, and perform other version
-control operations. </p>
-
-<p class="note"><strong>Note:</strong> You can also use the
-<strong>File > Setting > Version Control</strong> menu option to setup and modify the version
-control settings. </p>
-
-<h3>Files to ignore </h3>
-<p>A number of Android Studio files are typically not added to version control as these are
-temporary files or files that get overwritten with each build. These files are listed in
-an exclusion file, such as <code>.gitignore</code>, for the project and each app module.
-Typically, the following files are excluded from version control: </p>
-
-<ul>
- <li>.gradle </li>
- <li>/local.properties </li>
- <li>/.idea/workspace.xml </li>
- <li>/.idea/libraries </li>
- <li>.DS_Store</li>
- <li>/build </li>
- <li>/captures </li>
-</ul>
+++ /dev/null
-page.title=Android Studio Overview
-page.image=images/cards/card-android-studio-overview_16x9_2x.jpg
-page.metaDescription=The basics of working with Android Studio, from projects to build and performance.
-page.tags=studio,sdk,tools,firstapp
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#project-structure">Project Structure</a></li>
- <li><a href="#build-system">Gradle Build System</a></li>
- <li><a href="#debug-perf">Debug and Profile Tools</a></li>
- </ol>
-
-
-<a class="button" href="{@docRoot}sdk/index.html" style="margin:15px">
- Get Android Studio
-</a>
-
-</div>
-</div>
-
-
-<p>Android Studio is the official IDE for Android app development, based on
-<a class="external-link" href="https://www.jetbrains.com/idea/" target=
-"_blank">IntelliJ IDEA</a>. On top of IntelliJ's powerful code editor and
-developer tools, Android Studio offers even more features that enhance your
-productivity when building Android apps, such as:</p>
-
-
-<ul>
- <li>A flexible Gradle-based build system</li>
- <li>Build variants and multiple APK file generation</li>
- <li>Code templates to help you build common app features</li>
- <li>A rich layout editor with support for drag and drop theme editing</li>
- <li>Lint tools to catch performance, usability, version compatibility, and other problems</li>
- <li>Code shrinking with ProGuard and resource shrinking with Gradle</li>
- <li>Built-in support for
- <a href="http://developers.google.com/cloud/devtools/android_studio_templates/">Google Cloud Platform</a>,
- making it easy to integrate Google Cloud Messaging and App Engine</li>
-</ul>
-
-<p>This page provides an introduction to basic Android Studio features. For
-more detailed guides to using Android Studio, start by browsing pages in the
-<a href="{@docRoot}tools/workflow/index.html">Workflow</a> section.</p>
-
-<p>For a summary of the latest changes, see the <a href=
-"{@docRoot}tools/revisions/studio.html">Android Studio Release Notes</a>.</p>
-
-
-
-<h2 id="project-structure">Project Structure</h2>
-
-<div class="figure" style="width:230px">
-<img src="{@docRoot}images/tools/studio/studio-project-files.png" width="230" />
-<p class="img-caption"><strong>Figure 1.</strong> The project files in Android
-view.</p>
-</div>
-
-<p>Each project in Android Studio contains one or more modules with source code
-files and resource files. Different types of modules include:</p>
-
-<ul>
-<li>Android app modules</li>
-<li>Test modules</li>
-<li>Library modules</li>
-<li>App Engine modules</li>
-</ul>
-
-<p>By default, Android Studio displays your project files in the
-<em>Android</em> project view, as shown in figure 1.
-This view is organized by modules to
-provide quick access to the key source files of your
-project.</p>
-
-<p>All the build files are visible at the top level
-under <strong>Gradle Scripts</strong> and each app module
-contains the following three elements:</p></p>
-<ul>
- <li><b>manifests</b>: Manifest files.</li>
- <li><b>java</b>: Source code files.</li>
- <li><b>res</b>: Resource files.</li>
-</ul>
-
-<p>The Android project structure on disk differs
-from this flattened representation. To see the actual file structure of the
-project, select <strong>Project</strong> from the <strong>Project</strong>
-drop-down (in figure 1, it's showing as <strong>Android</strong>).</p>
-
-<p>You can also customize the view of the project files to focus on specific
-aspects of your app development. For example, selecting the
-<strong>Problems</strong> view of your project displays links to the source
-files containing any recognized coding and syntax errors, such as missing an
-XML element closing tag in a layout file.</p>
-
-<p>For more information, see
-<a class="external-link" href="http://confluence.jetbrains.com/display/IntelliJIDEA/Project+Organization">IntelliJ project organization</a>
-and <a href="{@docRoot}tools/projects/index.html">Managing Projects</a>.</p>
-
-
-<h2 id="build-system">Gradle Build System</h2>
-
-<p>Android Studio uses Gradle as the foundation of the build system, with
-more Android-specific capabilities provided by the <a
-href="{@docRoot}tools/revisions/gradle-plugin.html">Android Plugin for
-Gradle</a>. This build system
-runs as an integrated tool from the Android Studio menu and independently from
-the command line. You can use the features of the build system to:</p>
-
-<ul>
- <li>Customize, configure, and extend the build process.</li>
- <li>Create multiple APKs for your app with different features using the same project and
- modules.</li>
- <li>Reuse code and resources across source sets.</li>
-</ul>
-
-<p>The flexibility of Gradle enables you to achieve all of this without
-modifying your app's core source files. To build an Android Studio project, see
-<a href="{@docRoot}tools/building/building-studio.html">Building and Running
-from Android Studio</a>. To configure custom build settings in an Android
-Studio project, see <a href=
-"{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle
-Builds</a>.</p>
-
-
-
-
-<h2 id="debug-perf">Debug and Profile Tools</h2>
-
-<p>Android Studio assists you in debugging and improving the
-performance of your code, including inline debugging and
-performance analysis tools.</p>
-
-
-<h3 id="inline-debug">Inline debugging</h3>
-
-<p>Use inline debugging to enhance your code walk-throughs in the debugger view
-with inline verification of references, expressions, and variable values.
-Inline debug information includes:</p>
-
-<ul>
- <li>Inline variable values</li>
- <li>Referring objects that reference a selected object </li>
- <li>Method return values</li>
- <li>Lambda and operator expressions</li>
- <li>Tool tip values</li>
-</ul>
-
-<p>To enable inline debugging, in the <em>Debug</em> window click the Settings icon
-<img src="{@docRoot}images/tools/studio-debug-settings-icon.png"/> and select the
-check box for <strong>Show Values In Editor</strong>.</p>
-
-<h3 id="mem-cpu">Memory and CPU monitor</h3>
-<p>Android Studio provides a memory and CPU monitor view so you can more easily monitor your
-app's performance and memory usage to track CPU usage, find deallocated objects, locate memory
-leaks, and track the amount of memory the connected device is using. With your app running on a
-device or emulator, click the <strong>Android</strong> tab in the lower left corner of the
-runtime window to launch the Android runtime window. Click the <strong>Memory</strong> or
-<strong>CPU</strong> tab. </p>
-
-<img src="{@docRoot}images/tools/studio-memory-monitor.png"
-srcset="{@docRoot}images/tools/studio-memory-monitor2x.png 2x" width"635" height="171" alt="" />
- <p class="img-caption"><strong>Figure 2.</strong> Monitor memory and CPU usage.</p>
-
-<h4 id="heap-dump">Heap dump </h4>
-<p>When you're monitoring memory usage in Android Studio you can, at the same time, initiate
-garbage collection and dump the Java heap to a heap snapshot in an Android-specific HPROF binary
-format file. The HPROF viewer displays classes, instances of each class, and a reference tree to
-help you track memory usage and find memory leaks. </p>
-
-<img src="{@docRoot}images/tools/studio-hprof-viewer.png" alt="" />
- <p class="img-caption"><strong>Figure 3.</strong> HPROF viewer with heap dump.</p>
-
-<p>To create a snapshot of the Android app heap memory, click the
-Dump Java Heap icon (<img src="{@docRoot}images/tools/studio-dump-heap-icon.png" style="vertical-align:bottom;margin:0;height:17px"/>)
-in the Memory Monitor. Android Studio creates the heap snapshot file with the filename
-<code>Snapshot-yyyy.mm.dd-hh.mm.ss.hprof</code>
-in the <em>Captures</em> tab. Double-click the heap snapshot file to open the HPROF viewer.</p>
-
-<p>To convert a heap dump to standard HPROF format in Android Studio, right-click a heap
-snapshot in the <em>Captures</em> view and select <strong>Export to standard .hprof</strong>. </p>
-
-
-
-<h4 id="alloc-tracker">Allocation tracker </h4>
-<p>Android Studio allows you to track memory allocation as it monitors memory use. Tracking memory
-allocation allows you to monitor where objects are being allocated when you perform certain actions.
-Knowing these allocations enables you to adjust the method
-calls related to those actions to optimize your app's performance and memory use. </p>
-
-<img src="{@docRoot}images/tools/studio-allocation-tracker.png" alt="" />
- <p class="img-caption"><strong>Figure 4.</strong> Allocation tracker.</p>
-
-<p>For information about tracking and analyzing allocations, see
- <a href="{@docRoot}/tools/help/am-memory.html#tracking">Memory Monitor</a>.
-</p>
-
-
-<h3>Data file access</h3>
-<p>The Android SDK tools, such as <a href="{@docRoot}tools/help/systrace.html">Systrace</a>,
-<a href="{@docRoot}tools/help/logcat.html">logcat</a>, and
-<a href="{@docRoot}tools/help/traceview.html">Traceview</a>, generate performance and debugging
-data for detailed app analysis.</p>
-
-<p>To view the available generated data files, click <strong>Captures</strong> in the left
-corner of the runtime window. In the list of the generated files, double-click a file to view
-the data. Right-click any <code>.hprof</code> files to convert them to a standard
-<a href="{@docRoot}tools/help/hprof-conv.html"><code>.hprof</code> </a> file format.</p>
-
-
-<h3>Code inspections</h3>
-<p>In Android Studio, the configured <a href="{@docRoot}tools/help/lint.html"><code>lint</code></a>
-and other IDE inspections run automatically whenever you compile your program. In addition to the
-configured {@code lint} checks, additional
-<a class="external-link" href="https://www.jetbrains.com/idea/help/inspection-basics.html?search=inspection"
-target="_blank">IntelliJ code inspections</a> and annotation validation run to streamline code
-review.</p>
-
-
-<p>Android Studio enables several <code>lint</code> checks
-to ensure:
-<ul>
- <li><code> Cipher.getInstance()</code> is used with safe values</li>
- <li>In custom Views, the associated declare-styleable for the custom view uses the same
- base name as the class name</li>
- <li>Security check for fragment injection</li>
- <li>Where ever property assignment no longer works as expected</li>
- <li>Gradle plugin version is compatible with the SDK</li>
- <li>Right to left validation </li>
- <li>Required API version</li>
- <li>many others</li>
-</ul>
-
-
-<p>Hovering over an inspection error displays the full issue explanation inline for easy error
-resolution. There is also a helpful hyperlink at the end of the error message for additional
-error information.</p>
-
-<p>With Android Studio, you can also run {@code lint} inspections for a specific build variant, or
-for all build variants. You can configure the {@code lint} inspections that run by adding a
-<code>lintOptions</code> property to the Android settings in the <code>build.gradle</code>
-file. </p>
-
-<pre>
-android {
- lintOptions {
- // set to true to turn off analysis progress reporting by lint
- quiet true
- // if true, stop the gradle build if errors are found
- abortOnError false
- // if true, only report errors
- ignoreWarnings true
- }
-</pre>
-
-
-<p>You can also manage inspection profiles and configure inspections within Android Studio.
-Choose <strong>File > Settings ></strong>, expand the <strong>Editor</strong> options,
-and select <strong>Inspections</strong>.
-The <em>Inspection Configuration</em> page appears with the supported inspections.</p>
-<p><img src="{@docRoot}images/tools/studio-inspections-config.png" alt="" /> </p>
-<p class="img-caption"><strong>Figure 5.</strong> Configure inspections.</p>
-
-<p class="note"><strong>Note:</strong> To change the behavior of specific
-inspection notifications, change the inspection severity, for example from <em>warning</em>
-to <em>error</em>. </p>
-
-
-<p>To manually run inspections in Android Studio, choose <strong>Analyze > Inspect Code</strong>.
-The <em>Inspections Scope</em> dialog appears so you can specify the desired inspection profile and scope.</p>
-
-
-<p>For more information, see
-<a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with {@code lint}</a>
-and <a href="{@docRoot}tools/help/lint.html">lint tool</a>.</p>
-
-
-
-<h3 id="annotations">Annotations in Android Studio</h3>
-<p>Android Studio supports annotations for variables, parameters, and return values to help you
-catch bugs, such as null pointer exceptions and resource type conflicts. The
-<a href="{@docRoot}tools/help/sdk-manager.html">Android SDK Manager</a> packages
-the {@link android.support.annotation Support-Annotations} library
-in the Android Support Repository for use with Android
-Studio. Android Studio validates the configured annotations during code inspection. </p>
-
-<p>To add annotations to your code in Android Studio, first add a dependency for the
-{@link android.support.annotation Support-Annotations} library:</p>
-<ol>
- <li>Select <strong>File > Project Structure</strong>.</li>
- <li>In the <em>Project Structure</em> dialog, select the desired module, click the
- <strong>Dependencies</strong> tab. </li>
- <li>Click the <img src="{@docRoot}images/tools/studio-add-icon.png"/> icon to include a
- <strong>Library dependency</strong>.</li>
- <li>In the <em>Choose Library Dependency</em> dialog, select <code>support-annotations</code> and
- click <strong>Ok</strong>. </li>
-</ol>
-
-<p>The <code>build.gradle</code> file is updated with the <code>support-annotations</code>
-dependency.</p>
-
-<p>You can also manually add this dependency to your <code>build.gradle</code> file, as shown in
-the following example. </p>
-
-<pre>
-dependencies {
- compile fileTree(dir: 'libs', include: ['*.jar'])
- compile 'com.android.support:appcompat-v7:22.0.0'
- <strong>compile 'com.android.support:support-annotations:22.0.0'</strong>
-}
-</pre>
-
-
-
-<h4>Inferring nullability</h4>
-<p>A nullability analysis scans the contracts throughout the method hierarchies in your code to
-detect:</p>
-<ul>
- <li>Calling methods that can return null </li>
- <li>Methods that should not return null </li>
- <li>Variables, such as fields, local variables, and parameters, that can be null </li>
- <li>Variables, such as fields, local variables, and parameters, that cannot hold a null value </li>
-</ul>
-
-<p>The analysis then automatically inserts the appropriate null annotations in the detected
-locations. </p>
-
-<p>To run a nullability analysis in Android Studio,
-select the <strong>Analyze > Infer Nullity</strong>
-menu option. Android Studio inserts the Android
-{@link android.support.annotation.Nullable @Nullable} and
-{@link android.support.annotation.NonNull @NonNull} annotations in detected locations
-in your code. After running a null analysis, it's good practice to verify the injected
-annotations.</p>
-
-<p class="note"><strong>Note:</strong> The nullability analysis may insert the IntelliJ
-<a class="external-link" href="https://www.jetbrains.com/idea/help/-nullable-and-notnull-annotations.html?search=annotations">
-<code>@Nullable</code></a> and
-<a class="external-link" href="https://www.jetbrains.com/idea/help/-nullable-and-notnull-annotations.html?search=annotations">
-<code>@NotNull</code></a> annotations instead of the Android null annotations. When running
-a null analysis, manually search and replace any IntelliJ annotations or include
-<code>com.intellij:annotations:12.0</code> as a compile dependency in your
-<code>build.gradle</code> file. This example includes the IntelliJ annotations 12.0 library as a
-dependency in the <code>build.gradle</code> file:
-
-<pre>
-dependencies {
- compile fileTree(dir: 'libs', include: ['*.jar'])
- compile 'com.android.support:appcompat-v7:22.0.0'
- compile 'com.android.support:support-annotations:22.0.0'
- <strong>compile 'com.intellij:annotations:12.0'</strong>
-}
-</pre>
-
-</p>
-
-
-<h4>Validating annotations</h4>
-<p>You can also manually add nullability, resource, and enumerated annotations throughout your code
-to perform validations for a variety of reference values, such as
-<a href="{@docRoot}reference/android/R.string.html"><code>R.string</code></a> resources,
-<a href="{@docRoot}guide/topics/resources/drawable-resource.htm"><code>Drawable</code></a>
-resources,
-<a href="{@docRoot}reference/android/graphics/Color.html"><code>Color</code></a> resources,
-and enumerated constants. </p>
-
-<p>Run <strong>Analyze > Inspect Code</strong> to validate the configured annotations. </p>
-
-<p>For a complete list of the supported annotations, either use the auto-complete feature to display
-the available options for the <code>import android.support.annotation</code> statement or
-view the contents of the
-{@link android.support.annotation Support-Annotations}
-library. </p>
-
-<p>For more details about Android annotations, see
-<a href="{@docRoot}tools/debugging/annotations.html">Improving Code Inspection with Annotations</a>.
-
-<h3>Log messages</h3>
-<p>When you build and run your app with Android Studio, you can view adb and device log messages
-(logcat) by clicking <strong>Android</strong> at the bottom of the window.</p>
-
-<p>If you want to debug your app with the
-<a href="{@docRoot}tools/help/monitor.html">Android Debug Monitor</a>, you can launch it by
-clicking <strong>Monitor</strong>
-<img src="{@docRoot}images/tools/monitor-studio.png" style="vertical-align:bottom;margin:0;height:19px"/>
-in the toolbar. The Debug Monitor is where you can find the complete set of
-<a href="{@docRoot}tools/debugging/ddms.html">DDMS</a> tools for profiling your app,
-controlling device behaviors, and more. It also includes the Hierarchy Viewer tools to help
-<a href="{@docRoot}tools/debugging/debugging-ui.html"> optimize your layouts</a>.</p>
-
-
-
-
-
+++ /dev/null
-page.title=Configuration
-page.metaDescription=Learn about the Android Studio configuration.
-page.tags=studio, configuration
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#sdk-mgr">SDK Manager</a></li>
- <li><a href="#update-channel">Update Channels</a></li>
- <li><a href="#proxy">Proxy Settings</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}sdk/installing/index.html?pkg=studio">Installing Android Studio</a></li>
- <li><a href="{@docRoot}tools/workflow/index.html">Workflow</a></li>
- <li><a href="{@docRoot}sdk/installing/studio-features.html">Build System</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<p>Android Studio provides wizards and templates that verify your system
-requirements, such as the Java Development Kit (JDK) and available RAM, and configure default
-settings, such as an optimized default Android Virtual Device (AVD) emulation and updated system
-images. This document describes additional configuration settings you may want to use to
-customize your use of Android Studio. </p>
-
-<p>For specific documentation about emulator and device setup and use, see
-<a href="{@docRoot}tools/devices/index.html">Managing Virtual Devices</a>,
-<a href="{@docRoot}tools/device.html">Using Hardware Devices</a>, and
-<a href="{@docRoot}tools/extras/oem-usb.html">OEM USB Drivers</a>. </p>
-
-
-<h2 id="sdk-mgr">SDK Manager</h2>
-<p>After the initial Android Studio installation and setup, use the
-<a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> to verify and update the tools,
-platforms, packages, and other components used by your apps. You can also use the
-<strong>File</strong> > <strong>Settings</strong> >
-<strong>Appearance & Behavior</strong> > <strong>System Settings</strong> >
-<strong>Updates</strong> to configure the SDK Manager to automatically prompt whenever updates are
-available. </p>
-
-<p class="note"><strong>Note:</strong> You can also customize the <code>build.gradle</code> file
-so each app uses a specific build chain and compilation options. For more information see,
-<a href="{@docRoot}tools/building/configuring-gradle.html">Configuring Gradle Builds</a>. </p>
-
-
-
-<h2 id="update-channel">Update channels</h2>
-<p>Android Studio provides four update channels to keep Android Studio up-to-date based on your
-code-level preference:
-<ul>
- <li><strong>Canary channel</strong>: Canary builds provide bleeding edge releases, updated
- about weekly. While these builds do get tested, they are still subject to bugs, as we want
- people to see what's new as soon as possible. This is not recommended for production.</li>
- <li><strong>Dev channel</strong>: Dev builds are hand-picked older canary builds that survived
- the test of time. They are updated roughly bi-weekly or monthly.</li>
- <li><strong>Beta channel</strong>: Beta builds are used for beta-quality releases before a
- production release.</li>
- <li><strong>Stable channel</strong>: Used for stable, production-ready versions.</li>
-</ul>
-</p>
-
-<p>By default, Android Studio uses the <em>Stable</em> channel. Use
-<strong>File > Settings > Appearance & Behavior System Settings > Updates</strong> to change your
-channel setting. </p>
-
-
-
-<h2 id="proxy">Proxy Settings</h2>
-<p>Proxies serve as intermediary connection points between HTTP clients and web servers that add
-security and privacy to internet connections.</p>
-
-<p>To support running Android Studio behind a firewall, set the proxy settings for the
-Android Studio IDE and the SDK Manager. Use the Android Studio IDE HTTP Proxy settings page to set
-the HTTP proxy settings for Android Studio. The SDK Manager has a separate HTTP Proxy settings
-page.</p>
-
-<p>When running the Android Plugin for Gradle from the command line or on machines where
-Android Studio is not installed, such as continuous integration servers, set the proxy settings
-in the Gradle build file.</p>
-
-<p class="note"><strong>Note:</strong> After the initial installation of the Android Studio bundle,
-Android Studio can run with internet access or off-line. However, Android Studio requires an
-internet connection for Setup Wizard synchronization, 3rd-party library access, access to remote
-repositories, Gradle initialization and synchronization, and Android Studio version updates.</p>
-
-
-<h3>Setting up the Android Studio Proxy</h3>
-<p>Android Studio supports HTTP proxy settings so you can run Android Studio behind a firewall or
-secure network. To set the HTTP proxy settings in Android Studio:</p>
-<ol>
- <li>From the main menu choose <strong>File > Settings > Appearance & Behavior -- System
- Settings -- HTTP Proxy</strong>.
-
-<li>In Android Studio, open the IDE Settings dialog.
- <ul>
- <li>On Windows and Linux, choose
- <strong>File > Settings > IDE Setting -- HTTP Proxy</strong>. </li>
- <li>On Mac, choose
- <strong>Android Studio > Preferences > IDE Setting -- HTTP Proxy</strong>. </li>
- </ul>
- The HTTP Proxy page appears.</li>
- <li>Select <strong>auto-detection</strong> to use an auto-configuration URL to configure the
- proxy settings or <strong>manual</strong> to enter each of the settings. For a detailed explanation
- of these settings, see
- <a href="https://www.jetbrains.com/idea/help/http-proxy.html">HTTP Proxy</a>. </li>
- <li>Click <strong>Apply</strong> to enable the proxy settings. </li>
-</ol>
-
-<h3>Android Plugin for Gradle HTTP proxy settings</h3>
-When running the Android Plugin from the command line or on machines where Android Studio is not
-installed, set the Android Plugin for Gradle proxy settings in the Gradle build file.</p>
-
-<p>For application-specific HTTP proxy settings, set the proxy settings in the
-{@code build.gradle} file as required for each application module.</p>
-<pre>
-apply plugin: 'com.android.application'
-
-android {
- ...
-
- defaultConfig {
- ...
- systemProp.http.proxyHost=proxy.company.com
- systemProp.http.proxyPort=443
- systemProp.http.proxyUser=userid
- systemProp.http.proxyPassword=password
- systemProp.http.auth.ntlm.domain=domain
- }
- ...
-}
-</pre>
-
-
-
-<p>For project-wide HTTP proxy settings, set the proxy settings in the
-<code>gradle/gradle.properties</code> file. </p>
-
-<pre>
-# Project-wide Gradle settings.
-...
-
-systemProp.http.proxyHost=proxy.company.com
-systemProp.http.proxyPort=443
-systemProp.http.proxyUser=username
-systemProp.http.proxyPassword=password
-systemProp.http.auth.ntlm.domain=domain
-
-systemProp.https.proxyHost=proxy.company.com
-systemProp.https.proxyPort=443
-systemProp.https.proxyUser=username
-systemProp.https.proxyPassword=password
-systemProp.https.auth.ntlm.domain=domain
-
-...
-</pre>
-
-
-<p>For information about using Gradle properties for proxy settings, see the
- <a href="http://www.gradle.org/docs/current/userguide/build_environment.html">Gradle User Guide</a>.</p>
-
-<p class="note"><strong>Note:</strong> When using Android Studio, the settings in the Android
-Studio IDE HTTP proxy settings page override the HTTP proxy settings in the
-<strong>gradle.properties</strong> file.</p>
-
-
-
-<h3>SDK Manager HTTP Proxy Settings </h3>
-<p>SDK Manager proxy settings enable proxy internet access for Android package and library
-updates from SDK Manager packages. </p>
-
-<p>To set the SDK Manager settings for proxy internet access, start the SDK Manager and open the
-SDK Manager page. </p>
-
-<ul>
- <li>On Windows, select <strong>Tools > Options</strong> from the menu bar. </li>
- <li>On Mac and Linux, choose <strong>Tools > Options</strong> from the system menu bar. </li>
- </ul>
-
-<p>The Android SDK Manager page appears. Enter the settings and click <strong>Apply</strong>. </p>
-
-
-
+++ /dev/null
-page.title=Android Studio Features
-page.image=images/cards/card-studio-modules_crop_2x.png
-page.metaDescription=A quick look at Android Studio features that make your work faster.
-page.tags=studio, tools, sdk
-meta.tags="studio"
-
-
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
-
- <h2>In this document</h2>
- <ol>
- <li><a href="#trans-editor">Translations Editor</a></li>
- <li><a href="#git-samples">Android Code Samples on GitHub</a></li>
- <li><a href="#template-support">Expanded Template and Form Factor Support</a></li>
- <li><a href="#project-settings">Android Studio and Project Settings</a></li>
- <li><a href="#finger-print">Fingerprint Support</a></li>
- <li><a href="#dev-services">Developer Services</a></li>
- <li><a href="#private-res">Public and Private Resources</a></li>
- <li><a href="#support-apis">Editor Support for the Latest Android APIs</a></li>
- <li><a href="#test-module">Test APK Module</a></li>
- </ol>
-
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}tools/workflow/index.html">Workflow</a></li>
- <li><a href="{@docRoot}sdk/installing/studio-build.html">Build System</a></li>
- <li><a href="{@docRoot}sdk/installing/studio-tips.html">Android Studio Tip & Tricks</a></li>
- </ol>
-
-</div>
-</div>
-
-
-<p>If you're new to Android Studio or exploring recent updates, this
-page provides an introduction to some key Android Studio features.</p>
-
-<p>For specific Android Studio how-to documentation, see the pages in the <a href=
-"{@docRoot}tools/workflow/index.html">Workflow</a> section, such as
-<a href="{@docRoot}sdk/installing/create-project.html">Managing Projects from Android Studio</a>
-and
-<a href="{@docRoot}tools/building/building-studio.html">Building and Running from Android Studio</a>. </p>
-
-
-
-<h2 id="trans-editor">Translations Editor</h2>
-<p>If your application supports multiple languages, you need to properly manage your
-translated string resources. The Translations Editor lets you view and update all your string
-resources in one convenient place.</p>
-
-<p>
-Use the Translations Editor to view all your translated resources, modify translations, and add
-new locales. You can provide default values for your resources and mark resources as
-untranslatable. The Translations Editor also marks resources with missing translations in red,
-and provides a link to a page where you can upload resource files and order translation services.
-</p>
-
-<p>For more details on the Translations Editor, see
-<a href="{@docRoot}tools/help/translations-editor.html">Translations Editor</a>.</p>
-
- <img src="{@docRoot}images/tools/studio-translations-editor.png" />
- <p class="img-caption"><strong>Figure 1.</strong> Manage locales and strings in the
- Translations Editor.</p>
-
-<h2 id="git-samples">Android Code Samples on GitHub</h2>
-<p>Clicking <strong>Import Samples</strong> from the <strong>File</strong> menu or <em>Welcome</em>
-page provides seamless access to Google code samples on GitHub.</p>
- <p><img src="{@docRoot}images/tools/studio-samples-githubaccess.png" /></p>
- <p class="img-caption"><strong>Figure 2.</strong> Get code samples from GitHub.</p>
-
-
- <p><img src="{@docRoot}images/tools/studio-sample-in-editor.png" /></p>
- <p class="img-caption"><strong>Figure 3.</strong> Imported code sample.</p>
-
-
-
-<h2 id="template-support">Expanded Template and Form Factor Support</h2>
-<p>Android Studio supports templates for Google Services and expands the available device
-types. </p>
-
- <h4> Android Wear and TV support</h4>
- <p>For easy cross-platform development, the Project Wizard provides templates for
- creating your apps for Android Wear and TV. </p>
- <p><img src="{@docRoot}images/tools/studio-tvwearsupport.png" />
-
- <p class="img-caption"><strong>Figure 4.</strong> Supported form factors.</p>
- <p>During app creation, the Project Wizard also displays an API Level dialog to help you choose
- the best <em>minSdkVersion</em> for your project.</p>
-
-
- <h4> Google App Engine integration (Google Cloud Platform/Messaging)</h4>
- <p>Quick cloud integration. Using Google App Engine to connect to the Google cloud
- and create a cloud end-point is as easy as selecting <em>File > New Module > App Engine Java
- Servlet Module</em> and specifying the module, package, and client names. </p>
- <p><img src="{@docRoot}images/tools/studio-cloudmodule.png" /></p>
- <p class="img-caption"><strong>Figure 5</strong> Google App Engine integration.</p>
-
-
-<h2 id="project-settings">Android Studio and Project Settings</h2>
-<p>Android Studio provides setting dialogs so you can manage the most important Android Studio and
-project settings from the <strong>File > Project Structure</strong> and
-<strong>File > Settings</strong> menus. For example, you can use the
-<strong>File > Project Structure</strong> menu or
-the <code>build.gradle</code> file to update your <code>productFlavor</code> settings.
-Additional settings from the <strong>File > Project Structure</strong> menus include:
-<ul>
- <li>SDK and JDK location </li>
- <li>SDK version </li>
- <li>Gradle and Android Plugin for Gradle versions </li>
- <li>Build tools version </li>
- <li>Multidex setting</li>
- <li><code>buildTypes</code> </li>
- <li>Dependencies </li>
-</ul>
-</p>
-
-<p>Use the <strong>File > Settings</strong> menu to modify the Android Studio or project
-behavior, such a UI themes, system settings, and version control. </p>
-
-
-
-<h2 id="finger-print">Fingerprint Support</h2>
-<p>Android Studio provides the {@code finger} command, allowing you to simulate, and thus validate,
-fingerprint authentication for your app. After you set up your app to accept
-<a href="https://developer.android.com/preview/api-overview.html#authentication">fingerprint
-authentication</a>, your emulator or device should display the fingerprint authentication screen,
-as shown below. </p>
-
- <p><img src="{@docRoot}images/tools/studio-fingerprint.png" /></p>
- <p class="img-caption"><strong>Figure 6</strong> Fingerprint authentication.</p>
-
-<p>Open a terminal session, and telnet to the emulator. For example:</p>
-<pre>
-{@code telnet localhost 5554}
-</pre>
-
-<p>Enter the <code>finger</code> command to simulate finger touch and removal: </p>
-
-<ul>
- <li><code>finger touch <fingerprint-id></code> to simulate a finger touching the sensor</li>
- <li><code>finger remove</code> to simulate finger removal </li>
-</ul>
-
-<p>Your app should respond as if a user touched, and then removed their finger from, the
-fingerprint sensor. </p>
-
-
-<h2 id="dev-services">Developer Services</h2>
-<p>Android Studio supports enabling these developer services in your app: </p>
-<ul>
- <li>Ads using <a href="https://developers.google.com/admob/">AdMob</a></li>
- <li>Analytics <a href="https://developers.google.com/analytics/">Google Analytics</a></li>
- <li>Authentication using <a href="https://developers.google.com/identity/sign-in/android/">Google
- Sign-in</a> </li>
- <li>Notifications using <a href="https://developers.google.com/cloud-messaging/">Google
- Cloud Messaging</a> </li>
-</ul>
-
-<p>Enabling a developer service adds the required dependencies and, when applicable, also modifies
-the related configuration files. To activate the service, you must perform
-service-specific updates, such as loading an ad in the <code>MainActivity</code> class for ad
-display.</p>
-
-<p>To enable an Android developer service, select the <code>File > Project Structure</code>
-menu option and click a service under the <em>Developer Services</em> sub-menu. The service
-configuration page appears. In the service configuration page, click the service check box to
-enable the service and click <strong>OK</strong>. Android Studio updates your library dependencies
-for the selected service and, for Analytics, updates the <code>AndroidManifest.xml</code> and
-other tracker configuration files. You can enable multiple services within the same app. For more
-detail about starting the services, refer to each service's specific activation instructions. </p>
-
-
-
-<h2 id="private-res">Public and Private Resources</h2>
-<p>By default, Android Studio treats all library resources as public: A public library resource is
-available to library clients for use outside the library, and appears in code completion suggestions
-and other resource references. Android Studio also, however, supports the use of private library
-resources. A private library resource can only be used within the source library, and does not
-appear in code completion lists and other resource references. </p>
-
-<p>You cannot explicitly declare a library resource as private. Instead, if you declare any library
-resources as public, Android Studio assumes all the other library resources are private. </p>
-
-<p>An app treats all Android library resources as public unless you explicitly declare at least one
-resource in the library as public. Declaring one public resource causes your app to treat all other,
-undeclared resources in the library as private. </p>
-
-<p class="note"><strong>Note:</strong> Declaring public and private resources requires the
-<a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin for Gradle</a> version
-1.3 or higher. </p>
-
-
-<p>To declare a resource as public and set other undeclared resources as private, add a
-<code><public></code> declaration with the resource name and type in the resource file.
-This example shows the public declaration for the <code>mylib_app_name</code> string resource. </p>
-
-<pre>
-<resources>
- <public name="mylib_app_name" type="string"/>
-</resources>
-</pre>
-
-<p>For large numbers of declarations, we recommended that you place the public marker declarations
-in a separate file named <code>public.xml</code>. </p>
-
-<p>To help enforce private resource access, a <a href="{@docRoot}tools/help/lint.html">lint</a>
-warning appears when a client of a library references a private resource. Many Android libraries,
-such as the
-<a href="{@docRoot}tools/support-library/features.html#design">Design Support Library</a> and the
-<a href="{@docRoot}tools/support-library/features.html#v7-appcompat">v7 appcompat Library</a>,
-declare public resources to display only resources that developers can directly reference.
-</p>
-
-<p class="note"><strong>Note:</strong> If your app requires a private resource, copy the
-private resource from the library to the location in your app where it is needed. </p>
-
-<p>When the build system builds an Android Archive (AAR) file, it extracts the
-<code><public></code> resource declarations into a <code>public.txt</code> file, which is
-packaged inside the AAR file next to the <code>R.txt</code> file. The <code>public.txt</code> file
-contains a simple list of the declared public resources, describing their names and types. </p>
-
-<p>For a complete list of the available Android resource types, see
-<a href="http://developer.android.com/guide/topics/resources/available-resources.html">Resource
-Types</a></li> and
-<a href="http://developer.android.com/guide/topics/resources/more-resources.html">More Resource
-Types</a></li>. </p>
-
-
-
-<h2 id="support-apis">Editor Support for the Latest Android APIs</h2>
-<p>Android Studio supports the
-<a href="{@docRoot}design/material/index.html">Material Design</a></li> themes, widgets, and
-graphics, such as shadow layers and API version rendering (showing the layout across different
-UI versions). Also, the drawable XML tags and attributes, such as <code><ripple></code>
-and <code><animated-selector></code>, are supported.</p>
-
-
-
-<h2 id="test-module">Test APK Module</h2>
-<p>Android Studio supports adding a separate <code>test</code> module to your app so you can
-generate a test APK. This <code>test</code> module resides at the same level as your app and
-contains: the tests and instrumentation used to run the test APK on an Android device; an
-<code>Android Manifest.xml</code> file for test APK configuration settings; and, a
-<code>build.gradle</code> file for build settings.</p>
-
-<p>The <code>test</code> module cannot contain a <code>src/androidTest/</code> folder and does
-not support build variants. If you have different product flavors in your main application APK,
-create a different test module for each build variant.</p>
-
-
-<p>To create a test APK module:
-
-<ul>
- <li>Use the <strong>File > New > Module</strong> menu option to create a
- <code>test</code> module consisting of the following directories and files:
- <ul>
- <li><code>./test/</code> </li>
- <li><code>./test/build.gradle</code> </li>
- <li><code>./test/src/main/java/com/android/tests/basic/MainTest.java</code> </li>
- <li><code>./test/src/main/AndroidManifest.xml</code> </li>
- </ul>
- </li>
- <li>In the <code>build.gradle</code> file, add the required properties to the
- <code>android</code> block.
- <ul>
- <li><code>targetProjectPath ':<app name>'</code> specifies the main application APK
- to test. </li>
- <li><code>targetVariant ':<buildType>'</code> specifies the target build type.</li>
- </ul>
- <p>Here is an example of <code>build.gradle</code> file property settings: </p>
-
-<pre>
-android {
- compileSdkVersion 19
- buildToolsVersion = ‘21.1.3’
-
- targetProjectPath ':app'
- targetVariant 'debug'
-}
-</pre>
- </li>
- <li>Define the instrumentation entries in the manifest file.
- <p>Here is an example of <code><instrumentation></code> settings in the manifest file: </p>
-
-<pre>
-<?xml version="1.0" encoding="utf-8"?>
-<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.android.tests.basic.test">
-
- <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="16" />
-
- <application>
- >uses-library android:name="android.test.runner" />
- </application>
-
- <instrumentation android:name="android.test.InstrumentationTestRunner"
- android:targetPackage="com.android.tests.basic"
- android:handleProfiling="false"
- android:functionalTest="false"
- android:label="Tests for com.android.tests.basic"/>
-</manifest<
-</pre>
-
-<p class="note"><strong>Note:</strong> The <code>targetPackage</code> in the instrumentation
-settings specifies the package of the test variant. </p>
-
- </li>
- <li>In the <code>build.gradle</code> file for the tested app, include additional artifacts
- that the test APK requires, such as the <code> classes.jar</code> file, by adding the
- {@code publishNonDefault} property to the {@code Android} block, and assigning that property
- a value of {@code true}.
- <p>Here is an example of the <code>build.gradle</code> file that includes additional
- artifacts: </p></li>
-<pre>
-android {
- compileSdkVersion 19
- buildToolsVersion = ‘21.1.3’
-
- publishNonDefault true
-}
-</pre>
- </li>
-</ul>
-
-
-<p>In the {@code test} module in this example, the {@code build.gradle} file specifies the
-properties for the project path and target build type variant. </p>
-
- <p><img src="{@docRoot}images/tools/studio-test-module.png" /></p>
- <p class="img-caption"><strong>Figure 3.</strong> Test module for APK testing.</p>
-
-
-<p class="note"><strong>Note:</strong> By default, the test module's build variant uses the
-<code>debug</code> build type. You can configure additional build types using the
-<code>testBuildType</code> property in the <code>defaultConfig</code> block in the main
-app's <code>build.gradle</code> file. </p>
-
-
+++ /dev/null
-page.title=Android Studio User Interface Tools
-
-@jd:body
-
-<p>
- Android Studio provides a number of user interface tools to assist you with creating layouts,
- implementing style themes, and building graphic or text resources for your app.
-</p>
-
-<dl>
-
- <dt><a href="{@docRoot}sdk/installing/studio-layout.html">Layout Editor</a></dt>
- <dd>Drag and drop user interface elements to build layouts for your app.
- </dd>
-
- <dt><a href="{@docRoot}tools/help/theme-editor.html">Theme Editor</a></dt>
- <dd>Build re-usable user interface styles for layouts and widgets in your app.
- </dd>
-
- <dt><a href="{@docRoot}tools/help/translations-editor.html">Translations Editor</a></dt>
- <dd>View and update all your string resource translations in one convenient place.
- </dd>
-
- <dt><a href="{@docRoot}tools/help/vector-asset-studio.html">Vector Asset Studio</a></dt>
- <dd>Add material icons and import Scalable Vector Graphic (SVG) files into your
- Android Studio project as a drawable resource.</dd>
-
- <dt><a href="{@docRoot}tools/help/image-asset-studio.html">Image Asset Studio</a></dt>
- <dd>Generate custom icons for your Android applications from existing images,
- clipart, or text.</dd>
-
-</dl>
+++ /dev/null
-page.title=Testing
-@jd:body
-
-<p>Android provides an integrated testing framework that helps you test all aspects
-of your app. The Android <a href="{@docRoot}sdk/installing/index.html">SDK</a> and
-<a href="{@docRoot}tools/testing-support-library/index.html">Testing Support Library</a> include
-tools and APIs for setting up and running test apps within an emulator or on the device you are
-targeting. You can build and execute tests whether you are working in Android Studio or working
-from the command line.</p>
-
-<p>To familiarize yourself with mobile app testing in Android, start by reading these resources:</p>
-<ul>
- <li><a href="{@docRoot}tools/testing/testing_android.html">Testing Concepts</a>: Learn key
- concepts related to Android app testing and get an overview of the testing tools and APIs
- that Google provides.</li>
- <li><a href="{@docRoot}training/testing/start/index.html">Getting Started with Testing</a>: Learn
- how to build and run your tests, step-by-step, using the testing APIs and tools that
- Google provides.</li>
-</ul>
+++ /dev/null
-page.title=Android Testing Tools
-@jd:body
-
-<div id="qv-wrapper">
-<div id="qv">
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/testing/index.html">Best Practices for Testing</a></li>
- </ol>
-</div>
-</div>
-
- <p>
- Testing is a critical software development activity because it helps you
- improve the quality of your apps, ensure better user satisfaction, and
- reduce overall development time spent on fixing defects.
- </p>
-
- <p>The following sections describe tools that help
- you test your mobile apps for the Android platform.</a>
-
-<dl>
- <dt><strong><a href="{@docRoot}tools/testing-support-library/index.html">Android
- Testing Support Library</a></strong></dt>
- <dd>This library provides a set of APIs that allow
- you to quickly build and run test code for your apps, including JUnit 4 and functional user
- interface (UI) tests. The Android Testing Support Library includes the following test automation
- tools:
-
- <ul>
- <li><a href="{@docRoot}tools/testing-support-library/index.html#AndroidJUnitRunner">AndroidJUnitRunner</a>:
- JUnit 4-compatible test runner for Android
- </li>
-
- <li><a href="{@docRoot}tools/testing-support-library/index.html#Espresso">Espresso</a>:
- UI testing framework; suitable for functional UI testing within an app
- </li>
-
- <li><a href="{@docRoot}tools/testing-support-library/index.html#UIAutomator">UI Automator</a>:
- UI testing framework; suitable for cross-app functional UI testing across system and installed apps
- </li>
- </ul>
- </dd>
-
- <dt><strong><a href="{@docRoot}tools/help/monkey.html">Monkey</a></strong></dt>
- <dd>This tool 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 tool to stress-test applications that you are developing, in a random yet
-repeatable manner.
- </dd>
-
- <dt><strong><a href="{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a></strong></dt>
- <dd>This testing system provides an API for writing programs that control an Android device or
-emulator from outside of Android code.</dd>
-
-</dl>
\ No newline at end of file
+++ /dev/null
-page.title=Testing Concepts
-parent.title=Testing
-parent.link=index.html
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li><a href="#TestStructure">Test Structure</a></li>
- <li><a href="#TestAPI">Testing APIs</a>
- <ol>
- <li>
- <a href="#JUnit">JUnit</a>
- </li>
- <li>
- <a href="#Instrumentation">Instrumentation</a>
- </li>
- <li>
- <a href="#TestingSupportLibraryClasses">Android Testing Support Library APIs</a>
- </li>
- <li>
- <a href="#AssertionClasses">Assertion classes</a>
- </li>
- </ol>
- </li>
- <li>
- <a href="#Monkeys">Monkey and Monkeyrunner</a>
- </li>
- </ol>
- <h2>See also</h2>
- <ol>
- <li><a href="{@docRoot}training/testing/start/index.html">Getting Started with Testing</a></li>
- </ol>
- </div>
-</div>
-
-<p>
-This document describes key concepts related to Android app testing. It assumes you have a basic
-knowledge of the <a href="http://junit.org/" class="external-link">JUnit</a> testing framework.</p>
-
-<h2 id="TestStructure">Test Structure</h2>
-<p>Android testing is based on JUnit. In general, a JUnit test is a method whose statements test a
-part of the application. You organize test methods into classes called
-<em>test cases</em>. You can further organize these classes into <em>test suites</em>.</p>
-<p>In JUnit, you build one or more test classes and use a test runner to
-execute them. In Android, you use <a href="{@docRoot}tools/studio/index.html">
-Android Studio </a>(or the <a href="{@docRoot}tools/building/plugin-for-gradle.html">
-Android Plugin for Gradle</a>) to build one or more test source files into an
-<em>Android test app</em>.</p>
-
-<p>From your testing environment, you can run your test in one of the following ways:</p>
-<ul>
- <li><strong>On your local machine:</strong> Compile the test classes and
- execute them locally on the Java Virtual Machine (JVM) using the JUnit test runner.</li>
- <li><strong>On a device or emulator</strong>: Install the test app and the app
-under test to a physical device or emulator, and then execute your tests using an Android-specific
-test runner (such as <a href="{@docRoot}tools/testing-support-library/index.html#AndroidJUnitRunner">
-{@code AndroidJUnitRunner}</a>).</li>
-</ul>
-
-<p>The structure of your test code and the way you build and run the tests in Android Studio depend
-on the type of testing you are performing. The following table summarizes the common testing types
-for Android:</p>
-
-<table>
-<tr><th>Type</th>
- <th>Subtype</th>
- <th>Description</th></tr>
-
-<tr><td rowspan="3">Unit tests</td>
- <tr><td>Local Unit Tests</td>
- <td>Unit tests that run on your local machine only. These tests are compiled to run locally
-on the JVM to minimize execution time. Use this approach to run unit tests
-that have no dependencies on the Android framework or have dependencies that mock objects can
-satisfy.</td></tr>
- <tr><td>Instrumented unit tests</td>
- <td>Unit tests that run on an Android device or emulator. These tests have access to
-{@link android.app.Instrumentation} information, such as the {@link android.content.Context} of the
-app under test. Use this approach to run unit tests that have Android dependencies which mock
-objects cannot easily satisfy.</td></tr>
-
-<tr><td rowspan="3">Integration Tests</td>
- <tr><td>Components within your app only</td>
- <td>This type of test verifies that the target app behaves as expected when a user performs
-a specific action or enters a specific input in its activities. For example, it allows you to check
-that the target app returns the correct UI output in response to user interactions in the app’s
-activities. UI testing frameworks like
-<a href="{@docRoot}tools/testing-support-library/index.html#Espresso">Espresso</a> allow you to
-programmatically simulate user actions and test complex intra-app user interactions.</td></tr>
- <tr><td>Cross-app Components</td>
- <td>This type of test verifies the correct behavior of interactions between different user
-apps or between user apps and system apps. For example, you might want to test that your app behaves
-correctly when the user performs an action in the Android Settings menu. UI testing frameworks
-that support cross-app interactions, such as UI Automator, allow you to create tests for such
-scenarios.</td></tr>
-</table>
-
-<p>Based on the type of test you want to create, you need to configure the test code source
-location and the project dependencies in Android Studio as described in
-<a href="{@docRoot}training/testing/start/index.html">Getting Started with Testing</a>.</p>
-
-<h2 id="TestAPI">Testing APIs</h2>
-<p>The following list summarizes the common APIs related to app testing for Android.</p>
-
-<h3 id="JUnit">JUnit</h3>
-
-<p>You should write your unit or integration test class as a JUnit 4 test class.
-<a href="http://junit.org/" class="external-link">JUnit</a> is the most popular
-and widely-used unit testing framework for Java. The framework offers a convenient way to perform
-common setup, teardown, and assertion operations in your test.</p>
-
-<p>JUnit 4 allows you to write tests in a cleaner and more
-flexible way than its predecessor versions. Unlike the previous approach to Android unit testing
-based on JUnit 3, with JUnit 4, you do not need to extend the {@code junit.framework.TestCase}
-class. You also do not need to prepend the {@code test} keyword to your test method name, or
-use any classes in the {@code junit.framework} or {@code junit.extensions} package.</p>
-
-<p>A basic JUnit 4 test class is a Java class that contains one or more test methods.
-A test method begins with the {@code @Test} annotation and contains the code to exercise
-and verify a single functionality (that is, a logical <em>unit</em>) in the component that you want
-to test.</p>
-<p>The following snippet shows an example JUnit 4 integration test that uses the Espresso
-APIs to perform a click action on a UI element, then checks to see if an expected string is
-displayed.</p>
-<pre>
-@RunWith(AndroidJUnit4.class)
-@LargeTest
-public class MainActivityInstrumentationTest {
-
- @Rule
- public ActivityTestRule<MainActivity> mActivityRule = new ActivityTestRule<>(
- MainActivity.class);
-
- @Test
- public void sayHello(){
- onView(withText("Say hello!")).perform(click());
-
- onView(withId(R.id.textView)).check(matches(withText("Hello, World!")));
- }
-}
-</pre>
-<p>In your JUnit 4 test class, you can call out sections in your test code for
-special processing by using the following annotations:</p>
-<ul>
-<li>
-{@code @Before}: Use this annotation to specify a block of code that contains test setup
-operations. The test class invokes this code block before each test. You can have multiple
-{@code @Before} methods but the order in which the test class calls these methods
-is not guaranteed.
-</li>
-<li>
-{@code @After}: This annotation specifies a block of code that contains test
-tear-down operations. The test class calls this code block after every test method. You can define
-multiple {@code @After} operations in your test code. Use this annotation to release any
-resources from memory.
-</li>
-<li>
-{@code @Test}: Use this annotation to mark a test method. A single test class can contain
-multiple test methods, each prefixed with this annotation.
-</li>
-<li>
-{@code @Rule}: Rules allow you to flexibly add or redefine the behavior of each test
-method in a reusable way. In Android testing, use this annotation together with
-one of the test rule classes that the Android Testing Support Library provides, such as
-<a href="{@docRoot}reference/android/support/test/rule/ActivityTestRule.html">
-{@code ActivityTestRule}</a> or
-<a href="{@docRoot}reference/android/support/test/rule/ServiceTestRule.html">
-{@code ServiceTestRule}</a>.
-</li>
-<li>
-{@code @BeforeClass}: Use this annotation to specify static methods for each test class to
-invoke only once. This testing step is useful for expensive operations such as connecting to a
-database.
-</li>
-<li>
-{@code @AfterClass}: Use this annotation to specify static methods for the test class to invoke
-only after all tests in the class have run. This testing step is useful for releasing any
-resources allocated in the {@code @BeforeClass} block.
-</li>
-<li>
-{@code @Test(timeout=<milliseconds>)}: Some annotations support the ability to pass in
-elements for which you can set values. For example, you can specify a timeout period for the test.
-If the test starts but does not complete within the given timeout period, it automatically fails.
-You must specify the timeout period in milliseconds, for example: {@code @Test(timeout=5000)}.
-</li>
-</ul>
-<p>For more annotations, see the documentation for
-<a href="//junit.sourceforge.net/javadoc/org/junit/package-summary.html" class="external-link">
-JUnit annotations</a> and the
-<a href="{@docRoot}android/support/test/annotation/package-summary.html">
-Android-specific annotations</a>.
-<p>
- You use the JUnit {@link junit.framework.Assert} class to verify the correctness of an object's
- state. The assert methods compare values you expect from a test to the actual results and
- throw an exception if the comparison fails. <a href="#AssertionClasses">
- Assertion classes</a> describes these methods in more detail.
-</p>
-
-</p>
-<h3 id="Instrumentation">Instrumentation</h3>
-<p>
- Android instrumentation is a set of control methods or hooks in the Android system. These
- hooks control an Android component independently of its normal lifecycle. They also control how
- Android loads applications.
-</p>
-<p>
- The following diagram summarizes the testing framework:
-</p>
-<div style="width: 70%; margin-left:auto; margin-right:auto;">
-<a href="{@docRoot}images/testing/test_framework.png">
- <img src="{@docRoot}images/testing/test_framework.png"
- alt="The Android testing framework"/>
-</a>
-</div>
-<p>
-Normally, an Android component runs in a lifecycle that the system determines. For example, an
-{@link android.app.Activity} object's lifecycle starts when an {@link android.content.Intent}
-activates the {@link android.app.Activity}. The system calls the object's <code>onCreate()</code>
-method, on then the <code>onResume()</code> method. When the user starts another application, the
-system calls the <code>onPause()</code> method. If the {@link android.app.Activity} code calls
-the <code>finish()</code> method, the system calls the <code>onDestroy()</code> method. The Android
-framework API does not provide a way for your code to invoke these callback methods directly, but
-you can do so using instrumentation.
-</p>
-<p>
-The system runs all the components of an application in the same process. You can allow some
-components, such as content providers, to run in a separate process,
-but you can't force an application to run in the same process as another application that is
-already running.
-</p>
-<p>
-Instrumentation can load both a test package and the app under test into the
-same process. Since the application components and their tests are in the same process, your
-tests can invoke methods in the components, and modify and examine fields in the components.
-</p>
-<h3 id="TestingSupportLibraryClasses">Android Testing Support Library APIs</h3>
-<p>
-The <a href="{@docRoot}tools/testing-support-library/index.html">Android Testing Support Library</a>
-provides a set of APIs that allow you to quickly build and run test code for your apps, including
-JUnit 4 and functional user interface (UI) tests. The library includes the following
-instrumentation-based APIs that are useful when you want to automate your tests:</p>
-<ul>
- <li><a href="{@docRoot}tools/testing-support-library/index.html#AndroidJUnitRunner">
- {@code AndroidJUnitRunner}</a>:
- JUnit 4-compatible test runner for Android
- </li>
-
- <li><a href="{@docRoot}tools/testing-support-library/index.html#Espresso">Espresso</a>:
- UI testing framework; suitable for functional UI testing within an app
- </li>
-
- <li><a href="{@docRoot}tools/testing-support-library/index.html#UIAutomator">UI Automator</a>:
- UI testing framework; suitable for cross-app functional UI testing across system and installed
- apps</li>
- </ul>
-
-<h3 id="AssertionClasses">Assertion classes</h3>
-<p>Because Android Testing Support Library APIs extend JUnit, you can use assertion methods to
-display the results of tests. An assertion method compares an actual value returned by a test to an
-expected value, and throws an AssertionException if the comparison test fails. Using assertions
-is more convenient than logging, and provides better test performance.
-</p>
-<p>To simplify your test development, we recommend that you use the
-<a href="https://github.com/hamcrest"
-class="external-link">Hamcrest</a> library, which lets you create more flexible tests using the
-Hamcrest matcher APIs.</p>
-
-<h2 id="Monkeys">Monkey and Monkeyrunner</h2>
-<p>
- The SDK provides two tools for functional-level application testing:
-</p>
- <ul>
- <li>
-The <a href="{@docRoot}tools/help/monkey.html">UI/Application Exerciser Monkey</a>,
- usually called "monkey", is a command-line tool that sends pseudo-random streams of
- keystrokes, touches, and gestures to a device. You run it with the
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a> (adb) tool.
- You use it to stress-test your application and report back errors that are encountered.
- You can repeat a stream of events by running the tool each time with the same random
- number seed.
- </li>
- <li>
- The <a href="{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a> tool
- is an API and execution environment for test programs written in Python. The API
- includes functions for connecting to a device, installing and uninstalling packages,
- taking screenshots, comparing two images, and running a test package against an
- application. Using the API, you can write a wide range of large, powerful, and complex
- tests. You run programs that use the API with the <code>monkeyrunner</code> command-line
- tool.
- </li>
- </ul>
\ No newline at end of file
+++ /dev/null
-page.title=Testing from the Command-Line
-
-@jd:body
-
-<div id="qv-wrapper">
- <div id="qv">
- <h2>In this document</h2>
- <ol>
- <li>
- <a href="#RunTestsCommand">Running Tests</a>
- <ol>
- <li>
- <a href="#RunTestsGradle">Running unit tests with Gradle</a>
- </li>
- <li>
- <a href="#RunTestsDevice">Running tests with adb</a>
- </li>
- </ol>
- </li>
- <li>
- <a href="#AMSyntax">Using the Instrument Command</a>
- <ol>
- <li>
- <a href="#AMOptionsSyntax">Instrument options</a>
- </li>
- <li>
- <a href="#RunTestExamples">Instrument examples</a>
- </li>
- </ol>
- </li>
- </ol>
- <h2>See Also</h2>
- <ol>
- <li>
- <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>
- </li>
- </ol>
- </div>
-</div>
-<p>
- This document describes how to create and run tests directly from the command line. This
- document assumes that you already know how to create a Android application in your programming
- environment.
-</p>
-
-<h2 id="RunTestsCommand">Running Tests</h2>
-<p>
- You can run tests from the command-line, either with Gradle or with an
- <a href="{@docRoot}tools/help/adb.html">
- Android Debug Bridge (adb)</a> shell.
-</p>
-<h3 id="RunTestsGradle">Running unit tests with Gradle</h3>
-
-<p>The <a href="{@docRoot}tools/building/plugin-for-gradle.html">Android Plugin for Gradle</a>
-lets you run unit tests from your Gradle project via the command-line. For more information on
-how to build unit tests for your app, see
-<a href="{@docRoot}training/testing/unit-testing/index.html">Building Effective Unit Tests</a>.</p>
-
-<p>The table below summarizes how to run your unit tests with Gradle:</p>
-<table>
- <tr>
- <th>Unit Test Type</th>
- <th>Command To Run</th>
- <th>Test Result Location</th>
- </tr>
- <tr>
- <td>Local unit test</td>
- <td>Call the {@code test} task:
-<pre>
-./gradlew test
-</pre></td>
- <td>
-HTML test result files:
-{@code <path_to_your_project>/app/build/reports/tests/} directory.
-<p>XML test result files:
-{@code <path_to_your_project>/app/build/test-results/} directory.
-</p></td>
- </tr>
- <tr>
- <td>Instrumented unit test</td>
- <td>Call the {@code connectedAndroidTest} (or {@code cAT}) task:
-<pre>
-./gradlew cAT
-</pre>
- </td>
- <td>
-HTML test result files:
-{@code <path_to_your_project>/app/build/outputs/reports/androidTests/connected/} directory.
-<p>XML test result files:
-{@code <path_to_your_project>/app/build/outputs/androidTest-results/connected/} directory.
-</p></td>
- </tr>
-</table>
-
-<h3 id="RunTestsDevice">Running tests with ADB</h3>
-<p>
- When you run tests from the command-line with
- <a href="{@docRoot}tools/help/adb.html">
- Android Debug Bridge (adb)</a>, you get more options for choosing the tests
- to run than with any other method. You can select individual test methods, filter tests
- according to their annotation, or specify testing options. Since the test run is controlled
- entirely from a command-line, you can customize your testing with shell scripts in various ways.
-</p>
-<p>
- To run a test from the command-line, you run <code>adb shell</code> to start a command-line
- shell on your device or emulator, and then in the shell run the <code>am instrument</code>
- command. You control <code>am</code> and your tests with command-line flags.
-</p>
-<p>
- As a shortcut, you can start an <code>adb</code> shell, call <code>am instrument</code>, and
- specify command-line flags all on one input line. The shell opens on the device or emulator,
- runs your tests, produces output, and then returns to the command-line on your computer.
-</p>
-<p>
- To run a test with <code>am instrument</code>:
-</p>
-<ol>
- <li>
- If necessary, rebuild your main application and test package.
- </li>
- <li>
- Install your test package and main application Android package files
- (<code>.apk</code> files) to your current Android device or emulator</li>
- <li>
- At the command-line, enter:
-<pre>
-$ adb shell am instrument -w <test_package_name>/<runner_class>
-</pre>
- <p>
- where <code><test_package_name></code> is the Android package name of your test
- application, and <code><runner_class></code> is the name of the Android test
- runner class you are using. The Android package name is the value of the
- <code>package</code> attribute of the <code>manifest</code> element in the manifest file
- (<code>AndroidManifest.xml</code>) of your test package. The Android test runner
- class is usually
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a>.
- </p>
- <p>
- Your test results appear in <code>STDOUT</code>.
- </p>
- </li>
-</ol>
-<p>
- This operation starts an <code>adb</code> shell, then runs <code>am instrument</code>
- with the specified parameters. This particular form of the command will run all of the tests
- in your test package. You can control this behavior with flags that you pass to
- <code>am instrument</code>. These flags are described in the next section.
-</p>
-<h2 id="AMSyntax">Using the am instrument Command</h2>
-<p>
- The general syntax of the <code>am instrument</code> command is:
-</p>
-<pre>
-am instrument [flags] <test_package>/<runner_class>
-</pre>
-<p>
- The main input parameters to <code>am instrument</code> are described in the following table:
-</p>
-<table>
- <tr>
- <th>
- Parameter
- </th>
- <th>
- Value
- </th>
- <th>
- Description
- </th>
- </tr>
- <tr>
- <td>
- <code><test_package></code>
- </td>
- <td>
- The Android package name of the test package.
- </td>
- <td>
- The value of the <code>package</code> attribute of the <code>manifest</code>
- element in the test package's manifest file.
- </td>
- </tr>
- <tr>
- <td>
- <code><runner_class></code>
- </td>
- <td>
- The class name of the instrumented test runner you are using.
- </td>
- <td>
- This is usually
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a>.
- </td>
- </tr>
-</table>
-
-<p>
- The flags for <code>am instrument</code> are described in the following table:
-</p>
-<table>
- <tr>
- <th>
- Flag
- </th>
- <th>
- Value
- </th>
- <th>
- Description
- </th>
- </tr>
- <tr>
- <td>
- <code>-w</code>
- </td>
- <td>
- (none)
- </td>
- <td>
- Forces <code>am instrument</code> to wait until the instrumentation terminates
- before terminating itself. The net effect is to keep the shell open until the tests
- have finished. This flag is not required, but if you do not use it, you will not
- see the results of your tests.
- </td>
- </tr>
- <tr>
- <td>
- <code>-r</code>
- </td>
- <td>
- (none)
- </td>
- <td>
- Outputs results in raw format. Use this flag when you want to collect
- performance measurements, so that they are not formatted as test results. This flag is
- designed for use with the flag <code>-e perf true</code> (documented in the section
- <a href="#AMOptionsSyntax">Instrument options</a>).
- </td>
- </tr>
- <tr>
- <td>
- <code>-e</code>
- </td>
- <td>
- <test_options>
- </td>
- <td>
- Provides testing options as key-value pairs. The
- <code>am instrument</code> tool passes these to the specified instrumentation class
- via its <code>onCreate()</code> method. You can specify multiple occurrences of
- <code>-e <test_options></code>. The keys and values are described in the
- section <a href="#AMOptionsSyntax">am instrument options</a>. You can only use these
- key-value pairs with
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a> or with {@link android.test.InstrumentationTestRunner} and its
-subclasses. Using them with any other class has no effect.
- </td>
- </tr>
-</table>
-
-<h3 id="AMOptionsSyntax">am instrument options</h3>
-<p>
- The <code>am instrument</code> tool passes testing options to
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a> or {@link android.test.InstrumentationTestRunner} in the form of
-key-value pairs, using the <code>-e</code> flag, with this syntax:
-</p>
-<pre>
--e <key> <value>
-</pre>
-<p>
- Some keys accept multiple values. You specify multiple values in a comma-separated list.
- For example, this invocation of
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a> provides multiple values for the <code>package</code> key:
-</p>
-<pre>
-$ adb shell am instrument -w -e package com.android.test.package1,com.android.test.package2 \
-> com.android.test/android.support.test.runner.AndroidJUnitRunner
-</pre>
-<p>The following table lists the key-value pairs you can use with your test runner.</p>
-<table>
- <tr>
- <th>Key</th>
- <th>Value</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>
- <code>package</code>
- </td>
- <td>
- <Java_package_name>
- </td>
- <td>
- The fully-qualified <em>Java</em> package name for one of the packages in the test
- application. Any test case class that uses this package name is executed. Notice that
- this is not an <em>Android</em> package name; a test package has a single
- Android package name but may have several Java packages within it.
- </td>
- </tr>
- <tr>
- <td rowspan="2"><code>class</code></td>
- <td><class_name></td>
- <td>
- The fully-qualified Java class name for one of the test case classes. Only this test
- case class is executed.
- </td>
- </tr>
- <tr>
- <td><class_name><strong>#</strong>method name</td>
- <td>
- A fully-qualified test case class name, and one of its methods. Only this method is
- executed. Note the hash mark (#) between the class name and the method name.
- </td>
- </tr>
- <tr>
- <td><code>func</code></td>
- <td><code>true</code></td>
- <td>
- Runs all test classes that extend {@link android.test.InstrumentationTestCase}.
- </td>
- </tr>
- <tr>
- <td><code>unit</code></td>
- <td><code>true</code></td>
- <td>
- Runs all test classes that do <em>not</em> extend either
- {@link android.test.InstrumentationTestCase} or
- {@link android.test.PerformanceTestCase}.
- </td>
- </tr>
- <tr>
- <td><code>size</code></td>
- <td>
- [<code>small</code> | <code>medium</code> | <code>large</code>]
- </td>
- <td>
- Runs a test method annotated by size. The annotations are <code>@SmallTest</code>,
- <code>@MediumTest</code>, and <code>@LargeTest</code>.
- </td>
- </tr>
- <tr>
- <td><code>perf</code></td>
- <td><code>true</code></td>
- <td>
- Runs all test classes that implement {@link android.test.PerformanceTestCase}.
- When you use this option, also specify the <code>-r</code> flag for
- <code>am instrument</code>, so that the output is kept in raw format and not
- re-formatted as test results.
- </td>
- </tr>
- <tr>
- <td><code>debug</code></td>
- <td><code>true</code></td>
- <td>
- Runs tests in debug mode.
- </td>
- </tr>
- <tr>
- <td><code>log</code></td>
- <td><code>true</code></td>
- <td>
- Loads and logs all specified tests, but does not run them. The test
- information appears in <code>STDOUT</code>. Use this to verify combinations of other
- filters and test specifications.
- </td>
- </tr>
- <tr>
- <td><code>emma</code></td>
- <td><code>true</code></td>
- <td>
- Runs an EMMA code coverage analysis and writes the output to
- <code>/data/<app_package>/coverage.ec</code> on the device. To override the
- file location, use the <code>coverageFile</code> key that is described in the
- following entry.
- <p class="note">
- <strong>Note:</strong> This option requires an EMMA-instrumented build of the test
- application, which you can generate with the <code>coverage</code> target.
- </p>
- </td>
- </tr>
- <tr>
- <td><code>coverageFile</code></td>
- <td><code><filename></code></td>
- <td>
- Overrides the default location of the EMMA coverage file on the device. Specify this
- value as a path and filename in UNIX format. The default filename is described in the
- entry for the <code>emma</code> key.
- </td>
- </tr>
-</table>
-<strong><code>-e</code> Flag Usage Notes</strong>
-<ul>
- <li>
- <code>am instrument</code> invokes
- {@link android.test.InstrumentationTestRunner#onCreate(Bundle)}
- with a {@link android.os.Bundle} containing the key-value pairs.
- </li>
- <li>
- The <code>package</code> key takes precedence over the <code>class</code> key. If you
- specifiy a package, and then separately specify a class within that package, Android
- will run all the tests in the package and ignore the <code>class</code> key.
- </li>
- <li>
- The <code>func</code> key and <code>unit</code> key are mutually exclusive.
- </li>
-</ul>
-<h3 id="RunTestExamples">Usage examples</h3>
-<p>
-The following sections provide examples of using <code>am instrument</code> to run tests.
-They are based on the following structure:</p>
-<ul>
- <li>
- The test package has the Android package name <code>com.android.demo.app.tests</code>
- </li>
- <li>
- Two instrumented test classes:
- <ul>
- <li>{@code Foo1} which contains the test method {@code bar1}, and</li>
- <li>{@code Foo2} which contains test methods {@code bar2} and {@code bar3}</li>
- </ul>
- </li>
- <li>
- The test runner is
-<a href="{@docRoot}reference/android/support/test/runner/AndroidJUnitRunner.html">
-{@code AndroidJUnitRunner}</a>.
- </li>
-</ul>
-<h4>Running the entire test package</h4>
-<p>
- To run all of the test classes in the test package, enter:
-</p>
-<pre>
-$ adb shell am instrument -w com.android.demo.app.tests/android.support.test.runner.AndroidJUnitRunner
-</pre>
-<h4>Running all tests in a test case class</h4>
-<p>
- To run all of the tests in the class <code>UnitTests</code>, enter:
-</p>
-<pre>
-$ adb shell am instrument -w \
-> -e class com.android.demo.app.tests.Foo \
-> com.android.demo.app.tests/android.support.test.runner.AndroidJUnitRunner
-</pre>
-<p>
- <code>am instrument</code> gets the value of the <code>-e</code> flag, detects the
- <code>class</code> keyword, and runs all the methods in the <code>UnitTests</code> class.
-</p>
-<h4>Selecting a subset of tests</h4>
-<p>
- To run all of the tests in <code>Foo1</code>, and the <code>bar3</code> method in
- <code>Foo2</code>, enter:
-</p>
-<pre>
-$ adb shell am instrument -w \
-> -e class com.android.demo.app.tests.Foo1,com.android.demo.app.tests.Foo2#bar3 \
-> com.android.demo.app.tests/android.support.test.runner.AndroidJUnitRunner
-</pre>
+++ /dev/null
-<ul id="nav">
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot
-?>sdk/index.html"><span class="en">Download</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>sdk/installing/index.html">
- <span class="en">Install Android Studio</span></a></li>
- </ul>
- </li>
-
-
-<!-- Workflow menu-->
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/workflow/index.html"><span class="en">Workflow</span></a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/projects/index.html">
- <span class="en">Projects</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/building/index.html">
- <span class="en">Build and Run</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/devices/index.html">
- <span class="en">Virtual Devices</span></a></li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/device.html">
- <span class="en">Hardware Devices</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/extras/oem-usb.html">
- <span class="en">USB Drivers</span></a></li>
- </ul>
- </li>
-
- <li><a href="<?cs var:toroot?>tools/testing/index.html">
- <span class="en">Testing</span></a>
- </li>
-
- <li><a href="<?cs var:toroot ?>tools/debugging/index.html">
- <span class="en">Debugging</span></a></li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/publishing/publishing_overview.html"
- zh-cn-lang="发布概述"><span class="en">Publishing</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/publishing/preparing.html" zh-cn-lang="准备发布"><span class="en">Preparing for Release</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/publishing/versioning.html"><span class="en">Versioning Your Apps</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/publishing/app-signing.html"><span class="en">Signing Your Apps</span></a></li>
- </ul>
- </li>
-
- </ul>
- </li> <!-- end of Workflow -->
-
-
-<!-- Android Studio menu-->
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot?>tools/studio/index.html"><span class="en">Android Studio</span></a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/studio/studio-features.html">
- Features</a></li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/studio/studio-config.html">
- Configuration</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/sdk-manager.html">SDK Manager</a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>sdk/installing/create-project.html">
- Project Tools</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/project-mgmt.html">
- <span class="en">Project Structure Management</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/projects/templates.html">
- <span class="en">Using Code Templates</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/building/building-studio.html">
- <span class="en">Building and Running</span></a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/studio/code-tools.html">
- Code Tools</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/debugging/improving-w-lint.html">
- <span class="en">Improving Your Code with lint</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/debugging/annotations.html">
- <span class="en">Improving Code Inspection with Annotations</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/proguard.html">
- <span class="en">Shrink Your Code and Resources</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/app-link-indexing.html">
- <span class="en">Supporting URLs and App Indexing in Android Studio</span></a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/studio/ui-tools.html">
- UI Tools</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>sdk/installing/studio-layout.html">
- <span class="en">Layout Editor</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/theme-editor.html">
- <span class="en">Theme Editor</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/translations-editor.html">
- <span class="en">Translations Editor</span></a>
- <li><a href="<?cs var:toroot ?>tools/help/vector-asset-studio.html">
- <span class="en">Vector Asset Studio</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/image-asset-studio.html">
- <span class="en">Image Asset Studio</span></a></li>
- </ul>
- </li>
-
- <li><a href="<?cs var:toroot ?>tools/devices/managing-avds.html">
- <span class="en">AVD Manager</span></a></li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/devices/emulator.html">
- <span class="en">Android Emulator</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/emulator.html">Android Emulator
- Command-Line Features</a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/debugging/debugging-studio.html">
- <span class="en">Debugging Tools</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/debugging/ddms.html">
- <span class="en">DDMS</span></a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/help/android-monitor.html">Android Monitor</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/am-basics.html"><span
- class="en">Android Monitor Basics</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-logcat.html"><span
- class="en">logcat Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-memory.html"><span
- class="en">Memory Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-cpu.html"><span
- class="en">CPU Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-gpu.html"><span
- class="en">GPU Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-network.html"><span
- class="en">Network Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-hprof.html"><span
- class="en">HPROF Viewer and Analyzer</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-allocation.html"><span
- class="en">Allocation Tracker</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-methodtrace.html"><span
- class="en">Method Trace</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-sysinfo.html"><span
- class="en">System Information</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-screenshot.html"><span
- class="en">Screen Capture</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/am-video.html"><span
- class="en">Video Capture</span></a>
- </li>
- </li>
- </ul>
- </li>
-
- <li><a href="<?cs var:toroot ?>sdk/installing/studio-tips.html">
- Tips and Tricks</a></li>
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>sdk/installing/migrate.html">
- <span class="en">
- Migrating from Eclipse ADT</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/studio/eclipse-transition-guide.html">
- <span class="en">Transition Guide</span></a></li>
- </ul>
- </li>
- </ul>
-
- </li><!-- End of Android Studio menu -->
-
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/help/index.html"><span
-class="en">Tools Help</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/adb.html">adb</a></li>
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/help/android.html">android</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/devices/managing-avds-cmdline.html"><span class="en">
- Managing AVDs</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/projects/projects-cmdline.html"><span class="en">
- Managing Projects</span></a></li>
- </ul>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/avd-manager.html">AVD Manager</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/bmgr.html">bmgr</a>
- <li><a href="<?cs var:toroot ?>tools/help/desktop-head-unit.html">Desktop Head Unit</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/monitor.html">Device Monitor</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/dmtracedump.html">dmtracedump</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/draw9patch.html">Draw 9-Patch</a></li>
-
- <li><a href="<?cs var:toroot ?>tools/help/etc1tool.html">etc1tool</a></li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/help/hierarchy-viewer.html">
- <span class="en">Hierarchy Viewer</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/debugging/debugging-ui.html">
- <span class="en">Optimizing your UI</span></a></li>
- </ul>
- </li>
-
- <li><a href="<?cs var:toroot ?>tools/help/hprof-conv.html">hprof-conv</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/image-asset-studio.html">Image Asset Studio</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/jobb.html">jobb</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/lint.html">lint</span></a></li>
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/help/logcat.html">logcat</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/debugging/debugging-log.html">
- <span class="en">Reading and Writing Logs</span></a></li>
- </ul>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/mksdcard.html">mksdcard</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/gltracer.html">Tracer for OpenGL ES</a></li>
-
-
- <li><a href="<?cs var:toroot ?>tools/help/zipalign.html">zipalign</a></li>
-
- </ul>
- </li>
-
- </li><!-- end of tools help -->
-
-
-<!-- Build System menu-->
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>sdk/installing/studio-build.html">Build System</a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/building/building-cmdline.html">
- <span class="en">Running Gradle Builds</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/building/configuring-gradle.html">
- <span class="en">Configuring Gradle Builds</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/building/plugin-for-gradle.html">
- <span class="en">Android Plugin for Gradle</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/building/manifest-merge.html">
- <span class="en">Manifest Merging</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/building/multidex.html">
- <span class="en">Apps Over 64K Methods</span></a></li>
- </ul>
- </li><!-- end of build system -->
-
-
-<!-- Performance Tools menu-->
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/performance/index.html">Performance Tools</a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/debug-gpu-overdraw/index.html">
- Overdraw Debugger</a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/performance/profile-gpu-rendering/index.html">
- Rendering Profiler</a>
- </li>
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/performance/hierarchy-viewer/index.html">
- Hierarchy Viewer</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/hierarchy-viewer/setup.html"><span
- class="en">Setup</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/performance/hierarchy-viewer/profiling.html"><span
- class="en">Profiling</span></a>
- </li>
- </ul>
- </li>
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/performance/comparison.html">
- Memory Profilers</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/memory-monitor/index.html"><span
- class="en">Memory Monitor</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/performance/heap-viewer/index.html"><span
- class="en">Heap Viewer</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/performance/allocation-tracker/index.html"><span
- class="en">Allocation Tracker</span></a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/debugging/debugging-memory.html">
- <span class="en">Investigating Your RAM Usage</span></a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/debugging/debugging-tracing.html">
- <span class="en">Traceview</span></a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/traceview/index.html">
- Walkthrough</a>
- </li>
- <li><a href="<?cs var:toroot ?>tools/help/traceview.html">
- Command Reference</a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/debugging/systrace.html">
- <span class="en">Systrace</span></a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/systrace/index.html">
- Walkthrough</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/systrace.html">
- Command Reference</a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/performance/batterystats-battery-historian/index.html">
- Battery Profilers</a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/performance/batterystats-battery-historian/charts.html"><span
- class="en">Historian Charts</span></a>
- </li>
- </ul>
- </li>
- </ul>
- </li><!-- End Performance Tools menu-->
-
-
- <!-- Testing Tools menu-->
-
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/testing/testing-tools.html">
- <span class="en">Testing Tools</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/testing/testing_android.html">Testing Concepts</a></li>
- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/testing-support-library/index.html"><span
-class="en">Testing Support Library</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>reference/android/support/test/package-summary.html">
- API Reference</a></li>
- </ul>
- </li>
- <li><a href="<?cs var:toroot ?>training/testing/start/index.html">
- Testing with Android Studio</a></li>
- <li><a href="<?cs var:toroot ?>tools/testing/testing_otheride.html">
- Testing from the Command-Line</a></li>
- <li><a href="<?cs var:toroot ?>tools/help/monkey.html">monkey</a></li>
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot
-?>tools/help/monkeyrunner_concepts.html"><span class="en">monkeyrunner</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/help/MonkeyDevice.html"><span
-class="en">MonkeyDevice</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/MonkeyImage.html"><span
-class="en">MonkeyImage</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/help/MonkeyRunner.html"><span
-class="en">MonkeyRunner</span></a></li>
- </ul>
- </li>
- </ul>
- </li><!-- end of testing support library -->
-
-
-<!-- Support Library menu-->
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/support-library/index.html"><span
-class="en">Support Library</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/support-library/features.html">Features</a></li>
- <li><a href="<?cs var:toroot ?>tools/support-library/setup.html">Setup</a></li>
- </ul>
- </li><!-- end of support library -->
-
- <li class="nav-section">
- <div class="nav-section-header empty"><a href="<?cs var:toroot ?>tools/data-binding/guide.html"><span
-class="en">Data Binding Library</span></a></div>
- </li><!-- end of support library -->
-
-
-<!-- Revision menu-->
-
- <li class="nav-section">
- <div class="nav-section-header"><a href="<?cs var:toroot
-?>tools/revisions/index.html"><span class="en">Revisions</span></a></div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/revisions/studio.html">
- <span class="en">Android Studio</span>
- </a></li>
- <li><a href="<?cs var:toroot ?>tools/sdk/tools-notes.html">
- <span class="en">SDK Tools</span>
- </a></li>
- <li><a href="<?cs var:toroot ?>tools/revisions/build-tools.html">
- <span class="en">SDK Build Tools</span>
- </a></li>
- <li><a href="<?cs var:toroot ?>tools/revisions/gradle-plugin.html">
- <span class="en">Android Plugin for Gradle</span>
- </a></li>
- <li><a href="<?cs var:toroot ?>tools/revisions/platforms.html">
- <span class="en">SDK Platforms</span></a></li>
- <li><a href="<?cs var:toroot ?>tools/sdk/eclipse-adt.html">
- <span class="en">ADT Plugin</span></a></li>
- </ul>
- </li>
-
- <li class="nav-section">
- <div class="nav-section-header empty">
- <a href="<?cs var:toroot ?>tools/sdk/ndk/index.html">NDK</a>
- </div>
- </li>
-
-<!-- <li class="nav-section">
- <div class="nav-section-header">
- <a href="<?cs var:toroot ?>tools/adk/index.html">
- <span class="en">ADK</span></a>
- </div>
- <ul>
- <li><a href="<?cs var:toroot ?>tools/adk/adk2.html">ADK 2012 Guide</a></li>
- <li><a href="<?cs var:toroot ?>tools/adk/adk.html">ADK 2011 Guide</a></li>
- </ul>
- </li> -->
-
-<script type="text/javascript">
-<!--
- buildToggleLists();
- changeNavLang(getLangPref());
-//-->
-</script>
+++ /dev/null
-page.title=Introduction
-@jd:body
-
-<p>Developing applications for Android devices is facilitated by a group of tools that are
- provided with the SDK. You can access these tools through Android Studio or from the command line. Developing with Android Studio is the preferred method because
- it can directly invoke the tools that you need while developing applications.</p>
-
- <p>However, you may choose to develop with another IDE or a simple text editor and invoke the
- tools on the command line or with scripts. This is a less streamlined way to develop because you
- will sometimes have to call command line tools manually, but you will have access to the same
- number of features that you would have in Android Studio.</p>
-
-<div class="figure" style="width:461px">
- <img src="{@docRoot}images/developing/developing_overview.png"
- alt="Development process for Android applications"
- height="738" />
- <p class="img-caption">
- <strong>Figure 1.</strong> The development process for Android applications.
- </p>
-</div>
-
-<p>The basic steps for developing applications (with or without Android Studio) are shown in figure 1. The
-development steps encompass four development phases, which include:</p>
-
-<ul>
- <li><strong>Setup</strong>
- <p>During this phase you install and set up your development environment. You also create
- Android Virtual Devices (AVDs) and connect hardware devices on which you can install your
- applications.</p>
- <p>See <a href="{@docRoot}tools/devices/index.html">Managing Virtual Devices</a>
- and <a href="{@docRoot}tools/device.html">Using Hardware Devices</a> for more
- information.
- </li>
- <li><strong>Development</strong>
- <p>During this phase you set up and develop your Android project, which contains all of the
- source code and resource files for your application. For more informations, see
- <a href="{@docRoot}tools/projects/index.html">Create an Android project</a>.</p>
- </li>
- <li><strong>Debugging and Testing</strong>
- <p>During this phase you build your project into a debuggable <code>.apk</code> package that you
- can install and run on the emulator or an Android-powered device. Android Studio uses
- a build system based on <a href="http://www.gradle.org/" target="_android">Gradle</a>
- that provides flexibility, customized build variants, dependency resolution, and much more.
- If you're using another IDE, you can build your project using Gradle and install it on a device
- using <a href="{@docRoot}tools/help/adb.html">adb</a>. For more information, see
- <a href="{@docRoot}tools/building/index.html">Build and run your application</a>.</p>
- <p>Next, you debug your application using a JDWP-compliant debugger along with the debugging
- and logging tools that are provided with the Android SDK. Android Studio already comes packaged with
- a compatible debugger. For more information see,
- <a href="{@docRoot}tools/debugging/index.html">Debug your application with the
- SDK debugging and logging tools</a>.</p>
- <p>Last, you test your application using various Android SDK testing tools. For more
- information, see <a href="{@docRoot}tools/testing/index.html">Test your application
- with the Testing and Instrumentation framework</a>.</p>
- </li>
- <li><strong>Publishing</strong>
- <p>During this phase you configure and build your application for release and distribute your
- application to users. For more information, see
- <a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing Overview</a>.</p>
- </li>
-</ul>
-
-<h2 id="EssentialTools">Essential command line tools</h2>
-
- <p>When developing in IDEs or editors other than Android Studio, be familiar with
- all of the tools below, because you will have to run them from the command line.</p>
-
- <dl>
- <dt><a href="{@docRoot}tools/help/android.html">android</a></dt>
-
- <dd>Create and update Android projects and create, move, and delete AVDs.</dd>
-
- <dt><a href="{@docRoot}tools/devices/emulator.html">Android Emulator</a></dt>
-
- <dd>Run your Android applications on an emulated Android platform.</dd>
-
- <dt><a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a></dt>
-
- <dd>Interface with your emulator or connected device (install apps, shell the device, issue
- commands, etc.).</dd>
- </dl>
-
- <p>In addition to the above tools that are included with the SDK, you need the following open
- source and third-party tools:</p>
-
- <dl>
- <a href="http://www.gradle.org/">Gradle</a>
-
- <dd>To compile and build your Android project into an installable .apk file.</dd>
-
- <dt>Keytool</dt>
-
- <dd>To generate a keystore and private key, used to sign your .apk file. Keytool is part of the
- JDK.</dd>
-
- <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
- JDK.</dd>
- </dl>
-
- <p>If you are using Android Studio, tools such as <code>adb</code> and <code>android</code>
- are automatically called by Android Studio, 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
- Android Studio, 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 Android Studio to do this automatically as well.</p>
-
-<p>For more information on the tools provided with the Android SDK, see the
- <a href="{@docRoot}tools/index.html">Tools</a> section of the documentation.</p>
-
-<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
- section for documentation.
-</p>
-<h3 id="IntelliJ">Developing in IntelliJ IDEA</h3>
-<div style="float: right">
-<img alt="The IntelliJ graphical user interface" height="500px"
-src="{@docRoot}images/developing/intellijidea_android_ide.png"/>
-</div>
-<p>
- IntelliJ IDEA is a powerful Java IDE from JetBrains that provides
- full-cycle Android development support in both the free Community
- Edition and the Ultimate edition.
-</p>
-<p>
- The IDE ensures compatibility with the latest Android SDK and offers a
- smart code editor with completion, quick navigation between code and
- resources, a graphical debugger, unit testing support using Android
- Testing Framework, and the ability to run applications in either the
- emulator or a USB-connected device.
-</p>
-<p>
- <strong>Links:</strong>
-</p>
-<ul>
- <li>
- <a href="http://www.jetbrains.com/idea">IntelliJ IDEA official website</a>
-</li>
- <li>
- <a href="http://www.jetbrains.com/idea/features/google_android.html">Android support in IntelliJ IDEA</a>
-</li>
- <li>
- <a href="http://wiki.jetbrains.net/intellij/Android">IntelliJ IDEA Android Tutorials</a>
- </li>
-</ul>
+++ /dev/null
-page.title=Developer Workflow
-@jd:body
-
-<p>To develop apps for Android, you use a set of tools that are included in Android Studio.
-In addition to using the tools from Android Studio,
-you can also access most of the SDK tools from the command line. Developing with Android Studio is the
-preferred method because it can directly invoke the tools that you need while developing applications.</p>
-
-<p>However, you may choose to develop with another IDE or a simple text editor and invoke the
-tools on the command line or with scripts. This is a less streamlined way to develop because you
-will sometimes have to call command line tools manually, but you will have access to the same
-number of features that you would have in Android Studio.</p>
-
-<div class="figure" style="width:461px">
- <img src="{@docRoot}images/developing/developing_overview.png"
- alt="Development process for Android applications"
- height="738" />
- <p class="img-caption">
- <strong>Figure 1.</strong> The development process for Android applications.
- </p>
-</div>
-
-<h2>App Workflow</h2>
-
-<p>The basic steps for developing applications (with or without Android Studio) are shown in
-figure 1. The development steps encompass four development phases, which include:</p>
-
-<ul>
- <li><strong>Environment Setup</strong>
- <p>During this phase you install and set up your development environment. You also create
- Android Virtual Devices (AVDs) and connect hardware devices on which you can install your
- applications.</p>
- <p>See <a href="{@docRoot}tools/devices/index.html">Managing Virtual Devices</a>
- and <a href="{@docRoot}tools/device.html">Using Hardware Devices</a> for more
- information.
- </li>
- <li><strong>Project Setup and Development</strong>
- <p>During this phase you set up and develop your Android Studio project and application modules,
- which contain all of the source code and resource files for your application. For more
- information, see
- <a href="{@docRoot}tools/projects/index.html">Create an Android project</a>.</p>
- </li>
- <li><strong>Building, Debugging and Testing</strong>
- <p>During this phase you build your project into a debuggable <code>.apk</code> package(s)
- that you can install and run on the emulator or an Android-powered device. Android Studio uses
- a build system based on <a href="http://www.gradle.org/" target="_android">Gradle</a>
- that provides flexibility, customized build variants, dependency resolution, and much more.
- If you're using another IDE, you can build your project using Gradle and install it on a device
- using <a href="{@docRoot}tools/help/adb.html">adb</a>. For more information, see
- <a href="{@docRoot}tools/building/index.html">Build and run your application</a>.</p>
- <p>Next, with Android Studio you debug your application using the
- <a href="{@docRoot}tools/help/monitor.html">Android Device Monitor</a> and device log messages
- (<a href="{@docRoot}tools/help/logcat.html">logcat</a>) along with the IntelliJ IDEA intelligent
- coding features. You can also use a JDWP-compliant debugger along with the debugging and logging
- tools that are provided with the Android SDK. For more information see
- <a href="{@docRoot}tools/debugging/index.html">Debug your application with the SDK debugging and logging tools</a>.</p>
- <p>Last, you test your application using various Android SDK testing tools. For more
- information, see <a href="{@docRoot}tools/testing/index.html">Test your application
- with the Testing and Instrumentation framework</a>.</p>
- </li>
- <li><strong>Publishing</strong>
- <p>During this phase you configure and build your application for release and distribute your
- application to users. For more information, see
- <a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing
- Overview</a>.</p>
- </li>
-</ul>
-
-
-
-<h2 id="EssentialTools">Essential command line tools</h2>
-
- <p>When developing in IDEs or editors other than Android Studio, be familiar with
- all of the tools below, because you will have to run them from the command line or script.</p>
-
- <dl>
- <dt><a href="{@docRoot}tools/help/android.html">android</a></dt>
-
- <dd>Create and update Android projects and create, move, and delete AVDs.</dd>
-
- <dt><a href="{@docRoot}tools/help/emulator.html">Android Emulator</a></dt>
-
- <dd>Run your Android applications on an emulated Android platform.</dd>
-
- <dt><a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a></dt>
-
- <dd>Interface with your emulator or connected device (install apps, shell the device, issue
- commands, etc.).</dd>
- </dl>
-
- <p>In addition to the above tools that are included with the SDK, you need the following open
- source and third-party tools:</p>
-
- <dl>
- <dt><a href="http://www.gradle.org/">Gradle</a> </dt>
-
- <dd>To compile and build your Android project into an installable .apk file(s).</dd>
-
- <dt>Keytool</dt>
-
- <dd>To generate a keystore and private key, used to sign your .apk file. Keytool is part of the
- JDK.</dd>
-
- <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
- JDK.</dd>
- </dl>
-
- <p>If you are using Android Studio, tools such as <code>adb</code> and <code>android</code>
- are automatically called by Android Studio 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 Android Studio, 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 Android Studio
- to do this automatically as well.</p>
-
-<p>For more information on the tools provided with the Android SDK, see the
- <a href="{@docRoot}tools/help/index.html">Tools</a> section of the documentation.</p>
-
-
-
OSDN Git Service
