summaryrefslogtreecommitdiffstats
path: root/tests/backup
Commit message (Collapse)AuthorAgeFilesLines
* frameworks/base refactoringMathias Agopian2012-02-201-1/+1
| | | | | | create the new libandroidfw from parts of libui and libutils Change-Id: I1584995616fff5d527a2aba63921b682a6194d58
* frameworks/base refactoring.Mathias Agopian2012-02-171-1/+1
| | | | | | step 2: move libutils headers to their new home: androidfw Change-Id: I14624ba23db92a81f2cb929f104386e1fab293ef
* API CHANGE: rename BackupHelperAgent => BackupAgentHelper per API CouncilChristopher Tate2010-03-291-2/+2
| | | | | | Part of bug #2545514 Change-Id: Ic775e3b942c485252149c1b6c15c88517fa4e3e5
* Refactor android.backup => android.app.backupChristopher Tate2010-03-052-8/+8
| | | | Change-Id: I0b21316ff890d7f3c7d4b82837bb60670724c2e8
* Fix Proguard flags.Ying Wang2010-03-021-0/+2
|
* Automatically restore app data at install timeChristopher Tate2010-02-191-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When an application being installed defines a backupAgent in its manifest, we now automatically perform a restore of the latest-known-good data for that app. This is defined as "data backed up by this app from this handset, if available; otherwise data for this app as it existed when the device was initially provisioned." If neither option exists for the app, no restore action is taken. The CL involves major changes in the Backup and Package Managers... * The Package Manager's act of installing an application has now been split into two separate phases, with a data-restore phase optionally occurring between these two PM actions. First, the details of the install are performed as usual. Instead of immediately notifying install observers and issuing the install-related broadcasts, the in-process install state is snapshotted and the backup manager notified that a restore operation should be attempted. It does this by calling a new API on IBackupManager, passing a token by which it identifies its in-progress install state. The backup manager then downloads [if possible] the data for the newly-installed application and invokes the app's backupAgent to do the restore. After this step, regardless of failure, it then calls back into the Package Manager to indicate that the restore phase has been completed, supplying the token that was passed in the original notification from the Package Manager. The Package Manager then runs the final post-install actions: notifying install observers and sending out all the appropriate broadcasts. It's only at this point that the app becomes visible to the Launcher and the rest of the OS. ... and a few other bits and pieces... * The ApplicationInfo.backupAgentName field has been exposed to the SDK. This can be reverted if there's a reason to do so, but it wasn't clear that this info needs to be hidden from 3rd party apps. * Debug logging of restore set IDs and operation timeout tokens [used during any asynchronous Backup Manager operation] are now consistently in hex for readability. * We now properly reset our binder identity before calling into the transport during restore-set operations. This fixes a permissions failure when a single-app restore was attempted. * The 'BackupTest' test app is no longer lumped onto the system partition by default. Change-Id: If3addefb846791f327e2a221de97c8d5d20ee7b3
* Remove BACKUP_DATA permission and associated checksChristopher Tate2010-02-121-1/+0
| | | | | | | | Any package can now participate in backup/restore, without requiring any manifest-declared permission. *Control* of the backup manager is still guarded by the BACKUP permission, which is signatureOrSystem. Change-Id: I116fcfcd4cd255e3c976330da1c4dea7d4faae9d
* Revive backup testsOmari Stephens2009-12-022-4/+6
|
* Merge change 20918Android (Google) Code Review2009-08-132-1/+67
|\ | | | | | | | | * changes: Wrap up the stress test into a single script make test_restore.sh return a value signifying success or failure
| * Wrap up the stress test into a single scriptOmari Stephens2009-08-122-1/+67
| | | | | | | | make test_restore.sh return a value signifying success or failure
* | Backup participants must now hold the BACKUP_DATA permissionChristopher Tate2009-08-131-0/+1
|/ | | | | | | | Packages that do not use android.permission.BACKUP_DATA will neither be backed up nor restored. That permission is currently signature-only. In the future if access to the backup/restore infrastructure is made available to arbitrary 3rd party applications, the permission checks (and indeed, the permission itself) can simply be removed.
* git rid of the "x" prefixes for testOmari Stephens2009-08-111-1/+1
|
* The triumphant return of the shell scripts, with bugreports, less code dup, andOmari Stephens2009-08-113-50/+96
| | | | enhanced readability.
* Wipe data on backend before a backup runOmari Stephens2009-08-062-4/+23
| | | | | | | Append the date to 3.txt so that we can see if/when backup failures occurred solely from the device/server state Note that these files will probably be deleted from the tree immediately, to be replaced by the ruby versions.
* Make test_backup and test_restore usable againOmari Stephens2009-08-032-24/+84
| | | | | | | - Add copyright headers - Allow the user to pass options (like '-s FOO') to adb - Restart device adb as root if needed - Make test_restore to infer a restore set
* BackupManager wrapper class improvementsChristopher Tate2009-07-071-8/+6
| | | | | | | | | | | | | + Now rechecks the cached IBinder each time the wrapper is used, and if it's still null (i.e. the BackupManager was constructed before the system service came up) it's refetched. This lets even system code cache a single BackupManager instance and just keep making calls through it without worrying about interactions with the life cycle of the backup service. + Added a static dataChanged(packageName) method as a convenience for code that needs to indicate that some other package needs a backup pass. This is useful even for third party code in the case of multiple packages in a shared-uid situation.
* Add a test for SharedPreferencesBackupHelperJoe Onorato2009-06-263-6/+20
| | | | | (which nobody had ever tested. I like it when stuff just works the first time).
* Test that we correctly back up an empty file.Joe Onorato2009-06-263-1/+4
| | | | | (It turns out that we do. It didn't used to work, I'm not sure what changed)
* Add some helpful tests scripts for backup and make bmgr restore wait until ↵Joe Onorato2009-06-253-1/+67
| | | | the backup is done.
* Make the BackupHelperDispatcher properly handle multiple helpers.Joe Onorato2009-06-251-0/+1
|
* Pass the originating app's versionCode along with a restore setChristopher Tate2009-06-221-1/+2
| | | | | | | This change amends the doRestore() / onRestore() interface to backup agents to provide the integer android:versionCode of the app that stored the backup set. This should help agents figure out how to handle whatever historical data set they're handed at restore time.
* Helper API cleanup. Allows multiple helpers to function,Joe Onorato2009-06-222-45/+11
| | | | | because they'll always go in the same order, and this lets us not have to write headers to keep them paired.
* Make RestoreHelper and friends also write out the snapshot state.Joe Onorato2009-06-182-2/+7
|
* backup fixes:Joe Onorato2009-06-172-7/+23
| | | | | | - BackupTestAgent calls the DispatchHelper - Make BackupAgent.onRestore take a BackupDataInput, not just a generic ParcelFileDescriptor.
* FileRestoreHelper and RestoreHelperDispatcher work.Joe Onorato2009-06-171-3/+57
|
* Add RestoreFileHelper, BackupDataInput, and add java wrappers for the ↵Joe Onorato2009-06-121-1/+2
| | | | methods on BackupDataOutput.
* Make the file backup helper not crash if a file you requestedJoe Onorato2009-06-111-0/+1
| | | | | 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.
* Fix SharedPrefsBackupHelper so it doesn't hard code the paths to the files.Joe Onorato2009-06-111-0/+1
| | | | This took quite a bit of refactoring.
* rename a few files to camel-case, add copyright noticesMathias Agopian2009-06-041-1/+17
|
* Retool the backup process to use a new 'BackupAgent' classChristopher Tate2009-05-312-9/+4
| | | | | | | | | | | | | | | 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.
* Hook up the backup data writer, and add a utility to read the backup data files.Joe Onorato2009-05-201-2/+2
|
* Add the backup data file writer C++ class.Joe Onorato2009-05-151-0/+1
|
* Implement the C++ class to write the backed up file data.Joe Onorato2009-05-151-0/+3
|
* Get the backup calling through to the file backup helper.Joe Onorato2009-05-142-3/+28
| | | | | This includes some cleanup to make the parameters match between BackupService.onBackup and FileBackupHelper.performBackup.
* With this, the BackupService onBackup method is called.Joe Onorato2009-05-131-1/+1
| | | | | | It took a bunch of refactoring inside BackupManagerService, which is unfortunately all temporary anyway, but it unblocks a bunch of stuff.
* fix the sim build. disables the tests for now.Joe Onorato2009-05-081-3/+10
|
* More backup testsJoe Onorato2009-05-073-3/+47
|
* Add a test app for the backupJoe Onorato2009-05-054-0/+164
|
* Add some C++ code to do raw files for backupJoe Onorato2009-05-052-0/+123
generated by cgit v1.1 at 2024-05-17 07:11:36 +0000