To display only the features present on a particular device, select one or more filters from the SmartDocs bar below.
Input fields accept ENGLISH ONLY.
Queries from MX are not supported on Zebra devices running Android 11 or later. See alternative method.
EMDK For Android - 9.0
The "SmartDocs" bar can customize this page to show only the features present on a particular Zebra device.
OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. More info.
Clock allows an administrator to manually set the Date, Time and Time Zone on a device using local or UTC time, or to configure the device to automatically acquire those settings from a network (such as acquiring the Date and Time from a Network Time Protocol (NTP) server or acquiring the Date, Time and Time Zone from a cellular network). Clock also allows an administrator to choose between 12-hour (a.m./p.m.) and 24-hour (military time) display formats.
Zebra Android devices track the current Date and Time using the Coordinated Universal Time (UTC) standard. That information enables the Clock to accurately calculate the local Date and Time, expressed as the Local Time Coordinate (LTC). UTC is the equivalent of LTC at the Prime Meridian in Greenwich, England, where no offsets apply. For most other places, LTC is calculated starting with the UTC and adding or subtracting time based on the Time Zone in which the device being used, plus or minus the Daylight Saving Time offset, if any.
Clock sets Date and Time values in Coordinated Universal Time (UTC) to ensure proper conversion to local time based on Time Zone and Daylight Saving Time offsets. If LTC were used as a starting point, the order in which the Date, Time, and Time Zone were input could affect the resulting values. For more information, please see LTC Calculation Examples at the end of this guide.
Controls whether the Date and Time on the device are set using values from a cellular network or NTP server or must be set manually. When AutoTime is enabled, the device attempts to obtain the Date and Time from a cellular network (if one is available) or contacts an NTP server (if provided) at the interval specified in the SyncInterval parameter. When AutoTime is disabled, the Date and Time can be set manually to any valid values.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Parm Name: AutoTime
Used to enter the URL or IP address of the NTP server that the device can contact at the specified Sync Interval to acquire the Date and Time when AutoTime is enabled. Devices operating on a cellular network can typically acquire the Date, Time (and optionally the Time Zone) from the carrier network. Devices that do not support cellular communication or that may temporarily lack access to a supported cellular network can acquire Date and Time (but NOT the Time Zone) from an NTP server via a non-cellular network, such as Wi-Fi or Ethernet.
Parm input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Shown if: The Auto Time checkbox is "checked"
Parm Name: NTPServer
Requires:
- MX: 4.2+
- Android API: 19+
Used to enter the interval at which a device will attempt to contact the specified NTP server to acquire the Date and Time when AutoTime is enabled. For devices operating on a cellular network, AutoTime typically acquires the Date and Time from the carrier network.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Shown if: The Auto Time checkbox is "checked"
Parm Name: SyncInterval
Controls whether an administrator can set the maximum difference between the time on device clock and that of its selected NTP server. Threshold is set using the Time Sync Threshold parameter, below.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Parm Name: SpecifyTimeSyncThreshold
Used to enter a value (in milliseconds) for the maximum difference between the time on device clock and that of its selected NTP server. Default=5000ms (5 sec.).
Parm input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Shown if: The Specify Time Sync Threshold AND Auto Time checkboxes are "checked"
Parm Name: TimeSyncThreshold
Requires:
- MX: 11.8+
Used to select the Time and Date coordinates to be entered into the device for setting the system clock. Selecting Universal (option 1) causes values entered using UTCDate and UTCTime parameters to be converted by the Clock CSP to local time based on offsets for Time Zone and Daylight Saving Time.
Also see the LTC Calculation Examples section of this guide.
Shown if: The Auto Time checkbox is "unchecked"
Parm Name: CoordinateSystem
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Local | Configures the device to accept local Time (relative to the device location), adjusted for Time Zone. |
MX: 10.2+ |
||
| 1 | Universal | Configures the device to accept Coordinated Universal Time (UTC), the absolute time at the Prime Meridian. |
MX: 10.2+ |
Used to manually set the local Date on the device. Entering an empty value (or the absence of this parm from the XML) causes the previously configured Date to remain unchanged.
Parm input rules:
Note: This parameter DOES NOT perform adjustments to UTC values based on time zone or Daylight Savings offsets. To enable such functionality, select "Universal" in the Coordinate System parameter and enter date and time using the UTCDate and UTCTime parameters.
Shown if: The Auto Time checkbox is "unchecked" AND "Coordinate System" is set to Local
Parm Name: Date
Requires:
- MX: 4.1+
- Android API: 26+
Used to set the local Time on the device. Entering an empty value (or the absence of this parm from the XML) causes the previously configured Time to remain unchanged.
Parm input rules:
Note: This parameter DOES NOT perform adjustments to UTC values based on time zone or Daylight Savings offsets. To enable such functionality, select "Universal" in the Coordinate System parameter and enter date and time using the UTCDate and UTCTime parameters.
Shown if: The Auto Time checkbox is "unchecked" AND "Coordinate System" is set to Local
Parm Name: Time
Requires:
- MX: 4.1+
- Android API: 26+
Used to set the UTC Date for automatic calculation of the date on the device. Date and Time values given to the Clock using this parameter must be represented as UTC (see Overview). Entering an empty value (or the absence of this parm from the XML) will retain any previously configured Date.
For more information, see the LTC Calculation Examples section of this guide.
Parm input rules:
Shown if: The Auto Time checkbox is "unchecked" AND "Coordinate System" is set to Universal
Parm Name: UTCDate
Requires:
- MX: 10.2+
Used to set the UTC Time for automatic calculation of the local time for the device. Date and Time values given to the Clock using this parameter must be represented as UTC (see Overview). Entering an empty value (or the absence of this parm from the XML) will retain any previously configured Time.
For more information, see the LTC Calculation Examples section of this guide.
Parm input rules:
Shown if: The Auto Time checkbox is "unchecked" AND "Coordinate System" is set to Universal
Parm Name: UTCTime
Requires:
- MX: 10.2+
Used to set the Time Zone for calculating the Local Time Coordinate (LTC) on the device. Entering an empty value (or the absence of this parm from the XML) causes any previously configured setting to remain unchanged.
Parm input rules:
For more information, refer to these reference sites:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Shown if: The Auto Time Zone checkbox is "unchecked"
Parm Name: TimeZone
Requires:
- MX: 4.1+
Enables a cellular-equipped device to acquire the Time Zone in which it is located from the carrier network (if supported by that network). The Time Zone is used by Clock to calculate the local time on the device. When AutoTimeZone is disabled, the Time Zone can be set manually through the UI or programmatically using the Time Zone parameter. The AutoTimeZone feature applies only to cellular-equipped devices.
Warning: When changing the Auto Time Zone Enable/Disable setting, the Settings panel will not reflect the new setting if the panel was launched from the Android Recent Apps list. To avoid the appearance of this incorrect setting (which has no effect on proper device operation), the Settings app can be cleared from the Recent Apps list by adding the relevant XML from the App Manager to any profile created to set the clock.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Parm Name: AutoTimeZone
Controls whether to display time on the device in 24-hour "military time" format. When military time is Off, time is displayed in standard 12-hour (a.m./p.m.) format.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Parm Name: MilitaryTime
The examples in this section apply only to UTCDate and UTCTime parameters, which accept values based on the Coordinated Universal Time (UTC) standard.
When using UTCDate and UTCTime parameters, values given to the Clock must be represented as UTC values. This ensures an accurate result when calculating the local date and time for the device based on offsets for Time Zone and Daylight Saving Time, if any. If local time is used as a starting point, the order in which the Date, Time, and Time Zone are set could affect the resulting values. The examples below explain how to make these calculations correctly.
UTC is the equivalent of the Local Time Coordinate (LTC) at the Prime Meridian in Greenwich, England, where no offsets apply. For most other places, LTC is calculated starting with the UTC and adding or subtracting time based on the Time Zone in which the device being used, plus or minus the Daylight Saving Time offset, if any.
For more information, refer to these reference sites:
This example inverts the UTC offset. Since UTC time is later than Eastern time, hours are added to the desired Eastern time to calculate its UTC equivalent. When this figure is put into the device, the Clock recalculates the value to arrive at the desired local time for display by the device and for use in applications.
1. Note the desired local time for the device:
2. Make the following observations about device location:
3. Calculate the UTC value from the desired LTC:
4. The values specified to the Clock would therefore be:
When converted by the Clock, these UTC values would appear as the correct LTC values on the device.
This example also inverts the UTC offset. Since UTC time is earlier than India time, hours are subtracted from the desired Bangalore time to calculate its UTC equivalent, which results in a (backward) cross of the Prime Meridian (dateline). When this figure is put into the device, the Clock recalculates the value to arrive at the desired local time and day for display and program use.
1. Note the desired local time for the device:
2. Make the following observations about device location:
3. Calculate the UTC value from the desired LTC:
4. The values specified to the Clock would therefore be:
Note the Date is July 10, 2010, one day before the desired local time. That is because when it's 2:55 a.m. on July 11 in India, it's 9:25 p.m. (5 1/2 hours earlier) in Greenwich, England (where UTC originates), and the date is still July 10.
When converted by the Clock, these UTC values would appear as the correct LTC values on a device in Bangalore.
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="false"/>
<parm name="TimeZone" value="GMT-5"/>
<parm name="Date" value="2015-07-09"/>
<parm name="Time" value="10:25:33"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="true"/>
<characteristic type="AutoTimeDetails">
<parm name="SyncInterval" value="00:30:00"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="true"/>
<characteristic type="AutoTimeDetails">
<parm name="NTPServer" value="1.2.3.4"/>
<parm name="SyncInterval" value="00:30:00"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>