diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd index 8310c1860668a..7eba386a97828 100644 --- a/docs/html/preview/api-overview.jd +++ b/docs/html/preview/api-overview.jd @@ -97,7 +97,7 @@ use. Some of the changes include:
- Figure 2. Bundled notifications and direct reply. + Figure 2. Bundled notifications and direct reply.
To learn how to implement the new features, see the Notifications guide.
@@ -131,7 +131,7 @@ headers and actions, when using custom views in notifications.
- Figure 3. Quick Settings tiles in the notification shade. + Figure 3. Quick Settings tiles in the notification shade.
@@ -160,7 +160,7 @@ urgently required or frequently used, and should not be used as shortcuts to lau
- Figure 4. Data Saver in Settings. + Figure 4. Data Saver in Settings.
@@ -326,7 +326,7 @@ For more information, seeHardware-backed keystores provide a much safer method to create, store, and use cryptographic keys on Android devices. They protect keys from the Linux kernel, potential Android vulnerabilities, and extraction -from rooted devices.
+from rooted devices.To make it easier and more secure to use hardware-backed keystores, Android N introduces Key Attestation. Apps and off-devices can use Key @@ -568,7 +568,9 @@ deprecate some of the older patterns that can reduce system performance, especially on low-memory devices.
In Android N we're removing three commonly-used implicit broadcasts —
- {@link android.net.ConnectivityManager#CONNECTIVITY_ACTION}, NEW_PICTURE, and NEW_VIDEO — since those can wake the
+ {@link android.net.ConnectivityManager#CONNECTIVITY_ACTION}, {@link
+ android.hardware.Camera#ACTION_NEW_PICTURE}, and {@link
+ android.hardware.Camera#ACTION_NEW_VIDEO} — since those can wake the
background processes of multiple apps at once and strain memory and battery. If
your app is receiving these, take advantage of the N Developer Preview to
migrate to JobScheduler and related APIs instead.
- Similarly, apps can register to receive implicit {@code NEW_PICTURE} and - {@code NEW_VIDEO} broadcasts from other apps, such as Camera. When a user - takes a picture with the Camera app, these apps wake up to process the - broadcast. + Similarly, apps can register to receive implicit {@link + android.hardware.Camera#ACTION_NEW_PICTURE} and {@link + android.hardware.Camera#ACTION_NEW_VIDEO} broadcasts from other apps, such as + Camera. When a user takes a picture with the Camera app, these apps wake up + to process the broadcast.
@@ -152,13 +153,14 @@ page.image=images/cards/card-n-changes_2x.png android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts, even if they have manifest entries to request notification of these events. Apps running in the foreground can still listen for {@code CONNECTIVITY_CHANGE} on their - main thread if they request notification with a - {@link android.content.BroadcastReceiver}. + main thread if they request notification with a {@link + android.content.BroadcastReceiver}. -
- In the N Developer Preview, apps are not able to send or receive {@code - NEW_PICTURE} or {@code NEW_VIDEO} broadcasts. This restriction helps + In the N Developer Preview, apps are not able to send or receive {@link + android.hardware.Camera#ACTION_NEW_PICTURE} or {@link + android.hardware.Camera#ACTION_NEW_VIDEO} broadcasts. This restriction helps alleviate the performance and user experience impacts when several apps must wake up in order to process a new image or video. The N Developer Preview extends {@link android.app.job.JobInfo} and {@link