Home | History | Annotate | Download | only in marshmallow
      1 page.title=Android 6.0 APIs
      2 page.keywords=marshmallow,sdk,compatibility
      3 page.tags=androidm,marshmallow
      4 sdk.platform.apiLevel=23
      5 page.image=images/cards/card-api-overview_16-9_2x.png
      6 page.metaDescription=Get to know the new developer features in Android 6.0 Marshmallow.
      7 @jd:body
      8 
      9 
     10 <div id="qv-wrapper">
     11 <div id="qv">
     12 
     13 <h2>In this document
     14     <a href="#" onclick="hideNestedItems('#toc44',this);return false;" class="header-toggle">
     15         <span class="more">show more</span>
     16         <span class="less" style="display:none">show less</span></a></h2>
     17 
     18 <ol id="toc44" class="hide-nested">
     19 
     20   <li><a href="#fingerprint-authentication">Fingerprint Authentication</a></li>
     21   <li><a href="#confirm-credential">Confirm Credential</a></li>
     22   <li><a href="#app-linking">App Linking</a></li>
     23   <li><a href="#backup">Auto Backup for Apps</a></li>
     24   <li><a href="#direct-share">Direct Share</a></li>
     25   <li><a href="#voice-interactions">Voice Interactions</a></li>
     26   <li><a href="#assist">Assist API</a></li>
     27   <li><a href="#adoptable-storage">Adoptable Storage</a></li>
     28   <li><a href="#notifications">Notifications</a></li>
     29   <li><a href="#bluetooth-stylus">Bluetooth Stylus Support</a></li>
     30   <li><a href="#ble-scanning">Improved Bluetooth Low Energy Scanning</a></li>
     31   <li><a href="#hotspot">Hotspot 2.0 Release 1 Support</a></li>
     32   <li><a href="#4K-display">4K Display Mode</a></li>
     33   <li><a href="#behavior-themeable-colorstatelists">Themeable ColorStateLists</a></li>
     34   <li><a href="#audio">Audio Features</a></li>
     35   <li><a href="#video">Video Features</a></li>
     36   <li><a href="#camera">Camera Features</a>
     37     <ol>
     38       <li><a href="#flashlight">Flashlight API</a></li>
     39       <li><a href="#reprocessing">Camera Reprocessing</a></li>
     40     </ol>
     41   </li>
     42   <li><a href="#afw">Android for Work Features</a></li>
     43 </ol>
     44 
     45 <h2>API Differences</h2>
     46 <ol>
     47 <li><a href="{@docRoot}sdk/api_diff/23/changes.html">API level 22 to 23 &raquo;</a> </li>
     48 </ol>
     49 
     50 </div>
     51 </div>
     52 
     53 <p>Android 6.0 (<a href="{@docRoot}reference/android/os/Build.VERSION_CODES.html#M">M</a>)
     54 offers new features for users and app developers. This document provides an introduction to the
     55 most notable APIs.</p>
     56 
     57 <h3 id="Start">Start developing</h3>
     58 
     59 <p>To start building apps for Android 6.0, you must first <a href="{@docRoot}studio/index.html">get
     60 the Android SDK</a>. Then use the <a href="{@docRoot}tools/help/sdk-manager.html">SDK Manager</a>
     61 to download the Android 6.0 SDK Platform and System Images.</p>
     62 
     63 
     64 <h3 id="ApiLevel">Update your target API level</h3>
     65 
     66 <p>To better optimize your app for devices running Android {@sdkPlatformVersion},
     67   set your <a
     68 href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#target">{@code targetSdkVersion}</a> to
     69 <code>"{@sdkPlatformApiLevel}"</code>, install your app on an Android
     70 {@sdkPlatformVersion} system image, test it, then publish the updated app with
     71 this change.</p>
     72 
     73 <p>You can use Android {@sdkPlatformVersion} APIs while also supporting older
     74 versions by adding conditions to your code that check for the system API level
     75 before executing APIs not supported by your <a
     76 href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#min">{@code minSdkVersion}</a>.
     77 To learn more about maintaining backward compatibility, read <a
     78 href="{@docRoot}training/basics/supporting-devices/platforms.html">Supporting
     79 Different Platform Versions</a>.</p>
     80 
     81 <p>For more information about how API levels work, read <a
     82 href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">What is API
     83 Level?</a></p>
     84 
     85 <h2 id="fingerprint-authentication">Fingerprint Authentication</h2>
     86 
     87 <p>This release offers new APIs to let you authenticate users by using their fingerprint scans on
     88 supported devices, Use these APIs in conjunction with
     89 the <a href="{@docRoot}training/articles/keystore.html">Android Keystore system</a>.</p>
     90 
     91 <p>To authenticate users via fingerprint scan, get an instance of the new
     92 {@link android.hardware.fingerprint.FingerprintManager} class and call the
     93 {@link android.hardware.fingerprint.FingerprintManager#authenticate(android.hardware.fingerprint.FingerprintManager.CryptoObject, android.os.CancellationSignal, int, android.hardware.fingerprint.FingerprintManager.AuthenticationCallback, android.os.Handler) authenticate()}
     94 method. Your app must be running on a compatible
     95 device with a fingerprint sensor. You must implement the user interface for the fingerprint
     96 authentication flow on your app, and use the standard Android fingerprint icon in your UI.
     97 The Android fingerprint icon ({@code c_fp_40px.png}) is included in the
     98 <a href="{@docRoot}samples/FingerprintDialog/index.html">Fingerprint Dialog sample</a>. If you are
     99 developing multiple apps that use fingerprint authentication, note that each app must authenticate
    100 the users fingerprint independently.
    101 </p>
    102 
    103 <p>To use this feature in your app, first add the
    104   {@link android.Manifest.permission#USE_FINGERPRINT} permission in your manifest.</p>
    105 
    106 <pre>
    107 &lt;uses-permission
    108         android:name="android.permission.USE_FINGERPRINT" /&gt;
    109 </pre>
    110 <img src="{@docRoot}images/android-6.0/fingerprint-screen.png"
    111 srcset="{@docRoot}images/android-6.0/fingerprint-screen.png 1x, {@docRoot}images/android-6.0/fingerprint-screen_2x.png 2x"
    112 style="float:right; margin:0 0 10px 20px" width="282" height="476" />
    113 
    114 <p>To see an app implementation of fingerprint authentication, refer to the
    115 <a href="{@docRoot}samples/FingerprintDialog/index.html">Fingerprint Dialog sample</a>. For a
    116 demonstration of how you can use these authentication
    117   APIs in conjunction with other Android APIs, see the video
    118   <a class="video-shadowbox-button" href="https://www.youtube.com/watch?v=VOn7VrTRlA4">
    119   Fingerprint and Payment APIs</a>.</p>
    120 
    121 <p>If you are testing this feature, follow these steps:</p>
    122 <ol>
    123 <li>Install Android SDK Tools Revision 24.3, if you have not done so.</li>
    124 <li>Enroll a new fingerprint in the emulator by going to
    125 <strong>Settings > Security > Fingerprint</strong>, then follow the enrollment instructions.</li>
    126 <li>Use an emulator to emulate fingerprint touch events with the
    127 following command. Use the same command to emulate fingerprint touch events on the lockscreen or
    128 in your app.
    129 <pre class="no-prettyprint">
    130 adb -e emu finger touch &lt;finger_id&gt;
    131 </pre>
    132 <p>On Windows, you may have to run {@code telnet 127.0.0.1 &lt;emulator-id&gt;} followed by
    133   {@code finger touch &lt;finger_id&gt;}.
    134 </p>
    135 </li>
    136 </ol>
    137 
    138 <h2 id="confirm-credential">Confirm Credential</h2>
    139 <p>Your app can authenticate users based on how recently they last unlocked their device. This
    140 feature frees users from having to remember additional app-specific passwords, and avoids the need
    141 for you to implement your own authentication user interface. Your app should use this feature in
    142 conjunction with a public or secret key implementation for user authentication.</p>
    143 
    144 <p>To set the timeout duration for which the same key can be re-used after a user is successfully
    145 authenticated, call the new
    146 {@link android.security.keystore.KeyGenParameterSpec.Builder#setUserAuthenticationValidityDurationSeconds(int) setUserAuthenticationValidityDurationSeconds()}
    147 method when you set up a {@link javax.crypto.KeyGenerator} or
    148 {@link java.security.KeyPairGenerator}.</p>
    149 
    150 <p>Avoid showing the re-authentication dialog excessively -- your apps should try using the
    151 cryptographic object first and if the the timeout expires, use the
    152 {@link android.app.KeyguardManager#createConfirmDeviceCredentialIntent(java.lang.CharSequence, java.lang.CharSequence) createConfirmDeviceCredentialIntent()}
    153 method to re-authenticate the user within your app.
    154 </p>
    155 
    156 <p>To see an app implementation of this feature, refer to the
    157 <a href="{@docRoot}samples/ConfirmCredential/index.html">
    158   Confirm Credential sample</a>.</p>
    159 
    160 <h2 id="app-linking">App Linking</h2>
    161 <p>This release enhances Androids intent system by providing more powerful app linking.
    162 This feature allows you to associate an app with a web domain you own. Based on this
    163 association, the platform can determine the default app to use to handle a particular
    164 web link and skip prompting users to select an app. To learn how to implement this feature, see
    165 <a href="{@docRoot}training/app-links/index.html">Handling App Links</a>.
    166 
    167 <h2 id="backup">Auto Backup for Apps</h2>
    168 <p>The system now performs automatic full data backup and restore for apps. Your app must target
    169   Android 6.0 (API level 23) to enable this behavior; you do not need to add any additional code.
    170   If users delete their Google accounts, their backup data is deleted as well. To learn how this
    171   feature works and how to configure what to back up on the file system, see
    172   <a href="{@docRoot}training/backup/autosyncapi.html">Configuring Auto Backup for Apps</a>.</p>
    173 
    174 <h2 id="direct-share">Direct Share</h2>
    175 
    176 <img src="{@docRoot}images/android-6.0/direct-share-screen.png"
    177 srcset="{@docRoot}images/android-6.0/direct-share-screen.png 1x, {@docRoot}images/android-6.0/direct-share-screen_2x.png 2x"
    178 style="float:right; margin:0 0 20px 30px" width="312" height="329" />
    179 
    180 <p>This release provides you with APIs to make sharing intuitive and quick for users. You can now
    181 define <em>direct share targets</em> that launch a specific activity in your app. These direct share
    182 targets are exposed to users via the <em>Share</em> menu. This feature allows users to share
    183 content to targets, such as contacts, within other apps. For example, the direct share target might
    184 launch an activity in another social network app, which lets the user share content directly to a
    185 specific friend or community in that app.</p>
    186 
    187 <p>To enable direct share targets you must define a class that extends the
    188 {@link android.service.chooser.ChooserTargetService} class. Declare your
    189 service in the manifest. Within that declaration, specify the
    190 {@link android.Manifest.permission#BIND_CHOOSER_TARGET_SERVICE} permission and an
    191 intent filter using the
    192 {@link android.service.chooser.ChooserTargetService#SERVICE_INTERFACE SERVICE_INTERFACE} action.</p>
    193 <p>The following example shows how you might declare the
    194 {@link android.service.chooser.ChooserTargetService} in your manifest.</p>
    195 <pre>
    196 &lt;service android:name=".ChooserTargetService"
    197         android:label="&#64;string/service_name"
    198         android:permission="android.permission.BIND_CHOOSER_TARGET_SERVICE"&gt;
    199     &lt;intent-filter&gt;
    200         &lt;action android:name="android.service.chooser.ChooserTargetService" /&gt;
    201     &lt;/intent-filter&gt;
    202 &lt;/service&gt;
    203 </pre>
    204 
    205 <p>For each activity that you want to expose to
    206 {@link android.service.chooser.ChooserTargetService}, add a
    207 {@code &lt;meta-data&gt;} element with the name
    208 {@code "android.service.chooser.chooser_target_service"} in your app manifest.
    209 </p>
    210 
    211 <pre>
    212 &lt;activity android:name=".MyShareActivity
    213         android:label="&#64;string/share_activity_label"&gt;
    214     &lt;intent-filter>
    215         &lt;action android:name="android.intent.action.SEND" /&gt;
    216     &lt;/intent-filter>
    217 &lt;meta-data
    218         android:name="android.service.chooser.chooser_target_service"
    219         android:value=".ChooserTargetService" /&gt;
    220 &lt;/activity>
    221 </pre>
    222 
    223 <h2 id="voice-interactions">Voice Interactions</h2>
    224 <p>
    225 This release provides a new voice interaction API which, together with
    226 <a href="https://developers.google.com/voice-actions/" class="external-link">Voice Actions</a>,
    227 allows you to build conversational voice experiences into your apps. Call the
    228 {@link android.app.Activity#isVoiceInteraction()} method to determine if a voice action triggered
    229 your activity. If so, your app can use the
    230 {@link android.app.VoiceInteractor} class to request a voice confirmation from the user, select
    231 from a list of options, and more.</p>
    232 
    233 <p>Most voice interactions originate from a user voice action. A voice interaction activity can
    234 also, however, start without user input. For example, another app launched through a voice
    235 interaction can also send an intent to launch a voice interaction. To determine if your activity
    236 launched from a user voice query or from another voice interaction app, call the
    237 {@link android.app.Activity#isVoiceInteractionRoot()} method. If another app launched your
    238 activity, the method returns {@code false}. Your app may then prompt the user to confirm that
    239 they intended this action.</p>
    240 
    241 <p>To learn more about implementing voice actions, see the
    242 <a href="https://developers.google.com/voice-actions/interaction/"
    243 class="external-link">Voice Actions developer site</a>.
    244 </p>
    245 
    246 <h2 id="assist">Assist API</h2>
    247 <p>
    248 This release offers a new way for users to engage with your apps through an assistant. To use this
    249 feature, the user must enable the assistant to use the current context. Once enabled, the user
    250 can summon the assistant within any app, by long-pressing on the <strong>Home</strong> button.</p>
    251 <p>Your app can elect to not share the current context with the assistant by setting the
    252 {@link android.view.WindowManager.LayoutParams#FLAG_SECURE} flag. In addition to the
    253 standard set of information that the platform passes to the assistant, your app can share
    254 additional information by using the new {@link android.app.assist.AssistContent} class.</p>
    255 
    256 <p>To provide the assistant with additional context from your app, follow these steps:</p>
    257 
    258 <ol>
    259 <li>Implement the {@link android.app.Application.OnProvideAssistDataListener} interface.</li>
    260 <li>Register this listener by using
    261 {@link android.app.Application#registerOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener) registerOnProvideAssistDataListener()}.</li>
    262 <li>In order to provide activity-specific contextual information, override the
    263 {@link android.app.Activity#onProvideAssistData(android.os.Bundle) onProvideAssistData()}
    264 callback and, optionally, the new
    265 {@link android.app.Activity#onProvideAssistContent(android.app.assist.AssistContent) onProvideAssistContent()}
    266 callback.
    267 </ol>
    268 
    269 <h2 id="adoptable-storage">Adoptable Storage Devices</h2>
    270 <p>
    271 With this release, users can <em>adopt</em> external storage devices such as SD cards. Adopting an
    272 external storage device encrypts and formats the device to behave like internal storage. This
    273 feature allows users to move both apps and private data of those apps between storage devices. When
    274 moving apps, the system respects the
    275 <a href="{@docRoot}guide/topics/manifest/manifest-element.html#install">{@code android:installLocation}</a>
    276 preference in the manifest.</p>
    277 
    278 <p>If your app accesses the following APIs or fields, be aware that the file paths they return
    279 will dynamically change when the app is moved between internal and external storage devices.
    280 When building file paths, it is strongly recommended that you always call these APIs dynamically.
    281 Dont use hardcoded file paths or persist fully-qualified file paths that were built previously.</p>
    282 
    283 <ul>
    284 <li>{@link android.content.Context} methods:
    285     <ul>
    286         <li>{@link android.content.Context#getFilesDir() getFilesDir()}</li>
    287         <li>{@link android.content.Context#getCacheDir() getCacheDir()}</li>
    288         <li>{@link android.content.Context#getCodeCacheDir() getCodeCacheDir()}</li>
    289         <li>{@link android.content.Context#getDatabasePath(java.lang.String) getDatabasePath()}</li>
    290         <li>{@link android.content.Context#getDir(java.lang.String,int) getDir()}</li>
    291         <li>{@link android.content.Context#getNoBackupFilesDir() getNoBackupFilesDir()}</li>
    292         <li>{@link android.content.Context#getFileStreamPath(java.lang.String) getFileStreamPath()}</li>
    293         <li>{@link android.content.Context#getPackageCodePath() getPackageCodePath()}</li>
    294         <li>{@link android.content.Context#getPackageResourcePath() getPackageResourcePath()}</li>
    295     </ul>
    296 </li>
    297 <li>{@link android.content.pm.ApplicationInfo} fields:
    298     <ul>
    299         <li>{@link android.content.pm.ApplicationInfo#dataDir dataDir}</li>
    300         <li>{@link android.content.pm.ApplicationInfo#sourceDir sourceDir}</li>
    301         <li>{@link android.content.pm.ApplicationInfo#nativeLibraryDir nativeLibraryDir}</li>
    302         <li>{@link android.content.pm.ApplicationInfo#publicSourceDir publicSourceDir}</li>
    303         <li>{@link android.content.pm.ApplicationInfo#splitSourceDirs splitSourceDirs}</li>
    304         <li>{@link android.content.pm.ApplicationInfo#splitPublicSourceDirs splitPublicSourceDirs}</li>
    305     </ul>
    306 </li>
    307 </ul>
    308 
    309 <p>To debug this feature, you can enable adoption of a USB drive that is
    310 connected to an Android device through a USB On-The-Go (OTG) cable, by running this command:</p>
    311 
    312 <pre class="no-prettyprint">
    313 $ adb shell sm set-force-adoptable true
    314 </pre>
    315 
    316 <h2 id="notifications">Notifications</h2>
    317 <p>This release adds the following API changes for notifications:</p>
    318 <ul>
    319   <li>New {@link android.app.NotificationManager#INTERRUPTION_FILTER_ALARMS} filter level that
    320     corresponds to the new <em>Alarms only</em> do not disturb mode.</li>
    321   <li>New {@link android.app.Notification#CATEGORY_REMINDER} category value that is used to
    322   distinguish user-scheduled reminders from other events
    323   ({@link android.app.Notification#CATEGORY_EVENT}) and alarms
    324   ({@link android.app.Notification#CATEGORY_ALARM}).</li>
    325   <li>New {@link android.graphics.drawable.Icon} class that you can attach to your notifications
    326   via the
    327   {@link android.app.Notification.Builder#setSmallIcon(android.graphics.drawable.Icon) setSmallIcon()}
    328   and {@link android.app.Notification.Builder#setLargeIcon(android.graphics.drawable.Icon) setLargeIcon()}
    329   methods. Similarly, the
    330   {@link android.app.Notification.Builder#addAction(int, java.lang.CharSequence, android.app.PendingIntent)
    331   addAction()} method now accepts an {@link android.graphics.drawable.Icon} object instead of a
    332   drawable resource ID.</li>
    333   <li>New {@link android.app.NotificationManager#getActiveNotifications()} method that allows your
    334   apps to find out which of their notifications are currently alive. To see an app implementation
    335   that uses this feature, see the
    336   <a href="{@docRoot}samples/ActiveNotifications/index.html">Active Notifications sample</a>.</li>
    337 </ul>
    338 
    339 <h2 id="bluetooth-stylus">Bluetooth Stylus Support</h2>
    340 <p>This release provides improved support for user input using a Bluetooth stylus. Users can pair
    341 and connect a compatible Bluetooth stylus with their phone or tablet.  While connected, position
    342 information from the touch screen is fused with pressure and button information from the stylus to
    343 provide a greater range of expression than with the touch screen alone. Your app can listen for
    344 stylus button presses and perform secondary actions, by registering
    345 {@link android.view.View.OnContextClickListener} and
    346 {@link android.view.GestureDetector.OnContextClickListener} objects in your activity.</p>
    347 
    348 <p>Use the {@link android.view.MotionEvent} methods and constants to detect stylus button
    349 interactions:</p>
    350 <ul>
    351 <li>If the user touches a stylus with a button on the screen of your app, the
    352 {@link android.view.MotionEvent#getToolType(int) getTooltype()} method returns
    353 {@link android.view.MotionEvent#TOOL_TYPE_STYLUS}.</li>
    354 <li>For apps targeting Android 6.0 (API level 23), the
    355 {@link android.view.MotionEvent#getButtonState() getButtonState()}
    356 method returns {@link android.view.MotionEvent#BUTTON_STYLUS_PRIMARY} when the user
    357 presses the primary stylus button. If the stylus has a second button, the same method returns
    358 {@link android.view.MotionEvent#BUTTON_STYLUS_SECONDARY} when the user presses it. If the user presses
    359 both buttons simultaneously, the method returns both values OR'ed together
    360 ({@link android.view.MotionEvent#BUTTON_STYLUS_PRIMARY}|{@link android.view.MotionEvent#BUTTON_STYLUS_SECONDARY}).</li>
    361 <li>
    362 For apps targeting a lower platform version, the
    363 {@link android.view.MotionEvent#getButtonState() getButtonState()} method returns
    364 {@link android.view.MotionEvent#BUTTON_SECONDARY} (for primary stylus button press),
    365 {@link android.view.MotionEvent#BUTTON_TERTIARY} (for secondary stylus button press), or both.
    366 </li>
    367 </ul>
    368 
    369 <h2 id="ble-scanning">Improved Bluetooth Low Energy Scanning</h2>
    370 <p>
    371 If your app performs performs Bluetooth Low Energy scans, use the new
    372 {@link android.bluetooth.le.ScanSettings.Builder#setCallbackType(int) setCallbackType()}
    373 method to specify that you want the system to notify callbacks when it first finds, or sees after a
    374 long time, an advertisement packet matching the set {@link android.bluetooth.le.ScanFilter}. This
    375 approach to scanning is more power-efficient than whats provided in the previous platform version.
    376 </p>
    377 
    378 <h2 id="hotspot">Hotspot 2.0 Release 1 Support</h2>
    379 <p>
    380 This release adds support for the Hotspot 2.0 Release 1 spec on Nexus 6 and Nexus 9 devices. To
    381 provision Hotspot 2.0 credentials in your app, use the new methods of the
    382 {@link android.net.wifi.WifiEnterpriseConfig} class, such as
    383 {@link android.net.wifi.WifiEnterpriseConfig#setPlmn(java.lang.String) setPlmn()} and
    384 {@link android.net.wifi.WifiEnterpriseConfig#setRealm(java.lang.String) setRealm()}. In the
    385 {@link android.net.wifi.WifiConfiguration} object, you can set the
    386 {@link android.net.wifi.WifiConfiguration#FQDN} and the
    387 {@link android.net.wifi.WifiConfiguration#providerFriendlyName} fields.
    388 The new {@link android.net.wifi.ScanResult#isPasspointNetwork()} method indicates if a detected
    389 network represents a Hotspot 2.0 access point.
    390 </p>
    391 
    392 <h2 id="4K-display">4K Display Mode</h2>
    393 <p>The platform now allows apps to request that the display resolution be upgraded to 4K rendering
    394 on compatible hardware. To query the current physical resolution, use the new
    395 {@link android.view.Display.Mode} APIs. If the UI is drawn at a lower logical resolution and is
    396 upscaled to a larger physical resolution, be aware that the physical resolution the
    397 {@link android.view.Display.Mode#getPhysicalWidth()} method returns may differ from the logical
    398 resolution reported by {@link android.view.Display#getSize(android.graphics.Point) getSize()}.</p>
    399 
    400 <p>You can request the system to change the physical resolution in your app as it runs, by setting
    401 the {@link android.view.WindowManager.LayoutParams#preferredDisplayModeId} property of your apps
    402 window.  This feature is useful if you want to switch to 4K display resolution. While in 4K display
    403 mode, the UI continues to be rendered at the original resolution (such as 1080p) and is upscaled to
    404 4K, but {@link android.view.SurfaceView} objects may show content at the native resolution.</p>
    405 
    406 <h2 id="behavior-themeable-colorstatelists">Themeable ColorStateLists</h2>
    407 <p>Theme attributes are now supported in
    408 {@link android.content.res.ColorStateList} for devices running on Android 6.0 (API level 23). The
    409 {@link android.content.res.Resources#getColorStateList(int) Resources.getColorStateList()} and
    410 {@link android.content.res.Resources#getColor(int) Resources.getColor()} methods have been
    411 deprecated. If you are calling these APIs, call the new
    412 {@link android.content.Context#getColorStateList(int) Context.getColorStateList()} or
    413 {@link android.content.Context#getColor(int) Context.getColor()} methods instead. These methods are
    414 also available in the v4 appcompat library via {@link android.support.v4.content.ContextCompat}.</p>
    415 
    416 <h2 id="audio">Audio Features</h2>
    417 
    418 <p>This release adds enhancements to audio processing on Android, including: </p>
    419 <ul>
    420   <li>Support for the <a href="http://en.wikipedia.org/wiki/MIDI" class="external-link">MIDI</a>
    421 protocol, with the new {@link android.media.midi} APIs. Use these APIs to send and receive MIDI
    422 events.</li>
    423   <li>New {@link android.media.AudioRecord.Builder} and {@link android.media.AudioTrack.Builder}
    424 classes to create digital audio capture and playback objects respectively, and configure audio
    425 source and sink properties to override the system defaults.</li>
    426   <li>API hooks for associating audio and input devices. This is particularly useful if your app
    427 allows users to start a voice search from a game controller or remote control connected to Android
    428 TV. The system invokes the new
    429 {@link android.app.Activity#onSearchRequested(android.view.SearchEvent) onSearchRequested()}
    430 callback when the user starts a search. To determine if the user's input device has a built-in
    431 microphone, retrieve the {@link android.view.InputDevice} object from that callback, then call the
    432 new {@link android.view.InputDevice#hasMicrophone()} method.</li>
    433   <li>New {@link android.media.AudioManager#getDevices(int) getDevices()} method which lets you
    434 retrieve a list of all audio devices currently connected to the system. You can also register an
    435 {@link android.media.AudioDeviceCallback} object if you want the system to notify your app
    436 when an audio device connects or disconnects.</li>
    437 </ul>
    438 
    439 <h2 id="video">Video Features</h2>
    440 <p>This release adds new capabilities to the video processing APIs, including:</p>
    441 <ul>
    442 <li>New {@link android.media.MediaSync} class which helps applications to synchronously render
    443 audio and video streams. The audio buffers are submitted in non-blocking fashion and are
    444 returned via a callback. It also supports dynamic playback rate.
    445 </li>
    446 <li>New {@link android.media.MediaDrm#EVENT_SESSION_RECLAIMED} event, which indicates that a
    447 session opened by the app has been reclaimed by the resource manager. If your app uses DRM sessions,
    448 you should handle this event and make sure not to use a reclaimed session.
    449 </li>
    450 <li>New {@link android.media.MediaCodec.CodecException#ERROR_RECLAIMED} error code, which indicates
    451 that the resource manager reclaimed the media resource used by the codec. With this exception, the
    452 codec must be released, as it has moved to terminal state.
    453 </li>
    454 <li>New {@link android.media.MediaCodecInfo.CodecCapabilities#getMaxSupportedInstances()
    455 getMaxSupportedInstances()} interface to get a hint for the max number of the supported
    456 concurrent codec instances.
    457 </li>
    458 <li>New {@link android.media.MediaPlayer#setPlaybackParams(android.media.PlaybackParams)
    459 setPlaybackParams()} method to set the media playback rate for fast or
    460 slow motion playback. It also stretches or speeds up the audio playback automatically in
    461 conjunction with the video.</li>
    462 </ul>
    463 
    464 <h2 id="camera">Camera Features</h2>
    465 <p>This release includes the following new APIs for accessing the cameras flashlight and for
    466 camera reprocessing of images:</p>
    467 
    468 <h3 id="flashlight">Flashlight API</h3>
    469 <p>If a camera device has a flash unit, you can call the
    470 {@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()}
    471 method to switch the flash units torch mode on or off without opening the camera device. The app
    472 does not have exclusive ownership of the flash unit or the camera device. The torch mode is turned
    473 off and becomes unavailable whenever the camera device becomes unavailable, or when other camera
    474 resources keeping the torch on become unavailable. Other apps can also call
    475 {@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()}
    476 to turn off the torch mode. When the last app that turned on the torch mode is closed, the torch
    477 mode is turned off.</p>
    478 
    479 <p>You can register a callback to be notified about torch mode status by calling the
    480 {@link android.hardware.camera2.CameraManager#registerTorchCallback(android.hardware.camera2.CameraManager.TorchCallback, android.os.Handler) registerTorchCallback()}
    481 method. The first time the callback is registered, it is immediately called with the torch mode
    482 status of all currently known camera devices with a flash unit. If the torch mode is turned on or
    483 off successfully, the
    484 {@link android.hardware.camera2.CameraManager.TorchCallback#onTorchModeChanged(java.lang.String, boolean) onTorchModeChanged()}
    485 method is invoked.</p>
    486 
    487 <h3 id="reprocessing">Reprocessing API</h3>
    488 <p>The {@link android.hardware.camera2 Camera2} API is extended to support YUV and private
    489 opaque format image reprocessing. To determine if these reprocessing capabilities are available,
    490 call {@link android.hardware.camera2.CameraManager#getCameraCharacteristics(java.lang.String)
    491 getCameraCharacteristics()} and check for the
    492 {@link android.hardware.camera2.CameraCharacteristics#REPROCESS_MAX_CAPTURE_STALL} key. If a
    493 device supports reprocessing, you can create a reprocessable camera capture session by calling
    494 <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>,
    495 and create requests for input buffer reprocessing.</p>
    496 
    497 <p>Use the {@link android.media.ImageWriter} class to connect the input buffer flow to the camera
    498 reprocessing input. To get an empty buffer, follow this programming model:</p>
    499 
    500 <ol>
    501 <li>Call the {@link android.media.ImageWriter#dequeueInputImage()} method.</li>
    502 <li>Fill the data into the input buffer.</li>
    503 <li>Send the buffer to the  camera by calling the
    504 {@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method.</li>
    505 </ol>
    506 
    507 <p>If you are using a {@link android.media.ImageWriter} object together with an
    508 {@link android.graphics.ImageFormat#PRIVATE} image, your app cannot access the image
    509 data directly. Instead, pass the {@link android.graphics.ImageFormat#PRIVATE} image directly to the
    510 {@link android.media.ImageWriter} by calling the
    511 {@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method
    512 without any buffer copy.</p>
    513 
    514 <p>The {@link android.media.ImageReader} class now supports
    515 {@link android.graphics.ImageFormat#PRIVATE} format image streams. This support allows your app to
    516 maintain a circular image queue of {@link android.media.ImageReader} output images, select one or
    517 more images, and send them to the {@link android.media.ImageWriter} for camera reprocessing.</p>
    518 
    519 <h2 id="afw">Android for Work Features</h2>
    520 <p>This release includes the following new APIs for Android for Work:</p>
    521 <ul>
    522   <li><strong>Enhanced controls for Corporate-Owned, Single-Use devices:</strong> The Device Owner
    523 can now control the following settings to improve management of
    524 Corporate-Owned, Single-Use (COSU) devices:
    525   <ul>
    526     <li>Disable or re-enable the keyguard with the
    527 {@link android.app.admin.DevicePolicyManager#setKeyguardDisabled(android.content.ComponentName, boolean)
    528 setKeyguardDisabled()} method.</li>
    529     <li>Disable or re-enable the status bar (including quick settings, notifications, and the
    530 navigation swipe-up gesture that launches Google Now) with the
    531 {@link android.app.admin.DevicePolicyManager#setStatusBarDisabled(android.content.ComponentName, boolean) setStatusBarDisabled()}
    532 method.</li>
    533     <li>Disable or re-enable safe boot with the {@link android.os.UserManager} constant
    534 {@link android.os.UserManager#DISALLOW_SAFE_BOOT}.</li>
    535     <li>Prevent the screen from turning off while plugged in with the
    536   {@link android.provider.Settings.Global#STAY_ON_WHILE_PLUGGED_IN} constant.</li>
    537   </ul>
    538   </li>
    539   <li><strong>Silent install and uninstall of apps by Device Owner:</strong> A Device Owner can now
    540 silently install and uninstall applications using the {@link android.content.pm.PackageInstaller}
    541 APIs, independent of Google Play for Work. You can now provision devices through a Device Owner that
    542 fetches and installs apps without user interaction. This feature is useful for enabling one-touch
    543 provisioning of kiosks or other such devices without activating a Google account.</li>
    544 <li><strong>Silent enterprise certificate access: </strong> When an app calls
    545 {@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()},
    546 prior to the user being prompted to select a certificate, the Profile or Device Owner can now call
    547 the {@link android.app.admin.DeviceAdminReceiver#onChoosePrivateKeyAlias(android.content.Context, android.content.Intent, int, android.net.Uri, java.lang.String) onChoosePrivateKeyAlias()}
    548 method to provide the alias silently to the requesting application. This feature lets you grant
    549 managed apps access to certificates without user interaction.</li>
    550 <li><strong>Auto-acceptance of system updates.</strong> By setting a system update policy with
    551 {@link android.app.admin.DevicePolicyManager#setSystemUpdatePolicy(android.content.ComponentName, android.app.admin.SystemUpdatePolicy) setSystemUpdatePolicy()},
    552 a Device Owner can now auto-accept a system
    553 update, for instance in the case of a kiosk device, or postpone the update and prevent it being
    554 taken by the user for up to 30 days. Furthermore, an administrator can set a daily time window in
    555 which an update must be taken, for example during the hours when a kiosk device is not in use. When
    556 a system update is available, the system checks if the device policy controller app has set a system
    557 update policy, and behaves accordingly.
    558 </li>
    559 <li>
    560 <strong>Delegated certificate installation:</strong> A Profile or Device Owner can now grant a
    561 third-party app the ability to call these {@link android.app.admin.DevicePolicyManager} certificate
    562 management APIs:
    563 <ul>
    564   <li>{@link android.app.admin.DevicePolicyManager#getInstalledCaCerts(android.content.ComponentName)
    565 getInstalledCaCerts()}</li>
    566   <li>{@link android.app.admin.DevicePolicyManager#hasCaCertInstalled(android.content.ComponentName,byte[])
    567 hasCaCertInstalled()}</li>
    568   <li>{@link android.app.admin.DevicePolicyManager#installCaCert(android.content.ComponentName,byte[])
    569 installCaCert()}</li>
    570   <li>{@link android.app.admin.DevicePolicyManager#uninstallCaCert(android.content.ComponentName,byte[])
    571 uninstallCaCert()}</li>
    572   <li>{@link android.app.admin.DevicePolicyManager#uninstallAllUserCaCerts(android.content.ComponentName)
    573 uninstallAllUserCaCerts()}</li>
    574   <li>{@link android.app.admin.DevicePolicyManager#installKeyPair(android.content.ComponentName,java.security.PrivateKey,java.security.cert.Certificate,java.lang.String)
    575 installKeyPair()}</li>
    576 </ul>
    577 </li>
    578 <img src="{@docRoot}images/android-6.0/work-profile-screen.png"
    579 srcset="{@docRoot}images/android-6.0/work-profile-screen.png 1x, {@docRoot}images/android-6.0/work-profile-screen_2x.png 2x"
    580 style="float:right; margin:0 0 10px 20px" width="282" height="476" />
    581 <li><strong>Data usage tracking.</strong> A Profile or Device Owner can now query for the
    582 data usage statistics visible in <strong>Settings > Data</strong> usage by using the new
    583 {@link android.app.usage.NetworkStatsManager} methods. Profile Owners are automatically granted
    584 permission to query data on the profile they manage, while Device Owners get access to usage data
    585 of the managed primary user.</li>
    586 <li><strong>Runtime permission management:</strong>
    587 <p>A Profile or Device Owner can set a permission policy
    588 for all runtime requests of all applications using
    589 {@link android.app.admin.DevicePolicyManager#setPermissionPolicy(android.content.ComponentName, int)
    590 setPermissionPolicy()}, to either prompt the user to grant the permission or automatically grant or
    591 deny the permission silently. If the latter policy is set, the user cannot
    592 modify the selection made by the Profile or Device Owner within the apps permissions screen in
    593 <strong>Settings</strong>.</p></li>
    594 <li><strong>VPN in Settings:</strong> VPN apps are now visible in
    595     <strong>Settings > More > VPN</strong>.
    596 Additionally, the notifications that accompany VPN usage are now specific to how that VPN is
    597 configured. For Profile Owner, the notifications are specific to whether the VPN is configured
    598 for a managed profile, a personal profile, or both. For a Device Owner, the notifications are
    599 specific to whether the VPN is configured for the entire device.</li>
    600 <li><strong>Work status notification:</strong> A status bar briefcase icon now appears whenever
    601 an app from the managed profile has an activity in the foreground. Furthermore, if the device is
    602 unlocked directly to the activity of an app in the managed profile, a toast is displayed notifying
    603 the user that they are within the work profile.
    604 </li>
    605 </ul>
    606