About Device Diagnostic Tool

Device Diagnostic Tool 3.1

Overview

Device Diagnostic Tool (DDT) instantly tests and diagnoses the hardware operability on Zebra mobile devices to determine system health and functionality. Where appropriate, Zebra Help Desk uses this tool for troubleshooting device issues, relying on the results to provide optimum steps to reach a resolution. It is useful for quickly troubleshooting device issues, resulting to increased worker productivity, limited device downtime, and unnecessary returns to the Zebra Repair Center.

Hardware features tested:

  • Scanner Test – checks whether the scanner is operable
  • Button Test – checks the operation of push-to-talk, left or right scan trigger, volume up and volume down device buttons
  • Touch Screen Test – checks for operation of the device touch display
  • Bluetooth Tests – checks whether the Bluetooth radio is operable and returns Bluetooth related information: Bluetooth name, radio power cycle result, radio functional/non-functional, and discoverable/connectable
  • WiFi Tests – checks for operation of the WiFi radio and returns WiFi related information: MAC address, network test results from specified address, signal strength, IP address, BSSID, and speed
  • Battery Tests – checks the battery status and returns battery related information: part number, serial number, manufacture date, battery health, voltage, current, temperature, battery level and current capacity
  • WWAN Tests – checks for operation of the WWAN radio and returns related WWAN information: SIM state, voice state, data state, WAN type, signal strength, phone number, and device ID
  • Audio Test – checks for operation of the device microphone and speaker
  • SD Card Test - checks for presence/absence of external SD card, read/write status and total/free space on SD card
  • USB Test - checks the functionality of the USB port on the device
  • Network Test - checks whether the device can connect to a network (WLAN or WAN)
  • Keyboard Test - checks for physical key or button functionality, outputting the keycode value when the key or button is pressed
  • Camera Test - checks for camera functionality, enabling a user to capture an image with the device's rear camera and assess the image quality

For more information on each test, refer to Test Criteria.

Download DDT from the Zebra Support Portal.

New in 3.1

  • New Camera Test to verify camera functionality. It enables a user to capture an image with the device's rear camera and assess the image quality.

Version History

New in 3.0

  • New Keyboard Test to validate physical key or button functionality. It outputs the keycode value when a physical key or button is pressed by the user, validating its functionality.

New in 2.9

  • New configuration file for Button Test to support remapped physical buttons (scan trigger, push-to-talk, volume up/down) on the device.
  • For Zebra DNA Cloud solution installations:
    • DDT is now added to Zebra Collection in ZDNA Cloud.
    • DDT supports deployment, installation, and configuration through ZDNA console.
  • Newly supported devices in this release: TC22, TC27, ET60. See Zebra Support Portal for the list of supported devices.
  • Resolved Issues:
    • Button Test now supports remapped keycode for Push-To-Talk button.
    • Notification of DDT running is not displayed after reboot on Android 13 devices.
  • Known Issue: On ET60 devices, the Button Test is not supported with the default button configuration file. To resolve this, the buttons_config.xml configuration file must be modified to include ET60.

New in 2.8

  • New Android 13 device support; see Zebra Support Portal for supported devices.
  • New USB Test added to check the functionality of the USB port on the device.
  • New Network Test added to verify whether the device can connect to a WLAN or WAN network.
  • The package name for DDT is now changed from com.symbol.selfdiagnostics to com.zebra.mdna.selfdiagnostics. Due to this change, uninstallation of any prior version of DDT is required before installing this latest version.
  • Older DDT versions and package names are deprecated.
  • On Android 11 or higher, DDT now stores its configuration file in a secure storage location rather than the enterprise partition via Secure Storage Manager.
  • DDT is now available on Google Play and Zebra Support Portal.
  • Fixed issue: The Battery test now supports threshold value for Power Precision batteries.

New in 2.7

  • New Upload Preference option to specify whether to upload logs based on the specified test schedule or upload only after a test failure.
  • New Android 11 device support, see Zebra Support Portal.
  • Fixed issue: On TC57 when performing a Button test, a scan error occurred due to the inability to detect the scan button.

New in 2.6

  • New About screen added, containing version information. To access About, tap the menu on the top right of the main screen and select About.
  • Scanner Test now supports all barcode symbologies. Previously, a restricted set of symbologies were supported, which resulted to a failed test if an unsupported barcode was scanned.
  • DDT now sends test result data to Zebra Data Service for integration with VisibilityIQ.
  • Added test completion (end) time to the log files, in addition to the test start time.

New in 2.5

  • New SD Card Test to check for external SD card presence, total/free space and read/write status.
  • DDT is now localized in 7 different languages (French, Italian, German, Spanish, Portuguese, Simplified Chinese and Japanese) based on the language of the Android system.
  • New automated remote test scheduling and remote log file export with Managed Configuration.
  • Resolved issue: Test result is not logged properly when test is cancelled.

New in 2.4

  • New feature to upload logs to FTP server.
  • New feature to schedule jobs for device tests.
  • New battery threshold value to set the maximum charge cycle count of the battery that triggers "Need to replace battery" in Battery Health.
  • Fixed issue: On devices with large screens, such as tablets (e.g. ET51/ET56, L10) and vehicle mounted computers (e.g. VC80x, VC8300), both portrait and landscape modes are now supported.
  • Due to a new policy in the Google Play Store, location can no longer be used in the background. This led to the removal of Location permission from Device Diagnostic Tool. As a result, ESSID can no longer be retrieved since it relies on the location service.

New in 2.3

  • New Help option available which links to the Device Diagnostic Tool support portal.
  • New data fields captured for Battery test: battery level and battery current capacity.
  • New features configurable through the configuration file:
  • Fixed an issue where DDT does not revert the device back to its original device orientation, landscape or portrait mode, after application exit.
  • Enhancements:
    • For the WLAN test, the radio power cycle is replaced by a check to determine if the WiFi radio is enabled. If the WiFi radio is not enabled when initiating the WLAN test, the user is prompted to enable the radio.
    • To display the ESSID from a WLAN test on Android O or higher, Location service is required to be enabled on the device due to Android restrictions. If Location service is not enabled, the user is prompted to enable it. If the test proceeds without Location service enabled, ESSID returns "Location not enabled" instead of "Unknown SSID." * For the WWAN test, if a sim card is not present in the device, the test no longer fails and now shows Absent for the Sim State along with the appropriate status for the rest of the WWAN parameters.

New in 2.2

  • New devices supported - see supported devices for Device Diagnostic Tool on Zebra Downloads.
  • Android 10 limitations due to security restrictions:
    • In the WWAN test details screen, "Device ID" is not visible.
    • In the History.log file, "Device ID" and "Device Serial#" is not visible.
  • Fixed Issues:
    • On TC20 and TC25 Android Oreo, when performing the Button test the scan trigger press fails.
    • On TC25 Android Nougat, when performing the Button test the Time Remaining value for the parameter timeout does not take into effect for PTT or scan buttons.
  • Known Issues:
    • On Android 10 WWAN devices, if a sim card is not inserted and a WWAN test is performed, improper values may be returned for Voice state.
    • When a battery test is performed, improper values may be displayed on the following devices:
              • Devices that require AC Power to operate (no battery exists), such as CC605 and CC610
              • ET50 devices - the part number, serial number and manufactured date may display improperly

New in 2.1

  • Introduced 2 modes of operation: admin mode and user mode.
  • Changes in supported tests: - Tests added: Scanner, Button, Touch Screen, Audio - Tests removed: GPS, System
  • Added capability to import or export configuration files.
  • New Settings and Configure Tests app screens for administrators.
  • Added and removed device support. See Supported Devices table below.
  • Known Issues:
    • On TC20 and TC25 Android Oreo, when performing the Button test the scan trigger press fails.
    • On TC20 and TC25 Android Nougat, when performing the Battery test the Battery Health may return incorrect information.
    • On TC25 Android Nougat, when performing the Button test the Time Remaining value for the parameter timeout does not take into effect for PTT or scan buttons.
    • On TC75x Android Marshmallow, Data State in WWAN test may display “Data Disconnected” even though mobile data is enabled on the device.
    • When the app is running and the EMM command is executed to run the test remotely, if the user tries to launch the app manually after the test completes, the app may encounter unexpected behavior. In this case the user must manually restart Device Diagnostic Tool to recover.

Supported Devices

See supported devices for Device Diagnostic Tool on Zebra Downloads.

Installation Notes:

  • Multiple instances of app - If Device Diagnostic Tool v1.0 is already present on the device and Device Diagnostic Tool v2.1 or higher is then installed on the same device, there will be 2 versions of the app that exist. To avoid this scenario, the administrator can disable Device Diagnostic Tool v1.0 using AppManager CSP for the device to run a single version of the app.
  • Setting persistence - Upon initial app install, any setting changes made through the UI persist since configuration.xml does not exist. However, after exporting the .xml file, any changes in the UI no longer persist until the .xml file is imported into the device.

Important Usage Notes

  • Multiple Android user accounts - When using multiple Android user accounts on a single device, Device Diagnostic Tool use and functionality only applies to the active primary user.
  • Limitation due to low memory on the device - Once the available device memory is less than 3 MB, a message appears indicating there is no space on the device and logging will no longer take place. Additionally the Audio Test cannot be executed.
  • Split screen support - On Android N and above, Device Diagnostic Tool does not support split screen mode.
  • Android 10 and Android 11 limitations due to security restrictions:
    • In the WWAN test details screen, "Device ID" is not visible.
    • In the History.log file, "Device ID" and "Device Serial#" are not visible.
  • Android 13 limitation due to security restrictions:
    • New Android restrictions prohibit SD6490 and SD6375 platform devices from supporting the adb “push” command for deployment of files to the devices. To manually deploy a configuration file, use a desktop file browser to copy the file to the following location on the device: /sdcard/Android/data/com.zebra.mdna.selfdiagnostics/
  • Camera Test - When DDT is brought back to the foreground from the background, both the camera test and timeout period are reset.

See Also