summaryrefslogtreecommitdiffstats
path: root/tests/ImfTest/AndroidManifest.xml
diff options
context:
space:
mode:
authorChristopher Tate <ctate@google.com>2009-05-14 11:12:14 -0700
committerChristopher Tate <ctate@google.com>2009-05-31 13:10:03 -0700
commit181fafaf48208978b8ba2022683ffa78aaeddde1 (patch)
tree7c062847d418415e28813e70aac53c8c47e4ff69 /tests/ImfTest/AndroidManifest.xml
parentc01159bb00f7273f9b051dfbbe6bc10d54d3a846 (diff)
downloadframeworks_base-181fafaf48208978b8ba2022683ffa78aaeddde1.zip
frameworks_base-181fafaf48208978b8ba2022683ffa78aaeddde1.tar.gz
frameworks_base-181fafaf48208978b8ba2022683ffa78aaeddde1.tar.bz2
Retool the backup process to use a new 'BackupAgent' class
Backups will be handled by launching the application in a special mode under which no activities or services will be started, only the BackupAgent subclass named in the app's android:backupAgent manifest property. This takes the place of the BackupService class used earlier during development. In the cases of *full* backup or restore, an application that does not supply its own BackupAgent will be launched in a restricted manner; in particular, it will be using the default Application class rather than any manifest-declared one. This ensures that the app is not running any code that may try to manipulate its data while the backup system reads/writes its data set.
Diffstat (limited to 'tests/ImfTest/AndroidManifest.xml')
0 files changed, 0 insertions, 0 deletions