diff options
author | Christopher Tate <ctate@google.com> | 2015-01-29 13:17:37 -0800 |
---|---|---|
committer | Christopher Tate <ctate@google.com> | 2015-01-29 15:47:43 -0800 |
commit | e77c12ba37b7358ef6b6a6010e778926cc4194b8 (patch) | |
tree | 7220c96c1f5da422c8681ffe6082c0f2fb2e4501 /wifi/java | |
parent | 6efc3ac6d2094c72b6a2e288101a5349b017274d (diff) | |
download | frameworks_base-e77c12ba37b7358ef6b6a6010e778926cc4194b8.zip frameworks_base-e77c12ba37b7358ef6b6a6010e778926cc4194b8.tar.gz frameworks_base-e77c12ba37b7358ef6b6a6010e778926cc4194b8.tar.bz2 |
Don't run full-data backups when backup is disabled
If the scheduled job fires but backup is disabled or the device is
not yet provisioned (i.e. has not yet finished going through setup),
bow out gracefully without running any backup operations. Also, even
if a backup is directly invoked (e.g. via adb), verify again right
before we start collecting app data, and abandon the operation in
that path as well.
(This is redundant; having only the latter test would suffice, but
this lets us distinguish in the logging more easily.)
Finally, make sure that if we were waiting on setup before permitting
backup operations to begin, that we startup the full-data scheduling
as well as the [separate] key/value scheduling.
Bug 19197062
Change-Id: I3d8fb650c50f946d8ed7ac7170df361c707f2528
Diffstat (limited to 'wifi/java')
0 files changed, 0 insertions, 0 deletions