Android Logger Booting records logs during Android startup and stores the results under /data/local/logger. It gives ROM and module developers a persistent record of early runtime errors that may be difficult to collect after a failed or unstable boot.
Persistent Startup Diagnostics
Collect evidence first, then use the captured timestamps, process names, and crash messages to narrow down a boot problem.
Boot-Time Capture
Logging begins as Android starts, covering failures that occur before a user can open a terminal and run a manual logging command.
Known Output Path
Saved files remain grouped in /data/local/logger, making them straightforward to retrieve with a root file manager, terminal, or ADB.
Developer Focus
The module was created while diagnosing systemless LiteGapps boot issues, but the same records can help investigate other ROM and module failures.
Reviewing a Failed Boot
After reproducing the problem, boot into a state where /data is accessible and copy the complete logger directory before testing another change. Review the newest files first and correlate fatal signals, service restarts, SELinux denials, and repeated process crashes by timestamp.
Change one variable at a time. Disable the suspected module or component, reproduce the boot, and compare the next log set with the saved baseline. This makes the logger useful as evidence, not merely a large stream of unrelated messages.