Changes :-
- Include MacOS and Linux executables
- Latest windows bins
How to gather logs with LoggingKit
[With booted System] - Intended for Crashes, FCs and other SYSTEM Logs
-
- For Windows users: Install Universal ADB drivers or Brand specific ADB drivers if you don't have them
- For Linux and macOS users: To make the files executable, type in Terminal
chmod +xand drag the files
- On your phone enable USB debugging under
Developer options - Launch your required log type (to find out which logs you should gather, check Legend)
- Grant
ADB Keys - Close your log type
- Launch the needed log, again
- After recording log, attach the created file to your GitHub issue post.
Legend
| Log type | Description |
|---|---|
| log-ball | Full buffer logcat. Don't use unless requested |
| log-all | Verbose logcat, messy but records everything |
| log-e | Log for Error filter, only shows crashes |
| log-ril | Log for Modem/SIM and other RIL issues |
| log-kmsg | Log for Kernel msg when the kernel panics |
| log-dmsg | Log for Kernel on an active system |
| log-ActiveDmesg | Looping Log for Kernel on active system |
- Being stuck at
"Waiting For Device"means you either did not auth the adb key or your device does not even have debugging enabled - Extra: You can skip step 3/4 by running
ADB_Keys.batif you previously allowed your computer ADB