Get device logs

Last updated May 13th, 2026

This section shows how to get dumpstate logs from a device. As device log buffers are only temporarily stored for a short period of time, we strongly recommend you collect device logs as soon as you reproduce the issue you’re experiencing.

On devices running Android 15 and higher, you may have to disable Auto Blocker before you can access SysDump. To do this, go to your device’s settings, and disable Security and privacy > Auto Blocker.

Phone dumpstate logs

Before collecting logs, you may need to adjust the debug level of your device. You can review the debug level section to determine whether this is necessary.

To collect dumpstate logs on a phone:

  1. Try to reproduce the issue you’re experiencing.

  2. Once you’ve reproduced the issue, open the Phone app and enter *#9900# to open SysDump.

  3. Tap Run dumpstate/logcat.

  4. Tap Copy to sdcard.

  5. In the device’s internal storage, navigate to the /log directory, and retrieve the dumpState ZIP file.

  6. (Recommended) Once you’ve successfully retrieved the device logs, you can re-open SysDump and tap Delete dumpstate/logcat to free up space on your device. Additionally, if you previously adjusted the debug level, set the Debug Level back to Low.

Tablet dumpstate logs

Before collecting logs, you may need to adjust the debug level of your device. You can review the Adjust the debug level of your device section to determine whether it’s required.

For Wi-Fi only devices that don’t have the Phone app, you can get dumpstate logs as follows.

  1. Try to reproduce the issue you’re experiencing.

  2. Once you’ve reproduced the issue, open the Calculator app and enter (+30012012732+ to switch to factory mode.

  3. Enter *#9900# to open SysDump.

  4. Tap Run dumpstate/logcat.

  5. Tap Copy to sdcard.

  6. In the device’s internal storage, navigate to the /log directory, and retrieve the dumpState ZIP file.

  7. (Recommended) Once you’ve successfully retrieved the device logs, you can re-open SysDump and tap Delete dumpstate/logcat to free up space on your device. Additionally, if you previously adjusted the debug level, set the Debug Level back to Low.

Email logs

If you’re collecting email logs and dumpstate logs to troubleshoot an issue, make sure that they both capture the timeframe when you reproduced your issue.

Follow these steps to collect logs to investigate email and exchange issues.

  1. Open the Email app.

  2. On the top left, open Settings, and tap Add account.

  3. Under Set up Email, tap Other.

  4. Enter d@d.d as the email address, and enter password debug.

  5. Tap Manual setup (if there’s no Manual Setup button, just tap the left button at the bottom of the screen).

  6. Tap Enable Parser logging (extremely verbose).

  7. Reproduce the issue.

  8. Tap Dump emaillog, and Dump of EmailService.

  9. In the device’s internal storage, navigate to the /Download directory, and retrieve these files:

    • If it’s a fully-managed device, retrieve emaillog_0.txt. If the Email app is in a work profile, retrieve emaillog_10.txt.
    • emailServiceLog.txt.

Adjust the debug level of your device

By default, the debug level for phones and tablets is set to Low. You may need to adjust the debug level of your device if either:

  • The issue persists and is consistently reproduced under the same conditions, even after rebooting the device.
  • The Samsung Knox support team has requested that you adjust the debug level to obtain more detailed information from the device.

If either of the above conditions apply, complete the appropriate steps to open SysDump:

  • Phones: Open the Phone app and enter *#9900#.
  • Tablets: Open the Calculator app and enter (+30012012732+ to switch to factory mode, then enter *#9900#.

In SysDump, set the Debug Level to Mid and wait for the device to restart. You can then proceed to reproduce the issue and collect dumpstate logs as required.

Is this page helpful?