Reporting issues and logs

Report bugs at https://github.com/cawilliamson/treble_restlessos/issues, not in the Telegram group.

GitHub issues are only for bugs. Don't open an issue for questions, installation help or feature discussions, use the Support & Discussions channel in the Telegram group instead.

• Attach logs as files. Don't paste long logs into the issue text or the chat.
• Only logs from a real installation are accepted, not from DSU.
• Issues from a modified system image (repacked, debloated or otherwise changed) are not accepted. Reproduce the issue on an unmodified build first.
• Don't open a new issue for every build that doesn't work. Update your existing issue with the builds you tried and what happened on each.
• If you can't get usable logs on a release build, flash a debug build from https://build.chrisaw.io and reproduce the issue there.

All commands below are run on your PC with the device connected over USB, and they save the logs on the PC.

Basic logs

These work on any build, no root needed. Reproduce the issue first, then run:

adb logcat -b all -d > logcat.txt
adb bugreport bugreport.zip

Kernel and early boot logs

These need root. On a debug build, run adb root first. In TWRP/OrangeFox, adb is already root. On a rooted release build, run them as adb shell su -c '...'.

adb shell dmesg > dmesg.txt
adb pull /sys/fs/pstore
adb pull /proc/last_kmsg

Advanced logs

Only grab these when they fit your issue or when you're asked for them.

Random reboots or soft reboots:

adb pull /proc/sec_log # Samsung only
adb pull /sys/fs/pstore
adb shell dumpsys dropbox --print SYSTEM_RESTART > dropbox_restart.txt
adb shell dumpsys dropbox --print system_server_crash > dropbox_crash.txt
adb shell dumpsys dropbox --print system_server_watchdog > dropbox_watchdog.txt
adb shell dumpsys dropbox --print system_server_anr > dropbox_anr.txt

Bootloops and early boot crashes (works without a running system, e.g. from recovery when /data is decrypted):

adb exec-out tar czf - -C /data/system dropbox > dropbox.tgz
adb exec-out tar czf - -C /data tombstones > tombstones.tgz

Single logcat buffers:

adb logcat -b events -d > logcat_events.txt
adb logcat -b crash -d > logcat_crash.txt
adb logcat -b kernel -d > logcat_kernel.txt

Memory and swap (out-of-memory issues):

adb shell cat /proc/meminfo > meminfo.txt
adb shell cat /proc/vmstat > vmstat.txt
adb shell dumpsys meminfo > dumpsys_meminfo.txt

MediaTek devices, expdb partition (from recovery):

adb exec-out cat /dev/block/by-name/expdb > expdb.img
strings expdb.img > expdb.txt

Without a PC

The same commands work in an on-device shell such as Termux or aShell You. Drop the adb shell / adb exec-out prefix, run root commands with su -c '...' and write the output to /sdcard/, for example:

su -c 'logcat -b all -d' > /sdcard/logcat.txt

If an issue needs SELinux in permissive mode to reproduce, see SELinux permissive for debugging.