summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Adarsh Fernando <adarshf@google.com> 2016-04-19 08:16:03 -0700
committer Adarsh Fernando <adarshf@google.com> 2016-04-19 08:16:03 -0700
commit58cd6d4d031ec8aa4bcb1719cf648ee10e3a58e6 (patch)
tree1f22ffeda182899787a5f3201cd71031d4334ff2
parent0050cd771117eaf554cc7fd90e29514d12aa189f (diff)
Docs: Background optimizations 'foreground' -> 'running app' fix.
Change-Id: I2ad646f09303a8472a00a1132d50cfa9a8c8409a
-rw-r--r--docs/html/preview/behavior-changes.jd7
-rw-r--r--docs/html/preview/features/background-optimization.jd11
2 files changed, 8 insertions, 10 deletions
diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd
index ee17c4524c3e..0cf5bc9de6f2 100644
--- a/docs/html/preview/behavior-changes.jd
+++ b/docs/html/preview/behavior-changes.jd
@@ -156,10 +156,9 @@ page.image=images/cards/card-n-changes_2x.png
<ul>
<li>Apps targeting Android N do not receive {@link
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}.
+ have manifest entries to request notification of these events. Apps that are
+ running can still listen for {@code CONNECTIVITY_CHANGE} on their main thread
+ if they request notification with a {@link android.content.BroadcastReceiver}.
</li>
<li>Apps cannot send or receive {@link
diff --git a/docs/html/preview/features/background-optimization.jd b/docs/html/preview/features/background-optimization.jd
index 79ba5c81df2d..810d283cb2a0 100644
--- a/docs/html/preview/features/background-optimization.jd
+++ b/docs/html/preview/features/background-optimization.jd
@@ -59,9 +59,9 @@ page.keywords="android N", "implicit broadcasts", "job scheduler"
<ul>
<li>Apps targeting the Preview do not receive {@link
android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts if they
- register to receive them in their manifest. Apps running in the foreground
- can still listen for {@code CONNECTIVITY_CHANGE} on their main thread by
- registering a {@link android.content.BroadcastReceiver} with {@link
+ register to receive them in their manifest. Apps that are running can still
+ listen for {@code CONNECTIVITY_CHANGE} on their main thread by registering a
+ {@link android.content.BroadcastReceiver} with {@link
android.content.Context#registerReceiver Context.registerReceiver()}.
</li>
@@ -165,9 +165,8 @@ public static void scheduleJob(Context context) {
</h3>
<p>
- Apps running in the foreground can still listen for {@code
- CONNECTIVITY_CHANGE} with a registered {@link
- android.content.BroadcastReceiver}. However, the {@link
+ Apps that are running can still listen for {@code CONNECTIVITY_CHANGE} with a
+ registered {@link android.content.BroadcastReceiver}. However, the {@link
android.net.ConnectivityManager} API provides a more robust method to request
a callback only when specified network conditions are met.
</p>