Overview
Diagnosing early boot crashes, random system reboots, and kernel panics on Android is often complicated by the fact that storage encryption and logging daemons do not expose log files to user space until after the first device unlock.
Maintained by hxreborn (building upon earlier work by Jaida Wu and Howard Wu), Log-Catcher is a root logging module designed to automate system diagnostic capture across boot. It intercepts kernel ring buffers (dmesg) and Android framework logs (logcat) during startup, preserving them into organized, timestamped archive bundles upon unlock.
How It Operates
- Early Boot Interception: As soon as root daemon services initialize, Log-Catcher begins capturing the designated logcat buffers (
main,system,crash) and kernel diagnostic streams. - Post-Unlock Archiving: When the device keyguard is successfully unlocked and internal storage
/sdcard/is mounted and decrypted, the module packages the captured logs into a timestamped.tar.gzbundle inside/sdcard/Download. - Retention & Housekeeping: The service runs a housekeeping routine that checks the modification dates of existing archives, removing any logs exceeding
PRUNE_DAYSor exceeding theMAX_LOGSceiling.
Configuration
On KernelSU and APatch, you can manage configuration directly through the module’s embedded WebUI dashboard.
On Magisk, configuration is adjusted by editing /data/local/logcatcher/config:
EXPORT_PATH=/sdcard/Download
MAX_LOGS=10
PRUNE_DAYS=7
BUFFERS=main,system,crash
PERSISTENT=false
EXPORT_PATH: Directory where.tar.gzarchives are saved.MAX_LOGS: Maximum number of log archives retained before older files are deleted.PRUNE_DAYS: Age threshold (in days) after which old archives are pruned.BUFFERS: Comma-separated list of logcat buffers to record.PERSISTENT: Set totrueto keep recording logcat continuously in the background.
Installation
- Download the latest
hxr_logcat.zipfrom GitHub releases. - Install via Magisk, KernelSU, or APatch.
- Reboot your device to begin automated log collection.
