| 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
|