commit 73570db59f9178cf3a8affe943e96808ac404049
author Christopher Tate <ctate@google.com> Thu Feb 26 19:32:55 2015 -0800
committer Christopher Tate <ctate@google.com> Mon Mar 02 18:01:28 2015 -0800
tree fa500a58f47332bd66315f6c55c43eb85cdd3930
parent 20d58e2af7738209b068038197db516d365d887a

Use scheduled job rather than periodic alarms for key/value backups

Instead of a runs-forever periodic alarm that drives key/value backup
passes, we instead schedule-on-demand a trigger job that will kick off
the pass after a batching interval.  The key semantic change is that
we now never wake for key/value backup work unless we've been explicitly
asked to do so.  We also use a rather longer batching interval than
was previously the case.

Bug 19536032

Change-Id: Ie377562b2812c9aeda0ee73770dfa94af6017778

core/res/AndroidManifest.xml

diff --git a/core/res/AndroidManifest.xml b/core/res/AndroidManifest.xml
index 0d15ae54..b550558 100644
--- a/core/res/AndroidManifest.xml
+++ b/core/res/AndroidManifest.xml
@@ -3188,6 +3188,10 @@
                  android:permission="android.permission.BIND_JOB_SERVICE" >
         </service>
 
+        <service android:name="com.android.server.backup.KeyValueBackupJob"
+                 android:permission="android.permission.BIND_JOB_SERVICE" >
+        </service>
+
         <service
             android:name="com.android.server.pm.BackgroundDexOptService"
             android:exported="true"