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 am: df0509bce1 am: 86efe43 am: 016500b

Browse Source 
am: b26ec02b

* commit 'b26ec02bf91c178213163c4ee794031fe2faf8db':
  Docs: Background optimizations 'foreground' -> 'running app' fix.

Change-Id: Ifa3657eba9359ee67caa1e900903fc5ee9a2af3f
This commit is contained in:
Adarsh Fernando
2016-04-27 05:52:56 +00:00
committed by android-build-merger
parent c0ecde484d b26ec02bf9
commit 10c42541c6
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>
<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

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

@@ -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>