Loggingkit Pack

Changes :

• Updating Windows, MacOS and Linux executables
• Include MacOS and Linux executables
• Latest windows bins

ADB Changelog:

• Support forwarding to vsock on linux.
• Fix bug in adb track-devices where devices over wireless debugging wouldn't immediately receive updates.
• Implement preliminary support for mDNS device discovery without a separately installed mDNS service. This is currently disabled by default, and can be enabled by setting the environment variable ADB_MDNS_OPENSCREEN to 1 when starting the adb server.

---

How to gather logs with LoggingKit

[With booted System] - Intended for Crashes, FCs and other SYSTEM Logs

1. 1. For Windows users: Install Universal ADB drivers or Brand specific ADB drivers if you don't have them
   2. For Linux and macOS users: To make the files executable, type in Terminal chmod +x and drag the files
2. On your phone enable USB debugging under Developer options
3. Launch your required log type (to find out which logs you should gather, check Legend)
4. Grant ADB Keys
5. Close your log type
6. Launch the needed log, again
7. 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 (Until you stop)

• 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.bat if you previously allowed your computer ADB