diff options
Diffstat (limited to 'docs/html/tools')
| -rw-r--r-- | docs/html/tools/building/buidling-cmdline-ant.jd | 381 | ||||
| -rw-r--r-- | docs/html/tools/building/building-eclipse.jd | 6 | ||||
| -rw-r--r-- | docs/html/tools/building/plugin-for-gradle.jd | 6 | ||||
| -rw-r--r-- | docs/html/tools/help/adb.jd | 56 | ||||
| -rw-r--r-- | docs/html/tools/help/desktop-head-unit.jd | 439 | ||||
| -rw-r--r-- | docs/html/tools/revisions/studio.jd | 27 | ||||
| -rw-r--r-- | docs/html/tools/sdk/eclipse-adt.jd | 35 | ||||
| -rw-r--r-- | docs/html/tools/support-library/features.jd | 194 | ||||
| -rw-r--r-- | docs/html/tools/support-library/index.jd | 34 | ||||
| -rw-r--r-- | docs/html/tools/tools_toc.cs | 1 |
10 files changed, 751 insertions, 428 deletions
diff --git a/docs/html/tools/building/buidling-cmdline-ant.jd b/docs/html/tools/building/buidling-cmdline-ant.jd deleted file mode 100644 index 51158de..0000000 --- a/docs/html/tools/building/buidling-cmdline-ant.jd +++ /dev/null @@ -1,381 +0,0 @@ -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="#AntReference">Ant Command Reference</a></li> - </ol> - <h2>See also</h2> - <ol> - <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>There are two ways to build your application using the Ant build script: one for - testing/debugging your application — <em>debug mode</em> — and one for building your - final package for release — <em>release mode</em>. Regardless of which way you build your application, - it 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 in debug mode or release mode, you need to use the Ant tool to compile - and build your project. This will create the .apk file that you can install on an emulator or device. - When you build in debug mode, the .apk file is automatically signed by the SDK tools with - a debug key, 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 in release mode, the .apk file is <em>unsigned</em>, so you - must manually sign it with your own private key, using Keytool and Jarsigner.</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 Ant, you can obtain it from the <a href="http://ant.apache.org/">Apache Ant - home page</a>. Install it and make sure it is in your executable PATH. Before calling Ant, 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 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:</p> - - <ol> - <li>Open a command-line and navigate to the root of your project directory.</li> - <li>Use Ant to compile your project in debug mode: - <pre> -ant debug -</pre> - - <p>This creates your debug <code>.apk</code> file inside the project <code>bin/</code> directory, named - <code><your_project_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> - </li> - </ol> - - <p>Each time you change a source file or resource, you must run Ant 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 following section about <a href= - "#RunningOnEmulator">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:</p> - - <ol> - <li>Open a command-line and navigate to the root of your project directory.</li> - - <li>Use Ant to compile your project in release mode: - <pre> -ant release -</pre> - </li> - </ol> - - <p>This creates your Android application .apk file inside the project <code>bin/</code> - directory, named <code><em><your_project_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 project's {@code ant.properties} file. With this information provided, - the build script will prompt you for your keystore and alias password when you build in release - mode and produce your final application package, which will be ready for distribution.</p> - - <p class="caution"><strong>Caution:</strong> Due to the way Ant handles input, the password that - you enter during the build process <strong>will be visible</strong>. If you are concerned about - your keystore and alias password being visible on screen, then you may prefer to perform the - application signing manually, via Jarsigner (or a similar tool). To instead perform the signing - procedure manually, <a href="#ManualReleaseMode">build unsigned</a> and then continue with - <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p> - - <p>To specify your keystore and alias, open the project {@code ant.properties} file (found in - the root of the project directory) and add entries for {@code key.store} and {@code key.alias}. - For example:</p> - <pre> -key.store=path/to/my.keystore -key.alias=mykeystore -</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 project directory.</li> - - <li>Use Ant to compile your project in release mode: - <pre> -ant release -</pre> - </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 project <code>bin/</code> - directory, named <code><em><your_project_name></em>-release.apk</code>. This .apk file has - been signed with the private key specified in {@code ant.properties} 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 project {@code bin/} - 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. - <ul> - <li>On most devices running Android 3.2 or older, you can find the option under - <strong>Settings > Applications > Development</strong>.</li> - <li>On Android 4.0 and newer, it's in <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> - </ul> - </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 compile 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>The ADT plugin helps you get started quickly by signing your .apk files with a debug key, - prior to installing them on an emulator or development device. This means that you can quickly - run your application from Eclipse without having to generate your own private key. No specific - action on your part is needed, provided ADT has access to Keytool. 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 exporting - and signing your application with the ADT's Export Wizard.</p> - - <h2 id="AntReference">Ant Command Reference</h2> - <dt><code>ant clean</code></dt> - <dd>Cleans the project. If you include the <code>all</code> target before <code>clean</code> -(<code>ant all clean</code>), other projects are also cleaned. For instance if you clean a -test project, the tested project is also cleaned.</dd> - - <dt><code>ant debug</code></dt> - <dd>Builds a debug package. Works on application, library, and test projects and compiles - dependencies as needed.</dd> - - <dt id="emma"><code>ant emma debug</code></dt> - <dd>Builds a test project while building the tested project with instrumentation turned on. - This is used to run tests with code coverage enabled.</dd> - - <dt><code>ant release</code></dt> - <dd>Builds a release package.</dd> - - <dt><code>ant instrument</code> - </dt> - <dd>Builds an instrumented debug package. This is generally called automatically when building a - test project with code coverage enabled (with the <code>emma</code> - target)</dd> - - <dt><code>ant <build_target> install</code></dt> - <dd>Builds and installs a package. Using <code>install</code> by itself fails.</dd> - - <dt><code>ant installd</code></dt> - <dd>Installs an already compiled debug package. This fails if the <code>.apk</code> is not - already built.</dd> - - <dt><code>ant installr</code></dt> - <dd>Installs an already compiled release package. This fails if the <code>.apk</code> is not - already built.</dd> - - <dt><code>ant installt</code></dt> - <dd>Installs an already compiled test package. Also installs the <code>.apk</code> of the - tested application. This fails if the <code>.apk</code> is not already built.</dd> - - <dt><code>ant installi</code></dt> - <dd>Installs an already compiled instrumented package. This is generally not used manually as - it's called when installing a test package. This fails if the <code>.apk</code> is not already - built.</dd> - - <dt><code>ant test</code></dt> - <dd>Runs the tests (for test projects). The tested and test <code>.apk</code> files must be - previously installed.</dd> - - <dt><code>ant debug installt test</code></dt> - <dd>Builds a test project and the tested project, installs both <code>.apk</code> files, and - runs the tests.</dd> - - <dt><code>ant emma debug install test</code></dt> - <dd>Builds a test project and the tested project, installs both <code>.apk</code> files, and - runs the tests with code coverage enabled.</dd> - diff --git a/docs/html/tools/building/building-eclipse.jd b/docs/html/tools/building/building-eclipse.jd index 79ef3de..89c3e16 100644 --- a/docs/html/tools/building/building-eclipse.jd +++ b/docs/html/tools/building/building-eclipse.jd @@ -34,12 +34,12 @@ parent.link=index.html <p>This document shows you how to run your application on an emulator or a real device from Eclipse—all of which is done using the debug version of your application. For more information about how to sign your application with a private key for release, see <a href= - "{@docRoot}tools/workflow/publishing/app-signing.html#ExportWizard">Signing Your Applications</a></p> + "{@docRoot}tools/publishing/app-signing.html#ExportWizard">Signing Your Applications</a></p> <h2 id="RunningOnEmulatorEclipse">Running on the emulator</h2> <p>Before you can run your application on the Android Emulator, you must <a href= - "{@docRoot}tools/workflow/devices/managing-avds.html">create an AVD</a>.</p> + "{@docRoot}tools/devices/managing-avds.html">create an AVD</a>.</p> <p>To run (or debug) your application, select <strong>Run</strong> > <strong>Run</strong> (or <strong>Run</strong> > <strong>Debug</strong>) from the Eclipse menu bar. The ADT plugin will @@ -100,7 +100,7 @@ parent.link=index.html <li>Ensure that your development computer can detect your device when connected via USB</li> </ul> - <p>Read <a href="{@docRoot}tools/workflow/devices/device.html">Using Hardware Devices</a> + <p>Read <a href="{@docRoot}tools/device.html">Using Hardware Devices</a> for more information.</p> <p>Once set up and your device is connected via USB, install your application on the device by diff --git a/docs/html/tools/building/plugin-for-gradle.jd b/docs/html/tools/building/plugin-for-gradle.jd index c1ec425..513153d 100644 --- a/docs/html/tools/building/plugin-for-gradle.jd +++ b/docs/html/tools/building/plugin-for-gradle.jd @@ -112,7 +112,7 @@ several kinds of modules:</p> 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>Project Build File</h3> +<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 @@ -144,7 +144,7 @@ allprojects { 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>Module Build File</h3> +<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> @@ -378,7 +378,7 @@ and two <em>dimensions</em> of product flavors, one for app type (demo or full) CPU/ABI (x86, ARM, or MIPS). </p> -<h3>Source directories</h3> +<h3 id="sourceDirectories">Source directories</h3> <p>To build each version of your app, the build system combines source code and resources from:</p> diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index 641d463..2faff4f 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -420,62 +420,54 @@ Wi-Fi, as described here. <ol> <li> -Connect Android device and adb host computer +<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. -</li> +whose firewall is configured properly to support adb.</p> -<li> -Connect the device with USB cable to host. +<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> -Make sure adb is running in USB mode on host. -<pre> -$ adb usb -restarting in USB mode -</pre> +Connect the device to the host computer with a USB cable. </li> <li> -Connect to the device over USB. -<pre> -$ adb devices -List of devices attached -######## device +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> -Restart host adb in tcpip mode. -<pre> -$ adb tcpip 5555 -restarting in TCP mode port: 5555 -</pre> +Disconnect the USB cable from the target device. </li> <li> -Find out the IP address of the Android device: -Settings -> About tablet -> Status -> IP address. -Remember the IP address, of the form <code>#.#.#.#</code>. +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 adb host to device: -<pre> -$ adb connect #.#.#.# -connected to #.#.#.#:5555 +Connect to the device, identifying it by IP address. +<pre class="no-pretty-print"> +$ adb connect <device-ip-address> </pre> </li> + <li> -Remove USB cable from device, and confirm you can still access device: -<pre> +Confirm that your host computer is connected to the target device: +<pre class="no-pretty-print"> $ adb devices List of devices attached -#.#.#.#:5555 device +<device-ip-address>:5555 device </pre> </ol> @@ -500,10 +492,10 @@ Reconnect by executing the "adb connect" step again. <li> Or if that doesn't work, reset your adb host: -<pre> +<pre class="no-pretty-print"> adb kill-server </pre> and then start over from the beginning. </li> -</ol>
\ No newline at end of file +</ol> diff --git a/docs/html/tools/help/desktop-head-unit.jd b/docs/html/tools/help/desktop-head-unit.jd new file mode 100644 index 0000000..981979c --- /dev/null +++ b/docs/html/tools/help/desktop-head-unit.jd @@ -0,0 +1,439 @@ +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> + + + + diff --git a/docs/html/tools/revisions/studio.jd b/docs/html/tools/revisions/studio.jd index c922b28..298b173 100644 --- a/docs/html/tools/revisions/studio.jd +++ b/docs/html/tools/revisions/studio.jd @@ -43,6 +43,29 @@ Android Studio, as denoted by revision number. </p> <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.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/triangle-closed.png" class="toggle-content-img" alt=""/>Android Studio v1.3.1</a> <em>(August 2015)</em> </p> <div class="toggle-content-toggleme"> @@ -60,8 +83,6 @@ Android Studio, as denoted by revision number. </p> </div> - - <div class="toggle-content closed"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" @@ -100,7 +121,7 @@ Android Studio, as denoted by revision number. </p> <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> + <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> diff --git a/docs/html/tools/sdk/eclipse-adt.jd b/docs/html/tools/sdk/eclipse-adt.jd index 08634da..3c12a64 100644 --- a/docs/html/tools/sdk/eclipse-adt.jd +++ b/docs/html/tools/sdk/eclipse-adt.jd @@ -53,6 +53,39 @@ href="http://tools.android.com/knownissues">http://tools.android.com/knownissues <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.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/triangle-closed.png" class="toggle-content-img" alt=""/>ADT 23.0.6</a> <em>(March 2015)</em> </p> @@ -75,7 +108,7 @@ href="http://tools.android.com/knownissues">http://tools.android.com/knownissues <dt>General Notes:</dt> <dd> <ul> - <li>Fixed issues with the rendering library.</li> + <li>Fixed issues with the rendering library for the visual layout editor.</li> </ul> </dd> </dl> diff --git a/docs/html/tools/support-library/features.jd b/docs/html/tools/support-library/features.jd index abe1c08..b3af7a2 100644 --- a/docs/html/tools/support-library/features.jd +++ b/docs/html/tools/support-library/features.jd @@ -17,13 +17,19 @@ page.title=Support Library Features <li><a href="#v7-mediarouter">v7 mediarouter library</a></li> <li><a href="#v7-palette">v7 palette library</a></li> <li><a href="#v7-recyclerview">v7 recyclerview library</a></li> + <li><a href="#v7-preference">v7 preference library</a></li> </ol> </li> <li><a href="#v8">v8 Support Library</a></li> <li><a href="#v13">v13 Support Library</a></li> + <li><a href="#v14-preference">v14 Preference Support Library</a></li> <li><a href="#v17-leanback">v17 Leanback Library</a></li> + <li><a href="#v17-preference">v17 Preference Library for TV</a></li> <li><a href="#annotations">Annotations Support Library</a></li> <li><a href="#design">Design Support Library</a></li> + <li><a href="#custom-tabs">Custom Tabs Support Library</a></li> + <li><a href="#percent">Percent Support Library</a></li> + <li><a href="#recommendation">Recommendation Support Library for TV</a></li> </ol> <h2>See also</h2> @@ -344,7 +350,7 @@ com.android.support:palette-v7:21.0.0 <p>The recyclerview library adds the {@link android.support.v7.widget.RecyclerView} class. This class provides support for the -<a href="{@docRoot}training/material/lists-cards.jd#RecyclerView">RecyclerView +<a href="{@docRoot}training/material/lists-cards#RecyclerView">RecyclerView widget</a>, a view for efficiently displaying large data sets by providing a limited window of data items.</p> @@ -361,6 +367,40 @@ com.android.support:recyclerview-v7:21.0.0 </pre> +<h3 id="v7-preference">v7 Preference Support Library</h3> + +<p>The +<a href="{@docRoot}reference/android/support/v7/preference/package-summary.html">preference</a> +package provides APIs to support adding preference objects, such as +{@link android.support.v7.preference.CheckBoxPreference} and +{@link android.support.v7.preference.ListPreference}, for +users to modify UI settings. </p> + +<p>The v7 Preference library adds support for interfaces, such as +{@link android.support.v7.preference.Preference.OnPreferenceChangeListener} and +{@link android.support.v7.preference.Preference.OnPreferenceClickListener}, and classes, +such as {@link android.support.v7.preference.CheckBoxPreference} and +{@link android.support.v7.preference.ListPreference}. </p> + + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/v7/preference} directory. For more information +on how to set up your project, follow the instructions in <a +href="{@docRoot}tools/support-library/setup.html#libs-with-res">Adding libraries +with resources</a>. </p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:preference-v7:23.0.0 +</pre> + + + + + + + <h2 id="v8">v8 Support Library</h2> @@ -382,7 +422,7 @@ com.android.support:recyclerview-v7:21.0.0 <p class="note"> <strong>Note:</strong> Use of RenderScript with the support library is supported with Android Studio and Gradle-based builds, as well as the Eclipse plugin and Ant build tools. The - renderscript library is located in the <code>build-tools/$VERSION/renderscript/</code> folder. + renderscript library is located in the <code>build-tools/$VERSION/renderscript/</code> folder. </p> <p>The following example shows the Gradle build script properties for this library:</p> @@ -421,6 +461,69 @@ com.android.support:support-v13:18.0.0 + + +<h2 id="v14-preference">v14 Preference Support Library</h2> + + +<p>The {@link android.support.v14.preference} package provides APIs to add support +for preference interfaces such as +{@link android.support.v14.preference.PreferenceFragment.OnPreferenceStartFragmentCallback} + and +{@link android.support.v14.preference.PreferenceFragment.OnPreferenceStartScreenCallback}, + along with classes, such as +{@link android.support.v14.preference.MultiSelectListPreference} and +{@link android.support.v14.preference.PreferenceFragment}. For detailed + information about the v14 Preference Support Library APIs, see the + <a href="{@docRoot}reference/android/support/v14/preference/package-summary.html">preference</a> + package in the API reference. +</p> + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/v14/} directory. The library does not contain user +interface resources. To include it in your application project, follow the instructions for +<a href="{@docRoot}tools/support-library/setup.html#libs-without-res">Adding libraries without +resources</a>.</p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:preference-v14:23.0.0 +</pre> + + + + +<h2 id="v17-preference">v17 Preference Support Library for TV</h2> + + +<p>The {@link android.support.v17.preference} package provides APIs for providing preference + interfaces on TV devices, including support for the +{@link android.support.v17.preference.LeanbackListPreferenceDialogFragment.ViewHolder.OnItemClickListener} +interface and classes, such as +{@link android.support.v17.preference.BaseLeanbackPreferenceFragment} and +{@link android.support.v17.preference.LeanbackPreferenceFragment}. For detailed + information about the v17 Preference Support Library APIs, see the + <a href="{@docRoot}reference/android/support/v17/preference/package-summary.html">preference</a> + package in the API reference. +</p> + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/v17/} directory. The library does not contain user +interface resources. To include it in your application project, follow the instructions for +<a href="{@docRoot}tools/support-library/setup.html#libs-without-res">Adding libraries without +resources</a>.</p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:preference-v17:23.0.0 +</pre> + + + + + <h2 id="v17-leanback">v17 Leanback Library</h2> <p>The {@link android.support.v17.leanback} package provides APIs to support @@ -506,3 +609,90 @@ com.android.support:design:22.2.0 </pre> + +<h2 id="custom-tabs">Custom Tabs Support Library</h2> + +<p>The +<a href="{@docRoot}reference/android/support/customtabs/package-summary.html">Custom Tabs</a> +package provides APIs to support adding and managing custom tabs in your apps. </p> + +<p>The Custom Tabs Support library adds support for various classes, such as +<a href="{@docRoot}reference/android/support/customtabs/CustomTabsService.html">Custom Tabs +Service</a> +and +<a href="{@docRoot}reference/android/support/customtabs/CustomTabsSCallback.html">Custom Tabs +Callback</a>. </p> + + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/customtabs} directory. For more information +on how to set up your project, follow the instructions in <a +href="{@docRoot}tools/support-library/setup.html#libs-with-res">Adding libraries +with resources</a>. </p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:customtabs:23.0.0 +</pre> + + + + +<h2 id="percent">Percent Support Library</h2> + +<p>The +<a href="{@docRoot}reference/android/support/percent/package-summary.html">Percent</a> +package provides APIs to support adding and managing percentage based dimensions in your app. </p> + +<p>The Percent Support library adds support for the +<a href="{@docRoot}reference/android/support/percent/PercentLayoutHelper.PercentLayoutParams.html"> +PercentLayoutHelper.PercentLayoutParams</a> interface +and various classes, such as +<a href="{@docRoot}reference/android/support/percent/PercentFrameLayout.html">PercentFrameLayout</a> +and +<a href="{@docRoot}reference/android/support/percent/PercentRelativeLayout.html"> +PercentRelativeLayout</a>. </p> + + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/customtabs} directory. For more information +on how to set up your project, follow the instructions in <a +href="{@docRoot}tools/support-library/setup.html#libs-with-res">Adding libraries +with resources</a>. </p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:percent:23.0.0 +</pre> + + + +<h2 id="recommendation">App Recommendation Support Library for TV</h2> + +<p>The +<a href="{@docRoot}reference/android/support/app/recommendation/package-summary.html">App +Recommendation</a> +package provides APIs to support adding content recommendations in your app running on TV devices. </p> + +<p>The App library adds support for annotations, such as +<a href="{@docRoot}reference/android/support/app/recommendation/ContentRecommendation.ContentMaturity.html"> +ContentRecommendation.ContentMaturity</a> and various classes, such as +<a href="{@docRoot}reference/android/support/app/recommendation/ContentRecommendation.html">ContentRecommendation</a> +and +<a href="{@docRoot}reference/android/support/app/recommendation/RecommendationExtender.html"> +RecommendationExtender</a>. </p> + + +<p>After you download the Android Support Libraries, this library is located in the +{@code <sdk>/extras/android/support/customtabs} directory. For more information +on how to set up your project, follow the instructions in <a +href="{@docRoot}tools/support-library/setup.html#libs-with-res">Adding libraries +with resources</a>. </p> + +<p>The Gradle build script dependency identifier for this library is as follows:</p> + +<pre> +com.android.support:app.recommendation-app:23.0.0 +</pre> diff --git a/docs/html/tools/support-library/index.jd b/docs/html/tools/support-library/index.jd index 9bd9178..9dc0ed1 100644 --- a/docs/html/tools/support-library/index.jd +++ b/docs/html/tools/support-library/index.jd @@ -63,6 +63,36 @@ page.title=Support Library <div class="toggle-content opened"> <p id="rev21"><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" alt="" +/>Android Support Library, revision 23</a> <em>(August 2015)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Added new support libraries:</a></dt> + <dd> + <ul> + <li><a href="features.html#custom-tabs">Custom Tabs Support library</a></li> + <li><a href="features.html#percent">Percent Support library</a></li> + <li><a href="features.html#recommendation">App Recommendation Support library for TV</a></li> + <li><a href="features.html#v7-preference">v7 Preference Support library</a></li> + <li><a href="features.html#v14-preference">v14 Preference Support library</a></li> + <li><a href="features.html#v17-preference">v17 Preference Support library for TV</a></li> + </ul> + </dd> + + </dl> + + <p>For a complete list of the Support Library changes, see the + <a href="{@docRoot}sdk/support_api_diff/23/changes.html">Support + Library API Differences Report</a>. </p> + + </div> +</div> <!-- end of collapsible section --> + + + +<div class="toggle-content closed"> + <p id="rev21"><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt="" />Android Support Library, revision 22.2.1</a> <em>(July 2015)</em> </p> <div class="toggle-content-toggleme"> @@ -95,8 +125,6 @@ page.title=Support Library <a href="{@docRoot}sdk/support_api_diff/22.2.0/changes.html">Support Library API Differences Report</a>. </p> - - </div> </div> <!-- end of collapsible section --> @@ -684,7 +712,7 @@ page.title=Support Library <dt>Added <a href="{@docRoot}tools/support-library/features.html#multidex"> multidex support library</a> to support multiple <a href="https://source.android.com/devices/tech/dalvik/">Dalvik</a> Executable (DEX) files - for multi-dex file support prior to Android 5.0. </li> + for multi-dex file support prior to Android 5.0. </dt> </dl> </div> diff --git a/docs/html/tools/tools_toc.cs b/docs/html/tools/tools_toc.cs index db19d4f..72f9f21 100644 --- a/docs/html/tools/tools_toc.cs +++ b/docs/html/tools/tools_toc.cs @@ -160,6 +160,7 @@ class="en">Tools Help</span></a></div> <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/monitor.html">Device Monitor</a></li> + <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/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/emulator.html">Emulator</a></li> |