replicant-frameworks_native/libs/utils
Christopher Tate 6e472890ef Clear the device's data from the transport when backup is disabled
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.)
2009-09-24 11:19:04 -07:00
..
Android.mk implement Mutex and Condition with pthread instead of calling futex directly. 2009-07-13 15:14:23 -07:00
Asset.cpp Fix issue #2048263: More debugging information 2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp Don't re-parse the framework resources all the time. 2009-07-06 11:12:37 -07:00
BackupData.cpp Clear the device's data from the transport when backup is disabled 2009-09-24 11:19:04 -07:00
BackupHelpers.cpp Better (and less) logging from backup. 2009-06-26 17:19:11 -04:00
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp Fix issue #1862317: Browser does not appear to honor anchors (#es) in links 2009-09-20 12:40:03 -07:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp quick fix; utf8_codepoint_count must be utf8_length 2009-07-09 13:05:24 +09:00
String16.cpp
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp use broadcast() instead of signal() when signaling the condition-variable Thread::RequestExitAndWait() is waiting for 2009-09-09 02:45:26 -07:00
Timers.cpp
Unicode.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp fix FILE* version of ZipUtils::inflateToBuffer 2009-07-16 11:27:13 -07:00

Android Utility Function Library

If you need a feature that is native to Linux but not present on other
platforms, construct a platform-dependent implementation that shares
the Linux interface.  That way the actual device runs as "light" as
possible.

If that isn't feasible, create a system-independent interface and hide
the details.

The ultimate goal is *not* to create a super-duper platform abstraction
layer.  The goal is to provide an optimized solution for Linux with
reasonable implementations for other platforms.