Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add preview docs dir, toc, and basic files.

Browse Source 
Change-Id: I890dd21fed1217e4429f269eed5bada9a6faf2b4
This commit is contained in:
Dirk Dougherty
2016-02-06 18:24:32 -08:00
parent 01fb150153
commit 5748bc4a1b
14 changed files with 3082 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Android.mk
View File

@@ -1042,6 +1042,7 @@ LOCAL_DROIDDOC_OPTIONS:= \
-hdf android.whichdoc online \
$(sample_groups) \
-useUpdatedTemplates \
-includePreview \
-hdf android.hasSamples true \
-samplesdir $(samples_dir)

569
docs/html/preview/api-overview.jd Normal file
View File

@@ -0,0 +1,569 @@
page.title=API Overview
page.keywords=preview,sdk,compatibility
page.tags=previewresources, androidm
sdk.platform.apiLevel=22-mnc
page.image=images/cards/card-api-overview_16-9_2x.png
@jd:body
<div id="qv-wrapper">
<div id="qv">
<h2>In this document
<a href="#" onclick="hideNestedItems('#toc44',this);return false;" class="header-toggle">
<span class="more">show more</span>
<span class="less" style="display:none">show less</span></a></h2>
<ol id="toc44" class="hide-nested">
<li><a href="#app-linking">App Linking</a></li>
<li><a href="#backup">Auto Backup for Apps</a></li>
<li><a href="#authentication">Authentication</a>
<ol>
<li><a href="#fingerprint-authentication">Fingerprint Authentication</a></li>
<li><a href="#confirm-credential">Confirm Credential</a></li>
</ol>
</li>
<li><a href="#direct-share">Direct Share</a></li>
<li><a href="#voice-interactions">Voice Interactions</a></li>
<li><a href="#assist">Assist API</a></li>
<li><a href="#notifications">Notifications</a></li>
<li><a href="#bluetooth-stylus">Bluetooth Stylus Support</a></li>
<li><a href="#ble-scanning">Improved Bluetooth Low Energy Scanning</a></li>
<li><a href="#hotspot">Hotspot 2.0 Release 1 Support</a></li>
<li><a href="#4K-display">4K Display Mode</a></li>
<li><a href="#behavior-themeable-colorstatelists">Themeable ColorStateLists</a></li>
<li><a href="#audio">Audio Features</a></li>
<li><a href="#video">Video Features</a></li>
<li><a href="#camera">Camera Features</a>
<ol>
<li><a href="#flashlight">Flashlight API</a></li>
<li><a href="#reprocessing">Camera Reprocessing</a></li>
</ol>
</li>
<li><a href="#afw">Android for Work Features</a></li>
</ol>
<h2>API Differences</h2>
<ol>
<li><a href="{@docRoot}sdk/api_diff/23/changes.html">API level 22 to 23 (Preview 3) &raquo;</a> </li>
</ol>
</div>
</div>
<p>The M Developer Preview gives you an advance look at the upcoming release
for the Android platform, which offers new features for users and app
developers. This document provides an introduction to the most notable APIs.</p>
<p>
The M Developer Preview 3 release includes the <strong>final APIs for Android 6.0 (API level
23)</strong>. If you are preparing an app for use on Android 6.0,
<a href="{@docRoot}preview/setup-sdk.html">download the latest SDK</a> and to complete your
final updates and release testing. You can review the final APIs in the
<a href="{@docRoot}reference/packages.html">API Reference</a> and see the API differences in
the <a href="{@docRoot}sdk/api_diff/23/changes.html">Android API Differences Report</a>.
</p>
</p>
<p class="caution"><strong>Important:</strong>
You may now publish apps that target Android 6.0 (API level 23) to the Google Play store.
</p>
<p class="note"><strong>Note:</strong>
If you have been working with previous preview releases and want to see the differences
between the final API and previous preview versions, download the additional difference
reports included in the <a href="{@docRoot}preview/download.html#docs">preview docs
reference</a>.
</p>
<h3>Important behavior changes</h3>
<p>If you have previously published an app for Android, be aware that your app might be affected
by changes in the platform.</p>
<p>Please see <a href="behavior-changes.html">Behavior Changes</a> for complete information.</p>
<h2 id="app-linking">App Linking</h2>
<p>This preview enhances Android’s intent system by providing more powerful app linking.
This feature allows you to associate an app with a web domain you own. Based on this
association, the platform can determine the default app to use to handle a particular
web link and skip prompting users to select an app. To learn how to implement this feature, see
<a href="{@docRoot}preview/features/app-linking.html">App Linking</a>.
<h2 id="backup">Auto Backup for Apps</h2>
<p>The system now performs automatic full data backup and restore for apps. For the
duration of the <a href="{@docRoot}preview/overview.html">M Developer Preview program</a>, all
apps are backed up, independent of which SDK version they target. After the final M SDK release,
your app must target M to enable this behavior; you do not need to add any additional code. If users
delete their Google accounts, their backup data is deleted as well. To learn how this feature
works and how to configure what to back up on the file system, see
<a href="{@docRoot}preview/backup/index.html">Auto Backup for Apps</a>.</p>
<h2 id="authentication">Authentication</h2>
<p>This preview offers new APIs to let you authenticate users by using their fingerprint scans on
supported devices, and check how recently the user was last authenticated using a device unlocking
mechanism (such as a lockscreen password). Use these APIs in conjunction with
the <a href="{@docRoot}training/articles/keystore.html">Android Keystore system</a>.</p>
<h3 id="fingerprint-authentication">Fingerprint Authentication</h3>
<p>To authenticate users via fingerprint scan, get an instance of the new
{@link android.hardware.fingerprint.FingerprintManager} class and call the
{@link android.hardware.fingerprint.FingerprintManager#authenticate(android.hardware.fingerprint.FingerprintManager.CryptoObject, android.os.CancellationSignal, int, android.hardware.fingerprint.FingerprintManager.AuthenticationCallback, android.os.Handler) authenticate()}
method. Your app must be running on a compatible
device with a fingerprint sensor. You must implement the user interface for the fingerprint
authentication flow on your app, and use the standard Android fingerprint icon in your UI.
The Android fingerprint icon ({@code c_fp_40px.png}) is included in the
<a href="https://github.com/googlesamples/android-FingerprintDialog"
class="external-link">sample app</a>. If you are developing multiple apps that use fingerprint
authentication, note that each app must authenticate the user’s fingerprint independently.
</p>
<p>To use this feature in your app, first add the
{@link android.Manifest.permission#USE_FINGERPRINT} permission in your manifest.</p>
<pre>
&lt;uses-permission
android:name="android.permission.USE_FINGERPRINT" /&gt;
</pre>
<img src="{@docRoot}preview/images/fingerprint-screen.png"
srcset="{@docRoot}preview/images/fingerprint-screen.png 1x, {@docRoot}preview/images/fingerprint-screen_2x.png 2x"
style="float:right; margin:0 0 10px 20px" width="282" height="476" />
<p>To see an app implementation of fingerprint authentication, refer to the
<a href="https://github.com/googlesamples/android-FingerprintDialog" class="external-link">
Fingerprint Dialog sample</a>. For a demonstration of how you can use these authentication
APIs in conjunction with other Android APIs, see the video
<a class="video-shadowbox-button" href="https://www.youtube.com/watch?v=VOn7VrTRlA4">
Fingerprint and Payment APIs</a>.</p>
<p>If you are testing this feature, follow these steps:</p>
<ol>
<li>Install Android SDK Tools Revision 24.3, if you have not done so.</li>
<li>Enroll a new fingerprint in the emulator by going to
<strong>Settings > Security > Fingerprint</strong>, then follow the enrollment instructions.</li>
<li>Use an emulator to emulate fingerprint touch events with the
following command. Use the same command to emulate fingerprint touch events on the lockscreen or
in your app.
<pre class="no-prettyprint">
adb -e emu finger touch &lt;finger_id&gt;
</pre>
<p>On Windows, you may have to run {@code telnet 127.0.0.1 <emulator-id>} followed by
{@code finger touch <finger_id>}.
</p>
</li>
</ol>
<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
conjunction with a public or secret key implementation for user authentication.</p>
<p>To set the timeout duration for which the same key can be re-used after a user is successfully
authenticated, call the new
{@link android.security.keystore.KeyGenParameterSpec.Builder#setUserAuthenticationValidityDurationSeconds(int) setUserAuthenticationValidityDurationSeconds()}
method when you set up a {@link javax.crypto.KeyGenerator} or
{@link java.security.KeyPairGenerator}.</p>
<p>Avoid showing the re-authentication dialog excessively -- your apps should try using the
cryptographic object first and if the the timeout expires, use the
{@link android.app.KeyguardManager#createConfirmDeviceCredentialIntent(java.lang.CharSequence, java.lang.CharSequence) createConfirmDeviceCredentialIntent()}
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-ConfirmCredential" class="external-link">
Confirm Credential sample</a>.</p>
<h2 id="direct-share">Direct Share</h2>
<img src="{@docRoot}preview/images/direct-share-screen.png"
srcset="{@docRoot}preview/images/direct-share-screen.png 1x, {@docRoot}preview/images/direct-share-screen_2x.png 2x"
style="float:right; margin:0 0 20px 30px" width="312" height="329" />
<p>This preview provides you with APIs to make sharing intuitive and quick for users. You can now
define <em>direct share targets</em> that launch a specific activity in your app. These direct share
targets are exposed to users via the <em>Share</em> menu. This feature allows users to share
content to targets, such as contacts, within other apps. For example, the direct share target might
launch an activity in another social network app, which lets the user share content directly to a
specific friend or community in that app.</p>
<p>To enable direct share targets you must define a class that extends the
{@link android.service.chooser.ChooserTargetService} class. Declare your
service in the manifest. Within that declaration, specify the
{@link android.Manifest.permission#BIND_CHOOSER_TARGET_SERVICE} permission and an
intent filter using the
{@link android.service.chooser.ChooserTargetService#SERVICE_INTERFACE SERVICE_INTERFACE} action.</p>
<p>The following example shows how you might declare the
{@link android.service.chooser.ChooserTargetService} in your manifest.</p>
<pre>
&lt;service android:name=".ChooserTargetService"
android:label="&#64;string/service_name"
android:permission="android.permission.BIND_CHOOSER_TARGET_SERVICE"&gt;
&lt;intent-filter&gt;
&lt;action android:name="android.service.chooser.ChooserTargetService" /&gt;
&lt;/intent-filter&gt;
&lt;/service&gt;
</pre>
<p>For each activity that you want to expose to
{@link android.service.chooser.ChooserTargetService}, add a
{@code <meta-data>} element with the name
{@code "android.service.chooser.chooser_target_service"} in your app manifest.
</p>
<pre>
&lt;activity android:name=".MyShareActivity”
android:label="&#64;string/share_activity_label"&gt;
&lt;intent-filter>
&lt;action android:name="android.intent.action.SEND" /&gt;
&lt;/intent-filter>
&lt;meta-data
android:name="android.service.chooser.chooser_target_service"
android:value=".ChooserTargetService" /&gt;
&lt;/activity>
</pre>
<h2 id="voice-interactions">Voice Interactions</h2>
<p>
This preview provides a new voice interaction API which, together with
<a href="https://developers.google.com/voice-actions/" class="external-link">Voice Actions</a>,
allows you to build conversational voice experiences into your apps. Call the
{@link android.app.Activity#isVoiceInteraction()} method to determine if a voice action triggered
your activity. If so, your app can use the
{@link android.app.VoiceInteractor} class to request a voice confirmation from the user, select
from a list of options, and more.</p>
<p>Most voice interactions originate from a user voice action. A voice interaction activity can
also, however, start without user input. For example, another app launched through a voice
interaction can also send an intent to launch a voice interaction. To determine if your activity
launched from a user voice query or from another voice interaction app, call the
{@link android.app.Activity#isVoiceInteractionRoot()} method. If another app launched your
activity, the method returns {@code false}. Your app may then prompt the user to confirm that
they intended this action.</p>
<p>To learn more about implementing voice actions, see the
<a href="https://developers.google.com/voice-actions/interaction/"
class="external-link">Voice Actions developer site</a>.
</p>
<h2 id="assist">Assist API</h2>
<p>
This preview offers a new way for users to engage with your apps through an assistant. To use this
feature, the user must enable the assistant to use the current context. Once enabled, the user
can summon the assistant within any app, by long-pressing on the <strong>Home</strong> button.</p>
<p>Your app can elect to not share the current context with the assistant by setting the
{@link android.view.WindowManager.LayoutParams#FLAG_SECURE} flag. In addition to the
standard set of information that the platform passes to the assistant, your app can share
additional information by using the new {@link android.app.assist.AssistContent} class.</p>
<p>To provide the assistant with additional context from your app, follow these steps:</p>
<ol>
<li>Implement the {@link android.app.Application.OnProvideAssistDataListener} interface.</li>
<li>Register this listener by using
{@link android.app.Application#registerOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener) registerOnProvideAssistDataListener()}.</li>
<li>In order to provide activity-specific contextual information, override the
{@link android.app.Activity#onProvideAssistData(android.os.Bundle) onProvideAssistData()}
callback and, optionally, the new
{@link android.app.Activity#onProvideAssistContent(android.app.assist.AssistContent) onProvideAssistContent()}
callback.
</ol>
<h2 id="notifications">Notifications</h2>
<p>This preview adds the following API changes for notifications:</p>
<ul>
<li>New {@link android.app.NotificationManager#INTERRUPTION_FILTER_ALARMS} filter level that
corresponds to the new <em>Alarms only</em> do not disturb mode.</li>
<li>New {@link android.app.Notification#CATEGORY_REMINDER} category value that is used to
distinguish user-scheduled reminders from other events
({@link android.app.Notification#CATEGORY_EVENT}) and alarms
({@link android.app.Notification#CATEGORY_ALARM}).</li>
<li>New {@link android.graphics.drawable.Icon} class that you can attach to your notifications
via the
{@link android.app.Notification.Builder#setSmallIcon(android.graphics.drawable.Icon) setSmallIcon()}
and {@link android.app.Notification.Builder#setLargeIcon(android.graphics.drawable.Icon) setLargeIcon()}
methods. Similarly, the
{@link android.app.Notification.Builder#addAction(int, java.lang.CharSequence, android.app.PendingIntent)
addAction()} method now accepts an {@link android.graphics.drawable.Icon} object instead of a
drawable resource ID.</li>
<li>New {@link android.app.NotificationManager#getActiveNotifications()} method that allows your
apps to find out which of their notifications are currently alive. To see an app implementation
that uses this feature, see the <a href="https://github.com/googlesamples/android-ActiveNotifications"
class="external-link">Active Notifications sample</a>.</li>
</ul>
<h2 id="bluetooth-stylus">Bluetooth Stylus Support</h2>
<p>This preview provides improved support for user input using a Bluetooth stylus. Users can pair
and connect a compatible Bluetooth stylus with their phone or tablet. While connected, position
information from the touch screen is fused with pressure and button information from the stylus to
provide a greater range of expression than with the touch screen alone. Your app can listen for
stylus button presses and perform secondary actions, by registering
{@link android.view.View.OnContextClickListener} and
{@link android.view.GestureDetector.OnContextClickListener} objects in your activity.</p>
<p>Use the {@link android.view.MotionEvent} methods and constants to detect stylus button
interactions:</p>
<ul>
<li>If the user touches a stylus with a button on the screen of your app, the
{@link android.view.MotionEvent#getToolType(int) getTooltype()} method returns
{@link android.view.MotionEvent#TOOL_TYPE_STYLUS}.</li>
<li>For apps targeting M Preview, the
{@link android.view.MotionEvent#getButtonState() getButtonState()}
method returns {@link android.view.MotionEvent#BUTTON_STYLUS_PRIMARY} when the user
presses the primary stylus button. If the stylus has a second button, the same method returns
{@link android.view.MotionEvent#BUTTON_STYLUS_SECONDARY} when the user presses it. If the user presses
both buttons simultaneously, the method returns both values OR'ed together
({@link android.view.MotionEvent#BUTTON_STYLUS_PRIMARY}|{@link android.view.MotionEvent#BUTTON_STYLUS_SECONDARY}).</li>
<li>
For apps targeting a lower platform version, the
{@link android.view.MotionEvent#getButtonState() getButtonState()} method returns
{@link android.view.MotionEvent#BUTTON_SECONDARY} (for primary stylus button press),
{@link android.view.MotionEvent#BUTTON_TERTIARY} (for secondary stylus button press), or both.
</li>
</ul>
<h2 id="ble-scanning">Improved Bluetooth Low Energy Scanning</h2>
<p>
If your app performs performs Bluetooth Low Energy scans, use the new
{@link android.bluetooth.le.ScanSettings.Builder#setCallbackType(int) setCallbackType()}
method to specify that you want the system to notify callbacks when it first finds, or sees after a
long time, an advertisement packet matching the set {@link android.bluetooth.le.ScanFilter}. This
approach to scanning is more power-efficient than what’s provided in the previous platform version.
</p>
<h2 id="hotspot">Hotspot 2.0 Release 1 Support</h2>
<p>
This preview adds support for the Hotspot 2.0 Release 1 spec on Nexus 6 and Nexus 9 devices. To
provision Hotspot 2.0 credentials in your app, use the new methods of the
{@link android.net.wifi.WifiEnterpriseConfig} class, such as
{@link android.net.wifi.WifiEnterpriseConfig#setPlmn(java.lang.String) setPlmn()} and
{@link android.net.wifi.WifiEnterpriseConfig#setRealm(java.lang.String) setRealm()}. In the
{@link android.net.wifi.WifiConfiguration} object, you can set the
{@link android.net.wifi.WifiConfiguration#FQDN} and the
{@link android.net.wifi.WifiConfiguration#providerFriendlyName} fields.
The new {@link android.net.wifi.ScanResult#isPasspointNetwork()} method indicates if a detected
network represents a Hotspot 2.0 access point.
</p>
<h2 id="4K-display">4K Display Mode</h2>
<p>The platform now allows apps to request that the display resolution be upgraded to 4K rendering
on compatible hardware. To query the current physical resolution, use the new
{@link android.view.Display.Mode} APIs. If the UI is drawn at a lower logical resolution and is
upscaled to a larger physical resolution, be aware that the physical resolution the
{@link android.view.Display.Mode#getPhysicalWidth()} method returns may differ from the logical
resolution reported by {@link android.view.Display#getSize(android.graphics.Point) getSize()}.</p>
<p>You can request the system to change the physical resolution in your app as it runs, by setting
the {@link android.view.WindowManager.LayoutParams#preferredDisplayModeId} property of your app’s
window. This feature is useful if you want to switch to 4K display resolution. While in 4K display
mode, the UI continues to be rendered at the original resolution (such as 1080p) and is upscaled to
4K, but {@link android.view.SurfaceView} objects may show content at the native resolution.</p>
<h2 id="behavior-themeable-colorstatelists">Themeable ColorStateLists</h2>
<p>Theme attributes are now supported in
{@link android.content.res.ColorStateList} for devices running the M Preview. The
{@link android.content.res.Resources#getColorStateList(int) getColorStateList()} and
{@link android.content.res.Resources#getColor(int) getColor()} methods have been deprecated. If
you are calling these APIs, call the new
{@link android.content.Context#getColorStateList(int) getColorStateList()} or
{@link android.content.Context#getColor(int) getColor()} methods instead. These methods are also
available in the v4 appcompat library via {@link android.support.v4.content.ContextCompat}.</p>
<h2 id="audio">Audio Features</h2>
<p>This preview adds enhancements to audio processing on Android, including: </p>
<ul>
<li>Support for the <a href="http://en.wikipedia.org/wiki/MIDI" class="external-link">MIDI</a>
protocol, with the new {@link android.media.midi} APIs. Use these APIs to send and receive MIDI
events.</li>
<li>New {@link android.media.AudioRecord.Builder} and {@link android.media.AudioTrack.Builder}
classes to create digital audio capture and playback objects respectively, and configure audio
source and sink properties to override the system defaults.</li>
<li>API hooks for associating audio and input devices. This is particularly useful if your app
allows users to start a voice search from a game controller or remote control connected to Android
TV. The system invokes the new
{@link android.app.Activity#onSearchRequested(android.view.SearchEvent) onSearchRequested()}
callback when the user starts a search. To determine if the user's input device has a built-in
microphone, retrieve the {@link android.view.InputDevice} object from that callback, then call the
new {@link android.view.InputDevice#hasMicrophone()} method.</li>
<li>New {@link android.media.AudioManager#getDevices(int) getDevices()} method which lets you
retrieve a list of all audio devices currently connected to the system. You can also register an
{@link android.media.AudioDeviceCallback} object if you want the system to notify your app
when an audio device connects or disconnects.</li>
</ul>
<h2 id="video">Video Features</h2>
<p>This preview adds new capabilities to the video processing APIs, including:</p>
<ul>
<li>New {@link android.media.MediaSync} class which helps applications to synchronously render
audio and video streams. The audio buffers are submitted in non-blocking fashion and are
returned via a callback. It also supports dynamic playback rate.
</li>
<li>New {@link android.media.MediaDrm#EVENT_SESSION_RECLAIMED} event, which indicates that a
session opened by the app has been reclaimed by the resource manager. If your app uses DRM sessions,
you should handle this event and make sure not to use a reclaimed session.
</li>
<li>New {@link android.media.MediaCodec.CodecException#ERROR_RECLAIMED} error code, which indicates
that the resource manager reclaimed the media resource used by the codec. With this exception, the
codec must be released, as it has moved to terminal state.
</li>
<li>New {@link android.media.MediaCodecInfo.CodecCapabilities#getMaxSupportedInstances()
getMaxSupportedInstances()} interface to get a hint for the max number of the supported
concurrent codec instances.
</li>
<li>New {@link android.media.MediaPlayer#setPlaybackParams(android.media.PlaybackParams)
setPlaybackParams()} method to set the media playback rate for fast or
slow motion playback. It also stretches or speeds up the audio playback automatically in
conjunction with the video.</li>
</ul>
<h2 id="camera">Camera Features</h2>
<p>This preview includes the following new APIs for accessing the camera’s flashlight and for
camera reprocessing of images:</p>
<h3 id="flashlight">Flashlight API</h3>
<p>If a camera device has a flash unit, you can call the
{@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()}
method to switch the flash unit’s torch mode on or off without opening the camera device. The app
does not have exclusive ownership of the flash unit or the camera device. The torch mode is turned
off and becomes unavailable whenever the camera device becomes unavailable, or when other camera
resources keeping the torch on become unavailable. Other apps can also call
{@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()}
to turn off the torch mode. When the last app that turned on the torch mode is closed, the torch
mode is turned off.</p>
<p>You can register a callback to be notified about torch mode status by calling the
{@link android.hardware.camera2.CameraManager#registerTorchCallback(android.hardware.camera2.CameraManager.TorchCallback, android.os.Handler) registerTorchCallback()}
method. The first time the callback is registered, it is immediately called with the torch mode
status of all currently known camera devices with a flash unit. If the torch mode is turned on or
off successfully, the
{@link android.hardware.camera2.CameraManager.TorchCallback#onTorchModeChanged(java.lang.String, boolean) onTorchModeChanged()}
method is invoked.</p>
<h3 id="reprocessing">Reprocessing API</h3>
<p>The {@link android.hardware.camera2 Camera2} API is extended to support YUV and private
opaque format image reprocessing. To determine if these reprocessing capabilities are available,
call {@link android.hardware.camera2.CameraManager#getCameraCharacteristics(java.lang.String)
getCameraCharacteristics()} and check for the
{@link android.hardware.camera2.CameraCharacteristics#REPROCESS_MAX_CAPTURE_STALL} key. If a
device supports reprocessing, you can create a reprocessable camera capture session by calling
<a href="/reference/android/hardware/camera2/CameraDevice.html#createReprocessableCaptureSession(android.hardware.camera2.params.InputConfiguration, java.util.List<android.view.Surface>, android.hardware.camera2.CameraCaptureSession.StateCallback, android.os.Handler)"><code>createReprocessableCaptureSession()</code></a>,
and create requests for input buffer reprocessing.</p>
<p>Use the {@link android.media.ImageWriter} class to connect the input buffer flow to the camera
reprocessing input. To get an empty buffer, follow this programming model:</p>
<ol>
<li>Call the {@link android.media.ImageWriter#dequeueInputImage()} method.</li>
<li>Fill the data into the input buffer.</li>
<li>Send the buffer to the camera by calling the
{@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method.</li>
</ol>
<p>If you are using a {@link android.media.ImageWriter} object together with an
{@link android.graphics.ImageFormat#PRIVATE} image, your app cannot access the image
data directly. Instead, pass the {@link android.graphics.ImageFormat#PRIVATE} image directly to the
{@link android.media.ImageWriter} by calling the
{@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method
without any buffer copy.</p>
<p>The {@link android.media.ImageReader} class now supports
{@link android.graphics.ImageFormat#PRIVATE} format image streams. This support allows your app to
maintain a circular image queue of {@link android.media.ImageReader} output images, select one or
more images, and send them to the {@link android.media.ImageWriter} for camera reprocessing.</p>
<h2 id="afw">Android for Work Features</h2>
<p>This preview includes the following new APIs for Android for Work:</p>
<ul>
<li><strong>Enhanced controls for Corporate-Owned, Single-Use devices:</strong> The Device Owner
can now control the following settings to improve management of
Corporate-Owned, Single-Use (COSU) devices:
<ul>
<li>Disable or re-enable the keyguard with the
{@link android.app.admin.DevicePolicyManager#setKeyguardDisabled(android.content.ComponentName, boolean)
setKeyguardDisabled()} method.</li>
<li>Disable or re-enable the status bar (including quick settings, notifications, and the
navigation swipe-up gesture that launches Google Now) with the
{@link android.app.admin.DevicePolicyManager#setStatusBarDisabled(android.content.ComponentName, boolean) setStatusBarDisabled()}
method.</li>
<li>Disable or re-enable safe boot with the {@link android.os.UserManager} constant
{@link android.os.UserManager#DISALLOW_SAFE_BOOT}.</li>
<li>Prevent the screen from turning off while plugged in with the
{@link android.provider.Settings.Global#STAY_ON_WHILE_PLUGGED_IN} constant.</li>
</ul>
</li>
<li><strong>Silent install and uninstall of apps by Device Owner:</strong> A Device Owner can now
silently install and uninstall applications using the {@link android.content.pm.PackageInstaller}
APIs, independent of Google Play for Work. You can now provision devices through a Device Owner that
fetches and installs apps without user interaction. This feature is useful for enabling one-touch
provisioning of kiosks or other such devices without activating a Google account.</li>
<li><strong>Silent enterprise certificate access: </strong> When an app calls
{@link android.security.KeyChain#choosePrivateKeyAlias(android.app.Activity,android.security.KeyChainAliasCallback,java.lang.String[],java.security.Principal[],java.lang.String,int,java.lang.String) choosePrivateKeyAlias()},
prior to the user being prompted to select a certificate, the Profile or Device Owner can now call
the {@link android.app.admin.DeviceAdminReceiver#onChoosePrivateKeyAlias(android.content.Context, android.content.Intent, int, android.net.Uri, java.lang.String) onChoosePrivateKeyAlias()}
method to provide the alias silently to the requesting application. This feature lets you grant
managed apps access to certificates without user interaction.</li>
<li><strong>Auto-acceptance of system updates.</strong> By setting a system update policy with
{@link android.app.admin.DevicePolicyManager#setSystemUpdatePolicy(android.content.ComponentName, android.app.admin.SystemUpdatePolicy) setSystemUpdatePolicy()},
a Device Owner can now auto-accept a system
update, for instance in the case of a kiosk device, or postpone the update and prevent it being
taken by the user for up to 30 days. Furthermore, an administrator can set a daily time window in
which an update must be taken, for example during the hours when a kiosk device is not in use. When
a system update is available, the system checks if the Work Policy Controller app has set a system
update policy, and behaves accordingly.
</li>
<li>
<strong>Delegated certificate installation:</strong> A Profile or Device Owner can now grant a
third-party app the ability to call these {@link android.app.admin.DevicePolicyManager} certificate
management APIs:
<ul>
<li>{@link android.app.admin.DevicePolicyManager#getInstalledCaCerts(android.content.ComponentName)
getInstalledCaCerts()}</li>
<li>{@link android.app.admin.DevicePolicyManager#hasCaCertInstalled(android.content.ComponentName,byte[])
hasCaCertInstalled()}</li>
<li>{@link android.app.admin.DevicePolicyManager#installCaCert(android.content.ComponentName,byte[])
installCaCert()}</li>
<li>{@link android.app.admin.DevicePolicyManager#uninstallCaCert(android.content.ComponentName,byte[])
uninstallCaCert()}</li>
<li>{@link android.app.admin.DevicePolicyManager#uninstallAllUserCaCerts(android.content.ComponentName)
uninstallAllUserCaCerts()}</li>
<li>{@link android.app.admin.DevicePolicyManager#installKeyPair(android.content.ComponentName,java.security.PrivateKey,java.security.cert.Certificate,java.lang.String)
installKeyPair()}</li>
</ul>
</li>
<img src="{@docRoot}preview/images/work-profile-screen.png"
srcset="{@docRoot}preview/images/work-profile-screen.png 1x, {@docRoot}preview/images/work-profile-screen_2x.png 2x"
style="float:right; margin:0 0 10px 20px" width="282" height="476" />
<li><strong>Data usage tracking.</strong> A Profile or Device Owner can now query for the
data usage statistics visible in <strong>Settings > Data</strong> usage by using the new
{@link android.app.usage.NetworkStatsManager} methods. Profile Owners are automatically granted
permission to query data on the profile they manage, while Device Owners get access to usage data
of the managed primary user.</li>
<li><strong>Runtime permission management:</strong>
<p>A Profile or Device Owner can set a permission policy
for all runtime requests of all applications using
{@link android.app.admin.DevicePolicyManager#setPermissionPolicy(android.content.ComponentName, int)
setPermissionPolicy()}, to either prompt the user to grant the permission or automatically grant or
deny the permission silently. If the latter policy is set, the user cannot
modify the selection made by the Profile or Device Owner within the app’s permissions screen in
<strong>Settings</strong>.</p></li>
<li><strong>VPN in Settings:</strong> VPN apps are now visible in
<strong>Settings > More > VPN</strong>.
Additionally, the notifications that accompany VPN usage are now specific to how that VPN is
configured. For Profile Owner, the notifications are specific to whether the VPN is configured
for a managed profile, a personal profile, or both. For a Device Owner, the notifications are
specific to whether the VPN is configured for the entire device.</li>
<li><strong>Work status notification:</strong> A status bar briefcase icon now appears whenever
an app from the managed profile has an activity in the foreground. Furthermore, if the device is
unlocked directly to the activity of an app in the managed profile, a toast is displayed notifying
the user that they are within the work profile.
</li>
</ul>
<p class="note">
For a detailed view of all API changes in the M Developer Preview, see the <a href=
"{@docRoot}preview/download.html">API Differences Report</a>.
</p>

442
docs/html/preview/behavior-changes.jd Normal file
View File

@@ -0,0 +1,442 @@
page.title=Behavior Changes
page.keywords=preview,sdk,compatibility
sdk.platform.apiLevel=MNC
@jd:body
<div id="qv-wrapper">
<div id="qv">
<h2>In this document</h2>
<ol id="toc44" class="hide-nested">
<li><a href="#behavior-runtime-permissions">Runtime Permissions</a></li>
<li><a href="#behavior-power">Power-Saving Optimizations</a></li>
<li><a href="#behavior-adoptable-storage">Adoptable Storage Devices</a></li>
<li><a href="#behavior-apache-http-client">Apache HTTP Client Removal</a></li>
<li><a href="#behavior-audiomanager-Changes">AudioManager Changes</a></li>
<li><a href="#behavior-notifications">Notifications</a></li>
<li><a href="#behavior-test-selection">Text Selection</a></li>
<li><a href="#behavior-keystore">Android Keystore Changes</a></li>
<li><a href="#behavior-network">Wi-Fi and Networking Changes</a></li>
<li><a href="#behavior-camera">Camera Service Changes</a></li>
<li><a href="#behavior-runtime">Runtime</a></li>
<li><a href="#behavior-hardware-id">Access to Hardware Identifier</a></li>
<li><a href="#behavior-apk-validation">APK Validation</a></li>
<li><a href="#behavior-usb">USB Connection</a></li>
<li><a href="#behavior-afw">Android for Work Changes</a></li>
</ol>
<h2>API Differences</h2>
<ol>
<li><a href="{@docRoot}preview/download.html">API level 22 to M Preview &raquo;</a> </li>
</ol>
<h2>See Also</h2>
<ol>
<li><a href="{@docRoot}preview/api-overview.html">M Developer Preview API Overview</a> </li>
</ol>
</div>
</div>
<p>Along with new features and capabilities, the M Developer Preview includes a variety of
system changes and API behavior changes. This document highlights
some of the key changes that you should understand and account for in your apps.</p>
<p>If you have previously published an app for Android, be aware that these changes in the
platform affect your app.</p>
<h2 id="behavior-runtime-permissions">Runtime Permissions</h1>
<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 grant or revoke permissions individually for installed apps. </p>
<p>On your apps that target the M Preview release or higher, make sure to check for and request
permissions at runtime. To determine if your app has been granted a permission, call the
new {@link android.content.Context#checkSelfPermission(java.lang.String) checkSelfPermission()}
method. To request a permission, call the new
{@link android.app.Activity#requestPermissions(java.lang.String[], int) requestPermissions()}
method. Even if your app is not targeting the M Preview release, you should test your app under
the new permissions model.</p>
<p>For details on supporting the new permissions model in your app, see the
<a href="{@docRoot}preview/features/runtime-permissions.html">
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>
<ul>
<li><strong>Doze</strong>: If a user unplugs a device and leaves it stationary, with its screen off,
for a period of time, the device goes into <em>Doze</em> mode, where it attempts to keep the system
in a sleep state. In this mode, devices periodically resume normal operations for brief periods of
time so that app syncing can occur and the system can perform any pending operations.
<li><strong>App Standby</strong>: App Standby allows the system to determine that an app is idle
when the user is not actively using it. The system makes this determination when the user does not
touch the app for a certain period of time. If the device is unplugged, the system disables network
access and suspends syncs and jobs for the apps it deems idle.</li>
</ul>
<p>To learn more about these power-saving changes, see
<a href="{@docRoot}preview/features/power-mgmt.html">Power-Saving Optimizations</a>.</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
external storage device encrypts and formats the device to behave like internal storage. This
feature allows users to move both apps and private data of those apps between storage devices. When
moving apps, the system respects the
<a href="{@docRoot}guide/topics/manifest/manifest-element.html#install">{@code android:installLocation}</a>
preference in the manifest.</p>
<p>If your app accesses the following APIs or fields, be aware that the file paths they return
will dynamically change when the app is moved between internal and external storage devices.
When building file paths, it is strongly recommended that you always call these APIs dynamically.
Don’t use hardcoded file paths or persist fully-qualified file paths that were built previously.</p>
<ul>
<li>{@link android.content.Context} methods:
<ul>
<li>{@link android.content.Context#getFilesDir() getFilesDir()}</li>
<li>{@link android.content.Context#getCacheDir() getCacheDir()}</li>
<li>{@link android.content.Context#getCodeCacheDir() getCodeCacheDir()}</li>
<li>{@link android.content.Context#getDatabasePath(java.lang.String) getDatabasePath()}</li>
<li>{@link android.content.Context#getDir(java.lang.String,int) getDir()}</li>
<li>{@link android.content.Context#getNoBackupFilesDir() getNoBackupFilesDir()}</li>
<li>{@link android.content.Context#getFileStreamPath(java.lang.String) getFileStreamPath()}</li>
<li>{@link android.content.Context#getPackageCodePath() getPackageCodePath()}</li>
<li>{@link android.content.Context#getPackageResourcePath() getPackageResourcePath()}</li>
</ul>
</li>
<li>{@link android.content.pm.ApplicationInfo} fields:
<ul>
<li>{@link android.content.pm.ApplicationInfo#dataDir dataDir}</li>
<li>{@link android.content.pm.ApplicationInfo#sourceDir sourceDir}</li>
<li>{@link android.content.pm.ApplicationInfo#nativeLibraryDir nativeLibraryDir}</li>
<li>{@link android.content.pm.ApplicationInfo#publicSourceDir publicSourceDir}</li>
<li>{@link android.content.pm.ApplicationInfo#splitSourceDirs splitSourceDirs}</li>
<li>{@link android.content.pm.ApplicationInfo#splitPublicSourceDirs splitPublicSourceDirs}</li>
</ul>
</li>
</ul>
<p>To debug this feature in the developer preview, you can enable adoption of a USB drive that is
connected to an Android device through a USB On-The-Go (OTG) cable, by running this command:</p>
<pre class="no-prettyprint">
$ adb shell sm set-force-adoptable true
</pre>
<h2 id="behavior-apache-http-client">Apache HTTP Client Removal</h2>
<p>This preview removes support for the Apache HTTP client. If your app is using this client and
targets Android 2.3 (API level 9) or higher, use the {@link java.net.HttpURLConnection} class
instead. This API is more efficient because it reduces network use through transparent compression
and response caching, and minimizes power consumption. To continue using the Apache HTTP APIs, you
must first declare the following compile-time dependency in your {@code build.gradle} file:
</p>
<pre>
android {
useLibrary 'org.apache.http.legacy'
}
</pre>
<p>Android is moving away from OpenSSL to the
<a href="https://boringssl.googlesource.com/boringssl/" class="external-link">BoringSSL</a>
library. If you’re using the Android NDK in your app, don't link against cryptographic libraries
that are not a part of the NDK API, such as {@code libcrypto.so} and {@code libssl.so}. These
libraries are not public APIs, and may change or break without notice across releases and devices.
In addition, you may expose yourself to security vulnerabilities. Instead, modify your
native code to call the Java cryptography APIs via JNI or to statically link against a
cryptography library of your choice.</p>
<h2 id="behavior-audiomanager-Changes">AudioManager Changes</h2>
<p>Setting the volume directly or muting specific streams via the {@link android.media.AudioManager}
class is no longer supported. The {@link android.media.AudioManager#setStreamSolo(int,boolean)
setStreamSolo()} method is deprecated, and you should call the
{@link android.media.AudioManager#requestAudioFocus(android.media.AudioManager.OnAudioFocusChangeListener, int, int) requestAudioFocus()}
method instead. Similarly, the
{@link android.media.AudioManager#setStreamMute(int,boolean) setStreamMute()} method is
deprecated; instead, call the {@link android.media.AudioManager#adjustStreamVolume(int, int, int)
adjustStreamVolume()} method and pass in the direction value
{@link android.media.AudioManager#ADJUST_MUTE} or
{@link android.media.AudioManager#ADJUST_UNMUTE}.</p>
<h2 id="behavior-notifications">Notifications</h2>
<p>
This release removes the {@code Notification.setLatestEventInfo()} method. Use the
{@link android.app.Notification.Builder} class instead to construct notifications. To update a
notification repeatedly, reuse the {@link android.app.Notification.Builder} instance. Call the
{@link android.app.Notification.Builder#build()} method to get
updated {@link android.app.Notification} instances.
</p>
<p>The {@code adb shell dumpsys notification} command no longer prints out your notification text.
Use the {@code adb shell dumpsys notification --noredact} command instead to print out the text
in a notification object.</p>
<h2 id="behavior-test-selection">Text Selection</h2>
<img src="{@docRoot}preview/images/text-selection.gif"
style="float:right; margin:0 0 20px 30px" width="360" height="640" />
<p>When users select text in your app, you can now display text selection actions such as
<em>Cut</em>, <em>Copy</em>, and <em>Paste</em> in a
<a href="http://www.google.com/design/spec/patterns/selection.html#selection-text-selection"
class="external-link">floating toolbar</a>. The user interaction implementation is similar to that
for the contextual action bar, as described in
<a href="{@docRoot}guide/topics/ui/menus.html#CABforViews">
Enabling the contextual action mode for individual views</a>.</p>
<p>To implement a floating toolbar for text selection, make the following changes in your existing
apps:</p>
<ol>
<li>In your {@link android.view.View} or {@link android.app.Activity} object, change your
{@link android.view.ActionMode} calls from
{@code startActionMode(Callback)} to {@code startActionMode(Callback, ActionMode.TYPE_FLOATING)}.</li>
<li>Take your existing implementation of {@code ActionMode.Callback} and make it extend
{@link android.view.ActionMode.Callback2} instead.</li>
<li>Override the
{@link android.view.ActionMode.Callback2#onGetContentRect(android.view.ActionMode, android.view.View, android.graphics.Rect) onGetContentRect()}
method to provide the coordinates of the content {@link android.graphics.Rect} object
(such as a text selection rectangle) in the view.</li>
<li>If the rectangle positioning is no longer valid, and this is the only element to be invalidated,
call the {@link android.view.ActionMode#invalidateContentRect() invalidateContentRect()} method.</li>
</ol>
<p>If you are using <a href="{@docRoot}tools/support-library/index.html">
Android Support Library</a> revision 22.2, be aware that floating toolbars are not
backward-compatible and appcompat takes control over {@link android.view.ActionMode} objects by
default. This prevents floating toolbars from being displayed. To enable
{@link android.view.ActionMode} support in an
{@link android.support.v7.app.AppCompatActivity}, call
{@link android.support.v7.app.AppCompatActivity#getDelegate()}, then call
{@link android.support.v7.app.AppCompatDelegate#setHandleNativeActionModesEnabled(boolean)
setHandleNativeActionModesEnabled()} on the returned
{@link android.support.v7.app.AppCompatDelegate} object and set the input
parameter to {@code false}. This call returns control of {@link android.view.ActionMode} objects to
the framework. In devices running the M Preview, that allows the framework to support
{@link android.support.v7.app.ActionBar} or floating toolbar modes, while on pre-M Preview devices,
only the {@link android.support.v7.app.ActionBar} modes are supported.</p>
<h2 id="behavior-keystore">Android Keystore Changes</h2>
<p>With this preview, the
<a href="{@docRoot}training/articles/keystore.html">Android Keystore provider</a> no longer supports
DSA. ECDSA is still supported.</p>
<p>Keys which do not require encryption at rest will no longer be deleted when secure lock screen
is disabled or reset (for example, by the user or a Device Administrator). Keys which require
encryption at rest will be deleted during these events.</p>
<h2 id="behavior-network">Wi-Fi and Networking Changes</h2>
<p>This preview introduces the following behavior changes to the Wi-Fi and networking APIs.</p>
<ul>
<li>Your apps can now change the state of {@link android.net.wifi.WifiConfiguration} objects only
if you created these objects. You are not permitted to modify or delete
{@link android.net.wifi.WifiConfiguration} objects created by the user or by other apps.
</li>
<li>
Previously, if an app forced the device to connect to a specific Wi-Fi network by using
{@link android.net.wifi.WifiManager#enableNetwork(int,boolean) enableNetwork()} with the
{@code disableAllOthers=true} setting, the device disconnected from other networks such as
cellular data. In this preview, the device no longer disconnects from such other networks. If
your app’s {@code targetSdkVersion} is {@code “20”} or lower, it is pinned to the selected
Wi-Fi network. If your app’s {@code targetSdkVersion} is {@code “21”} or higher, use the
multinetwork APIs (such as
{@link android.net.Network#openConnection(java.net.URL) openConnection()},
{@link android.net.Network#bindSocket(java.net.Socket) bindSocket()}, and the new
{@link android.net.ConnectivityManager#bindProcessToNetwork(android.net.Network)
bindProcessToNetwork()} method) to ensure that its network traffic is sent on the selected network.</li>
</ul>
<h2 id="behavior-camera">Camera Service Changes</h2>
<p>In this preview, the model for accessing shared resources in the camera service has been changed
from the previous “first come, first serve” access model to an access model where high-priority
processes are favored. Changes to the service behavior include:</p>
<ul>
<li>Access to camera subsystem resources, including opening and configuring a camera device, is
awarded based on the “priority” of the client application process. Application processes with
user-visible or foreground activities are generally given a higher-priority, making camera resource
acquisition and use more dependable.</li>
<li>Active camera clients for lower priority apps may be “evicted” when a higher priority
application attempts to use the camera. In the deprecated {@link android.hardware.Camera} API,
this results in
{@link android.hardware.Camera.ErrorCallback#onError(int,android.hardware.Camera) onError()} being
called for the evicted client. In the {@link android.hardware.camera2 Camera2} API, it results in
{@link android.hardware.camera2.CameraDevice.StateCallback#onDisconnected(android.hardware.camera2.CameraDevice) onDisconnected()}
being called for the evicted client.</li>
<li>On devices with appropriate camera hardware, separate application processes are able to
independently open and use separate camera devices simultaneously. However, multi-process use
cases, where simultaneous access causes significant degradation of performance or capabilities of
any of the open camera devices, are now detected and disallowed by the camera service. This change
may result in “evictions” for lower priority clients even when no other app is directly
attempting to access the same camera device.
</li>
<li>
Changing the current user causes active camera clients in apps owned by the previous user account
to be evicted. Access to the camera is limited to user profiles owned by the current device user.
In practice, this means that a “Guest” account, for example, will not be able to leave running
processes that use the camera subsystem when the user has switched to a different account.
</li>
</ul>
<h2 id="behavior-runtime">Runtime</h2>
<p>The ART runtime now properly implements access rules for the
{@link java.lang.reflect.Constructor#newInstance(java.lang.Object...) newInstance()} method. This
change fixes a problem where Dalvik was checking access rules incorrectly in previous versions.
If your app uses the
{@link java.lang.reflect.Constructor#newInstance(java.lang.Object...) newInstance()} method and you
want to override access checks, call the
{@link java.lang.reflect.Constructor#setAccessible(boolean) setAccessible()} method with the input
parameter set to {@code true}. If your app uses the
<a href="{@docRoot}tools/support-library/features.html#v7-appcompat">v7 appcompat library</a> or the
<a href="{@docRoot}tools/support-library/features.html#v7-recyclerview">v7 recyclerview library</a>,
you must update your app to use to the latest versions of these libraries. Otherwise, make sure that
any custom classes referenced from XML are updated so that their class constructors are accessible.</p>
<p>This preview updates the behavior of the dynamic linker. The dynamic linker now understands the
difference between a library’s {@code soname} and its path
(<a href="https://code.google.com/p/android/issues/detail?id=6670" class="external-link">
public bug 6670</a>), and search by {@code soname} is now
implemented. Apps which previously worked that have bad {@code DT_NEEDED} entries
(usually absolute paths on the build machine’s file system) may fail when loaded.</p>
<p>The {@code dlopen(3) RTLD_LOCAL} flag is now correctly implemented. Note that
{@code RTLD_LOCAL} is the default, so calls to {@code dlopen(3)} that didn’t explicitly use
{@code RTLD_LOCAL} will be affected (unless your app explicitly used {@code RTLD_GLOBAL}). With
{@code RTLD_LOCAL}, symbols will not be made available to libraries loaded by later calls to
{@code dlopen(3)} (as opposed to being referenced by {@code DT_NEEDED} entries).</p>
</p>
<h2 id="behavior-hardware-id">Access to Hardware Identifier</h2>
<p>To provide users with greater data protection, starting in this release, Android
removes programmatic access to the device’s local hardware identifier for
apps using the Wi-Fi and Bluetooth APIs. The
{@link android.net.wifi.WifiInfo#getMacAddress() WifiInfo.getMacAddress()} and the
{@link android.bluetooth.BluetoothAdapter#getAddress() BluetoothAdapter.getAddress()} methods
now return a constant value of {@code 02:00:00:00:00:00}.</p>
<p>To access the hardware identifiers of nearby external devices via Bluetooth and Wi-Fi scans,
your app must now have the following permissions:</p>
<ul>
<li>{@link android.net.wifi.WifiManager#getScanResults() WifiManager.getScanResults()}:
Your app must have {@link android.Manifest.permission#ACCESS_FINE_LOCATION} or
{@link android.Manifest.permission#ACCESS_COARSE_LOCATION} permission.</li>
<li>{@link android.bluetooth.BluetoothDevice#ACTION_FOUND BluetoothDevice.ACTION_FOUND}:
Your app must have {@link android.Manifest.permission#ACCESS_COARSE_LOCATION} permission.</li>
<li>{@link android.bluetooth.le.BluetoothLeScanner#startScan(android.bluetooth.le.ScanCallback)
BluetoothLeScanner.startScan()}: Your app must have
{@link android.Manifest.permission#ACCESS_FINE_LOCATION} or
{@link android.Manifest.permission#ACCESS_COARSE_LOCATION} permission.</li>
</ul>
<p class="note"><strong>Note</strong>: When a device running M Developer Preview initiates a
background Wi-Fi or Bluetooth scan, the operation is visible to external devices as
originating from a randomized MAC address.</p>
<h2 id="behavior-apk-validation">APK Validation</h2>
<p>The platform now performs stricter validation of APKs. An APK is considered corrupt if a file is
declared in the manifest but not present in the APK itself. An APK must be re-signed if any of the
contents are removed.</p>
<h2 id="behavior-usb">USB Connection</h2>
<p>Device connections through the USB port are now set to charge-only mode by default. To access
the device and its content over a USB connection, users must explicitly grant permission for such
interactions. If your app supports user interactions with the device over a USB port, take into
consideration that the interaction must be explicitly enabled.
</p>
<h2 id="behavior-afw">Android for Work Changes</h2>
<p>This preview includes the following behavior changes for Android for Work:</p>
<ul>
<li><strong>Work contacts in personal contexts.</strong> The Google Dialer
Call Log now displays work contacts when the user views past calls.
Setting
{@link android.app.admin.DevicePolicyManager#setCrossProfileCallerIdDisabled(android.content.ComponentName, boolean) setCrossProfileCallerIdDisabled()}
to {@code true} hides the work profile contacts in the Google Dialer Call Log. Work contacts can be
displayed along with personal contacts to devices over Bluetooth only if
you set {@link android.app.admin.DevicePolicyManager#setBluetoothContactSharingDisabled(android.content.ComponentName, boolean)
setBluetoothContactSharingDisabled()} to {@code false}. By default, it is set to {@code true}.
</li>
<li><strong>Wi-Fi configuration removal:</strong> Wi-Fi configurations added by a Profile Owner
(for example, through calls to the
{@link android.net.wifi.WifiManager#addNetwork(android.net.wifi.WifiConfiguration)
addNetwork()} method) are now removed if that work profile is deleted.
</li>
<li><strong>Wi-Fi configuration lockdown:</strong> Any Wi-Fi configuration created by
an active Device Owner can no longer be modified or deleted by the user if
{@link android.provider.Settings.Global#WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN} is non-zero.
The user can still create and modify their own Wi-Fi configurations. Active Device
Owners have the privilege of editing or removing any Wi-Fi configurations, including
those not created by them.
</li>
<li><strong>Download Work Policy Controller via Google account addition:</strong> When a Google
account that requires management via a Work Policy Controller (WPC) app is added to a device
outside of a managed context, the add account flow now prompts the user to install the
appropriate WPC. This behavior also applies to accounts added via
<strong>Settings > Accounts</strong> and in the initial device setup wizard.</li>
<li><strong>Changes to specific {@link android.app.admin.DevicePolicyManager} API behaviors:</strong>
<ul>
<li>Calling the
{@link android.app.admin.DevicePolicyManager#setCameraDisabled(android.content.ComponentName,boolean) setCameraDisabled()}
method affects the camera for the calling user only; calling it from the managed profile doesn’t
affect camera apps running on the primary user.</li>
<li>In addition, the
{@link android.app.admin.DevicePolicyManager#setKeyguardDisabledFeatures(android.content.ComponentName,int) setKeyguardDisabledFeatures()}
method is now available for Profile Owners, as well as to Device Owners. </li>
<li>A Profile Owner can set these keyguard restrictions:
<ul>
<li>{@link android.app.admin.DevicePolicyManager#KEYGUARD_DISABLE_TRUST_AGENTS} and
{@link android.app.admin.DevicePolicyManager#KEYGUARD_DISABLE_FINGERPRINT}, which affect the
keyguard settings for the profile’s parent user.</li>
<li>{@link android.app.admin.DevicePolicyManager#KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS}, which
only affects notifications generated by applications in the managed profile.</li>
</ul>
</li>
<li>The {@link android.app.admin.DevicePolicyManager#createAndInitializeUser(android.content.ComponentName, java.lang.String, java.lang.String, android.content.ComponentName, android.os.Bundle) createAndInitializeUser()} and {@link android.app.admin.DevicePolicyManager#createUser(android.content.ComponentName, java.lang.String) createUser()} methods have been deprecated.</li>
<li>The {@link android.app.admin.DevicePolicyManager#setScreenCaptureDisabled(android.content.ComponentName, boolean) setScreenCaptureDisabled()}
method now also blocks the assist structure when an app of the given user is in the foreground. </li>
<li>{@link android.app.admin.DevicePolicyManager#EXTRA_PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM}
now defaults to SHA-256. SHA-1 is still supported for backwards compatibility but will be removed
in future.
{@link android.app.admin.DevicePolicyManager#EXTRA_PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM}
now only accepts SHA-256.</li>
<li>Device initializer APIs which existed in the M Developer Preview are now removed.</li>
<li><code>EXTRA_PROVISIONING_RESET_PROTECTION_PARAMETERS</code> is removed so NFC bump
provisioning cannot programmatically unlock a factory reset protected device.</li>
<li>You can now use the {@link android.app.admin.DevicePolicyManager#EXTRA_PROVISIONING_ADMIN_EXTRAS_BUNDLE}
extra to pass data to the device owner app during NFC provisioning of the managed device.</li>
<li>Android for Work APIs are optimized for M runtime permissions, including Work profiles,
assist layer, and others. New {@link android.app.admin.DevicePolicyManager} permission APIs don't
affect pre-M apps.</li>
<li>When users back out of the synchronous part of the setup flow initiated through an
{@link android.app.admin.DevicePolicyManager#ACTION_PROVISION_MANAGED_PROFILE} or
{@link android.app.admin.DevicePolicyManager#ACTION_PROVISION_MANAGED_DEVICE} intent, the system
now returns a {@link android.app.Activity#RESULT_CANCELED} result code.</li>
</ul></li>
<li><strong>Changes to other APIs</strong>:
<ul>
<li>Data Usage: The {@code android.app.usage.NetworkUsageStats} class has been renamed
{@link android.app.usage.NetworkStats}.</li>
</ul>
</li>
<li><strong>Changes to global settings</strong>:
<ul>
<li>These settings can no longer be set via {@link android.app.admin.DevicePolicyManager#setGlobalSetting(android.content.ComponentName, java.lang.String, java.lang.String) setGlobalSettings()}</code>:
<ul>
<li><code>BLUETOOTH_ON</code></li>
<li><code>DEVELOPMENT_SETTINGS_ENABLED</code></li>
<li><code>MODE_RINGER</code></li>
<li><code>NETWORK_PREFERENCE</code></li>
<li><code>WIFI_ON</code></li>
</ul>
</li>
<li>These global settings can now be set via {@link android.app.admin.DevicePolicyManager#setGlobalSetting(android.content.ComponentName, java.lang.String, java.lang.String) setGlobalSettings()}:
<ul>
<li>{@link android.provider.Settings.Global#WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN}</li>
</ul>
</li>
</ul>
</ul>

371
docs/html/preview/download.jd Normal file
View File

@@ -0,0 +1,371 @@
page.title=Downloads
page.image=images/cards/card-download_16-9_2x.png
@jd:body
<div style="position:relative; min-height:600px">
<div class="wrap" id="tos" style="position:absolute;display:none;width:inherit;">
<p class="sdk-terms-intro">Before downloading and installing components of the Android Preview
SDK, you must agree to the following terms and conditions.</p>
<h2 class="norule">Terms and Conditions</h2>
<div class="sdk-terms" onfocus="this.blur()" style="width:678px">
This is the Android SDK Preview License Agreement (the “License Agreement”).
1. Introduction
1.1 The Android SDK Preview (referred to in the License Agreement as the “Preview” and specifically including the Android system files, packaged APIs, and Preview library files, if and when they are made available) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the Preview.
1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time.
1.3 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States.
2. Accepting the License Agreement
2.1 In order to use the Preview, you must first agree to the License Agreement. You may not use the Preview if you do not accept the License Agreement.
2.2 By clicking to accept and/or using the Preview, you hereby agree to the terms of the License Agreement.
2.3 You may not use the Preview and may not accept the License Agreement if you are a person barred from receiving the Preview under the laws of the United States or other countries including the country in which you are resident or from which you use the Preview.
2.4 If you will use the Preview internally within your company or organization you agree to be bound by the License Agreement on behalf of your employer or other entity, and you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the Preview on behalf of your employer or other entity.
3. Preview License from Google
3.1 Subject to the terms of the License Agreement, Google grants you a royalty-free, non-assignable, non-exclusive, non-sublicensable, limited, revocable license to use the Preview, personally or internally within your company or organization, solely to develop applications to run on the Android platform.
3.2 You agree that Google or third parties owns all legal right, title and interest in and to the Preview, including any Intellectual Property Rights that subsist in the Preview. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you.
3.3 You may not use the Preview for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not: (a) copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Preview or any part of the Preview; or (b) load any part of the Preview onto a mobile handset or any other hardware device except a personal computer, combine any part of the Preview with other software, or distribute any software or device incorporating a part of the Preview.
3.4 You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the Preview.
3.5 Use, reproduction and distribution of components of the Preview licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. You agree to remain a licensee in good standing in regard to such open source software licenses under all the rights granted and to refrain from any actions that may terminate, suspend, or breach such rights.
3.6 You agree that the form and nature of the Preview that Google provides may change without prior notice to you and that future versions of the Preview may be incompatible with applications developed on previous versions of the Preview. You agree that Google may stop (permanently or temporarily) providing the Preview (or any features within the Preview) to you or to users generally at Google's sole discretion, without prior notice to you.
3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features.
3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the Preview.
4. Use of the Preview by You
4.1 Google agrees that nothing in the License Agreement gives Google any right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the Preview, including any intellectual property rights that subsist in those applications.
4.2 You agree to use the Preview and write applications only for purposes that are permitted by (a) the License Agreement, and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).
4.3 You agree that if you use the Preview to develop applications, you will protect the privacy and legal rights of users. If users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If users provide you with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, each user has given you permission to do so.
4.4 You agree that you will not engage in any activity with the Preview, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of Google or any third party.
4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so.
4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.
4.7 The Preview is in development, and your testing and feedback are an important part of the development process. By using the Preview, you acknowledge that implementation of some features are still under development and that you should not rely on the Preview having the full functionality of a stable release. You agree not to publicly distribute or ship any application using this Preview as this Preview will no longer be supported after the official Android SDK is released.
5. Your Developer Credentials
5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.
6. Privacy and Information
6.1 In order to continually innovate and improve the Preview, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the Preview are being used and how they are being used. Before any of this information is collected, the Preview will notify you and seek your consent. If you withhold consent, the information will not be collected.
6.2 The data collected is examined in the aggregate to improve the Preview and is maintained in accordance with Google's Privacy Policy located at http://www.google.com/policies/privacy/.
7. Third Party Applications
7.1 If you use the Preview to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.
7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners.
7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party.
8. Using Google APIs
8.1 Google APIs
8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.
8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so.
9. Terminating the License Agreement
9.1 the License Agreement will continue to apply until terminated by either you or Google as set out below.
9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the Preview and any relevant developer credentials.
9.3 Google may at any time, terminate the License Agreement, with or without cause, upon notice to you.
9.4 The License Agreement will automatically terminate without notice or other action upon the earlier of:
(A) when Google ceases to provide the Preview or certain parts of the Preview to users in the country in which you are resident or from which you use the service; and
(B) Google issues a final release version of the Android SDK.
9.5 When the License Agreement is terminated, the license granted to you in the License Agreement will terminate, you will immediately cease all use of the Preview, and the provisions of paragraphs 10, 11, 12 and 14 shall survive indefinitely.
10. DISCLAIMERS
10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE PREVIEW IS AT YOUR SOLE RISK AND THAT THE PREVIEW IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE.
10.2 YOUR USE OF THE PREVIEW AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE PREVIEW IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. WITHOUT LIMITING THE FOREGOING, YOU UNDERSTAND THAT THE PREVIEW IS NOT A STABLE RELEASE AND MAY CONTAIN ERRORS, DEFECTS AND SECURITY VULNERABILITIES THAT CAN RESULT IN SIGNIFICANT DAMAGE, INCLUDING THE COMPLETE, IRRECOVERABLE LOSS OF USE OF YOUR COMPUTER SYSTEM OR OTHER DEVICE.
10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
11. LIMITATION OF LIABILITY
11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.
12. Indemnification
12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys’ fees) arising out of or accruing from (a) your use of the Preview, (b) any application you develop on the Preview that infringes any Intellectual Property Rights of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you of the License Agreement.
13. Changes to the License Agreement
13.1 Google may make changes to the License Agreement as it distributes new versions of the Preview. When these changes are made, Google will make a new version of the License Agreement available on the website where the Preview is made available.
14. General Legal Terms
14.1 the License Agreement constitutes the whole legal agreement between you and Google and governs your use of the Preview (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the Preview.
14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google.
14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable.
14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement.
14.5 EXPORT RESTRICTIONS. THE PREVIEW IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE PREVIEW. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE.
14.6 The License Agreement may not be assigned or transferred by you without the prior written approval of Google, and any attempted assignment without such approval will be void. You shall not delegate your responsibilities or obligations under the License Agreement without the prior written approval of Google.
14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.
</div><!-- sdk terms -->
<div id="sdk-terms-form">
<p>
<input id="agree" type="checkbox" name="agree" value="1" onclick="onAgreeChecked()" />
<label id="agreeLabel" for="agree">I have read and agree with the above terms and conditions</label>
</p>
<p><a href="" class="button disabled" id="downloadForRealz" onclick="return onDownloadForRealz(this);"></a></p>
</div>
</div><!-- end TOS -->
<div id="landing">
<div id="qv-wrapper">
<div id="qv">
<h2>In this document</h2>
<ol>
<li><a href="#sdk">Android 6.0 SDK</a></li>
<li><a href="#docs">Developer Documentation</a></li>
<li><a href="#images">Hardware System Images</a></li>
</ol>
<h2>Legacy downloads</h2>
<ol>
<li><a href="{@docRoot}preview/download_mp1.html">Developer Preview Archive</a></li>
</ol>
</div>
</div>
<p>
The Android M Preview SDK includes development tools, Android system images, and library files to
help you test your app and the new APIs coming in the next release of the platform. This document
describes how to get the downloadable components of the preview for testing your app.
</p>
<h2 id="sdk">Android 6.0 SDK</h2>
<p>
With Developer Preview 3, the official Android 6.0 SDK is now available for download through the <a href=
"{@docRoot}tools/help/sdk-manager.html">Android SDK Manager</a>. For more information on
downloading and configuring the SDK, see <a href=
"{@docRoot}preview/setup-sdk.html#downloadSdk">Set Up the SDK</a>.
</p>
<h2 id="docs">Developer Documentation</h2>
<p>
The developer documentation for Developer Preview 3 is released as Android 6.0 (API level 23) and
is available online, including the <a href="{@docRoot}reference/packages.html">API level 23
reference</a> and <a href="{@docRoot}sdk/api_diff/23/changes.html">diff report</a>. The following
developer documentation download package provides additional, incremental difference reports
between the preview releases.
</p>
<table>
<tr>
<th scope="col">Description</th>
<th scope="col">Download / Checksums</th>
</tr>
<tr id="docs-dl">
<td>Android M Preview 3<br>Developer Docs</td>
<td><a href="#top" onclick="onDownload(this)"
>m-preview-3-developer-docs.zip</a><br>
MD5: d99b14b0c06d31c8dfecb25072654ca3<br>
SHA-1: 9cefeeda07676130da606a1796e1c00fffc667c1
</td>
</tr>
<table>
<h2 id="images">Hardware System Images</h2>
<p>
These system images allow you to install a preview version of the platform on a physical device for
testing. By configuring a device with one of these images, you can install and test your app to
see how it performs on the next version of the platform. The process of installing a system image
on a device <em>removes all data from the device</em>, so you should backup your data before
installing a system image.
</p>
<p class="warning">
<b>Warning:</b> The following Android system images are previews and are subject to change. Your
use of these system images is governed by the Android SDK Preview License Agreement. The Android
preview system images are not stable releases, and may contain errors and defects that can result
in damage to your computer systems, devices, and data. The preview Android system images are not
subject to the same testing as the factory OS and can cause your phone and installed services and
applications to stop working.
</p>
<table>
<tr>
<th scope="col">Device</th>
<th scope="col">Download / Checksums</th>
</tr>
<tr id="hammerhead">
<td>Nexus 5 (GSM/LTE) <br>"hammerhead"</td>
<td><a href="#top" onclick="onDownload(this)"
>hammerhead-MPA44I-preview-2ebbc049.tgz</a><br>
MD5: 91a924fb0c9f8e716e3b4c9954fd0dbb<br>
SHA-1: 2ebbc049b68c4da8baeee3e42bb94d7a965ba4a3
</td>
</tr>
<tr id="shamu">
<td>Nexus 6 <br>"shamu"</td>
<td><a href="#top" onclick="onDownload(this)"
>shamu-MPA44I-preview-62b9c486.tgz</a><br>
MD5: ac6e58da86125073d9c395257fd42664<br>
SHA-1: 62b9c486fd7a5020e228d53ca5acd5c1857e48ff
</td>
</tr>
<tr id="volantis">
<td>Nexus 9 <br>"volantis"</td>
<td><a href="#top" onclick="onDownload(this)"
>volantis-MPA44I-preview-5c30a6e2.tgz</a><br>
MD5: 7f83768757913d3fea945a661020d185<br>
SHA-1: 5c30a6e2acd11a81f4105b12d23ff654f534f699
</td>
</tr>
<tr id="fugu">
<td>Nexus Player <br>"fugu"</td>
<td><a href="#top" onclick="onDownload(this)"
>fugu-MPA44I-preview-2860040a.tgz</a><br>
MD5: 438da8d37da9e341a69cfb16a4001ac5<br>
SHA-1: 2860040a326582f1ff5f702bf9a1ef002717fc98
</td>
</tr>
</table>
<h3 id="install-image">Install an Image to a Device</h3>
<p>
In order to use a device image for testing, you must install it on a compatible device. Follow
the instructions below to install a system image:
</p>
<ol>
<li>Download and uncompress one of the system image packages listed here.</li>
<li>Backup any data you want to preserve from the device.</li>
<li>Follow the instructions at
<a href="https://developers.google.com/android/nexus/images#instructions">developers.google.com/android</a>
to flash the image onto your device.</li>
</ol>
<h3 id="update-image">Updating a Device with the Preview</h3>
<p>
Once you have installed a preview system image on a development device, the device is upgraded
automatically with the next preview release through over-the-air (OTA) updates. When the update
is available, the device displays notification that an update is available and allows you to
install it. You can also manually install the next preview image by repeating the procedure in
the previous section.
</p>
<h3 id="revertDevice">Revert a Device to Factory Specifications</h3>
<p>
If you want to uninstall the preview and revert the device to factory specifications, go to
<a href="http://developers.google.com/android/nexus/images">developers.google.com/android</a> and
download the image you want to flash to for your device. Follow the instructions on that page to
flash the image to your device.
</p>
</div><!-- landing -->
</div><!-- relative wrapper -->
<script>
var urlRoot = "http://storage.googleapis.com/androiddevelopers/shareables/preview/";
function onDownload(link) {
$("#downloadForRealz").html("Download " + $(link).text());
$("#downloadForRealz").attr('href', urlRoot + $(link).text());
$("#tos").fadeIn('fast');
$("#landing").fadeOut('fast');
return true;
}
function onAgreeChecked() {
/* verify that the TOS is agreed */
if ($("input#agree").is(":checked")) {
/* reveal the download button */
$("a#downloadForRealz").removeClass('disabled');
} else {
$("a#downloadForRealz").addClass('disabled');
}
}
function onDownloadForRealz(link) {
if ($("input#agree").is(':checked')) {
/*
$("#tos").fadeOut('fast');
$("#landing").fadeIn('fast');
*/
ga('send', 'event', 'M Preview', 'System Image', $("#downloadForRealz").html());
/*
location.hash = "";
*/
return true;
} else {
return false;
}
}
$(window).hashchange( function(){
if (location.hash == "") {
location.reload();
}
});
</script>

187
docs/html/preview/guide.jd Normal file
View File

@@ -0,0 +1,187 @@
page.title=Testing Guide
page.image=images/cards/card-build_16x9_2x.png
page.keywords=previewresources,androidm,testing,permissions
@jd:body
<div id="qv-wrapper">
<div id="qv">
<h2>In this document</h2>
<ol>
<li><a href="#runtime-permissions">Testing Permissions</a></li>
<li><a href="#doze-standby">Testing Doze and App Standby</a></li>
<li><a href="#ids">Auto Backup and Device Identifiers</a></li>
</ol>
</div>
</div>
<p>
The Android M Developer Preview gives you an opportunity to ensure your apps work with the next
version of the platform. This preview includes a number of APIs and behavior changes that can
impact your app, as described in the <a href="{@docRoot}preview/api-overview.html">API
Overview</a> and <a href="{@docRoot}preview/behavior-changes.html">Behavior Changes</a>. In testing
your app with the preview, there are some specific system changes that you should focus on to
ensure that users have a good experience.
</p>
<p>
This guide describes the what and how to test preview features with your app. You should
prioritize testing of these specific preview features, due to their high potential impact on your
app's behavior:
</p>
<ul>
<li><a href="#runtime-permissions">Permissions</a>
</li>
<li><a href="#doze-standby">Doze and App Standby</a>
</li>
<li><a href="#ids">Auto Backup and Device Identifiers</a></li>
</ul>
<p>
For more information about how to set up devices or virtual devices with a preview system image
for testing, see <a href="{@docRoot}preview/setup-sdk.html">Set up the Preview SDK</a>.
</p>
<h2 id="runtime-permissions">Testing Permissions</h2>
<p>
The new <a href="{@docRoot}preview/features/runtime-permissions.html">Permissions</a> model
changes the way that permissions are allocated to your app by the user. Instead of granting all
permissions during the install procedure, your app must ask the user for individual permissions
at runtime. For users this behavior provides more granular control over each app’s activities, as
well as better context for understanding why the app is requesting a specific permission. Users
can grant or revoke the permissions granted to an app individually at any time. This feature of
the preview is most likely to have an impact on your app's behavior and may prevent some of your
app features from working, or they may work in a degraded state.
</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
publishing an updated version of your app at the official platform launch.
</p>
<h3 id="permission-test-tips">Test tips</h3>
<p>
Use the following test tips to help you plan and execute testing of your app with the new
permissions behavior.
</p>
<ul>
<li>Identify your app’s current permissions and the related code paths.</li>
<li>Test user flows across permission-protected services and data.</li>
<li>Test with various combinations of granted/revoked permission.</li>
<li>Use the {@code adb} tool to manage permssions from the command line:
<ul>
<li>List permissions and status by group:
<pre>adb shell pm list permissions -d -g</pre>
</li>
<li>Grant or revoke one or more permissions using the following syntax:<br>
<pre>adb shell pm [grant|revoke] &lt;permission.name&gt; ...</pre>
</li>
</ul>
</li>
<li>Analyze your app for services that use permissions.</li>
</ul>
<h3 id="permission-test-strategy">Test strategy</h3>
<p>
The permissions change affects the structure and design of your app, as well as
the user experience and flows you provide to users. You should assess your app’s current
permissions use and start planning for the new flows you want to offer. The official release of
the platform provides compatibility behavior, but you should plan on updating your app and not
rely on these behaviors.
</p>
<p>
Identify the permissions that your app actually needs and uses, and then find the various code
paths that use the permission-protected services. You can do this through a combination of
testing on the new platform and code analysis. In testing, you should focus on opting in to
runtime permissions by changing the app’s {@code targetSdkVersion} to the preview version. For
more information, see <a href="{@docRoot}preview/setup-sdk.html#">Set up the Preview SDK</a>.
</p>
<p>
Test with various combinations of permissions revoked and added, to highlight the user flows that
depend on permissions. Where a dependency is not obvious or logical you should consider
refactoring or compartmentalizing that flow to eliminate the dependency or make it clear why the
permission is needed.
</p>
<p>
For more information on the behavior of runtime permissions, testing, and best practices, see the
<a href="{@docRoot}preview/features/runtime-permissions.html">Permissions</a> developer
preview page.
</p>
<h2 id="doze-standby">Testing Doze and App Standby</h2>
<p>
The power saving features of Doze and App Standby limit the amount of background processing that
your app can perform when a device is in an idle state or while your app is not in focus. The
restrictions the system may impose on apps include limited or no network access,
suspended background tasks, suspended Notifications, ignored wake requests, and alarms. To ensure
that your app behaves properly with these power saving optimizations, you should test your app by
simulating these low power states.
</p>
<h4 id="doze">Testing your app with Doze</h4>
<p>To test Doze with your app:</p>
<ol>
<li>Configure a hardware device or virtual device with a M Preview system image.</li>
<li>Connect the device to your development machine and install your app.</li>
<li>Run your app and leave it active.</li>
<li>Simulate the device going into Doze mode by running the following commands:
<pre>
$ adb shell dumpsys battery unplug
$ adb shell dumpsys deviceidle step
$ adb shell dumpsys deviceidle -h
</pre>
</li>
<li>Observe the behavior of your app when the device is re-activated. Make sure it
recovers gracefully when the device exits Doze.</li>
</ol>
<h4 id="standby">Testing apps with App Standby</h4>
<p>To test the App Standby mode with your app:</p>
<ol>
<li>Configure a hardware device or virtual device with a M Preview system image.</li>
<li>Connect the device to your development machine and install your app.</li>
<li>Run your app and leave it active.</li>
<li>Simulate the app going into standby mode by running the following commands:
<pre>
$ adb shell am broadcast -a android.os.action.DISCHARGING
$ adb shell am set-idle &lt;packageName&gt; true
</pre>
</li>
<li>Simulate waking your app using the following command:
<pre>$ adb shell am set-idle &lt;packageName&gt; false</pre>
</li>
<li>Observe the behavior of your app when it is woken. Make sure it recovers gracefully
from standby mode. In particular, you should check if your app's Notifications and background
jobs continue to function as expected.</li>
</ol>
<h2 id="ids">Auto Backup for Apps and Device-Specific Identifiers</h2>
<p>If your app is persisting any device-specific identifiers, such as Google
Cloud Messaging registration ID, in internal storage,
make sure to follow best practices to exclude the storage
location from auto-backup, as described in <a href="{@docRoot}preview/backup/index.html">Auto
Backup for Apps</a>. </p>

BIN
docs/html/preview/images/m-preview-timeline-crop.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
docs/html/preview/images/m-preview-timeline.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

73
docs/html/preview/index.jd Normal file
View File

@@ -0,0 +1,73 @@
page.title=Android N Developer Preview
page.tags="preview",
meta.tags="preview, devpreview", androidm
fullpage=true
forcelocalnav=true
header.hide=1
footer.hide=1
@jd:body
<section class="dac-expand dac-hero dac-light" >
<div class="wrap">
<div class="cols dac-hero-content">
<div class="col-9of16 col-push-7of16 dac-hero-figure">
<img class="dac-hero-image" src="{@docRoot}images/home/devices-hero_620px_2x.png"
srcset="{@docRoot}images/home/devices-hero_620px.png 1x,
{@docRoot}images/home/devices-hero_620px_2x.png 2x">
</div>
<div class="col-7of16 col-pull-9of16">
<h1 class="dac-hero-title">Android N Developer Preview</h1>
<p class="dac-hero-description">
<strong>Get your apps ready for the next version of Android.</strong>
Test on Nexus 5, 6, 9, and
Player. Explore what's new &mdash; <strong>multiwindow UI</strong>,
<strong>Doze Lite</strong> and <strong>Background Check</strong> power-saving features, new
<strong>notification</strong> capabilities, and more.
</p>
<a class="dac-hero-cta" href="{@docRoot}preview/overview.html">
<span class="dac-sprite dac-auto-chevron"></span>
Get started
</a><!--<br>
<a class="dac-hero-cta" href="{@docRoot}preview/support.html">
<span class="dac-sprite dac-auto-chevron"></span>
Update to Developer Preview (final SDK)
</a><br>-->
</div>
</div>
<div class="dac-section dac-small">
<div class="resource-widget resource-flow-layout col-16"
data-query="collection:preview/landing/resources"
data-cardSizes="6x2"
data-maxResults="6"></div>
</div>
</div>
</section>
<section class="dac-section dac-gray"><div class="wrap">
<h1 class="dac-section-title">Resources</h1>
<div class="dac-section-subtitle">
Essential information to help you get your apps ready for Android M.
</div>
<div class="resource-widget resource-flow-layout col-16"
data-query="collection:preview/landing/more"
data-cardSizes="6x6"
data-maxResults="16"></div>
<ul class="dac-section-links">
<li class="dac-section-link">
<a href="https://code.google.com/p/android-developer-preview/">
<span class="dac-sprite dac-auto-chevron"></span>
Report Issues
</a>
</li>
<li class="dac-section-link"><a href="http://g.co/dev/AndroidMDevPreview">
<span class="dac-sprite dac-auto-chevron"></span>
Join G+ Community
</a>
</li>
</ul>
</div>
</section>

143
docs/html/preview/license.jd Normal file
View File

@@ -0,0 +1,143 @@
page.title=License Agreement
@jd:body
<p>
To get started with the Android SDK Preview, you must agree to the following terms and conditions.
As described below, please note that this is a preview version of the Android SDK, subject to change, that you use at your own risk. The Android SDK Preview is not a stable release, and may contain errors and defects that can result in serious damage to your computer systems, devices and data.
</p>
<p>
This is the Android SDK Preview License Agreement (the “License Agreement”).
</p>
<div class="sdk-terms" style="height:auto;border:0;padding:0;width:700px">
1. Introduction
1.1 The Android SDK Preview (referred to in the License Agreement as the “Preview” and specifically including the Android system files, packaged APIs, and Preview library files, if and when they are made available) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the Preview.
1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time.
1.3 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States.
2. Accepting the License Agreement
2.1 In order to use the Preview, you must first agree to the License Agreement. You may not use the Preview if you do not accept the License Agreement.
2.2 By clicking to accept and/or using the Preview, you hereby agree to the terms of the License Agreement.
2.3 You may not use the Preview and may not accept the License Agreement if you are a person barred from receiving the Preview under the laws of the United States or other countries including the country in which you are resident or from which you use the Preview.
2.4 If you will use the Preview internally within your company or organization you agree to be bound by the License Agreement on behalf of your employer or other entity, and you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the Preview on behalf of your employer or other entity.
3. Preview License from Google
3.1 Subject to the terms of the License Agreement, Google grants you a royalty-free, non-assignable, non-exclusive, non-sublicensable, limited, revocable license to use the Preview, personally or internally within your company or organization, solely to develop applications to run on the Android platform.
3.2 You agree that Google or third parties owns all legal right, title and interest in and to the Preview, including any Intellectual Property Rights that subsist in the Preview. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you.
3.3 You may not use the Preview for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not: (a) copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Preview or any part of the Preview; or (b) load any part of the Preview onto a mobile handset or any other hardware device except a personal computer, combine any part of the Preview with other software, or distribute any software or device incorporating a part of the Preview.
3.4 You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the Preview.
3.5 Use, reproduction and distribution of components of the Preview licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. You agree to remain a licensee in good standing in regard to such open source software licenses under all the rights granted and to refrain from any actions that may terminate, suspend, or breach such rights.
3.6 You agree that the form and nature of the Preview that Google provides may change without prior notice to you and that future versions of the Preview may be incompatible with applications developed on previous versions of the Preview. You agree that Google may stop (permanently or temporarily) providing the Preview (or any features within the Preview) to you or to users generally at Google's sole discretion, without prior notice to you.
3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features.
3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the Preview.
4. Use of the Preview by You
4.1 Google agrees that nothing in the License Agreement gives Google any right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the Preview, including any intellectual property rights that subsist in those applications.
4.2 You agree to use the Preview and write applications only for purposes that are permitted by (a) the License Agreement, and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).
4.3 You agree that if you use the Preview to develop applications, you will protect the privacy and legal rights of users. If users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If users provide you with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, each user has given you permission to do so.
4.4 You agree that you will not engage in any activity with the Preview, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of Google or any third party.
4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so.
4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.
4.7 The Preview is in development, and your testing and feedback are an important part of the development process. By using the Preview, you acknowledge that implementation of some features are still under development and that you should not rely on the Preview having the full functionality of a stable release. You agree not to publicly distribute or ship any application using this Preview as this Preview will no longer be supported after the official Android SDK is released.
5. Your Developer Credentials
5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.
6. Privacy and Information
6.1 In order to continually innovate and improve the Preview, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the Preview are being used and how they are being used. Before any of this information is collected, the Preview will notify you and seek your consent. If you withhold consent, the information will not be collected.
6.2 The data collected is examined in the aggregate to improve the Preview and is maintained in accordance with Google's Privacy Policy located at http://www.google.com/policies/privacy/.
7. Third Party Applications
7.1 If you use the Preview to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.
7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners.
7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party.
8. Using Google APIs
8.1 Google APIs
8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.
8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so.
9. Terminating the License Agreement
9.1 the License Agreement will continue to apply until terminated by either you or Google as set out below.
9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the Preview and any relevant developer credentials.
9.3 Google may at any time, terminate the License Agreement, with or without cause, upon notice to you.
9.4 The License Agreement will automatically terminate without notice or other action upon the earlier of:
(A) when Google ceases to provide the Preview or certain parts of the Preview to users in the country in which you are resident or from which you use the service; and
(B) Google issues a final release version of the Android SDK.
9.5 When the License Agreement is terminated, the license granted to you in the License Agreement will terminate, you will immediately cease all use of the Preview, and the provisions of paragraphs 10, 11, 12 and 14 shall survive indefinitely.
10. DISCLAIMERS
10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE PREVIEW IS AT YOUR SOLE RISK AND THAT THE PREVIEW IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE.
10.2 YOUR USE OF THE PREVIEW AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE PREVIEW IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. WITHOUT LIMITING THE FOREGOING, YOU UNDERSTAND THAT THE PREVIEW IS NOT A STABLE RELEASE AND MAY CONTAIN ERRORS, DEFECTS AND SECURITY VULNERABILITIES THAT CAN RESULT IN SIGNIFICANT DAMAGE, INCLUDING THE COMPLETE, IRRECOVERABLE LOSS OF USE OF YOUR COMPUTER SYSTEM OR OTHER DEVICE.
10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
11. LIMITATION OF LIABILITY
11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.
12. Indemnification
12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys’ fees) arising out of or accruing from (a) your use of the Preview, (b) any application you develop on the Preview that infringes any Intellectual Property Rights of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you of the License Agreement.
13. Changes to the License Agreement
13.1 Google may make changes to the License Agreement as it distributes new versions of the Preview. When these changes are made, Google will make a new version of the License Agreement available on the website where the Preview is made available.
14. General Legal Terms
14.1 the License Agreement constitutes the whole legal agreement between you and Google and governs your use of the Preview (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the Preview.
14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google.
14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable.
14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement.
14.5 EXPORT RESTRICTIONS. THE PREVIEW IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE PREVIEW. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE.
14.6 The License Agreement may not be assigned or transferred by you without the prior written approval of Google, and any attempted assignment without such approval will be void. You shall not delegate your responsibilities or obligations under the License Agreement without the prior written approval of Google.
14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.
</div>

389
docs/html/preview/overview.jd Normal file
View File

@@ -0,0 +1,389 @@
page.title=Program Overview
page.metaDescription=Welcome to the Android M Developer Preview, a program that gives you everything you need to test and optimize your apps for the next version of Android.
page.image=images/cards/card-preview_16-9_2x.png
page.tags="preview", "developer", "android"
@jd:body
<div class="cols" style=
"background-color:#f2daf5; padding: 5px 0;margin-bottom:1em; text-align:center;">
<h3>
Developer Preview 3 is now available
</h3>
<p>Includes final SDK and near-final system images</p>
<div style="margin:auto 1em">
<ul class="dac-section-links">
<li class="dac-section-link">
<a href="{@docRoot}preview/support.html#preview3-notes">
<span class="dac-sprite dac-auto-chevron"></span>
Read the Notes</a>
</li>
<li class="dac-section-link">
<a href="{@docRoot}preview/support.html#preview3-get">
<span class="dac-sprite dac-auto-chevron"></span>
Get the Update</a>
</li>
<li class="dac-section-link">
<a href="https://code.google.com/p/android-developer-preview/">
<span class="dac-sprite dac-auto-chevron"></span>
Report Issues</a>
</li>
</ul>
</div>
</div>
<p>
Welcome to the <strong>Android M Developer Preview</strong>, a program that gives you
everything you need to test and optimize your apps for the next version of
Android. It's free, and you can get started right away just by downloading
the M Developer Preview tools.
</p>
<div style="background-color:#eceff1;padding:1em;">
<div class="wrap">
<div class="cols">
<div class="col-4of12">
<h5>
Hardware and emulator system images
</h5>
<p>
Run and test your apps on Nexus 5, 6, 9, and Player (for TV), as well
as emulator.
</p>
</div>
<div class="col-4of12">
<h5>
Latest platform code
</h5>
<p>
We’ll provide multiple updates during the Preview, so you’ll be testing
against the latest platform changes.
</p>
</div>
<div class="col-4of12">
<h5>
Updates delivered by OTA
</h5>
<p>
You can get updates over-the-air, once you’ve flashed a
device to the initial preview.
</p>
</div>
</div>
<div class="cols">
<div class="col-4of12">
<h5>
New behaviors and capabilities
</h5>
<p>
Start work early to support new platform behaviors such as
the new runtime permissions model and power-saving features.
</p>
</div>
<div class="col-4of12">
<h5>
Priority window for developer-reported issues
</h5>
<p>
During the first several weeks we’ll give priority to developer-reported
issues, so test and give feedback as soon as possible.
</p>
</div>
<div class="col-4of12">
<h5>
Feedback and support
</h5>
<p>
Report issues and give us feedback using our <a href=
"https://code.google.com/p/android-developer-preview/">issue tracker</a>.
Connect with other developers in the <a
href="http://g.co/dev/AndroidMDevPreview">M&nbsp;Developer Community</a>.
</p>
</div>
</div>
</div>
</div>
<!--
<p>
With the M Developer Preview, you'll get an early start on testing your apps,
with enough time to make adjustments before the public platform release later
in the year. We'll provide several updates to the Preview tools in the weeks
ahead, so you can keep in sync with the latest changes as the platform moves
toward launch.
</p>
<img src="{@docRoot}preview/images/m-preview-timeline.png" alt=
"Preview program timeline" id="timeline">
<p>
You can help us improve the platform by <a href=
"https://code.google.com/p/android-developer-preview/">reporting issues</a>
through our feedback channels. This is especially
critical in the first month of the preview, when we’ll be giving priority to
developer-reported issues and feedback.
</p> -->
<h2 id="timeline">
Timeline and updates
</h2>
<img src="{@docRoot}preview/images/m-preview-timeline-crop.png" alt=
"Preview program timeline" id="timeline">
<p>
The M Developer Preview runs from May 28 until the final Android M public release planned for Q3
2015.
</p>
<p>
At key development milestones, we’ll deliver updates for your test devices.
The milestones are
</p>
<ul>
<li>
<strong><a href="{@docRoot}preview/download_mp1.html">Preview&nbsp;1</a></strong> (available).
</li>
<li>
<strong><a href="{@docRoot}preview/download_mp2.html">Preview&nbsp;2</a></strong> (available).
</li>
<li>
<strong><a href="{@docRoot}preview/download.html">Preview&nbsp;3</a></strong>
(final APIs and official Android 6.0 SDK, available).
</li>
</ul>
<p>
These updates culminate in the <strong>official Android 6.0 SDK</strong> (now available),
which lets you build with the final APIs for the new version of Android, as well as
near-final system images to let you test system behaviors and features.
</p>
<p>
As you test and develop on Android M, we strongly recommend <strong>keeping
your development environment up-to-date</strong> as Preview updates are released.
To make the process easier, we'll deliver <strong>updates over-the-air
(OTA)</strong> to devices already flashed to a Preview build, as well as
providing system images that you can download and flash manually.
</p>
<p class="note">
<strong>Note:</strong> Developer Preview 3 includes final APIs and near-final
system images available by both download and OTA. At the full public release of
Android M later in Q3, final system images will be available by download only,
so you'll need to <strong>flash manually</strong> to
your test devices.</strong>
</p>
<p>
We’ll notify you when Preview updates are available via the <a href=
"http://android-developers.blogspot.com/">Android Developers Blog</a>, as
well as this site and the
<a href="http://g.co/dev/AndroidMDevPreview">Android M Developer Community</a>.
</p>
<h2 id="preview_tools">
What’s in the Preview?
</h2>
<p>
The M Developer Preview includes everything you need to test your existing
apps on a variety of screen sizes, network technologies, CPU/GPU chipsets,
and hardware architectures.
</p>
<h4>
SDK tools
</h4>
<p>
You can download these components through the SDK Manager in <a href=
"{@docRoot}sdk/installing/adding-packages.html">Android Studio</a>:
</p>
<ul>
<li><strong>Official Android 6.0 SDK and tools</strong>
</li>
<li>M Developer Preview <strong>emulator system image</strong> (32-bit &amp;
64-bit)
</li>
<li>M Developer Preview <strong>emulator system Image for Android TV</strong>
(32-bit)
</li>
</ul>
<h4>
Hardware system images
</h4>
<p>
You can download these hardware system images for Nexus devices from the
<a href="download.html">Downloads page</a>:
</p>
<ul>
<li>
<strong>Nexus 5</strong> (GSM/LTE) “hammerhead” device system image
</li>
<li>
<strong>Nexus 6</strong> “shamu” device system image
</li>
<li>
<strong>Nexus 9</strong> (Wi-Fi) “volantis” device system image
</li>
<li>
<strong>Nexus Player</strong> (Android TV) “fugu” device system image
</li>
</ul>
<h4>
Documentation and sample code
</h4>
<p>
These documentation resources help you learn about the Preview:
</p>
<ul>
<li>
<a href="setup-sdk.html">Set Up the SDK</a> has step-by-step instructions
for getting started.
</li>
<li>
<a href="{@docRoot}preview/testing/guide.html">Testing Guide</a> and <a href=
"behavior-changes.html">Behavior Changes</a> point you to key areas to test.
</li>
<li>Documentation of new APIs, including an <a href="api-overview.html">API Overview</a>,
downloadable <a href="{@docRoot}preview/download.html#docs">API Reference</a>, and detailed developer guides on
key features such as
<a href="{@docRoot}preview/features/runtime-permissions.html">permissions</a>,
<a href="{@docRoot}preview/backup/index.html">app backup</a>, and others.
</li>
<li>
<a href="{@docRoot}preview/samples.html">Sample code</a> that demonstrates how to support
permissions and other new features.
</li>
<li>
<a href="{@docRoot}preview/support.html#release-notes">Release notes</a> for the current version
of the M Developer Preview, including change notes and diff reports.
</li>
</ul>
<h4>
Support resources
</h4>
<p>
Use these support resources as you test and develop on the M
Developer Preview:
</p>
<ul>
<li><a href="https://code.google.com/p/android-developer-preview/">M
Developer Preview Issue Tracker</a> is your <strong>primary feedback
channel.</strong> You can report bugs, performance issues, and general
feedback through the issue tracker. You can also check for <a
href="https://code.google.com/p/android-developer-preview/wiki/KnownIssues">known issues</a>
and find workaround steps.
</li>
<li>The <a href="http://g.co/dev/AndroidMDevPreview">Android M Developer
Community</a> is a Google+ community where you can <strong>connect with
other developers</strong> working with Android M. You can share
observations or ideas or find answers to questions about Android M.
</li>
</ul>
<h2 id="preview_apis_and_publishing">
Final SDK, targeting, and publishing
</h2>
<p>
<p>With Developer Preview 3, the platform APIs are now official (API level 23) and the
<strong>official Android 6.0 SDK is now available</strong>. We recommend updating your environment
right away through Android Studio. Once you've updated your environment, you can target
the new API level, compile against the new platform, and publish at your convenience
to Google Play (including alpha, beta, or release channels).
<p>If you want to opt out
of compatibility behaviors (which is strongly recommended),
you can target the Android 6.0 platform by setting your app's <code><a href=
"/guide/topics/manifest/uses-sdk-element.html">targetSdkVersion</a></code>
to <code>“23”</code>.
</p>
<p>Before releasing an app that targets API level 23, we strongly
recommend distributing it to a group of testers through the new <a
href="http://android-developers.blogspot.com/2015/07/iterate-faster-on-google-play-with.html">
beta testing features available in the Google Play Developer Console. See the
<a href="https://support.google.com/googleplay/android-developer/answer/3131213">Help
Center article</a> for more information.
</p>
<h2 id="get_started">
How to get started
</h2>
<p>
To get started testing your app with Android M:
</p>
<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. 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>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>
<li>Follow the <a href="https://developers.google.com/android/nexus/images">
flashing instructions</a> to flash the latest M developer preview system image
for Nexus 5, 6, 9, and Player. Once you've flashed your development device,
Preview updates will be delivered through over-the-air (OTA) updates.</a>
</li>
<li>Review the <a href="{@docRoot}reference/packages.html">API
Reference</a> and <a href="{@docRoot}preview/samples.html">M Preview
samples</a> to gain more insight into new API features and how to use them in
your app.
</li>
<li>Join the <a href="http://g.co/dev/AndroidMDevPreview">Android M
Developer Community</a> to get the latest news and connect with other
developers working with the new platform.
</li>
</ol>
<p>
Thank you for your participation in the Android M Developer Preview program!
</p>

126
docs/html/preview/preview_toc.cs Normal file
View File

@@ -0,0 +1,126 @@
<ul id="nav">
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/overview.html"
es-lang="Información general del programa"
ja-lang="プログラム概要"
ko-lang="프로그램 개요"
pt-br-lang="Visão geral do programa"
ru-lang="Обзор программы"
zh-cn-lang="计划概览"
zh-tw-lang="程式總覽">
Program Overview</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/setup-sdk.html"
es-lang="Configurar el SDK de la versión preliminar"
ja-lang="Preview SDK のセットアップ"
ko-lang="미리 보기 SDK 설정하기"
pt-br-lang="Configuração do Preview SDK"
ru-lang="Настройка пакета SDK Preview"
zh-cn-lang="设置预览版 SDK"
zh-tw-lang="設定預覽版 SDK">
Preview SDK</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header"><a href="<?cs var:toroot ?>preview/behavior-changes.html"
es-lang="Cambios en los comportamientos"
ja-lang="動作の変更点"
ko-lang="동작 변경"
pt-br-lang="Mudanças de comportamento"
ru-lang="Изменения в работе"
zh-cn-lang="行为变更"
zh-tw-lang="行為變更">Behavior Changes
</a></div>
<ul>
<li><a href="<?cs var:toroot ?>preview/doze-lite.html"
>Doze Lite</a></li>
<li><a href="<?cs var:toroot ?>preview/background-check.html"
>Background Check</a></li>
<li><a href="<?cs var:toroot ?>preview/direct-boot.html"
>Direct Boot</a></li>
</ul>
</li>
<li class="nav-section">
<div class="nav-section-header"><a href="<?cs var:toroot ?>preview/api-overview.html"
es-lang="Información general de la API"
ja-lang="API の概要"
ko-lang="API 개요"
pt-br-lang="Visão geral da API"
ru-lang="Обзор API-интерфейсов"
zh-cn-lang="API 概览"
zh-tw-lang="API 總覽">New APIs and Features
</a></div>
<ul>
<li><a href="<?cs var:toroot ?>preview/multiwindow.html"
>Multiwindow Support</a></li>
<li><a href="<?cs var:toroot ?>preview/notifications.html"
>Notification Enhancements</a></li>
<li><a href="<?cs var:toroot ?>preview/scoped-access.html"
>Scoped Access to Files &amp; Folders</a></li>
<li><a href="<?cs var:toroot ?>preview/quicksettings.html"
>Quick Settings</a></li>
</ul>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/testing/guide.html"
es-lang="Guía de prueba"
ja-lang="テストガイド"
ko-lang="테스트 가이드"
pt-br-lang="Guia de teste"
ru-lang="Руководство по тестированию"
zh-cn-lang="测试指南"
zh-tw-lang="測試指南">
Testing Guide</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/samples.html"
es-lang="Ejemplos"
ja-lang="サンプル"
ko-lang="샘플"
pt-br-lang="Exemplos"
ru-lang="Примеры"
zh-cn-lang="示例"
zh-tw-lang="範例">
Samples</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/ota.html"
>Device Image Downloads</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/download.html"
>OTA Device Updates</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/support.html">
Support & Release Notes</a></div>
</li>
<li class="nav-section">
<div class="nav-section-header empty"><a href="<?cs var:toroot ?>preview/license.html"
es-lang="Contrato de licencia"
ja-lang="使用許諾契約"
ko-lang="라이선스 계약"
pt-br-lang="Contrato de licença"
ru-lang="Лицензионное соглашение"
zh-cn-lang="许可协议"
zh-tw-lang="授權協議">
License Agreement</a></div>
</li>
</ul>

70
docs/html/preview/samples.jd Normal file
View File

@@ -0,0 +1,70 @@
page.title=Samples
page.image=images/cards/samples-new_2x.png
@jd:body
<p>
The following code samples are provided for the M Developer Preview. To download
the samples in Android Studio, select the <b>File > Import Samples</b> menu option.
</p>
<p class="note">
<strong>Note:</strong> These downloadable projects are designed
for use with Gradle and Android Studio.
</p>
<h3 id="RuntimePermissions">Runtime Permissions</h3>
<p>
Android M changes the way system permissions work. Users are asked to approve permission
requests at runtime instead of during installation. This sample shows how to request these
permissions.
</p>
<p><a href="https://github.com/googlesamples/android-RuntimePermissions">Get it on GitHub</a></p>
<h3 id="ConfirmCredentials">Confirm Credential</h3>
<p>
This sample demonstrates how to use device credentials as an authentication method in your app.
</p>
<p><a href="https://github.com/googlesamples/android-ConfirmCredential">Get it on
GitHub</a></p>
<h3 id="FingerprintDialog">Fingerprint Dialog</h3>
<p>
This sample demonstrates how to recognize registered fingerprints to authenticate the user
in your app.
</p>
<p><a href="https://github.com/googlesamples/android-FingerprintDialog">Get it on GitHub</a></p>
<h3 id="AutomaticBackup">Auto Backup for Apps</h3>
<p>
Android M introduces automatic backup for app settings. This sample demonstrates how to add
filtering rules to an app in order to manage settings backup.
</p>
<p><a href="https://github.com/googlesamples/android-AutoBackupForApps">Get it on GitHub</a></p>
<h3 id="CameraRaw">Camera 2 Raw</h3>
<p>
Demonstrates how to use the <code>Camera2</code> API to capture RAW camera buffers and save
them as <code>DNG</code> files.
</p>
<p><a href="https://github.com/googlesamples/android-Camera2Raw">Get it on GitHub</a></p>
<h3 id="ActiveNotification">Active Notification</h3>
<p>
This sample demonstrates how the
<a href="{@docRoot}reference/android/app/NotificationManager.html"><code>NotificationManager</code></a>
can tell you how many notifications your app is currently showing.
</p>
<p><a href="https://github.com/googlesamples/android-ActiveNotifications">Get it on GitHub</a></p>

178
docs/html/preview/setup-sdk.jd Normal file
View File

@@ -0,0 +1,178 @@
page.title=Set Up the SDK
page.image=images/cards/card-set-up_16-9_2x.png
@jd:body
<div id="qv-wrapper">
<div id="qv">
<h2>In this document</h2>
<ol>
<li><a href="#get-as13">Get Android Studio 1.3</a></li>
<li><a href="#get-sdk">Get the Android 6.0 SDK</a></li>
<li><a href="#create-update">Create or Update a Project</a></li>
<li><a href="#setup-test">Set Up for Testing</a></li>
</ol>
</div>
</div>
<p>With Developer Preview 3, the <strong>official Android 6.0 SDK is now available</strong> from the Android SDK
Manager. This document assumes that you are familiar with Android app development, such
as using the Android SDK Manager and creating projects. If you are new to
Android, see <a href="{@docRoot}training/basics/firstapp/index.html">Building Your First
App</a> training lesson first.</p>
<h2 id="get-as13">Get Android Studio 1.3</h2>
<p>
It is highly recommended that you install the Android Studio 1.3 to work best with
the Android 6.0 SDK. Please update your Android Studio installation to version 1.3 or
higher, or follow the instructions for
<a href="{@docRoot}sdk/installing/index.html?pkg=studio">Installing Android Studio</a>.
</p>
<h2 id="get-sdk">Get the Android 6.0 SDK</h2>
<p>To add the Android 6.0 SDK components to your development environment:</p>
<ol>
<li>Launch Android Studio 1.3 or higher.
</li>
<li>Open the <strong>Settings</strong> window (on Windows, you can do this
by choosing <strong>File &gt; Settings</strong>). Choose the
<strong>Appearance &amp; Behavior &gt; System
Settings &gt; Updates</strong> panel.
<p class="aside">On Mac OS X, you can find the <strong>Appearance &amp;
Behavior</strong> panel
in Android Studio's <strong>Preferences</strong> window.</p>
</li>
<li>On the <strong>Updates</strong> panel, choose the option for
<strong>Automatically check updates for Android SDK: Preview Channel</strong>.
</li>
<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 6.0</strong>.
</li>
<li>In the <strong>Tools</strong> section, select the latest Android <strong>
SDK Tools</strong>, <strong>Platform-tools</strong>, and
<strong>Build-tools</strong>.
</li>
<li>Click <strong>Install packages</strong> and accept the licensing
agreement for all of the packages.
</li>
<li>Verify that the Android 6.0 SDK is installed by opening the <strong>
Settings</strong> window and choosing the <strong>Appearance &amp; Behavior
&gt; System Settings &gt; Android SDK</strong> panel.</li>
<li>On the <strong>Android SDK</strong> panel, choose
the <strong>SDK Platforms</strong> tab. <strong>Android 6.0</strong> should be listed as <em>Installed</em>. Also, open the
<strong>SDK Tools</strong> tab to verify that the latest tools are
installed.
</li>
</ol>
<p>After completing these steps, the preview components are available in your development
environment. </p>
<h2 id="create-update">Create or Update a Project</h2>
<p>
In order to use the preview APIs, you must create or update a development project to use
the preview components.
</p>
<h3 id="create">Create a new project</h3>
<p>
We recommend using Android Studio to create a project with the preview. Follow the steps
described in <a href="{@docRoot}sdk/installing/create-project.html">Creating a Project</a>
until you arrive at the <em>Form Factors</em> screen in the project wizard. Then perform
the following steps to create a project configured for the preview.
</p>
<ul>
<li>Check <strong>Phone and Tablet</strong>.</li>
<li>Select <strong>API 23: Android 6.0 (Marshmallow)</strong> in <strong>Minimum
SDK</strong>.</li>
</ul>
<h3 id="update">Update an existing project</h3>
<p>
For existing projects, if you are using Android 6.0 APIs (API level 23) you must
modify the project configuration. In your development environment, open the
<code>build.gradle</code> file for your module and
set these values as follows:
</p>
<ul>
<li><code>compileSdkVersion</code> is set to <code>'23'</code></li>
<li><code>targetSdkVersion</code> is set to <code>'23'</code></li>
</ul>
<h2 id="setup-test">Set Up for Testing</h2>
<p>
Testing an app with the preview requires that you have a device or virtual device configured with
the preview version of the platform. If you have a compatible device, you can install the preview
platform for testing. Otherwise, you can configure a virtual device for testing.
</p>
<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
system image on these devices for testing your app.
You can set up a virtual device with the preview version of the platform from within Android Studio
using the Android Virtual Device Manager tool.
</p>
<p class="caution">
<strong>Important:</strong> Installing a preview image on a device <em>removes all data from
it</em>, so you should backup any data before installing a preview image.
</p>
<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
using the Android Virtual Device Manager tool.
</p>
<p>To create an AVD with the AVD Manager:</p>
<ol>
<li>Install the Preview SDK in your development environment, as described
in <a href="{@docRoot}preview/setup-sdk.html">Setting Up the Preview
SDK.</a></li>
<li>Follow the steps in
<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 Android TV</li>
<li><strong>Target:</strong>
Android M (Preview) - API Level M</li>
<li><strong>ABI:</strong> x86</li>
</ul>
</li>
</ol>
<p>
For more information about creating virtual devices for testing, see <a href=
"{@docRoot}tools/devices/index.html">Managing Virtual Devices</a>.
</p>

533
docs/html/preview/support.jd Normal file
View File

@@ -0,0 +1,533 @@
page.title=Support and Release Notes
page.tags="preview", "developer preview"
page.image=images/cards/card-support_16-9_2x.png
@jd:body
<div class="cols" style=
"background-color:#f2daf5; padding: 5px 0;margin-bottom:1em; text-align:center;">
<h3>
Developer Preview 3 is now available
</h3>
<p>Includes final SDK and near-final system images</p>
<div style="margin:auto 1em">
<ul class="dac-section-links">
<li class="dac-section-link">
<a href="#preview3-notes">
<span class="dac-sprite dac-auto-chevron"></span>
Read the Notes</a>
</li>
<li class="dac-section-link">
<a href="#preview3-get">
<span class="dac-sprite dac-auto-chevron"></span>
Get the Update</a>
</li>
<li class="dac-section-link">
<a href="https://code.google.com/p/android-developer-preview/">
<span class="dac-sprite dac-auto-chevron"></span>
Report Issues</a>
</li>
</ul>
</div>
</div>
<p>
Two primary support channels are available to you when developing and testing
with the Android M Developer Preview. If you've encountered bugs or have
feedback about the M Developer Preview, you can <a href=
"https://code.google.com/p/android-developer-preview/">create an issue</a> on
our issue tracker. We'll triage the issue for further review and provide
updates as needed.
</p>
<p>
To discuss issues or ideas with other developers working with Android M, join
the <a href="http://g.co/dev/AndroidMDevPreview">M Developer Preview Google+
community</a>.
</p>
<h2 id="preview3-notes">
Developer Preview 3
</h2>
<div class="wrap">
<div class="cols">
<div class="col-9of16">
<p>
<em>Date: August 2015<br>
Build: MPA44I<br>
Hardware support: Nexus 5, 6, 9, Player<br>
Emulator support: x86 &amp; ARM 32/64-bit<br>
Google Play services: 7.8</em>
</p>
</div>
</div>
</div>
<p>
Developer Preview 3 is the <strong>final incremental update</strong>
to the Android M preview platform that was originally released in May 2015.
The update includes <strong>final APIs and the official Android 6.0 SDK</strong>,
as well as near-final system images for testing your apps. The
updated system images bring a variety of fixes and enhancements across
the system, including those related to issues reported by developers
through the external issue tracker.
</p>
<p>
If you are currently developing or testing on Android M, you should <strong>update
your environment</strong> as soon as possible, so that
you can begin <strong>final compatibility testing</strong> in preparation for
the public release to device manufacturers later this year.</p>
<p class="important">Updating to the Android 6.0 SDK and the latest
system images 3 ensures that you are building against final
platform APIs in <strong>API level 23</strong> and testing
against final behaviors. If you are just getting started,
follow the instructions in <a href=
"/preview/setup-sdk.html">Set up the Preview SDK</a>.
</p>
<h3>
What's included
</h3>
<p>
Developer Preview 3 includes the official Android 6.0
SDK as well as updated preview system images, documentation,
and samples for developing against the Android 6.0
development platform.
</p>
<ul>
<li>
<strong>SDK platform</strong> and <strong>system images</strong> (Nexus and
emulator) for building and testing. You can download the Android 6.0 SDK and tools from
the SDK Manager, and the system images are available by over-the-air (OTA)
update or download (see below).
</li>
<li>
<strong>Updated documentation</strong>. The <a href=
"{@docRoot}preview/behavior-changes.html">Behavior Changes</a>, <a href=
"{@docRoot}preview/api-overview.html">API Overview</a>, and <a href=
"{@docRoot}preview/features/runtime-permissions.html">Permissions</a> documents have
been updated to reflect the latest changes in the platform. An updated
<a href="/preview/download.html">Developer Documentation download
package</a> is available, including full reference docs and API diff
reports. Reference documentation is also now <a
href="{@docRoot}reference/packages.html">available online</a>.
</li>
<li>
<strong>Translations</strong> of the documentation are available. Use
the language selector at the bottom right corner of any page to switch
languages. Note that some of the translated docs are not yet updated for
Developer Preview 3.
</li>
<li>The <a href="{@docRoot}preview/samples.html">Android M code samples</a> are also
updated to account for API and behavior changes:
<ul>
<li>
<a href=
"https://github.com/googlesamples/android-RuntimePermissions">RuntimePermissions</a>
and <a href=
"https://github.com/googlesamples/android-RuntimePermissionsBasic">RuntimePermissionsBasic</a>
are updated to reflect latest permissions API changes, including
<code>shouldShowRequestPermissionRationale()</code>.
</li>
<li>
Other samples are updated to support runtime permissions.
</li>
</ul>
</li>
</ul>
<h3 id="changes">
Key changes
</h3>
<ul>
<li>General
<ul>
<li>Updated the Fingerprint API to enables better error reporting,
better fingerprint enrollment experience, and enumeration support for greater
reliability.</li>
<li>Modified app access to BLE and Wi-Fi scans to require the location permisssion when they
target Android 6.0 (API level 23) or higher. Apps targeting API 22 or earlier can
still perform BTLE and WiFi scans, but only when they are in the foreground. While in the background, those apps will get no results from BTLE and WiFi scans.</li>
</ul>
</li>
<li>Permission changes
<ul>
<li>Updated the user interface for permissions and enhanced some of the permissions
behaviors.</li>
<li>The {@link android.Manifest.permission#GET_ACCOUNTS} permission is now a member of the
{@link android.Manifest.permission_group#CONTACTS} permission group and it has a
{@code android:protectionLevel} of {@code dangerous}. This change means that when
targeting Android 6.0 (API level 23), you must check for and request this permission if
your app requires it.
</li>
<li>The {@code android.permission.READ_PROFILE} and {@code android.permission.WRITE_PROFILE}
permissions have been removed from the {@link android.Manifest.permission_group#CONTACTS}
permission group.
</li>
</ul>
</li>
</ul>
<p>
For a complete list of changes, including renamed and removed APIs, see the API Diff report for
<a href="{@docRoot}sdk/api_diff/23/changes.html">API level 22 to 23</a>.
</p>
<h3 id="ki">
Known issues
</h3>
<ul>
<li>General issues:
<ul>
<li>On LTE devices, including Nexus 9, GPS is not functioning properly, which may
interfere with navigation services.
</li>
<li>During Hangouts calls, users may experience distorted or low audio on some devices.
</li>
<li>The Google Apps Device Policy app bundled with MPA44G is unable to set up an Android for
Work Profile, so you cannot create a new Work Profile with that version of the app. This issue is
resolved in the Google Apps Device Policy app bundled with MPA44I. Other apps that provide Android
for Work functionality remain unaffected on either build.
</li>
</ul>
</li>
</ul>
<p>
For a complete list of reported issues, please refer to the <a href=
"https://code.google.com/p/android/issues/list">open issues list</a> on the
Developer Preview <a href=
"https://code.google.com/p/android-developer-preview/">issue tracker</a>.
</p>
<h3 id="preview3-get">
Get Developer Preview 3
</h3>
<p>
You can download the official Android 6.0 SDK platform and
Developer Preview 3 emulator images from the SDK Manager.
</p>
<p>
Developer Preview 3 system images for supported Nexus devices are available
by download and by over-the-air (OTA) update. The OTA update is available
only to supported devices that are currently running a Developer Preview build.
If your device is running a Developer Preview build, you should automatically receive
the OTA update within a few days of availability.
</p>
<p>
For instructions on how to download and flash your device to the latest Developer
Preview, see the links and instructions on the <a href=
"{@docRoot}preview/download.html">Downloads</a> page.
</p>
<p>
For instructions on how to start developing and testing with Android 6.0
Marshmallow, read <a href="{@docRoot}preview/setup-sdk.html">Setting
up the SDK</a>.
</p>
<h2 id="preview2-notes">
Developer Preview 2
</h2>
<div class="wrap">
<div class="cols">
<div class="col-9of16">
<p>
<em>Date: July 2015<br>
Builds: MPZ79M (Nexus 5, 6, 9), MPZ79N (Nexus Player)<br>
Hardware support: Nexus 5, 6, 9, Player<br>
Emulator support: x86 &amp; ARM 32/64-bit<br>
Google Play services: 7.6</em>
</p>
</div>
</div>
</div>
<p>
Android M Developer Preview 2 is an <strong>incremental update</strong> to
the Android M preview platform that was originally released in May 2015. The
update includes a variety of enhancements and bug fixes made across the
system, including those related to issues reported by developers through the
external issue tracker.
</p>
<p>
If you are currently developing or testing on Android M, you should
<strong>update your environment</strong> to Developer Preview 2 as soon as
possible. This ensures that you are building with the latest platform APIs
and testing against the latest behaviors. If you are just getting started
with the Android M Developer Preview SDK, follow the instructions in <a href=
"{@docRoot}preview/setup-sdk.html">Set up the Preview SDK</a>, then update your
environment for Developer Preview 2.
</p>
<h3>
What's included
</h3>
<p>
Developer Preview 2 includes an updated SDK with system images,
documentation, and samples for developing against the latest Android M
platform.
</p>
<ul>
<li>
<strong>SDK platform</strong> and <strong>system images</strong> (Nexus and
emulator) for building and testing. You can download the updated tools from
the SDK Manager, and the system images are available by over-the-air (OTA)
update or download (see below).
</li>
<li>
<strong>Updated documentation</strong>. The <a href=
"{@docRoot}preview/behavior-changes.html">Behavior Changes</a>, <a href=
"{@docRoot}preview/api-overview.html">API Overview</a>, and <a href=
"{@docRoot}preview/features/runtime-permissions.html">Permissions</a> documents have
been updated to reflect the latest changes in the platform. An updated
<a href="{@docRoot}preview/download.html">Developer Documentation download
package</a> is available, including full reference docs and API diff
reports.
</li>
<li>
<strong>Translations</strong> of the documentation are now available. Use
the language selector at the bottom right corner of any page to switch
languages. Note that some of the translated docs are not yet updated for
Developer Preview 2 (coming soon).
</li>
<li>The <a href="{@docRoot}preview/samples.html">Android M code samples</a> are also
updated to account for API and behavior changes:
<ul>
<li>
<a href=
"https://github.com/googlesamples/android-RuntimePermissions">RuntimePermissions</a>
/ <a href=
"https://github.com/googlesamples/android-RuntimePermissionsBasic">RuntimePermissionsBasic</a>
are updated to reflect latest permissions API changes, including
<code>shouldShowRequestPermissionRationale()</code>.
</li>
<li>
<a href=
"https://github.com/googlesamples/android-FingerprintDialog">FingerprintDialog</a>
adds a flow to ask for passwords when new fingerprints are added as
well as a preference if the app will use fingerprints as a method of
authentication.
</li>
</ul>
</li>
</ul>
<h3 id="changes-p2">
Key changes
</h3>
<ul>
<li>Permissions changes
<ul>
<li>The <code>android.permission.USE_FINGERPRINT</code> permission now
has "normal" protection level, so it is no longer necessary to request
this permission directly from the user. The <code>USE_FINGERPRINT</code>
permission enables fingerprints to be enabled for authentication, but
does not give the requesting app access to the enrollment/fingerprint
administration flow.
</li>
<li>The <code>android.permission.WRITE_EXTERNAL_STORAGE</code> permission
has protection level "dangerous", meaning that apps wanting to write to
external storage will need to request permission from the user at
runtime. Both <code>READ_EXTERNAL_STORAGE</code> and
<code>WRITE_EXTERNAL_STORAGE</code> are members of the
<code>STORAGE</code> permission group.
</li>
<li>Remote Bluetooth/Wi-Fi MAC's now require either the
<code>android.permission.ACCESS_COARSE_LOCATION</code> or
<code>android.permission.ACCESS_FINE_LOCATION</code> permission.
</li>
<li>Some accounts and identity permissions are moved to
<code>CONTACTS</code> permissions group and others are removed or granted
based on account type. In particular,
<code>android.permission.USE_CREDENTIALS</code>,
<code>android.permission.MANAGE_ACCOUNTS</code>, and
<code>android.permission.AUTHENTICATE_ACCOUNTS</code> are ungrouped
pending further changes in a later release.
</li>
<li>The Wi-Fi permissions
<code>android.permission.CHANGE_WIFI_STATE</code>,
<code>android.permission.CHANGE_WIMAX_STATE</code>, and
<code>android.permission.CHANGE_WIFI_MULTICAST_STATE</code> now have
protection level "normal".
</li>
<li>The Bluetooth permissions <code>android.permission.BLUETOOTH</code>
and <code>android.permission.BLUETOOTH_ADMIN</code> now have protection
level "normal".
</li>
<li>Bookmarks and subscribed feeds permissions are removed.
</li>
<li>Apps included in the system image are no longer granted dangerous
permissions automatically. All apps should check for and request
permissions at runtime.
</li>
<li>Introduces the utility method
<code>Activity.shouldShowRequestPermissionRationale(String)</code>, which
lets your app see whether users have previously rejected a permission
request. This lets you know that your app should explain the the user why
it needs that permission. For more information see the <a href=
"{@docRoot}preview/features/runtime-permissions.html#explain-need">Permissions</a>
developer guide.
</li>
</ul>
</li>
<li>Other changes
<ul>
<li>The <code>android.app.AssistContent</code> and
<code>android.app.AssistStructure</code> classes are moved into a new
package, <code>android.app.assist</code>.
</li>
<li>Bluetooth Stylus APIs are updated and include new callback events.
The <code>View.OnStylusButtonPressListener</code> class is renamed to
<code>View.OnContextClickListener</code> and
<code>GestureDetector.OnStylusButtonPressListener</code> class to <code>
GestureDetector.OnContextClickListener</code>.
</li>
</ul>
</li>
</ul>
<p>
For a complete list of changes, including renamed and removed APIs, please
refer to the API Diff Reports included in the <a href=
"{@docRoot}preview/download.html#docs">Developer Documentation download package</a>.
</p>
<h3 id="ki-p2">
Known issues
</h3>
<ul>
<li>General issues:
<ul>
<li>The system Messenger app crashes on the 64-bit emulator.</li>
<li>After updating to Developer Preview 2, Contacts sync experiences
intermittent issues. The workaround is to clear and re-sync Contact Storage
data after update. To clear data, go to <strong>Settings &gt; Apps &gt; Show
system &gt; Contacts Storage</strong>. Select "Storage" and then
<strong>Clear data</strong>.</li>
<li>In YouTube app, it's not possible to share a video. The share window is
blank.</li>
<li>The bundled Google Apps Device Policy app included in Developer Preview 2 is unable to
properly set up an Android for Work Profile, so you cannot create a new Work Profile with this
app after you update. This issue is specific to the Google Apps Device Policy app, and not the
Android for Work platform (or our partner EMM providers). As a workaround for users of the
Google Apps Device Policy app, be sure to create a Work Profile in Developer Preview 1 before
updating to Developer Preview 2.
</li>
</ul>
</li>
<li>Issues specific to MPZ79N on Nexus Player:
<ul>
<li>Bluetooth share crashes after clearing data. Please <strong>do not
clear app data for system services</strong>, otherwise you will need to Factory
Reset your device</li>
<li>Remote control can experience intermittent connectivity issues. </li>
<li>Movies show black screen with some ANRs on exiting the video.</li>
<li>In YouTube app, lower-resolution videos have a green bar at the top
and some color-ghosting</li>
</li>
</ul>
</li>
</ul>
<p>
For a complete list of reported issues, please refer to the <a href=
"https://code.google.com/p/android/issues/list">open issues list</a> on the
Developer Preview <a href=
"https://code.google.com/p/android-developer-preview/">issue tracker</a>.
</p>
<h3 id="preview2-get">
Get Developer Preview 2
</h3>
<p>
You can download the Developer Preview 2 platform and emulator images from
the SDK Manager.
</p>
<p>
Developer Preview 2 system images for supported Nexus devices are available
by download and by over-the-air (OTA) update. The OTA update is available
only to supported devices that are currently running Developer Preview 1. If
your devices are running Developer Preview 1, you should automatically receive
the OTA update within a few days of availability.
</p>
<p>
If you are just getting started with Android M Developer Preview, and want
to receive Developer Preview 2 via OTA, download the appropriate
Developer Preview 1 <a href="{@docRoot}preview/download_mp1.html#images">
system image</a>, and flash it to your device. Then,
leave the device powered on for several hours. It registers with the
OTA service, and receives Developer Preview 2 by OTA.
</p>
<p>
For instructions on how to download and flash your device to the Developer
Preview, see the links and instructions on the <a href=
"{@docRoot}preview/download.html">Downloads</a> page.
</p>
<p>
For instructions on how to start developing and testing with Android M, read
<a href="{@docRoot}preview/setup-sdk.html">Setting up the SDK</a>.
</p>
<h2 id="preview1-notes">
Developer Preview 1
</h2>
<div class="wrap">
<div class="cols">
<div class="col-6of12">
<p>
<em>Date: May 2015<br>
Build: MPZ44Q<br>
Hardware support: Nexus 5, 6, 9, Player<br>
Emulator support: x86 &amp; ARM (32/64-bit)<br>
Google Play services: 7.5</em>
</p>
</div>
</div>
</div>
<p>
Initial release.
</p>