replicant-frameworks_native

History

Dianne Hackborn 7b92d7ec36 Debugging for issue #2228381 android.view.InflateException Binary XML file line #37: Error inflating class <unknown> after adding a secondary account Now that I have these debug logs, I want to keep them since they will make debugging these kinds of issues a lot easier in the future. (Note in this case there was no problem in the framework.) Change-Id: If2b0bbeda4706b7c5dc1ba4a5db04b74f40e1543		2009-11-20 14:26:42 -08:00
..
Android.mk
Asset.cpp
AssetDir.cpp
AssetManager.cpp
BackupData.cpp	Turn off most of the backup-related debug logging	2009-09-30 17:07:37 -07:00
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp	Debugging for issue #2228381 android.view.InflateException	2009-11-20 14:26:42 -08:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp
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

README

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.