Install & Setup

Device Tracker 4.2

Overview

Device Tracker is a cloud-based solution that is hosted and managed by Zebra. Device licenses are required for Device Tracker to operate. Contact Zebra services for access to Device Tracker cloud and licenses prior to installation.

Client app installation and configuration on the devices can be performed using one of the following methods:

  • Manual Installation - manually install the client app on the device.
  • Automated Installation - use one of the following tools to remotely install or mass deploy Device Tracker to devices:
    • StageNow - a Zebra tool used to stage, setup and mass deploy apps and configurations to Zebra Android mobile computers.
    • Enterprise Mobility Management (EMM) system - leverage an existing EMM to deploy apps and configurations to devices.

Requirements must be met prior to installation. After installation is complete, proceed to the Configuration section to configure Device Tracker for initial use.

Notes: 

  • During a Google Play Services update, the Android system automatically stops Device Tracker. After the update is complete, relaunch the Device Tracker app or reboot the device to continue tracking of the device.
  • Device Tracker version 4.1 or lower is not supported on Android 11 and above. If an Android 10 device is installed with Device Tracker version 4.1 or lower, perform one of the following before upgrading to Android 11:
    • Uninstall the older Device Tracker version.
    • Upgrade to Device Tracker version 4.2.

Requirements

Device Requirements

Requirements for Device Tracker client on the device:

  • Supported Devices - See compatible devices table on the Zebra support portal.
  • Operating System - Only supported on select Android 8 Oreo, Android 10 and Android 11 GMS devices. See Zebra support portal for compatible devices.
    Note: For Android 11, all LG updates support Device Tracker except for LG update 11-20-18.00, which requires the April 2022 hotfix for support. For A11 LG updates, see the respective product page in Zebra support portal.
  • Bluetooth must be enabled to find devices using the visual proximity indicator. Zebra provides a tool, StageNow, for EMMs to configure the device remotely to enable Bluetooth.
  • Wi-Fi must be enabled and connected to the network with access to the cloud server. Zebra's StageNow tool used with Wi-Fi Manager allows EMMs to configure the device remotely to enable Wi-Fi access.
  • Location services must be enabled on all devices to find devices using the Bluetooth-based proximity indicator.
  • Secondary BLE support is required to locate the device if it loses battery power or is powered off. See Supported Devices with secondary BLE support. See Secondary BLE Configuration for instructions to enable this feature on supported devices.
  • Device licenses are required for Device Tracker to operate. Contact a Zebra reseller to procure licenses.
  • Do Not Disturb (DND) must be turned off in Android for the device being retrieved to play a sound.

Network Requirements

The network requirements for communication between the device client app and the cloud server are:

  • Open HTTPS port for communication between the Device Tracker client and Device Tracker cloud. Port 443 is normally used for all HTTPS communication by default, but this may vary based on network configuration.

  • The following domains must be allowed through the firewall or proxy.
    Domain names accessed by device:

    • connectivitycheck.gstatic.com (Required for Android to check internet connectivity.)
    • *.googleapis.com (Required for Device Tracker to authenticate device communication and connect with the cloud server.)
    • *.firebaseio.com (Required for Device Tracker to access the cloud database.)
    • *.cloudfunctions.net (Required for Device Tracker to access the cloud server.)
    • [ProjectID].firebaseapp.com (Required for accessing password reset link, where [ProjectID] is supplied by Zebra during onboarding.)

    Domain name accessed by the admin on a PC:

    • Web portal - supplied by Zebra during onboarding.

If the firewall or proxy does not support wildcards, add the following domains to the allow list:

  • connectivitycheck.gstatic.com (Required for Android to check internet connectivity.)
  • www.googleapis.com (Required for Device Tracker to authenticate device communication with the cloud server.)
  • firestore.googleapis.com (Required for Device Tracker to access the cloud database.)
  • cloudfunctions.googleapis.com (Required for Device Tracker to connect with the cloud server.)
  • us-central1-[ProjectID].cloudfunctions.net (Required for Device Tracker to connect with the cloud server, where [ProjectID] is supplied by Zebra during onboarding.)
  • [ProjectID].firebaseio.com (Required for Device Tracker to access the cloud database, where [ProjectID] is supplied by Zebra during onboarding.)
  • [ProjectID]-default-rtdb.firebaseio.com (Required for Device Tracker to access the cloud database, where [ProjectID] is supplied by Zebra during onboarding.)
  • s-usc1c-nss-*.firebaseio.com (Required for Device Tracker to access the cloud database, where * represents multiple characters. Since * can change over time, the firewall needs to allow any domain with this pattern for the app to function.)
  • [ProjectID].firebaseapp.com (Required for accessing password reset link, where [ProjectID] is supplied by Zebra during onboarding.)

If the password is reset, an email is sent from zdtrksupport@zebra.com.

NOTE: [ProjectID] is supplied by Zebra services during the onboarding process. An XML file is supplied, which contains a string similar to:

    <parm name="ProjectId" value="<customer name>-dtrk-na-p" />

The "value" field contains the ProjectID. In this example, the project ID is: <customer name>-dtrk-na-p

Web Portal Requirements

The web portal allows adminstrators to configure application behavior, manage users and view licenses. To access the web portal, in a supported browser enter the URL provided by Zebra. The supported browsers are:

  • Chrome
  • Edge
  • Safari (v14.0 and later)

The administrator's email address is registered as a user in the system. For first-time use, in the web portal click Forgot Password and enter the registered administrator's email address. An email is sent describing how to reset the password for the administrator to login.

Manual Installation

When manually installing the app on the device, accept all permissions when granted and configure the server connection.

Prerequisites

Perform the following on the host PC prior to manual installation:

  1. Download the latest .APK file from the Zebra support portal.
  2. Download the server connectivity settings barcode provided by Zebra during the onboarding process. If not supplied, perform the following:
         A. Download the server connectivity settings XML file provided by Zebra during the onboarding process.
         B. Create a server connectivity settings barcode using StageNow. See Server Connectivity Profile for instructions.

Installation

Manual installation steps to be performed on the device:

  1. Connect the device to a Wi-Fi network. Ensure the network requirements are met to access the Device Tracker cloud.
  2. Install the downloaded .APK file on the device.
  3. Launch the Device Tracker app. Grant all permissions when prompted. For Android 11 and higher, when granting Location permissions, choose option “Allow all the time”.
  4. Launch StageNow client and scan the server connectivity settings barcode from step 2 in the Prerequisites section above.
  5. Enable secondary BLE on supported devices to allow these devices to be located even when powered off. See Secondary BLE Configuration section for details. (Optional)

Automated Installation

Automated installation installs and configures apps on devices for mass deployment. This enables administrators to easily deploy an app and its configurations on many devices unattended. There are 2 methods for automated installation: StageNow or EMM.

StageNow remote install profiles can be used to install the client app on the device, automatically grant all permissions during install, configure the server connection and enable secondary BLE (optional).

Notes:

  • If Device Tracker is included in a list of specific apps that are allowed to run on a device, e.g. in an EMM, the file manager app must also be allowed as part of this list to enable administrators to import .CSV files.
  • When installing the application on a device using an EMM, some EMMs do not grant all the required permissions for the application to run in the background to track the device. Alternatively, an XML file can be generated from the StageNow profile and consumed by the EMM granting all permissions.
  • Deployment with XML may vary between different EMM systems. Refer to the EMM guide.

StageNow

Use Zebra's StageNow tool for automated installation - generate barcodes and then scan the barcodes with StageNow client on the device to install and configure Device Tracker. Follow the procedure below to install the client app on the device, automatically grant all permissions during install, configure the server connection and enable secondary BLE (optional).

Prerequisites

On a host PC, perform the following:

  1. Download the latest .APK file from the Zebra support portal.
  2. Download the app certificate, needed to create the install profile.
  3. Use StageNow to create a barcode to deploy Device Tracker as follows:
    • Install Device Tracker app.
    • Grant permission for the app to run in the background and track devices by removing Device Tracker from the Battery Optimization exemption list using AppMgr.
    • To use the Device Check-out feature, grant permission to display the Check-out screen to prevent users from accessing the device prior to scanning their user barcode. This is done by granting System Alert Window using AccessMgr.
    • Start Device Tracker app or start its service.
      See Install Profile for detailed instructions.
  4. Download the server connectivity settings barcode provided by Zebra during the onboarding process. If not supplied, perform the following:
        A. Download the server connectivity settings XML file provided by Zebra during the onboarding process.
        B. Create a server connectivity settings barcode using StageNow. See Server Connectivity Profile for detailed instructions.

Installation

Steps to install and configure Device Tracker on the device using StageNow:

  1. Connect the device to a Wi-Fi network. Ensure the network requirements are met to access the Device Tracker cloud.
  2. Launch StageNow client.
  3. Scan the barcode to install Device Tracker; see step 3 in Prerequisites.
  4. Scan the barcode to enable the Device Tracker app to communicate with the cloud server; see step 4 in Prerequisites .
  5. To find devices that are powered off or offline, enable secondary BLE on supported devices. See Secondary BLE Configuration section for details. (Optional)

Using EMM

Device Tracker can be remotely installed to devices without manual intervention through an EMM. XML is exported from StageNow profiles to be consumed by the EMM to install the client app on the device, automatically grant all permissions during install, configure the server connection and enable secondary BLE (optional).

Prerequisites

Prerequisites for installation using EMM:

  1. Download the latest .APK file from the Zebra support portal.
  2. Download the Device Tracker MX XML file, which performs the following:
    • Grant permission for Device Tracker to run in the background and track devices. Device Tracker is removed from the Battery Optimization exemption list (using MX AppMgr) for Device Tracker to continue running in the background during Android doze mode.
    • Grant permission to display the Device Checkout option in the web portal by granting Device Tracker access to the System Alert Window (using MX AccessMgr). Use of Device Checkout prevents users from accessing the device prior to scanning their user barcode.
    • Start Device Tracker service to begin tracking devices. See Install Profile for details.
  3. Download the server connectivity settings XML file provided by Zebra during the onboarding process.

Installation

Instructions to install and configure Device Tracker through an EMM:

  1. Connect the device to a Wi-Fi network. Ensure the network requirements are met to access the Device Tracker cloud.
  2. Install the .APK file to the device; see step 1 in Prerequisites. Make sure to allow the following permissions used by Device Tracker:
    • android.permission.READ_PHONE_STATE – Required to read the device serial number and register devices with the Device Tracker server for tracking.
    • android.permission.ACCESS_BACKGROUND_LOCATION – Required to find devices using the Bluetooth proximity meter
    • android.permission.ACCESS_FINE_LOCATION – Required to find devices using the Bluetooth proximity meter.
  3. Deploy Device Tracker MX XML file to the device; see step 2 in Prerequisites. This grants permissions to display over other apps, disable battery optimization and starts the tracking service.
  4. Deploy server connectivity settings XML file to the device; see step 3 in Prerequisites.
  5. Enable Secondary BLE for devices that support secondary BLE. See Secondary BLE Configuration for details.

Remote Install Profiles

Use Zebra's StageNow tool to create 3 separate profiles: Install, Server Connectivity and Secondary BLE Configuration. These profiles are consumed by Zebra’s StageNow tool or an EMM to remotely install Device Tracker on devices. Instructions to create each profile follow in the subsections below.

Prerequisites

Prerequisites to create StageNow profiles:

Install Profile

Create a StageNow install profile to:

  • Copy the .APK file to the device.
  • Install the .APK file.
  • Grant permission for the app to run in the background during doze mode (Android’s power-saving feature triggered when the device is in a prolonged suspended state).
  • Grant overlay permission to display the checkout screen. (Optional)
  • Start Device Tracker service to begin tracking.

Instructions to create a StageNow install profile (must fulfill the prerequisites):

  1. Open StageNow on a host computer.

  2. In the StageNow home screen, click Create New Profile from the left menu.

  3. Ensure MX version 8.0 or higher is selected at the top drop-down selector. The MX version on the device should match this or higher. See MX documentation for instructions how to check the version. If automatically bypassing the overlay permission for Check-out, select MX 10.0 or higher.

  4. Select Xpert Mode from the list and click Create. Wizard selection

  5. Enter the profile name. Click Start.

  6. If using StageNow to copy the install file to the device, scroll down and click the plus (+) sign next to FileMgr. This adds FileMgr to the Config tab on the right side.

  7. Scroll to AppMgr and click the plus (+) sign next to it. This adds AppMgr to the Config tab on the right side.

  8. Repeat step 7 again. AppMgr is listed twice in the Config tab.

  9. If automatically bypassing the screen overlay permission, scroll to AccessMgr and click the plus (+) sign next to it. This adds AccessMgr to the Config tab on the right side.

  10. Scroll to Intent and click the plus (+) sign next to it. This adds Intent to the Config tab on the right side.

  11. Click Add. The following list of configuration settings is displayed: Installation profile - config settings

  12. If using StageNow to copy the install file to the device, proceed with this step. Otherwise, skip to step 14.
    StageNow Config 1 - Copy the install file to the device with FileMgr. In the FileMgr screen under the Create New Setting tab, select and enter the desired options to install the APK, for example:
         • File Action: Transfer/Copy File
         • Target Access Method: File in the device file system
         • Target Path and File Name: [enter file path]
         • Source Access Method: [select applicable method]
         • Source File URI: [enter information prompted]
    Click Continue.

  13. StageNow Config 2 – Install the client app. For the first AppMgr, select the following:
         • Action: Install
    Enter/select the desired options for the remaining fields. Click Continue.

  14. StageNow Config 3 – Battery Optimization. For the second AppMgr, enter/select the following:
         • Action: Application for Battery Optimization
         • Remove Application for Battery Optimization: com.zebra.devicetrackercloud
    Click Continue.

  15. StageNow Config 4 – Grant overlay permission. For AccessMgr, enter the following:
         • Permission Access Action: Grant Permission to an Application
         • Permission Name: System Alert Window
         • Application Package Name: com.zebra.devicetrackercloud
         • Application Signature: [browse to certificate file downloaded]

  16. StageNow Config 5 – Start Device Tracker service by sending an intent. For Intent, enter/select the following:
         • Action: StartService
         • Android Action Name: com.zebra.devicetrackercloud.csp.NGDTCspService
         • Package Name: com.zebra.devicetrackercloud
         • Class Name: com.zebra.devicetrackercloud.csp.NGDTCspService
    Click Continue.

  17. Click Complete Profiles. Profile creation is complete.

  18. Select one of the following based on the deployment method:

  • StageNow: Generate the barcode from the StageNow profile. Open StageNow client on the device and scan the barcode(s) generated.
  • EMM: Export XML from the StageNow profile. Do not edit the XML file - it can cause unexpected behavior. Send the XML using either OEMConfig or MX to configure the app and grant all required permissions. The install profile and server connectivity profile XML files must be used separately.

Server Connectivity Profile

To apply server settings in the app client for it to communicate with the cloud, create a StageNow server connectivity profile. The server configuration XML file is required, supplied by Zebra.

Instructions to create a StageNow server connectivity profile (must fulfill the prerequisites):

  1. Open StageNow on a host computer.

  2. In the StageNow home screen, click Create New Profile from the left menu.

  3. Ensure the proper MX version is selected at the top drop-down selector. This should match the MX version on the device. See MX documentation for instructions how to check the version. Select Xpert Mode from the list and click Create. Wizard selection

  4. Enter the profile name. Click Start.

  5. Find Batch and click the plus (+) sign next to it. This adds Batch to the Config tab on the right side. Server connectivity profile - config setting

  6. Click Add. In the Batch screen, select the following:
         • Batch Action: Execute Batch
         • Batch File Type: XML File
         • Batch File Access Method: File embedded in XML
         • XML File Data: [browse to the server configuration XML file supplied from Zebra services]

  7. Click Continue.

  8. Click Complete Profiles.

  9. Select one of the following based on the deployment method:

  • StageNow: Generate the barcode from the StageNow profile. Open StageNow client on the device and scan the barcode(s) generated.
  • EMM: Export XML from the StageNow profile. Do not edit the XML file - it can cause unexpected behavior. Send the XML using either OEMConfig or MX to configure the app and grant all required permissions. The installation profile and server connectivity profile XML files must be used separately.

Note: If an enterprise reset is performed on the device, the server settings must be re-applied to communicate with the server.

If the server configurations are changed, reboot the device after deploying the installation and server connectivity profiles.

Once the app is started on Android Oreo or higher devices, a Device Tracker notification message is displayed in the device notification drawer. This notification cannot be dismissed, indicating that Device Tracker is running in the background.

Secondary BLE Configuration

Enable Secondary BLE (Bluetooth Low Energy) to find devices when powered off. Locationing is based on signals transmitted from the secondary BLE beacon of the misplaced device that are detected from the device performing the search. By enabling secondary BLE, another device can locate the powered device by detecting the advertising packets sent by the powered off device.

Beacon Manager (BeaconMgr) controls the signals transmitted by the secondary BLE radio on the powered off device. Aside from administrative control detecting beacons, Beacon Manager also controls the power level of the transmitted signal to help balance power consumption within a detectable range. For supported devices, use BeaconMgr with the following parameters:

     • Beaconing: Turn ON
     • Beaconing in Airplane Mode: Turn ON
     • Beacon type: AltBeacon
     • Explicit Beacon UUID?: [uncheck checkbox]
     • AltBeacon ID1: EBEB
     • AltBeacon ID2: ECDD
     • Transmission (Tx) Power Level: High (1 dBm)
     • Transmission (Tx) Interval: Low Latency (100 ms)
     • Manufacturer Byte: 00
     • Reference RSSI: [For battery-based secondary BLE, such as TC52AX and MC33AX, enter C0. Otherwise, leave blank]

See Beacon Manager documentation for more information.

Configuration differs slightly depending on the location of the secondary BLE radio:

Instructions to create a secondary BLE configuration profile using StageNow (must fulfill the prerequisites):

  1. Open StageNow on a host computer.

  2. In the StageNow home screen, click Create New Profile from the left menu.

  3. Ensure the proper MX version, MX 10.2 or higher, is selected at the top drop-down selector for secondary BLE support. Support for Manufacturer Byte and Reference RSSI options were added starting with MX 10.5. See MX documentation for instructions how to check the version. Select Xpert Mode from the list and click Create. Wizard selection

  4. Enter the profile name. Click Start.

  5. Find BeaconMgr and click the plus (+) sign next to it. This adds BeaconMgr to the Config tab on the right side. Add config setting

  6. Click Add. In the BeaconMgr screen, select the following:
         • Beaconing: Turn ON
         • Beaconing in Airplane Mode: Turn ON
         • Beacon type: AltBeacon
         • Explicit Beacon UUID?: [uncheck checkbox]
         • AltBeacon ID1: EBEB
         • AltBeacon ID2: ECDD
         • Transmission (Tx) Power Level: High (1 dBm)
         • Transmission (Tx) Interval: Low Latency (100 ms)
         • Manufacturer Byte: 00
         • Reference RSSI: [For battery-based secondary BLE, such as TC52AX and MC33AX, enter C0. Otherwise, leave blank]

  7. Click Continue.

  8. Click Complete Profiles.

  9. Select one of the following based on the deployment method:

  • StageNow: Generate the barcode from the StageNow profile. Open StageNow client on the device and scan the barcode(s) generated.
  • EMM: Export XML from the StageNow profile. Do not edit the XML file - it can cause unexpected behavior. Send the XML using either OEMConfig or MX to configure the app and grant all required permissions. The installation profile and server connectivity profile XML files must be used separately.

Ensure devices are connected to the network and can connect to the server for at least 5 minutes during the intial setup.

Uninstallation

Instructions to uninstall Device Tracker:

  1. Remove the app manually on the device or through an EMM.
  2. Contact Zebra services to terminate the Device Tracker cloud instance.

See Also