The L Developer Preview uses metadata associated with your app notifications -to sort the notifications more intelligently. The metadata you set also -controls how the system presents your app notifications when the user is in Do -Not Disturb mode. To set the metadata, call the following methods in -{@code android.app.Notification.Builder} when you construct the -notification:
+to sort the notifications more intelligently. To set the metadata, call the +following methods in {@code android.app.Notification.Builder} when you +construct the notification:In previous releases, the Recents screen could only display a single task for each app that the user interacted with -most recently. The L Developer Preview enables your app to open more tasks as +most recently. Now your app can open more tasks as needed for additional concurrent activities for documents. -This feature facilitates multitasking -by letting users quickly switch between individual activities and documents -from the Recents screen, with a consistent switching experience across all apps. +This feature facilitates multitasking by letting users quickly switch between +individual activities and documents from the Recents screen, with a consistent +switching experience across all apps. Examples of such concurrent tasks might include open tabs in a web browser app, documents in a productivity app, concurrent matches in a game, or chats in a messaging app. Your app can manage its tasks @@ -362,35 +360,12 @@ as well as bug fixes. The default user-agent string for a been updated to incorporate 36.0.0.0 as the version number.
Additionally, this release brings support for the -WebAudio, -WebGL, and -WebRTC open standards. To learn more about -the new features included in this release, see WebView for Android.
+WebAudio, +WebGL, and +WebRTC open standards. To learn more about +the new features included in this release, see WebView for Android. -Beginning in the L Developer Preview, users can more easily switch between -all input -method editors (IME) supported by the platform. Performing the designated -switching action (usually touching a Globe icon on the soft keyboard) will cycle -among all such IMEs. This change takes place in -{@link android.view.inputmethod.InputMethodManager#shouldOfferSwitchingToNextInputMethod -InputMethodManager.shouldOfferSwitchingToNextInputMethod()}.
- -In addition, the framework now checks whether the next IME includes a -switching mechanism at all (and, thus, whether that IME supports switching to -the IME after it). An -IME with a switching mechanism will not cycle to an IME without one. This -change takes place in -{@link android.view.inputmethod.InputMethodManager#switchToNextInputMethod -InputMethodManager.switchToNextInputMethod}. - -
To see an example of how to use the updated IME-switching APIs, refer to the -updated soft-keyboard implementation sample in this release.
- -The L Developer Preview adds Java interfaces and native support for OpenGL @@ -761,9 +736,8 @@ $ historian.par [-p powerfile] bugreport.txt > out.html
The L Developer Preview provides new functionality for running apps within an enterprise environment. A device administrator can -initiate a managed provisioning process to add a co-present but separate Android -work profile to a device, if the user has an existing personal account. -Apps that are associated with Android work profiles will appear alongside +initiate a managed provisioning process to add a co-present but separate managed profile to a device, if the user has an existing personal account. +Apps that are associated with managed profiles will appear alongside non-managed apps in the user’s Launcher, Recent apps screen, and notifications.
To start the managed provisioning process, send {@code @@ -771,15 +745,11 @@ ACTION_PROVISION_MANAGED_PROFILE} in an {@link android.content.Intent}. If the call is successful, the system triggers the {@code android.app.admin.DeviceAdminReceiver. onProfileProvisioningComplete()} callback. You can then call {@code app.admin.DevicePolicyManager. setProfileEnabled()} to -enable this Android work profile.
- -A device administrator can associate a user with more than one Android -work profile. To get a list of the Android work profiles associated with the -user, call {@code android.os.UserManager. getUserProfiles()}.
+enable this managed profile.If you are developing a Launcher app, you can use the new {@code android.content.pm.LauncherApps} class to get a list of launchable activities -for the current user and any associated Android work profiles. Your Launcher can make +for the current user and any associated managed profiles. Your Launcher can make the managed apps visually prominent by appending a “work” badge to the icon drawable with {@code android.os.UserManager. getBadgeDrawableForUser()}.
@@ -801,7 +771,7 @@ specially-configured device owner app, through the {@code android.app.aTo set up a device owner, follow these steps:
Beginning in the L Developer Preview, users can more easily switch between +all input +method editors (IME) supported by the platform. Performing the designated +switching action (usually touching a Globe icon on the soft keyboard) will cycle +among all such IMEs. This change takes place in +{@link android.view.inputmethod.InputMethodManager#shouldOfferSwitchingToNextInputMethod +InputMethodManager.shouldOfferSwitchingToNextInputMethod()}.
+ +In addition, the framework now checks whether the next IME includes a +switching mechanism at all (and, thus, whether that IME supports switching to +the IME after it). An +IME with a switching mechanism will not cycle to an IME without one. This +change takes place in +{@link android.view.inputmethod.InputMethodManager#switchToNextInputMethod +InputMethodManager.switchToNextInputMethod}. + +
To see an example of how to use the updated IME-switching APIs, refer to the +updated soft-keyboard implementation sample in this release.
+