Move Call Log backup into it's own package.
Moves the call log backup from the contacts provider into it's own
package. This should make it easier to support backup through the same
package name for OEMs which revise (and rename) the contacts provider.
Also add a CallLogChangeReceiver to receive notices from the
CallLogProvider when the call log changes. When this happens, the
receiver notifies the backup manager that it should run a backup at it's
earliest convenience.
Change-Id: I5774bba333a83adf53e1733f80a3df9e8140adb8
diff --git a/AndroidManifest.xml b/AndroidManifest.xml
index 0654e39..bf486de 100644
--- a/AndroidManifest.xml
+++ b/AndroidManifest.xml
@@ -1,12 +1,22 @@
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
- package="com.android.providers.calllog"
+ package="com.android.providers.calllogbackup"
android:sharedUserId="android.uid.shared"
android:sharedUserLabel="@string/sharedUserLabel">
- <application android:process="android.process.acore"
- android:label="@string/app_label"
+ <application android:label="@string/app_label"
android:icon="@drawable/app_icon"
- android:allowBackup="true">
+ android:allowBackup="true"
+ android:backupAgent="CallLogBackupAgent">
+ <meta-data android:name="com.google.android.backup.api_key"
+ android:value="AEdPqrEAAAAISbHhhUji6KZyyjz4I8-MdBqlnoiTJoFAEUHHzA" />
+
+ <receiver android:name="CallLogChangeReceiver"
+ android:permission="android.permission.SEND_CALL_LOG_CHANGE">
+ <!-- Sent when the call log changes. We use it to trigger a backup request. -->
+ <intent-filter>
+ <action android:name="android.intent.action.CALL_LOG_CHANGE" />
+ </intent-filter>
+ </receiver>
</application>
</manifest>