The "SmartDocs" bar can customize this page to show only the features present on a particular Zebra device.
OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. More info.
The Device Administrator CSP (DevAdmin) controls which apps have administrative privileges, can access Android Device Admin APIs and how, when and whether the Screen-Lock is invoked.
Android defines some APIs as Device Administration APIs, as implemented within the DevicePolicyManager class. These APIs enable applications to perform tasks that can affect the security of the device. As such, they are restricted to specially approved "Device Administrator" applications. If an application is written to conform to the DeviceAdminReceiver model and is approved to become a Device Administrator, then it can use some or all of the Device Administration APIs.
In standard Android devices, an application that is written to conform to the DeviceAdminReceiver model must explicitly request the device user to approve it as a Device Administrator. This is based on the assumption that the device user is knowledgeable enough to make this determination. For a device that is owned and/or used by a single user, that assumption might be reasonable. For an Enterprise-owned device that might be shared among multiple device users, that assumption may be a poor one.
The DevAdmin provides direct access to certain device administration tasks and allows programmatic approval as a Device Administrator of applications written to conform to the DeviceAdminReceiver model without involving or notifying the device user. This allows an Enterprise to grant its own trusted applications access to the Device Administration APIs, thus enabling those applications to perform device administration tasks.
Used to grant or deny approval as a Device Administrator from a qualifying application. To qualify, the app must be written to conform to the DeviceAdminReceiver model. All applications by default are initially denied approval as a Device Administrator and must be explicitly approved. Only an application that is currently installed and written to conform to the DeviceAdminReceiver model may be approved as a Device Administrator.
When an application is approved as a Device Administrator, it will be notified that it can begin using the Device Administration APIs. When Device Administrator approval is removed, the app is likewise notified that it must stop using the Device Administration APIs.
NOTE: The ability to grant or deny approval for an application using the DevAdmin does not prevent the device user from doing the same for an application using the System Settings panel. The effect of this parameter is the same as that of a device user going though System Settings. Access to the System Settings panel can be controlled with the UI Manager.
Parm Name: DevAdminAction
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do nothing | This value (or the absence of this parm from the XML) will not make any change to whether any application is approved to be a Device Administrator; any previously selected setting will be retained. |
OSX: 1.3+ MX: 4.3+ |
||
| 1 | Turn On as Device Administrator | Approves a specific application as a Device Administrator. |
OSX: 1.3+ MX: 4.3+ |
||
| 2 | Turn Off as Device Administrator | Removes Device Administrator approval from a specific application. |
OSX: 1.3+ MX: 4.3+ |
Used to enter the Package Name of an application to which to grant or deny Device Administrator privileges.
NOTE: The Package Name of the application must be known and specified. The Package Name can be acquired from the application developer, by looking up the Package Name on a device, or using developer tools to extract the Package Name from the APK file.
Parm value input rules:
Shown if: Device Administration Action is "Turn On as Device Administrator" or "Turn Off as Device Administrator"
Parm Name: DevAdminPkg
Requires:
- OSX: 1.3+
- MX: 4.3+
Used to enter the Class Name that will be added to or removed from the Device Admin list, which determines whether the application can access Android Device Admin APIs.
NOTE: The name of the class within the application that implements the DeviceAdminReceiver must be known and specified. This is not the same as the Activity class name required to launch the application and would likely need to be acquired from the application developer.
Parm value input rules:
Shown if: Device Administration Action is "Turn On as Device Administrator" or "Turn Off as Device Administrator"
Parm Name: DevAdminClass
Requires:
- OSX: 1.3+
- MX: 4.3+
Controls whether apps can be installed (on devices with or without GMS) by the device user from sources other than Google Play. Off by default (option 2) on Zebra devices with GMS; On by default on non-GMS devices.
IMPORTANT: On non-GMS devices, disabling apps from Unknown Sources (option 2) prevents only the device user from installing apps on the device. It does NOT prevent apps from being installed through the App Manager or other programmatic means.
Note: Not supported on devices running Android 8.x Oreo or higher.
Status: Deprecated. This feature will be discontinued in devices running Android 13 and later.
Parm Name: UnknownSourcesStatus
Used to determine the wallpaper displayed on the Lock screen. When selecting a Custom wallpaper (option 2), identify the wallpaper file on the device using the Custom Wallpaper parameter.
Parm Name: LockScreenWallpaper
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do not change | This value (or the absence of this parm from the XML) makes no change to device settings; any previously selected setting is retained. |
MX: 10.5+ |
||
| 1 | Restore to default | Restores the Lock Screen wallpaper to its factory-default setting. |
MX: 10.5+ |
||
| 2 | Custom | Allows a custom wallpaper image to be selected for display on the Lock Screen. |
MX: 10.5+ |
Used to enter the file name and path on the device of an image file (.jpg or .png, 126 MB max.) for display when the Lock Screen is shown on the device.
Parm value input rules:
.jpg or .png file formatsNote: Supported only on devices running Android 10 or later. Android 11 requires MX 11.3 or later.
Shown if: Lock Screen Wallpaper is "Custom"
Parm Name: CustomLockWallpaper
Requires:
- MX: 10.5+
Used to select the type of notification content to be shown on the Lock Screen, if any.
WARNING: Displaying notifications of any kind on the Lock Screen could expose confidential data to users who lack credentials to unlock the device.
Note: Supported only on devices running Android 10 or later. Android 11 requires MX 11.3 or later.
Parm Name: NotificationOnLockScreen
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do not change | This value (or the absence of this parm from the XML) makes no change to device settings; any previously selected setting is retained. |
MX: 10.5+ |
||
| 1 | Show all content | Allows all notifications sent to the device or its user to be displayed on the device Lock Screen. |
MX: 10.5+ |
||
| 2 | Show only non-sensitive content | Allows all notifications except those deemed 'sensitive' by Android to be displayed on the device Lock Screen. |
MX: 10.5+ |
||
| 3 | Hide notifications | Blocks all notifications from being displayed on the device Lock Screen. |
MX: 10.5+ |
Controls whether a screen lock will be invoked when the device powers up or user inactivity exceeds the Screen-Lock Timeout Interval parameter, and which Android Lock Screen will be displayed.
ENTERPRISE HOME SCREEN NOTE: Installation of Zebra EHS by default disables the Android Settings panel on devices, which causes any execution of this parameter to fail. To use this parameter on devices intended to run EHS, Zebra recommends setting the ScreenLockType before EHS is installed on target device(s). To set the ScreenLockType on devices already running EHS, enable EHS Privileged Settings on the device(s) to temporarily activate the Settings app, set the ScreenLockType as desired, then disable Privileged Settings to re-secure the device.
Note: On TC20/TC25 devices, available only when running Android 8.x Oreo and later.
Parm Name: ScreenLockType
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do not change | This value (or the absence of this parm from the XML) will cause no change to the Screen Lock Type; any previously selected setting will be retained. |
OSX: 6.0+ MX: 6.0+ |
||
| 1 | Swipe | Causes the Swipe screen-lock to be displayed whenever the Lock Screen is invoked. |
OSX: 6.0+ MX: 6.0+ |
||
| 2 | Pattern | Causes the Pattern screen-lock to be displayed whenever the Lock Screen is invoked. |
OSX: 6.0+ MX: 6.0+ |
||
| 3 | Pin | Causes the numerical "Pin" screen-lock to be displayed whenever the Lock Screen is invoked. |
OSX: 6.0+ MX: 6.0+ |
||
| 4 | Password | Causes the Password screen-lock to be displayed whenever the Lock Screen is invoked. |
OSX: 6.0+ MX: 6.0+ |
||
| 5 | None | Prevents the display of any Lock Screen at any time. |
OSX: 6.0+ MX: 6.0+ |
Controls the length of time a device must remain inactive with the display screen off before a screen-lock is invoked.
Android supports two levels of inactivity, each controlled independently. The Display Screen Timeout, administered by the Display Manager, controls the length of time a device must remain inactive before the display screen is turned off. The Screen Lock Timeout interval (this parameter), controls how long the screen must remain off before a screen-lock will be invoked.
When the device screen is turned back on, manually by some sort of device user activity, or programmatically due to some device event, the result will depend on how long the device screen was off and the value set for the Screen Lock Timeout. If the display screen was off for less than the Screen Lock Timeout, then the screen will not be locked (and hence will not need to be unlocked by the device user). If the display screen was off for at least the Screen Lock Timeout, then the screen will be locked (and hence will need to be unlocked by the device user).
This behavior can be modified in two ways, based on other aspects of the device that may be configured. First, if no lock behavior is set for the device (e.g. no pin or password), then "unlocking" (if required) may require only a swipe, and not any actual data entry by the device user. Second, if the device is configured to lock automatically when the display screen is turned off by the power key, then a screen lock will always occur when the display screen is turned back on after being turned off via the power key, regardless of how much time the display screen was off.
NOTE: The Android display system supports a fixed set of interval values for the Screen-Lock Timeout as listed in the table below. This parameter is capable of configuring the timeout using only those supported values. Entering a value that is less than the smallest value shown in the table or greater than the largest value will be ignored and generate an error in the Result XML document. However, entering a value between two supported values will cause the closest value to the requested value to be selected, and generate no error in the Result XML document.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android Device Policy Manager (DPM) APIs.
Parm Name: ScreenLockTimeoutInterval
Controls whether the "YES" button is available for selection by a device user on the "Secure Start-up" dialog box after changing the device lock-screen password, PIN or swipe pattern in the Android Settings panel. If "YES" is pressed, the same password, PIN or pattern that protects access to the Android Launcher app also would be applied to protect the device start-up process, preventing the device from booting if restarted.
IMPORTANT: If the device is rebooted with this feature enabled, the device remains unmanaged and inoperable until the password, PIN or pattern is entered and the start-up process is allowed to complete.
Parm Name: SecureStartupSelection
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do not change | This value (or the absence of this parm from the XML) makes no change to device settings; any previously selected setting is retained. |
OSX: 6.2+ MX: 10.0+ Android API: 26+ |
||
| 1 | Enable | Allows the user to select "YES" when prompted to protect the device boot process. |
OSX: 6.2+ MX: 10.0+ Android API: 26+ |
||
| 2 | Disable | Disables "YES" button, preventing device user from electing to protect the device boot process. |
OSX: 6.2+ MX: 10.0+ Android API: 26+ |
Used to select whether the device user receives notifications when the Device Owner installs, uninstalls or upgrades apps.
Parm Name: SilentAppInstall
| Option | Name | Description | Note | Status | Requires |
|---|---|---|---|---|---|
| 0 | Do not change | This value (or the absence of this parm from the XML) causes no change to device settings; any previously selected setting is retained. |
OSX: 11.5+ MX: 10.5+ Android API: 30+ |
||
| 1 | Show | Allows notifications to be displayed on the device when the DO installs, uninstalls or upgrades an app. |
OSX: 11.5+ MX: 10.5+ Android API: 30+ |
||
| 2 | Hide | Prevents notifications from being displayed on the device when the DO installs, uninstalls or upgrades an app. |
OSX: 11.5+ MX: 10.5+ Android API: 30+ |
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3" >
<parm name="ScreenLockTimeoutInterval" value="60"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3" >
<parm name="UnknownSourcesStatus" value="1"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3" >
<characteristic-query type="AppAsDevAdmin"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3" >
<characteristic type="AppAsDevAdmin">
<parm name="DevAdminAction" value="1"/>
<characteristic type="DevAdminDetails">
<parm name="DevAdminPkg" value="PackageName1"/>
<parm name="DevAdminClass" value="ClassName1"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="DevAdmin" version="4.3" >
<characteristic type="AppAsDevAdmin">
<parm name="DevAdminAction" value="1"/>
<characteristic type="DevAdminDetails">
<parm name="DevAdminPkg" value="PackageName2"/>
<parm name="DevAdminClass" value="ClassName2"/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin">
<parm-query name="ScreenLockTimeoutInterval"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3">
<parm name="ScreenLockTimeoutInterval" value="1"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin">
<parm-query name="UnknownSourcesStatus"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="DevAdmin" version="4.3">
<parm name="UnknownSourcesStatus" value="1"/>
</characteristic>
</wap-provisioningdoc>