Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Docs: Background optimizations 'foreground' -> 'running app' fix." into mnc-mr-docs

Browse Source
This commit is contained in:
Adarsh Fernando
2016-04-19 22:55:13 +00:00
committed by Android (Google) Code Review
parent 75951d7c86 58cd6d4d03
commit df0509bce1
2 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/html/preview/behavior-changes.jd
View File

@@ -156,10 +156,9 @@ page.image=images/cards/card-n-changes_2x.png
<ul> <ul>
<li>Apps targeting Android N do not receive {@link <li>Apps targeting Android N do not receive {@link
android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts, even if they android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts, even if they
have manifest entries to request notification of these events. Apps running have manifest entries to request notification of these events. Apps that are
in the foreground can still listen for {@code CONNECTIVITY_CHANGE} on their running can still listen for {@code CONNECTIVITY_CHANGE} on their main thread
main thread if they request notification with a {@link if they request notification with a {@link android.content.BroadcastReceiver}.
android.content.BroadcastReceiver}.
</li> </li>
<li>Apps cannot send or receive {@link <li>Apps cannot send or receive {@link

11
docs/html/preview/features/background-optimization.jd
View File

@@ -59,9 +59,9 @@ page.keywords="android N", "implicit broadcasts", "job scheduler"
<ul> <ul>
<li>Apps targeting the Preview do not receive {@link <li>Apps targeting the Preview do not receive {@link
android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts if they android.net.ConnectivityManager#CONNECTIVITY_ACTION} broadcasts if they
register to receive them in their manifest. Apps running in the foreground register to receive them in their manifest. Apps that are running can still
can still listen for {@code CONNECTIVITY_CHANGE} on their main thread by listen for {@code CONNECTIVITY_CHANGE} on their main thread by registering a
registering a {@link android.content.BroadcastReceiver} with {@link {@link android.content.BroadcastReceiver} with {@link
android.content.Context#registerReceiver Context.registerReceiver()}. android.content.Context#registerReceiver Context.registerReceiver()}.
</li> </li>
@@ -165,9 +165,8 @@ public static void scheduleJob(Context context) {
</h3> </h3>
<p> <p>
Apps running in the foreground can still listen for {@code Apps that are running can still listen for {@code CONNECTIVITY_CHANGE} with a
CONNECTIVITY_CHANGE} with a registered {@link registered {@link android.content.BroadcastReceiver}. However, the {@link
android.content.BroadcastReceiver}. However, the {@link
android.net.ConnectivityManager} API provides a more robust method to request android.net.ConnectivityManager} API provides a more robust method to request
a callback only when specified network conditions are met. a callback only when specified network conditions are met.
</p> </p>