Mark Salyzyn 13aca598f8 recovery: use __android_log_pmsg_file_write for log files ... (cherry-pick from commit a4f701af93) - Add call to __android_log_pmsg_file_write for recovery logging. - Add call to refresh pmsg if we reboot back into recovery and then allow overwrite of those logs. - Add a new one-time executable recovery-refresh that refreshes pmsg in post-fs phase of init. We rely on pmsg eventually scrolling off to age the content after recovery-persist has done its job. - Add a new one-time executable recovery-persist that transfers from pmsg to /data/misc/recovery/ directory if /cache is not mounted in post-fs-data phase of init. - Build and appropriately trigger the above two as required if BOARD_CACHEIMAGE_PARTITION_SIZE is undefined. - Add some simple unit tests NB: Test failure is expected on systems that do not deliver either the recovery-persist or recovery-refresh executables, e.g. systems with /cache. Tests also require a timely reboot sequence of test to truly verify, tests provide guidance on stderr to direct. Bug: 27176738 Change-Id: I17bb95980234984f6b2087fd5941b0a3126b706b		2016-03-31 13:52:54 -07:00
..
common	Port applypatch.sh tests to recovery_component_tests	2016-03-11 18:37:34 -08:00
component	Port applypatch.sh tests to recovery_component_tests	2016-03-11 18:37:34 -08:00
testdata	Port applypatch.sh tests to recovery_component_tests	2016-03-11 18:37:34 -08:00
unit	recovery: use __android_log_pmsg_file_write for log files	2016-03-31 13:52:54 -07:00
Android.mk	recovery: use __android_log_pmsg_file_write for log files	2016-03-31 13:52:54 -07:00