| 5092dea7f5d82a536308f9fc8c6684ae82c1ba42 |
|
03-May-2017 |
Christopher Tate <ctate@google.com> |
Correct scope of "disabled?" check viz backup/restore decisions
*Really* don't back up or restore data for disabled apps.
Bug 37851910
Test: manual
Change-Id: I4b9bdcabb386789b03633d9d26775e54bf3c3d03
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| 590096a0e372f640fb41d4cb97d8bc68fb7b8ea2 |
|
26-Mar-2016 |
Makoto Onuki <omakoto@google.com> |
Extract signature related utilities
So that they can be used from services/core.
Bug 27548047
Change-Id: I610e267cba320418e766c0e609fa26c485dc6e1f
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| 03d64a52105ce6eada02bf030e1a746c226fd8b1 |
|
26-May-2015 |
Christopher Tate <ctate@google.com> |
Don't erase backup metadata when an app is uninstalled
We still retain the data in the backup, in order to support the flow
in which a user has the app and its data is stored; then the app
is uninstalled; then later the app is reinstalled. We depend on
having correct metadata for the data in the datastore in order to
evaluate its validity for restore-at-install, so we mustn't
forget that metadata just because the app is not currently
installed.
We also now permit the sentinel pseudopackage name "@pm@" as an
argument to dataChanged(), indicating specifically that the metadata
should be scheduled for backup without having to be piggybacked on
another app's requested backup pass. That lets us now make sure to
schedule a backup pass for metadata-update in response to app
install activity.
Finally, fix a "min instead of max" bug in full backup scheduling
that was causing the OS to ignore the transport's inter-package
quiet time requirement when multiple packages were overdue for
backup.
Bug 21471973
Change-Id: I1dbc260edb91b8deadd2744e273dfa9578b9ef2a
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| 22192ada99691221f9ab167c046fb71c23baf723 |
|
05-Dec-2014 |
Christopher Tate <ctate@google.com> |
Correctly parse previous PMBA state during backup
Bug 18628030
Change-Id: Iefa23de50dd9e1b27cfa5d887f117876d57e4083
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| f7cbb1fc25223bbf793f7128280ee4b00d509eb0 |
|
22-Jul-2014 |
Christopher Tate <ctate@google.com> |
Always check restore against the latest backend metadata
Bug 16484934
Change-Id: I472a7db89a94b9804f6ea94c25da206dd111a497
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| 51fea57e06fcb1dab1d239a5fff6e75ba2b7cee7 |
|
24-Jun-2014 |
Christopher Tate <ctate@google.com> |
Refactor restore to deal with heterogeneous datasets
Transport-based restore now handles both key/value and full-data
(stream) data delivery.
Also: PMBA now holds metadata for *all* apps, not just those with
backup agents. Since we need to consult this for every restore-
at-install operation we cache this locally now, tagged per transport
and per remote dataset, to avoid having to re-download it as part
of every future restore operation.
Also fixed a bug in LocalTransport that was preventing restore of
key/value datasets, i.e. all of them that were nominally available
prior to this change.
NOTE: at present there is no automatic full-data backup; if for
testing purposes you need to create some to then use for restore,
you still need to use 'bmgr fullbackup ...' to push them.
NOTE: at present the unified transport restore uses a refactored
"engine" implementation to handle stream data that encapsulates
the existing "adb restore" implementation. However, the adb
restore code path has not yet been refactored to wrap the newly-
extracted engine version; it still contains its own copy of all
the relevant logic. This will change in a future CL, at which
point offline/USB archive restore will simply wrap the same
shared stream-restore engine implementation.
Bug 15330073
Bug 15989617
Change-Id: Ieedb18fd7836ad31ba24656ec9feaaf69e164af8
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| d4659698fe2c8d854089138000ec24193d8359b8 |
|
09-Apr-2014 |
Christopher Tate <ctate@google.com> |
Don't crash on null installer package bookkeeping.
Bug 13906859
Change-Id: I926ccc5620abae8b97bd2b7de21b82b7729e78dd
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| a99d02170bc0e54f729b2b735571c8eea8d5034d |
|
05-Apr-2014 |
Christopher Tate <ctate@google.com> |
Back up the preferred home app, if any
If the user has stated a preference about their home app, make sure we
capture that so that a system restore can return them to that preferred
situation. It's built into the system metadata so that we can, if
necessary, fast-path configuration of that home app while the rest of
the restore operation is in flight.
Change-Id: I64dfee8f7a2a9e40f556cd19298d7b367c6aa8dc
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|
| 9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories
Refactored the directory structure so that services can be optionally
excluded. This is step 1. Will be followed by another change that makes
it possible to remove services from the build.
Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/backup/java/com/android/server/backup/PackageManagerBackupAgent.java
|