Skip to main content

Managing Log Archives

The bottom portion of the main screen displays a list of the archive files that exist on the device. The combined storage required by these files can become large, so it is recommended to regularly remove them by using one of two methods:

  • Export file: Tap the Export icon () for a file entry to export it to an external location. See the following section for details.

  • Delete file: Tap the Delete icon () for a file entry to delete it from the device.

Exporting Log Archives​

When you tap the Export icon for an archive file, you will see the following dialog:

Export Log Archive

The initial selections in the dialog are based on the configuration specified in the Settings screen under General Settings. If no SD card is installed in the device, that option is disabled.

You can change the settings (including the server URL) to redirect the selected archive to a different location. The next section details where the file is located when exporting to an SD Card. Tap the Export button to send the archive to the specified location. Once the export begins, the archive entry displays an indicator of the transfer progress.

Export in progress

More than one archive can be queued for export at the same time by tapping the Export icon for additional archives in the list. While an archive is waiting to be transferred, it will display a status of "Pending". If you tap on the Cancel button () at any time before the export has completed, the transfer will be stopped and the archive will remain in the list.

When the export has completed successfully, the file will automatically be deleted from the internal storage of the device (and removed from the list). If an error occurs during the transfer, the archive will remain in the list and a notification will be generated indicating that there was an error. This would typically only happen if there was a network error during transmission.

Location of Log Archives​

Instead of exporting log archives using the UI, you may connect the device directly to a PC and copy the files from the device over USB. Follow these steps to locate the archive files on the device using Windows:

  1. Attach the device to a PC with a USB cable.
  2. Open Windows Explorer. If the Android device is not listed, then launch the Settings Application on the device and follow these steps:
    1. Tap "Connected devices"
    2. Tap "USB"
    3. Under the heading "Use USB for", tap "File Transfer"
  3. Open the icon for the Android device (e.g. "Skorpio X5").
  4. Open "Internal Shared Storage". If the files are located on an SD card, you can choose that location instead (e.g. "SanDisk SD Card")
  5. The archive files are located in the following folder: Android\data\com.datalogic.logger\files

After making a copy of the file, it is best to delete the file from the device to make room for additional archives.

Archive contents​

Once the log archive is transferred from the device, you can examine its contents. The name of the file provides some information as to its contents. The name follows this format:

log_<deviceModel>_<deviceSerialNumber>_<dateTime>.zip

The date/time used in the name is taken at the point the archive is created (when logging stops).

The archive file is a standard ZIP file, so any software (such as Windows Explorer) that can read ZIP files can be used to read its contents. Inside the archive you will find the following files. Each file is a text file, viewable from several programs, such as Notepad.

  • readme.txt
    This describes the settings used to control logging behavior, as well as special circumstances (such as recovery from a device freeze) of how the archive was created.
  • logcat.log (if enabled)
    This contains the log content generated by the Logcat module.
  • kern.log (if enabled).
    This contains the log content generated by the Kernel module.
note

The log modules use the Linux line termination sequence (LF). This may not be compatible with all Windows-based text file viewers.

The specific entries inside each log file are intended to be examined by a software engineer who is familiar with the software that generated the message.