diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/html/auto/overview.jd | 4 | ||||
-rw-r--r-- | docs/html/distribute/essentials/quality/wear.jd | 41 | ||||
-rw-r--r-- | docs/html/google/play/billing/billing_testing.jd | 2 | ||||
-rw-r--r-- | docs/html/guide/topics/ui/actionbar.jd | 2 | ||||
-rw-r--r-- | docs/html/sdk/index.jd | 2 | ||||
-rw-r--r-- | docs/html/tools/debugging/debugging-memory.jd | 6 | ||||
-rw-r--r-- | docs/html/tools/devices/managing-avds.jd | 6 | ||||
-rw-r--r-- | docs/html/tools/sdk/tools-notes.jd | 2 | ||||
-rw-r--r-- | docs/html/training/search/index.jd | 2 |
9 files changed, 51 insertions, 16 deletions
diff --git a/docs/html/auto/overview.jd b/docs/html/auto/overview.jd index cf63b98..ae1efec 100644 --- a/docs/html/auto/overview.jd +++ b/docs/html/auto/overview.jd @@ -207,7 +207,7 @@ playback state through callbacks.</li> <p>The Android Auto app uses a car-specific UI model to display content and user interaction opportunities. Android Auto provides you with a standard UI designed to minimize driver -distraction. You do not have to test a custom UI for for driver distraction, which is a +distraction. You do not have to test a custom UI for driver distraction, which is a lengthy and expensive process involving multiple legislations across the globe and different standards for each vehicle OEM.</p> @@ -217,7 +217,7 @@ media apps. You can customize the UI colors, action icons, background images, an <h3 id="launchapp">Launcher</h3> <p>The launcher shows all the compatible media apps installed on the user’s -Android device and lets users select one of them from an scrollable list:</p> +Android device and lets users select one of them from a scrollable list:</p> <div class="auto-img-container-single"> <div class="auto-img-container"> diff --git a/docs/html/distribute/essentials/quality/wear.jd b/docs/html/distribute/essentials/quality/wear.jd index 667e945..4125027 100644 --- a/docs/html/distribute/essentials/quality/wear.jd +++ b/docs/html/distribute/essentials/quality/wear.jd @@ -1,6 +1,6 @@ page.title=Wear App Quality page.tags="wear","wearables","quality","guidelines" -page.metaDescription=Wearables are small factor devices that are built for glanceability and require unique design and functionality. +page.metaDescription=Wearables are smaller devices that are built for glanceability and require unique apps to provide just the right information at the the right time. page.image=/distribute/images/gp-wear-quality.png @jd:body @@ -158,7 +158,7 @@ page.image=/distribute/images/gp-wear-quality.png </tr> <tr> - <td rowspan="1" id="gestures"> + <td rowspan="2" id="gestures"> Gestures </td> @@ -174,6 +174,19 @@ page.image=/distribute/images/gp-wear-quality.png </td> </tr> +<tr> + <td id="WR-GD"> + WR-GD + </td> + <td> + <p style="margin-bottom:.5em;"> + If the app disables the swipe-to-dismiss gesture in a full-screen activity, it responds to the + long-press-to-dismiss gesture in that activity. + (<a href="{@docRoot}training/wearables/ui/exit.html">Learn how</a>) + </p> + </td> +</tr> + </table> @@ -212,16 +225,32 @@ data-sortorder="-timestamp" data-cardsizes="6x2" data-maxresults="6"> </tr> <tr> - <td rowspan="2" id="layout"> + <td rowspan="3" id="layout"> Layout </td> - <td id="WR-LL"> - WR-LL + <td id="WR-LS"> + WR-LS + </td> + <td> + <p style="margin-bottom:.5em;"> + App user interface is formatted appropriately for square displays. App content fits within + the physical display area and no text or controls are cut off by the screen edges. + <br/> + (<a href="{@docRoot}training/wearables/ui/layouts.html">Learn how</a>) + </p> + </td> +</tr> + +<tr> + <td id="WR-LR"> + WR-LR </td> <td> <p style="margin-bottom:.5em;"> - App user interface is formatted appropriately for both square and round displays. + App user interface is formatted appropriately for round displays. App content fits within + the physical display area and no text or controls are cut off by the screen edges. + <br/> (<a href="{@docRoot}training/wearables/ui/layouts.html">Learn how</a>) </p> </td> diff --git a/docs/html/google/play/billing/billing_testing.jd b/docs/html/google/play/billing/billing_testing.jd index 10f5326..36456cc 100644 --- a/docs/html/google/play/billing/billing_testing.jd +++ b/docs/html/google/play/billing/billing_testing.jd @@ -10,7 +10,7 @@ page.tags="inapp, billing, iap" <ol> <li><a href="#testing-purchases">Testing In-app Purchases</a></li> <li><a href="#billing-testing-static">Testing with Static Responses</a></li> - <li><a href="#billing-testing-real">Setting Up for Test Purchases</a></li> + <li><a href="#billing-testing-test">Setting Up for Test Purchases</a></li> <li><a href="#draft_apps">Draft Apps are No Longer Supported</a></li> </ol> <h2>See also</h2> diff --git a/docs/html/guide/topics/ui/actionbar.jd b/docs/html/guide/topics/ui/actionbar.jd index a61696a..d972c47 100644 --- a/docs/html/guide/topics/ui/actionbar.jd +++ b/docs/html/guide/topics/ui/actionbar.jd @@ -1427,7 +1427,7 @@ href="#ActionView">action views</a>.</dd> <p>Here's an example that defines a custom theme for an activity, {@code CustomActivityTheme}, that includes several styles to customize the action bar.</p> -<p>Notice that there are two version for each action bar style property. The first one +<p>Notice that there are two versions for each action bar style property. The first one includes the {@code android:} prefix on the property name to support API levels 11 and higher that include these properties in the framework. The second version does <em>not</em> include the {@code android:} prefix and is for older versions of the platform, on which diff --git a/docs/html/sdk/index.jd b/docs/html/sdk/index.jd index 3d9ef21..a646795 100644 --- a/docs/html/sdk/index.jd +++ b/docs/html/sdk/index.jd @@ -243,7 +243,7 @@ This is the Android Software Development Kit License Agreement <h1 style="margin-top:0">Get the Android SDK</h1> -<p>The Android SDK provides you the API libraries and developer tools necessary to build, test, +<p>The Android SDK provides the API libraries and developer tools necessary to build, test, and debug apps for Android.</p> <p>Download the ADT Bundle to quickly start developing apps. It includes the essential Android diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd index fccb67e..ae67b3c 100644 --- a/docs/html/tools/debugging/debugging-memory.jd +++ b/docs/html/tools/debugging/debugging-memory.jd @@ -243,7 +243,7 @@ here, as some details of the output differ across platform versions.</p> 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) @@ -251,7 +251,7 @@ here, as some details of the output differ across platform versions.</p> Local Binders: 64 Proxy Binders: 34 Death Recipients: 0 OpenSSL Sockets: 1 - + SQL MEMORY_USED: 1739 PAGECACHE_OVERFLOW: 1164 MALLOC_SIZE: 62 @@ -374,7 +374,7 @@ 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 standard tool like jhat or the <a href= "http://www.eclipse.org/mat/downloads.php">Eclipse Memory Analyzer Tool</a> (MAT). 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>/tools/</code> +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> diff --git a/docs/html/tools/devices/managing-avds.jd b/docs/html/tools/devices/managing-avds.jd index 10633d2..d3bbfdc 100644 --- a/docs/html/tools/devices/managing-avds.jd +++ b/docs/html/tools/devices/managing-avds.jd @@ -31,6 +31,12 @@ parent.link=index.html <p>From the main screen, you can create, delete, repair and start AVDs as well as see the details of each AVD. </p> + + <p class="note"><strong>Note:</strong> The emulator system images include experimental +64-bit system images along with standard 32-bit system images. The 64-bit system images +require the Intel x86 Emulator Accelerator (HAXM) Rev.5 which can be downloaded from the +<a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a> <em>Extras</em> folder. + </p> <h2 id="createavd">Creating an AVD</h2> diff --git a/docs/html/tools/sdk/tools-notes.jd b/docs/html/tools/sdk/tools-notes.jd index 20388be..3e3cb4b 100644 --- a/docs/html/tools/sdk/tools-notes.jd +++ b/docs/html/tools/sdk/tools-notes.jd @@ -13,7 +13,7 @@ latest revision of the SDK Tools in the <code><sdk>/tools</code> directory of the SDK Tools, use the <em>Android SDK Manager</em> to get the update, rather than downloading a new SDK starter package. For more information about how to update, see <a -href="{@docRoot}sdk/exploring.html#UpdatingComponents">Exploring the SDK</a>.</p> +href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>.</p> <h2 id="notes">Revisions</h2> diff --git a/docs/html/training/search/index.jd b/docs/html/training/search/index.jd index 612e8e8..66874bb 100644 --- a/docs/html/training/search/index.jd +++ b/docs/html/training/search/index.jd @@ -49,5 +49,5 @@ startpage=true <dt><b><a href="backward-compat.html">Remaining Backward Compatible</a></b></dt> - <dd>Learn how to keep search features backward compatible with older devices by using.</dd> + <dd>Learn how to keep search features backward compatible with older devices.</dd> </dl> |