diff options
| author | Christopher Tate <ctate@google.com> | 2012-05-17 14:59:41 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2012-05-17 16:02:15 -0700 |
| commit | 97ea122c6526125e64213e9c10d9c20f9bc70d9c (patch) | |
| tree | 9fc67c0719b29191484a2f0449374dfb2be54144 /core/java | |
| parent | 9cb376e792567b5278e0eb418a3aeb848339a283 (diff) | |
| download | frameworks_base-97ea122c6526125e64213e9c10d9c20f9bc70d9c.zip frameworks_base-97ea122c6526125e64213e9c10d9c20f9bc70d9c.tar.gz frameworks_base-97ea122c6526125e64213e9c10d9c20f9bc70d9c.tar.bz2 | |
Eliminate "backup enabled but not provisioned" failure modes
Previously, the setup app was responsible for telling the backup
manager through a side band that the user had passed through the
backup/restore-related portion of the setup flow. Now that the
flow has been streamlined and certain mandatory portions of it
are no longer relevant, we can ditch the whole idea of the backup
manager's internal "provisioned" state. This makes setup and the
setup "wizard" applications less fragile as well as eliminating
the possibility of unrecoverable "backup was never provisioned"
failure modes.
Now, the only check the backup manager has to do is against the
full "device is provisioned" flag, just like all of the other
components on the phone that only become usable after the setup
process has exited [such as phone calls].
Bug 6493520
Change-Id: I13ec8dd8baa1e74ed8569b0326219a98a7f632a9
Diffstat (limited to 'core/java')
0 files changed, 0 insertions, 0 deletions