diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index 5ab4b89d308c4..d1639aab7893b 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -14,8 +14,7 @@ page.image=images/cards/card-key-changes_16-9_2x.png
    -
  1. Auto Backup for Apps
    2. -
  2. Notifications
    3. +
  3. Automatic App Data Backup
  4. Authentication

API Differences

    -
  1. API level 22 to M »
    2. +
  2. API level 22 to M Preview »
@@ -55,40 +67,24 @@ methods that do not yet have reference material available on developer.android.com. These API elements are formatted in {@code code style} in this document (without hyperlinks). For the preliminary API documentation for these elements, download the -preview reference.

+href="{@docRoot}preview/download.html#docs"> preview reference.

Important behavior changes

If you have previously published an app for Android, be aware that your app might be affected -by changes in M.

+by changes in the platform.

-

Please see Behavior Changes for complete information.

+

Please see Behavior Changes for complete information.

-

Auto Backup for Apps

+

Automatic App Data Backup

The system now performs automatic full data backup and restore for apps. This behavior is -enabled by default for apps targeting M; you do not need to add any additional code. If users -delete their Google account, 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 the App Backup for Apps guide.

- -

Notifications

-

M adds the following API changes for notifications:

- +enabled by default for apps targeting M Preview; 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 +Automatic App Data Backup.

Authentication

-

The M release offers new APIs to let you authenticate users by using their fingerprint scans on +

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 Android Keystore system.

@@ -97,17 +93,15 @@ the Android Keystore system<

To authenticate users via fingerprint scan, get an instance of the new {@code android.hardware.fingerprint.FingerprintManager} class and call the -{@code FingerprintManager.authenticate()} method. Your app must be running on a device with a -fingerprint sensor. You must implement the user interface for the fingerprint -authentication flow on your app, and use the standard fingerprint Android icon in your UI. -If you are developing multiple apps that use fingerprint authentication, note that each app must -authenticate the user’s fingerprint independently. +{@code FingerprintManager.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 +sample app. If you are developing multiple apps that use fingerprint +authentication, note that each app must authenticate the user’s fingerprint independently.

- -

To use this feature in your app, first add the {@code USE_FINGERPRINT} permission in your manifest.

@@ -116,34 +110,34 @@ manifest.

android:name="android.permission.USE_FINGERPRINT" /> -

The following snippet shows how you might listen for fingerprint events in your -{@code FingerprintManager.AuthenticationCallback} implementation.

+ -
-// Call this to start listening for fingerprint events
-public void startListening(FingerprintManager.CryptoObject cryptoObject) {
-    if (!isFingerprintAuthAvailable()) {
-        return;
-    }
-    mCancellationSignal = new CancellationSignal();
-    mSelfCancelled = false;
-    mFingerprintManager.authenticate(cryptoObject,
-            mCancellationSignal, this, 0 /* flags */);
-    // Icon to display when prompting users to start a fingerprint scan
-    mIcon.setImageResource(R.drawable.ic_fp_40px);
-}
+
To see an app implementation of fingerprint authentication, refer to the
+
+  Fingerprint Dialog sample.

 
-// Helper method to check if the device supports fingerprint
-// scanning and if the user has enrolled at least one fingerprint.
-public boolean isFingerprintAuthAvailable() {
-    return mFingerprintManager.isHardwareDetected()
-        && mFingerprintManager.hasEnrolledFingerprints();
-}
+
If you are testing this feature, follow these steps:

+
    
+
  1. Enroll a new fingerprint in the emulator by going to
+Settings > Security > Fingerprint, then follow the enrollment instructions.
    2. 
+
  2. Install Android SDK Tools Revision 24.3, if you have not done so.
    3. 
+
  3. 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.
+
    +adb -e emu finger touch <finger_id>
 
    
+
    On Windows, you may have to run {@code telnet 127.0.0.1 <emulator-id>} followed by
+  {@code finger touch <finger_id>}.
+
    
+
    4. 
+

 
 
Confirm Credentials

 
Your app can authenticate users based on how recently they last unlocked their device. You can
-use the same public or secret key to authenticate users into multiple apps. This feature frees
+use the same public or secret key to authenticate users. 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.

 
@@ -152,46 +146,14 @@ generating or importing. To set the constraints for using a key, use the
 {@code android.security.KeyPairGeneratorSpec.Builder} and
 {@code android.security.KeyGeneratorSpec.Builder} classes for public key pairs and secret keys
 respectively. If you are importing keys, use the {@link android.security.KeyStoreParameter.Builder}
-class to set your constraints.

+class to set your constraints. You can use the
+{@link android.app.KeyguardManager#createConfirmDeviceCredentialIntent(java.lang.CharSequence, java.lang.CharSequence) createConfirmDeviceCredentialIntent()}
+method to re-authenticate the user within your app if the timeout expired.
+

 
-
The following example shows how you might create a symmetric key in the Keystore which can only be
-used if the user has successfully unlocked the device within the last 5 minutes.

-
-
-private void createKey() {
-    // Generate a key to decrypt payment credentials, tokens, etc.
-    // This will most likely be a registration step for the user when
-    // they are setting up your app.
-    try {
-        KeyStore ks = KeyStore.getInstance("AndroidKeyStore");
-        ks.load(null);
-        KeyGenerator keyGenerator = KeyGenerator.getInstance("AES",
-                "AndroidKeyStore");
-        keyGenerator.init(new KeyGeneratorSpec.Builder(this)
-                // Alias of the entry in Android KeyStore where the key will appear
-                .setAlias(KEY_NAME)
-                // Key use constraints
-                .setPurposes(KeyStoreKeyProperties.Purpose.ENCRYPT
-                    | KeyStoreKeyProperties.Purpose.DECRYPT)
-                .setBlockModes("CBC")
-                .setUserAuthenticationRequired(true)
-                // Require that the user has unlocked in the last 5 minutes
-                .setUserAuthenticationValidityDurationSeconds(5 * 60)
-                .setEncryptionPaddings("PKCS7Padding")
-                .build());
-        keyGenerator.generateKey();
-    } catch (NoSuchAlgorithmException | NoSuchProviderException
-            | InvalidAlgorithmParameterException | KeyStoreException
-            | CertificateException | IOException e) {
-          throw new RuntimeException(e);
-    }
-}
-

-
-
To determine the last time users logged into their account, call the
-{@code android.accounts.AccountManager.confirmCredentials()} method. If the call is successful, the
-method returns an bundle that includes a {@code KEY_LAST_AUTHENTICATED_TIME} value which indicates
-the last time, in milliseconds, that the credential for that account was validated or created.

+
To see an app implementation of this feature, refer to the
+
+  Confirm Device Credentials sample.

 
 
Direct Share

 
@@ -199,7 +161,7 @@ the last time, in milliseconds, that the credential for that account was validat
 srcset="{@docRoot}preview/images/direct-share-screen.png 1x, preview/images/direct-share-screen_2x.png 2x"
 style="float:right; margin:0 0 20px 30px" width="312" height="385" />
 
-
This release provides you with APIs to makes sharing intuitive and quick for users. You can now
+
This preview provides you with APIs to makes sharing intuitive and quick for users. You can now
 define deep links that target a specific activity in your app. These deep links are
 exposed to users via the Share menu. This feature allows users to share content to
 targets, such as contacts, within other apps. For example, the deep link might launch an
@@ -214,9 +176,6 @@ friend or community in that app.

 {@code SERVICE_INTERFACE} action.

 
The following example shows how you might declare the {@code ChooserTargetService} in your
 manifest.

-

-

-

 
 <service android:name=".ChooserTargetService"
         android:label="@string/service_name"
@@ -243,37 +202,142 @@ manifest.

         android:value=".ChooserTargetService" />
 </activity>
 

+
To see an app implementation of this feature, refer to the
+
+  Deep Link Sharing sample.

+
 
 
Voice Interactions

 

-This release provides a new voice interaction API which, together with
+This preview provides a new voice interaction API which, together with
 Voice Actions,
 allows you to build conversational voice experiences into your apps. Call the
 {@code android.app.Activity.isVoiceInteraction()} method to determine if your activity was
 started in response to a voice action. If so, your app can use the
 {@code android.app.VoiceInteractor} class to request a voice confirmation from the user, select
-from a list of options, and more.

-
To learn more about implementing voice actions, see the voice interaction API
+from a list of options, and more. To learn more about implementing voice actions, see the
 guide.
+class="external-link">Voice Actions developer site.
 

 
+
Assist API

+

+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 Home button.

+
The platform passes the current context to the assistant. 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 {@code android.app.Activity.AssistContent} class.

+
+
To provide the assistant with additional context from your app, follow these steps:

+
+
    
+
  1. Implement the {@link android.app.Application.OnProvideAssistDataListener} interface.
    2. 
+
  2. Register this listener by using
+{@link android.app.Application#registerOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener) registerOnProvideAssistDataListener()}.
    3. 
+
  3. In order to provide activity-specific contextual information, override the
+{@link android.app.Activity#onProvideAssistData(android.os.Bundle) onProvideAssistData()}
+callback and, optionally, the new {@code Activity.onProvideAssistContent()} callback.
+

+
+
Notifications

+
This preview adds the following API changes for notifications:

+
+
 
Bluetooth Stylus Support

-
The M release provides improved support for user input using a Bluetooth stylus. If the user
-touches a stylus with a button on the screen of your app, the
-{@link android.view.MotionEvent#getToolType(int) getTooltype()} method now returns
-{@code TOOL_TYPE_STYLUS}. The {@link android.view.MotionEvent#getButtonState() getButtonState()}
-method returns {@link android.view.MotionEvent#BUTTON_SECONDARY} when the user
+
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 the new
+{@code View.onStylusButtonPressListener} and {@code GestureDetector.OnStylusButtonPressListener}
+callbacks in your activity.

+
+
Use the {@link android.view.MotionEvent} methods and constants to detect stylus button
+interactions:

+
 
-
New Audio Features

+
Improved Bluetooth Low Energy Scanning

+

+If your app performs performs Bluetooth Low Energy scans, you can use the new
+{@code android.bluetooth.le.ScanSettings.Builder.setCallbackType()} method to specify that
+you want callbacks to only be notified when an advertisement packet matching the set
+{@link android.bluetooth.le.ScanFilter} is first found, and when it is not seen for a period of
+time. This approach to scanning is more power-efficient than what’s provided in the previous
+platform version.
+

 
-
This release adds enhancements to audio processing on Android, including: 

+
Hotspot 2.0 Release 1 Support

+

+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 {@code setPlmn()} and
+{@code setRealm()}. In the {@link android.net.wifi.WifiConfiguration} object, you can set the
+{@link android.net.wifi.WifiConfiguration#FQDN} and the {@code providerFriendlyName} fields.
+The new {@code ScanResult.PasspointNetwork} property indicates if a detected
+network represents a Hotspot 2.0 access point.
+

+
+
4K Display Mode

+
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
+{@code 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
+{@code Display.Mode.getPhysicalWidth()} method returns may differ from the logical
+resolution reported by {@link android.view.Display#getSize(android.graphics.Point) getSize()}.

+
+
You can request the system to change the physical resolution in your app as it runs, by setting
+the {@code 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.

+
+
To test the new 4K display mode, simulate a secondary display of a larger resolution using the
+Developer Options settings.

+
+
Themeable ColorStateLists

+
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 {@code Context.getColorStateList()} or
+{@code Context.getColor()} methods instead. These methods are also available in the
+v4 appcompat library via {@link android.support.v4.content.ContextCompat}.

+
+
Audio Features

+
+
This preview adds enhancements to audio processing on Android, including: 

 
 
-
New Android for Work Features

-
This release includes the following new APIs for Android for Work:

+
Video Features

+
This preview adds new capabilities to the video processing APIs, including:

+
+
+
Camera Features

+
This preview includes the following new APIs for accessing the camera’s flashlight and for
+camera reprocessing of images:

+
+
Flashlight API

+
If a camera device has a flash unit, you can call the {@code CameraManager.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 {@code 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.

+
+
You can register a callback to be notified about torch mode status by calling the
+{@code CameraManager.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
+{@code CameraManager.TorchCallback.onTorchModeChanged()} method is invoked.

+
+
Reprocessing API

+
The {@link android.hardware.camera2 Camera2} API is extended to support YUV and private
+opaque format image reprocessing. Your app determine if the reprocessing capabilities are available
+via {@code CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES}. If a device supports reprocessing,
+you can create a reprocessable camera capture session by calling
+{@code CameraDevice.createReprocessableCaptureSession()}, and create requests for input
+buffer reprocessing.

+
+
Use the {@code ImageWriter} class to connect the input buffer flow to the camera reprocessing
+input. To get an empty buffer, follow this programming model:

+
+
    
+
  1. Call the {@code ImageWriter.dequeueInputImage()} method.
    2. 
+
  2. Fill the data into the input buffer.
    3. 
+
  3. Send the buffer to the  camera by calling the {@code ImageWriter.queueInputImage()} method.
    4. 
+

+
+
If you are using a {@code ImageWriter} object together with an
+{@code android.graphics.ImageFormat.PRIVATE} image, your app cannot access the image
+data directly. Instead, pass the {@code ImageFormat.PRIVATE} image directly to the
+{@code ImageWriter} by calling the {@code ImageWriter.queueInputImage()} method without any
+buffer copy.

+
+
The {@code ImageReader} class now supports {@code android.graphics.ImageFormat.PRIVATE} format
+image streams. This support allows your app to maintain a circular image queue of
+{@code ImageReader} output images, select one or more images, and send them to the
+{@code ImageWriter} for camera reprocessing.

+
+
Android for Work Features

+
This preview includes the following new APIs for Android for Work:

 
 
 

   For a detailed view of all API changes in the M Developer Preview, see the API Differences Report.
+  "{@docRoot}preview/download.html">API Differences Report.
 

\ No newline at end of file
diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd
new file mode 100644
index 0000000000000..0dd549b8863f3
--- /dev/null
+++ b/docs/html/preview/behavior-changes.jd
@@ -0,0 +1,407 @@
+page.title=Behavior Changes
+page.keywords=preview,sdk,compatibility
+sdk.platform.apiLevel=23
+@jd:body
+
+

+
+

+
+
API Level: M

+
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 be understand and account for in your apps.

+
+
If you have previously published an app for Android, be aware that your app
+  might be affected by these changes in the platform.

+
+
Runtime Permissions

+
This preview introduces a new runtime permissions model, where users can now directly manage
+their app permissions at runtime. This model gives users improved visibility and control over
+permissions, while streamlining the installation and auto-update processes for app developers.
+Users can set permissions on or off for all apps running on the M Preview. However, apps that
+don’t target the M Preview cannot request permissions at runtime.

+
+
On your apps that target the M Preview, make sure to check and request for permissions at
+runtime. To determine if your app has been granted a permission, call the
+new {@code Context.checkSelfPermission()} method. To request for a permission, call the new
+{@code Activity.requestPermission()} method.

+
+
For more information on supporting the new permissions model in your app, see
+
+Android M Preview Runtime Permissions.

+
+
Project Volta

+
This preview introduces new power-saving optimizations for idle devices and apps.

+
+
Doze mode

+
If a device is unplugged and left stationary with the screen off for a period of time, it
+goes into Doze 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.

+
+
The following restrictions apply to your apps while in Doze mode:

+
+

+
When the device exists doze mode, it executes any jobs and syncs that are pending.

+
You can test this feature by connecting a device running the M Preview to your development
+machine and calling the following commands:
+

+
+$ adb shell dumpsys battery unplug
+$ adb shell dumpsys deviceidle step
+$ adb shell dumpsys deviceidle -h
+

+
Note: The upcmoning
+Google Cloud Messaging release lets you designate
+high-priority messages. If your app receives high-priority GCM messages, it’s granted
+brief network access even when the device is in doze mode.
+

+
+
App standby

+
With this preview, the system may determine that apps are idle when they are not in active
+use. Your app is considered idle after a period of time, unless the system detects
+any of these signals:

+
+
+
+
If the device is unplugged, apps deemed idle will have their network access disabled
+and their syncs and jobs suspended. When the device is plugged into a power supply, these apps are
+allowed network access and can execute any jobs and syncs that are pending. If the
+device is idle for long periods of time, idle apps are allowed network access around once a day.

+
+
You can test this feature by connecting a device running the M Preview to your development
+machine and calling the following commands:
+

+
+$ adb shell am broadcast -a android.os.action.DISCHARGING
+$ adb shell am set-idle <packageName> true
+$ adb shell am set-idle <packageName> false
+$ adb shell am get-idle <packageName>
+

+
+
Note: The upcoming
+Google Cloud Messaging (GCM) release lets you
+designate high-priority messages. If your app receives high-priority GCM messages, it’s granted
+brief network access even when the app is idle.
+

+
+
Adoptable Storage Devices

+

+With this preview, users can adopt 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
+{@code android:installLocation}
+preference in the manifest.

+
+
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.

+
+
+
+
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:

+
+
+$ adb shell sm set-force-adoptable true
+

+
+
Apache HTTP Client Removal

+
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:
+

+
+android {
+    useLibrary 'org.apache.http.legacy'
+}
+

+
Android is moving away from OpenSSL to the
+BoringSSL
+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.

+
+
AudioManager Changes

+
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
+{@code AudioManager.requestAudioFocus()} method instead. Similarly, the
+{@link android.media.AudioManager#setStreamMute(int,boolean) setStreamMute()} method is
+deprecated; instead, call the {@code AudioManager.adjustStreamVolume()} method
+and pass in the direction value {@code ADJUST_MUTE} or {@code ADJUST_UNMUTE}.

+
+
Text Selection

+
+
+
+
When users select text in your app, you can now display text selection actions such as
+Cut, Copy, and Paste in a
+floating toolbar. The user interaction implementation is similar to that
+for the contextual action bar, as described in
+
+Enabling the contextual action mode for individual views.

+
+
To implement a floating toolbar for text selection, make the following changes in your existing
+apps:

+
    
+
  1. 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)}.
    2. 
+
  2. Take your existing implementation of {@code ActionMode.Callback} and make it extend
+{@code ActionMode.Callback2} instead.
    3. 
+
  3. Override the {@code Callback2.onGetContentRect()} method to provide the coordinates of the
+content {@link android.graphics.Rect} object (such as a text selection rectangle) in the view.
    4. 
+
  4. If the rectangle positioning is no longer valid, and this is the only element to be invalidated,
+call the {@code ActionMode.invalidateContentRect()} method.
    5. 
+

+
+
If you are using 
+Android Support Library 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
+{@code android.support.v7.app.AppCompatActivity.getDelegate()}, then call
+{@code android.support.v7.app.AppCompatDelegate.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.

+
+
Android Keystore Changes

+
With this preview, the
+Android Keystore provider no longer supports
+DSA. ECDSA is still supported.

+
+
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.

+
+
Night Mode (User-configurable Dark Theme)

+

+Support for the {@code -night} resource qualifier has been updated. Previously, night mode was
+only available when a device was docked and in car mode. With this preview, night mode is
+available on
+all devices and is user-configurable via Settings > Display > Theme. You can adjust
+this setting globally using {@link android.app.UiModeManager#setNightMode(int) setNightMode()}. The
+Dark theme corresponds to {@link android.app.UiModeManager#MODE_NIGHT_YES}. When the device is in
+night mode, the resource framework prefers resources that have the {@code -night} qualifier. To
+take advantage of user-configurable Dark mode in your app, extend from the
+{@code Theme.Material.DayNight} set of themes rather than {@code Theme.Material} or
+{@code Theme.Material.Light}.
+

+
+
Wi-Fi and Networking Changes

+
+
This preview introduces the following behavior changes to the Wi-Fi and networking APIs.

+
+
+
Camera Service Changes

+
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:

+
+
+
ART Runtime

+
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
+v7 appcompat library or the
+v7 recyclerview library,
+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.

+
+
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
+(
+public bug 6670), 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.

+
+
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).

+

+
+
APK Validation

+
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.

+
+
Android for Work Changes

+
This preview includes the following behavior changes for Android for Work:

+
diff --git a/docs/html/preview/images/work-profile-screen.png b/docs/html/preview/images/work-profile-screen.png
new file mode 100644
index 0000000000000..c3e4e440bd633
Binary files /dev/null and b/docs/html/preview/images/work-profile-screen.png differ
diff --git a/docs/html/preview/images/work-profile-screen_2x.png b/docs/html/preview/images/work-profile-screen_2x.png
new file mode 100644
index 0000000000000..5dcf610db0ee8
Binary files /dev/null and b/docs/html/preview/images/work-profile-screen_2x.png differ
diff --git a/docs/html/preview/preview_toc.cs b/docs/html/preview/preview_toc.cs
index 7e9f292fea5d0..037193235f520 100644
--- a/docs/html/preview/preview_toc.cs
+++ b/docs/html/preview/preview_toc.cs
@@ -38,10 +38,9 @@
   
 
   
  • 
-    
    
+    
    
       Behavior Changes
    
   
    • 
-
   
  • 
     
    
       Samples