For devices with Android 11 and OLDER
This guide documents managed configurations of the Original Schema for current and legacy Zebra devices. Learn more.
Use this guide if:
- Targeting devices with Android 8.x–11.x
AND... - All desired features were implemented with MX 11.5 or earlier
- The OEMConfig package name for this schema is
com.zebra.oemconfig.common
Terms in this Guide
Concepts
Define - Used when referring to the definition in the OEMConfig schema that determines what the administrator is permitted to do as opposed to what an admin might elect to do. For example, within a Step, an admin is permitted to include one of every defined Managed Configuration Group but in most cases would only elect to include only one or a few.
Include - Used when referring to a decision by an administrator to elect to perform some Action or configuration as opposed to what the administrator is permitted to do, but may or may not elect to do. For example, an admin would be permitted to include one of everything, but likely would elect to include only one or a few.
Instance - A SINGLE occurrence or use of something (such as a Step, MC, Group, Sub-group, or Sub-array). An Instance might refer to the inclusion of a Step in a Transaction; an MC or Group in a Step; an MC, Sub-group, or Sub-array in a Group; or a Sub-group as an element of a Sub-array.
Elements
Transaction - An ordered list of Steps, each of which specifies one or more Actions to be performed or settings to be configured on a Zebra device. Steps are executed in the exact order specified within the Transaction, but the order of execution within a Step is controlled by the system. The recommended means of controlling the order of execution, if required, is to use separate Steps within a Transaction.
Step - A collection of Actions to be performed or settings to be configured at a specific point within a Transaction. Within a Step, some MCs are defined directly (such as for entering an Explanation or selecting an Error Mode), but most are organized into Managed Configuration Groups. An instance of a Step can include no more than one instance of any MC or Group that is defined for a Step. Within a Step, all included MCs and Groups, and anything included within any Groups, are executed in an order determined by the system to afford the greatest likelihood of success. For example, the system might execute a Bluetooth configuration after an Action to enable Bluetooth because configuring Bluetooth might fail if attempted when Bluetooth was disabled.
Group - See Managed Configuration Group.
Managed Configuration Group - A collection of MCs, Sub-groups, or Sub-arrays that are defined to control some aspect of the device (such as Analytics Configuration or Audio Configuration). A Group can include no more than one instance of any MC, Sub-group, or Sub-array that is defined for that Group.
Sub-group - A collection of MCs, Sub-groups, or Sub-arrays that are defined as permitted to control some sub-aspect of the device (such as Send to Cloud Detail in Bug Reporting Configuration). A Sub-group can include no more than one instance of any MC, Sub-group, or Sub-array defined for that Sub-group.
Sub-array - An ordered list of instances of a SINGLE Sub-group, each of which can contain anything that is defined for that Sub-group. The only time the same MC, Sub-group, or Sub-array can be included more than once into the same Step is when it appears within different elements of a Sub-array. For example, the Key Mapping Configuration Group defines a Sub-array Add Mapping Behaviors that can be used to configure multiple behaviors for a single key in different modifier states (orange, green, blue, etc.). A single Step can include multiple instances of the MCs defined for the Behaviors Sub-group, by including them in different elements in the Add Mapping Behaviors Sub-array.
Transaction Overview
This section of the OEMConfig documentation describes all supported Managed Configurations (MCs), which can be used to define an ordered list of Steps for defining one or more Actions to be performed or settings to be configured on a Zebra device as part of an overall Transaction. Before attempting to configure a Transaction, it's important to understand the concept of Managed Configuration Groups, Sub-groups, Sub-arrays. A Transaction can contain one or many of these elements, and can be nested multiple levels deep.
Type Styling
- Bold Italic type indicates values of a Managed Configuration such as On or Enable.
- Bold type indicates the name of an MC, Group, Sub-group, or Sub-array, such as the Audio Configuration Group or the State Managed Configuration.
- Italic type indicates defined terms, such as Transaction and Step.
NOTE: Defined terms are Capitalized to differentiate from italics used for emphasis.
Transaction Steps
Specify an ordered list of Transaction Steps that define the Actions or configurations that you wish to perform on a device as part of an overall Transaction.
Detail Information:
Key = steps
Type = bundle_array
Transaction Step
Specify a single Transaction Step that defines one or more Actions or configurations that you wish to perform on a device at a specific point in an an overall Transaction.
Detail Information:
Key = step
Type = bundle
Explanation
Enter an optional Explanation that describes the purpose or intended behavior of a Transaction Step.
Since a Transaction may include many Transaction Steps and each Transaction Step could include one or more configurations, describing the Transaction Step can be beneficial when later reviewing the Transaction and/or when editing a Transaction, and especially when reordering the Transaction Steps within the Transaction.
Detail Information:
Key = stepExplanation
Type = string
Error Mode
Select an Error Mode that determines how errors that occur during the execution of a Transaction Step should be handled.
Since a Transaction may include multiple Transaction Steps, there may be cases where one Transaction Step within a Transaction is dependent on configuration performed by one or more preceding Transaction Steps in the same Transaction. In such cases, it may be desirable to terminate a Transaction if the processing of a Transaction Step results in an error to avoid propagating the results of that error into subsequent Transaction Steps.
By default, execution will continue with the next Transaction Step once execution of the current Transaction Step is completed. A decision to override this default behavior can be made independently for each Transaction Step within a Transaction by supplying an Error Mode value:
- If the value Continue is selected, the default behavior will be used and hence any errors that occur during the execution of the current Transaction Step will NOT terminate execution of subsequent Transaction Steps in the same Transaction. Execution will thus always continue with the next Transaction Step once execution of the current Transaction Step is completed.
- If the value Stop is selected, the default behavior will be overridden and hence any errors that occur during the execution of the current Transaction Step will terminate execution of subsequent Transaction Steps in the same Transaction. Execution will continue with the next Transaction Step only if execution of the current Transaction Step completes with NO errors.
Detail Information:
Key = stepErrorMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Continue | Continue |
| Stop | Stop |
Managed Configuration Groups
A Step can include one or more of the following Managed Configuration Groups.
Analytics Configuration
Use this Sub-group to configure State and User Control of State.
Detail Information:
Key = analyticsStep
Type = bundle
State
Select whether the Analytics Client on a device is turned on (enabled) or turned off (disabled).
The Analytics Client is turned on (enabled) by default on all devices:
- If the value Off is selected, the Analytics Client will be turned off (disabled), and hence it will not collect any machine data during the operation of the device and will not deliver any machine data regardless of whether connectivity is available.
- If the value On is selected, the Analytics Client will be turned on (enabled), and hence it will automatically collect machine data during the operation of the device and deliver it, when connectivity is available, to the Zebra Analytics Cloud Server.
On some devices, the ability to turn off (disable) the Analytics Client may not be supported.
Detail Information:
Key = analyticsState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.3.
User Control of State
Select whether the the device user will be allowed to control whether the Analytics Client on a device is turned on (enabled) or turned off (disabled).
The Analytics Client is turned on (enabled) by default on all devices:
- If the value Off is selected, the device user will not be allowed to change whether the Analytics Client is turned off (disabled) or on (enabled), and hence whether it will collect or deliver any machine data during the operation of the device.
- If the value On is selected, the device user will be allowed to change whether the Analytics Client is turned off (disabled) or on (enabled), and hence whether it will collect or deliver any machine data during the operation of the device.
Detail Information:
Key = analyticsUserControlState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 7.2.
App Feature Configuration
Use this Sub-group to configure App Feature State, App Feature Name, and App Feature Package Name .
Detail Information:
Key = appFeatureStep
Type = bundle
Support Information:
Supported on Operating System(s): Pie and Oreo.
Supported from: MX 9.3.
App Feature State
Select whether a specified Application Feature should be On or Off.
If the value Do not change is selected, then no change will be made to whether the specified Application Feature should be On or Off.
If the value Off is selected, the Application Feature will be turned Off.
If the value On is selected, the Application Feature will be turned On.
You must also specify App Feature Name to provide the Feature Name that identifies the Application Feature to be turned On or Off and App Feature Package Name to specify the Android Package Name that identifies the application for which the Application Feature will be turned On or Off.
Detail Information:
Key = appFeatureState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
Supported on Operating System(s): Pie and Oreo.
Supported from: MX 9.3.
App Feature Name
Select the Feature Name that identifies the application for which an Application Feature will be turned On or Off when App Feature State is specified. You must also specify App Feature Package Name to identify the application for which the specified Application Feature will be turned On or Off or select Do nothing to to make no change to any application.
Detail Information:
Key = appFeatureName
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Background Data | 1 |
Support Information:
Supported on Operating System(s): Pie and Oreo.
Supported from: MX 9.3.
App Feature Package Name
Enter the Android Package Name that identifies the application for which an Application Feature will be turned On or Off when App Feature State is specified. You must also specify App Feature Name to specify the Feature Name that identifies the Application Feature that will be turned On or Off for the specified application or leave blank (empty string) to make no change to any application.
Detail Information:
Key = appFeaturePackageName
Type = string
Support Information:
Supported on Operating System(s): Pie and Oreo.
Supported from: MX 9.3.
AppGallery Configuration
Use this Sub-group to configure State, Push Notifications, Credential Type, Custom User Name, Custom Password, and Custom Organization Key.
Detail Information:
Key = appgalleryStep
Type = bundle
Support Information:
- Support discontinued from: MX 9.2.
State
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | false |
| On | true |
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Push Notifications
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryPushNotifications
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | false |
| On | true |
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Credential Type
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryCredentialType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Default | true |
| Custom | false |
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Custom User Name
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryCredentialTypeCustomUserName
Type = string
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Custom Password
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryCredentialTypeCustomPassword
Type = string
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Custom Organization Key
This Managed Configuration is deprecated and will be discontinued in a subsequent version.
Detail Information:
Key = appgalleryCredentialTypeCustomOrganizationKey
Type = string
Support Information:
Supported from: MX 6.0.
Support discontinued from: MX 9.2.
Audio Configuration
Use this Sub-group to configure Allow device user Control Vibrate On Call, Best Path Exclude Action, Best Path Exclude Device, Control Vibrate On Call Options, Play AC Detect Sound, Replication Action, and Mute/Vibrate.
Detail Information:
Key = audioStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.2.
Allow device user Control Vibrate On Call
Select whether the device user can change the state of vibrate on call
If the value Do not change is selected, then no change will be made to be made to whether the device user will be able to change the state of vibrate on call options.
If the value Enable is selected, the device user will be able to change the state of vibrate on call options.
If the value Disable is selected, the device user will not be able to change the state of vibrate on call options.
Detail Information:
Key = audioUserContolVibrateForCalls
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Enable | 1 |
| Disable | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.3.
Best Path Exclude Action
Select whether to Action to perform to manage the list of paths to exclude from best path consideration when the device is docked.
If the value Do nothing is selected, then no changes will be made to the list of paths to exclude from best path consideration when the device is docked.
If the value Add Device is selected, the audio path selected in Best Path Exclude Device will be added to the list of of paths to exclude from best path consideration when the device is docked.
If the value Remove Device is selected, the audio path selected in Best Path Exclude Device will be removed from the list of of paths to exclude from best path consideration when the device is docked.
If the value Remove All Devices is selected, all audio paths will be removed the list of of paths to exclude from best path consideration when the device is docked.
Detail Information:
Key = audioBestPathExcludeAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add Device | 1 |
| Remove Device | 2 |
| Remove All Devices | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.3.
Best Path Exclude Device
Select the audio path on which the best path exclude action is to be taken when the device is docked.
Detail Information:
Key = audioBestPathExcludeDevice
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Wired Headset (3.5 mm) | 2 |
| USB Audio | 3 |
| Bluetooth A2DP Audio | 4 |
| HDMI Audio | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.3.
Control Vibrate On Call Options
Select whether the device user can change the state of vibrate for incoming calls.
If the value Do not change is selected, then no change will be made to whether the device will vibrate for incoming calls.
If the value Never Vibrate is selected, the device will never vibrate for incoming calls.
If the value Always Vibrate is selected, the device will always vibrate for incoming calls.
if the value Vibrate First Then Ring Gradually is selected, the device will vibrate first and then the ringer will gradually increase in volume.
Detail Information:
Key = audioSetVibrateOnCallsOption
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Never Vibrate | 1 |
| Always Vibrate | 2 |
| Vibrate First Then Ring Gradually | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.1.
Play AC Detect Sound
Select whether a notification sound will be played when AC power is connected.
If the value Do not change is selected, then no change will be made to whether a notification sound will be played when AC power is connected.
If the value Off is selected, no a notification sound will be played when AC power is connected.
If the value On is selected, a a notification will be played when AC power is connected.
Detail Information:
Key = audioPlayACConnectChime
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Replication Action
Select the audio replication behavior of of the device.
If the value Do not change is selected, then no change will be made to the audio replication behavior of the device.
If the value Replicate headset audio on built-in speaker is selected, audio routed to the headset will also be routed to the built-in speaker. This might be desirable in a situation where the device user may walk away from a vehicle mounted device and leave his headset in the vehicle while performing some task nearby. If an audible alert is also routed to the built-in speaker, the device user might still hear it.
If the value Do not replicate headset audio on built-in speaker is selected, audio routed to the headset will also be routed to the built-in speaker. This might be desirable in a situation where the device is being used in an area where routing audio to the built-in speaker could be disruptive to others in the area.
Detail Information:
Key = audioReplicationAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Replicate headset audio on built-in speaker | 1 |
| Do not replicate headset audio on built-in speaker | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.2.
Mute/Vibrate
Select the mute and vibrate behavior of a device.
If the value Do not change is selected, then no change will be made to the mute and vibrate behavior of a device.
If the value Mute without Vibrate is selected, the volume will be muted (made silent) and the device will NOT vibrate, permitting neither audible nor tactile alerts.
If the value Mute with Vibrate is selected, the volume will be muted (made silent) and the device will vibrate, permitting tactile but NOT audible alerts.
If the value Unmute without Vibrate is selected, the volume will be unmuted (made audible) and the device will NOT vibrate, permitting audible but not tactile alerts.
Detail Information:
Key = audioStepMuteVibrate
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Mute without Vibrate | 1 |
| Mute with Vibrate | 2 |
| Unmute without Vibrate | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Auto Trigger Configuration
Use this Sub-group to configure State and Range
Automatic triggering allows a device user to initiate trigger-activated functions simply by bringing an object within proximity of the device sensor as opposed to requiring the device user to manually initiate such functions.
Detail Information:
Key = autoTriggerStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
State
Select whether and how automatic triggering should occur on a device.
If the value Do not change is selected, then no change will be made to whether and how automatic triggering should occur on a device.
If the value Off is selected, automatic triggering will never occur and the device user will be required to manually initiate trigger-activated functions.
If the value Auto On is selected, automatic triggering may occur automatically if the device is placed into a suitable holster, holder, or stand allowing the device user to initiate trigger-activated functions simply by bringing an object within proximity to the device sensor.
If the value Always On is selected, automatic triggering can always occur automatically , whether the device is placed into a suitable holster, holder, or stand allowing the device user to initiate trigger-activated functions simply by bringing an object within proximity to the device sensor.
Detail Information:
Key = autoTriggerState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 0 |
| Auto On | 1 |
| Always On | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Range
Select the range at which automatic triggering will detect the presence of an object and initiate automatic triggering.
If the value Do not change is selected, then no change will be made to the range at which automatic triggering will detect the presence of an object and initiate automatic triggering.
If the value Near is selected, automatic triggering will occur only when an object is brought within near proximity to the device sensor. This may be desirable if the device is being worn in a holster and hence it is convenient to bring objects very close to the device sensor.
If the value Far is selected, automatic triggering will occur when an object is brought within less near proximity to the device sensor. This may be desirable if the device is located in a stand or holder and hence it is less convenient to have to bring objects very close to the device sensor.
Detail Information:
Key = autoTriggerRange
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Near | 0 |
| Far | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Blacklist Configuration
Use this Sub-group to configure Action, Allow System Package Name, and Disallow System Package Name
Blacklisting applies only to System applications, which are applications built into the device and are therefore always present. It has no effect on user applications, which are installed during staging or at some time after the device is put into service and DO NOT come preinstalled on the device. User apps are controlled using the Whitelist Configuration Group.
WARNING: It is important to understand that an app COULD use the Blacklist Configuration Group to blacklist itself. If an app is blacklisted, then it is prevented from running once the Blacklist Configuration is successfully applied, even if the app being blacklisted was the app that requested the blacklisting to be performed.
Detail Information:
Key = blacklistStep
Type = bundle
Action
Select whether a specified System (built-in) Application on a device will be enabled or disabled.
If the value Do not change is selected, then no change will be made to whether the specified System (built-in) Application on a device will be enabled or disabled.
If the value Allow is selected, you must also specify Allow System Package Name to provide the Android Package Name that identifies the Built-In System Application to be allowed.
If the value Disallow is selected, you must also specify Disallow System Package Name to provide the Android Package Name that identifies the Built-In System Application to be disallowed.
Notes:
All built-in System Applications are enabled by default on devices.
Allowing a built-in System Application allows it to be freely launched, either by the device user or programmatically by other Applications.
Disallowing a built-in System Application prevents it from being launched, either by the device user or programmatically by other Applications.
Since a built-in System Application is built-in, you cannot uninstall it from a device, even if you do not wish it to be used.
To prevent the use of a built-in System Application, you can disable it and thereby prevent its use, even though it remains installed.
Detail Information:
Key = blacklistAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | DisableApplication |
| Allow | EnableApplication |
Support Information:
- Supported from: MX 4.2.
Allow System Package Name
Enter the Android Package Name that identifies a Built-In System Application to be allowed when the Action value Allow is selected for Action or leave blank (empty string) to change no application.
Detail Information:
Key = blacklistActionAllowSystemPackageName
Type = string
Support Information:
- Supported from: MX 4.2.
Disallow System Package Name
Enter the Android Package Name that identifies a Built-In System Application to be disallowed when the Action value Disallow is selected for Action to change no application.
Detail Information:
Key = blacklistActionDisallowSystemPackageName
Type = string
Support Information:
- Supported from: MX 4.2.
Bluetooth Configuration
Use this Sub-group to configure Beacon, Discoverability, New Pairings, Paired Device Action, Silent Pairing Default Method, Turn On/Off Silent Pairing, Turn On/Off Single Pairing Category, Action, Add Rule Device Name, Add Rule Device Upper Address Part, Add Rule MAC Address, Add Rule Pairing PIN Code, Remove Rule Device Name, Remove Rule MAC Address, Remove Rule Device Upper Address Part, and BLE.
Detail Information:
Key = bluetoothStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Beacon Configuration
Use this Sub-group to configure State, Airplane Mode State, Beaconing On Battery Reinsert, Type, Explicit Beacon UUID, AltBeacon, Custom Beacon, Custom Transmit Power Level, Transmit Power Level, Custom Transmit Interval, and Transmit Interval.
Detail Information:
Key = btBeaconConfig
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
State
Select whether a beacon will be emitted (on) or not (off) while the device display is turned off.
If the value Do not change is selected, the current state will not be changed.
If the value Off is selected, a beacon will NOT be emitted when the device display is turned off.
If the value On is selected, a beacon WILL be emitted when the device display is turned off.
Detail Information:
Key = btBeaconState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Airplane Mode State
Select whether the emitting of Beacons while the Device is Powered Off will be conditioned based on whether Airplane Mode was On at the time the Device was powered Off when On is specified for State.
If the value Do not change is selected, the state will not be changed.
If the value Off is selected, the state of Airplane Mode at the time the device is Powered Off will NOT affect beaconing.
If the value On is selected, the state of Airplane Mode at the time the device is Powered Off WILL affect beaconing.
Detail Information:
Key = btBeaconAirplaneModeState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Beaconing On Battery Reinsert
Select whether to emit beacon upon battery reinsertion while device is still powered off when On is specified for State.
If the value Do not change is selected, whether to emit beacon upon battery reinsertion while device is still powered will be left unchanged.
If the value Off is selected, a beacon will NOT be emitted upon battery reinsertion while device is still powered off.
If the value On is selected, a beacon WILL be emitted upon battery reinsertion while device is still powered off. This is the default.
Detail Information:
Key = btBeaconingOnBatteryReinsert
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Type
Select the Type of Beacon to be emitted.
If the value Do not change is selected, then no change will be made to the beacon type.
If the value AltBeacon is selected, an AltBeacon style Beacon will be emitted. If On is specified for Explicit Beacon UUID, then UUID must also be specified.
If the value Custom is selected, a Custom style Beach will be emitted and Data must also be specified to define the Custom Beacon style.
Detail Information:
Key = btBeaconType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| AltBeacon | 2 |
| Custom | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Explicit Beacon UUID
Select whether an explicit UUID will be used for the beacon when AltBeacon is specified for Type.
If the value Do not change is selected, then no change will be made to whether an explicit UUID will be used for the beacon.
If the value Off is selected, then an explicit UUID will NOT be used for the beacon.
If the value On is selected, then an explicit UUID will be used for the beacon.
Detail Information:
Key = btExplicitBeaconUUID
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 0 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
AltBeacon Configuration
Use this Sub-group to configure UUID, ID1, ID2, Manufacturing Byte, and Reference RSSI.
Detail Information:
Key = btAltBeaconConfig
Type = bundle
Support Information:
- NOT supported on Device(s): TC20 and TC25.
UUID
Enter the UUID to use when AltBeacon is specified for Type and On is specified for Explicit Beacon UUID or leave blank (empty string) to leave unchanged.
Detail Information:
Key = btAltBeaconUUID
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
ID1
Enter the 4 hexadecimal characters to use for ID1 when AltBeacon is specified for Type or leave blank (empty string) to leave unchanged or enter EBEB to return to default.
Detail Information:
Key = btAltBeaconID1
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
ID2
Enter the 4 hexadecimal characters to use for ID2 when AltBeacon is specified for Type or leave blank (empty string) to leave unchanged or enter ECDD to return to default.
Detail Information:
Key = btAltBeaconID2
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Manufacturing Byte
Enter the 2 hexadecimal characters to use for the manufacturing byte when AltBeacon is specified for Type or leave blank (empty string) to leave unchanged or enter 00 to return to default.
Detail Information:
Key = btAltBeaconMfgByte
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Reference RSSI
Enter the 2 hexadecimal characters to used for the reference RSSI when AltBeacon is specified for Type or leave blank (empty string) to request use of a calculated value.
Detail Information:
Key = btAltBeaconRefRSSI
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Custom Beacon Configuration
Use this Sub-group to configure Data.
Detail Information:
Key = btCustomBeaconConfig
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Data
Enter the custom UUID/URL/DATA to use for the custom beacon type when Custom is specified for Type. or leave blank (empty string) to leave unchanged.
The value entered should contain up to 56 hexadecimal characters that follow the Bluetooth SIG Advertising format may be used.
Detail Information:
Key = btCustomBeaconData
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Custom Transmit Power Level
Enter the power level (in dBm) of the beacons that will be sent while the device is powered off or leave blank (empty string) to leave unchanged.
The value entered should be between -127 and 1.
Detail Information:
Key = btCustomBeaconXmitPower
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Transmit Power Level
Select the Power Level of the beacon that will be emitted while the device is powered off. If not selected, default value will be used (default values vary by device)
If Do not change is selected, the transmit power level of the beacon will left unchanged.
If High (1dBm) is selected, the transmit power level of the beacon will be set to 1dBm (maximum power)
If Medium (-7dBm) is selected, the transmit power level of the beacon will be set to -7dBm.
If Low Power (-15dBm) is selected, the transmit power level of the beacon will be set to -15dBm
If Ultra Low Power(-21dBm) is selected, the transmit power level of the beacon will be set to -21dBm
If Custom is selected a value between -127 and +1 (dBm) must be entered for Transmit Power Level
Detail Information:
Key = btBeaconXmitPower
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| High (1dBm) | 1 |
| Medium (-7dBm) | 2 |
| Low Power (-15dBm) | 3 |
| Ultra Low Power(-21dBm) | 4 |
| Custom | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Custom Transmit Interval
Enter the Interval between beacons that will be sent while the device is powered off or leave blank (empty string) to leave unchanged.
The value entered should be between 100 and 10240 msec.
Detail Information:
Key = btCustomBeaconXmitInterval
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Transmit Interval
Select the Interval between beacons that will be sent while the device is powered off. If not selected, default value will be used (default values vary by device)
If Do not change is selected, the transmit interval will be left unchanged
If Low Latency (100 ms) is selected, the transmit interval between beacons will be set to 100msec (Low Latency)
If Balanced (250 ms) is selected, the transmit interval between beacons will be set to 250msec (Balanced)
If Low Power (1000 ms) is selected, the transmit interval between beacons will be set to 1000msec (Low Power)
If Custom is selected, the transmit interval between beacons will be set to the value specified in Transmit Interval
Detail Information:
Key = btBeaconXmitInterval
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Low Latency (100 ms) | 1 |
| Balanced (250 ms) | 2 |
| Low Power (1000 ms) | 3 |
| Custom | 4 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Discoverability
Select whether the device is Discoverable via Bluetooth.
Devices are NOT Discoverable via Bluetooth by default except when the Bluetooth Pairing screen of the Settings UI is active.
If the value Do not change is selected, then no change will be made to whether the device is Discoverable via Bluetooth.
If the value Off is selected, the default behavior will be in effect and the device will not be Discoverable via Bluetooth except when the Bluetooth Pairing screen of the Settings UI is active.
If the value On is selected, the default behavior will be overridden and the device will be Discoverable via Bluetooth whenever Bluetooth is enabled (turned on).
Detail Information:
Key = bluetoothDiscoverability
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
New Pairings
Select whether the device will accept new Bluetooth Pairings.
Devices will accept new Bluetooth Pairings by default.
If the value Do not change is selected, then no change will be made to whether the device will accept new Bluetooth Pairings.
If the value Disallow is selected, the default behavior will be overridden and the device will not accept new Bluetooth Pairings.
If the value Allow is selected, the default behavior will be in effect and the device will accept new Bluetooth Pairings.
Detail Information:
Key = bluetoothNewPairings
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Paired Device Action
Select whether the device will clear all paired devices.
If the value Do Not Clear All Paired Devices is selected, then no pairings will be cleared.
If the value Clear All Paired Devices is selected, then all existing pairings will be cleared.
Detail Information:
Key = bluetoothPairedDeviceAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do Not Clear All Paired Devices | |
| Clear All Paired Devices | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.3.
Silent Pairing Default Method
Select whether to allow silent pairing using only Zebra-defined peripherals.
Devices will silently perform Bluetooth Pairings by default.
If the value Do not change is selected, the then no change will be made to the method used as the default for silent pairings.
If the value Disable All is selected, silent pairing will be performed on NO devices.
If the value Enable with Zebra-defined peripherals only is selected, silent pairing will only be performed on Zebra defined devices only.
Detail Information:
Key = bluetoothSilentPairingDefMethod
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable All | 1 |
| Enable with Zebra-defined peripherals only | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Turn On/Off Silent Pairing
Select whether the device can silently perform Bluetooth pairings.
Devices will silently perform Bluetooth Pairings by default.
If the value Do not change is selected, the then no change will be made to whether the device can silently perform Bluetooth pairings.
If the value Disallow is selected, the default behavior will be overridden and the device can not silently perform Bluetooth Pairings.
If the value Allow is selected, the default behavior will be in effect and the device can silently perform Bluetooth Pairings.
Note that even when the device CAN silently perform Bluetooth Pairings, it WILL NOT do so unless Action is used to configure specific silent pairing rules that define how silent pairing should occur.
Detail Information:
Key = bluetoothSilentPairingsState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Allow | 2 |
| Disallow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Turn On/Off Single Pairing Category
Select the category of device of which only a single pairing will be allowed.
Only one device of the specified category will be permitted to pair.
- If the value Headset is selected, only one Bluetooth headset will be permitted to pair at a time.
- If the value Scanner is selected, only one Bluetooth scanner will be permitted to pair at a time.
- If the value Printer is selected, only one Bluetooth printer will be permitted to pair at a time.
- If the value Payment is selected, only one Bluetooth payment will be permitted to pair at a time.
- If the value Dex is selected, only one Bluetooth Dex will be permitted to pair at a time.
Note that even when the device IS configured to permit only single Bluetooth Pairings, it WILL NOT do so unless Action is used to configure specific silent pairing rules that define how single pairing should occur.
Detail Information:
Key = bluetoothSinglePairingsCategory
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Headset | 1 |
| Scanner | 2 |
| Printer | 3 |
| Payment | 4 |
| Dex | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Action
Select an Action to be performed to manage a list of Bluetooth Pairing Rules.
If the value Do nothing is selected, then no Action will be performed to manage a list of Bluetooth Pairing Rules.
If the value Add Rule is selected, you must also specify Add Rule Device Name, to provide the name of the new rule to be added or Add Rule MAC Address, to provide the Bluetooth MAC Address of the new rule to be added. You must also specify Add Rule Device Class or Add Rule Device Upper Address Part to provide the criteria that the new rule will use to determine which new Bluetooth Pairings will be allowed.
If the value Remove Rule is selected, you must specify at least one of the following to provide the information that will be used to determine which rule or rules, which have matching information, will be removed:
- Remove Rule Device Name, to provide the name of the existing rule to be removed or Remove Rule MAC Address to provide the Bluetooth MAC Address of the existing rule to be removed
- Remove Rule Device Class
- Remove Rule Device Upper Address Part
If the value Remove All Rules is selected, then all previously added rules will be removed and you do not need to specify any additional information.
Notes:
- Bluetooth Pairing Rules can be used to enable "Silent" Bluetooth Pairings to be automatically completed without device user interaction. By defining the right set of rules, you can allow pairings between certain types of peripheral devices and a device happen automatically. By automatically is meant that if a pairing is established by an application running on a device, or at the request of a peripheral device, that pairing can complete without device user approval or interaction. Since the list of Bluetooth Pairing Rules is empty by default on devices, "Silent" Bluetooth Pairing is disabled by default, thus all new Bluetooth Pairings will occur manually and thus will require device user interaction to complete . Once one or more Bluetooth Pairing Rules are added, new pairings to selected peripheral devices identified by these rules could be allowed to occur automatically, if allowed by the rules, while all new other new pairings would continue to occur manually.
Detail Information:
Key = bluetoothAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add Rule | |
| Remove Rule | |
| Remove All Rules | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Add Rule Device Name
Enter a Device Name for a new Bluetooth Pairing Rule to be added to the list of Bluetooth Pairing Rules that control the operation of Bluetooth Pairing when the Action value Add Rule is selected for Action.
Note that you can specify Add Rule Device Name or Add Rule MAC Address, but not both.
Detail Information:
Key = bluetoothActionAddRuleName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Add Rule Device Upper Address Part
Enter the Device Upper Address Part for a new rule to be added to the list of rules that control the operation of Bluetooth Silent Pairing when the Action value Add Rule is selected for Action or leave blank (empty string) to specify no address.
When a Device Upper Address Part is specified for a rule, Bluetooth Silent Pairing will automatically complete new Bluetooth Pairings for Bluetooth devices that have the specified Device Upper Address Part in the upper part of their Bluetooth Address.
Detail Information:
Key = bluetoothActionAddRuleUpperAddressPart
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Add Rule MAC Address
Enter the Bluetooth MAC Address XX:XX:XX:XX:XX:XX for a new rule to be added from the list of rules that control the operation of Bluetooth Silent Pairing when the Action value Add Rule is selected for Action or leave blank (empty string) to specify no address.
Note that you can specify Add Rule Device Name or Add Rule MAC Address, but not both.
Detail Information:
Key = bluetoothActionAddRuleMACAddress
Type = string
Support Information:
Supported on Operating System(s): Pie.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Add Rule Pairing PIN Code
Enter the Pairing PIN Code for a new rule to be added to the list of rules that control the operation of Bluetooth Silent Pairing when the Action value Add Rule is selected for Action or leave blank (empty string) to specify no PIN.
When a Pairing PIN Code is specified for a rule, and the device has a Bluetooth version prior to 2.1, Bluetooth Silent Pairing will automatically use the specified Pairing PIN Code to complete Bluetooth Silent Pairings enabled by the Silent Pairing Rule.
When the device has a Bluetooth version 2.1 or later, a Pairing PIN Code is not required to complete Bluetooth Silent Pairings enabled by the Silent Pairing Rule.
Detail Information:
Key = bluetoothActionAddRulePIN
Type = string
Support Information:
Supported on Operating System(s): Pie.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Remove Rule Device Name
Enter a Device Name for a Bluetooth Pairing Rule to be removed from the list of Bluetooth Pairing Rules when the Action value Remove Rule is selected for Action.
Any existing rule that has the specified name will be removed. Leave blank (empty string) if you do not want to remove by Device Name.
Note that you can specify Remove Rule Device Name or Remove Rule MAC Address, but not both.
Detail Information:
Key = bluetoothActionRemoveRuleName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Remove Rule MAC Address
Enter the Bluetooth MAC Address XX:XX:XX:XX:XX:XX that identifies an existing rule to be removed from the list of rules that control the operation of Bluetooth Silent Pairing when the Action value Remove Rule is selected for Action or leave blank (empty string) to specify no address.
Any existing rule that has the specified Bluetooth MAC Address will be removed.
Note that you can specify Remove Rule Device Name or Remove Rule MAC Address, but not both.
Detail Information:
Key = bluetoothActionRemoveRuleMACAddress
Type = string
Support Information:
Supported on Operating System(s): Pie.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Remove Rule Device Upper Address Part
Enter the Device Upper Address Part of an existing rule to be removed from the list of rules that control the operation of Bluetooth Silent Pairing when the Action value Remove Rule is selected for Action or leave blank (empty string) to specify no address.
Any existing rule or rules that have the specified Device Upper Address Part will be removed.
Detail Information:
Key = bluetoothActionRemoveRuleUpperAddressPart
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
BLE Configuration
Use this Sub-group to configure Channel Action, Channel Rule, Channel Rule BLE Channel Blocking, and Channel Rule RF Blocking.
Detail Information:
Key = bleConfig
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Channel Action
Select the Action to be performed on BLE channels used for BLE data connections that are initiated only from target device.
If the value Do nothing is selected, then no Action will be performed on BLE channels used for BLE data connections that are initiated only from target device.
If the value Add Rule is selected, the configuration specified will be added as a rule for BLE data connections. You must also specify Channel Rule and either Channel Rule BLE Channel Blocking or Channel Rule RF Blocking to supply the information defining the rule to be added.
If the value Remove All Rules is selected, all existing rules are deleted.
Detail Information:
Key = bleChannelAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add Rule | |
| Remove All Rules | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.1.
Channel Rule
Select a type rule for BLE channel blocking. The selected type of rule will be added to the list of rules already blocking BLE channels, if any.
Detail Information:
Key = bleChannelRule
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Block BLE Channels | 0 |
| Block RF-Band Based BLE Channels | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.1.
Channel Rule BLE Channel Blocking
Enter BLE channels(s) to block when Add Rule is specified for Channel Action and Block BLE Channels is specified for Channel Rule or leave blank (empty string) to leave unchanged.
Notes:
A valid BLE channel is specified as an integer in the range 0-36.
A BLE channel range can be specified by separating valid low and high channel values by a dash.
Multiple BLE channels or ranges can be specified by separating them by commas.
-Example: 0-5,7,31-35.
Detail Information:
Key = bleBLEChannelBlocking
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.1.
Channel Rule RF Blocking
Enter radio frequency band(s) that all BLE channels should block when when Add Rule is specified for Channel Action and Block RF-Band Based BLE Channels is specified for Channel Rule or leave blank (empty string) to leave unchanged.
Notes:
A valid RF channel is specified as an integer in the range 2402-2480.
An RF channel range can be specified by separating valid low and high channel values by a dash.
Multiple RF channels or ranges can be specified by separating them by commas.
-Example: 2414-2418,2420,2431-2453.
Detail Information:
Key = bleRFBlocking
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.1.
Bug Reporting Configuration
Use this Sub-group to configure Extensions State, Intent Enable, Screenshot Enable, Show In Power Key Menu, ANR Error Action, Unexpected Error Action, Send to Cloud Detail, Store in Device Detail, Send Via Email Detail, Dialog Elements, and Dialog Time Out.
Detail Information:
Key = bugreportStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Extensions State
Select whether the Standard Android or Zebra Extended Bug Reporting should be used for generation of Bug Reports from a device.
If the value Do not change is selected, then no change will be made to whether the Standard Android or Zebra Extended Bug Reporting should be used for generation of Bug Reports from a device.
If the value Off is selected, Standard Android Bug Reporting will be used, with no Zebra Extensions or Enhancements.
If the value On is selected, Zebra Extended Bug Reporting. You may also need to specify additional configuration with the Group to configure the desired behavior and options of Zebra Extended Bug Reporting.
Detail Information:
Key = bugreportBugReportProfile
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | old |
| On | new |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Intent Enable
Select whether the Zebra Extended Bug Reporting should allow a Bug Report to be initiated by an application by sending a broadcast intent with an action value of com.symbol.mxmf.intent.START_FOR_BUG_REPORT. This is meaningful only when Zebra Extended Bug Reporting is enabled.
If the value Do not change is selected, then no change will be made to whether the Zebra Extended Bug Reporting should allow a Bug Report to be initiated by an application by sending a broadcast intent.
If the value Off is selected, Zebra Extended Bug Reporting, if enabled, will not initiate a Bug Report when the defined intent is received.
If the value On is selected, Zebra Extended Bug Reporting, if enabled, will initiate a Bug Report when the defined intent is received.
Detail Information:
Key = bugreportEnableIntent
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Screenshot Enable
Select whether the Zebra Extended Bug Reporting should be allowed to capture screenshots and attach them to Bug Reports.
If the value Do not change is selected, then no change will be made to whether the Zebra Extended Bug Reporting should be allowed to capture screenshots and attach them to Bug Reports.
If the value Off is selected, Zebra Extended Bug Reporting, if enabled, will not capture Bug Reports nor attach them to Bug Reports.
If the value On is selected, Zebra Extended Bug Reporting, if enabled, will capture Bug Reports and attach them to Bug Reports.
Detail Information:
Key = bugreportEnableScreenshot
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Show In Power Key Menu
Select whether Zebra Extended Bug Reporting should display an option to initiate a Bug Report in the menu which appears after long-pressing the power key on the device.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should display an option to initiate a Bug Report in the menu which appears after long-pressing the power key on the device.
If the value Off is selected, Zebra Extended Bug Reporting will NOT add an option to the menu.
If the value On is selected, Zebra Extended Bug Reporting, will add an option to the menu.
Detail Information:
Key = bugreportEnableBRInPwrMenu
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
ANR Error Action
Select whether Zebra Extended Bug Reporting should watch for the occurrence of Application Not Responding (ANR) errors and take action when they are detected.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should watch for the occurrence of Application Not Responding (ANR) errors and take action when they are detected.
If the value Do not capture is selected, Zebra Extended Bug Reporting will NOT watch for the occurrence of ANR errors, and hence will take no action if they occur.
If the value Capture bug report is selected, Zebra Extended Bug Reporting will watch for the occurrence of ANR errors, and will automatically initiate a Bug Report each time it detects that one has occurred.
If the value Capture logcat log is selected, Zebra Extended Bug Reporting will watch for the occurrence of ANR errors, and will automatically initiate a Logcat capture each time it detects that one has occurred.
Detail Information:
Key = bugreportANRErrAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do not capture | NoCapture |
| Capture bug report | CaptureBR |
| Capture logcat log | CaptureLogcat |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.0.
Unexpected Error Action
Select whether Zebra Extended Bug Reporting should watch for the occurrence of Unexpected Application Errors (UAEs) and take action when they are detected.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should watch for the occurrence of Unexpected Application Errors (UAEs) and take action when they are detected.
If the value Do not capture is selected, Zebra Extended Bug Reporting will NOT watch for the occurrence of UAEs, and hence will take no action if they occur.
If the value Capture bug report is selected, Zebra Extended Bug Reporting will watch for the occurrence of UAEs, and will automatically initiate a Bug Report each time it detects that one has occurred.
If the value Capture logcat log is selected, Zebra Extended Bug Reporting will watch for the occurrence of UAEs, and will automatically initiate a Logcat capture each time it detects that one has occurred.
Detail Information:
Key = bugreportUnexpectedErrAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do not capture | NoCapture |
| Capture bug report | CaptureBR |
| Capture logcat log | CaptureLogcat |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.0.
Send to Cloud Detail
Use this Sub-group to configure State and Time to Live.
Detail Information:
Key = bugreportCloudDetails
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
State
Select whether Zebra Extended Bug Reporting should automatically send copies of generated Bug Reports to the Zebra Cloud Server.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should automatically send copies of generated Bug Reports to the Zebra Cloud Server.
If the value Off is selected, Zebra Extended Bug Reporting will NOT send copies of generated Bug Reports to the Zebra Cloud Server.
If the value On is selected, Zebra Extended Bug Reporting, if enabled, will send copies of all generated Bug Reports to the Zebra Cloud Server.
Detail Information:
Key = bugreportCloudEnable
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Time to Live
Select a timeout value, the expiration of which will cause the sending Bug Reports to the Zebra Cloud Server to automatically cease.
If the value Do not change is selected, the configuration will be left unchanged.
If the value Never Expire is selected, and Zebra Extended Bug Reporting is configured to send Bug Reports to the Zebra Cloud Server via the Group Send to Cloud Detail, Zebra Extended Bug Reporting will continue to send Bug Reports to the Zebra Cloud Server, until the configuration is explicitly changed again.
If any other value is selected, at the time Zebra Extended Bug Reporting is configured to send Bug Reports to the Zebra Cloud Server via the Group Send to Cloud Detail, Zebra Extended Bug Reporting will start a timer from the specified timeout value and will cease sending Bug Reports to the Zebra Cloud Server when the timer expires, until the configuration is explicitly changed again.
Detail Information:
Key = bugreportCloudTTL
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Never Expire | 0 |
| 1 Day | 1 |
| 1 Week | 7 |
| 2 Weeks | 14 |
| 1 Month | 30 |
| 3 Months | 90 |
| 6 Months | 180 |
| 1 Year | 365 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Store in Device Detail
Use this Sub-group to configure State, File Path, and Time to Live.
Detail Information:
Key = bugreportStorageDetails
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
State
Select whether Zebra Extended Bug Reporting should automatically store copies of generated Bug Reports in the device.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should automatically store copies of generated Bug Reports in the device.
If the value Off is selected, Zebra Extended Bug Reporting will NOT store copies of generated Bug Reports in the device.
If the value On is selected, Zebra Extended Bug Reporting, if enabled, will store copies of generated Bug Reports in the device.
Detail Information:
Key = bugreportStorageEnable
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
File Path
Enter the path where Zebra Extended Bug Reporting should automatically store copies of generated Bug Reports in the device when the value On is selected for State or leave blank (empty string) to leave unchanged.
Note that either fixed or removable storage are supported, but the specified path must be valid at the time Bug Report is generated. If no path is specified, bug reports are stored in /storage/sdcard0/BugReports/, which will always be a valid path for storage of Bug Reports on all devices.
Detail Information:
Key = bugreportBugReportFilePath
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Time to Live
Select a timeout value, the expiration of which will cause the storing of Bug Reports in the device to automatically cease.
If the value Do not change is selected, the configuration will be left unchanged.
If the value Never Expire is selected, and when Zebra Extended Bug Reporting is configured to store Bug Reports in the device via the Group Store in Device Detail, Zebra Extended Bug Reporting will continue to store Bug Reports in the device until the configuration is explicitly changed again.
If any other value is selected, at the time Zebra Extended Bug Reporting is configured to store Bug Reports in the device via the Group Store in Device Detail, a timer will be started for the specified timeout value and when that timer expires, Zebra Extended Bug Reporting will cease storing Bug Reports in the device, until the configuration is explicitly changed again.
Detail Information:
Key = bugreportStorageTTL
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Never Expire | 0 |
| 1 Day | 1 |
| 1 Week | 7 |
| 2 Weeks | 14 |
| 1 Month | 30 |
| 3 Months | 90 |
| 6 Months | 180 |
| 1 Year | 365 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Send Via Email Detail
Use this Sub-group to configure State, SMTP Host, SMTP Port, Sender ID, Sender Password, Send To Address, and Time to Live.
Detail Information:
Key = bugreportEmailDetails
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
State
Select whether Zebra Extended Bug Reporting should automatically send copies of generated Bug Reports via email.
If the value Do not change is selected, then no change will be made to whether Zebra Extended Bug Reporting should automatically send copies of generated Bug Reports via email.
If the value Off is selected, Zebra Extended Bug Reporting will NOT send copies of generated Bug Reports via email.
If the value On is selected, Zebra Extended Bug Reporting, if enabled, will send copies of generated Bug Reports via email. You should also specify additional information to provide the details of the email to be sent.
Detail Information:
Key = bugreportEmailEnable
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | False |
| On | True |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
SMTP Host
Enter the address or host name of the SMTP (email) Server via which emails will be sent to deliver generated Bug Reports, and should be specified when the value On is selected for State or leave blank (empty string) to leave unchanged.
Note that you must have access to an email account on the selected SMTP Server and you must specify additional configuration within the Group to configure Zebra Extended Bug Reporting to send emails via that SMTP Server. In addition, you must have access to a valid email account to use as the destination of the emails, which is NOT required to be on the same SMTP Server, and must specify details of the email address within the Group, to configure Zebra Extended Bug Reporting to send the emails to that destination.
Detail Information:
Key = bugreportEmailSMTPHost
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
SMTP Port
Enter the TCP port number of the SMTP (email) Server via which emails will be sent to deliver generated Bug Reports when SMTP Host is specified or leave blank (empty string) to leave unchanged.
Detail Information:
Key = bugreportEmailSMTPPort
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Sender ID
Enter the ID of the email account that will be used as the source (from address) of emails that will be sent to deliver generated Bug Reports, and should be specified when the value On is selected for State and when a valid SMTP (email) Server is specified via SMTP Host or leave blank (empty string) to leave unchanged.
Note that you must have access to a valid email account on the configured SMTP (email) Server and must specify additional information in the Group, such as Sender Password to enable Zebra Extended Bug Reporting to successfully send the emails using that account via that server.
Detail Information:
Key = bugreportEmailSendersID
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Sender Password
Enter the password of the email account that will be used as the source (from address) of emails that will be sent to deliver generated Bug Reports, and should be specified when the value On is selected for State and a valid SMTP (email) Server is specified via SMTP Host and a valid email address is specified via Sender ID or leave blank (empty string) to leave unchanged.
Detail Information:
Key = bugreportEmailSendersPassword
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Send To Address
Enter the email address of the email account that will be used as the destination (to address) of emails that will be sent to deliver generated Bug Reports, and should be specified when the value On is selected for State or leave blank (empty string) to leave unchanged.
Detail Information:
Key = bugreportEmailSendTo
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Time to Live
Select a timeout value, the expiration of which will cause the sending of Bug Reports via email to automatically cease.
If the value Do not change is selected, the configuration will be left unchanged.
If the value Never Expire is selected, and Zebra Extended Bug Reporting is configured to send Bug Reports to the Zebra Cloud Server via the Group Send Via Email Detail, Zebra Extended Bug Reporting will continue to send Bug Reports via email, until the configuration is explicitly changed again.
If any other value is selected, at the time Zebra Extended Bug Reporting is configured to send Bug Reports via email via the Group Send Via Email Detail, Zebra Extended Bug Reporting will start a timer from the specified timeout value and will cease sending Bug Reports via email when the timer expires, until the configuration is explicitly changed again.
Detail Information:
Key = bugreportEmailTTL
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Never Expire | 0 |
| 1 Day | 1 |
| 1 Week | 7 |
| 2 Weeks | 14 |
| 1 Month | 30 |
| 3 Months | 90 |
| 6 Months | 180 |
| 1 Year | 365 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Dialog Elements
Use this Sub-array to configure one or more Element Detail(s).
Detail Information:
Key = bugreportDialogElements
Type = bundle_array
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Element Detail
Use this Sub-group to configure Type, Error Name Text Box Text, Label Text, and Text Box Text.
Detail Information:
Key = bugreportDialogElement
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Type
Select the type of a single dialog element being included in the dialog that will be presented to the device user to collect information that will be included in generated Bug Reports.
If the value Do nothing is selected, then no element will be created.
If the value ErrorNameTextBox is selected, a text box will be added to the dialog presented to the device user in which the name to be assigned to the Bug Report being generated can be entered. You must also specify Error Name Text Box Text to provide a text to be pre-populated into the text box.
If the value Label is selected, a text label will be added to the dialog presented to the device user. You must also specify Label Text to provide the text to be populated into the label.
If the value TextBox is selected, a text box will be added to the dialog presented to the device user in which generic text can be entered. You must also specify Text Box Text to provide the text to be pre-populated into the text box. The specified text will to provide guidance to the device user about the expected value and will disappear when the user begins typing into the text box.
If the value VoiceRecordButton is selected, a voice record button will be added to the dialog presented to the device user. Clicking this button will allow the device user to record a verbal explanation of the bug to be attached to the generated Bug Report.
Detail Information:
Key = bugreportDialogElementType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| ErrorNameTextBox | AddErrorNameTextBox |
| Label | AddLabel |
| TextBox | AddTextBox |
| VoiceRecordButton | AddVoiceRecordButton |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Error Name Text Box Text
Enter the text to be pre-populated into a text box that will be added to the dialog presented to the device user in which the name to be assigned to the Bug Report being generated can be entered and should be specified when the value ErrorNameTextBox is selected for Type or leave blank (empty string) to pre-populate no text.
Detail Information:
Key = bugreportDialogElementTypeErrorNameTextBoxText
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Label Text
Enter the text of a label that will be added to the dialog presented to the device user when the value Label is selected for Type or leave blank (empty string) to specify no label.
Detail Information:
Key = bugreportDialogElementTypeLabelText
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Text Box Text
Enter the text that be pre-populated into a text box added to the dialog presented to the device user into which generic text can be entered and should be specified when the value TextBox is selected for Type or leave blank (empty string) to pre-populate no text.
The specified text should provide guidance to the device user about the value they should enter and will be overwritted by the value entered into the text box.
Detail Information:
Key = bugreportDialogElementTypeTextBoxText
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Dialog Time Out
Enter the amount of inactivity time (time in milliseconds with no device user activity), after which the dialog presented to the device user will automatically be dismissed or leave blank (empty string) to leave unchanged.
Dismissing the Bug Report causes it to be completed as if the device user had explicitly clicked the Submit Button.
Detail Information:
Key = bugreportDialogTimeout
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Camera Configuration
Use this Sub-group to configure Use Of Back Camera, Use Of Front Camera, and Use Of Imager.
Detail Information:
Key = cameraStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Use Of Back Camera
Select whether the Rear Facing Camera, if present on a device, can be used to take pictures.
If the value Do not change is selected, then no change will be made to whether the Rear Facing Camera, if present on a device, can be used to take pictures.
If the value Off is selected, no applications or services running on the device will be allowed to take pictures using the Rear Facing Camera.
If the value On is selected, any applications or services running on the device will be allowed to take pictures using the Rear Facing Camera.
Detail Information:
Key = cameraUseOfBack
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Use Of Front Camera
Select whether the Front Facing (selfie) Camera, if present on a device, can be used to take pictures.
If the value Do not change is selected, then no change will be made to whether the Front Facing (selfie) Camera, if present on a device, can be used to take pictures.
If the value Off is selected, no applications or services running on the device will be allowed to take pictures using the Front Facing (selfie) Camera.
If the value On is selected, any applications or services running on the device will be allowed to take pictures using the Front Facing (selfie) Camera.
Detail Information:
Key = cameraUseOfFront
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Use Of Imager
Select whether the Imager (special-purpose image capture device), if present on a device, can be used to take pictures.
If the value Do not change, is selected, then no change will be made to whether the Imager (special-purpose image capture device), if present on a device, can be used to take pictures.
If the value Off is selected, no applications or services running on the device will be allowed to take pictures using the Imager (special-purpose image capture device) Camera.
If the value On is selected, any applications or services running on the device will be allowed to take pictures using the Imager (special-purpose image capture device) Camera.
Detail Information:
Key = cameraUseOfImager
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Clock Configuration
Use this Sub-group to configure Time Mode, Manual Date, Manual Time, Manual UTC Date, Manual UTC Time, Auto NTP Server Address, Auto NTP Sync Interval, Time Zone Mode, Zone, and Time Format.
Detail Information:
Key = clockStep
Type = bundle
Time Mode
Select whether time and date configuration will be performed explicitly, through configuration, or automatically, by connecting to a Network Time Protocol (NTP) Server.
If the value Do not change is selected, no change will be made.
If the value Manual is selected, you should also specify one or more of the following: Manual UTC Date, Manual UTC Time, Manual Date, or Manual Time.
If the value Auto is selected, you must also specify Auto NTP Server Address and Auto NTP Sync Interval.
Detail Information:
Key = clockTimeMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Manual | false |
| Auto | true |
Support Information:
- Supported from: MX 4.2.
Manual Date
Enter the date to be set on a device when the value Manual is selected for Time Mode or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockManualDate
Type = string
Support Information:
- Supported from: MX 4.1.
Manual Time
Enter the time to be set on a device when the value Manual is selected for Time Mode or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockManualTime
Type = string
Support Information:
- Supported from: MX 4.1.
Manual UTC Date
Enter the date to be set on a device normalized to universal time (UTC) when the value Manual is selected for Time Mode or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockManualDateUTC
Type = string
Support Information:
- Supported from: MX 10.2.
Manual UTC Time
Enter the time to be set on a device normalized to universal time (UTC) when the value Manual is selected for Time Mode or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockManualTimeUTC
Type = string
Support Information:
- Supported from: MX 10.2.
Auto NTP Server Address
Enter the address of the Network Time Protocol (NTP) Server to be used to perform automatic date and time configuration on a device when the value Auto is selected for Time Mode or leave blank (empty string) to leave unchanged.
If specified, then you must also specify Auto NTP Sync Interval to provide the interval at which the time should be acquired from the specified server.
Detail Information:
Key = clockAutoNtpServer
Type = string
Support Information:
- Supported from: MX 4.2.
Auto NTP Sync Interval
Select the interval at which automatic date and time configuration will be performed on a device when the value Auto is selected for Time Mode and when Auto NTP Server Address.
If the value Do not change is selected, then no change will be made to the interval at which automatic date and time configuration will be performed on a device.
If the value 30 minutes is selected, the interval at which automatic date and time configuration will be set to 30 minutes.
If the value 60 minutes is selected, the interval at which automatic date and time configuration will be set to 60 minutes.
If the value 6 hours is selected, the interval at which automatic date and time configuration will be set to 6 hours.
If the value 24 hours is selected, the interval at which automatic date and time configuration will be set to 24 hours.
Detail Information:
Key = clockAutoNtpSyncInterval
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 30 minutes | 00:30:00 |
| 60 minutes | 00:60:00 |
| 6 hours | 06:00:00 |
| 24 hours | 24:00:00 |
Support Information:
- Supported from: MX 4.2.
Time Zone Mode
Select whether time zone configuration will be performed explicitly, using other configurations in the Group, or automatically, by connecting to a Network Identity and Time Zone (NITZ) source.
If the value Do not change is selected, no change will be made.
If the value Manual is selected, time zone configuration will need to be performed explicitly, using other configurations in the Group.
If the value Auto is selected, time zone configuration will be performed automatically, by connecting to a Network Identity and Time Zone (NITZ) source.
Detail Information:
Key = clockTimeZoneMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Manual | false |
| Auto | true |
Support Information:
- Supported from: MX 6.0.
Zone
Enter the time zone to be set on a device when the value Manual is selected for Time Zone Mode or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockManualTimeZone
Type = string
Support Information:
- Supported from: MX 4.1.
Time Format
Select whether the format in which time will be displayed on the device will be in 12 hour (AM/PM) or 24 hour (military) format or leave blank (empty string) to leave unchanged.
Detail Information:
Key = clockTimeFormat
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 12 | 2 |
| 24 | 1 |
Support Information:
- Supported from: MX 6.0.
DataWedge Configuration
Use this Sub-group to configure Database File, NG Simulscan Template File, Automatic Database Import, Intent Access Control of Configuration APIs, Intent Access Control of Notification APIs, Intent Access Control of Query APIs, Intent Access Control of Runtime APIs, Manual, and Programmatic Import.
Detail Information:
Key = dataWedgeStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Database File
Enter the device path and file name of a DataWedge Database file (full or partial) to replace or be merged to modify the current configuration of DataWedge or leave blank (empty string) to do nothing.
Detail Information:
Key = dataWedgeDatabaseFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
NG Simulscan Template File
Enter the device path and file name of a valid Simulscan template file to be imported to replace or add to DataWedge or leave blank (empty string) to do nothing.
Detail Information:
Key = dataWedgeSimulscanTemplateFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.0.
Automatic Database Import
Select whether DataWedge Database Files deployed to the DataWedge autoimport folder on the device will automatically trigger importing of the file.
Detail Information:
Key = dataWedgeAutoImport
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 0 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Intent Access Control of Configuration APIs
Select the Access Control to be used by DataWedge Configuration Intent APIs.
If the value Do not change is selected, then no change will be made.
If the value Uncontrolled (default) - Allow use by all Applications is selected, then access will Uncontrolled and thus use will be Allowed by all Applications. This is the default.
If the value Controlled - Allow use only by Whitelisted Applications is selected, then access will Controlled and thus use will be Allowed only by Whitelisted Applications.
Detail Information:
Key = dataWedgeIntentAccessControlConfigurationAPIs
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Uncontrolled (default) - Allow use by all Applications | 1 |
| Controlled - Allow use only by Whitelisted Applications | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Intent Access Control of Notification APIs
Select the Access Control to be used by DataWedge Notification Intent APIs.
If the value Do not change is selected, then no change will be made.
If the value Uncontrolled (default) - Allow use by all Applications is selected, then access will Uncontrolled and thus use will be Allowed by all Applications. This is the default.
If the value Controlled - Allow use only by Whitelisted Applications is selected, then access will Controlled and thus use will be Allowed only by Whitelisted Applications.
Detail Information:
Key = dataWedgeIntentAccessControlNotificationAPIs
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Uncontrolled (default) - Allow use by all Applications | 1 |
| Controlled - Allow use only by Whitelisted Applications | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Intent Access Control of Query APIs
Select the Access Control to be used by DataWedge Query Intent APIs.
If the value Do not change is selected, then no change will be made.
If the value Uncontrolled (default) - Allow use by all Applications is selected, then access will Uncontrolled and thus use will be Allowed by all Applications. This is the default.
If the value Controlled - Allow use only by Whitelisted Applications is selected, then access will Controlled and thus use will be Allowed only by Whitelisted Applications.
Detail Information:
Key = dataWedgeIntentAccessControlQueryAPIs
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Uncontrolled (default) - Allow use by all Applications | 1 |
| Controlled - Allow use only by Whitelisted Applications | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Intent Access Control of Runtime APIs
Select the Access Control to be used by DataWedge Runtime Intent APIs.
If the value Do not change is selected, then no change will be made.
If the value Uncontrolled (default) - Allow use by all Applications is selected, then access will Uncontrolled and thus use will be Allowed by all Applications. This is the default.
If the value Controlled - Allow use only by Whitelisted Applications is selected, then access will Controlled and thus use will be Allowed only by Whitelisted Applications.
Detail Information:
Key = dataWedgeIntentAccessControlRuntimeAPIs
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Uncontrolled (default) - Allow use by all Applications | 1 |
| Controlled - Allow use only by Whitelisted Applications | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Manual Configuration
Select whether device users will be allowed to manually alter the configuration of DataWedge from the DataWedge configuration UI.
If the value Do not change is selected, then no change will be made to whether device users will be allowed to manually alter the configuration of DataWedge from the DataWedge configuration UI.
If the value Disallow is selected, then device users will NOT be allowed to manually alter the configuration of DataWedge from the DataWedge configuration UI.
If the value Allow is selected, then device users will be allowed to manually alter the configuration of DataWedge from the DataWedge configuration UI.
Detail Information:
Key = dataWedgeManualConfiguration
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Programmatic Import
Select whether whether applications will be allowed to programmatically import DataWedge Configuration Files using the DataWedge Intent API.
If the value Do not change is selected, then no change will be made to whether applications will be allowed to programmatically import DataWedge Configuration Files using the DataWedge Intent API.
If the value Disallow is selected, then applications will NOT be allowed to programmatically import DataWedge Configuration Files using the DataWedge Intent API.
If the value Allow is selected, then applications will be allowed to programmatically import DataWedge Configuration Files using the DataWedge Intent API.
Detail Information:
Key = dataWedgeApiImport
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Device Administration Configuration
Use this Sub-group to configure Action, Allow Submit XML Package Name, Disallow Submit XML Package Name, Submit XML, Allow Package Update Package Name, Disallow Package Update Package Name, Reserve User ID Package Name, Reserve User ID Package Signature, Unreserve User ID Package Name, Lock Screen Wallpaper, Custom Lock Screen Wallpaper, App Management Notifications, Notifications on Lock Screen, Secure Start-up Selection by device user, and Alert Button.
Detail Information:
Key = devadminStep
Type = bundle
Action
Select an Action to control access to or utilize the Zebra MX Management System on a device.
If the value Do nothing is selected, then no action will be performed.
If the value Allow App To Submit Xml is selected, a single application or service is allowed to submit XML for processing by the Zebra MX Management System. You must also specify Allow Submit XML Package Name to provide the Android Package Name that identifies the application or service is to be allowed.
If the value Disallow App From Submitting Xml is selected, a single application service is disallowed from submitting XML for processing by the Zebra MX Management System. You must also specify Disallow Submit XML Package Name to provide the Android Package Name that identifies the application or service is to be disallowed.
If the value Submit Xml is selected, you must also specify Submit XML to provide the XML string that will be submitted for processing by the .Zebra MX Management System.
If the value Reserve UID for App is selected, you must also specify Reserve User ID Package Name to identify the particular package to which the User ID is reserved.
You must also specify Reserve User ID Package Signature to assure that the package to which the User ID is reserved is the right one.
If the value Unreserve UID for App is selected, you must also specify Unreserve User ID Package Name to identify the particular package to which the User ID is reserved.
If the value Allow App To Update is selected, you must also specify Allow Package Update Package Name to identify the particular package allowed to be updated. This is only necessary for applications that were previously disallowed using Disallow App From Update
If the value Disallow App From Update is selected, you must also specify Disallow Package Update Package Name to identify the particular package to be prevented from being updated.
Detail Information:
Key = devadminAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Allow App To Submit Xml | AllowSubmitXml |
| Disallow App From Submitting Xml | DisallowSubmitXml |
| Submit Xml | SubmitXml |
| Reserve UID for App | ReserveUID |
| Unreserve UID for App | UnreserveUID |
| Allow App To Update | AllowApplicationUpgrade |
| Disallow App From Update | DisallowApplicationUpgrade |
Support Information:
- Supported from: MX 9.2.
Allow Submit XML Package Name
Enter the Android Package Name that identifies the application or service is to be allowed when the value Allow App To Submit Xml is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionAllowSubmitXmlPackageName
Type = string
Support Information:
- Supported from: MX 4.2.
Disallow Submit XML Package Name
Enter the Android Package Name that identifies the application or service is to be disallowed when the value Disallow App From Submitting Xml is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionDisallowSubmitXmlPackageName
Type = string
Support Information:
- Supported from: MX 4.2.
Submit XML
Enter an XML string to be submitted for processing by the .Zebra MX Management System, when the value Submit Xml is selected for Action.
Detail Information:
Key = devadminActionSubmitXml
Type = string
Allow Package Update Package Name
Enter the Android Package Name of the application allowed to be updated, when the value Allow App To Update is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionAllowUpdatePackageName
Type = string
Support Information:
- Supported from: MX 10.3.
Disallow Package Update Package Name
Enter the Android Package Name of the application not allowed to be updated, when the value Disallow App From Update is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionDisallowUpdatePackageName
Type = string
Support Information:
- Supported from: MX 10.3.
Reserve User ID Package Name
Enter the Android Package Name of the application needing a reserved UID, when the value Reserve UID for App is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionReserveUIDPackageName
Type = string
Support Information:
- Supported from: MX 9.2.
Reserve User ID Package Signature
Enter the Android Package Signature of the application needing a reserved UID, when the value Reserve UID for App is selected for Action or leave blank (empty string) to do nothing. The value entered must be the Base 64 encoded content of the DER format certificate used to sign the application. The DER-format certificate can be obtained from the application author or can be extracted from the APK file if necessary. Base 64 encoding must be performed to ensure that the value is suitable for transmission as a Managed Configuration.
Detail Information:
Key = devadminActionReserveUIDPackageSignature
Type = string
Support Information:
- Supported from: MX 9.2.
Unreserve User ID Package Name
Enter the Android Package Name of the application whose user ID can be released (unreserved), when the value Unreserve UID for App is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = devadminActionUnreserveUIDPackageName
Type = string
Support Information:
- Supported from: MX 9.2.
Lock Screen Wallpaper
Select the wallpaper to use on the lock screen of the device.
If the value Do not change is selected, then no change will be made to the wallpaper to use on the lock screen of the device.
If the value Restore to default is selected, the default lock screen wallpaper will be used and you should NOT specify Custom Lock Screen Wallpaper.
If the value Custom is selected, the custom wallpaper will be used and you must specify in Custom Lock Screen Wallpaper to supply the file.
Detail Information:
Key = daLockScreenWallpaper
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Custom Lock Screen Wallpaper
Enter the path and file name of an image file on the device (.jpg or .png) to use as the custom wallpaper when Custom is specified for Lock Screen Wallpaper.
Detail Information:
Key = daCustomLockWallpaper
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
App Management Notifications
Select whether the device user receives notifications when the Device Owner installs, uninstalls or upgrades applications. Applies to Android 11 and later.
If the value *Do not change is selected, then no change will be made to whether the device user receives notifications.
If the value Show is selected, notifications will be shown to the user when the Device Owner installs, uninstalls, or upgrades applications.
If the value Hide is selected, no notifications will be shown to the user when the Device Owner installs, uninstalls, or upgrades applications.
Detail Information:
Key = daSilentAppInstall
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Show | 1 |
| Hide | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Notifications on Lock Screen
Select the types of notifications to show on the lock screen.
If the value Do not change is selected, then no change will be made to the types of notifications to show on the lock screen.
If the value Show all content is selected, all notifications will be shown.
If the value Show only non-sensitive content is selected, only non-sensitive content will be shown.
If the value Hide notifications is selected, all notifications will be hidden.
Detail Information:
Key = daNotificationsOnLockScreen
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Show all content | 1 |
| Show only non-sensitive content | 2 |
| Hide notifications | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Secure Start-up Selection by device user
Select whether the device user will be allowed to Select Secure Start-up when changing pin/password/pattern.
If the value Do not change is selected, then no change will be made to whether the device user will be allowed to Select Secure Start-up when changing pin/password/pattern.
If the value Enable the YES button is selected, the device user will be allowed Select Secure Start-up when changing pin/password/pattern.
If the value Disable the YES button is selected, the device user will NOT be allowed Select Secure Start-up when changing pin/password/pattern.
Detail Information:
Key = secureStartupDialog
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Enable the YES button | 1 |
| Disable the YES button | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.0.
Alert Button
Use this Sub-group to configure Mode, Action, Keep Device Awake, Key Identifier, Intent Action, Intent Category, Intent Class, Intent Package Name, Intent Data URI, Intent File, Intent MIME Type, Intent Extras, and Sensor Parameter.
Detail Information:
Key = alertButton
Type = bundle
Support Information:
- NOT supported on Device(s): TC20 and TC25.
Mode
Select the mode used by the Alert Button on a device.
If the value Do not change is selected, then no change will be made to the mode used by the Alert Button on a device.
If the value Schedule sending of Intent on key presses is selected, the action specified in Action will be performed when the configured button is pressed. You must also specify Action to provide the action to be done along with Key Identifier to define the key identifier to be used to trigger the alert.
If the value Cancel sending of Intent on key presses is selected, the previously configured action is canceled.
If the value Schedule sending of Intent on sensor trigger is selected, the action specified in Action will be performed when the sensors triggered. You must also specify the parameter Sensor Parameter
If the value Cancel sending of Intent on sensor trigger is selected, the previously configured action for sensor trigger is canceled.
Detail Information:
Key = alertButtonMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Schedule sending of Intent on key presses | 2 |
| Cancel sending of Intent on key presses | 3 |
| Schedule sending of Intent on sensor trigger | 4 |
| Cancel sending of Intent on sensor trigger | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Action
Select the Action to be taken when the Alert Button is pressed, when the value of Schedule sending of Intent on key presses is selected for Mode.
Detail Information:
Key = alertButtonModeAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| StartActivity | StartActivity |
| StartService | StartService |
| Broadcast | Broadcast |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Keep Device Awake
Select whether the device should stay awake when the Alert Button is configured, when the value Schedule sending of Intent on key presses is selected for Mode.
If the value Do not change is selected, then no change will be made to whether the device should stay awake when the Alert Button is configured.
If the value No is specified, the device will NOT stay awake when the Alert Button is configured.
If the value Yes is specified, the device will stay awake when the Alert Button is configured.
Note that the data type of this MC has changed from bool to string, in order to add a Do nothing value to better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "alertButtonModeKeepAwake" to "alertButtonModeKeepAwakeString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will no longer contain that value for this MC and will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = alertButtonModeKeepAwakeString
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Yes | true |
| No | false |
Support Information:
- Supported from: MX 10.2.
Key Identifier
Select the Key Identifier to be used for the Alert Button, when the value Schedule sending of Intent on key presses is selected for Mode.
Detail Information:
Key = alertButtonModeKeyIdentifier
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| 0 | 0 |
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| 4 | 4 |
| 5 | 5 |
| 6 | 6 |
| 7 | 7 |
| 8 | 8 |
| 9 | 9 |
| A | A |
| B | B |
| C | C |
| D | D |
| E | E |
| F | F |
| G | G |
| H | H |
| I | I |
| J | J |
| K | K |
| L | L |
| M | M |
| N | N |
| O | O |
| P | P |
| Q | Q |
| R | R |
| S | S |
| T | T |
| U | U |
| V | V |
| W | W |
| X | X |
| Y | Y |
| Z | Z |
| .(Period) | DOT |
| , (Comma) | COMMA |
| *(Star) | STAR |
| #(Pound) | POUND |
| F1 | F1 |
| F2 | F2 |
| F3 | F3 |
| F4 | F4 |
| F5 | F5 |
| F6 | F6 |
| F7 | F7 |
| F8 | F8 |
| F9 | F9 |
| F10 | F10 |
| F11 | F11 |
| F12 | F12 |
| Enter | ENTER |
| Up | UP |
| Down | DOWN |
| Left | LEFT |
| Right | RIGHT |
| Escape | ESC |
| Backspace | BACKSPACE |
| Space | SPACE |
| Return | RETURN |
| Clear | CLR |
| Field Exit | FIELD_EXIT |
| Alt | ALT |
| Control | CTRL |
| Shift | SHIFT |
| Blue | BLUE |
| Orange | ORANGE |
| Diamond | DIAMOND |
| Green Dot | GREEN |
| Red Dot | RED |
| Volume Up | VOLUMEUP |
| Volume Down | VOLUMEDOWN |
| Scan | SCAN |
| Grip Trigger | GRIP_TRIGGER |
| Grip Trigger 2 | GRIP_TRIGGER_2 |
| Button L1 | LEFT_TRIGGER_1 |
| Button L2 | LEFT_TRIGGER_2 |
| Button R1 | RIGHT_TRIGGER_1 |
| Button R2 | RIGHT_TRIGGER_2 |
| Left Trigger | LEFT_TRIGGER |
| Right Trigger | RIGHT_TRIGGER |
| Center Trigger | CENTER_TRIGGER |
| Gun Trigger | GUN_TRIGGER |
| Headset Button | HEADSET_HOOK |
| Back | BACK |
| Home | HOME |
| Menu | MENU |
| Recent | RECENT |
| Search | SEARCH |
| Keyboard Backlight | KEYLIGHT |
| Display Backlight | LAMP |
| Power | POWER |
| P1 Button | P1 |
| P2 Button | P2 |
| P3 Button | P3 |
| P4 Button | P4 |
| P5 Button | P5 |
| P6 Button | P6 |
| Rear Button | REAR_BUTTON |
| Left External Trigger | LEFT_EXTERNAL_TRIGGER |
| Right External Trigger | RIGHT_EXTERNAL_TRIGGER |
| Touch NAV_PAD | NAV_PAD |
| Macro 1 | M1 |
| Macro 2 | M2 |
| Macro 3 | M3 |
| Macro 4 | M4 |
| Macro 5 | M5 |
| Macro 6 | M6 |
| Brightness Up | BRIGHTNESSUP |
| Brightness Down | BRIGHTNESSDOWN |
| Keyboard | KEYBOARD |
| Keyboard Backlight Brightness Up | KEYLIGHTUP |
| Keyboard Backlight Brightness Down | KEYLIGHTDOWN |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Action
Enter the action value of an Android Intent to be sent when the Alert Button is activated.
An action value is NOT mandatory to specify for an Android Intent. But an action value is commonly used to identify the purpose of an Android Intent. This can be especially when the application or service to be invoked supports multiple functions, in which case the action value is commonly used to identify which function to perform when invoking that application or service. You will need to consult the documentation or developer of a given application or service to determine whether an action value is needed and, if so, which value will invoke the desired behavior.
Detail Information:
Key = alertButtonModeIntentAction
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Category
Enter the category value of an Android Intent to be sent to invoke the alert button is activated.
A category value is NOT mandatory to specify for an Android Intent. But a category value is commonly used to help identify the purpose of an Android Intent. This can be especially when the application or service to be invoked supports many functions, in which case many action values may be used to identify those functions and it may be useful to categorize those functions. In some cases, the same action value might be supported in more than one category. You will need to consult the documentation or developer of a given application or service to determine whether a category value is needed and, if so, which value will invoke the desired behavior.
Detail Information:
Key = alertButtonModeIntentCategory
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Class
Enter the Android Class that identifies an Android Component within an application or service to invoke when the Alert Button is activated.
Detail Information:
Key = alertButtonModeIntentClass
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Package Name
Enter the Android Package Name of the application to invoke when the Alert Button is activated.
It is not mandatory to specify the Android Package Name when sending an Android Intent, but is is often advisable.
- When an Android Package Name is specified, the intent becomes an Explicit Intent and the intent can ONLY be sent to an application or service with that Android Package Name and no other. This can increase security and is often used when the intent being sent requires any sensitive data. You must also specify Class whenever an Android Package Name is specified, since an Explicit Intent is always sent to an Android Component, which is identified by a Android Package Name and a Class within that Package.
- When no Android Package Name is specified, the intent becomes an Implicit Intent and the intent may be sent to any application or service that has registered its ability to handle that intent. This can increase flexibility and is often used when the intent being sent requires no sensitive data and when it may be desirable to dynamically control which application or service is ultimately invoked to handle that intent.
Detail Information:
Key = alertButtonModeIntentPackageName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Data URI
Enter a Uniform Resource Identifier (URI) that identifies some data, in the form of a resource on the device (e.g. a file in the device file system) or off the device (e.g. a resource available via a network) that should be utilized by the application or service invoked when the Alert Button is pressed
Whether the intended recipient of the intent expects a URI to be specified as part of the intent or not is up to that recipient and/or the definition of the intent that recipient is designed to consume.
Detail Information:
Key = alertButtonModeIntentDataUri
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent File
Enter intent file to be set for the intent to be sent.
Detail Information:
Key = alertButtonModeIntentFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent MIME Type
Enter a Multipurpose Internet Mail Extensions (MIME) type to use when processing the intent data and when the Alert Button is activated.
Normally the type would be inferred from the data itself. Setting a MIME type explicitly, disables automatic type detection and and forces handling according to the specified type.
Detail Information:
Key = alertButtonModeIntentMimeType
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Intent Extras
Use this Sub-group to configure Extra #1 Name, Extra #1 Type, Extra #1 Value, Extra #2 Name, Extra #2 Type, Extra #2 Value, Extra #3 Name, Extra #3 Type, Extra #3 Value, Extra #4 Name, Extra #4 Type, Extra #4 Value, Extra #5 Name, Extra #5 Type, and Extra #5 Value with up to 5 intent extras to be included in the intent triggered when the Alert Button is pressed.
Detail Information:
Key = alertButtonModeIntentExtras
Type = bundle
Support Information:
- NOT supported on Device(s): TC20 and TC25.
Extra #1 Name
Enter the intent extra name to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When Extra #1 Name is specified, you must also specify Extra #1 Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = extraName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #1 Type
Select the intent extra value type to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent.
If the value Do nothing is selected, then no extra will be attached to the intent.
If the value Standard Integer is selected, an extra of type Standard Integer will be attached to the intent and an Standard Integer value must be specified in Extra #1 Value.
If the value Character is selected, an extra of type Character will be attached to the intent and a Character value must be specified in Extra #1 Value.
If the value Character Sequence is selected, an extra of type Character Sequence will be attached to the intent and a Character Sequence value must be specified in Extra #1 Value.
If the value Floating Point is selected, an extra of type Floating Point will be attached to the intent and a Floating Point value must be specified in Extra #1 Value.
If the value Long Integer is selected, an extra of type Long Integer will be attached to the intent and a Long Integer value must be specified in Extra #1 Value.
If the value Boolean is selected, an extra of type Boolean will be attached to the intent and a Boolean value must be specified in Extra #1 Value.
If the value Short Integer is selected, an extra of type Short Integer will be attached to the intent and a Short Integer value must be specified in Extra #1 Value.
If the value Double Precision Floating Point is selected, an extra of type Double Precision Floating will be attached to the intent and a Double Precision Floating value must be specified in Extra #1 Value.
If the value String is selected, an extra of type String will be attached to the intent and a String value must be specified in Extra #1 Value.
If the value Single Byte Integer is selected, an extra of type Single Byte Integer will be attached to the intent and a Single Byte Integer value must be specified in Extra #1 Value.
Detail Information:
Key = extraType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Standard Integer | int |
| Character | char |
| Character Sequence | charsequence |
| Floating Point | float |
| Long Integer | long |
| Boolean | boolean |
| Short Integer | short |
| Double Precision Floating Point | double |
| String | string |
| Single Byte Integer | byte |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #1 Value
Enter the intent extra value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Enter the value associated with Extra #1 Name corresponding to the type specified in Extra #1 Type
Detail Information:
Key = extraValue
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #2 Name
Enter the intent extra name to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When Extra #2 Name is specified, you must also specify Extra #2 Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = extra1Name
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #2 Type
Select the intent extra value type to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent.
If the value Do nothing is selected, then no extra will be attached to the intent.
If the value Standard Integer is selected, an extra of type Standard Integer will be attached to the intent and an Standard Integer value must be specified in Extra #2 Value.
If the value Character is selected, an extra of type Character will be attached to the intent and a Character value must be specified in Extra #2 Value.
If the value Character Sequence is selected, an extra of type Character Sequence will be attached to the intent and a Character Sequence value must be specified in Extra #2 Value.
If the value Floating Point is selected, an extra of type Floating Point will be attached to the intent and a Floating Point value must be specified in Extra #2 Value.
If the value Long Integer is selected, an extra of type Long Integer will be attached to the intent and a Long Integer value must be specified in Extra #2 Value.
If the value Boolean is selected, an extra of type Boolean will be attached to the intent and a Boolean value must be specified in Extra #2 Value.
If the value Short Integer is selected, an extra of type Short Integer will be attached to the intent and a Short Integer value must be specified in Extra #2 Value.
If the value Double Precision Floating Point is selected, an extra of type Double Precision Floating will be attached to the intent and a Double Precision Floating value must be specified in Extra #2 Value.
If the value String is selected, an extra of type String will be attached to the intent and a String value must be specified in Extra #2 Value.
If the value Single Byte Integer is selected, an extra of type Single Byte Integer will be attached to the intent and a Single Byte Integer value must be specified in Extra #2 Value.
Detail Information:
Key = extra1Type
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Standard Integer | int |
| Character | char |
| Character Sequence | charsequence |
| Floating Point | float |
| Long Integer | long |
| Boolean | boolean |
| Short Integer | short |
| Double Precision Floating Point | double |
| String | string |
| Single Byte Integer | byte |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #2 Value
Enter the intent extra value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Enter the value associated with Extra #2 Name corresponding to the type specified in Extra #2 Type
Detail Information:
Key = extra1Value
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #3 Name
Enter the intent extra name to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When Extra #3 Name is specified, you must also specify Extra #3 Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = extra2Name
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #3 Type
Select the intent extra value type to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent.
If the value Do nothing is selected, then no extra will be attached to the intent.
If the value Standard Integer is selected, an extra of type Standard Integer will be attached to the intent and an Standard Integer value must be specified in Extra #3 Value.
If the value Character is selected, an extra of type Character will be attached to the intent and a Character value must be specified in Extra #3 Value.
If the value Character Sequence is selected, an extra of type Character Sequence will be attached to the intent and a Character Sequence value must be specified in Extra #3 Value.
If the value Floating Point is selected, an extra of type Floating Point will be attached to the intent and a Floating Point value must be specified in Extra #3 Value.
If the value Long Integer is selected, an extra of type Long Integer will be attached to the intent and a Long Integer value must be specified in Extra #3 Value.
If the value Boolean is selected, an extra of type Boolean will be attached to the intent and a Boolean value must be specified in Extra #3 Value.
If the value Short Integer is selected, an extra of type Short Integer will be attached to the intent and a Short Integer value must be specified in Extra #3 Value.
If the value Double Precision Floating Point is selected, an extra of type Double Precision Floating will be attached to the intent and a Double Precision Floating value must be specified in Extra #3 Value.
If the value String is selected, an extra of type String will be attached to the intent and a String value must be specified in Extra #3 Value.
If the value Single Byte Integer is selected, an extra of type Single Byte Integer will be attached to the intent and a Single Byte Integer value must be specified in Extra #3 Value.
Detail Information:
Key = extra2Type
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Standard Integer | int |
| Character | char |
| Character Sequence | charsequence |
| Floating Point | float |
| Long Integer | long |
| Boolean | boolean |
| Short Integer | short |
| Double Precision Floating Point | double |
| String | string |
| Single Byte Integer | byte |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #3 Value
Enter the intent extra value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Enter the value associated with Extra #3 Name corresponding to the type specified in Extra #3 Type
Detail Information:
Key = extra2Value
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #4 Name
Enter the intent extra name to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When Extra #4 Name is specified, you must also specify Extra #4 Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = extra3Name
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #4 Type
Select the intent extra value type to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent.
If the value Do nothing is selected, then no extra will be attached to the intent.
If the value Standard Integer is selected, an extra of type Standard Integer will be attached to the intent and an Standard Integer value must be specified in Extra #4 Value.
If the value Character is selected, an extra of type Character will be attached to the intent and a Character value must be specified in Extra #4 Value.
If the value Character Sequence is selected, an extra of type Character Sequence will be attached to the intent and a Character Sequence value must be specified in Extra #4 Value.
If the value Floating Point is selected, an extra of type Floating Point will be attached to the intent and a Floating Point value must be specified in Extra #4 Value.
If the value Long Integer is selected, an extra of type Long Integer will be attached to the intent and a Long Integer value must be specified in Extra #4 Value.
If the value Boolean is selected, an extra of type Boolean will be attached to the intent and a Boolean value must be specified in Extra #4 Value.
If the value Short Integer is selected, an extra of type Short Integer will be attached to the intent and a Short Integer value must be specified in Extra #4 Value.
If the value Double Precision Floating Point is selected, an extra of type Double Precision Floating will be attached to the intent and a Double Precision Floating value must be specified in Extra #4 Value.
If the value String is selected, an extra of type String will be attached to the intent and a String value must be specified in Extra #4 Value.
If the value Single Byte Integer is selected, an extra of type Single Byte Integer will be attached to the intent and a Single Byte Integer value must be specified in Extra #4 Value.
Detail Information:
Key = extra3Type
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Standard Integer | int |
| Character | char |
| Character Sequence | charsequence |
| Floating Point | float |
| Long Integer | long |
| Boolean | boolean |
| Short Integer | short |
| Double Precision Floating Point | double |
| String | string |
| Single Byte Integer | byte |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #4 Value
Enter the intent extra value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Enter the value associated with Extra #4 Name corresponding to the type specified in Extra #4 Type
Detail Information:
Key = extra3Value
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #5 Name
Enter the intent extra name to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When Extra #5 Name is specified, you must also specify Extra #5 Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = extra4Name
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #5 Type
Select the intent extra value type to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent.
If the value Do nothing is selected, then no extra will be attached to the intent.
If the value Standard Integer is selected, an extra of type Standard Integer will be attached to the intent and an Standard Integer value must be specified in Extra #5 Value.
If the value Character is selected, an extra of type Character will be attached to the intent and a Character value must be specified in Extra #5 Value.
If the value Character Sequence is selected, an extra of type Character Sequence will be attached to the intent and a Character Sequence value must be specified in Extra #5 Value.
If the value Floating Point is selected, an extra of type Floating Point will be attached to the intent and a Floating Point value must be specified in Extra #5 Value.
If the value Long Integer is selected, an extra of type Long Integer will be attached to the intent and a Long Integer value must be specified in Extra #5 Value.
If the value Boolean is selected, an extra of type Boolean will be attached to the intent and a Boolean value must be specified in Extra #5 Value.
If the value Short Integer is selected, an extra of type Short Integer will be attached to the intent and a Short Integer value must be specified in Extra #5 Value.
If the value Double Precision Floating Point is selected, an extra of type Double Precision Floating will be attached to the intent and a Double Precision Floating value must be specified in Extra #5 Value.
If the value String is selected, an extra of type String will be attached to the intent and a String value must be specified in Extra #5 Value.
If the value Single Byte Integer is selected, an extra of type Single Byte Integer will be attached to the intent and a Single Byte Integer value must be specified in Extra #5 Value.
Detail Information:
Key = extra4Type
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Standard Integer | int |
| Character | char |
| Character Sequence | charsequence |
| Floating Point | float |
| Long Integer | long |
| Boolean | boolean |
| Short Integer | short |
| Double Precision Floating Point | double |
| String | string |
| Single Byte Integer | byte |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Extra #5 Value
Enter the intent extra value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Enter the value associated with Extra #5 Name corresponding to the type specified in Extra #5 Type
Detail Information:
Key = extra4Value
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Sensor Parameter
Enter name of the extra to send in the intent that is sent for sensor status when the value Schedule sending of Intent on sensor trigger is selected for Mode and StartActivity, or StartService, or Broadcast is selected for Action.
Detail Information:
Key = alertButtonModeSensorParameter
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Device Central Configuration
Use this Sub-group to configure Bluetooth On/Off Control, Bluetooth Pairing Control, Firmware Update Button, and Smart Leash.
Detail Information:
Key = deviceCentralStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Bluetooth On/Off Control
Select whether the device user should be allowed to use the Device Central UI to control Bluetooth Power.
If the value Do not change is selected, then no change will be made to whether the device user should be allowed to use the Device Central UI to control Bluetooth Power.
If the value Disallow is selected, Device Central will NOT provide UI that allows the device user to control the Bluetooth power state.
If the value Allow is selected, Device Central will provide UI that allows the device user to control the Bluetooth power state.
Detail Information:
Key = deviceCentralBluetoothOnOffControl
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Bluetooth Pairing Control
Select whether Device Central system should allow multiple pairings to the same Device Class. This feature has been deprecated in Device Central. Look in the Bluetooth Configuration
If the value Do not change is selected, then no change will be made to whether Device Central system should allow multiple pairings to the same Device Class.
If the value Multiple Pairings Per Device Class is selected, Device Central system will allow multiple pairings at a time for each Bluetooth Device Class (e.g. multiple headsets and/or multiple printers).
If the value Single Pairing Per Device Class is selected, Device Central system will only allow one pairing at a time for each Bluetooth Device Class (e.g. one headset and one printer).
Detail Information:
Key = deviceCentralBluetoothPairingControl
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Multiple Pairings Per Device Class | 2 |
| Single Pairing Per Device Class | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Firmware Update Button
Select whether the device user should be allowed to use the Device Central UI to initiate a Firmware Update.
If the value Do not change is selected, then no change will be made to whether the device user should be allowed to use the Device Central UI to initiate a Firmware Update.
If the value Disallow is selected, Device Central will NOT provide UI that allows the device user to initiate a Firmware Update.
If the value Allow is selected, Device Central will provide UI that allows the device user to initiate a Firmware Update.
Detail Information:
Key = deviceCentralFirmwareUpdateButton
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Smart Leash
Use this Sub-group to configure Audio Feedback Repeat Count, Audio Feedback Sound, Audio Feedback State, Audio Feedback Volume, Haptic Feedback State, Haptic Feedback Time, Settings UI, and State.
Detail Information:
Key = deviceCentralSmartLeash
Type = bundle
Support Information:
- NOT supported on Device(s): TC20 and TC25.
Audio Feedback Repeat Count
Enter the number of times the sound should be repeated when Audio Feedback State is set to Turn On. Supported values range between 0 and 100 or leave blank (empty string) to leave unchanged.
Detail Information:
Key = SmartLeashAudioFeedbackRepeatCount
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Audio Feedback Sound
Enter the sound to be used when the Smart Leash Audio Feedback is active (on). The name of an existing Ringtone or the fully qualified path to an audio file is expected. .wav, .ogg, .mp3 and .m4a audio file types are supported or leave blank (empty string) to leave unchanged.
Detail Information:
Key = SmartLeashAudioFeedbackSound
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Audio Feedback State
Select whether the Smart Leash Audio Feedback is active (on) or inactive (off).
If the value Do not change is selected, then no change will be made to whether the Smart Leash Audio Feedback is active (on) or inactive (off).
If the value Turn Off is selected, Device Central will turn on Audio Feedback in Smart Leash.
If the value Turn On is selected, Device Central will turn off Audio Feedback in Smart Leash.
Detail Information:
Key = SmartLeashAudioFeedbackState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Audio Feedback Volume
Enter the percentage of volume that should be used when Audio Feedback State is set to Turn On. Supported values range between 1 and 100 or leave blank (empty string) to leave unchanged.
Detail Information:
Key = SmartLeashAudioFeedbackVolume
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Haptic Feedback State
Select whether the Smart Leash Haptic Feedback is active (on) or inactive (off).
If the value Do not change is selected, then no change will be made to whether the Smart Leash Haptic Feedback is active (on) or inactive (off).
If the value Turn Off is selected, Device Central will turn on Audio Feedback in Smart Leash.
If the value Turn On is selected, Device Central will turn off Audio Feedback in Smart Leash.
Detail Information:
Key = SmartLeashHapticFeedbackState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Haptic Feedback Time
Enter the duration of vibration when the Haptic Feedback State is set to Turn On or leave blank (empty string) to leave unchanged.
Detail Information:
Key = SmartLeashHapticFeedbackDuration
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Settings UI
Select whether the device user should be allowed to use the Device Central UI to configure Smart Leash.
If the value Do not change is selected, then no change will be made to whether the device user should be allowed to use the Device Central UI to configure Smart Leash.
If the value Disallow is selected, Device Central will NOT provide UI that allows the device user to configure Smart Leash.
If the value Allow is selected, Device Central will provide UI that allows the device user to configure Smart Leash.
Detail Information:
Key = SmartLeashSettingsUI
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
State
Select whether the Smart Leash active (on) or inactive (off).
If the value Do not change is selected, then no change will be made to whether the Smart Leash active (on) or inactive (off).
If the value Turn Off is selected, Device Central will turn on Smart Leash.
If the value Turn On is selected, Device Central will turn off Smart Leash.
Detail Information:
Key = SmartLeashState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
DHCP Option Configuration
Use this Sub-group to configure Request Boot File Name (Option 67), Request NTP Server (Option 42), Request TFTP Server Address (Option 66), Request Domain Search List (Option 119), Request TFTP Server Names (Option 150), Request Vendor Specific Option#1 (Option 186), Request Vendor Specific Option#2 (Option 188), Request Vendor Specific Option#3 (Option 230), Send Client Identifier State (Option 61), Send Client Identifier Value (Option 61), Send Host Name State (Option 12), Send Host Name Value (Option 12), Send User Class State (Option 77), Send User Class Value (Option 77), Send Vendor Class State (Option 60), Send Vendor Class Value (Option 60), Send FQDN State (Option 81), Send FQDN Value (Option 81), Send FQDN Flag (Option 81), Request Custom Option Number, Request Custom Option State, Send Custom Option Number, Send Custom Option State, and Send Custom Option Value
The DHCP Client on the device sends a DHCP Request to a DHCP Server and receives back a DHCP Acknowledgment. A DHCP Request sent by a device can contain information about the device or the DHCP Client, and can contain requests for additional information from the DHCP Server. A DHCP Acknowledgment sent by the DHCP Server contains the IP Address assigned to the device by the DHCP Server along with other related information and any additional information requested by the device in the DHCP Request.
DHCP Options are variable-length strings that are identified by DHCP Options Numbers that can be included in a DHCP Request or a DHCP Acknowledgment to convey information between a DHCP Client and a DHCP Server. From the point of view of the device where the DHCP Client is running, a DHCP Option can allow the DHCP Client to Send information to the DHCP Server or can allow the DHCP Client to Request the DHCP Server to return information to the DHCP Client.
Detail Information:
Key = dhcpStep
Type = bundle
Request Boot File Name (Option 67)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the Boot File Name and return it using DHCP Option 67 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the Boot File Name and return it using DHCP Option 67 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the Boot File Name and return it using DHCP Option 67 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the Boot File Name and return it using DHCP Option 67 along with the IP Address.
Detail Information:
Key = dhcpRequestBootFileName
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.4.
Request NTP Server (Option 42)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the NTP Server and return it using DHCP Option 42 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the NTP Server and return it using DHCP Option 42 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the NTP Server and return it using DHCP Option 42 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the NTP Server and return it using DHCP Option 42 along with the IP Address.
Detail Information:
Key = dhcpRequestNtpServer
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.4.
Request TFTP Server Address (Option 66)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Address and return it using DHCP Option 66 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Address and return it using DHCP Option 66 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the TFTP Server Address and return it using DHCP Option 66 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Address and return it using DHCP Option 66 along with the IP Address.
Detail Information:
Key = dhcpRequestTftpServerAddress
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.4.
Request Domain Search List (Option 119)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the Domain Search List and return it using DHCP Option 119 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the Domain Search List and return it using DHCP Option 119 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the Domain Search List and return it using DHCP Option 119 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the Domain Search List and return it using DHCP Option 119 along with the IP Address.
Detail Information:
Key = dhcpRequestDomainSearchList
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.4.
Request TFTP Server Names (Option 150)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Name(s) and return it using DHCP Option 150 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Name(s) and return it using DHCP Option 150 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the TFTP Server Name(s) and return it using DHCP Option 150 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the TFTP Server Name(s) and return it using DHCP Option 150 along with the IP Address.
Detail Information:
Key = dhcpRequestTftpServerNames
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.4.
Request Vendor Specific Option#1 (Option 186)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the First Vendor Specific Option and return it using DHCP Option 186 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the First Vendor Specific Option and return it using DHCP Option 186 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the First Vendor Specific Option and return it using DHCP Option 186 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the First Vendor Specific Option and return it using DHCP Option 186 along with the IP Address.
Detail Information:
Key = dhcpRequestVendorSpecific1
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.5.
Request Vendor Specific Option#2 (Option 188)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the Second Vendor Specific Option and return it using DHCP Option 188 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the Second Vendor Specific Option and return it using DHCP Option 188 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the Second Vendor Specific Option and return it using DHCP Option 188 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the Second Vendor Specific Option and return it using DHCP Option 188 along with the IP Address.
Detail Information:
Key = dhcpRequestVendorSpecific2
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 4.5.
Request Vendor Specific Option#3 (Option 230)
Select whether the DHCP Client on a device will request that the DHCP Server acquire the Third Vendor Specific Option and return it using DHCP Option 230 along with the IP Address.
If the value Do not change is specified, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire the Third Vendor Specific Option and return it using DHCP Option 230 along with the IP Address.
If the value Off is specified, the DHCP Client on a device will NOT request that the DHCP Server acquire the Third Vendor Specific Option and return it using DHCP Option 230 along with the IP Address.
If the value On is specified, the DHCP Client on a device will request that the DHCP Server acquire the Third Vendor Specific Option and return it using DHCP Option 230 along with the IP Address.
Detail Information:
Key = dhcpRequestVendorSpecific3
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 6.3.
Send Client Identifier State (Option 61)
Select whether the DHCP Client on a device will send a Client Identifier to the DHCP Server using DHCP Option 61 when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will send a Client Identifier to the DHCP Server using DHCP Option 61 when requesting an IP Address.
If the value Off is selected, the DHCP Client on a device will NOT send a Client Identifier to the DHCP Server using DHCP Option 61 when requesting an IP Address and you should NOT specify Send Client Identifier State (Option 61).
If the value On is selected, the DHCP Client on a device will send a Client Identifier to the DHCP Server using DHCP Option 61 when requesting an IP Address and you must specify Send Client Identifier State (Option 61).to provide the value of the Client Identifier to be sent.
Detail Information:
Key = dhcpSendClientIdentifierState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 6.3.
Send Client Identifier Value (Option 61)
Enter the Client Identifier that the DHCP Client on a device will send to the DHCP Server using DHCP Option 12 when requesting an IP Address when the value On is selected for Send Client Identifier State (Option 61).
Detail Information:
Key = dhcpSendClientIdentifierValue
Type = string
Support Information:
- Supported from: MX 6.3.
Send Host Name State (Option 12)
Select whether the DHCP Client on a device will send a Host Name to the DHCP Server using DHCP Option 12 when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will send a Host Name to the DHCP Server using DHCP Option 12 when requesting an IP Address.
If the value Off is selected, the DHCP Client on a device will NOT send a Host Name to the DHCP Server using DHCP Option 12 when requesting an IP Address and you should NOT specify Send Host Name Value (Option 12).
If the value On is selected, the DHCP Client on a device will send a *Host Name to the DHCP Server using DHCP Option 12 when requesting an IP Address and you must also specify Send Host Name Value (Option 12) to provide the value of the Host Name to be sent.
Detail Information:
Key = dhcpSendHostNameState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 4.4.
Send Host Name Value (Option 12)
Enter the Host Name that the DHCP Client on a device will send to the DHCP Server using DHCP Option 12 when requesting an IP Address when the value On* is selected for Send Host Name State (Option 12).
Detail Information:
Key = dhcpSendHostNameValue
Type = string
Support Information:
- Supported from: MX 4.4.
Send User Class State (Option 77)
Select whether the DHCP Client on a device will send a User Class to the DHCP Server using DHCP Option 77 when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will send a User Class to the DHCP Server using DHCP Option 77 when requesting an IP Address.
If the value Off is selected, the DHCP Client on a device will NOT send a User Class to the DHCP Server using DHCP Option 77 when requesting an IP Address and you should not specify Send User Class Value (Option 77).
If the value On is selected, DHCP Client on a device will send a *User Class to the DHCP Server using DHCP Option 77 when requesting an IP Address and you must also specify Send User Class Value (Option 77) to provide the value of the User Class to be sent.
Detail Information:
Key = dhcpSendUserClassState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 4.4.
Send User Class Value (Option 77)
Enter the User Class that the DHCP Client on a device will send to the DHCP Server using DHCP Option 77 when requesting an IP Address when the value On is selected for Send User Class State (Option 77).
Detail Information:
Key = dhcpSendUserClassValue
Type = string
Support Information:
- Supported from: MX 4.4.
Send Vendor Class State (Option 60)
Select whether the DHCP Client on a device will send a Vendor Class to the DHCP Server using DHCP Option 60 when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will send a Vendor Class to the DHCP Server using DHCP Option 60 when requesting an IP Address.
If the value Off is selected, you do not need to specify any additional information.
If the value On is selected, you must also specify Send Vendor Class Value (Option 60) to provide the value of the Vendor Class to be sent.
Detail Information:
Key = dhcpSendVendorClassState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 4.5.
Send Vendor Class Value (Option 60)
Enter the Vendor Class that the DHCP Client on a device will send to the DHCP Server using DHCP Option 60 when requesting an IP Address when the value On is selected for Send Vendor Class State (Option 60).
Detail Information:
Key = dhcpSendVendorClassValue
Type = string
Support Information:
- Supported from: MX 4.5.
Send FQDN State (Option 81)
Select whether the DHCP Client on a device will send a Fully Qualified Domain Name (FQDN) to the DHCP Server using DHCP Option 81 when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will send a Fully Qualified Domain Name (FQDN) to the DHCP Server using DHCP Option 81 when requesting an IP Address.
If the value Off is selected, the DHCP Client on a device will NOT send a Fully Qualified Domain Name (FQDN) to the DHCP Server using DHCP Option 81 when requesting an IP Address and a value should NOT be specified for Send FQDN Value (Option 81).
If the value On is selected, the DHCP Client on a device will send a *Fully Qualified Domain Name (FQDN) to the DHCP Server using DHCP Option 81 when requesting an IP Address and a value must also be specified for Send FQDN Value (Option 81) to provide that Fully Qualified Domain Name (FQDN) and for Send FQDN Flag (Option 81) to specify the flags to be sent with it.
Detail Information:
Key = dhcpSendFqdnState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 6.3.
Send FQDN Value (Option 81)
Enter the Fully Qualified Domain Name (FQDN) that will be sent to the DHCP Server using DHCP Option 81 when requesting an IP Address. This value must be specified when the value On is selected for Send FQDN State (Option 81). You must also specify Send FQDN Flag (Option 81) to provide the flags to be sent along with the *Fully Qualified Domain Name (FQDN).
Detail Information:
Key = dhcpSendFqdnValue
Type = string
Support Information:
- Supported from: MX 6.3.
Send FQDN Flag (Option 81)
Enter the flags to be sent along with the Fully Qualified Domain Name (FQDN) that will be sent to the DHCP Server using DHCP Option 81 when requesting an IP Address when the value On is selected for Send FQDN State (Option 81) and when Send FQDN Value (Option 81) is specified.
Detail Information:
Key = dhcpSendFqdnFlag
Type = string
Support Information:
- Supported from: MX 6.3.
Request Custom Option Number
Enter the option number of a custom DHCP Option that the DHCP Client on a device should request from DHCP Server and return along with the IP Address when the value On is selected for Request Custom Option State.
Detail Information:
Key = dhcpRequestCustomOptionNumber
Type = string
Support Information:
- Supported from: MX 8.1.
Request Custom Option State
Select whether the DHCP Client on a device will request that the DHCP Server acquire a custom DHCP option and return it along with the IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server acquire a custom DHCP option and return it along with the IP Address.
If the value Off is selected, no custom DHCP Option will be requested and you should not specify Request Custom Option Number.
If the value On is selected, a custom DHCP Option will be requested and you must also specify Request Custom Option Number to provide the custom option number to be requested.
Detail Information:
Key = dhcpRequestCustomOptionState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | 1 |
| Off | 2 |
Support Information:
- Supported from: MX 8.1.
Send Custom Option Number
Enter the option number of a custom DHCP Option that the DHCP Client on a device should send when requesting an IP Address when the value On is selected for Send Custom Option State. You must also specify Send Custom Option State to provide the value to be sent for the custom DHCP Option.
Detail Information:
Key = dhcpSendCustomOptionNumber
Type = string
Support Information:
- Supported from: MX 8.1.
Send Custom Option State
Select whether the DHCP Client on a device will request that the DHCP Server send a custom DHCP option when requesting an IP Address.
If the value Do not change is selected, then no change will be made to whether the DHCP Client on a device will request that the DHCP Server send a custom DHCP option when requesting an IP Address.
If the value Off is selected, no custom DHCP Option will be sent and you should NOT specify Send Custom Option Number or Send Custom Option Value.
If the value On is selected, a custom DHCP Option will be sent and you must also specify Send Custom Option Number to provide the custom option number to be sent and Send Custom Option Value to provide the custom option value to be sent.
Detail Information:
Key = dhcpSendCustomOptionState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | |
| Off | 2 |
Support Information:
- Supported from: MX 8.1.
Send Custom Option Value
Enter the option value for a custom DHCP Option that the DHCP Client on a device should send when requesting an IP Address when the value On is selected for Send Custom Option State and when Send Custom Option Number is specified.
Detail Information:
Key = dhcpSendCustomOptionValue
Type = string
Support Information:
- Supported from: MX 8.1.
Display Configuration
Use this Sub-group to configure Force Activities Resizable, Resizable Windows, Secondary Display Mode, Secondary Display Remote Control, Timeout, Blanking Mode, Stay Awake, Signal, Polarity, Debounce Delay, Allowed Orientations, Lock Override Button, Locked Orientation Positions, Rotation Mode, Set Display Size, Set Font Size, Backlight Adaptive Brightness, and Brightness.
Detail Information:
Key = displayStep
Type = bundle
Force Activities Resizable
Select whether the device display and secondary display will force activities to be treated as resizable even if not declared in the application manifest.
If Do not change is selected, then no change will be made to whether the device display and secondary display will force activities to be treated as resizable even if not declared in the application manifest.
If All Activities Resizable is selected, all activities running on the primary (mobile) display and the secondary (external) display will be forced to be treated as resizable even if not declared in the application manifest.
If Follow Application Manifest is selected, activities running on the primary (mobile) display and the secondary (external) display will be treated as resizable only if declared to be resizable in the application manifest.
Detail Information:
Key = displayForceActivitiesResizable
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| All Activities Resizable | 1 |
| Follow Application Manifest | 2 |
Support Information:
- Supported from: MX 10.5.
Resizable Windows
Select whether the primary (mobile) display will support resizable windows.
If the value Do not change is selected, then no change will be made to whether the primary (mobile) display will support resizable windows.
If the valueTurn On is selected, the primary (mobile) display will support resizable windows.
If the valueTurn Off is selected, the primary (mobile) display will NOT support resizable windows.
Note:
By default, the primary (mobile) display will NOT support resizable windows, and this can be used to change that.
By default, the secondary (desktop) display will support resizable windows, and this CANNOT be used to change that.
Detail Information:
Key = displayResizableWindows
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn On | 1 |
| Turn Off | 2 |
Support Information:
- Supported from: MX 10.5.
Secondary Display Mode
Select the mode to use for the secondary (external) display.
If Present Independent Desktop is selected, then no change will be made to the mode to use for the secondary (external) display.
If Present Independent Desktop is selected, the secondary display will present an independent desktop with content that is separate from the content displayed on the primary (mobile) display.
If Mirror Device Screen is selected, the secondary display will present a duplicate (mirror) of the content displayed on the primary (mobile) display.
Detail Information:
Key = secondaryDisplayMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Present Independent Desktop | 1 |
| Mirror Device Screen | 2 |
Support Information:
- Supported from: MX 10.5.
Secondary Display Remote Control
Select the display on which remote operations will be performed.
If the value Do not change is selected, then no change will be made to the display on which remote operations will be performed.
If the value Primary (Mobile) is selected, remote control operations will always be performed on the primary (mobile) display.
If the value Secondary (Desktop) is selected, remote control operations will be performed on the secondary (desktop) display, if one is available, or will fall back to the primary (mobile) display.
Detail Information:
Key = secondaryDisplayRemoteControl
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Primary (Mobile) | 0 |
| Secondary (Desktop) | 1 |
Support Information:
- Supported from: MX 11.1.
Timeout
Select the amount of inactivity, in seconds, after which the device will timeout and automatically turn the Display Screen off.
If the value Do not change is selected, then no change will be made to the amount of inactivity, in seconds, after which the device will timeout and automatically turn the Display Screen off.
If the value 15 seconds is selected, device will timeout and automatically turn the Display Screen off after 15 seconds of inactivity.
If the value 30 seconds is selected, device will timeout and automatically turn the Display Screen off after 30 seconds of inactivity.
If the value 1 minute is selected, device will timeout and automatically turn the Display Screen off after 1 minute of inactivity.
If the value 2 minutes is selected, device will timeout and automatically turn the Display Screen off after 2 minutes of inactivity.
If the value 5 minutes is selected, device will timeout and automatically turn the Display Screen off after 5 minutes of inactivity.
If the value 10 minutes is selected, device will timeout and automatically turn the Display Screen off after 10 minutes of inactivity.
If the value 30 minutes is selected, device will timeout and automatically turn the Display Screen off after 30 minutes of inactivity.
Detail Information:
Key = displayTimeout
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 15 seconds | 15 |
| 30 seconds | 30 |
| 1 minute | 60 |
| 2 minutes | 120 |
| 5 minutes | 300 |
| 10 minutes | 600 |
| 30 minutes | 1800 |
| Never | 65535 |
Support Information:
- Supported from: MX 4.3.
Blanking Mode
Select whether the Display will automatically Blank (display nothing) on a device.
When a device user is operating a vehicle with a vehicle-mounted device, it is often advisable, for safety or regulatory reasons, to prevent the device user from interacting with the device or being distracted by the Display of the device, while the vehicle is in motion. Display Blanking Mode provides the ability to configure the device such that the Display Screen will automatically be Blanked (display nothing) when an electrical signal (such as one attached to the accelerator) is detected that indicates that the vehicle is in motion.
If the value Do not change is selected, then no change will be made to Display Blanking.
If the value Never Blank is selected, Display Blanking Mode will be turned off and hence automatic Display Blanking will never occur.
If the value Blank When Triggered by Signal is selected, Display Blanking Mode will be turned on and hence the Display will be automatically Blanked and you must also specify all of the following:
Signal - to specify the signal that will be used to activate automatic Display Blanking.
Polarity - to specify the polarity of the signal specified via Signal that will be used to activate automatic Blanking.
Debounce Delay - to specify the time that will be used to debounce the signal specified via Signal.
Note that at present, Display Blanking Mode is supported only on VC8x and similarly equipped vehicle-mounted Zebra mobile computers running Android.
Detail Information:
Key = displayBlankingMode
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Stay Awake
Select whether the Display will Stay Awake (prevent automatic time out that turns the Display Screen off) when the device is connected to external power.
If the value Do not change is selected, the then no change will be made to .whether the Display will Stay Awake (prevent automatic time out that turns the Display Screen off) when the device is connected to external power.
If the value Off is selected, the Display will NOT Stay Awake and hence the device will time out and automatically turn the Display Screen off, when the Display Screen timeout, configured via Timeout expires, even if the device is connected to external power.
If the value On is selected, the Display will Stay Awake and hence the device will not time out and will not automatically turn the Display Screen off, so long as the device is connected to external power, even if the Display Screen timeout, configured via Timeout expires.
Configuring a device to Stay Awake might be useful in a variety of conditions, including:
When a device is being used in a vehicle, it may be continuously receiving power from the vehicle power supply, rather than running off its own internal battery. The Display Screen timeout, configured via Timeout, which is generally used to increase battery life, may add little value in such situations.
When a device is being used for debugging, it may be connected to a PC via a USB cable and therefore might continuously receiving power from the PC, rather than running off its own internal battery. The Display Screen timeout, configured via Timeout, which is generally used to increase battery life, may interfere with the ability to test and debug applications.
Detail Information:
Key = displayStayAwake
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.2.
Signal
Select the Signal that will be used to trigger automatic Display Blanking when the value Blank When Triggered by Signal is selected for Blanking Mode to turn on Display Blanking Mode.
If the value Do not change is selected, then no change will be made to Display Blanking.
If the value Input 1 is selected, on the Zebra VC80x vehicle-mounted Android device the Clear To Send (CTS) input signal on Serial Port 1 will be used to trigger automatic Display Blanking.
If the value Input 2 is selected, on the Zebra VC80x vehicle-mounted Android device the Clear To Send (CTS) input signal on Serial Port 2 will be used to trigger automatic Display Blanking.
Note that a common configuration to support Display Blanking Mode would be to connect the Request to Send (RTS) output signal of the selected Serial Port to the Clear To Send (CTS) input signal on the same serial port, via a switch, such as one activated by the vehicle accelerator. When the switch is activated, the output RTS output signal would be fed back into the CTS input signal and detected to trigger automatic Display Blanking.
Detail Information:
Key = displayBlankingModeSignal
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Input 1 | 1 |
| Input 2 | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Polarity
Select the Polarity of the Signal that will be used to trigger automatic Display Blanking when the value Blank When Triggered by Signal is selected for Blanking Mode to turn on Display Blanking Mode.
If the value Do not change is selected, then no change will be made to Display Blanking.
If the value Blank screen when signal goes inactive (OFF) is selected, the automatic Display Blanking will occur when the specified signal is detected as going inactive (OFF). This choice would be used in specialized configurations where the signal to be used to trigger automatic Display Blanking has reverse polarity.
If the value Blank screen when signal goes active (ON) is selected, the automatic Display Blanking will occur when the specified signal is detected as going active (ON). This is the most common choice for the common configuration of connecting RTS and CTS via a switch.
Detail Information:
Key = displayBlankingModeSignalPolarity
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Blank screen when signal goes inactive (OFF) | 2 |
| Blank screen when signal goes active (ON) | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Debounce Delay
Enter the Debounce Delay that will be used for the Signal that will be used to trigger automatic Display Blanking when the value Blank When Triggered by Signal is selected for Blanking Mode to turn on Display Blanking Mode or leave blank (empty string) to leave unchanged.
The value specified should be an integer value specifying the delay in milliseconds that will be used following a change in signal state for changing the state of Display Blanking. This is useful to avoid spurious or repetitive changes in Display Blanking state as a result of bounce or chatter on the signal used to trigger automatic Display Blanking. The value specified should be in the range of 250 milliseconds (one quarter of a second) to 32767 milliseconds (more than 32 seconds), which should be adequate to handle most situations.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "displayBlankingModeSignalDebounceDelay" to "displayBlankingModeSignalDebounceDelayString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = displayBlankingModeSignalDebounceDelayString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Allowed Orientations
Select which orientations the display is permitted to rotate into when auto rotation is active.
If Do not change is selected, then no change will be made to which orientations the display is permitted to rotate into when auto rotation is active.
If All (0 90 180 270 degrees) is selected, the display is permitted to rotate into ALL orientations when auto rotation is active.
If All except portrait inverted (180 degrees) is selected, the display is permitted to rotate into ALL orientations EXCEPT inverted portrait when auto rotation is active.
Detail Information:
Key = displayAllowedOrientations
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| All (0 90 180 270 degrees) | 1 |
| All except portrait inverted (180 degrees) | 2 |
Support Information:
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Lock Override Button
Select whether the device user is allowed to use an on-screen button to override the display orientation when autorotation is turned off.
If the value Do not change is selected, then no change will be made to whether the device user is allowed to use an on-screen button to override the display orientation when autorotation is turned off.
If the value Enable is selected, the device user will be allowed to use an on-screen button to override the display orientation when autorotation is turned off.
if the value Disable is selected, the device user will NOT be allowed to use an on-screen button to override the display orientation when autorotation is turned off.
Detail Information:
Key = displayLockOverrideButton
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Enable | 1 |
| Disable | 2 |
Support Information:
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Locked Orientation Positions
Select an orientation for the display when autorotation is turned off.
If Do not change is selected, then no change will be made to the orientation of the display.
If Portrait (No rotation) is selected, the display will go into portrait orientation.
If Landscape left (90 degrees) is selected, the display will go into landscape orientation.
if Portrait inverted (180 degrees) is selected, the display will go into portrait inverted orientation.
if Landscape right (270 degrees) is selected, the display will go into landscape inverted orientation.
Detail Information:
Key = displayLockedOrientation
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Portrait (No rotation) | 0 |
| Landscape left (90 degrees) | 1 |
| Portrait inverted (180 degrees) | 2 |
| Landscape right (270 degrees) | 3 |
Support Information:
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Rotation Mode
Select whether the content presented on the device display will be automatically rotated, based on the accelerometer, to match the physical orientation of the device.
If Do not change is selected, then no change will be made to whether the content presented on the device display will be automatically rotated, based on the accelerometer, to match the physical orientation of the device.
If the value Lock to Current is selected, the content presented on the device display will remain in whatever orientation it was in at the time this setting was changed from Automatic to Lock to Current.
If the value Automatic is selected, the content presented on the device display will be automatically rotated, based on the accelerometer, to match the physical orientation of the device.
Notes:
No method is currently provided to set the orientation when a device automatic rotation is turned off. The result of turning off automatic rotation may be unpredictable if performed in conditions under which the physical orientation of the device is not known (e.g. while the device is in use). For best results, automatic rotation should be turned off when the device is in a known orientation (such as when docked or in a charging cradle).
The Lock to Current setting can be overridden by an application that's coded to do so. This can be useful if the app functions only in a particular orientation or if that orientation provides a better user experience.
Detail Information:
Key = displayRotationMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Lock to Current | 2 |
| Automatic | 1 |
Support Information:
- Supported from: MX 10.1.
Set Display Size
Select the display size that controls the size of various content elements, from one of several pre-defined display sizes.
If the value *Do not change is selected, then no change will be made to the display size.
If the value Small is selected, a small display size will be used to fit a larger amount content of a smaller size.
If the value Default is selected, a default display size will be used to fit a standard amount of content of a standard size.
If the value Large is selected, a large display size will be used to fit a smaller amount of content of a larger size.
If the value Larger is selected, an ever larger display size will be used to fit an even smaller amount of content of an even larger size.
If the value Larger is selected, a very large display size will be used to fit a very small amount of content of a very large larger size.
Detail Information:
Key = setDisplaySize
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Small | SMALL |
| Default | DEFAULT |
| Large | LARGE |
| Larger | LARGER |
| Largest | LARGEST |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Set Font Size
Select the system font size.
If the value *Do not change is selected, then no change will be made to the system font size.
If the value Small is selected, a small system font size will be used to fit a larger amount text of a smaller size.
If the value Default is selected, a default system font size will be used to fit a standard amount of text of a standard size.
If the value Large is selected, a large system font size will be used to fit a smaller amount of text of a larger size.
If the value Largest is selected, an ever larger system font size will be used to fit an even smaller amount of text of an even larger size.
Detail Information:
Key = setFontSize
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Small | 0.85 |
| Default | 1.0 |
| Large | 1.15 |
| Largest | 1.3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Backlight Adaptive Brightness
Select whether the display brightness will be set automatically based on the ambient light sensor.
If Do not change is selected, then no change will be made to whether the display brightness will be set automatically based on the ambient light sensor.
If On is selected, the display brightness will be set automatically based on the ambient light sensor.
If Off is selected, the display brightness will NOT be set automatically based on the ambient light sensor.
Detail Information:
Key = displayBacklightAdaptiveBrightness
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 10.2.
Brightness
Select the Backlight Brightness when the value Off is selected for Backlight Adaptive Brightness.
If the value Do not change is selected, then no change will be made to the Backlight Brightness.
If a value from 1 to 99 is selected, then the Backlight Brightness will be set to the specified percentage of the highest supported level.
If the value 100 is selected, then the Backlight Brightness will be set to the highest supported level.
Note that the data type of this MC has changed from integer to string, in order to add a Do not change value to better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "displayBacklightBrightness" to "displayBacklightBrightnessString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = displayBacklightBrightnessString
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 0 | 0 |
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| 4 | 4 |
| 5 | 5 |
| 6 | 6 |
| 7 | 7 |
| 8 | 8 |
| 9 | 9 |
| 10 | 10 |
| 11 | 11 |
| 12 | 12 |
| 13 | 13 |
| 14 | 14 |
| 15 | 15 |
| 16 | 16 |
| 17 | 17 |
| 18 | 18 |
| 19 | 19 |
| 20 | 20 |
| 21 | 21 |
| 22 | 22 |
| 23 | 23 |
| 24 | 24 |
| 25 | 25 |
| 26 | 26 |
| 27 | 27 |
| 28 | 28 |
| 29 | 29 |
| 30 | 30 |
| 31 | 31 |
| 32 | 32 |
| 33 | 33 |
| 34 | 34 |
| 35 | 35 |
| 36 | 36 |
| 37 | 37 |
| 38 | 38 |
| 39 | 39 |
| 40 | 40 |
| 41 | 41 |
| 42 | 42 |
| 43 | 43 |
| 44 | 44 |
| 45 | 45 |
| 46 | 46 |
| 47 | 47 |
| 48 | 48 |
| 49 | 49 |
| 50 | 50 |
| 51 | 51 |
| 52 | 52 |
| 53 | 53 |
| 54 | 54 |
| 55 | 55 |
| 56 | 56 |
| 57 | 57 |
| 58 | 58 |
| 59 | 59 |
| 60 | 60 |
| 61 | 61 |
| 62 | 62 |
| 63 | 63 |
| 64 | 64 |
| 65 | 65 |
| 66 | 66 |
| 67 | 67 |
| 68 | 68 |
| 69 | 69 |
| 70 | 70 |
| 71 | 71 |
| 72 | 72 |
| 73 | 73 |
| 74 | 74 |
| 75 | 75 |
| 76 | 76 |
| 77 | 77 |
| 78 | 78 |
| 79 | 79 |
| 80 | 80 |
| 81 | 81 |
| 82 | 82 |
| 83 | 83 |
| 84 | 84 |
| 85 | 85 |
| 86 | 86 |
| 87 | 87 |
| 88 | 88 |
| 89 | 89 |
| 90 | 90 |
| 91 | 91 |
| 92 | 92 |
| 93 | 93 |
| 94 | 94 |
| 95 | 95 |
| 96 | 96 |
| 97 | 97 |
| 98 | 98 |
| 99 | 99 |
| 100 | 100 |
Support Information:
- Supported from: MX 10.2.
Enterprise Keyboard Configuration
Use this Sub-group to configure Auto Capitalization, Auto Correction, Block Offensive Words, Double Space Period, Flick for Alternate Chars, Key Long Press Delay, Language Action, Language, Custom, Navigation Mode, Numeric Layout Mode, Show Alphanumeric Tab, Show Numeric Tab, Show Scan Tab, Show Symbol Tab, Show Voice Input Key, Show Voice Tab, System Language Support, Preferred Tab, Suggest Contact Names, Suggest Misspelling Corrections, Popup on Keypress, Sound on Keypress, Mode, Volume, Vibrate on Keypress, Mode, Custom Keyboard Height, Custom Keyboard Width, Keyboard Height, Keyboard Width, Duration, Remap Alpha P1, Remap Numeric P1, Remap Numeric P2, Remap Numeric P3, Remap Numeric P4, and Remap Symbol P1.
Detail Information:
Key = ekbStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Auto Capitalization
Select whether the Enterprise Keyboard on a device will have automatic capitalization turned on (enabled) or turned off (disabled) for the first letter of each sentence.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will have automatic capitalization turned on (enabled) or turned off (disabled) for the first letter of each sentence.
If the value Off is selected, automatic capitalization will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, automatic capitalization will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbAutoCaps
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Auto Correction
Select whether the Enterprise Keyboard on a device will have automatic correction of misspelled words turned on (enabled) or turned off (disabled), wherein the space and punctuation keys initiate automatic correction of misspelled words.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will have automatic correction of misspelled words turned on (enabled) or turned off (disabled), wherein the space and punctuation keys initiate automatic correction of misspelled words.
If the value Off is selected, automatic correction of misspelled words will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, automatic correction of misspelled words will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbAutoCorrection
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Block Offensive Words
Select whether the Enterprise Keyboard on a device will have automatic blocking of offensive words turned on (enabled) or turned off (disabled).
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will have automatic blocking of offensive words turned on (enabled) or turned off (disabled).
If the value Off is selected, automatic offensive word blocking will be turned off (disabled).
If the value On is selected, automatic offensive word blocking will be turned on (enabled).
Detail Information:
Key = ekbBlockOffensiveWords
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Double Space Period
Select whether the Enterprise Keyboard on a device will have automatic sentence ending turned on (enabled) or turned off (disabled) wherein a double tap on the space key causes the entry of a period followed by two spaces.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will have automatic sentence ending turned on (enabled) or turned off (disabled) wherein a double tap on the space key causes the entry of a period followed by two spaces.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbDoubleSpacePeriod
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Flick for Alternate Chars
Select whether the Enterprise Keyboard on a device will show alternate characters when a flick gesture is performed.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show alternate characters when a flick gesture is performed.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbFlickForAlternateChars
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.1.
Key Long Press Delay
Enter the length of time a key within the Enterprise Keyboard must be held pressed to be considered a long press or leave blank (empty string) to leave unchanged.
The value entered should be a string containing an integer value from 100 to 700 indicating the number of milliseconds a key must be held to be considered a long press.
Note that the data type of this MC has changed from integer to string, in order to add a "Do not change" option and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "displayBlankingModeSignalDebounceDelay" to "displayBlankingModeSignalDebounceDelayString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to enter a suitable value, as described above, for the key with the new name.
Detail Information:
Key = ekbKeyLongPressDelayString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Language Action
Select the Action to perform to configure use of a non-System language.
If the value Do not change is selected, the no Action will be perform to configure use of a non-System language.
If the value Enable is selected, a non-System language will be configured to be used and Language must be specified to select that language.
If the value Enable is selected, a non-System language will be configured to not be used and Language must be specified to select that language.
Detail Information:
Key = ekbLanguageAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Enable | 1 |
| Disable | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Language
Select a non-System language for which use should be configured when the value Enable or Disable is specified for Language Action.
If the value Do not change is selected, then no change will be made to the usage of any non-System language.
If the value English_US is selected, then usage of English as spoken in the USA will be configured.
If the value English_UK is selected, then usage of English as spoken in the UK will be configured.
If the value Polish is selected, then usage of Polish will be configured.
If the value Slovak is selected, then usage of Slovak will be configured.
If the value Romanian is selected, then usage of Romanian will be configured.
If the value Czech is selected, then usage of Czech will be configured.
If the value Russian is selected, then usage of Russian will be configured.
If the value ALL is selected, then usage of All non-System Languages will be configured.
If the value CUSTOM is selected, then usage of a specified non-System Language will be configured. and you must also specify Custom to identify that language.
Detail Information:
Key = ekbLanguageActionLanguage
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| English_US | English_US |
| English_UK | English_UK |
| Polish | Polish |
| Slovak | Slovak |
| Romanian | Romanian |
| Czech | Czech |
| Russian | Russian |
| ALL | ALL |
| CUSTOM | CUSTOM |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Custom
Enter the custom name of the non-System language for which usage will be configured when the value Enable or Disable is specified for Language Action and when the value CUSTOM is specified for Language.
Detail Information:
Key = ekbLanguageActionLanguageCustom
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Navigation Mode
Select the navigation mode the Enterprise Keyboard on a device will use to provide its user experience.
If the value Do not change is selected, then no change will be made to the navigation mode the Enterprise Keyboard on a device will use to provide its user experience.
If the value Tab-based (new) is selected, the Enterprise Keyboard will use the new user experience wherein different tabs can be used to select the desired keyboard.
If the value Key-based (legacy) is selected, the Enterprise Keyboard will use the legacy user experience wherein keys can be used to select the desired keyboard.
Detail Information:
Key = ekbNavigationMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Tab-based (new) | 1 |
| Key-based (legacy) | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Numeric Layout Mode
Select the numeric layout mode the Enterprise Keyboard on a device will use when it determines that a numeric keyboard should be displayed.
If the value Do not change is selected, then no change will be made to the numeric layout mode the Enterprise Keyboard on a device will use when it determines that a numeric keyboard should be displayed.
If the value Telephone Mode is selected, the Enterprise Keyboard will display a numeric keyboard in telephone mode (e.g. 123, 456, 789).
If the value Calculator Mode is selected, the Enterprise Keyboard will display a numeric keyboard in calculator mode (e.g. 789, 456, 123).
Detail Information:
Key = ekbNumericLayoutMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Telephone Mode | 1 |
| Calculator Mode | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.1.
Show Alphanumeric Tab
Select whether the Enterprise Keyboard on a device will show the alphanumeric tab to allow selection of the alphanumeric keyboard.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show the alphanumeric tab to allow selection of the alphanumeric keyboard.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowAlphaNumericTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Show Numeric Tab
Select whether the Enterprise Keyboard on a device will show the numeric tab to allow selection of the numeric keyboard.
If the value *Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show the numeric tab to allow selection of the numeric keyboard.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowNumericTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Show Scan Tab
Select whether the Enterprise Keyboard on a device will show the scan tab to allow control of barcode scanning.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show the scan tab to allow control of barcode scanning.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowScanTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Show Symbol Tab
Select whether the Enterprise Keyboard on a device will show the symbol tab to allow selection of the symbol keyboard.
If the value *Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show the symbol tab to allow selection of the symbol keyboard.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowSymbolTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Show Voice Input Key
Select whether the Enterprise Keyboard on a device will show a key to invoke voice input (if supported).
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show a key to invoke voice input (if supported).
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowVoiceInputKey
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Show Voice Tab
Select whether the Enterprise Keyboard on a device will show the symbol tab to allow selection of the special symbols keyboard.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will show the microphone tab to allow voice input.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowVoiceTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
System Language Support
Select whether to use the standard Android Languages or the built-in Enterprise Keyboard languages.
If the value Do not change is selected, then no change will be made to whether to use the standard Android Languages or the built-in Enterprise Keyboard languages.
If the value Enterprise Keyboard is selected, the standard Android Languages will be used.
If the value Android System is selected, the built-in Enterprise Keyboard languages.
Detail Information:
Key = ekbUseSystemLanguages
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Android System | 1 |
| Enterprise Keyboard | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Preferred Tab
Select the preferred tab the Enterprise Keyboard on a device will select by default when textual data is being entered.
If the value Do not change is selected, then no change will be made to the preferred tab the Enterprise Keyboard on a device will select by default when textual data is being entered.
If the value Numeric is selected, the Enterprise Keyboard will select the Numeric tab by default when textual data is being entered.
If the value Alphanumeric is selected, the Enterprise Keyboard will show the Alphanumeric tab by default when textual data is being entered.
If the value Symbol is selected, the Enterprise Keyboard will show the Symbol tab by default when textual data is being entered.
If the value Scan is selected, the Enterprise Keyboard will show the Scan tab by default when textual data is being entered.
If the value Voice is selected, the Enterprise Keyboard will show the Voice tab by default when textual data is being entered.
Detail Information:
Key = ekbSelectPreferredTab
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Numeric | 1 |
| Alphanumeric | 2 |
| Symbol | 3 |
| Scan | 4 |
| Voice | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Suggest Contact Names
Select whether the Enterprise Keyboard on a device showing contact name suggestions while typing based on past actions will be turned on (enabled) or turned off (disabled).
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device showing contact name suggestions while typing based on past actions will be turned on (enabled) or turned off (disabled).
If the value Off is selected, contact name suggestions will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, contact name suggestions will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowContactNamesSuggestions
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Suggest Misspelling Corrections
Select whether the Enterprise Keyboard on a device showing suggestions for corrections of misspelled words while typing will be turned on (enabled) or turned off (disabled).
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device showing suggestions for corrections of misspelled words while typing will be turned on (enabled) or turned off (disabled).
If the value Off is selected, correction suggestions will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, correction suggestions will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbShowCorrectionSuggestions
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Popup on Keypress
Select whether the Enterprise Keyboard on a device will have key popup on each keypress turned on (enabled) or turned off (disabled) wherein a visible indication that the key was pressed occurs.
If the value Do not change is selected, then no change will be made to whether the Enterprise Keyboard on a device will have key popup on each keypress turned on (enabled) or turned off (disabled) wherein a visible indication that the key was pressed occurs.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard.
Detail Information:
Key = ekbPopupOnKeypress
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Sound on Keypress
Select whether a sound will be produced on each keypress using the Enterprise Keyboard.
If the value Do not change is selected, no change will be made to whether a sound will NOT be produced on each keypress using the Enterprise Keyboard.
If the value Off is selected, a sound will NOT be produced on each keypress using the Enterprise Keyboard.
If the value On is selected, a sound will be produced on each keypress using the Enterprise Keyboard.
Detail Information:
Key = ekbSoundOnKeypress
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Mode
Select the volume mode that will be used by the Enterprise Keyboard on a device when sound occurs on each keypress.
If the value Do not change is selected, then no change will be made to the volume mode that will be used by the Enterprise Keyboard on a device when sound occurs on each keypress.
If the value System Default Volume is selected, the System Default Volume for keypress sounds will be used.
If the value Specified Volume is selected, a specified volume will be used and you must also specify Volume to provide that volume.
Detail Information:
Key = ekbSoundOnKeypressVolumeMode
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Volume
Enter the volume (from 0 to 100) that will be used by the Enterprise Keyboard on a device when sound occurs on each keypress, when the value On is selected for Sound on Keypress and the value Specified Volume is selected for Mode or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "ekbSoundOnKeypressVolume" to "ekbSoundOnKeypressVolumeString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = ekbSoundOnKeypressVolumeString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Vibrate on Keypress
Select whether the Enterprise Keyboard on a device will have vibration on each keypress turned on (enabled) or turned off (disabled) wherein a tactile indication that the key was pressed occurs.
If the value Do not change is selected, no change will be made to whether the Enterprise Keyboard on a device will have vibration on each keypress turned on (enabled) or turned off (disabled) wherein a tactile indication that the key was pressed occurs.
If the value Off is selected, this feature will be turned off (disabled), and hence it will not be available for use in entering data using the Enterprise Keyboard.
If the value On is selected, this feature will be turned on (enabled), and hence it will be available for use in entering data using the Enterprise Keyboard. You must also specify Mode to provide the mode used to determine the duration of the vibration.
Detail Information:
Key = ekbVibrateOnKeypress
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Mode
Select the duration mode that will be used by the Enterprise Keyboard on a device when vibrate occurs on each keypress.
If the value Do not change is selected, then no change will be made to the duration mode that will be used by the Enterprise Keyboard on a device when vibrate occurs on each keypress.
If the value System Default Duration is selected, the System Default Duration for keypress vibrate will be used.
If the value Specified Duration is selected, a specified duration will be used and you must also specify Duration to provide that duration.
Detail Information:
Key = ekbVibrateOnKeypressDurationMode
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Custom Keyboard Height
Enter a custom height for the soft keyboard as a percentage (from 25-100) to REDUCE its height when displayed on an external monitor.
Detail Information:
Key = ekbKeyboardCustomHeight
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Custom Keyboard Width
Enter a custom width for the soft keyboard as a percentage (from 25-100) to REDUCE its width when displayed on an external monitor.
Detail Information:
Key = ekbKeyboardCustomWidth
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Keyboard Height
Select the keyboard height to use. If System default is selected, the system default height will be used. To specify a height, a value in Custom Keyboard Height is required.
Detail Information:
Key = ekbKeyboardHeight
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Specify height | |
| System default | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Keyboard Width
Select the keyboard width to use. If System default is selected, the system default width will be used. To specify a width, a value in Custom Keyboard Width is required.
Detail Information:
Key = ekbKeyboardWidth
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Specify width | |
| System default | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Duration
Enter the duration (from 0 to 100 milliseconds) that will be used by the Enterprise Keyboard on a device when a vibrate occurs on each keypress, when the value Specified Duration is selected for Vibrate on Keypress and the value System Default Duration is selected for Mode or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "ekbVibrateOnKeypressDuration" to "ekbVibrateOnKeypressDurationString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = ekbVibrateOnKeypressDurationString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Alpha P1
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Alpha P1 Key (located on the Alpha keyboard at Row 1, Column 1) is pressed or leave blank (empty string) to leave unchanged..
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapAlphaP1
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Numeric P1
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Numeric P1 Key (located on the Numeric keyboard at Row 1, Column 1) is pressed or leave blank (empty string) to leave unchanged.
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapNumericP1
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Numeric P2
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Numeric P2 Key (located on the Numeric keyboard at Row 2, Column 1) is pressed or leave blank (empty string) to leave unchanged..
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key or leave blank (empty string) to leave unchanged.. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapNumericP2
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Numeric P3
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Numeric P3 Key (located on the Numeric keyboard at Row 3, Column 1) is pressed or leave blank (empty string) to leave unchanged.
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapNumericP3
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Numeric P4
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Numeric P4 Key (located on the Numeric keyboard at Row 4, Column 1) is pressed or leave blank (empty string) to leave unchanged..
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapNumericP4
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Remap Symbol P1
Enter a value that defines the behavior the Enterprise Keyboard on a device will perform when the Symbol P1 Key (located on the Symbol keyboard at Row 4, Column 1) is pressed or leave blank (empty string) to leave unchanged..
Possible values can be:
A single character value (e.g. the letter "A" or the symbol "@") causes that character value to be sent as the behavior for the remapped key.
A hexadecimal value in the format \uXXXXXX (e.g. \u000001) causes the specified key code to be sent as the behavior for the remapped key. Allowable values can be determined from the Android documentation: https://developer.android.com/reference/android/view/KeyEvent.
The value \EMOJI causes the remapped key to switch to the EMOJI keyboard.
Detail Information:
Key = ekbRemapSymbolP1
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Enterprise NFC Configuration
Use this Sub-group to configure Reset to Defaults, Logging, Type A Tags, Type B Tags, Type F Tags, Type V Tags, Use NFC Data Exchange Format (NDEF), Polling Mode, CPU Boost, Type A Tag Baud Rate, Type B Tag Baud Rate, Peer to Peer Mode, Card Emulation Mode, Power, and Use on Lock Screen.
Detail Information:
Key = nfcStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Reset to Defaults
Select whether the Enterprise NFC settings should all be reset to their default values.
Detail Information:
Key = nfcResetToDefaults
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Reset to Defaults | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Logging
Select whether logging should be used by Enterprise NFC.
If the value Do not change is selected, the no change will be made to whether logging should be used by Enterprise NFC.
If the value Off is selected, Enterprise NFC will NOT capture logs.
If the value On is selected, Enterprise NFC will capture logs.
Detail Information:
Key = nfcDebugLogging
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | false |
| On | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.3.
Type A Tags
Select whether the Enterprise NFC should read NFC Type A Tags.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should read NFC Type A Tags.
If the value Do Not Read is selected, Enterprise NFC will NOT attempt to read NFC Type A Tags. This could increase the speed of reading other tag types in cases where Type A Tags are not used.
If the value Read is selected, Enterprise NFC will attempt to read NFC Type A Tags. This might decrease the speed of reading tags unless reading of other tag types is turned off.
Detail Information:
Key = nfcReadTypeATags
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Read | false |
| Read | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Type B Tags
Select whether the Enterprise NFC should read NFC Type B Tags.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should read NFC Type B Tags.
If the value Do Not Read is selected, Enterprise NFC will NOT attempt to read NFC Type B Tags. This could increase the speed of reading other tag types in cases where Type B Tags are not used.
If the value Read is selected, Enterprise NFC will attempt to read NFC Type B Tags. This might decrease the speed of reading tags unless reading of other tag types is turned off.
Detail Information:
Key = nfcReadTypeBTags
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Read | false |
| Read | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Type F Tags
Select whether the Enterprise NFC should read NFC Type F Tags.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should read NFC Type F Tags.
If the value Do Not Read is selected, Enterprise NFC will NOT attempt to read NFC Type F Tags. This could increase the speed of reading other tag types in cases where Type F Tags are not used.
If the value Read is selected, Enterprise NFC will attempt to read NFC Type F Tags. This might decrease the speed of reading tags unless reading of other tag types is turned off.
Detail Information:
Key = nfcReadTypeFTags
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Read | false |
| Read | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Type V Tags
Select whether the Enterprise NFC should read NFC Type V Tags.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should read NFC Type V Tags.
If the value Do Not Read is selected, Enterprise NFC will NOT attempt to read NFC Type V Tags. This could increase the speed of reading other tag types in cases where Type V Tags are not used.
If the value Read is selected, Enterprise NFC will attempt to read NFC Type V Tags. This might decrease the speed of reading tags unless reading of other tag types is turned off.
Detail Information:
Key = nfcReadTypeVTags
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Read | false |
| Read | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Use NFC Data Exchange Format (NDEF)
Select whether the Enterprise NFC should use NFC Data Exchange Format (NDEF).
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should use NFC Data Exchange Format (NDEF).
If the value Do Not Use is selected, Enterprise NFC will NOT attempt tp read NDEF formatted tags. This could increase the speed of reading non-NDEF tags by not spending unnecessary time trying to interpret tag data according to NDEF formatting rules.
If the value Use is selected, Enterprise NFC will attempt to read NDEF formatted tags. This may decrease speed somewhat, compared to reading unformatted tags, but increases flexibility by allowing applications to receive tag data interpreted according to NDEF formatting rules. Starting in Android 11, support for NFC Data Exchange Format (NDEF) is deprecated.
Detail Information:
Key = nfcUseNDEF
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Use | false |
| Use | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Polling Mode
Select the Enterprise NFC Polling Mode that should be used.
If the value Do not change is selected, then no change will be made to the Enterprise NFC Polling Mode that should be used.
If the value Hybrid is selected, Enterprise NFC will poll in a manner designed to strike a reasonable balance between polling speed and battery life.
If the value Standard is selected, then Enterprise NFC will poll in a manner designed to maximize polling speed. This may increase battery drain but will reduce tag detection time.
If the value Low Power is selected, Enterprise NFC will poll in a manner designed to minimize impact on battery life. This may increase the overall tag detection time, but will reduce battery drain.
Detail Information:
Key = nfcPollingMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hybrid | 2 |
| Standard | 1 |
| Low Power | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
CPU Boost
Select whether the Enterprise NFC should Boost CPU Speed during NFC transactions.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should Boost CPU Speed during NFC transactions.
If the value Do Not Boost is selected, Enterprise NFC will leave the CPU Speed unmodified during NFC transactions.
If the value Boost is selected, Enterprise NFC will Boost the CPU Speed during NFC transactions to enhance performance of those transactions.
Detail Information:
Key = nfcCpuBoost
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Boost | false |
| Boost | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Type A Tag Baud Rate
Select the Baud Rate that Enterprise NFC should use for Type A Tags.
If the value Do not change is selected, then no change will be made to the Baud Rate that Enterprise NFC should use for Type A Tags.
If the value 106 kbps is selected, Enterprise NFC will always communicate to Type A Tags using a Baud Rate of 106 kbps.
If the value 212 kbps is selected, Enterprise NFC will communicate to Type A Tags using a Baud Rate of 106 kbps or 212 kbps, depending on the Baud Rate supported by the tag.
If the value 424 kbps is selected, Enterprise NFC will communicate to Type A Tags using a Baud Rate of 106 kbps, 212 kbps, or 424 kbps, depending on the Baud Rate supported by the tag.
If the value Any is selected, Enterprise NFC will communicate to Type A Tags using any available (automatically selected) Baud Rate supported by the tag.
Detail Information:
Key = nfcTypeABaudRate
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 106 kbps | 1 |
| 212 kbps | 16 |
| 424 kbps | 32 |
| Any | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Type B Tag Baud Rate
Select the Baud Rate that Enterprise NFC should use for Type B Tags.
If the value Do not change is selected, then no change will be made to the Baud Rate that Enterprise NFC should use for Type B Tags.
If the value 106 kbps is selected, Enterprise NFC will always communicate to Type B Tags using a Baud Rate of 106 kbps.
If the value 212 kbps is selected, Enterprise NFC will communicate to Type B Tags using a Baud Rate of 106 kbps or 212 kbps, depending on the Baud Rate supported by the tag.
If the value 424 kbps is selected, Enterprise NFC will communicate to Type B Tags using a Baud Rate of 106 kbps, 212 kbps, or 424 kbps, depending on the Baud Rate supported by the tag.
If the value Any is selected, Enterprise NFC will communicate to Type B Tags using any available (automatically selected) Baud Rate supported by the tag.
Detail Information:
Key = nfcTypeBBaudRate
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| 106 kbps | 4 |
| 212 kbps | 64 |
| 424 kbps | 128 |
| Any | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Peer to Peer Mode
Select whether the Enterprise NFC should use Peer to Peer Mode. This is generally used when two NFC enabled devices want to communicate with each other to exchange data.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should use Peer to Peer Mode.
If the value Do Not Use is selected, Enterprise NFC will NOT use Peer-to-Peer Mode and hence will operate only in Read/Write Mode, unless it is also configured to operated in Card Emulation Mode by via Card Emulation Mode.
If the value Use is selected, Enterprise NFC will use Peer-to-Peer Mode and hence will operate in both Peer-to-Peer Mode and Read/Write Mode, and and optionally also in Card Emulation Mode, if configured via Card Emulation Mode. Starting in Android 11, support for Peer-to-Peer Mode is deprecated.
Detail Information:
Key = nfcPeerToPeerMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Use | false |
| Use | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Card Emulation Mode
Select whether the Enterprise NFC should use Card Emulation Mode.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should use Card Emulation Mode.
If the value Do Not Use is selected, Enterprise NFC will NOT use Card Emulation Mode and hence will operate only in Read/Write Mode, unless it is also configured to operated in Peer-to-Peer Mode by via Peer to Peer Mode.
If the value Use is selected, Enterprise NFC will use Card Emulation Mode and hence will operate in both Card Emulation Mode and Read/Write Mode and optionally also in Peer-to-Peer Mode, if configured via Peer to Peer Mode.
Detail Information:
Key = nfcCardEmulationMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Do Not Use | false |
| Use | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Power
Select whether the Enterprise NFC should be turned on or turned off.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should be turned on or turned off.
If the value Turn Off is selected, Enterprise NFC will be turned off.
If the value Turn On is selected, Enterprise NFC will be turned on.
Detail Information:
Key = nfcPower
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn On | 1 |
| Turn Off | 2 |
Support Information:
- NOT supported on Device(s): TC20 and TC25.
Use on Lock Screen
Select whether the Enterprise NFC should be allowed to be used from the Lock Screen.
If the value Do not change is selected, then no change will be made to whether the Enterprise NFC should be allowed to be used from the Lock Screen.
If the value Disallow is selected, Enterprise NFC will NOT allow NFC operations to be performed when the device is at the lock screen.
If the value Allow is selected, Enterprise NFC will allow NFC operations to be performed when the device is at the lock screen.
Detail Information:
Key = nfcUseOnLockScreen
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | false |
| Allow | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Ethernet Configuration
Use this Sub-group to configure Power, Control by User, Use Proxy Server, Proxy Server, Port, Bypass List, IP Address Type, IP Address, Gateway Address, Network Mask, Primary DNS, and Secondary DNS.
Detail Information:
Key = ethernetStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Power
Select the Power State of the Ethernet Adapter.
If the value Do not change is selected, then no change will be made to the Power State of the Ethernet Adapter.
If the value Off is selected, then the Power State of the Ethernet Adapter will be turned off.
If the value On is selected, then the Power State of the Ethernet Adapter will be turned on.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetPower
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Control by User
Select whether Ethernet Power control by the device user will be allowed or not.
If the value Do not change is selected, then no change will be made to whether Ethernet Power control by the device user will be allowed or not.
If the value Off is selected, the device user will NOT be allowed to control Ethernet Power.
If the value On is selected, the device user will be allowed to control Ethernet Power.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetPowerControlByUser
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Use Proxy Server
Select whether a Proxy Server should be used to access the Internet from the network accessed via the Ethernet Adapter.
If the value Do not change is selected, then no change will be made to whether a Proxy Server should be used to access the Internet from the network accessed via the Ethernet Adapter.
If the value Use a Proxy Server is selected, a Proxy Server will be used to access the Internet from the network accessed via the Ethernet Adapter. You must also specify Proxy Server, Port, and Bypass List to define the Proxy Server and any addresses that should bypass it.
If the value Do NOT Use a Proxy Server is selected, a Proxy Server will NOT be used to access the Internet from the network accessed via the Ethernet Adapter.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetUseProxyServer
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Proxy Server
Enter the Proxy Server used to access the Internet from the network accessed via the Ethernet Adapter. You must also specify Portand Bypass List to define the Proxy Server and any addresses that should bypass it.
A given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetProxyServer
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Port
Enter the Port that will be used to reach the Proxy Server to access the Internet from the network accessed via the Ethernet Adapter when Use a Proxy Server is specified for Use Proxy Server and when Proxy Server and Bypass List are specified or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "ethernetProxyServerPort" to "ethernetProxyServerPortString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetProxyServerPortString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Bypass List
Enter the Proxy Server Bypass List which specifies addresses that should bypass the Proxy Server used to access the Internet from the network accessed via the Ethernet Adapter when Use a Proxy Server is specified for Use Proxy Server and when Proxy Server and Port are specified.
A given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetProxyServerBypassList
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
IP Address Type
Select how an IP Address will be assigned to the Ethernet adapter.
If the value Do not change is selected, no change will be made to how an IP Address will be assigned to the Ethernet adapter.
If the value Dynamic (DHCP) is selected, an IP Address for the Ethernet adapter will be automatically acquired by the DHCP Client from the DHCP Server and you should NOT specify IP Address, Gateway Address, Network Mask, Primary DNS, or Secondary DNS.
If the value Static (Manual) is selected, an IP Address for the Ethernet adapter will be assigned based on the value specified via IP Address. You must also specify Gateway Address, Network Mask, and Primary DNS. You may also optionally specify Secondary DNS.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetIpAddrType
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
IP Address
Enter the IP Address to be statically assigned to the Ethernet adapter when Dynamic (DHCP) is specified for IP Address Type. You must also specify Gateway Address, Network Mask, and Primary DNS. You may also optionally specify Secondary DNS.
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetIpAddress
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Gateway Address
Enter the Gateway Address to be assigned to the Ethernet adapter.
A given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetGatewayAddress
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Network Mask
Enter the Network Mask to be assigned to the Ethernet adapter.
A given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetNetMask
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Primary DNS
Enter the Primary DNS Server Address to be assigned to the Ethernet adapter.
A given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetDNS1
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Secondary DNS
Enter the Secondary DNS Server Address to be assigned to the Ethernet adapter when Dynamic (DHCP) is specified for IP Address Type and when IP Address, Gateway Address, Network Mask, and Primary DNS are specified
Note that a given device may or may not support an Ethernet Adapter. An attempt to configure the Ethernet Adapter on a device that does not have one will result in an error.
Detail Information:
Key = ethernetDNS2
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
File Management
Use this Sub-group to configure Download Destination Path and File Name, Download File Source URI, Delete Path and File Name, Upload Source Path and File Name, Upload File Destination URI, Upload File Target File Name Pattern, Upload Order, Upload Duplicate Handling, Upload Delete Source After Upload, and Deploy File For Application.
Detail Information:
Key = filesStep
Type = bundle
Support Information:
- Supported from: MX 5.0.
Download Destination Path and File Name
Enter the Destination Path and File Name of a file to be downloaded from a Server to the Device File System.
If specified, the following must also be specified:
- Download File Source URI must be specified to identify the location from which the file will be downloaded from a Server. This is mandatory because the file can only be downloaded from a Server and hence no file will be downloaded if this is not specified.
Detail Information:
Key = fileDownloadDestPathAndFileName
Type = string
Support Information:
- Supported from: MX 5.0.
Download File Source URI
Enter the Source URI of a location from which the file will be downloaded from a Server to the Device File System when specified via Download Destination Path and File Name.
This is mandatory when Download Destination Path and File Name is specified to identify the file on a Server to be downloaded and hence no file will be downloaded if this is not specified.
Detail Information:
Key = filesDownloadSourceURI
Type = string
Support Information:
- Supported from: MX 5.0.
Delete Path and File Name
Enter the Path and optionally the File Name of a Folder or File to be Deleted from the Device File System or leave blank (empty string) to do nothing.
To Delete a Folder, specify a value that ends in a forward slash (/) character and that specifies the full Path in the Device File System to the Folder to be Deleted.
To Delete a File, specify a value that ends with the File Name and Extension and that specifies the full Path in the Device File System to the File to be Deleted.
Detail Information:
Key = fileDeletePathAndFileName
Type = string
Support Information:
- Supported from: MX 5.0.
Upload Source Path and File Name
Enter the Source Path and File Name (which may include wildcard characters), which identifies one or more Files to be Uploaded to a Server from the Device File System.
If specified, the following must also be specified:
Upload File Destination URI must be specified to identify the location, but not the file name, to which files will be uploaded on a Server. This is mandatory because files will only be uploaded to location on a Server and hence no files will be uploaded if this is not specified.
Upload File Target File Name Pattern must be specified to identify the pattern that will be used to create the files name of each file that is uploaded to the location specified by Upload File Destination URI on a Server. This is mandatory because no files can be uploaded to a Server unless they can be assigned names and hence no files will be uploaded if this is not specified
Upload Order must be specified to define the order in which multiple files identified by Upload Source Path and File Name will uploaded to a Server. This is mandatory because multiple files might be identified and no files can be uploaded unless the order in which they should be uploaded is known and hence no files will be uploaded if this is not specified.
Upload Duplicate Handling must be specified to define what will happen if a file to be uploaded to a Server, as determined by the pattern specified in Upload File Target File Name Pattern, already exists on the Server in the location specified by Upload File Destination URI. This is mandatory because no file can be uploaded unless it is known what to do if the file collides with an existing file on the Server and hence no files will be uploaded if this is not specified.
Upload Delete Source After Upload must be specified to define what will happen to a file after it is uploaded to a Server. This is mandatory because no file can be uploaded unless it is known what to do with it after it is uploaded and hence no files will be uploaded if this is not specified.
Detail Information:
Key = filesUploadSourcePathAndFileName
Type = string
Support Information:
- Supported from: MX 10.1.
Upload File Destination URI
Enter the location, but not the file name, to which files will be uploaded to a Server when Upload Source Path and File Name is specified.
This is mandatory when Upload Source Path and File Name is specified because files will only be uploaded to location on a Server and hence no files will be uploaded if this is not specified.
Detail Information:
Key = filesUploadDestinationURI
Type = string
Support Information:
- Supported from: MX 10.1.
Upload File Target File Name Pattern
Enter a Pattern that will be used to create the files name of each file that is uploaded to the location on a Server specified by Upload File Destination URI when Upload Source Path and File Name is specified.
This is mandatory because no files can be uploaded to a Server unless they can be assigned names and hence no files will be uploaded if this is not specified
The Pattern may contain any characters that are valid for use in a File Name on a Server, which may vary by Server but will generally include letters, digits, and a decimal point (dot) and may also contain one or more of the following:
If the constant value %model% appears in the Pattern, then it will be replaced with the model name of the device.
If the constant value %serial% appears in the Pattern, then it will be replaced with the serial number of the device.
If the constant value %date% appears in the Pattern, then it will be replaced with the date the File was created in the Device File System.
If the constant value %time% appears in the Pattern, then it will be replaced with the time the File was created in the Device File System.
For example, if the Pattern was "Log-%model%-%serial%-%date%-%time%.zip", a File that is Uploaded to the Server might be assigned the File Name "Log-TC51-123456789-041520-112300.zip", indicating that the File was a Log File that was created on a TC51 device whose serial number was "123456789" and where the file was created on the device at 11:23 AM on April 15, 2020.
Detail Information:
Key = filesUploadTargetFileNamePattern
Type = string
Support Information:
- Supported from: MX 10.1.
Upload Order
Select the order in which multiple matching files will be uploaded to a Server when Upload Source Path and File Name is specified.
If the value Do nothing is selected, then no files will be uploaded.
If the value Newest files first is selected, then the file with the newest creation date and time in the Device File System will be uploaded first, followed by the next newest, and so on. This may be useful if the most recent file is deemed to be most relevant or useful and should be uploaded first, with older files uploaded later as time permits.
If the value Oldest files first is selected, then the file with the oldest creation date and time in the Device File System will be uploaded first, followed by the next oldest, and so on. This may be useful if the oldest files are least useful on the device and should be uploaded to the Server (and then potentially deleted from the device) to make room for newer files that may be more relevant and useful to keep on the device.
If the value Sorted by filename is selected, then the file with the lowest alphabetically sorted File Name in the Device File System will be uploaded first, followed by the next lowest, and so on. This may be useful if age of files is not particularly relevant to the usefulness of the files on the Server or on the device.
Note that for for best results when uploading multiple files, the value Yes should be specified for Upload Delete Source After Upload. By causing files to be deleted from the Device File System as they are successfully uploaded to the Server, errors can be smoothly handled. For example, if a communications failure occurs during the upload of a file, the upload will terminate before sending all files. A subsequent upload can then pick up with the first file in the specified order, and upload of the file for which the prior upload failed will be re-attempted when it is reached according to the defined order. Once a file is successfully uploaded, it can be deleted, thus preventing it from being uploaded again later.
Detail Information:
Key = filesUploadUploadOrder
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Newest files first | 1 |
| Oldest files first | 2 |
| Sorted by filename | 3 |
Support Information:
- Supported from: MX 10.1.
Upload Duplicate Handling
Select how to handle the situation where an attempt is made to Upload a File to a Server when Upload File Destination URI is specified and a file of the same name already exists on the Server.
If the value Do nothing is selected, then the no files will be uploaded.
If the value Replace the file in the destination is selected, then any file to be uploaded from the Device File System to the Server will replace any existing file of the same name that exists in the location specified by Upload File Destination URI. This can be used to attempt re-upload a file for which an upload has previously failed and for which a partial file might have been created on the Server that should be replaced by the file through the re-upload.
If the value Skip the file and remove from the source is selected, then any file to be uploaded from the Device File System to the Server will NOT be uploaded if an existing file of the same name already exists in the location specified by Upload File Destination URI and the file will be deleted from the Device File System. This can be used to clean up files that have previously been uploaded to the Server and that were not deleted at that time but which are no longer needed in the device.
If the value Skip the file and keep it at the source is selected, then any file to be uploaded from the Device File System to the Server will NOT be uploaded if an existing file of the same name already exists in the location specified by Upload File Destination URI and the file will be left in the Device File System. This can be used to prevent re-uploading of files that have previously been uploaded to the Server, and hence which do not need to be re-uploaded, but that are still needed in in the device and hence cannot be deleted.
Detail Information:
Key = filesUploadIfDuplicate
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Replace the file in the destination | 1 |
| Skip the file and remove from the source | 2 |
| Skip the file and keep it at the source | 3 |
Support Information:
- Supported from: MX 10.1.
Upload Delete Source After Upload
Select will happen to a file after it is uploaded to a Server.
If the value Do nothing is selected, then no file will be uploaded.
If the value No is selected, then files will NOT be automatically deleted from the Device File System after they have been successfully uploaded to the Server. This would be used if the file is still relevant to keep in the device after it has been uploaded to a Server.
If the value Yes is selected, then files will be automatically deleted from the Device File System after they have been successfully uploaded to the Server. This would be used if the file is no longer relevant to keep in the device after it has been uploaded to a Server.
Detail Information:
Key = filesUploadDeleteAfterUpload
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| No | 0 |
| Yes | 1 |
Support Information:
- Supported from: MX 10.1.
Deploy File For Application
Use this Sub-group to configure Target Application, File, and Optional Path, Target Application Signature, Persistence Of Deployed File, and Deploy File Source URI to deploy a file to a Target Application.
Detail Information:
Key = fileDeploy
Type = bundle
Target Application, File, and Optional Path
Enter the Android Package Name of the Target Application and the File Name (with optional path) of the file to be delivered to the device and made available to the Target Application. Example: com.company.myapp/config/config.json
If specified, the following must also be specified:
Target Application Signature must be specified to identify the certificate that is used to sign genuine versions of the Android Package for the Target Application. This is mandatory because the file will only be delivered to genuine versions of the Target Application and hence no file will be delivered if this is not specified.
Persistence Of Deployed File must be specified to identify whether the file will be persisted across an Enterprise Reset once it is delivered. This is mandatory because the file can only be delivered if it is known whether it should be stored persistently or not and hence no file will be delivered if this is not specified.
Deploy File Source URI must be specified to identify the location from which the file will be acquired from a Server. This is mandatory because the file can only be delivered if it can be acquired from a Server and hence no file will be delivered if this is not specified.
Detail Information:
Key = fdDestAppPathAndFileName
Type = string
Support Information:
- Supported from: MX 11.3.
Target Application Signature
Enter the Base 64 encoded contents of the DER-format certificate file (.CER file) that must be used to sign genuine versions of the Android Package for the Target Application when specified via Target Application, File, and Optional Path.
This is mandatory when Target Application, File, and Optional Path is specified to be used to verify that the Target Application is genuine and hence no file will be acquired if this is not specified.
Detail Information:
Key = fdDestSignature
Type = string
Support Information:
- Supported from: MX 11.3.
Persistence Of Deployed File
Select whether the file will be persisted across an Enterprise Reset when it is delivered to the device and made available to the Target Application when specified via Target Application, File, and Optional Path.
If the value Do nothing is specified, then no file will be delivered because the file can only be delivered if it is known whether it should be stored persistently.
If the value Do Not Persist is specified, then the file will be stored securely for delivery to the Target Application but will be stored such that it will be lost as a result of any Data Wipe, such as would occur in an Enterprise Reset or a Factory Reset.
If the value Persist is specified, then the file will be stored securely for delivery to the Target Application and will be stored such that it will be preserved across a Data Wipe performed as a result of an Enterprise Reset.
Detail Information:
Key = fdDeployPersistence
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Do Not Persist | 0 |
| Persist | 1 |
Support Information:
- Supported from: MX 11.3.
Deploy File Source URI
Enter the Source URI of a file on a Server that will be acquired and delivered to the device and made available to the Target Application when specified via Target Application, File, and Optional Path.
This is mandatory when Target Application, File, and Optional Path is specified to identify the file on a Server to be acquired and delivered to the device and hence no file will be acquired if this is not specified.
Detail Information:
Key = fdSourceURI
Type = string
Support Information:
- Supported from: MX 11.3.
Firmware Over The Air Configuration
Use this Sub-group to configure LifeGuard OTA Full Automation, LifeGuard OTA Options, LifeGuard OTA Service, LifeGuard OTA UI, Mode Manual Action, Enterprise Reset SUW Bypass, OS Streaming - Authorization Type, OS Upgrade Suppress Reboot, OS Downgrade File, OS Streaming - Custom Authentication Header, OS Streaming - File URL, OS Streaming - Password, OS Streaming - Username, OS Streaming - Zebra Authentication Token, OS Upgrade File, OS Upgrade or Downgrade File, LifeGuard Update Over Cellular, and Verify Manifest File.
Detail Information:
Key = fotaStep
Type = bundle
Support Information:
- Supported from: MX 9.1.
LifeGuard OTA Full Automation
Select the state used to perform automatic updates on the device.
If the value Do not change is selected, then no change will be made to the state used to perform automatic updates on the device.
If the value On is selected, OS update operations will be performed automatically as soon as new software is available.
If the value Off is selected, OS update operations will not be performed automatically even if new software is available.
Detail Information:
Key = OsAutoUpdate
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | 1 |
| Off | 2 |
Support Information:
- Supported from: MX 11.1.
LifeGuard OTA Options
Enter one or more optional parameters to determine LifeGuard OTA behavior or leave blank (empty string) to leave unchanged.
Detail Information:
Key = LifeGuardOTAOptions
Type = string
Support Information:
- Supported from: Future Use.
LifeGuard OTA Service
Select the mode used to perform Firmware Over The Air (FOTA) operations on a device.
If the value Do not change is selected, then no change will be made to the mode used to perform Firmware Over The Air (FOTA) operations on a device.
If the value Off is selected, Firmware Over The Air (FOTA) operations will be performed in Manual Mode only when Mode Manual Action is specified and when one or more of the following are specified: Enterprise Reset SUW Bypass, OS Upgrade Suppress Reboot, OS Upgrade File, Verify Manifest File.
If the value On is selected, Firmware Over The Air (FOTA) operations will be performed in Automatic Mode you do not need to specify any additional information.
Detail Information:
Key = fotaMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | 1 |
| Off | 2 |
Support Information:
- Supported from: MX 9.1.
LifeGuard OTA UI
Select whether the device user should be allowed to control the Mode of the LifeGuard Over The Air Client via the in-device Client UI.
If the value Do not change is selected, then no change will be made to whether the device user should be allowed to control the Mode of the LifeGuard Over The Air Client via the in-device Client UI.
If the value Disallow is selected, the device user will NOT be allowed to control the Mode of the LifeGuard Over The Air Client via the in-device Client UI.
If the value Allow is selected, the device user will be allowed to control the Mode of the LifeGuard Over The Air Client via the in-device Client UI.
Detail Information:
Key = fotaUserControlMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
- Supported from: MX 9.1.
Mode Manual Action
Select an Action to perform in Manual Mode to explicitly perform a Firmware Over The Air (FOTA) operation on a device when the value Off is selected for LifeGuard OTA Service.
If the value Do nothing is selected, then no Action will be performed in Manual Mode to explicitly perform a Firmware Over The Air (FOTA) operation on a device when the value Off is selected for LifeGuard OTA Service.
If the value Enterprise Reset is selected, you may also specify Enterprise Reset SUW Bypass to control whether the Setup Wizard (SUW) will be bypassed on GMS devices following the Enterprise Reset.
If the value Factory Reset is selected, you do not need to specify any additional information.
If the value Full Device Wipe is selected, you do not need to specify any additional information.
If the value OS Update is selected, you must also specify OS Upgrade or Downgrade File to provide the path and file name of the image file (which must already be in the device file system at the specified location with the specified name) to be used to perform the operation.
If the value Verify Manifest is selected, you must also specify Verify Manifest File to provide the path and file name of the Manifest file (which must already be in the device file system at the specified location with the specified name) to be used to perform the verification.
If the value OS Upgrade is selected, you must also specify OS Upgrade File to provide the path and file name of the image file (which must already be in the device file system at the specified location with the specified name) to be used to perform the operation. You may also specify OS Upgrade Suppress Reboot to control whether a reboot should automatically be performed following an A/B upgrade.
If the value OS Downgrade is selected, you must also specify OS Downgrade File to provide the path and file name of the image file (which must already be in the device file system at the specified location with the specified name) to be used to perform the operation.
If the value OS Upgrade Streamingis selected, you must also specify OS Streaming - File URL to provide the URL of the image file to be used to perform the operation and you must also specify OS Streaming - Authorization Type to provide information about how authentication to that URL will be performed and one or more of OS Streaming - Username, OS Streaming - Password, OS Streaming - Zebra Authentication Token, or OS Streaming - Custom Authentication Header to supply the detail information needed to perform the selected authentication.
If the valueOS Downgrade Streaming (Discontinued) is selected, then no Action will be performed because support for this Action is no longer available.
If the value Cancel is selected, if possible, the current operation is canceled and you do not need to specify any additional information.
Notes:
The Action value OS Update can be used to perform either an Upgrade or Downgrade operation on devices with Android versions < 8.0 but can only be used to perform an Upgrade operation on devices with Android versions >= 8.0. Furthermore, if the provided ZIP file attempts to do a Downgrade, the Downgrade will NOT occur on devices with Android versions >= 8.0.
The Action value OS Upgrade can only be used to perform an Upgrade operation on devices with Android versions >= 8.0. Furthermore, if the provided ZIP file attempts to do a Downgrade, the Downgrade will NOT occur.
The Action value OS Downgrade can only be used to perform a Downgrade operation on devices with Android versions >= 8.0. Furthermore, if the provided ZIP file attempts to do an Upgrade, the Upgrade will NOT occur.
The Action value OS Upgrade Streaming can only be used to perform a streaming upgrade operation on devices with Android version >= 8.0.
Detail Information:
Key = fotaAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Enterprise Reset | 5 |
| Factory Reset | 6 |
| Full Device Wipe | 7 |
| OS Update | 8 |
| Verify Manifest | 9 |
| OS Upgrade | |
| OS Downgrade | 11 |
| OS Upgrade Streaming | 12 |
| OS Downgrade Streaming (Discontinued) | |
| Cancel | 14 |
Support Information:
- Supported from: MX 8.1.
Enterprise Reset SUW Bypass
Select whether the Setup Wizard (SUW) will be bypassed on GMS devices when in the future Enterprise Resets are performed by specifying the Action value Enterprise Reset Mode Manual Action.
If the value Do not change is selected, then no change will be made to whether the Setup Wizard (SUW) will be bypassed on GMS devices when in the future Enterprise Resets are performed.
If the value Bypass is selected, the Setup Wizard (SUW) will be bypassed on GMS devices when in the future Enterprise Resets are performed.
If the value Do NOT Bypass is selected, the Setup Wizard (SUW) will NOT be bypassed on GMS devices when in the future Enterprise Resets are performed.
Detail Information:
Key = fotaActionEnterpriseResetSuwBypass
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Bypass | 1 |
| Do NOT Bypass | 2 |
Support Information:
- Supported from: MX 7.1.
OS Streaming - Authorization Type
Select the authentication type to use in Manual Mode to reach the remote URL holding the file needed to perform a Firmware Over The Air (FOTA) operation on a device when the value is selected.
If the value Do nothing is selected, then no update will be done.
If the value No Authorization is selected, no authorization will be used to reach the URL and you do not need to specify any additional information.
If the value Zebra Authentication Token is selected, you must also specify OS Streaming - Zebra Authentication Token to provide the token to use to authenticate to the server.
If the value Basic Authentication is selected, you must also specify OS Streaming - Username and OS Streaming - Password to provide the username and password needed to authenticate to the server.
If the value Custom Authorization Header is selected, you must also specify OS Streaming - Custom Authentication Header to provide any custom information necessary to authenticate to the server.
Detail Information:
Key = fotaActionOsUpdateStreamingAuthType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| No Authorization | 0 |
| Zebra Authentication Token | 1 |
| Basic Authentication | 2 |
| Custom Authorization Header | 3 |
Support Information:
- Supported from: MX 10.0.
OS Upgrade Suppress Reboot
Select whether the automatic reboot that would normally be performed following the successful completion of an A/B Upgrade should be suppressed, when the Action value OS Upgrade is selected for Mode Manual Action. Note that if the automatic reboot is suppressed, the reboot will still be required to activate the new OS following the A/B Upgrade, and the later performance of that reboot, at a suitable time, will become the responsibility of the EMM choosing to suppress the automatic reboot.
If the value Do not change is selected, then no change will be made to whether the automatic reboot that would normally be performed following the successful completion of an A/B Upgrade should be suppressed.
If the value Suppress is selected, the automatic reboot that would normally be performed following the successful completion of an A/B Upgrade will be suppressed.
If the value Do NOT Suppress is selected, the automatic reboot that would normally be performed following the successful completion of an A/B Upgrade will NOT be suppressed.
Note: This is not supported for differential or LifeGuard updates on devices running Android 10 or earlier, since they do not support A/B Upgrade.
Detail Information:
Key = fotaActionOsUpdateSuppressReboot
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Suppress | 1 |
| Do NOT Suppress | 2 |
Support Information:
- Supported from: MX 8.1.
OS Downgrade File
Enter the path and file name of an OS Full or Patch image file, which must already exist at the specified location in the device file system, to be used to downgrade a device to an older OS when the Action value OS Downgrade is selected for Mode Manual Action.
Detail Information:
Key = fotaActionOsDowngradeOnlyFile
Type = string
Support Information:
- Supported from: MX 8.1.
OS Streaming - Custom Authentication Header
Enter all custom information to authenticate to the server to get access to the URL holding the OS or Patch image file to be used to perform a streaming update on a device when the Action value OS Upgrade Streaming is selected for Mode Manual Action and when OS Streaming - Authorization Type is specified.
Detail Information:
Key = fotaActionOsUpdateStreamingCustomAuthHeader
Type = string
Support Information:
- Supported from: MX 10.0.
OS Streaming - File URL
Enter the URL of an OS Full or Patch image file to be used to perform a streaming update on a device when the Action value OS Upgrade Streaming is selected for Mode Manual Action and when OS Streaming - Authorization Type is specified.
Detail Information:
Key = fotaActionOsUpdateStreamingFile
Type = string
Support Information:
- Supported from: MX 10.0.
OS Streaming - Password
Enter the password associated with OS Streaming - Username to authenticate to the server to get access to the URL holding the OS or Patch image file to be used to perform a streaming update on a device when the Action value OS Upgrade Streaming is selected for Mode Manual Action and when OS Streaming - Authorization Type is specified.
Detail Information:
Key = fotaActionOsUpdateStreamingPassword
Type = string
Support Information:
- Supported from: MX 10.0.
OS Streaming - Username
Enter the username to authenticate to the server to get access to the URL holding the OS or Patch image file to be used to perform a streaming update on a device when the Action value OS Upgrade Streaming is selected for Mode Manual Action and when OS Streaming - Authorization Type is specified.
Detail Information:
Key = fotaActionOsUpdateStreamingUserName
Type = string
Support Information:
- Supported from: MX 10.0.
OS Streaming - Zebra Authentication Token
Enter the token to use to authenticate to Zebra Support Central to get access to the URL holding the OS or Patch image file to be used to perform a streaming update on a device when the Action value OS Upgrade Streaming is selected for Mode Manual Action and when OS Streaming - Authorization Type is specified.
Detail Information:
Key = fotaActionOsUpdateStreamingZebraAuthToken
Type = string
Support Information:
- Supported from: MX 10.0.
OS Upgrade File
Enter the path and file name of an OS Full or Patch image file, which must already exist at the specified location in the device file system, to be used to upgrade a device to a newer OS when the Action value OS Upgrade is selected for Mode Manual Action.
Detail Information:
Key = fotaActionOsUpdateFile
Type = string
Support Information:
- Supported from: MX 8.1.
OS Upgrade or Downgrade File
Enter the path and file name of an OS Full or Patch image file, which must already exist at the specified location in the device file system, to be used to selectively upgrade or downgrade a device to a newer or older OS (based on the image file) when the Action value OS Update is selected for Mode Manual Action.
Detail Information:
Key = fotaActionOsUpgradeOrDowngradeFile
Type = string
Support Information:
- Supported from: MX 8.1.
LifeGuard Update Over Cellular
Select whether LifeGuard updates should occur over Cellular (metered) networks.
If the value Do not change is selected, then no change will be made to whether LifeGuard updates should occur over Cellular (metered) networks.
If the value On is selected, Cellular (metered) networks will be used for updates.
If the value Off is selected, Cellular (metered) networks will not be used for updates.
Detail Information:
Key = OsUpateOverCellular
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| On | 1 |
| Off | 2 |
Support Information:
- Supported from: MX 11.4.
Verify Manifest File
Enter the path and file name of a Manifest file, which must already exist at the specified location in the device file system, to be used to verify support of a corresponding image file on a device when the Action value Verify Manifest is selected for Mode Manual Action.
Detail Information:
Key = fotaActionVerifyManifestFile
Type = string
Support Information:
- Supported from: MX 8.1.
General UI Configuration
Use this Sub-group to configure Action, Clear Application Cache Package, Clear Application Data Package, Allow device user Control of Do Not Disturb Mode, App Info Icon on Long Press on Recent App Header, Auto Correct, Battery Charging LED, Battery Swap UI Popup, Control Dark Theme, Control Proximity Sensor, Display of Navigation Bar, External Keyboard, Launcher Package Name, Locale, Long Press on Home Key to Launch Google Assistant, Network Notification Popup, On-Screen Power Button, Pull Down Notification Bar, Show Airplane Mode in Power Key Menu, Show Battery Percentage In Notification Bar, Show Pairing Popup, Show Passwords, Show Power Off in Power Key Menu, Show Touch Mode in Power Key Menu, Show Virtual Keyboard when Physical Keyboard is Active, Status Bar, Use Of Clipboard, Sharing, Use of Date in Notification Panel to Access Clock Application, Use of Home Key, Use of Magnification Gestures, Use of Recent Apps Key, Use of Split Screen Mode, User Control of Multi User, Double Trigger, Touch Mode, Screen Protector, Turn on/off the Large Key Indicator feature, Device user control of Large Key Indicator, Assistant App, Custom Assistant App, Home Screen Wallpaper, and Custom Home Screen Wallpaper.
Detail Information:
Key = uiStep
Type = bundle
Support Information:
- Supported from: MX 9.1.
Action
Select an Action to perform miscellaneous UI behavior on a device:
If the value Do nothing is selected, no action will be taken.
If the value Clear Clipboard is selected, any data currently in the clipboard of the device will be discarded, This will cause the data to no longer be available to paste.
If the value Clear Recently Used Apps List is selected, the list of previously used (launched) applications will be cleared. This can be used to prevent the device user from accessing previously used applications or control their behavior or configuration from the list presented when the Recent button is pressed.
If the value Clear Application Cache is selected, the cache of a specified application will be cleared. The most common use of this would be to delete cached information, such as login credentials or state, and thereby return the application to its default behavior. The use of this Action value requires that you must also specify Clear Application Cache Package to identify the application whose cache is to be cleared.
If the value Turn On All GMS Applications is selected, all GMS applications that are considered Safe to Disable will be enabled.
If the value Turn Off All GMS Applications is selected, all GMS applications that are considered Safe to Disable will be disabled.
Note: Since it is possible to turn GMS Applications on or off individually, using the values Turn On All GMS Applications and Turn Off All GMS Applications will guarantee only that all GMS Applications are On or Off immediately after the requested Action is completed. Subsequent Actions could result in any mixture of GMS Applications being turned On or Off. The behavior of the system or any GMS applications under such conditions is not guaranteed.
Detail Information:
Key = uiAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Clear Clipboard | 1 |
| Clear Recently Used Apps List | 2 |
| Clear Application Cache | 3 |
| Turn On All GMS Applications | 4 |
| Turn Off All GMS Applications | 5 |
| Clear Application User Data | 10 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Clear Application Cache Package
Enter the Android Package Name for which the cache should be cleared Clear Application Cache is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = uiActionClearApplicationCachePackage
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.0.
Clear Application Data Package
Enter the Android Package Name for which all user data should be cleared when performing a Clear Application User Data Action when the value Clear Application User Data is selected for Action or leave blank (empty string) to do nothing.
Detail Information:
Key = uiActionClearApplicationUserDataPackage
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Allow device user Control of Do Not Disturb Mode
Select whether the device user will be presented with the option to control the state of Do Not Disturb Mode from the Menu presented when the power key is held down on a device.
If the value Do not change is selected, then no change will be made to whether the device user will be presented with the option to control the state of Do Not Disturb Mode from the Menu presented when the power key is held down on a device.
If the value Hide is selected, the device user will NOT be presented with the option to control the state of Do Not Disturb Mode from the Menu presented when the power key is held down on a device.
If the value Show is selected, the device user will be presented with the option to control the state of Do Not Disturb Mode from the Menu presented when the power key is held down on a device.
Detail Information:
Key = uiUserControlDoNotDisturbMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
App Info Icon on Long Press on Recent App Header
Select whether a Long Press on the Home Key will Launch the Google Assistant.
If the value Do not change is selected, then no change will be made to whether a Long Press on the Home Key will Launch the Google Assistant.
If the value Hide is selected, an App Info Icon will NOT be shown on Long Press on Recent App Header.
If the value Show is selected, an App Info Icon will be shown on Long Press on Recent App Header.
Detail Information:
Key = uiAppInfoOnLongPressRecentAppHeader
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.2.
Auto Correct
Select whether the device user prompted for corrections to potential mistakes made during entry of data on a device.
If the value Do not change is selected, then no change will be made to whether the device user prompted for corrections to potential mistakes made during entry of data on a device.
If the value Off is selected, the device user will NOT be prompted to correct potential mistakes during data entry.
If the value On is selected, the device user will be prompted to correct potential mistakes during data entry.
Detail Information:
Key = uiAutoCorrect
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Battery Charging LED
Select whether the charging system be allowed to display the battery charging state using the charging LED when a device is in operating mode.
If the value Do not change is selected, then no change will be made to whether the charging system be allowed to display the battery charging state using the charging LED when a device is in operating mode.
If the value Disable is selected, the charging system will be prevented from using the charging LED to display the battery charging state, which may reduce distractions in environments where many devices are charging.
If the value Enable is selected, the charging system will be allowed to use the charging LED to display the battery charging state, which may make it easier to distinguish a fully charged device from a partially charged device.
Detail Information:
Key = uiBatteryChargingLED
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable | 2 |
| Enable | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Battery Swap UI Popup
Select whether the device user will automatically be presented with the Battery Swap UI when the device battery level drops below a fixed threshold.
- If the value Disable is selected, the device user will NOT automatically be presented with the Battery Swap UI when the device battery level drops below a fixed threshold.
- If the value Enable is selected, the device user will automatically be presented with the Battery Swap UI when the device battery level drops below a fixed threshold, perhaps helping to avoid emergency shutdown and potential loss of data as a result.
Detail Information:
Key = uiBatterySwapPopup
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable | 2 |
| Enable | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Control Dark Theme
Select whether dark theme will be used on the device.
If the value Do not change is selected, then no change will be made to whether dark theme will be used on the device.
If the value Off is selected, dark theme will NOT be used.
If the value On is selected, dark theme will be used.
Detail Information:
Key = uiDarkTheme
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 11.3.
Control Proximity Sensor
Select whether the proximity sensor will be used.
If the value Do not change is selected, then no change will be made to whether the proximity sensor will be used.
If the value Disallow is selected, the proximity sensor will be used.
If the value Allow is selected, the proximity sensor will not be used.
Detail Information:
Key = uiProximitySensor
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
- Supported from: MX 11.5.
Display of Navigation Bar
Select whether the on-screen Navigation Bar will be displayed and hence whether it will take up screen real estate and can be used to navigate the device UI.
If the value Do not change is selected, then no change will be made to whether the on-screen Navigation Bar will be displayed and hence whether it will take up screen real estate and can be used to navigate the device UI.
If the value Off is selected, the on-screen Navigation Bar will NOT be displayed and hence whether it will NOT take up any screen real estate, and hence cannot be used to navigate the device UI.
If the value On is selected, the on-screen Navigation Bar will be displayed and hence whether it will take up any screen real estate, and hence be used to navigate the device UI.
Detail Information:
Key = uiDisplayNavigationBar
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 7.1.
External Keyboard Configuration
Use this Sub-group to configure Action, Add Keyboard Name, Add Layout Name, and Remove Keyboard Name.
Detail Information:
Key = uiExternalKeyboardConfig
Type = bundle
Action
Select an Action to be performed to manage External Keyboard Layout Mappings..
If the value Do nothing is selected, no Action will be performed to manage External Keyboard Layout Mappings..
If the value Add/Replace Keyboard Layout Mapping is selected, the External Keyboard Layout Mapping for the layout specified in Add Layout Name will be added or replaced for the keyboard name specified via Add Keyboard Name
If the value Remove Keyboard Layout Mapping is selected, the External Keyboard Layout Mapping previously added for the keyboard name specified via Add Keyboard Name will be removed.
If the value Remove All Keyboard Layout Mappings is selected, all External Keyboard Layout Mappings will be removed.
Detail Information:
Key = uiEKCAction
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Add Keyboard Name
Enter the keyboard name to associate with the layout being defined or leave blank (empty string) to leave unchanged. You must also specify Add Layout Name to provide the layout to be applied to the named keyboard.
Note that the name entered must be among keyboards listed in the Input Settings panel on device.
Detail Information:
Key = uiEKCName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Add Layout Name
Enter the keyboard layout name being defined or leave blank (empty string) to leave unchanged.
Detail Information:
Key = uiEKCLayoutName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Remove Keyboard Name
Enter the external keyboard name to be removed or leave blank (empty string) to leave unchanged.
Note that the name entered must be a keyboard name for which a mapping was previously added.
Detail Information:
Key = uiEKCOptionalName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Launcher Package Name
Enter the Android Package Name to be made the default launcher application or leave blank (empty string) to leave unchanged.
This would typically be used when installing an new launcher (home screen) application as a replacement for the default Android launcher.
Detail Information:
Key = uiLauncherPackageName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.1.
Locale
Select the Locale to be used on a device.
A Locale is specified by selecting a Language (e.g. English) and optionally a Region (e.g. the United States).
If the value Do not change is selected, then no change will be made to the current Locale will be made.
If a value containing only a Language is selected, a standard non-regional form of the specified Language will be used (e.g. CHINA).
If a value containing both a Language and a Region is selected, a regional form of the specified Language for the specified Region will be used (e.g. CANADA_FRENCH).
Detail Information:
Key = uiLocale
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| CANADA | en_CA |
| CANADA_FRENCH | fr_CA |
| CHINA | zh_CN |
| CHINESE | zh |
| ENGLISH | en |
| FRANCE | fr_FR |
| FRENCH | fr |
| GERMAN | de |
| GERMANY | de_DE |
| ITALIAN | it |
| ITALY | it_IT |
| JAPAN | ja_JP |
| JAPANESE | ja |
| KOREA | ko_KR |
| KOREAN | ko |
| PRC | zh_CN |
| SIMPLIFIED_CHINESE | zh_CN |
| TAIWAN | zh_TW |
| TRADITIONAL_CHINESE | zh_TW |
| UK | en_GB |
| US | en_US |
| SPANISH | es_ES |
| US_SPANISH | es_US |
| BRAZIL_PORTUGUESE | pt_BR |
| PORTUGUESE | pt_PT |
| AUSTRALIA_ENGLISH | en_AU |
| INDIA_ENGLISH | en_IN |
| SWEDEN_SWEDISH | sv_SE |
| NORWAY_NORWEGIAN-BOKMAL | nb_NO |
| FINLAND_FINISH | fi_FI |
| DENMARK_DANISH | da_DK |
Support Information:
- Supported from: MX 5.1.
Long Press on Home Key to Launch Google Assistant
Select whether a Long Press on the Home Key will Launch the Google Assistant.
If the value * not change* is selected, then no change will be made to whether a Long Press on the Home Key will Launch the Google Assistant.
If the value Disallow is selected, a Long Press on the Home Key will NOT Launch the Google Assistant.
If the value Allow is selected, a Long Press on the Home Key will Launch the Google Assistant.
Detail Information:
Key = uiLongPressHomeLaunchesGoogleAssistant
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.2.
Network Notification Popup
Select whether the Network Notification Popup will be presented to inform the device user that their network may be monitored.
If the value Do not change is selected, then no change will be made to whether the Network Notification Popup will be presented to inform the device user that their network may be monitored.
If the value Off is selected, the Network Notification Popup will NOT be presented, and hence the device user will NOT be notified that their network may be monitored, even if circumstances warrant such notification.
If the value On is selected, the Network Notification Popup may be presented, and hence the device user may be notified that their network may be monitored, if circumstances warrant such notification.
Detail Information:
Key = uiNetworkNotificationPopup
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.1.
On-Screen Power Button
Select whether the On Screen Power Button feature will be turned ON or OFF.
If the value Do not change is selected, then no change will be made to whether the On Screen Power Button feature will be turned ON or OFF.
If the value Disable is selected, the On Screen Power Button feature will be turned OFF and hence the on-screen power button will NOT be displayed.
If the value Enable is selected, the On Screen Power Button feature will be turned ON and hence the on-screen power button WILL be displayed. Note that the On Screen Power Button feature allows a button to be displayed which allows the device user to turn the device off, similar to the operation of the physical power button (if any) and can be used to improve the user experience in cases where a physical power button is not present or is not convenient to use, such as when the device user is wearing gloves.
Detail Information:
Key = uiOnScreenPowerButton
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable | 2 |
| Enable | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Pull Down Notification Bar
Select whether the device user is allowed to Pull Down the Notification Bar to interact with notifications in the Notifications Panel.
If the value Do not change is selected, then no change will be made to whether the device user is allowed to Pull Down the Notification Bar to interact with notifications in the Notifications Panel.
If the value Off is selected, the device user will NOT be allowed to Pull Down the Notification Bar, and hence will not be allowed to interact with notifications in the Notifications Panel.
If the value On is selected, the device user will be allowed to Pull Down the Notification Bar, and hence will be allowed to interact with notifications in the Notifications Panel.
Detail Information:
Key = uiPullDownNotificationBar
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Show Airplane Mode in Power Key Menu
Select whether the device user will be presented with the option to control the state of Airplane Mode from the Menu presented when the power key is held down on a device.
If the value Do not change is selected, then no change will be made to whether the device user will be presented with the option to control the state of Airplane Mode from the Menu presented when the power key is held down on a device.
If the value Hide is selected, the device user will NOT be presented with the option to control the state of Airplane Mode from the Menu presented when the power key is held down on a device.
If the value Show is selected, the device user will be presented with the option to control the state of Airplane Mode from the Menu presented when the power key is held down on a device.
Detail Information:
Key = uiShowAirplaneModeInPwrKeyMenu
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Show Battery Percentage In Notification Bar
Select whether the battery percentage will be displayed in the notification bar.
If the value Do not change is selected, then no change will be made to whether the battery percentage will be displayed in the notification bar.
If the value Turn Off is selected, the battery percentage will NOT be displayed in the notification bar.
If the value Turn On is selected, the battery percentage will be displayed in the notification bar.
Detail Information:
Key = uiShowBatteryPercentage
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Show Pairing Popup
Select whether a New Pairing Popup will be presented when an unpaired peripheral device attempts to establish a new Bluetooth pairing with a device.
If the value Do not change is selected, then no change will be made to whether a New Pairing Popup will be presented when an unpaired peripheral device attempts to establish a new Bluetooth pairing with a device.
If the value Off is selected, a New Pairing Popup will NOT be presented when an unpaired peripheral device attempts to establish a new Bluetooth pairing with a device.
If the value On is selected, a New Pairing Popup will be presented when an unpaired peripheral device attempts to establish a new Bluetooth pairing with a device.
Notes:
This option has no effect on existing pairings.
This option does not prevent new pairings that are initiated from the device to the peripheral.
This option does not prevent new pairings from being established based on configured Silent Pairing rules.
Detail Information:
Key = uiPairingPopup
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Show Passwords
Select whether passwords should be shown (displayed) when entered on the device or hidden (masked).
If the value Do not change is selected, then no change will be made to whether passwords should be shown (displayed) when entered on the device or hidden (masked).
If the value Off is selected, passwords will globally be hidden (masked) whenever they are being entered on the device.
If the value On is selected, passwords will globally be shown (displayed) whenever they are being entered on the device.
Detail Information:
Key = uiShowPasswords
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Show Power Off in Power Key Menu
Select whether the device user will be presented with the option to Power Off the device from the Menu presented when the power key is held down on a device.
If Do not change is selected, then no change will be made to whether the device user will be presented with the option to Power Off the device from the Menu presented when the power key is held down on a device.
If Hide is selected, the user will not be able to choose the Power Off menu item on the Power Key Menu.
If Show is selected, the user will be able to choose the Power Off menu item on the Power Key Menu.
Detail Information:
Key = uiShowPowerOffInPwrKeyMenu
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Show Touch Mode in Power Key Menu
Select whether the device user will be presented with the option to control the state of the Touch Mode from the Menu presented when the power key is held down on a device.
If the value Do not change is selected, then no change will be made to whether the device user will be presented with the option to control the state of the Touch Mode from the Menu presented when the power key is held down on a device.
If the value Hide is selected, then the device user will NOT be presented with the option to control the state of the Touch Mode from the Menu presented when the power key is held down on a device.
If the value Show is selected, then the device user will be presented with the option to control the state of the Touch Mode from the Menu presented when the power key is held down on a device.
Detail Information:
Key = uiShowTouchModeInPwrKeyMenu
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.2.
Show Virtual Keyboard when Physical Keyboard is Active
Select whether the Virtual Keyboard will be shown when the Physical Keyboard is Active.
If the value Do not change is selected, then no change will be made to whether the Virtual Keyboard will be shown when the Physical Keyboard is Active.
If the value Off is selected, the Virtual Keyboard will NOT be shown if the device has a Physical Keyboard that is Active. This can help avoid the annoyance and confusing of using up screen real-estate to display an on-screen keyboard when the device user is using a Physical Keyboard to enter data.
If the value On is selected, the Virtual Keyboard will be shown when data entry is in progress regardless of whether the device has an Active Physical Keyboard.
Detail Information:
Key = uiShowVirtualKeyboard
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.0.
Status Bar
Select whether the Android Status Bar should be displayed.
If the value Do not change is selected, then no change will be made to whether the Android Status Bar should be displayed.
If the value Hide is selected, the Android Status Bar will not be displayed, which also means that the device user will not be allowed to interact with notifications in the Notifications Panel.
If the value Show is selected, the Android Status Bar will be displayed, which also means that the device user might be allowed to interact with notifications in the Notifications Panel.
Detail Information:
Key = uIStatusBar
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Hide | 2 |
| Show | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.4.
Use Of Clipboard
Select whether the device user will be allowed to utilize the clipboard on a device to cut, copy, and paste text between applications.
If the value Do not change is selected, then no change would be made to whether the device user will be allowed to utilize the clipboard on a device to cut, copy, and paste text between applications.
If the value Off is selected, the device user will NOT be allowed to utilize the clipboard on a device to cut, copy, and paste text between applications.
If the value On is selected, the device user will be allowed to utilize the clipboard on a device to cut, copy, and paste text between applications.
Detail Information:
Key = uiUseOfClipboard
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.2.
Sharing
Select whether the device user will be allowed to utilize the clipboard Sharing on a device to share the contents of the clipboard.
If the value Do not change is selected, then no change will be made to whether the device user will be allowed to utilize the clipboard Sharing on a device to share the contents of the clipboard.
If the value Off is selected, then the device user will NOT be allowed to utilize the clipboard Sharing on a device to share the contents of the clipboard.
If the value On is selected, then the device user will be allowed to utilize the clipboard Sharing on a device to share the contents of the clipboard.
Detail Information:
Key = uiUseOfClipboardSharing
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Use of Date in Notification Panel to Access Clock Application
Select whether the Date in the Notification Panel can be used to invoke the Clock Application.
If the value Do not changeis selected, then no change will be made to whether the Date in the Notification Panel can be used to invoke the Clock Application.
If the value Allow is selected, clicking the Date in the Notification Panel will invoke the Clock Application.
If the value Disallow is selected, clicking the Date in the Notification Panel will NOT invoke the Clock Application.
Detail Information:
Key = uiDateInNotificationAccessClock
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.2.
Use of Home Key
Select whether the device user will be allowed to utilize the Home Key on a device to leave the current context and return to the Home/Launcher screen.
If the value Do not change is selected, then no change will be made to whether the device user will be allowed to utilize the Home Key on a device to leave the current context and return to the Home/Launcher screen.
If the value Off is selected, the Home key will be ignored and will cause no action if it is pressed.
If the value On is selected, the Home key will be honored and will cause device to go to the Home/Launcher screen when if it is pressed.
Detail Information:
Key = uiUseOfHomeKey
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Use of Magnification Gestures
Select whether the device user is allowed to Use Magnification Gestures.
If the value Do not change is selected, then no change will be made to whether the device user is allowed to Use Magnification Gestures.
If the value Off is selected, the Magnification Gestures will be ignored and no action will be taken if they are used by the device user.
If the value On is selected, the Magnification Gestures will be honored and appropriate action will be taken if they are used by the device user.
Detail Information:
Key = uiUseOfMagnificationGestures
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 8.0.
Use of Recent Apps Key
Select whether the device user is allowed to Use the Recent Apps Key to access recently launched applications.
If the value Do not change is selected, then no change will be made to whether the device user is allowed to Use the Recent Apps Key to access recently launched applications.
If the value Off is selected, the Recent Apps Key will be ignored, and hence the device user will not be allowed to access recently launched applications.
If the value On is selected, the Recent Apps Key will be honored, and hence the device user will be allowed to access recently launched applications.
Detail Information:
Key = uiUseOfRecentAppsKey
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
- Supported from: MX 7.1.
Use of Split Screen Mode
Select whether Split Screen Mode is allowed to be used on the device.
If the value Do not change is selected, then no change will be made to whether Split Screen Mode is allowed to be used on the device.
If the value Disallow is selected, the use of Split Screen Mode will be blocked on the device.
If the value Allow is selected, the use of Split Screen Mode will be allowed on the device.
Detail Information:
Key = uiSplitScreenMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
User Control of Multi User
Select whether Primary device user is allowed to invoke UI to manage Multi User, including the ability to Create, Delete, and limit the actions of Secondary Users.
If the value Do not change is selected, then no change will be made to whether Primary device user is allowed to invoke UI to manage Multi User, including the ability to Create, Delete, and limit the actions of Secondary Users.
If the value Disallow is selected, the Primary device user will not be allowed to manage Secondary Users, even if the device supports multiple users.
If the value Allow is selected, the Primary device user will be allowed to manage Secondary Users, if the device supports multiple users.
Detail Information:
Key = uiUserControlMultiUser
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disallow | 2 |
| Allow | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Double Trigger
Use this Sub-group to configure Maximum Time Between Trigger Pulls, Mode, Alt State, Ctrl State, Fn State, Key Code, and Shift State.
Detail Information:
Key = doubleTrigger
Type = bundle
Support Information:
- Supported from: MX 11.4.
Maximum Time Between Trigger Pulls
Enter the maximum time allowed for a double trigger pull to be considered in milliseconds when it is sent as the Behavior for a specified Key when Send a key-code is specified for Mode. or leave blank (empty string) to leave unchanged.
Detail Information:
Key = dtMaxTime
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Mode
Select whether a double trigger will send a key code.
If the value Do nothing is selected, no action will be taken.
If the value Send a key-code is selected, a double trigger pull within the window specified by Maximum Time Between Trigger Pulls will cause the key code specified in Key Code to be sent.
If the value Don't send a key-code is selected, a double trigger pull will not send a key code.
Detail Information:
Key = dtMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Send a key-code | 1 |
| Don't send a key-code | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Alt State
Select whether the Key Code specified via Key Code will be sent with the Alt keyboard state when it is sent as the Behavior for a specified Key when Send a key-code is specified for Mode.
If the value Current is selected, when the Key Code is sent, it will be sent with the CURRENT Alt key state. This will cause the Key Code to be interpreted as an Alt key or not based on the current Alt key state.
If the value Off is selected, when the Key Code is sent, it will NOT be sent with the Alt keyboard state NOT set. This will ensure that the Key Code will NOT interpreted as an Alt key.
If the value On is selected, when the Key Code is sent, it WILL be sent with the Alt keyboard state set. This will ensure that the Key Code WILL be interpreted as an Alt key.
Detail Information:
Key = dtAltState
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Ctrl State
Select whether the Key Code specified via Key Code will be sent with the Ctrl keyboard state when it is sent as the Behavior for a specified Key when Send a key-code is specified for Mode.
If the value Current is selected, when the Key Code is sent, it will be sent with the CURRENT Ctrl key state. This will cause the Key Code to be interpreted as an Ctrl key or not based on the current Ctrl key state.
If the value Off is selected, when the Key Code is sent, it will NOT be sent with the Ctrl keyboard state NOT set. This will ensure that the Key Code will NOT interpreted as an Ctrl key.
If the value On is selected, when the Key Code is sent, it WILL be sent with the Ctrl keyboard state set. This will ensure that the Key Code WILL be interpreted as an Ctrl key.
Detail Information:
Key = dtCtrlState
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Fn State
Select whether the Key Code specified via Key Code will be sent with the Fn keyboard state when it is sent as the Behavior for a specified Key when Send a key-code is specified for Mode.
If the value Current is selected, when the Key Code is sent, it will be sent with the CURRENT Fn key state. This will cause the Key Code to be interpreted as an Fn key or not based on the current Fn key state.
If the value Off is selected, when the Key Code is sent, it will NOT be sent with the Fn keyboard state NOT set. This will ensure that the Key Code will NOT interpreted as an Fn key.
If the value On is selected, when the Key Code is sent, it WILL be sent with the Fn keyboard state set. This will ensure that the Key Code WILL be interpreted as an Fn key.
Detail Information:
Key = dtFnState
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Key Code
Select the key code to send when Send a key-code is set to Mode and a double trigger is performed.
Detail Information:
Key = dtKeyCode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| 0 | 7 |
| 1 | 8 |
| 2 | 9 |
| 3 | 10 |
| 4 | 11 |
| 5 | 12 |
| 6 | 13 |
| 7 | 14 |
| 8 | 15 |
| 9 | 16 |
| + (Plus) | 81 |
| - (Minus) | 69 |
| = (Equals) | 70 |
| ( (Left Bracket) | 71 |
| ) (Right Bracket) | 72 |
| ` (Grave) | 68 |
| / (Slash) | 76 |
| \\\\ (Backslash) | 73 |
| ; (Semicolon) | 74 |
| ' (Apostrophe) | 75 |
| , (Comma) | 55 |
| . (Period) | 56 |
| * (Star) | 17 |
| # (Pound) | 18 |
| @ (At) | 77 |
| A | 29 |
| B | 30 |
| C | 31 |
| D | 32 |
| E | 33 |
| F | 34 |
| G | 35 |
| H | 36 |
| I | 37 |
| J | 38 |
| K | 39 |
| L | 40 |
| M | 41 |
| N | 42 |
| O | 43 |
| P | 44 |
| Q | 45 |
| R | 46 |
| S | 47 |
| T | 48 |
| U | 49 |
| V | 50 |
| W | 51 |
| X | 52 |
| Y | 53 |
| Z | 54 |
| Enter | 66 |
| Tab | 61 |
| Space | 62 |
| Escape | 111 |
| Delete | 67 |
| F1 | 131 |
| F2 | 132 |
| F3 | 133 |
| F4 | 134 |
| F5 | 135 |
| F6 | 136 |
| F7 | 137 |
| F8 | 138 |
| F9 | 139 |
| F10 | 140 |
| F11 | 141 |
| F12 | 142 |
| NUMPAD 0 | 144 |
| NUMPAD 1 | 145 |
| NUMPAD 2 | 146 |
| NUMPAD 3 | 147 |
| NUMPAD 4 | 148 |
| NUMPAD 5 | 149 |
| NUMPAD 6 | 150 |
| NUMPAD 7 | 151 |
| NUMPAD 8 | 152 |
| NUMPAD 9 | 153 |
| NUMPAD / (NUMPAD Divide) | 154 |
| NUMPAD * (NUMPAD Multiply) | 155 |
| NUMPAD - (NUMPAD Subtract) | 156 |
| NUMPAD + (NUMPAD Add) | 157 |
| NUMPAD . (NUMPAD Period) | 158 |
| NUMPAD , (NUMPAD Comma) | 159 |
| NUMPAD Enter | 160 |
| NUMPAD = (NUMPAD Equals) | 161 |
| NUMPAD { (NUMPAD Left Parenthesis) | 162 |
| NUMPAD } (NUMPAD Right Parenthesis) | 163 |
| DPAD Up | 19 |
| DPAD Down | 20 |
| DPAD Left | 21 |
| DPAD Right | 22 |
| DPAD Center | 23 |
| Move Home | 122 |
| Move End | 123 |
| Page Up | 92 |
| Page Down | 93 |
| Insert | 124 |
| Forward Delete | 112 |
| Clear | 28 |
| Lamp | 10024 |
| Suppress Key | 10026 |
| Blue | 10027 |
| Orange | 10028 |
| Grey | 10029 |
| Diamond | 10039 |
| Alt | 10030 |
| Control | 10031 |
| Shift | 10032 |
| Keyboard | 10034 |
| Touch Calibrate | 10035 |
| Scan | 10036 |
| Search Key | 10037 |
| None | 10038 |
| KeyLight | 10025 |
| Keylight Up | 10040 |
| Keylight Down | 10041 |
| Left Shift | 59 |
| Right Shift | 60 |
| Left Alt | 57 |
| Right Alt | 58 |
| Left Control | 113 |
| Right Control | 114 |
| Meta Left | 117 |
| Meta Right | 118 |
| Caps Lock | 115 |
| Num Lock | 143 |
| Scroll Lock | 116 |
| SysRq | 120 |
| Break | 121 |
| Function | 119 |
| Back | 4 |
| Forward | 125 |
| Home | 3 |
| Menu | 82 |
| Settings | 176 |
| Application Switch | 187 |
| Calculator | 210 |
| Explorer | 64 |
| Envelope | 65 |
| Bookmark | 174 |
| Music | 209 |
| Call | 5 |
| End Call | 6 |
| Microphone Mute | 91 |
| Camera | 27 |
| Search | 84 |
| Contacts | 207 |
| Calendar | 208 |
| Volume Up | 24 |
| Volume Down | 25 |
| Volume Mute | 164 |
| Brightness Up | 221 |
| Brightness Down | 220 |
| Power | 26 |
| Sleep | 223 |
| Wakeup | 224 |
| Headset | 79 |
| Push-to-talk | 228 |
| Camera Focus | 80 |
| Media Play/Pause | 85 |
| Media Stop | 86 |
| Media Next | 87 |
| Media Previous | 88 |
| Media Rewind | 89 |
| Media Fast-Forward | 90 |
| Media Play | 126 |
| Media Pause | 127 |
| Media Close | 128 |
| Media Eject | 129 |
| Media Record | 130 |
| Button L1 | 102 |
| Button R1 | 103 |
| Button L2 | 104 |
| Button R2 | 105 |
| Button A | 96 |
| Button B | 97 |
| Button C | 98 |
| Button X | 99 |
| Button Y | 100 |
| Button Z | 101 |
| Left Thumb Button | 106 |
| Right Thumb Button | 107 |
| Start Button | 108 |
| Select Button | 109 |
| Mode Button | 110 |
| Gamepad Button 1 | 188 |
| Gamepad Button 2 | 189 |
| Gamepad Button 3 | 190 |
| Gamepad Button 4 | 191 |
| Gamepad Button 5 | 192 |
| Gamepad Button 6 | 193 |
| Gamepad Button 7 | 194 |
| Gamepad Button 8 | 195 |
| Gamepad Button 9 | 196 |
| Gamepad Button 10 | 197 |
| Gamepad Button 11 | 198 |
| Gamepad Button 12 | 199 |
| Gamepad Button 13 | 200 |
| Gamepad Button 14 | 201 |
| Gamepad Button 15 | 202 |
| Gamepad Button 16 | 203 |
| Zenkaku/Hankaku | 211 |
| Eisu | 212 |
| Muhenkan | 213 |
| Henkan | 214 |
| Katakana/Hiragana | 215 |
| Ro | 217 |
| Yen | 216 |
| Kana | 218 |
| Keyboard | 10034 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Shift State
Select whether the Key Code specified via Key Code will be sent with the Shift keyboard state when it is sent as the Behavior for a specified Key when Send a key-code is specified for Mode.
If the value Current is selected, when the Key Code is sent, it will be sent with the CURRENT Shift key state. This will cause the Key Code to be interpreted as an Shift key or not based on the current Shift key state.
If the value Off is selected, when the Key Code is sent, it will NOT be sent with the Shift keyboard state NOT set. This will ensure that the Key Code will NOT interpreted as an Shift key.
If the value On is selected, when the Key Code is sent, it WILL be sent with the Shift keyboard state set. This will ensure that the Key Code WILL be interpreted as an Shift key.
Detail Information:
Key = dtShiftState
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.4.
Touch Mode
Select the operational mode of the Touch Panel in selected devices:
If the value Do not change is selected, no change to the current operational mode of the Touch Panel will be made.
If the value Stylus or Finger is selected, the Touch Panel will be configured to optimize use with a Stylus or an ungloved Finger.
If the value Glove or Finger is selected, the Touch Panel will be configured to optimize use with a Gloved finger or an ungloved Finger.
If the value Finger Only is selected, the Touch Panel will be configured to optimize an ungloved Finger.
If the value Stylus or Glove or Finger is selected, the Touch Panel will be configured to optimize use with a Stylus, a Gloved finger, or an ungloved Finger.
If the value Finger and Wet is selected, the Touch Panel will be configured to optimize use with a finger on a wet touch panel
Notes:
Not all devices support the ability to configure the Touch Panel mode and those that do may not support every mode.
An attempt to configure the Touch Panel mode on a device that does not support it will result in an error.
An attempt to configure a Touch Panel mode on a device that does not support that mode will result in an error.
Detail Information:
Key = uiTouchMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Stylus or Finger | Stylus and Finger |
| Glove or Finger | Glove and Finger |
| Finger Only | Finger |
| Stylus or Glove or Finger | Stylus and Glove and Finger |
| Finger and Wet | Finger and Wet |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Screen Protector
Select whether Touch Panel should be optimized to account for the presence of a Screen Protector when Touch Mode is specified.
If Do not change is selected, the Touch Panel configuration related to the presence of a Screen Protector will be unchanged (left in its current state).
If Not present is specified, the Touch Panel will be configured to optimize use without the presence a Screen Protector.
If Present is specified, the Touch Panel will be configured to optimize use with the presence a Screen Protector.
Note that not all devices support the ability to configure the Touch Panel to account for the presence of a Screen Protector.
Note that the data type of this MC has changed from bool to string, in order to add a Do nor change value to better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "uiTouchScreenProtector" to "uiTouchScreenProtectorString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will no longer contain that value for this MC and will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = uiTouchScreenProtectorString
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Not present | false |
| Present | true |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Turn on/off the Large Key Indicator feature
Select whether the Large Key Indicator feature, which allows a large on-screen indicator to be displayed to indicate the state physical keypad on the device (if any) and which can assist the device user in cases where multiple key sequences are required.
If the value Do not change is selected, then no change will be made to whether the Large Key Indicator feature, which allows a large on-screen indicator to be displayed to indicate the state physical keypad on the device.
If the value Turn Off is selected, the Large Key Indicator feature will be turned OFF and hence the on-screen indicator will NOT be displayed.
If the value Turn On is selected, the Large Key Indicator feature will be turned ON and hence the on-screen indicator WILL be displayed.
Detail Information:
Key = uiSetLKI
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
- Supported from: MX 9.0.
Device user control of Large Key Indicator
Select whether the device user will be allowed to turn the Large Key Indicator feature ON or OFF.
If the value Do not change is selected, then no change will be made to whether the device user will be allowed to turn the Large Key Indicator feature ON or OFF.
If the value Enable is selected, the device user WILL be allowed to turn the Large Key Indicator feature ON or OFF.
If the value Disable is selected, the device user will NOT be allowed to turn the Large Key Indicator feature ON or OFF.
Detail Information:
Key = uiUserControlLKI
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable | 2 |
| Enable | 1 |
Support Information:
- Supported from: MX 9.0.
Assistant App
Select the assistant to use on the device.
If the value *Do not change *is selected, then no change will be made to the currently selected assistant will be made.
If the value Google Digital Assistant is selected, the Google Digital Assistant will be used
If the value Custom assistant app is selected, a custom assistant app will be used and you must specify Custom Assistant App to provide that assistant.
If the value None is selected, no assistant app will be used.
Detail Information:
Key = uiAssistantApp
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Google Digital Assistant | 1 |
| Custom assistant app | |
| None | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Custom Assistant App
Enter the package name of the custom assistant application to be used on the device when Custom assistant app is specified for Assistant App or leave blank (empty string) if no custom assistant application is required.
Detail Information:
Key = uiCustomAssistantApp
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Home Screen Wallpaper
Select the assistant to use on the device.
If the value Do not change is selected, then no change will be made to the currently selected wallpaper will be made.
If the value Restore to default is selected, the default wallpaper will be used.
If the value Custom is selected, the custom wallpaper specified in Custom Home Screen Wallpaper will be used.
Detail Information:
Key = uiHomeScreenWallpaper
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
Support discontinued from: MX 11.0.
Custom Home Screen Wallpaper
Enter the path and file name of an image file on the device (.jpg or .png) when Custom is specified for Home Screen Wallpaper or leave blank (empty string) if no custom wallpaper is required.
Detail Information:
Key = uiCustomHomeWallpaper
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.5.
GMS Configuration
Use this Sub-group to configure GMS Feature Set and GMS Profile.
Detail Information:
Key = gmsStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
GMS Feature Set
Select the amount of functionality of Google Mobile Services (GMS) to enable.
If the value Do not change is selected, then no change will be made to the amount of functionality of Google Mobile Services (GMS) to enable.
If the value All - Full Set of GMS Features is selected, the entire set of Google Mobile Services (GMS), will be enabled for use. Note that if Google Mobile Services are allowed to be used, may collect and send data to Google.
If the value Restricted - Fixed Minimal Set of GMS Features is selected, a limited (fixed) subset of Google Mobile Services (GMS), will be enabled for use. The subset will automatically be chosen to ensure that basic device functionality is not impaired, that all enabled Google Mobile Services operate usefully, and that no enabled Google Mobile Services send any data to Google.
If the value Profiled - Selected Subset of GMS Features is selected, a selected subset of Google Mobile Services (GMS) features will be enabled for use and you must specify GMS Profile to identify that subset.
Detail Information:
Key = gmsFeatureSet
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
GMS Profile
Select the Google Mobile Services (GMS) profile to enable.
If the value Do not change is selected, then no change will be made to Google Mobile Services (GMS) profile.
If the value Chrome Browser is selected, Chrome Browser will be enabled for use.
If the value Google Maps is selected, Google Maps will be enabled for use.
If the value Firebase Cloud Messaging is selected, Firebase Cloud Messaging will be enabled for use.
If the value Combination of Chrome and Maps and FCM is selected, Combination of Chrome, Maps and FCM will be enabled for use.
Detail Information:
Key = gmsProfile
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Chrome Browser | 1 |
| Google Maps | 2 |
| Firebase Cloud Messaging | 3 |
| Combination of Chrome and Maps and FCM | 4 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
GPRS Configuration
Use this Sub-group to configure Action, Add APN Name, Add APN Replace If Existing, Add APN Make Default, Add APN Access Point, Add APN User Name, Add APN Password, Add APN Port, Add APN Proxy, Add APN MMS Port, Add APN MMS Proxy, Add APN Server, Add APN MMSC, Add APN Type, Add APN MCC, Add APN MNC, Add APN Protocol, Add APN Roaming Protocol, Add Authentication Type, Add MVNO Type, Add MVNO Match Data, and Remove APN Name.
Detail Information:
Key = gprsStep
Type = bundle
Support Information:
- Supported from: MX 8.4.
Action
Select an Action to be performed to manage the GPRS APNs on a device.
If the value Do nothing is selected, then no Action will be performed to manage the GPRS APNs on a device.
If the value AddApn is selected, a new APN will be added, or an existing APN will be overwritten with a new APN. You must also specify Add APN Name to provide the name of the new APN to be added or the name of the existing APN to be replaced. In addition, Add APN Replace If Existing to determine whether an existing APN of the same name should replaced, and Add APN Make Default to determine whether the added or replaced APN should be made the new default APN. You may also specify some or all of the following to further define the APN:
Add APN Make Default
Add APN Access Point
Add APN User Name
Add APN Password
Add APN Port
Add APN Proxy
Add APN MMS Port
Add APN MMS Proxy
Add APN Server
Add APN MMSC
Add APN Type
Add APN MCC
Add APN MNC
If the value RemoveApn is selected, an existing APN will be removed. You must also specify Remove APN Name to provide the name of the APN to be removed.
If the value RemoveAllApns is selected, all existing APNs will be removed and you do not need to specify any additional information.
Detail Information:
Key = gprsAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| AddApn | |
| RemoveApn | |
| RemoveAllApns | 3 |
Support Information:
- Supported from: MX 8.4.
Add APN Name
Enter the name of an APN to be added when the value AddApn is selected for Action.
Detail Information:
Key = gprsActionAddApnName
Type = string
Support Information:
- Supported from: MX 4.2.
Add APN Replace If Existing
Select what happens when an APN already exists with the APN name being added when the value AddApn is selected for Action.
- If the value Replace Existing is selected, if an APN with the name specified via Add APN Name already exists, it will be replaced by the definition of the APN being added.
- If the value Keep Existing is selected, if an APN with the name specified via Add APN Name already exists, it will NOT be replaced. The existing APN will be preserved and the new APN will NOT be added.
Detail Information:
Key = gprsActionAddApnReplaceIfExisting
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Replace Existing | 1 |
| Keep Existing | 0 |
Support Information:
- Supported from: MX 4.2.
Add APN Make Default
Select whether a new APN being added should become the new default APN when the value AddApn is selected for Action. - If the value Yes is selected, the new APN being added will become the new default APN and will be preferred over other APNs when establishing a cellular data connection.
- If the value No is selected, the new APN will not become the new default APN and whatever APN was previously the default will remain the default.
Detail Information:
Key = gprsActionAddApnMakeDefault
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Yes | 1 |
| No | 0 |
Support Information:
- Supported from: MX 4.2.
Add APN Access Point
Enter a value that uniquely identifies an APN on the network when the value AddApn is selected for Action.
APN Identifiers are allocated by cellular carriers to identify the networks that can be reached via various APNs. When acquiring a cellular data plan from a carrier, an APN Identifier will be provided, typically along with other information that qualifies or controls access to the network it identifies.
Detail Information:
Key = gprsActionAddApnAccessPoint
Type = string
Support Information:
- Supported from: MX 4.2.
Add APN User Name
Enter a user name that can be used to authenticate to an APN when the value AddApn is selected for Action.
A network accessed via a given APN Identifier may or may not require authentication. If authentication is required, a user name is generally always required and a password MAY also be required.
Detail Information:
Key = gprsActionAddApnUserName
Type = string
Support Information:
- Supported from: MX 4.2.
Add APN Password
Enter a password that can be used to authenticate to an APN when the value AddApn is selected for Action.
A network accessed via a given APN Identifier may or may not require authentication. If authentication is required, a user name is generally always required and a password MAY also be required.
Detail Information:
Key = gprsActionAddApnPassword
Type = string
Support Information:
- Supported from: MX 4.2.
Add APN Port
Enter the port number of an HTTP proxy to use for all traffic over the network accessed via an APN when the value AddApn is selected for Action.
If a Proxy is required, a Port is also generally always required.
Detail Information:
Key = gprsActionAddApnPort
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN Proxy
Enter the address or name of an HTTP proxy to use for all traffic over the network accessed via an APN when the value AddApn is selected for Action.
- If a Proxy is required, a Port is also generally always required.
Detail Information:
Key = gprsActionAddApnProxy
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN MMS Port
Enter the port number of an HTTP proxy to use ONLY for (Multimedia Messaging Service) MMS traffic over the network accessed via an APN when the value AddApn is selected for Action.
- If an MMS Proxy is required, an MMS Port is also generally always required.
Detail Information:
Key = gprsActionAddApnMmsPort
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN MMS Proxy
Enter the address or name of an HTTP proxy to use ONLY for (Multimedia Messaging Service) MMS traffic over the network accessed via an APN when the value AddApn is selected for Action.
- If an MMS Proxy is required, an MMS Port is also generally always required.
Detail Information:
Key = gprsActionAddApnMmsProxy
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN Server
Enter a WAP Gateway Server address that should be used for an APN when the value AddApn is selected for Action.
WAP Gateways are rarely, if ever, used on or supported by modern cellular carrier networks.
Detail Information:
Key = gprsActionAddApnServer
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN MMSC
Enter the Multimedia Messaging Service Center (MMSC) address required to route MMS traffic over the network accessed via an APN when the value AddApn is selected for Action.
Detail Information:
Key = gprsActionAddApnMmsc
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN Type
Enter the Type of APN to be added when the value AddApn is selected for Action.
The value to specify for Type should be obtained from the cellular carrier whose network is to be accessed via the APN.
Detail Information:
Key = gprsActionAddApnType
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN MCC
Enter the Mobile Country Code (MCC) of the APN to be added when the value AddApn is selected for Action.
The MCC generally match the SIM Card being used or the APN will not be usable.
Detail Information:
Key = gprsActionAddApnMcc
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN MNC
Enter the Mobile Network Code (MNC) of the APN to be added when the value AddApn is selected for Action.
The MNC generally match the SIM Card being used or the APN will not be usable.
Detail Information:
Key = gprsActionAddApnMnc
Type = string
Support Information:
- Supported from: MX 8.4.
Add APN Protocol
Select the APN Protocol.
If the value Do not change is selected, then no change will be made to the APN Protocol.
If the value IPv4 is selected, IPv4 will be applied.
If the value IPv6 is selected, IPv6 will be applied.
If the value IPv4/IPv6 is selected, IPv4/IPv6 will be applied.
Detail Information:
Key = gprsActionAddApnProtocol
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| IPv4 | 1 |
| IPv6 | 2 |
| IPv4/IPv6 | 3 |
Support Information:
- Supported from: MX 9.3.
Add APN Roaming Protocol
Select the APN Roaming Protocol.
If the value Do not change is selected, then no change will be made to the APN Roaming Protocol.
If the value IPv4 is selected, IPv4 will be applied.
If the value IPv6 is selected, IPv6 will be applied.
If the value IPv4/IPv6 is selected, IPv4/IPv6 will be applied.
Detail Information:
Key = gprsActionAddApnProtocolRoaming
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| IPv4 | 1 |
| IPv6 | 2 |
| IPv4/IPv6 | 3 |
Support Information:
- Supported from: MX 9.3.
Add Authentication Type
Select the Type of Authentication to be used for APN to be added when the value AddApn is selected for Action.
If the value Do nothing is selected, then no APN will be added.
If the value None is selected, No Authentication Protocol will be used to authenticate for the APN.
If the value PAP is selected, the Password Authentication Protocol (PAP) will be used to authenticate for the APN.
If the value CHAP is selected, the Challenge Handshake Authentication Protocol (CHAP) will be used to authenticate for the APN.
Detail Information:
Key = gprsActionAddApnAuthenticationType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| None | 1 |
| PAP | 2 |
| CHAP | 3 |
Support Information:
- Supported from: MX 8.3.
Add MVNO Type
Select the MVNO (Mobile Virtual Network Operator) Type to be used for APN to be added when the value AddApn is selected for Action.
- If the value None is selected, No MVNO will be used to configured for the APN.
- If the value SPN is selected, the MVNO will be specified via an SPN (Service Provider Name) value for the APN, which you must also specify via Add MVNO Match Data.
- If the value IMSI is selected, the MVNO will be specified via an IMSI (International Mobile Subscriber Identity) value for the APN, which you must specify via Add MVNO Match Data.
- If the value GID is selected, the MVNO will be specified via an GID (Group Identifier) value for the APN, which you must specify via Add MVNO Match Data.
- If the value ICCID is selected, the MVNO will be specified via an GID (Integrated Circuit Card ID) value for the APN, which you must specify via Add MVNO Match Data.
Detail Information:
Key = gprsActionAddApnMvnoType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| None | 1 |
| SPN | 2 |
| IMSI | 3 |
| GID | 4 |
| ICCID | 5 |
Support Information:
- Supported from: MX 8.4.
Add MVNO Match Data
Enter the MVNO (Mobile Virtual Network Operator) Match Data to be used for APN to be added when the value AddApn is selected for Action and if a value other than None is selected for Add MVNO Type.
The exact value to be specified depends on the MVNO Type specified. Consult your MVNO carrier for information on the MVNO Type and MVNO Match Data value to be used.
Detail Information:
Key = gprsActionAddApnMvnoMatchData
Type = string
Support Information:
- Supported from: MX 8.4.
Remove APN Name
Enter the name of an APN to be removed when the value RemoveApn is selected for Action.
Detail Information:
Key = gprsActionRemoveApnName
Type = string
Support Information:
- Supported from: MX 4.1.1.
Host Name Configuration
Use this Sub-group to configure Device Friendly Name and Device Network Name.
Detail Information:
Key = hostStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Device Friendly Name
Enter the friendly name by which the device will be known to the device user or leave blank (empty string) to leave unchanged.
Detail Information:
Key = hostFriendlyDeviceName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.5.
Device Network Name
Enter the name by which a device will be known on the network or leave blank (empty string) to leave unchanged.
Detail Information:
Key = hostDeviceName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.1.
Key Mapping Configuration
Use this Sub-group to configure Action, Add Mapping Key ID, and Add Mapping Behaviors.
Detail Information:
Key = keymapStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Action
Select an Action to affect the behaviors mapped to the keys on the physical keyboard (if any) of a device:
- If the value Add Mapping is selected, a new mapping for a single physical key is added to the mapping tables for one or more keyboard states. You must also specify Add Mapping Key ID to provide the physical key for which mappings are to be added or replaced. In addition, you must also specify the Sub-array Add Mapping Behaviors to define the behavior(s) to be mapped to the identified physical key. If any prior mappings were applied to specify the behaviors of the identified physical key, they will all be replaced by the new specified behaviors.
- If the value Reset All Mappings is selected, the mapping tables are reset to their defaults. This effectively removes all mappings that have previously been added and returns the behaviors of all keys to their default out-of-box state.
Detail Information:
Key = keymapAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add Mapping | 1 |
| Reset All Mappings | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Add Mapping Key ID
Select a value that uniquely identifies a physical key on the physical keyboard of a device for which one or more behaviors are to be specified when the value Add Mapping is selected for Action.
Detail Information:
Key = keymapActionAddMappingKeyId
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| 0 | 0 |
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| 4 | 4 |
| 5 | 5 |
| 6 | 6 |
| 7 | 7 |
| 8 | 8 |
| 9 | 9 |
| A | A |
| B | B |
| C | C |
| D | D |
| E | E |
| F | F |
| G | G |
| H | H |
| I | I |
| J | J |
| K | K |
| L | L |
| M | M |
| N | N |
| O | O |
| P | P |
| Q | Q |
| R | R |
| S | S |
| T | T |
| U | U |
| V | V |
| W | W |
| X | X |
| Y | Y |
| Z | Z |
| . (Period) | DOT |
| , (Comma) | COMMA |
| * (Star) | STAR |
| # (Pound) | POUND |
| F1 | F1 |
| F2 | F2 |
| F3 | F3 |
| F4 | F4 |
| F5 | F5 |
| F6 | F6 |
| F7 | F7 |
| F8 | F8 |
| F9 | F9 |
| F10 | F10 |
| F11 | F11 |
| F12 | F12 |
| Enter | ENTER |
| Up | UP |
| Down | DOWN |
| Left | LEFT |
| Right | RIGHT |
| NAV_OK | NAV_OK |
| Escape | ESC |
| Backspace | BACKSPACE |
| Delete | DELETE |
| Insert | INSERT |
| Space | SPACE |
| Return | RETURN |
| Clear | CLR |
| Field Exit | FIELD_EXIT |
| Alt | ALT |
| Control | CTRL |
| Shift | SHIFT |
| Func | FUNC |
| Alpha | ALPHA |
| CL | CL |
| FN | FN |
| Blue | BLUE |
| Orange | ORANGE |
| Grey | GREY |
| Diamond | DIAMOND |
| Green Dot | GREEN |
| Red Dot | RED |
| Volume Up | VOLUMEUP |
| Volume Down | VOLUMEDOWN |
| Scan | SCAN |
| Grip Trigger | GRIP_TRIGGER |
| Grip Trigger 2 | GRIP_TRIGGER_2 |
| Button L1 | LEFT_TRIGGER_1 |
| Button L2 | LEFT_TRIGGER_2 |
| Button R1 | RIGHT_TRIGGER_1 |
| Button R2 | RIGHT_TRIGGER_2 |
| Left Trigger | LEFT_TRIGGER |
| Right Trigger | RIGHT_TRIGGER |
| Center Trigger | CENTER_TRIGGER |
| Gun Trigger | GUN_TRIGGER |
| Headset Button | HEADSET_HOOK |
| Back | BACK |
| Home | HOME |
| Menu | MENU |
| Recent | RECENT |
| Search | SEARCH |
| Keyboard Backlight | KEYLIGHT |
| Display Backlight | LAMP |
| Power | POWER |
| P1 Button | P1 |
| P2 Button | P2 |
| P3 Button | P3 |
| P4 Button | P4 |
| P5 Button | P5 |
| P6 Button | P6 |
| W1 Button | W1 |
| W2 Button | W2 |
| Rear Button | REAR_BUTTON |
| Left External Trigger | LEFT_EXTERNAL_TRIGGER |
| Right External Trigger | RIGHT_EXTERNAL_TRIGGER |
| Bluetooth Remote Trigger 1 | BLUETOOTH_REMOTE_TRIGGER_1 |
| Bluetooth Remote Trigger 2 | BLUETOOTH_REMOTE_TRIGGER_2 |
| Touch NAV_PAD | NAV_PAD |
| Macro 1 | M1 |
| Macro 2 | M2 |
| Macro 3 | M3 |
| Macro 4 | M4 |
| Macro 5 | M5 |
| Macro 6 | M6 |
| Brightness Up | BRIGHTNESSUP |
| Brightness Down | BRIGHTNESSDOWN |
| Keyboard | KEYBOARD |
| Keyboard Backlight Brightness Up | KEYLIGHTUP |
| Keyboard Backlight Brightness Down | KEYLIGHTDOWN |
| Rotate | ROTATE |
| - (Minus) | MINUS |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Add Mapping Behaviors
Use this Sub-array to configure one or more Behavior(s).
Detail Information:
Key = keymapActionAddMappingBehaviors
Type = bundle_array
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Behavior
Use this Sub-group to configure Table Name, Type, Send Key Code, Alt, Ctrl, Fn, Shift, Send Trigger, Send Intent, Type, Action, Category, Package Name, Class, Data URI, Flags, MIME Type, Extra Name, Extra Value, Launch Application Name, and Add Key Event.
Detail Information:
Key = keymapBehavior
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Table Name
Select the name of the table into which a specific behavior will be stored. Mapping tables are associated with keyboard states and are named based on the state key on the physical keyboard of a device that causes that keyboard state to be activated or deactivated.
Note that due to variations in keyboard size and layout, not all keyboard states may be supported on all devices or on all keyboard possible on any given device. Some or all of the following may values may be supported:
If the value Base is selected, the Base Mapping table will be selected. The Base Mapping table defines the behavior that will be performed for a physical key when it is pressed while no special keyboard state is active.
If the value Blue is selected, the Blue Mapping table will be selected. The Blue Mapping table defines the behavior that will be performed for a physical key when it is pressed in conditions where the Blue key has been used to activate the Blue keyboard state.
If the value Orange is selected, the Orange Mapping table will be selected. The Orange Mapping table defines the behavior that will be performed for a physical key when it is pressed in conditions where the Orange key has been used to activate the Orange keyboard state.
If the value Grey is selected, the Grey Mapping table will be selected. The Grey Mapping table defines the behavior that will be performed for a physical key when it is pressed in conditions where the Grey key has been used to activate the Grey keyboard state.
If the value Shift is selected, the Shift Mapping table will be selected. The Shift Mapping table defines the behavior that will be performed for a physical key when it is pressed in conditions where the Shift key has been used to activate the Shift keyboard state.
If the value Control is selected, the Control Mapping table will be selected. The Control Mapping table defines the behavior that will be performed for a physical key when it is pressed in conditions where the Control key has been used to activate the Control keyboard state.
Detail Information:
Key = keymapBehaviorTableName
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Base | Base |
| Blue | Blue |
| Orange | Orange |
| Grey | Grey |
| Diamond | Diamond |
| Shift | Shift |
| Control | Control |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Type
Select the type of behavior that will be performed when a specified key is pressed while the keyboard state associated with the specified Mapping table is active. The following may values are supported:
If the value Do nothing is selected, then no change will be made to the behavior that will be performed when a specified key is pressed while the keyboard state associated with the specified Mapping table is active. The result would be equivalent to not including the behavior in the Sub-array Add Mapping Behaviors.
If the value Send Key Code is selected, the behavior performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active will be to send a specified key code. This performs Classic Keyboard Remapping, where the behavior of a key is changed to be the behavior of some other key, which may or may not be present on the physical keyboard. You must also specify Send Key Code to provide the key code that will be sent.
If the value Send Trigger is selected, the behavior performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active will be to send a trigger signal. Trigger signals may be used to initiate various activities, such as barcode scanning, RFID reading, push to talk, etc. You must also specify Send Trigger to select which trigger signal will be sent,
If the value Launch Application is selected, the behavior performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active will be to launch an application. You must also specify Launch Application Name to provide the Friendly Name of the application to be launched. Note that this is NOT the Android Package Name. To launch an application by its Android Package Name, the value Send Intent should be used.
If the value Send Intent is selected, the behavior performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active will be to send and Android Intent, which might cause any number of possible results, depending on the nature of the intent configured to be sent. You must also specify some or all of the following to define the Android Intent to be sent:
Type
Action
Category
Package Name
Class
Data URI
Flags
MIME Type
Extra Name
Extra Value
Sending an Android Intent provides a very flexible way to specify the behavior to be performed for a key by invoking an application or service. As such, there are many options that control the nature of the intent that will be sent. It is generally recommended to fully understand the nature of the Android Intent to be sent before attempting to configure it as a key behavior. In many cases, the application or service to be invoked will define the nature of the intent is wishes to received and that definition can be used to drive the configuration.
If the value Suppress Key is selected, NO behavior will be performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active. This provides a method to remap a key to do nothing.
If the value Reset To Default is selected, the behavior performed when the specified key is pressed while the keyboard state associated with the specified Mapping table is active be reset back to its defaults. This will effectively remove any prior mapping of that key in that state and return the key to its standard behavior in that state.
Detail Information:
Key = keymapBehaviorType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Send Key Code | 2 |
| Send Trigger | 1 |
| Launch Application | 4 |
| Send Intent | 3 |
| Suppress Key | 5 |
| Reset To Default | 7 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Send Key Code
Select the key code that will be sent as the behavior for a specified key a specified state when the value Send Key Code is selected for Type.
- If the value Suppress Key" is selected, then the key code sent will cause the key to be ignored. This will produce behavior comparable to if the value *Suppress Key were specified for **Type.
Detail Information:
Key = keymapBehaviorTypeSendKeyCode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| 0 | 7 |
| 1 | 8 |
| 2 | 9 |
| 3 | 10 |
| 4 | 11 |
| 5 | 12 |
| 6 | 13 |
| 7 | 14 |
| 8 | 15 |
| 9 | 16 |
| + (Plus) | 81 |
| - (Minus) | 69 |
| = (Equals) | 70 |
| ( (Left Bracket) | 71 |
| ) (Right Bracket) | 72 |
| ` (Grave) | 68 |
| / (Slash) | 76 |
| \\\\ (Backslash) | 73 |
| ; (Semicolon) | 74 |
| ' (Apostrophe) | 75 |
| , (Comma) | 55 |
| . (Period) | 56 |
| * (Star) | 17 |
| # (Pound) | 18 |
| @ (At) | 77 |
| A | 29 |
| B | 30 |
| C | 31 |
| D | 32 |
| E | 33 |
| F | 34 |
| G | 35 |
| H | 36 |
| I | 37 |
| J | 38 |
| K | 39 |
| L | 40 |
| M | 41 |
| N | 42 |
| O | 43 |
| P | 44 |
| Q | 45 |
| R | 46 |
| S | 47 |
| T | 48 |
| U | 49 |
| V | 50 |
| W | 51 |
| X | 52 |
| Y | 53 |
| Z | 54 |
| Enter | 66 |
| Tab | 61 |
| Space | 62 |
| Escape | 111 |
| Delete | 67 |
| F1 | 131 |
| F2 | 132 |
| F3 | 133 |
| F4 | 134 |
| F5 | 135 |
| F6 | 136 |
| F7 | 137 |
| F8 | 138 |
| F9 | 139 |
| F10 | 140 |
| F11 | 141 |
| F12 | 142 |
| NUMPAD 0 | 144 |
| NUMPAD 1 | 145 |
| NUMPAD 2 | 146 |
| NUMPAD 3 | 147 |
| NUMPAD 4 | 148 |
| NUMPAD 5 | 149 |
| NUMPAD 6 | 150 |
| NUMPAD 7 | 151 |
| NUMPAD 8 | 152 |
| NUMPAD 9 | 153 |
| NUMPAD / (NUMPAD Divide) | 154 |
| NUMPAD * (NUMPAD Multiply) | 155 |
| NUMPAD - (NUMPAD Subtract) | 156 |
| NUMPAD + (NUMPAD Add) | 157 |
| NUMPAD . (NUMPAD Period) | 158 |
| NUMPAD , (NUMPAD Comma) | 159 |
| NUMPAD Enter | 160 |
| NUMPAD = (NUMPAD Equals) | 161 |
| NUMPAD { (NUMPAD Left Parenthesis) | 162 |
| NUMPAD } (NUMPAD Right Parenthesis) | 163 |
| DPAD Up | 19 |
| DPAD Down | 20 |
| DPAD Left | 21 |
| DPAD Right | 22 |
| DPAD Center | 23 |
| Move Home | 122 |
| Move End | 123 |
| Page Up | 92 |
| Page Down | 93 |
| Insert | 124 |
| Forward Delete | 112 |
| Clear | 28 |
| Lamp | 10024 |
| Suppress Key | 10026 |
| Blue | 10027 |
| Orange | 10028 |
| Grey | 10029 |
| Diamond | 10039 |
| Alt | 10030 |
| Control | 10031 |
| Shift | 10032 |
| Keyboard | 10034 |
| Touch Calibrate | 10035 |
| Scan | 10036 |
| Search Key | 10037 |
| None | 10038 |
| KeyLight | 10025 |
| Keylight Up | 10040 |
| Keylight Down | 10041 |
| Left Shift | 59 |
| Right Shift | 60 |
| Left Alt | 57 |
| Right Alt | 58 |
| Left Control | 113 |
| Right Control | 114 |
| Meta Left | 117 |
| Meta Right | 118 |
| Caps Lock | 115 |
| Num Lock | 143 |
| Scroll Lock | 116 |
| SysRq | 120 |
| Break | 121 |
| Function | 119 |
| Back | 4 |
| Forward | 125 |
| Home | 3 |
| Menu | 82 |
| Settings | 176 |
| Application Switch | 187 |
| Calculator | 210 |
| Explorer | 64 |
| Envelope | 65 |
| Bookmark | 174 |
| Music | 209 |
| Call | 5 |
| End Call | 6 |
| Microphone Mute | 91 |
| Camera | 27 |
| Search | 84 |
| Contacts | 207 |
| Calendar | 208 |
| Volume Up | 24 |
| Volume Down | 25 |
| Volume Mute | 164 |
| Brightness Up | 221 |
| Brightness Down | 220 |
| Power | 26 |
| Sleep | 223 |
| Wakeup | 224 |
| Headset | 79 |
| Push-to-talk | 228 |
| Camera Focus | 80 |
| Media Play/Pause | 85 |
| Media Stop | 86 |
| Media Next | 87 |
| Media Previous | 88 |
| Media Rewind | 89 |
| Media Fast-Forward | 90 |
| Media Play | 126 |
| Media Pause | 127 |
| Media Close | 128 |
| Media Eject | 129 |
| Media Record | 130 |
| Button L1 | 102 |
| Button R1 | 103 |
| Button L2 | 104 |
| Button R2 | 105 |
| Button A | 96 |
| Button B | 97 |
| Button C | 98 |
| Button X | 99 |
| Button Y | 100 |
| Button Z | 101 |
| Left Thumb Button | 106 |
| Right Thumb Button | 107 |
| Start Button | 108 |
| Select Button | 109 |
| Mode Button | 110 |
| Gamepad Button 1 | 188 |
| Gamepad Button 2 | 189 |
| Gamepad Button 3 | 190 |
| Gamepad Button 4 | 191 |
| Gamepad Button 5 | 192 |
| Gamepad Button 6 | 193 |
| Gamepad Button 7 | 194 |
| Gamepad Button 8 | 195 |
| Gamepad Button 9 | 196 |
| Gamepad Button 10 | 197 |
| Gamepad Button 11 | 198 |
| Gamepad Button 12 | 199 |
| Gamepad Button 13 | 200 |
| Gamepad Button 14 | 201 |
| Gamepad Button 15 | 202 |
| Gamepad Button 16 | 203 |
| Zenkaku/Hankaku | 211 |
| Eisu | 212 |
| Muhenkan | 213 |
| Henkan | 214 |
| Katakana/Hiragana | 215 |
| Ro | 217 |
| Yen | 216 |
| Kana | 218 |
| Keyboard | 10034 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Alt
Select how a key code will be sent as the behavior for a specified key a specified state when the value Send Key Code is selected for Type and when Send Key Code is specified.
If the value Current is selected, when the key code is sent, it will be sent with the current Alt keyboard state inactive.
If the value Off is selected, when the key code is sent, it will be sent with the Alt keyboard state inactive. This will ensure that the key code is NOT interpreted as an Alt key.
If the value On is selected, when the key code is sent, it will be sent with the Alt keyboard state active. This will ensure that the key code is interpreted as an Alt key.
If no value is specified, when the key code is sent, the Alt keyboard state will not be changed. This will cause the key to be interpreted as an Alt key or not based on the existing state.
Detail Information:
Key = keymapBehaviorTypeSendKeyCodeAlt
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Ctrl
Select how a key code will be sent as the behavior for a specified key a specified state when the value Send Key Code is selected for Type and when Send Key Code is specified.
If the value Current is selected, when the key code is sent, it will be sent with the current Ctrl keyboard state inactive.
If the value Off is selected, when the key code is sent, it will be sent with the Ctrl keyboard state inactive. This will ensure that the key code is NOT interpreted as an Ctrl key.
If the value On is selected, when the key code is sent, it will be sent with the Ctrl keyboard state active. This will ensure that the key code is interpreted as an Ctrl key.
If no value is specified, when the key code is sent, the Ctrl keyboard state will not be changed. This will cause the key to be interpreted as an Ctrl key or not based on the existing state.
Detail Information:
Key = keymapBehaviorTypeSendKeyCodeCtrl
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Fn
Select how a key code will be sent as the behavior for a specified key a specified state when the value Send Key Code is selected for Type and when Send Key Code is specified.
If the value Current is selected, when the key code is sent, it will be sent with the current Fn keyboard state inactive.
If the value Off is selected, when the key code is sent, it will be sent with the Fn keyboard state inactive. This will ensure that the key code is NOT interpreted as an Fn key.
If the value On is selected, when the key code is sent, it will be sent with the Fn keyboard state active. This will ensure that the key code is interpreted as an Fn key.
If no value is specified, when the key code is sent, the Fn keyboard state will not be changed. This will cause the key to be interpreted as an Fn key or not based on the existing state.
Detail Information:
Key = keymapBehaviorTypeSendKeyCodeFn
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Shift
Select how a key code will be sent as the behavior for a specified key a specified state when the value Send Key Code is selected for Type and when Send Key Code is specified.
If the value Current is selected, when the key code is sent, it will be sent with the current Shift keyboard state inactive.
If the value Off is selected, when the key code is sent, it will be sent with the Shift keyboard state inactive. This will ensure that the key code is NOT interpreted as an Shift key.
If the value On is selected, when the key code is sent, it will be sent with the Shift keyboard state active. This will ensure that the key code is interpreted as an Shift key.
If no value is specified, when the key code is sent, the Shift keyboard state will not be changed. This will cause the key to be interpreted as an Shift key or not based on the existing state.
Detail Information:
Key = keymapBehaviorTypeSendKeyCodeShift
Type = string
| UI Choice | JSON Value |
|---|---|
| Current | |
| On | 1 |
| Off | 0 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Send Trigger
Select the trigger signal that will be sent as the behavior for a specified key a specified state when the value Send Trigger is selected for Type.
Eight trigger signals are defined, but not all may be supported on all devices. All devices generally support at least Trigger 1 and generally default to using this trigger signal to activate the barcode scanner. Some devices may support additional trigger signals and some devices might be reconfigured to use Trigger 1 for some purpose other than barcode scanning. To determine which trigger signals are supported on a given device, consult the documentation for that specific device.
Detail Information:
Key = keymapBehaviorTypeSendTrigger
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Trigger 1 | 10016 |
| Trigger 2 | 10017 |
| Trigger 3 | 10018 |
| Trigger 4 | 10019 |
| Trigger 5 | 10020 |
| Trigger 6 | 10021 |
| Trigger 7 | 10022 |
| Trigger 8 | 10023 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Send Intent
Select when an intent should be sent as the behavior for a remapped key.
- If the value On Key Down is selected, the intent will be sent immediately when the key is first detected as being pressed.
- If the value On Key Up is selected, the intent will not be sent until the key is detected as being released after being being pressed.
- If the value On Both Key Up and Down is selected, the intent will be sent immediately when the key is first detected as being pressed and then again when the key is detected as being released.
Detail Information:
Key = keymapBehaviorTypeSendIntent
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| On Key Down | 1 |
| On Key Up | 2 |
| On Both Key Up and Down | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Type
Enter the method in which an Android Intent should be sent to invoke an application or service when the value Send Intent is selected for Type.
Depending on the application or service to be invoked, there is likely only one method that can be used successfully to invoke a desired behavior in that application or service. You will need to consult the documentation or developer of a given application or service to determine whether a category value is needed and, if so, which value will invoke the desired behavior. The possible values are.
- If the value StartActivity is selected, the Android Intent will be sent using the startActivity() method. This method is suitable for invoking Activities, which are components that perform user interactions. If the behavior to be invoked involves interacting with the device user, this method will most likely be used.
- If the value Broadcast is selected, the Android Intent will be sent using the sendBroadcast() method. This method is suitable for invoking Services, which are components that implement background operations. If the behavior to be invoked does not involves interacting with the device user, this method will most likely be used.
Detail Information:
Key = keymapBehaviorTypeSendIntentType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| StartActivity | StartActivity |
| Broadcast | Broadcast |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Action
Enter the action value of an Android Intent to be sent to invoke an application or service when the value Send Intent is selected for Type.
An action value is NOT mandatory to specify for an Android Intent. But an action value is commonly used to identify the purpose of an Android Intent. This can be especially when the application or service to be invoked supports multiple functions, in which case the action value is commonly used to identify which function to perform when invoking that application or service. You will need to consult the documentation or developer of a given application or service to determine whether an action value is needed and, if so, which value will invoke the desired behavior.
Detail Information:
Key = keymapBehaviorTypeSendIntentAction
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Category
Enter the category value of an Android Intent to be sent to invoke an application or service when the value Send Intent is selected for Type.
A category value is NOT mandatory to specify for an Android Intent. But a category value is commonly used to help identify the purpose of an Android Intent. This can be especially when the application or service to be invoked supports many functions, in which case many action values may be used to identify those functions and it may be useful to categorize those functions. In some cases, the same action value might be supported in more than one category. You will need to consult the documentation or developer of a given application or service to determine whether a category value is needed and, if so, which value will invoke the desired behavior.
Detail Information:
Key = keymapBehaviorTypeSendIntentCategory
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Package Name
Enter the Android Package Name of the application or service to invoke when the value Send Intent is selected for Type.
It is not mandatory to specify the Android Package Name when sending an Android Intent, but is is often advisable.
- When an Android Package Name is specified, the intent becomes an Explicit Intent and the intent can ONLY be sent to an application or service with that Android Package Name and no other. This can increase security and is often used when the intent being sent requires any sensitive data. You must also specify Class whenever an Android Package Name is specified, since an Explicit Intent is always sent to an Android Component, which is identified by a Android Package Name and a Class within that Package.
- When no Android Package Name is specified, the intent becomes an Implicit Intent and the intent may be sent to any application or service that has registered its ability to handle that intent. This can increase flexibility and is often used when the intent being sent requires no sensitive data and when it may be desirable to dynamically control which application or service is ultimately invoked to handle that intent.
Detail Information:
Key = keymapBehaviorTypeSendIntentPackageName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Class
Enter the Android Class that identifies an Android Component within an application or service to invoke when the value Send Intent is selected for Type and when Package Name is specified.
Detail Information:
Key = keymapBehaviorTypeSendIntentClass
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Data URI
Enter a Uniform Resource Identifier (URI) that identifies some data, in the form of a resource on the device (e.g. a file in the device file system) or off the device (e.g. a resource available via a network) that should be utilized by the application or service invoked by the intent.
Whether the intended recipient of the intent expects a URI to be specified as part of the intent or not is up to that recipient and/or the definition of the intent that recipient is designed to consume.
Detail Information:
Key = keymapBehaviorTypeSendIntentDataUri
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Flags
Enter intent flags to be set for the intent to be sent.
Intent flags control how the intent is handled by Android. Some intent flags are specific to the type of component that will be invoked by the Intent (e.g. activity vs service). Whether certain intent flags are needed to produce the desired result when the intended recipient of the intent is invoked is up to that recipient and/or the definition of the intent that recipient is designed to consume. Intent flags MUST be specified as a hexadecimal value with the appropriate bits set for any flag or flags desired. Consult the Android documentation to translate intent flag names, when needed, into their appropriate hexadecimal values.
Detail Information:
Key = keymapBehaviorTypeSendIntentFlags
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
MIME Type
Enter a Multipurpose Internet Mail Extensions (MIME) type to use when processing the intent data and when Data URI is specified.
Normally the type would be inferred from the data itself. Setting a MIME type explicitly, disables automatic type detection and and forces handling according to the specified type.
Detail Information:
Key = keymapBehaviorTypeSendIntentMimeType
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Extra Name
Enter the name of a single extra named string value to be attached to the intent to be sent.
Android allows a collection of extra named values, of various types, to be attached to an intent. Exactly one value whose data type must be string can be specified. When a name is specified, you must also specify Extra Value to provide the corresponding value to be attached for the string extra.
Detail Information:
Key = keymapBehaviorTypeSendIntentExtraName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Extra Value
Enter the value of the String Extra to be attached to the intent to be sent and whose name is specified via Extra Name.
Detail Information:
Key = keymapBehaviorTypeSendIntentExtraValue
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Launch Application Name
Enter the Friendly Name of an application to be launched when the value Launch Application is selected for Type.
Note that the application Friendly Name is NOT the same as Android Package Name. The application Friendly Name is generally the name by which the application is identified in in-device UI, such as the application Launcher, the application's Title Bar, and the list of application names display in the Recent Application list and the AppInfo section of the Settings UI. To launch an application based on its Android Package Name, the value Send Intent should be selected for Type instead.
Detail Information:
Key = keymapBehaviorTypeLaunchApplicationName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Add Key Event
Select whether the key event should be added to the intent when the value Send Intent is selected for Type.
Detail Information:
Key = keymapBehaviorTypeSendIntentAddKeyEvent
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| No | 0 |
| Yes | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Log Management
Use this Sub-group to configure Log Action, Upload Snapshots URI, and Collection.
Detail Information:
Key = logStep
Type = bundle
Log Action
Select the Log Action to be performed.
If the value Do nothing is selected, then no Action will be performed by the Log Management subsystem.
If the value Start Background Collection is selected, then the Log Management subsystem will perform an Action to Start Background Collection of Log Files. To ensure that Log File content required for troubleshooting is available, Background Collection of Log Files should be Started well before the occurrence of an event of interest to ensure that when the Log Files are acquired, they will contain information concerning that event.
If the value Stop Background Collection is selected, then the Log Management subsystem will perform an Action to Stop Background Collection of Log Files. Since Background Collection of Log Files can consume significant system resources, it is best to Stop Background Collection of Log Files when troubleshooting is completed and collection of Log Files is no longer required.
If the value Create Snapshot is selected, then the Log Management subsystem will perform an Action to Create a Snapshot of all available Log data up to the point when the Snapshot was Created. Since the Log Management subsystem has limits on the amount of Log data that can be Collected in the Background and will begin discarding older Log data in favor or newer Log data once those limits have been reached, the amount of history a Snapshot can contain will be limited. To avoid missing Log data, a Snapshot would need to be Created at least as frequently as the limits are reached. Multiple Snapshots could be Created and Uploaded at a later time, subject to the storage capacity of the device.
Detail Information:
Key = logAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Start Background Collection | ENABLE |
| Stop Background Collection | DISABLE |
| Create Snapshot | BACKUP_NOW |
Support Information:
- Supported from: MX 4.1.
Upload Snapshots URI
Enter the URI of a location on a Server to which all Snapshot Files previously Created on the device, and which have not yet been Uploaded, will be Uploaded. Each time this is specified, an attempt to Upload Snapshot Files will be made, but that attempt may or may not result in any Snapshot Files being Uploaded, depending on whether any suitable files exist and whether suitable connectivity is available. If this is not specified, then no Upload of Snapshot Files will be attempted.
The specified URI MUST start with a Protocol Specification that indicates which file transfer protocol should be used to Upload the Snapshot File. The following are supported:
FTP:// - The (insecure) File Transfer Protocol (FTP) protocol will be used to Upload the Snapshot File.
FTPS:// - The (secure) File Transfer Protocol over SSL (FTPS) protocol will be used to Upload the Snapshot File.
The specified URI:
MAY contain authentication credentials that will be used to authenticate to the Remote Server before Uploading the Snapshot File.
MUST contain an IP address or domain name that identifies the Remote Server to which the Snapshot File will be Uploaded.
SHOULD typically contain path that identifies the location on the Remote Server, relative to the home folder of the default account or the account selected by the authentication credentials, to which the Snapshot File will be Uploaded.
MUST NOT contain a file name since the name of the file to which the Snapshot File will be Uploaded on the Remote Server will be automatically generated, as described below, to ensure that Snapshot Files from various devices, and created at various times, do not overwrite each other.
Snapshot Files will be Uploaded in the following manner:
Snapshot Files will be Uploaded in the order they were Created on the device (oldest to newest).
Each Snapshot File will be automatically deleted from the device once it has been successfully Uploaded to a Server.
Each Snapshot File that is Uploaded to the Remote Server will be assigned an automatically generated unique file name of the format:
- model-serial-date-time.zip.
The above format enables files Uploaded to the same folder on the Remote Server to be differentiated by the models and serial numbers of the devices that Uploaded them and by the date and time when the files were created on those devices.
- For example: TC510K-17068522528997-01312020-132649.zip
Within the above example:
TC510K is the model identifier of the device that Uploaded the Snapshot File.
17068522528997 is the serial number of the device that Uploaded the Snapshot File.
01312020 is the date the Snapshot File was Created in the device, indicating January 31, 2020.
132649 is the time the Snapshot File was Created in the device, indicating 1:26:49 PM.
Detail Information:
Key = logUploadSnapshotsUri
Type = string
Support Information:
- Supported from: MX 10.1.
Collection Configuration
Use this Sub-group to configure Logging Level.
Detail Information:
Key = logCollectionConfiguration
Type = bundle
Logging Level
Select the Level of Logging to be performed.
If the value Do not change is selected, then no changes will be made to the configuration of the Log Management subsystem.
If the value Basic is selected, then the Log Management subsystem will be configured to collect Kernel and Logcat log data.
If the value Basic+Qxdm is selected, then the Log Management subsystem will be configured to collect Kernel, Logcat and Qxdm log data. Qxdm log data is only supported on WAN (Cellular) devices.
If the value Basic+TCP Dump is selected, then the Log Management subsystem will be configured to collect Kernel, Logcat and TCP Dump log data.
Since Background Collection of Log Files can consume significant system resources, it is best to select the minimum level of Logcat logging that will serve the need. When unsure, it may be advisable to start with lowest level and work up to higher levels if needed.
Detail Information:
Key = logLogcatLevel
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Basic | [binary data] |
| Basic+Qxdm | [binary data] |
| Basic+TCP Dump | [binary data] |
Support Information:
- Supported from: MX 10.1.
Notification Configuration
Use this Sub-group to configure Notification State and Notification Package Name .
Detail Information:
Key = notificationStep
Type = bundle
Support Information:
Supported on Operating System(s): Android 11.
Supported from: MX 11.2.
Notification State
Select whether user notifications are on or off.
If the value Do not change is selected, then no change will be made to whether user notifications are on or off.
If the value Show For All Apps is selected, notifications for all applications will be shown to the user.
If the value Hide For All Apps is selected, notifications for all applications will NOT be shown to the user.
If the value Show By App is selected, notifications for the application defined in Notification Package Name will be shown to the user.
If the value Hide By App is selected, notifications for the application defined in Notification Package Name will NOT be shown to the user.
Detail Information:
Key = notificationState
Type = string
Support Information:
Supported on Operating System(s): Android 11.
Supported from: MX 11.2.
Notification Package Name
Select the Android Package Name that identifies the application for which notifications will be turned On or Off whenShow By App or Hide By App is specified for Notification State.
Detail Information:
Key = notificationPackageName
Type = string
Support Information:
Supported on Operating System(s): Android 11.
Supported from: MX 11.2.
Permission Access Configuration
Use this Sub-group to configure Permission Access Action, Grant Permission, Grant Application Package, Grant Application Signature, Revoke Permission, Revoke Application Package, Revoke Application Signature, Ask Permission, Ask Application Package, and Ask Application Signature.
Detail Information:
Key = permissionAccessStep
Type = bundle
Support Information:
- Supported from: MX 10.4.
Permission Access Action
Select an Action to be performed to manage which Sensitive Android Permissions are allowed to be used by which applications.
If the value Do not change is selected, then no Action will be performed to manage which Sensitive Android Permissions are allowed to be used by which applications.
If the value Grant is selected, then a Sensitive Android Permission will be Granted to a selected Application and you must also specify Grant Permission to identify the Permission to be Granted and you must specify Grant Application Package and Grant Application Signature to identify the Application to which the Permission will be Granted. You should NOT specify %steps.step.permissionAccessStep.permissionAccessActionRevokeApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionRevokeApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionRevokePermissionPermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionRevokeApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionRevokeApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionGrantApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionGrantApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskPermissionPermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionAskApplicationSignaturePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionGrantApplicationPackagePermission Access Configurationsteps.step.permissionAccessStep.permissionAccessActionGrantApplicationSignaturePermission Access Configuration, or Revoke Application Signature.
Detail Information:
Key = permissionAccessAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Grant | Grant |
| Revoke | Revoke |
| Ask | Ask |
Support Information:
- Supported from: MX 10.4.
Grant Permission
Select the name of a Sensitive Android Permission to be Granted to a specified Application when the value Grant is selected for Permission Access Action. You must also specify Grant Application Package and Grant Application Signature to identify the Application.
If the value Do nothing is selected, then no change will be made to Grant any Sensitive Android Permission to any Application.
If the value Access Notifications is selected, then the specified Application will be Granted the ability to monitor and potentially dismiss Android Notifications.
If the value Package Usage Stats is selected, then the specified Application will be Granted the ability to monitor and collect information about the activities of other Applications.
If the value System Alert Window is selected, then the specified Application will be Granted the ability to draw content on top of the display content of other Applications.
If the value Get AppOps Stats is selected, then the specified Application will be Granted the ability to collect statistics about other Applications.
If the value Battery Stats is selected, then the specified Application will be Granted the ability to collect device battery statistics.
If the value Manage External Storage is selected, then the specified Application will be Granted broad access to access external storage.
Detail Information:
Key = permissionAccessActionGrantPermission
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Access Notifications | android.permission.ACCESS_NOTIFICATIONS |
| Package Usage Stats | android.permission.PACKAGE_USAGE_STATS |
| System Alert Window | android.permission.SYSTEM_ALERT_WINDOW |
| Get AppOps Stats | android.permission.GET_APP_OPS_STATS |
| Battery Stats | android.permission.BATTERY_STATS |
| Manage External Storage | android.permission.MANAGE_EXTERNAL_STORAGE |
| Bind Notification Listener | [binary data] |
Support Information:
- Supported from: MX 10.4.
Grant Application Package
Enter the Android Package Name of an Application to which a Sensitive Android Permission should be Granted when the value Grant is selected for Permission Access Action. You must also specify Grant Application Signature to provide the information about the signing certificate used to sign valid versions of the Application.
Detail Information:
Key = permissionAccessActionGrantApplicationPackage
Type = string
Support Information:
- Supported from: MX 10.4.
Grant Application Signature
Enter the Android Package Signature that provides information about the signing certificate used to sign valid versions of an Application to which a Sensitive Android Permission should be Granted when the value Grant is selected for Permission Access Action and when Grant Application Package is specified.
Detail Information:
Key = permissionAccessActionGrantApplicationSignature
Type = string
Support Information:
- Supported from: MX 10.4.
Revoke Permission
Select the name of a Sensitive Android Permission to be Revoked from a specified Application when the value Revoke is selected for Permission Access Action. You must also specify Revoke Application Package and Revoke Application Signature to identify the Application.
If the value Do nothing is selected, then no change will be made to Revoke any Sensitive Android Permission from any Application.
If the value Access Notifications is selected, then the specified Application will have Revoked from it the ability to monitor and potentially dismiss Android Notifications.
If the value Package Usage Stats is selected, then the specified Application will have Revoked from it the ability to monitor and collect information about the activities of other Applications.
If the value System Alert Window is selected, then the specified Application will have Revoked from it the ability to draw content on top of the display content of other Applications.
If the value Get AppOps Stats is selected, then the specified Application will have Revoked from it the ability to collect statistics about other Applications.
If the value Battery Stats is selected, then the specified Application will be have Revoked from it the ability to collect device battery statistics.
If the value Manage External Storage is selected, then the specified Application will be have Revoked from it broad access to access external storage.
Detail Information:
Key = permissionAccessActionRevokePermission
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Access Notifications | android.permission.ACCESS_NOTIFICATIONS |
| Package Usage Stats | android.permission.PACKAGE_USAGE_STATS |
| System Alert Window | android.permission.SYSTEM_ALERT_WINDOW |
| Get AppOps Stats | android.permission.GET_APP_OPS_STATS |
| Battery Stats | android.permission.BATTERY_STATS |
| Manage External Storage | android.permission.MANAGE_EXTERNAL_STORAGE |
Support Information:
- Supported from: MX 10.4.
Revoke Application Package
Enter the Android Package Name of an Application from which a Sensitive Android Permission should be Revoked when the value Revoke is selected for Permission Access Action. You must also specify Revoke Application Signature to provide the information about the signing certificate used to sign valid versions of the Application.
Detail Information:
Key = permissionAccessActionRevokeApplicationPackage
Type = string
Support Information:
- Supported from: MX 10.4.
Revoke Application Signature
Enter the Android Package Signature that provides information about the signing certificate used to sign valid versions of an Application from which a Sensitive Android Permission should be Revoked when the value Revoke is selected for Permission Access Action and when Revoke Application Package is specified.
Detail Information:
Key = permissionAccessActionRevokeApplicationSignature
Type = string
Support Information:
- Supported from: MX 10.4.
Ask Permission
Select the name of a Sensitive Android Permission to which users will need to be Asked to Grant to a specified Application when the value Ask is selected for Permission Access Action. You must also specify Ask Application Package and Ask Application Signature to identify the Application.
If the value Do nothing is selected, then no change will be made to whether the device user will be Asked to Grant for any Sensitive Android Permission to any Application.
If the value Access Notifications is selected, then the specified Application will cause the device user to be Asked to Grant the ability to monitor and potentially dismiss Android Notifications.
If the value Package Usage Stats is selected, then the specified Application will cause the device user to be Asked to Grant the ability to monitor and collect information about the activities of other Applications.
If the value System Alert Window is selected, then the specified Application will cause the device user to be Asked to Grant the ability to draw content on top of the display content of other Applications.
If the value Get AppOps Stats is selected, then the specified Application will cause the device user to be Asked to Grant the ability to collect statistics about other Applications.
If the value Battery Stats is selected, then the specified Application will cause the device user to be Asked to Grant the ability to collect device battery statistics.
If the value Manage External Storage is selected, then the specified Application will cause the device user to be Asked to Grant broad access to access external storage.
Detail Information:
Key = permissionAccessActionAskPermission
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Access Notifications | android.permission.ACCESS_NOTIFICATIONS |
| Package Usage Stats | android.permission.PACKAGE_USAGE_STATS |
| System Alert Window | android.permission.SYSTEM_ALERT_WINDOW |
| Get AppOps Stats | android.permission.GET_APP_OPS_STATS |
| Battery Stats | android.permission.BATTERY_STATS |
| Manage External Storage | android.permission.MANAGE_EXTERNAL_STORAGE |
Support Information:
- Supported from: MX 10.4.
Ask Application Package
Enter the Android Package Name of an Application for which the device user will be Asked whether to Grant or Deny a Sensitive Android Permission when the value Ask is selected for Permission Access Action.
Detail Information:
Key = permissionAccessActionAskApplicationPackage
Type = string
Support Information:
- Supported from: MX 10.4.
Ask Application Signature
Enter the Android Package Signature that provides information about the signing certificate used to sign valid versions of an Application to which a the device user should be Asked to Grant a Sensitive Android Permission when the value Ask is selected for Permission Access Action and when Ask Application Package is specified.
Detail Information:
Key = permissionAccessActionAskApplicationSignature
Type = string
Support Information:
- Supported from: MX 10.4.
Power Configuration
Use this Sub-group to configure Power Action, Battery Percentage Decommission Threshold, Battery Usage Decommission Threshold, Battery Critical Low Threshold, Battery Optimization Action, Add Package Names, Remove Package Names, Port Action, Port Select, Auto Power Control, Auto Power Off, Timeout, Auto Power On, Heater Action, Heater Select, Off Threshold, On Threshold, All Wake-up Sources State, Battery Saver Control Mode, Battery Saver Control Mode Automatic Percentage Threshold, Battery Saver Mode, Doze Mode State, User Control of Battery Saver Mode, Wake-up Source Key Identifier, Custom, Wake-up Source to Activate the Display State, and Wake-up Method.
Detail Information:
Key = powerStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Power Action
Select an Action to control the Power to the device.
If the value Do nothing is selected, then no Action will be performed.
If the value Sleep is selected, the device will go to Sleep (i.e. enter Suspend Mode).
If the value Reboot is selected, the device will perform an OS Reboot (i.e. a simple Reset).
Detail Information:
Key = powerAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Sleep | 1 |
| Reboot | 4 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.1.
Battery Percentage Decommission Threshold
Enter the percentage of remaining battery capacity below which the battery will be deemed ready for decommissioning or leave blank (empty string) to leave unchanged.
Detail Information:
Key = powerBatteryThresholdPercentage
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Battery Usage Decommission Threshold
Enter the amount of battery usage (e.g. charge/discharge cycles, coulombs in/out, etc.) that can occur before the battery will be deemed ready for decommissioning or leave blank (empty string) to leave unchanged.
Detail Information:
Key = powerBatteryThresholdUsage
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.4.
Battery Critical Low Threshold
Enter the threshold battery level below which the battery is deemed to be critically low or leave blank (empty string) to leave unchanged.
- The Default Value is 4, which causes the battery to be deemed critically low when the battery level dips below 4% remaining capacity.
- If a value from 1 through 25 is entered, the battery will be deemed critically low when the battery level dips below the entered percentage of remaining capacity.
Detail Information:
Key = powerBatteryThresholdCriticalLow
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.3.
Battery Optimization Action
Select an Action to control which applications are subject to battery optimization and which are exempt.
If the value Do nothing is selected, then no Action will be performed to control which applications are subject to battery optimization and which are exempt.
If the value Add is selected, one or more applications will be made subject to battery optimizations and you must also specify Add Package Names to provide the Android Package Name(s) of the application(s) to be made subject to battery optimizations.
If the value Remove is selected, one or more applications will be made subject to battery optimizations and you must also specify Remove Package Names to provide the Android Package Name(s) of the application(s) to be exempted from battery optimizations.
Detail Information:
Key = powerBatteryOptimizationAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add | Add |
| Remove | Remove |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Add Package Names
Enter one or more Android Package Name(s) that identify application(s) that should be made subject to battery optimizations.
- If specified, multiple Android Package Names should be separated using commas.
Detail Information:
Key = powerBatteryOptimizationActionAddPackageNames
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Remove Package Names
Enter one or more Android Package Name(s) that identify application(s) that should be exempted from battery optimizations.
If specified, multiple Android Package Names should be separated using commas.
Detail Information:
Key = powerBatteryOptimizationActionRemovePackageNames
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.0.
Port Action
Select an Action to perform to control the Output Power various Ports on the device.
If the value Do not change is selected, then no Action will be performed to control the Output Power various Ports on the device.
If the value Turn Output Power OFF is selected, the Output Power for a specified Port will be turned off. You must also specify Port Select to provide the Port for which Output Power will be controlled.
If the value Turn Output Power ON is selected, the Output Power for a specified Port will be turned on. You must also specify Port Select to provide the Port for which Output Power will be controlled.
Detail Information:
Key = powerPortAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Output Power OFF | 2 |
| Turn Output Power ON | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Port Select
Select the Port that will be affected by an Action to control the Output Power on the device when Port Action is specified.
- If the value Serial Port 1 is selected, the Output Power will be turned on or off for the first device Serial Port.
- If the value Serial Port 2 is selected, the Output Power will be turned on or off for the second device Serial Port.
- If the value USB Port 2 is selected, the Output Power will be turned on or off for the second device USB Port.
Detail Information:
Key = powerPortSelect
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Serial Port 1 | Serial Port 1 |
| Serial Port 2 | Serial Port 2 |
| USB Port 2 | USB Port 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Auto Power Control
Select whether device power will be automatically controlled.
If the value Do not change is selected, then no change will be made to ether device power will be automatically controlled.
If the value Off is selected, the device power will NOT be automatically controlled.
If the value On is selected, the device power will be automatically controlled and you should must also specify one or more of the following:
Auto Power Off to specify whether/how device power will automatically be turned off.
Auto Power On to specify whether/how device power will automatically be turned on.
Detail Information:
Key = powerAutoPowerControl
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Auto Power Off
Select whether and how device power will be automatically turned off as part of automatic power control when On is specifed for Auto Power Control.
If the value Do not change is selected, then no change will be made to whether and how device power will be automatically turned off as part of automatic power control.
If the value Never is selected, the device power will NOT automatically turn off when the ignition turns off.
If the value When Ignition is Turned Off is selected, the device power will automatically turn off whenever the ignition turns off. You must also specify Timeout to provide the time to wait after the ignition turns off before device power is automatically turned off.
Detail Information:
Key = powerAutoPowerOff
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Timeout
Enter the timeout that will be in effect before device power is automatically turned off as part of automatic power control, when the value On is selected for Auto Power Control is specified and the value When Ignition is Turned Off is selected for Auto Power Off or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "powerAutoPowerOffTimeout" to "powerAutoPowerOffTimeoutString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = powerAutoPowerOffTimeoutString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Auto Power On
Select whether and how device power will be automatically turned on as part of automatic power control On is specifed for Auto Power Control.
If the value Do not change is selected, then no change will be made to whether and how device power will be automatically turned on as part of automatic power control.
If the value Never is selected, the device power will NOT automatically turn on when the ignition turns on.
If the value When Ignition is Turned On is selected, the device power will automatically turn on whenever the ignition turns on.
Detail Information:
Key = powerAutoPowerOn
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Never | 0 |
| When Ignition is Turned On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Heater Action
Select an Action to be performed to control device heaters.
If the value Do not change is selected, then no Action will be performed to control device heaters.
If the value Enable Heater is selected, the Heater will be be turned on and off as needed based on the configured ON/OFF thresholds. You must also specify Heater Select to identify the Heater to be affected.
If the value Disable Heater is selected, the Heater will turned off and will stay off, regardless of the configured ON/OFF thresholds. You must also specify Heater Select to identify the Heater to be affected.
If the value Set ON/OFF Thresholds is selected, the ON/OFF thresholds that will be used when the Heater is Enabled will be configured. You must also specify all of the following:
Heater Select to identify the Heater to be affected.
On Threshold to set the threshold temperature below which the Heater will automatically be turned on.
Off Threshold to set the threshold temperature above which the Heater will automatically be turned off.
Detail Information:
Key = powerHeaterAction
Type = string
Support Information:
Supported on Operating System(s): Oreo and Pie.
Supported on Device(s): VC80X and VC8300.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Support discontinued from: MX 9.0.
Heater Select
Select the Heater to be affected by a specified Heater Action when Heater Action is specified:
If the value Do not change is selected, then no Heater will be affected.
If the value Serial I/O is selected, the Heater that warms the Serial I/O Port of the device will be selected.
If the value USB I/O is selected, the Heater that warms the USB I/O Port of the device will be selected.
If the value Battery is selected, the Heater that warms the Battery of the device will be selected.
If the value Touch Panel is selected, the Heater that warms the Touch Panel of the device will be selected.
If the value Keyboard is selected, the Heater that warms the Keyboard of the device will be selected.
If the value Scanner Window is selected, the Heater that warms the Scanner Window of the device will be selected.
Detail Information:
Key = powerHeaterSelect
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Serial I/O | 1 |
| USB I/O | 2 |
| Battery | 3 |
| Touch Panel | 4 |
| Keyboard | 5 |
| Scanner Window | 6 |
Support Information:
Supported on Operating System(s): Oreo and Pie.
Supported on Device(s): VC80X and VC8300.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
Off Threshold
Select the temperature above which a specified Heater should automatically turn OFF, when the value below which the specified Heater should automatically turn on is selected for Heater Action or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "powerHeaterActionOffThreshold" to "powerHeaterActionOffThresholdString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = powerHeaterActionOffThresholdString
Type = string
Support Information:
Supported on Operating System(s): Oreo and Pie.
Supported on Device(s): VC80X and VC8300.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
On Threshold
Select the temperature below which a specified Heater should automatically turn ON, when the value below which the specified Heater should automatically turn on is selected for Heater Action or leave blank (empty string) to leave unchanged.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "powerHeaterActionOnThreshold" to "powerHeaterActionOnThresholdString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = powerHeaterActionOnThresholdString
Type = string
Support Information:
Supported on Operating System(s): Oreo and Pie.
Supported on Device(s): VC80X and VC8300.
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.1.
All Wake-up Sources State
Select whether all Wake-Up Sources will be enabled or not.
If the value Do not change is selected, then no change will be made to whether all Wake-Up Sources will be enabled or not.
If the value Off is selected, the device will not have all the wake-up sources enabled
If the value On is selected, the device will have all the wake-up sources enabled.
Detail Information:
Key = powerAllWakeupSourceState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.0.
Battery Saver Control Mode
Select how Battery Saver Mode will be activated (turned on) and deactivated (turned off) on the device.
If the value Do not change is selected, then no change will be made to how Battery Saver Mode will be activated (turned on) and deactivated (turned off) on the device.
If the value Automatically is selected, the device will activate (turn on) Battery Saver Mode automatically, and Battery Saver Control Mode Automatic Percentage Threshold must also be specified to provide the threshold battery level percentage below which the device will automatically activate Battery Saver Mode.
If the value Manually is selected, the device will NOT activate (turn on) Battery Saver Mode automatically, and will activate Battery Saver Mode only when specifically requested by the device user or by specifying the value Turn On for Battery Saver Mode. You should NOT specify Battery Saver Control Mode Automatic Percentage Threshold.
Detail Information:
Key = batterySaverControlMode
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Battery Saver Control Mode Automatic Percentage Threshold
Enter the battery level percentage below which Battery Saver Mode will automatically be activated (turned on) on the device when Automatically is specified for Battery Saver Control Mode.
Detail Information:
Key = batterySaverModePercentage
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Battery Saver Mode
Select whether Battery Saver Mode is active (turned on) or inactive (turned off) on the device when Manually is specified for Battery Saver Control Mode.
If the value Do not change is selected, then no change will be made to whether Battery Saver Mode is active (turned on) or inactive (turned off) on the device.
If the value Turn Off is selected, Battery Saver Mode will be deactivated (turned off) on the device.
If the value Turn On is selected, Battery Saver Mode will be activated (turned on) on the device.
Detail Information:
Key = batterySaverModeUsage
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Turn Off | 2 |
| Turn On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 10.1.
Doze Mode State
Select whether Doze Mode will be globally used on the device.
If the value Do not change is selected, then no change will be made to whether Doze Mode will be globally used on the device.
If the value Off is selected, the device will never enter Doze Mode for any applications.
If the value On is selected, the device will will enter Doze Mode for various applications based on the normal Android rules for Doze Mode.
Detail Information:
Key = powerDozeModeState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.2.
User Control of Battery Saver Mode
Select whether the device user will be allowed to control the State of Battery Saver Mode via UI on the device.
If the value Do not change is selected, then no change will be made to whether the device user will be allowed to control the State of Battery Saver Mode via UI on the device.
If the value Disable is selected, then the device user will NOT be allowed to control the State of Battery Saver Mode via UI on the device.
If the value Enable is selected, then the device user will be allowed to control the State of Battery Saver Mode via UI on the device.
Detail Information:
Key = batterySaverUserControlOfMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Disable | 2 |
| Enable | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 11.2.
Wake-up Source Key Identifier
Select the Key Identifier of the Wake-Up Source to control
If the value L1 Button is selected, the device will use the First (Topmost) Button located on the Left side of the device for Display Wake-Up
If the value L2 Button is selected, the device will use the Second (Down from the top) Button located on the Left side of the device for Display Wake-Up
If the value R1 Button is selected, the device will use the First (Topmost) Button located on the Right side of the device for Display Wake-Up
If the value R2 Button is selected, the device will use the Second (Down from the top) Button located on the Right side of the device for Display Wake-Up
If the value Grip (Gun) Trigger is selected, the device will use the Trigger on the Grip (Gun Handle) for Display Wake-Up
If the value Rear Button is selected, the device will use the Button located on the Rear of the device for Display Wake-Up
If the value Custom is selected, the device will use a Custom Button for Display Wake-Up and you must also specify Custom to identify it.
Detail Information:
Key = powerWakeupKeyId
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Custom
Enter the Custom name of the key identifier of the Wake-Up Source to control when Off or On is specified for Wake-up Source to Activate the Display State and when Custom is specified for Wake-up Source Key Identifier.
Detail Information:
Key = powerWakeupKeyIdCustom
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Wake-up Source to Activate the Display State
Select whether to turn on or off the ability of a specified Wake-up Source to activate the display.
If the value Do not change is selected, then no change will be made to whether to turn on or off the ability of a specified Wake-up Source to activate the display.
If the value Off is selected, the Wake-up Source identified by Wake-up Source Key Identifier will NOT activate the display.
If the value On is selected, the Wake-up Source identified by Wake-up Source Key Identifier will activate the display.
Detail Information:
Key = powerWakeupDisplayState
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | 2 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.3.
Wake-up Method
Select the Method that will be used to implement and control device Wake-up.
If the value Do not change is selected, then no change will be made to the Method that will be used to implement and control device Wake-up.
If the value Use Hardware Signals for Wake-Up is selected, the device will use hardware signals for wake-up
If the value Use Software (Mappable Keycodes) for Wake-Up is selected, the device will use software (mappable keycodes) for wake-up.
Detail Information:
Key = powerWakeupMethod
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Use Software (Mappable Keycodes) for Wake-Up | 2 |
| Use Hardware Signals for Wake-Up | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 9.2.
Remote Scanner Management
Use this Sub-group to configure Action, Config Serial Number, Config File, Update Serial Number, Update File, Reset Serial Number, Page Serial Number, Disconnect Serial Number, and Unpair Serial Number.
Detail Information:
Key = remotescannerStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 7.1.
Action
Select an Action to control a Remote Scanner that isconnected to a device.
- If the value Apply Configuration Package(RS6000 only) is selected, a configuration file will be used to apply new configuration to a Remote Scanner. You must also specify Config Serial Number to provide the Serial Number that identifies the Remote Scanner to be configured. You must also specify Config File to provide the path and file name of the configuration file to be applied.
- If the value Update Scanner Firmware is selected, a firmware file will be used to update the firmware of a Remote Scanner. You must also specify Update Serial Number to provide the Serial Number that identifies the Remote Scanner to be updated. You must also specify Update File to provide the path and file name of the firmware file to be applied.
- If the value Reset Scanner(RS6000 only) is selected, a Remote Scanner will be reset, allowing errors to be cleared and proper operation of aRemote Scanner to be restored. You must also specify Reset Serial Number to provide the Serial Number that identifies the Remote Scanner to be reset.
- If the value Page Scanner(RS6000 only) is selected, a Remote Scanner will be paged, allowing a misplaced Remote Scanner to be more easily located. You must also specify Page Serial Number to provide the Serial Number that identifies the Remote Scanner to be paged.
- If the value Disconnect Scanner(RS6000 only) is selected, a Remote Scanner will be disconnected, terminating the connection between the device and the Remote Scanner and preventing its subsequent use. You must also specify Disconnect Serial Number to provide the Serial Number that identifies the Remote Scanner to be disconnected.
- If the value Unpair Scanner(RS6000 only) is selected, a Remote Scanner will be unpaired, terminating the pairing between the device and the Remote Scanner and preventing its re-connection without first repairing. You must also specify Unpair Serial Number to provide the Serial Number that identifies the Remote Scanner to be unpaired.
Detail Information:
Key = remotescannerAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Apply Configuration Package(RS6000 only) | 1 |
| Update Scanner Firmware | 2 |
| Reset Scanner(RS6000 only) | 3 |
| Page Scanner(RS6000 only) | 4 |
| Disconnect Scanner(RS6000 only) | 5 |
| Unpair Scanner(RS6000 only) | 6 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.3.
Config Serial Number
Enter the Serial Number that identifies a Remote Scanner to which configuration should be applied when the value Apply Configuration Package(RS6000 only) is selected for Action. You must also specify Config File to provide the path and file name of the configuration file to be used.
Detail Information:
Key = remotescannerActionConfigSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
Config File
Enter the path and file name of a configuration file, which must exist at the specified location in the device file system, from which configuration should be applied to the specified Remote Scanner when the value Apply Configuration Package(RS6000 only) is selected for Action.
Detail Information:
Key = remotescannerActionConfigFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
Update Serial Number
Enter the Serial Number that identifies a Remote Scanner for which a firmware update should be performed when the value Update Scanner Firmware is selected for Action. You must also specify Update File to provide the path and file name of the firmware file to be used.
Detail Information:
Key = remotescannerActionUpdateSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Update File
Enter the path and file name of a firmware file, which must exist at the specified location in the device file system, from which firmware update should be performed to the specified Remote Scanner when the value Update Scanner Firmware is selected for Action.
Detail Information:
Key = remotescannerActionUpdateFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.2.
Reset Serial Number
Enter the Serial Number that identifies a Remote Scanner to be reset when the value Reset Scanner(RS6000 only) is selected for Action.
Detail Information:
Key = remotescannerActionResetSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
Page Serial Number
Enter the Serial Number that identifies a Remote Scanner to be paged when the value Page Scanner(RS6000 only) is selected for Action.
Detail Information:
Key = remotescannerActionPageSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
Disconnect Serial Number
Enter the Serial Number that identifies a Remote Scanner to be disconnected when the value Disconnect Scanner(RS6000 only) is selected for Action.
Detail Information:
Key = remotescannerActionDisconnectSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
Unpair Serial Number
Enter the Serial Number that identifies a Remote Scanner to be unpaired when the value Unpair Scanner(RS6000 only) is selected for Action.
Detail Information:
Key = remotescannerActionUnpairSerialNumber
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 5.2.
RFID Configuration
Use this Sub-group to configure Country of Operation, Channel Mask, Channel Hopping, Ukraine Region Power Mode, Action, Update Firmware File, Transmit Power Level, Query Select, Query Session, and Query Target.
Detail Information:
Key = rfidStep
Type = bundle
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Country of Operation
Select the Country of Operation in which the RFID module will be used.
It is critical that the Country of Operation be set at least once, since the RFID module has no default Country of Operation and will not operate unless/until the Country of Operation is explicitly set, to ensure that country-specific regulator requirements are met.
In most cases, the Country of Operation will be set once and never changed, unless the device is physically relocated to a different country.
In most cases, the Country of Operation will be set once and never changed, unless the device is physically relocated to a different country.
Detail Information:
Key = rfidCountryOfOperation
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| ALBANIA | 1 |
| ANDORRA | 2 |
| ARGENTINA | 3 |
| AUSTRALIA | 4 |
| BANGLADESH | 5 |
| BHUTAN | 6 |
| BOLIVIA | 7 |
| BOSNIA_HERZENGOVINA | 8 |
| BRAZIL | 9 |
| CANADA | 10 |
| CAMBODIA | 11 |
| CHILE | 12 |
| CHINA | 13 |
| COLOMBIA | 14 |
| DOMINICAN_REPUBLIC | 15 |
| ECUADOR | 16 |
| EL_SALVADOR | 17 |
| UNITED_KINGDOM | 18 |
| GUATEMALA | 19 |
| GUAM | 20 |
| HONG_KONG | 21 |
| INDIA | 22 |
| INDONESIA | 23 |
| JAPAN_1W_LBT | 24 |
| JAPAN_250MW | 25 |
| LAOS_EU | 26 |
| LAOS_FCC | 27 |
| MACAU | 28 |
| MACEDONIA | 29 |
| MALAYSIA | 30 |
| MEXICO | 31 |
| MONACO | 32 |
| MOTENEGRO | 33 |
| NEW_ZEALAND_FCC | 34 |
| NEW_ZEALAND_EU | 35 |
| PAKISTAN | 36 |
| PANAMA | 37 |
| PARAGUAY | 38 |
| PERU | 39 |
| PHILIPPINES | 40 |
| PUERTO_RICO | 41 |
| RUSSIA | 42 |
| SAUDI_ARABIA | 43 |
| SINGAPORE | 44 |
| SOUTH_AFRICA | 45 |
| SOUTH_KOREA | 46 |
| SRI_LANKA | 47 |
| TAIWAN | 48 |
| THAILAND | 49 |
| TURKEY | 50 |
| UAE | 51 |
| UNITED_STATES | 52 |
| URUGUAY | 53 |
| VENEZUELA | 54 |
| VIETNAM | 55 |
| VIRGINIA_ISLAND | 56 |
| ETSI 302.208 compliant generic | 57 |
| FCC Part-16 compliant generic | 58 |
| ISRAEL | 59 |
| ALGERIA | 60 |
| ARMENIA | 61 |
| AUSTRIA | 62 |
| AZERBAIJAN | 63 |
| BAHRAIN | 64 |
| BELGIUM | 65 |
| BULGARIA | 66 |
| COSTA_RICA | 67 |
| CROATIA | 68 |
| CYPRUS | 69 |
| CZECH_REPUBLIC | 70 |
| DENMARK | 71 |
| EGYPT | 72 |
| ESTONIA | 73 |
| FINLAND | 74 |
| FRANCE | 75 |
| GEORGIA | 76 |
| GERMANY | 77 |
| GREECE | 78 |
| HUNGARY | 79 |
| ICELAND | 80 |
| IRELAND | 81 |
| ITALY | 82 |
| JORDAN | 83 |
| KAZAKHSTAN | 84 |
| KUWAIT | 85 |
| LATVIA | 86 |
| LITHUANIA | 87 |
| LUXEMBOURG | 88 |
| MALTA | 89 |
| NETHERLANDS | 90 |
| NORWAY | 91 |
| OMAN | 92 |
| POLAND | 93 |
| PORTUGAL | 94 |
| QATAR | 95 |
| ROMANIA | 96 |
| SERBIA | 97 |
| SLOVAKIA | 98 |
| SLOVENIA | 99 |
| SPAIN | 100 |
| SWEDEN | 101 |
| SWITZERLAND | 102 |
| TUNISIA | 103 |
| UKRAINE | 104 |
| ANGUILLA | 106 |
| MOROCCO | 107 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Channel Mask
Enter the Channel Mask that determines which of the Channels that are allowed, based on the currently selected Country of Operation will be used by the RFID module.
- If no Channel Mask is specified, the RFID module will be free to use any or all Channels that are available based on the currently selected Country of Operation.
- If a Channel Mask is specified, the specified value must consist of one or more Channel Numbers, separated by commas if more than one is specified, which identify the Channels that can be used. The RFID module will limit itself to just the Channels that are allowed for the currently selected Country of Operation AND that are in the set of Channels specified.
Consult the product documentation for the device being used to obtain the set of allowable Channel Numbers.
Detail Information:
Key = rfidCountryOfOperationChannelMask
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Channel Hopping
Select whether Channel Hopping will be performed among the Channels that are used by the RFID module for the country specified via Country of Operation.
If the value Do nothing is selected, the country specified via Country of Operation will NOT be set because it is mandatory to specify whether Channel Hopping will be used for a country when setting the country.
If the value Off is selected, Channel Hopping will NOT be performed between supported Channels for the selected Country.
If the value On is selected, Channel Hopping WILL be performed between supported Channels for the selected Country.
Detail Information:
Key = rfidCountryOfOperationChannelHopping
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Off | 0 |
| On | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Ukraine Region Power Mode
Select the Ukraine Region specific power mode to be used by the RFID module.
Detail Information:
Key = rfidCountryOfOperationUkraineRegionPowerMode
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| License free 100MW power-mode | 0 |
| Licensed 2W power-mode | 1 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Action
Select an Action to alter the behavior or configuration of the RFID module.
If the value Update Firmware is selected, the firmware of the RFID module will be updated and you must also specify Update Firmware File to provide the path and file name of the file, which must exist in the device file system, containing the firmware update to be applied to the RFID module.
If the value Export Settings is selected, the current configuration of the RFID module will be exported and stored in a file in the device file system. This file could then be extracted from the device and used for troubleshooting potential configuration issues related to the RFID module.
If the value Reset Radio is selected, the radio of the RFID module will be reset, without changing its settings. This could be used to recover from an error or other failure of the RFID module.
If the value Reset Radio to Factory Defaults is selected, the configuration of the RFID module will be returned to its default out-of-box state and the radio will be reset. This could be used to recover from a serious configuration error that prevents the RFID module from functioning appropriately.
Detail Information:
Key = rfidAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Update Firmware | |
| Export Settings | 2 |
| Reset Radio | 4 |
| Reset Radio to Factory Defaults | 5 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Update Firmware File
Enter the path and file name of the file containing the firmware update to be applied when the value Update Firmware or the value Update Firmware and Reset Radio to Factory Defaults is selected for Action.
Detail Information:
Key = rfidActionUpdateFirmwareFile
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Transmit Power Level
Enter the power level to be used when the RFID module radio is transmitting or leave blank (empty string) to leave unchanged.
The value entered should be an integer value in tenths of dBm in the range of 0 to 300, inclusive or leave blank (empty string) to leave unchanged. For example, to specify an RFID Power Level of 29.5 dBm, specify a value of 295.
Note that the data type of this MC has changed from integer to string, in order to add the ability to specify a blank (empty) string value to indicate "Do not change" and thereby better support EMMs, especially those that use the Google iFrame, and that may need to send a value even if one is not specified. Since the type changed, the key name also had to change, from "rfidTransmitPowerLevel" to "rfidTransmitPowerLevelString". As a result of the name and type change, when upgrading to this new version of OemConfig, any configurations that were previously created and saved using an older version of OemConfig, and that included a value for this MC, will need to be edited to supply a comparable value for the key with the new name.
Detail Information:
Key = rfidTransmitPowerLevelString
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Query Select
Select which RFID tags should be operated upon by the RFID module during a Query Operation, based on the state of the SL flag.
If the value Do not change is selected, then no change will be made to which RFID tags should be operated upon by the RFID module during a Query Operation, based on the state of the SL flag.
If the value Query applies to all tags is selected, when the RFID module performs a Query Operation, it will consider all RFID tags that are currently visible to the RFID module.
If the value Query applies to tags with SL de-asserted is selected, when the RFID module performs a Query Operation, it will consider only those RFID tags that are currently visible to the RFID module AND that have SL flag de-asserted (i.e tags for which the SL flag has NOT been set using the Select command).
If the value Query applies to tags with SL asserted is selected, when the RFID module performs a Query Operation, it will consider only those RFID tags that are currently visible to the RFID module AND that have SL flag asserted (i.e tags for which the SL flag HAS been set using the Select command).
Detail Information:
Key = rfidQuerySelect
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Query applies to all tags | 0 |
| Query applies to tags with SL de-asserted | 2 |
| Query applies to tags with SL asserted | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Query Session
Select which Session should be used by the RFID module to access RFID tags during a Query Operation.
If the value Do not change is selected, then no change will be made to which Session should be used by the RFID module to access RFID tags during a Query Operation.
If the value SessionS0 is selected, SessionS0 will be used by the RFID module to access RFID tags during a Query Operation.
If the value SessionS1 is selected, SessionS1 will be used by the RFID module to access RFID tags during a Query Operation.
If the value SessionS2 is selected, SessionS2 will be used by the RFID module to access RFID tags during a Query Operation.
If the value SessionS3 is selected, SessionS3 will be used by the RFID module to access RFID tags during a Query Operation.
Sessions provide options for how to count tags. For more information on the use of Sessions, consult the device product documentation.
Detail Information:
Key = rfidQuerySession
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| SessionS0 | 0 |
| SessionS1 | 1 |
| SessionS2 | 2 |
| SessionS3 | 3 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Query Target
Select how the A and B flags of RFID tags should be handled by the RFID module during a Query Operation.
If the value Do not change is selected, then no change will be made to how the A and B flags of RFID tags should be handled by the RFID module during a Query Operation.
If the value Inventory Target Flag A is selected, when the RFID module performs a Query Operation, it will consider only those RFID tags that are currently visible to the RFID module AND that are in State A.
If the value Inventory Target Flag B is selected, when the RFID module performs a Query Operation, it will consider only those RFID tags that are currently visible to the RFID module AND that are in State B.
If the value AB Flip is selected, when the RFID module performs a Query Operation, it will consider only those RFID tags that are currently visible to the RFID module AND that are in either State A or State B and will Flip the State from A to B or B to A for the session.
Detail Information:
Key = rfidQueryTarget
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Inventory Target Flag A | 0 |
| Inventory Target Flag B | 1 |
| AB Flip | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 8.1.
Security Configuration
Use this Sub-group to configure Action, Add Key Name, Add Key Value, Remove Key Name, Encrypt SD Card Key Name, Instant Screen Lock on Power Key, Screen Lock Type, and Screen Lock Timeout.
Detail Information:
Key = securityStep
Type = bundle
Action
Select an Action to adjust various security features on a device.
- If the value Add Key is selected, you must also specify Add Key Name to provide the name of the key to be added and you must also specify Add Key Value to provide the value of the key to be added.
- If the value Remove Key is selected, you must also specify Remove Key Name to provide the name of the key to be removed.
- If the value Remove All Keys is selected, you do not need to specify any additional information. Not supported on devices running Android 11 or later.
- If the value Encrypt SD Card is selected, you must also specify Encrypt SD Card Key Name to provide the name of the key to be used to encrypt the SD Card.
- If the value Wipe SD Card is selected, you do not need to specify any additional information.
Detail Information:
Key = securityAction
Type = string
| UI Choice | JSON Value |
|---|---|
| Do nothing | |
| Add Key | AddKey |
| Remove Key | RemoveKey |
| Remove All Keys | RemoveAllKeys |
| Encrypt SD Card | EncryptSdCard |
| Wipe SD Card | WipeSdCard |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Add Key Name
Enter the name of a key to be added when the Action value Add Key is selected for Action.
You must also specify Add Key Value to provide the value to be added for the specified key name.
Detail Information:
Key = securityActionAddKeyName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Add Key Value
Enter the value of a key to be added when the Action value Add Key is selected for Action.
You must also specify Add Key Name to provide the key name for which this value should be added.
A key value must be a string value containing exactly 64 hexadecimal characters ("0-9" and/or "A-F" characters) that encode a 256 bit binary value for an AES encryption key.
The key value can be generated in any manner desired as long as it is a 256 bit binary value and is represented as 64 hexadecimal characters, although in most cases, best practice would be to randomly generate keys to maximize their effectiveness in protecting data.
Detail Information:
Key = securityActionAddKeyValue
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Remove Key Name
Enter the name of a key to be removed when the Action value Remove Key is selected for Action.
Detail Information:
Key = securityActionRemoveKeyName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Encrypt SD Card Key Name
Enter the name of a key to be used to encrypt the SD Card when the Action value Encrypt SD Card is selected for Action.
Detail Information:
Key = securityEncryptSDCardKeyName
Type = string
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Instant Screen Lock on Power Key
Select what happens when the Power Key on the device is used to turn the device off, especially whether the device will be locked, requiring it to be unlocked by entering a PIN or password, if one is specified.
If the value Do not change is selected, then no change will be made to happens when the Power Key on the device is used to turn the device off.
If the value Off is selected, turning the device off using the Power Key will be handled the same as when the device times out and turns itself off automatically. In such a case, if device remains off for longer than value set via Screen Lock Timeout, when it is turned back on, the device will be locked, requiring whatever unlock action is set via Screen Lock Type.
If the value On is selected, turning the device off using the Power Key will be handled differently than when the device times out and turns itself off automatically, specifically the device will become locked immediately when the device is turned off using the Power Key. In such a case, no matter how long the device remains off, when it is turned back on, the device will be locked, requiring whatever unlock action is set via Screen Lock Type.
Detail Information:
Key = securityPowerKeyInstantLock
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Off | Off |
| On | On |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 4.3.
Screen Lock Type
Select the type of lock that is used to protect the device from use by unauthorized persons.
If the value Do not change is selected, no change will be made to the type of lock that is used to protect the device from use by unauthorized persons.
If the value None is selected, no lock will be applied and the device can be used by anyone.
If the value Swipe is selected, unlocking will require only a simple swipe and the device can be used by anyone.
If the value PIN is selected, unlocking will require entry of a PIN (personal identification number) and the device can only be unlocked by someone knowing the correct PIN value.
If the value Password is selected, unlocking will require entry of a password and the device can only be unlocked by someone knowing the correct password value.
If the value Pattern is selected, unlocking will require drawing a pattern on the screen using the touch panel and the device can only be unlocked by someone knowing the correct pattern.
Detail Information:
Key = securityScreenLockType
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| None | 5 |
| Swipe | 1 |
| PIN | 3 |
| Password | 4 |
| Pattern | 2 |
Support Information:
NOT supported on Device(s): TC20 and TC25.
Supported from: MX 6.0.
Screen Lock Timeout
Select what happens when a device turns off as a result of a timeout.
If the value Do not change is selected, then no change will be made to what happens when a device turns off as a result of a timeout.
If the value Immediately after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 0 (immediately).
If the value 5 seconds after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 5 seconds.
If the value 15 seconds after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 15 seconds.
If the value 30 seconds after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 30 seconds.
If the value 1 minute after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 1 minute
If the value 2 minutes after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 2 minutes.
If the value 5 minutes after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 5 minutes.
If the value 10 minutes after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 10 minutes.
If the value 30 minutes after Display Timeout is selected, then the time after timeout before the device will need to be unlocked will be set to 30 minutes.
Notes:
- If the device stays off for at least the time specified, the device will be locked and an unlock will be required when the device is turned back on, if any lock was configured using Screen Lock Type.
- If the device stays off for less than the time specified, the device will NOT be locked and hence no unlock will be required when the device is turned back on, even if a lock was configured using Screen Lock Type.
Detail Information:
Key = securityScreenLockTimeout
Type = string
| UI Choice | JSON Value |
|---|---|
| Do not change | |
| Immediately after Display Timeout | 1 |
| 5 seconds after Display Timeout | 5 |
| 15 seconds after Display Timeout | 15 |
| 30 seconds after Display Timeout | 30 |
| 1 minute after Display Timeout | 60 |
| 2 minutes after Display Timeout | 120 |
| 5 minutes after Display Timeout | 300 |
| 10 minutes after Display Timeout | 600 |
| 30 minutes after Display Timeout | 1800 |