| 1398e27bb0f5768cbbd5b9d9fd7c8675da63ccb0 |
|
06-Apr-2010 |
Christopher Tate <ctate@google.com> |
Fix 'bmgr restore'
Zero means success. Fixes bug #2573785
Change-Id: I11bd4d85aa2b3a061aa37e085790ee8cd52d50a2
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 2d449afe3d075020bdd1115bcc15c9383cbce122 |
|
30-Mar-2010 |
Christopher Tate <ctate@google.com> |
Make RestoreSession.getAvailableRestoreSets() asynchronous
This transaction can involve the transport having to query a remote backend
over the wire, so it can take a Long Time(tm). Make it main-thread-safe by
making it asynchronous, with the results passed as a callback to the invoker's
RestoreObserver. We also make the IRestoreObserver callback interface
properly oneway.
Bug #2550665
Bug #2549422
Change-Id: If18a233a0a3d54c7b55101715c9e6195b762c5a0
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 9c3cee9824026764275e4d84ba9b5d9fdc5da690 |
|
26-Mar-2010 |
Christopher Tate <ctate@google.com> |
API CHANGE: Backup/restore API changes requested by the API Council
* @hide the android.app.backup.RestoreSession class and functionality
* Provide a public method on android.app.backup.BackupManager that apps
can use to request a restore pass of their last-known-good dataset.
The new method is called requestRestore().
* Provide the name of the package being restored, not just its ordinal,
in the RestoreObserver's onUpdate() callback.
Part of bug #2545514
Change-Id: I9689bf8d6e2b808b4ee412424a36a835be0a5ca8
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 4528186e0d65fc68ef0dd1941aa2ac8aefcd55a3 |
|
06-Mar-2010 |
Christopher Tate <ctate@google.com> |
Refactor android.backup => android.app.backup
Change-Id: I0b21316ff890d7f3c7d4b82837bb60670724c2e8
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 485c3a16cef38136a821e79a5fe37df4e1779d28 |
|
04-Mar-2010 |
Christian Sonntag <cxs@google.com> |
fix hex parsing of bmgr
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 7d411a3b947ba82d1d57f73c0fa698c3b9c95892 |
|
26-Feb-2010 |
Christopher Tate <ctate@google.com> |
Add single-package restore to Bmgr feature set
Also sanity-check the package name on the Backup Manager side, failing gracefully
if the given package is not a backup/restore participant.
Bug: 2293977
Change-Id: I3575046ffcaa3cf45c1c602824baeadd64082f70
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 8472581aa32eee1368de379c2c079ea0a66baa3c |
|
05-Feb-2010 |
Christopher Tate <ctate@google.com> |
Add single-package restore from an app's most-recent data
Renamed the RestoreSession performRestore() method to restoreAll(), and
added a new restorePackage() method that only restores the single
specified app. In order to restore an app other than itself, the
caller must hold the android.permission.BACKUP permission.
This change also introduces dataset tracking: the Backup Manager
persistently remembers both the current backup dataset's identity
and that of the "ancestral" dataset, i.e. the one most recently used
for a whole-device restore such as performed by SetupWizard. When a
single package is restored via restorePackage(), the selection of
most-recent dataset to use is this:
1. The data from the currently-active backup dataset, if such exists.
An app that has ever backed up data will therefore get its last-
known-good data.
2. The app's data from the ancestral dataset, if such exists. This
covers the case of a factory reset followed by reinstallation of
an app at a later time. The app had not yet backed anything up
post-wipe, but the old data is in the ancestral dataset and should
be brought forward when the app reappears.
3. If neither 1. nor 2. exist, there is no data to restore, so just
skip it and return failure.
Note that the infrastructure to automatically attempt a restore after
an application has been installed does not yet exist; that's coming.
Change-Id: I0ba170df9885128000c46ed28d3dddda3a63a143
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 0e0b4ae5bc5c652c8339d71ed9667e1e37baaa03 |
|
11-Aug-2009 |
Christopher Tate <ctate@android.com> |
Don't let bmgr leave a restore session hanging on error
Specifically, don't wait for the RestoreObserver to be informed that the restore
has completed unless performRestore() ran. We were winding up in a case where
bmgr was hanging forever waiting on a nonexistent restore process instead of
calling endRestoreSession().
Also improve the documentation, explicitly calling out the need to call
endRestoreSession() even if previous operations on the session were
unsuccessful.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 84780f56f441deb4ff736987986daeaf64db17a4 |
|
08-Aug-2009 |
Christopher Tate <ctate@android.com> |
Don't crash if the Backup Manager returns a null RestoreSet[]
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 77095d49f203eed6a6742f2605ca319e7360af32 |
|
07-Aug-2009 |
Christian Sonntag <cxs@android.com> |
make restore tokens shown in hex.
Since they are android ids, it is much easier to use them as hex, since we can just copy then into android inspector and learn more about the restore set.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 08e40b858e8a3266c5519a83fda6f7505f1c14db |
|
07-Aug-2009 |
Christopher Tate <ctate@android.com> |
Fix Bmgr's logic around restore completion
The caller needs to wait for the restore observer to be informed that the
restore has finished processing before it can safely shut down the restore
session.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| d23d7f2d12c20314e1e8ff206fafc8f21745ca2d |
|
02-Jul-2009 |
Christopher Tate <ctate@google.com> |
Add a 'wipe' operation to Bmgr
"bmgr wipe PACKAGE" now issues the backup transport clearBackupData() operation
for the given package.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 6ef58a1509b9d3348a33ca5686917796c2759aa5 |
|
29-Jun-2009 |
Christopher Tate <ctate@google.com> |
Implement persistent enable/disable of the backup manager
Backup & restore is still enabled by default, but with the expectation that it
will be enabled during the course of the Setup Wizard or some other privileged
entity that has notified the user about the ramifications. While disabled,
data-changed notices will still be collected, but no backup pass will be
scheduled. When the backup manager is later enabled, any pending data-changed
notices will then be processed and the apps invoked for backup.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 9171749700853305f3e6abbcdbd9e02f3a71d459 |
|
27-Jun-2009 |
Christopher Tate <ctate@google.com> |
Use system properties to track the current transport
This change retools the transport selection mechanism a fair bit. Transports
are now specified by name rather than by numeric ID, and the name of the
currently selected transport is stored in a persistent system property under the
name "persist.service.bkup.trans".
The name -> IBackupTransport translation is now handled by maintaining a map
from the names to the live IBackupTransport objects that correspond. The Google
transport service observer now registers and unregisters the transport as the
service goes up and down.
The bmgr command has been expanded to include real transport interrogation and
selection by name, and some documentation has been written for it.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 156411df4627336b246db78cddca8248ed615b67 |
|
26-Jun-2009 |
Dan Egnor <egnor@google.com> |
Use a long for restore token
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| c73a218c2663e6ae3ec8a9ab8b9524f95702ade9 |
|
26-Jun-2009 |
Christopher Tate <ctate@google.com> |
Add some error reporting & info to bmgr's output
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 4a64bded06a0299785c295a975e2818308eb53e2 |
|
26-Jun-2009 |
Joe Onorato <joeo@android.com> |
Add some helpful tests scripts for backup and make bmgr restore wait until the backup is done.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| 5e8a4b842c20dd47b82e9915f1bd730ee1b0d46d |
|
26-Jun-2009 |
Joe Onorato <joeo@android.com> |
Give the bmgr command an IRestoreObserver too.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| abce4e8714bed26a2b37b20ad3f02cf619d71c9a |
|
19-Jun-2009 |
Christopher Tate <ctate@google.com> |
Use signatures on restore
On restore now, the backup manager gets the signature blocks corresponding to
the restore set from the transport. It then validates those signatures against
the on-device app signatures, and refuses to restore data to an app whose
on-device sig block does not match the backup image's.
Also actually implement 'bmgr transport N' so that we can select the local
transport easily during runtime.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| f68eb500f99361541049e09eb7f9ddd6f4ef4efa |
|
16-Jun-2009 |
Christopher Tate <ctate@google.com> |
More bmgr work; fix clear-data signalling
The 'list sets' and 'restore token#' commands from bmgr now do what they are
supposed to. At this point we see the restore target's data being cleared
properly and its agent being launched and invoked for restore.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|
| ace7f094bf07bbd90cb998b9462e4f2d101a498c |
|
16-Jun-2009 |
Christopher Tate <ctate@google.com> |
Sketch out a 'bmgr' command line tool
Not finished, but eventually will allow adb shell access to the Backup Manager
for testing purposes etc.
/frameworks/base/cmds/bmgr/src/com/android/commands/bmgr/Bmgr.java
|