From 182e8b53eae566568ade7512c5e84c3d4af75ead Mon Sep 17 00:00:00 2001 From: David Friedman Date: Fri, 13 May 2016 10:03:52 -0700 Subject: [PATCH] Docs: CL for continuing work on tactically merged N-DP3 docs. This CL continues the work from ag/1036623 and ag/1036124. Change-Id: Ic1e026ed9f53a389a0435c2b8e21edfe9ef635c4 --- docs/html/preview/api-overview.jd | 66 ++++++++++--------- docs/html/preview/behavior-changes.jd | 52 ++++++++++++++- .../preview/features/notification-updates.jd | 9 +-- 3 files changed, 92 insertions(+), 35 deletions(-) diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index 09227f2515210..1b6da06d1380c 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -38,6 +38,7 @@ page.image=images/cards/card-n-apis_2x.png
  • Scoped directory access
  • Keyboard Shortcuts Helper
  • Sustained Performance API
    • +
  • VR Support
  • Print service enhancements
  • Virtual Files
  • FrameMetricsListener API
    • @@ -85,6 +86,7 @@ interacts with other apps.

    Figure 1. Apps running in split-screen mode.

    +

    Especially on tablets and other larger-screen devices, multi-window support @@ -401,7 +403,7 @@ displayed — users can add or move tiles just by dragging and dropping them

    - For information about creating an app tile, see the + For information about creating an app tile, see the documentation for android.service.quicksettings.Tile in the downloadable API Reference.

    @@ -474,8 +476,9 @@ available to users. It offers more than 25 variants each for commonly used languages such as English, Spanish, French, and Arabic. It also adds partial support for more than 100 new languages.

    -

    Apps can get the list of locales set by the user by calling LocaleList.GetDefault(). To support the expanded number of locales, Android N is changing the way -that it resolves resources. Make sure that you test and verify that your apps +

    Apps can get the list of locales set by the user by calling +LocaleList.GetDefault(). To support the expanded number of locales, Android N is +changing the way that it resolves resources. Make sure that you test and verify that your apps working as expected with the new resource resolution logic.

    To learn about the new resource-resolution behavior and the best practices you @@ -550,7 +553,8 @@ should follow, see Android Extension Pack (AEP) except for EXT_texture_sRGB_decode. +href="https://www.khronos.org/registry/gles/extensions/ANDROID/ANDROID_extension_pack_es31a.txt"> +Android Extension Pack (AEP) except for EXT_texture_sRGB_decode.

  • Floating-point framebuffers for HDR and deferred shading.
  • BaseVertex draw calls to enable better batching and streaming.
  • Robust buffer access control to reduce WebGL overhead. @@ -850,22 +854,18 @@ Directory Access developer documentation.

    Keyboard Shortcuts Helper

    -In Android N, the user can press Meta+/ to trigger a Keyboard Shortcuts +In Android N, the user can press "Alt + /" to trigger a Keyboard Shortcuts screen that displays all shortcuts available both from the system and from the app in focus. These are retrieved automatically from the app’s menu if available, but developers can provide their own fine-tuned shortcuts lists -for the screen. This is done simply by overriding the following method -in {@code Activity.java}: +for the screen. You can do this by overriding the new +Activity.onProvideKeyboardShortcuts() method, described in the downloadable +API Reference.

    -
    -public void onProvideKeyboardShortcuts(
-     List data, Menu menu, int deviceId)
-
    -

    To trigger the Keyboard Shortcuts Helper from anywhere in your app, -call {@code requestKeyboardShortcutsHelper} for the relevant activity. +call {@code Activity.requestKeyboardShortcutsHelper()} for the relevant activity.

    Sustained Performance API

    @@ -879,9 +879,9 @@ developers creating high-performance, long-running apps.

    To address these limitations, Android N includes support for -sustained performance mode, enabling OEMs to provide hints on -device-performance capabilities for long-running applications. App developers -can use these hints to tune applications for a predictable, +sustained performance mode, enabling OEMs to provide hints about +device-performance capabilities for long-running apps. App developers +can use these hints to tune apps for a predictable, consistent level of device performance over long periods of time.

    @@ -890,10 +890,20 @@ App developers can try out this new API in the N Developer Preview on Nexus 6P devices only. To use this feature, set the sustained performance window flag for the window you want to run in sustained performance mode. Set this flag using the -{@code setSustainedPerformanceMode(boolean)} method. The system automatically +{@code Window.setSustainedPerformanceMode()} method. The system automatically disables this mode when the window is no longer in focus.

    +

    VR Support

    + +

    +Leveraging the Sustained Performance API +and newly introduced {@code VrListenerService} class, Android N provides support for +VR apps developed using the Cardboard +SDK. For more information about the {@code VrListenerService} class, see the relevant section +of the downloadable API Reference. + +

    @@ -939,9 +949,10 @@ disables this mode when the window is no longer in focus.

    The FrameMetricsListener API allows an app to monitor its UI rendering -performance by exposing a streaming pubsub API to transfer frame +performance. The API provides this capability by exposing a streaming Pub/Sub API to transfer frame timing info for the app's current window. The data returned is -equivalent to that displayed by {@code adb shell dumpsys gfxinfo framestats}, +equivalent to that displayed by {@code +adb shell dumpsys gfxinfo framestats}, but is not limited to the past 120 frames.

    @@ -958,25 +969,20 @@ for real use cases within an app.

    -The API provides a callback interface to be implemented and -registered on the window that you wish to monitor: +To monitor a window, implement the FrameMetricsListener.onMetricsAvailable() +callback method and register it on that window. For more information, refer to +the {@code FrameMetricsListener} class documentation in +the downloadable API Reference.

    -
    - public interface FrameMetricsListener {
-        void onMetricsAvailable(Window window, FrameMetrics frameMetrics,
-                int dropCountSinceLastInvocation);
-    }
-
    -

    -The API returns a FrameMetrics object, which contains timing data that +The API provides a {@code FrameMetrics} object, which contains timing data that the rendering subsystem reports for various milestones in a frame lifecycle. The supported metrics are: {@code UNKNOWN_DELAY_DURATION}, {@code INPUT_HANDLING_DURATION}, {@code ANIMATION_DURATION}, {@code LAYOUT_MEASURE_DURATION}, {@code DRAW_DURATION}, {@code SYNC_DURATION}, {@code COMMAND_ISSUE_DURATION}, {@code SWAP_BUFFERS_DURATION}, -{@code TOTAL_DURATION}, and {@code FIRST_DRAW_FRAME} +{@code TOTAL_DURATION}, and {@code FIRST_DRAW_FRAME}.

    diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd index 7c8bfe8ba29e0..88dca54b1c3ea 100644 --- a/docs/html/preview/behavior-changes.jd +++ b/docs/html/preview/behavior-changes.jd @@ -23,6 +23,7 @@ page.image=images/cards/card-n-changes_2x.png
  • File System Permission Changes
    • +
  • Sharing Files Between Apps
  • Accessibility Improvements
    1. Screen Zoom
      2. @@ -257,6 +258,23 @@ page.image=images/cards/card-n-changes_2x.png +

      Sharing Files Between Apps

      + +

      +For apps targeting Android N, the Android framework enforces +the {@link android.os.StrictMode} API policy that prohibits exposing {@code file://} URIs +outside your app. If an intent containing a file URI leaves your app, the app fails +with a {@code FileUriExposedException} exception. +

      + +

      +To share files between applications, you should send a {@code content://} URI +and grant a temporary access permission on the URI. The easiest way to grant this permission is by +using the {@link android.support.v4.content.FileProvider} class. For more information +on permissions and sharing files, +see Sharing Files. +

      +

      Accessibility Improvements

      @@ -487,7 +505,7 @@ JavaVM::AttachCurrentThread from <jni.h>. running in device owner mode, the DISALLOW_ADD_USER restriction is automatically set. This prevents users from creating unmanaged secondary users. In addition, the CreateUser() and - createAndInitial() methods are deprecated; the new + createAndInitializeUser() methods are deprecated; the new DevicePolicyManager.createAndManageUser() method replaces them. @@ -496,6 +514,10 @@ JavaVM::AttachCurrentThread from <jni.h>. DevicePolicyManagewr.getWifiMacAddress(). If Wi-Fi has never been enabled on the device, this method returns a value of {@code null}. + +

    2. The Work Mode setting controls access to work apps. When work mode is off the + system launcher indicates work apps are unavailable by greying them out. Enabling + work mode again restores normal behavior.

      @@ -576,5 +598,33 @@ common example is storing too much data in which causes {@code ActivityThread.StopInfo} to throw a {@code RuntimeException} when your app targets Android N.

      3. + +
    3. +If an app posts {@link java.lang.Runnable} tasks to a {@link android.view.View}, and +the {@link android.view.View} +is not attached to a window, the system +queues the {@link java.lang.Runnable} task with the {@link android.view.View}; +the {@link java.lang.Runnable} task does not execute until the +{@link android.view.View} is attached +to a window. This behavior fixes the following bugs: +
        +
      • If an app posted to a {@link android.view.View} from a thread other than the intended + window’s UI thread, the {@link java.lang.Runnable} may run on the wrong thread as a result. +
        • +
      • If the {@link java.lang.Runnable} task was posted from a thread other than + a looper thread, the app could expose the {@link java.lang.Runnable} task.
        • +
      +
      4. + +
    4. +If an app on Android N with +{@link android.Manifest.permission#DELETE_PACKAGES DELETE_PACKAGES} +permission tries to delete a package, but a different app had installed that package, +the system requires user confirmation. In this scenario, apps should expect +{@link android.content.pm.PackageInstaller#STATUS_PENDING_USER_ACTION STATUS_PENDING_USER_ACTION} +as the return status when they invoke +{@link android.content.pm.PackageInstaller#uninstall PackageInstaller.uninstall()}. +
      5. + diff --git a/docs/html/preview/features/notification-updates.jd b/docs/html/preview/features/notification-updates.jd index c40536053f766..016333734b579 100644 --- a/docs/html/preview/features/notification-updates.jd +++ b/docs/html/preview/features/notification-updates.jd @@ -209,9 +209,10 @@ notificationManager.notify(notificationId, repliedNotification); The notification must be either updated or cancelled after the app has received remote input. When the user replies to a remote update using Direct Reply, - do not cancel the notification. Instead, update the notification to display the user's reply. You can update the notification using a - MessagingStyle, or you can append the user's reply to the remote - input history. + do not cancel the notification. Instead, update the notification to display the user's reply. +For notifications using {@code MessagingStyle}, you should add +the reply as the latest message. When using other templates, you can +append the user's reply to the remote-input history.

      Bundled Notifications

      @@ -395,4 +396,4 @@ Notification notification = new Notification.Builder() .addMessage("What's up?", timestamp2, "Coworker") .addMessage("Not much", timestamp3, null) .addMessage("How about lunch?", timestamp4, "Coworker")); - \ No newline at end of file +