From a2cc6cc81a0da2349c6ff1d680af78564ac0627b Mon Sep 17 00:00:00 2001 From: Quddus Chong Date: Mon, 23 Jun 2014 12:34:59 -0700 Subject: docs: Updates to the L Preview Highlights. Change-Id: I085174255e3b45fcdb320fe94a091c7975e80b61 --- docs/html/preview/api-overview.jd | 126 ++++++++++++++++++-------------------- 1 file changed, 58 insertions(+), 68 deletions(-) (limited to 'docs/html') diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index d9cac48..20764be 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -24,7 +24,6 @@ sdk.platform.apiLevel=20
  • User Interface
    1. Material design support
      2. -
    2. Do Not Disturb mode
    3. Lockscreen notifications
    4. Notifications metadata
    5. Concurrent documents and activities in the Recents screen
      6. @@ -39,11 +38,12 @@ sdk.platform.apiLevel=20
    6. Animation & Graphics
      1. Support for OpenGL ES 3.1
        2. +
      2. Android Extension Pack
    7. Multimedia
        -
      1. Camera v2 API
        2. +
      2. Camera API for advanced camera capabilities
      3. Audio playback
      4. Media playback control
      @@ -55,7 +55,7 @@ sdk.platform.apiLevel=20
    8. Wireless and Connectivity
        -
      1. Dynamic network selection and seamless handoff
        2. +
      2. Multiple network connections
      3. Bluetooth broadcasting
      4. NFC enhancements
      @@ -85,17 +85,10 @@ sdk.platform.apiLevel=20
    9. Manifest Declarations
      1. Declarable required features
        2. -
      2. User permissions
    -

    See also

    -
      -
    1. API -Differences Report »
      2. -
    - @@ -188,8 +181,8 @@ notifications look right with the new color scheme:

    If you are currently adding sounds and vibrations to your notifications by using the {@link android.media.Ringtone}, {@link android.media.MediaPlayer}, or {@link android.os.Vibrator} classes, remove this code so that -the system can present notifications correctly in Do -Not Disturb mode. Instead, use the {@link android.app.Notification.Builder} +the system can present notifications correctly in Do +not Disturb mode. Instead, use the {@link android.app.Notification.Builder} methods instead to add sounds and vibration.

    Notifications now appear in a small floating window @@ -302,31 +295,6 @@ notification, first create the replacement notification using notification object, attach the replacement notification to it through the {@code Notification.Builder.setPublicVersion()} method.

    -

    Do Not Disturb mode

    - -

    The L Developer Preview introduces a new Do Not Disturb mode. When -the user puts the device in Do Not Disturb mode, the device limits -the frequency of the notifications it shows the user (when the user -wants to avoid distractions). The user can -customize the feature in a number of ways, such as:

    - - - -

    You should add the appropriate metadata to your app notifications to help -make sure Do Not Disturb mode handles them properly. For example, if -your app is an alarm clock, -you can tag the notification as an alarm so it will wake the user up even if the -device is in Do Not Disturb mode. For more information, see Notifications metadata.

    -

    Notifications metadata

    The L Developer Preview uses metadata associated with your app notifications to sort the notifications more intelligently. The metadata you set also @@ -338,7 +306,7 @@ notification:

    -

    The Java interface for OpenGL ES 3.1 on Android is provided with GLES31. When +

    The Java interface for OpenGL ES 3.1 on Android is provided with {@code GLES31}. When using OpenGL ES 3.1, be sure that you declare it in your manifest file with the {@code <uses-feature>} tag and the {@code android:glEsVversion} attribute. For example:

    @@ -454,9 +422,32 @@ tag and the {@code android:glEsVversion} attribute. For example:

    device’s supported OpenGL ES version at runtime, see the OpenGL ES API guide.

    +

    Android Extension Pack

    + +

    In addition to OpenGL ES 3.1, this release provides an extension pack with Java interfaces and +native support for advanced graphics functionality. These extensions are treated as a single +package by Android. (If the {@code ANDROID_extension_pack_es31} extension is present, your app can +assume all extensions in the package are present and enable the shading language features with +a single {@code #extension} statement.

    +

    The extension pack supports:

    + + +

    The Java interface for the extension pack is provided with {@code GLES31Ext}. +In your app manifest, you can declare that support for the extension pack is +required, with the +{@code <uses-feature>} +tag, but the precise syntax is not finalized in the L Developer Preview.

    +

    Multimedia

    -

    Camera v2 API

    +

    Camera API for advanced camera capabilities

    The L Developer Preview introduces the new {@code android.hardware.camera2} API to facilitate fine-grain photo capture and image processing. You can now @@ -474,6 +465,9 @@ capture request. Now when the system completes the image capture request, your {@code onCaptureCompleted()}, providing you with the image capture metadata in a {@code CaptureResult}.

    +

    To see an example of how to use the updated Camera API, refer to the {@code Camera2Basic} +and {@code Camera2Video} implementation samples in this release.

    +

    Audio playback

    This release includes the following changes to {@link android.media.AudioTrack}:

    @@ -557,7 +551,7 @@ content.

    Wireless & Connectivity

    -

    Dynamic network selection and seamless handoff

    +

    Multiple network connections

    The L Developer Preview provides new multi-networking APIs. These let your app dynamically scan for available networks with specific capabilities, and establish a connection to them. This is useful when your app requires a @@ -680,6 +674,9 @@ JobScheduler jobScheduler = jobScheduler.schedule(uploadTask); +

    To see an example of how to use the {@code JobScheduler} API, refer to the +{@code JobSchedulerSample} implementation sample in this release.

    +

    Developer tools for power measurement

    The L Developer Preview provides several new developer tools and APIs to help you better measure and understand your app's power usage.

    @@ -762,31 +759,32 @@ $ 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 managed -profile to a device with an existing personal account. The administrator has -control over the managed profile.

    +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 +non-managed apps in the user’s Launcher, Recent apps screen, and notifications.

    To start the managed provisioning process, send {@code 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 -set this profile to the enabled state.

    - -

    A user may be associated with more than one managed profile. To get a list of -the managed profiles associated with the user, call -{@code android.os.UserManager. getUserProfiles()}.

    +enable this Android work profile.

    -

    Once a managed profile is created for a user, apps that are managed by the -device administrator will appear alongside non-managed apps in the user’s -Launcher, Recent apps screen, and notifications.

    +

    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()}.

    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 managed profiles. Your Launcher can make +for the current user and any associated Android work 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()}.

    +drawable with {@code android.os.UserManager. getBadgeDrawableForUser()}.

    + +

    To see an example of how to use the new functionality, refer to the +{@code BasicManagedProfile} implementation sample in this release.

    Task locking

    The L Developer Preview introduces a new task locking API that @@ -897,7 +895,7 @@ your app needs.

    -

    User permissions

    -

    The following values are now supported in the -{@code - <uses-permission>} to declare the -permissions your app requires in order to access certain APIs. - -

    +

    For a detailed view of all API changes in the L Developer Preview, see the +API Differences Report.

    -- cgit v1.1