| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
methods on BackupDataOutput.
|
|
|
|
|
| |
can't be stated. This means you don't need to know if the files
you are backing up exist or not -- we'll figure it out for you.
|
|
|
|
| |
This took quite a bit of refactoring.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This includes some cleanup to make the parameters match
between BackupService.onBackup and FileBackupHelper.performBackup.
|
|
|
|
|
|
| |
It took a bunch of refactoring inside BackupManagerService,
which is unfortunately all temporary anyway, but it unblocks
a bunch of stuff.
|
| |
|
| |
|
| |
|
|
|