[Background Sync] Use GcmNetworkManager to start the browser for sync events.

chrome/android/java/AndroidManifest.xml

 <?xml version="1.0" encoding="utf-8"?>
 <!-- Copyright 2015 The Chromium Authors. All rights reserved.
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file. -->
 
 <!--
 Note: This is a jinja2 template, processed at build time into the final manifest.
 
 Blocks denoted with { % block some_name % }foo{ % endblock % } can be overridden
 by a child template that "extends" this file.
@@ skipping 26 matching lines @@
     <uses-permission-sdk-m android:name="android.permission.BLUETOOTH_ADMIN"/>
 
     <uses-permission android:name="android.permission.CAMERA" />
     <uses-permission android:name="android.permission.GET_ACCOUNTS"/>
     <uses-permission android:name="android.permission.INTERNET"/>
     <uses-permission android:name="android.permission.MANAGE_ACCOUNTS"/>
     <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS"/>
     <uses-permission android:name="android.permission.NFC"/>
     <uses-permission android:name="android.permission.READ_SYNC_SETTINGS"/>
     <uses-permission android:name="android.permission.READ_SYNC_STATS"/>
+    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>

[Yaron, 2015/09/24 16:13:17]

Also, where is it used? Within play services?

[iclelland, 2015/09/24 17:11:50]

Yes, it's only used within play services -- the NetworkScheduler verifies that
the app has this permission before it allows a task which persists across
reboots to be scheduled.

See
https://developers.google.com/android/reference/com/google/android/gms/gcm/On...

(The permission itself is usually used to get an app to receive the
ACTION_BOOT_COMPLETED intent, but we're not using it for that. I presume that
the check inside of GCM is to ensure that you're not trying to "cheat" by having
play services tell you when the device rebooted, if you don't have that
permission yourself.)

[jkarlin, 2015/09/24 18:08:47]

Ian: I thought we agreed that this permission had to go?

[iclelland, 2015/09/24 18:33:04]

Maybe I misunderstood -- I thought we agreed that we needed to get someone with
deeper Android understanding to review it, before deciding whether or not to
dump it.

Without this permission, we *cannot* register GCM tasks that persist across a
reboot. If a sync is scheduled, with the device offline, and the user restarts
the phone, it will be lost (applies to periodic, eventually, as well as
one-shot). We won't be able to trigger the sync event until the user manually
starts the browser again.

If that's acceptable (or a different CL), or it's at least preferable to adding
the permission, then we can remove it, and the setPersistent() call that
requires it.

[jkarlin, 2015/09/24 18:38:34]

That's right, my mistake.
I think it'll come down to whether or not the permission is part of a bucket
that we already have permission for.

[iclelland, 2015/09/24 18:56:19]

My understanding is that that permission does not trigger any permission dialog,
on install or on upgrade; it's a non-dangerous permission, and doesn't fall into
any of the buckets.

     <uses-permission android:name="android.permission.RECORD_AUDIO"/>
     <uses-permission android:name="android.permission.USE_CREDENTIALS"/>
     <uses-permission android:name="android.permission.VIBRATE"/>
     <uses-permission android:name="android.permission.WAKE_LOCK"/>
     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
     <uses-permission android:name="android.permission.WRITE_SYNC_SETTINGS"/>
 
     <permission android:name="{{ manifest_package }}.permission.CHILD_SERVICE" android:protectionLevel="signature" />
     <permission android:name="{{ manifest_package }}.permission.READ_WRITE_BOOKMARK_FOLDERS" android:protectionLevel="signatureOrSystem" />
     <permission android:name="{{ manifest_package }}.TOS_ACKED" android:protectionLevel="signatureOrSystem" />
@@ skipping 486 matching lines @@
         <service android:name="org.chromium.chrome.browser.notifications.NotificationService"
             android:exported="false"/>
         <receiver android:name="org.chromium.chrome.browser.notifications.NotificationService$Receiver"
             android:exported="false">
             <intent-filter>
                 <action android:name="org.chromium.chrome.browser.notifications.CLICK_NOTIFICATION" />
                 <action android:name="org.chromium.chrome.browser.notifications.CLOSE_NOTIFICATION" />
             </intent-filter>
         </receiver>
 
-        <!-- Service Worker Background Sync service listener -->
+        <!-- Service Worker Background Sync GCM scheduler task -->
         <service android:name="org.chromium.content.browser.BackgroundSyncLauncherService"
-            android:exported="false" />
-        <receiver android:name="org.chromium.content.browser.BackgroundSyncLauncherService$Receiver">
+            android:permission="com.google.android.gms.permission.BIND_NETWORK_TASK_SERVICE"
+            android:exported="true">
             <intent-filter>
-                <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
+                <action android:name="com.google.android.gms.gcm.ACTION_TASK_READY" />
             </intent-filter>
-        </receiver>
+        </service>
 
         <service android:name="org.chromium.chrome.browser.prerender.ChromePrerenderService"
             android:exported="true"
             tools:ignore="ExportedService" />
         <service android:name="org.chromium.chrome.browser.customtabs.CustomTabsConnectionService"
             android:exported="true"
             tools:ignore="ExportedService">
             <intent-filter>
               <action android:name="android.support.customtabs.action.CustomTabsService" />
             </intent-filter>
@@ skipping 86 matching lines @@
              choose the first MediaRouteController that can play it, so the order of the list can be important.
              The most specific MediaRouteControllers should be listed first, followed by more generic ones.
              The downstream manifest replaces this block, and hence replaces the list of media route
              controllers with its own list. -->
         <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
             android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
 
         {% endblock %}
     </application>
 </manifest>