| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The core logging in BackupManagerService and in the Google backup transport are
still enabled at this point.
Change-Id: I10abfa565bbd1097dd3631051b6aca163e4af33a
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Turning off backup in the Settings UI constitutes an opt-out of the whole
mechanism. For privacy reasons we instruct the backend to wipe all of the data
belonging to this device when the user does this. If the attempt fails it is
rescheduled in the future based on the transport's requestBackupTime()
suggestion. If network connectivity changes prompt the transport to indicate a
backup pass is appropriate "now," any pending init operation is processed before
the backup schedule is resumed.
The broadcasts used internally to the backup manager are now fully protected;
third party apps can neither send nor receive them.
(Also a minor logging change; don't log 'appropriate' EOF encountered during
parsing of a backup data stream.)
|
| | |
|
| |
|
|
| |
the end.
|
| |
|
|
|
| |
m_dataEndPos points to the end of the data, not the beginning
of the next entity.
|
| | |
|
| |
|
|
|
| |
because they'll always go in the same order, and this lets
us not have to write headers to keep them paired.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
methods on BackupDataOutput.
|
| |
|
