How To Capture the ADB Log From a Device

The ADB log may be required when troubleshooting issues on a device, especially when investigation is required from the SOTI development team.

Android Enterprise

1. Before the user can capture the ADB log, they must first download the ADB tool on the Windows machine to which the device will be connected via USB:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

2. After downloading, extract the contents to the directory: For instance, C:\ADB

3. Log in to the web console, navigate to the Device Group and select the target device.

4. Select the Configurations tab and scroll down until you find Advanced Configuration > Connection Settings to enable debug logging.

5. Enable the Override Settings Inherited From Parent Group toggle.

6. Under the Log File Management section, increase the maximum size to 15000 KB. (The value can be adjusted based on the space available on the device)

7. Enable the toggle Enable Debug Logging on Device (Normally Off).

8. Select Save.

Note: Steps 3 through 8 above are required to enable additional logging for the SOTI MobiControl device agent and are optional when only collecting the ADB logs.

9. Create or update the existing Profile with Feature Control in the SOTI MobiControl web console to enable USB debugging.

10. Connect the device to your computer or laptop using a USB cable.

11. Open a command prompt as administrator and run the following command:

adb logcat -v threadtime *:V>> C:\ADB\adblogfile.txt

12. Reproduce the issue on the device so it can be captured in the ADB log. The log file (adblogfile.txt) is saved in the C:\ADB folder on your local computer.