diff options
Diffstat (limited to 'docs/html/preview')
| -rw-r--r-- | docs/html/preview/api-overview.jd | 8 | ||||
| -rw-r--r-- | docs/html/preview/behavior-changes.jd | 23 | ||||
| -rw-r--r-- | docs/html/preview/download.jd | 4 | ||||
| -rw-r--r-- | docs/html/preview/overview.jd | 10 | ||||
| -rw-r--r-- | docs/html/preview/setup-sdk.jd | 49 | ||||
| -rw-r--r-- | docs/html/preview/testing/guide.jd | 2 |
6 files changed, 60 insertions, 36 deletions
diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index e6c851b..1686d79 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -20,7 +20,7 @@ page.image=images/cards/card-api-overview_16-9_2x.png <li><a href="#authentication">Authentication</a> <ol> <li><a href="#fingerprint-authentication">Fingerprint Authentication</a></li> - <li><a href="#confirm-credentials">Confirm Credentials</a></li> + <li><a href="#confirm-credential">Confirm Credential</a></li> </ol> </li> <li><a href="#direct-share">Direct Share</a></li> @@ -144,7 +144,7 @@ adb -e emu finger touch <finger_id> </li> </ol> -<h3 id="confirm-credentials">Confirm Credentials</h3> +<h3 id="confirm-credential">Confirm Credential</h3> <p>Your app can authenticate users based on how recently they last unlocked their device. This feature frees users from having to remember additional app-specific passwords, and avoids the need for you to implement your own authentication user interface. Your app should use this feature in @@ -164,8 +164,8 @@ method to re-authenticate the user within your app. </p> <p>To see an app implementation of this feature, refer to the -<a href="https://github.com/googlesamples/android-ConfirmCredentials" class="external-link"> - Confirm Credentials sample</a>.</p> +<a href="https://github.com/googlesamples/android-ConfirmCredential" class="external-link"> + Confirm Credential sample</a>.</p> <h2 id="direct-share">Direct Share</h2> diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd index 9b3dbab..5ddac7a 100644 --- a/docs/html/preview/behavior-changes.jd +++ b/docs/html/preview/behavior-changes.jd @@ -50,20 +50,21 @@ some of the key changes that you should understand and account for in your apps. might be affected by these changes in the platform.</p> <h2 id="behavior-runtime-permissions">Runtime Permissions</h1> -<p>This preview introduces a new runtime permissions model, where users can now directly manage -their app permissions at runtime. This model gives users improved visibility and control over +<p>This preview introduces a new permissions model, where users can now directly manage +app permissions at runtime. This model gives users improved visibility and control over permissions, while streamlining the installation and auto-update processes for app developers. -Users can set permissions on or off for all apps running on the M Preview. However, apps that -don’t target the M Preview cannot request permissions at runtime.</p> +Users can grant or revoke permissions individually for installed apps. </p> <p>On your apps that target the M Preview, make sure to check and request for permissions at runtime. To determine if your app has been granted a permission, call the new {@code Context.checkSelfPermission()} method. To request for a permission, call the new -{@code Activity.requestPermission()} method.</p> +{@code Activity.requestPermission()} method. Even if your app is not targeting M, you +should test your app under the new permissions model.</p> -<p>For more information on supporting the new permissions model in your app, see +<p>For details on supporting the new permissions model in your app, see the <a href="{@docRoot}preview/features/runtime-permissions.html"> -Android M Preview Runtime Permissions</a>.</p> +Permissions</a> developer preview page. For tips on how to assess the impact on your app, +see the <a href="{@docRoot}preview/testing/guide.html#runtime-permissions">Testing Guide</a></p> <h2 id="behavior-power">Power-Saving Optimizations</h2> <p>This preview introduces new power-saving optimizations for idle devices and apps.</p> @@ -103,6 +104,10 @@ high-priority messages. If your app receives high-priority GCM messages, it’s brief network access even when the device is in doze. </p> +<p>See the +<a href="{@docRoot}preview/testing/guide.html#doze-standby">Testing Guide</a> for tips on how +to test Doze in your apps. </p> + <h3 id="behavior-app-standby">App standby</h3> <p>With this preview, the system may determine that apps are idle when they are not in active use. Your app is considered idle after a period of time, unless the system detects @@ -140,6 +145,10 @@ designate high-priority messages. If your app receives high-priority GCM message brief network access even when the app is idle. </p> +<p>See the +<a href="{@docRoot}preview/testing/guide.html#doze-standby">Testing Guide</a> for tips on how +to test App Standby in your apps. </p> + <h2 id="behavior-adoptable-storage">Adoptable Storage Devices</h2> <p> With this preview, users can <em>adopt</em> external storage devices such as SD cards. Adopting an diff --git a/docs/html/preview/download.jd b/docs/html/preview/download.jd index 448a23d..6c7c945 100644 --- a/docs/html/preview/download.jd +++ b/docs/html/preview/download.jd @@ -255,8 +255,8 @@ This is the Android SDK Preview License Agreement (the “License Agreement”). <td>Nexus 9 <br>"volantis"</td> <td><a href="#top" onclick="onDownload(this)" >volantis-MPZ44Q-preview-d15ad483.tgz</a><br> - MD5: 8989ce077510a1b814d58dcdb33d160e<br> - SHA-1: d15ad483d0364102984411abda66a4d7b85886c0 + MD5: fae40377fd999d2b09128665c915264d<br> + SHA-1: 7ab05f96093b2cb370b226f65931202714cbc2ca </td> </tr> <tr id="fugu"> diff --git a/docs/html/preview/overview.jd b/docs/html/preview/overview.jd index d6bafb1..36b177d 100644 --- a/docs/html/preview/overview.jd +++ b/docs/html/preview/overview.jd @@ -116,7 +116,7 @@ page.tags="preview", "developer", "android" <img src="{@docRoot}preview/images/m-preview-timeline-crop.png" alt= "Preview program timeline" id="timeline"> <p> - The M Developer Preview runs from May 27 until the final Android M SDK, which + The M Developer Preview runs from May 28 until the final Android M SDK, which we’ll release shortly before the public release during Q3 2015. </p> @@ -326,7 +326,7 @@ page.tags="preview", "developer", "android" </p> <h2 id="get_started"> - How to get started? + How to get started </h2> <p> @@ -336,10 +336,12 @@ page.tags="preview", "developer", "android" <ol> <li>Review the <a href="{@docRoot}preview/api-overview.html">API Overview</a> and <a href="{@docRoot}preview/behavior-changes.html">Behavior Changes</a> to get an - idea of what's new and how it affects your apps. + idea of what's new and how it affects your apps. In particular, learn about + the new <a href="{@docRoot}preview/features/runtime-permissions.html">runtime + permissions</a> model, power-saving features, and auto backup. </li> - <li>Setup for testing and development by following the instructions for + <li>Set up your environment by following the instructions for <a href="{@docRoot}preview/setup-sdk.html">Setting up the Preview SDK</a> and configuring test devices. </li> diff --git a/docs/html/preview/setup-sdk.jd b/docs/html/preview/setup-sdk.jd index 62c3c58..d3327e8 100644 --- a/docs/html/preview/setup-sdk.jd +++ b/docs/html/preview/setup-sdk.jd @@ -24,14 +24,13 @@ App</a> training lesson first.</a></p> <h2 id="get-as13">Get Android Studio 1.3</h2> -<p>The Developer Preview requires Android Studio 1.3, which is in -preview status. You need -to install the preview version of Android Studio 1.3 to work with the Preview -SDK.</p> +<p>The Developer Preview is best used with Android Studio 1.3, which is in +preview status. It is highly recommended that you install the preview version of +Android Studio 1.3 to work with the Preview SDK.</p> <p class="caution"><strong>Caution:</strong> The canary preview of Android Studio 1.3 is still in active development. If you are using your primary development -machine to test the developer preview, you should create a second installation +machine to test the developer preview, you can create a second installation of Android Studio to use for testing.</p> <p>To install the Android Studio 1.3 preview:</p> @@ -41,9 +40,15 @@ of Android Studio to use for testing.</p> Studio</a>. </li> - <li>Open the <strong>Settings</strong> window by choosing <strong>File > - Settings</strong>. Choose the <strong>Appearance & Behavior > System - Settings > Updates</strong> panel.</li> + <li>Open the <strong>Settings</strong> window (on Windows, you can do this + by choosing <strong>File > Settings</strong>). Choose the + <strong>Appearance & Behavior > System + Settings > Updates</strong> panel. + + <p class="aside">On OSX, you can find the <strong>Appearance & + Behavior</strong> panel + in Android Studio's <strong>Preferences</strong> window.</p> + </li> <li> On the <strong>Updates</strong> panel, choose the option <strong>Automatically check updates for: Canary Channel</strong>. @@ -63,18 +68,24 @@ of Android Studio to use for testing.</p> <li>Launch the Android Studio 1.3 preview. </li> - <li>Open the <strong>Settings</strong> window by choosing <strong>File > - Settings</strong>. Choose the <strong>Appearance & Behavior > System - Settings > Updates</strong> panel.</li> + <li>Open the <strong>Settings</strong> window (on Windows, you can do this + by choosing <strong>File > Settings</strong>). Choose the + <strong>Appearance & Behavior > System + Settings > Updates</strong> panel. + + <p class="aside">On OSX, you can find the <strong>Appearance & + Behavior</strong> panel + in Android Studio's <strong>Preferences</strong> window.</p> + </li> <li>On the <strong>Updates</strong> panel, choose the options <strong>Automatically check updates for: Canary Channel</strong> and <strong>Automatically check updates for Android SDK: Preview Channel</strong>. </li> - <li>Click the <strong>Android SDK Manager</strong> button to launch the SDK - Manager. (With Android Studio 1.3, the SDK Manager is integrated into Android - Studio instead of being a standalone application.) + <li>Launch the <strong>Android SDK Manager</strong>. (With Android Studio 1.3, + the SDK Manager is integrated into Android Studio instead of being a + standalone application.) </li> <li>Under the <strong>Platforms</strong> section, select <strong>Android MNC @@ -124,7 +135,8 @@ of Android Studio to use for testing.</p> <ul> <li>Check <strong>Phone and Tablet</strong>.</li> - <li>Select <strong>API 22+: Android M (Preview)</strong> in <strong>Minimum SDK</strong>.</li> + <li>Select <strong>MNC: Android M (Preview)</strong> in <strong>Minimum + SDK</strong>.</li> </ul> @@ -151,7 +163,7 @@ of Android Studio to use for testing.</p> platform for testing. Otherwise, you can configure a virtual device for testing. </p> -<h3 id="setup-device">Set up a Physical Device</h3> +<h3 id="setup-device">Set up a physical device</h3> <p> If you have a Nexus 5, Nexus 6, Nexus 9, or Android TV, you can install a preview @@ -165,7 +177,7 @@ of Android Studio to use for testing.</p> it</em>, so you should backup any data before installing a preview image. </p> -<h3 id="setupAVD">Set up a Virtual Device</h3> +<h3 id="setupAVD">Set up a virtual device</h3> <p> You can set up virtual device with the preview version of the platform from within Android Studio @@ -182,9 +194,10 @@ of Android Studio to use for testing.</p> <a href="{@docRoot}tools/devices/managing-avds.html">Managing AVDs with AVD Manager</a>. Use the following settings: <ul> - <li><strong>Device:</strong> Nexus 5, Nexus 6, Nexus 9, or Nexus Player</li> + <li><strong>Device:</strong> Nexus 5, Nexus 6, Nexus 9, or Android TV</li> <li><strong>Target:</strong> Android M (Preview) - API Level M</li> + <li><strong>ABI:</strong> x86</li> </ul> </li> </ol> diff --git a/docs/html/preview/testing/guide.jd b/docs/html/preview/testing/guide.jd index 07a25a2..56bb4d9 100644 --- a/docs/html/preview/testing/guide.jd +++ b/docs/html/preview/testing/guide.jd @@ -57,7 +57,7 @@ page.keywords=previewresources,androidm,testing,permissions app features from working, or they may work in a degraded state. </p> -<p> +<p class="caution"> This change affects all apps running on the new platform, even those not targeting the new platform version. The platform provides a limited compatibility behavior for legacy apps, but you should begin planning your app’s migration to the new permissions model now, with a goal of |