I\'ve reviewed the docs and the sample BackupRestore app and written my own test app implementing android:backupAgent
. I extended the BackupAgent
clas
The outputBackup pass but e=true p=false
means the backup manager is enabled (e=true
) but not provisioned (p=false
).
It will only run backups if both of these conditions are met. So for some reason the backupmanager is not provisioned on your emulator image, after digging through the code I noticed it should get auto-provisioned during bootup (DefaultActivity)
I/ActivityManager( 73): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.sdksetup/.DefaultActivity } from pid 0
I just created a fresh emulator image, and it worked without problems there.
I also tried to use the "new" Backup Manager Service and always got following error messages:
12-01 09:58:54.420: WARN/BackupTransportService(9965): Unknown package in backup request: @pm@
12-01 09:58:54.450: WARN/BackupTransportService(9965): Not ready for backup request right now: [OperationScheduler: enabledState=false lastSuccess=2010-10-07/09:33:51 moratoriumSet=2010-12-01/09:53:32 moratorium=1970-01-01/01:00:00 trigger=1970-01-01/01:00:00]
12-01 09:58:54.450: WARN/PerformBackupThread(9965): Backup pass unsuccessful, restaging
Does anybody know what this means???
If I change backup transport to local version with following command
adb shell bmgr transport android/com.android.internal.backup.LocalTransport
everything works well. So its not a problem of my code, I think...
Regards!
Check your phone's settings. If the syncronization-service is disabled then backup via Data Backup API won't work.