OEMConfig Powered by MX 14.2.0.1 Release Notes

Highlights

• Adds support for MX 14.2 features

Device Support

• Supports all Zebra devices running Android 11 and later

Important Note for devices running Android 13 and later

Due to new mandatory privacy requirements from Google, the Setup Wizard Bypass feature has been discontinued on devices running Android 13 and later. Consequently, it is no longer possible to skip the Setup Wizard screen, and the StageNow barcode will not function during the Setup Wizard. For more details, please refer to the Zebra FAQ documentation: Zebra FAQ documentation.

New in OEMConfig 14.2.0.1

Note: MX 14.2 is supported only on devices running Android 11 or later.

Supports MX 14.2, which adds the following major features and enhancements:

• Access Manager: Adds to Access Permissions the ability to use Android "exact alarm" APIs and to read (and optionally write) Android systems settings.
• Audio Volume UI Manager: Adds the ability to: Enable/Disable Mute state control by the device user. Enable/Disable Vibrate state control by the device user.
• Bluetooth Manager: Adds the ability to: Set individual Bluetooth Profiles as active or inactive.
• KeyMapping Manager: Adds the ability to: Channel Switch and Alert Button Key Identifiers in Zebra's new device designed for First Responders.
• DevAdmin: Adds the ability to: Add a Secondary Keyguard to work in addition to the Android lock screen. Automatically reboot after installation of a Secondary Keyguard.
• UI Manager: Adds the ability to: Change default behavior of the Wearable Status Bar on select Zebra wearable devices.
• Wi-Fi: Adds the ability to: Turn On/Off Wi-Fi Casting, which allows the device to "broadcast" the contents of its screen via Wi-Fi Direct connection. Control Wi-Fi Direct PIN, which can force the device user to enter a PIN when initiating a WiFi Direct connection with another device (default = no PIN).
• Wireless Manager: Adds the ability to: Select "pass-through antenna" settings on the device when used with external antenna(s).

Resolved Issues

• [SPR-55773] 42Gears is now able to disable the Data Limit on TC26 devices through OEMConfig.
• [SPR-56205] Keyboard mappings are now being applied correctly through OEMConfig.
• [SPR-56257] OEMConfig "File already present" no longer causes EMMs to report failure.

Usage Notes

• OEMConfig Powered by MX 14.2.0.1 (com.zebra.oemconfig.release) is now available on Google Play.
• EMM developers, in partnership with Google, must download the OEMConfig app from Google Play to extract the OEMConfig application restrictions (schema) for Zebra devices.
• OEMConfig is built with Android API level 34.
• OEMConfig can be tested using the following broadcast intent: adb shell am broadcast -a com.android.vending.APPLICATION_RESTRICTIONS_CHANGED -n com.zebra.oemconfig.release/.BootCompleteReceiver

Important Links

• OEMConfig documentation
• MX documentation

Known Issues

• Batch, Condition Manager, and Persist Manager are not supported with the XML pass-through feature.
• TUT-110892 - Manual intervention is needed to install ZWC apk in the personal profile since the required BSPA intent is not received by WORK ZWC.

About OEMConfig

Zebra OEMConfig is an administrative tool for configuring Zebra Android devices using Android Managed Configurations, developed by Google and the Android community. To configure a feature for which no Android Enterprise API is available, using Managed Configurations is the only available method based on publicly available specifications. OEMConfig interfaces with Zebra's Mobility Extensions Management System (known simply as MX), a non-XML, non-proprietary communication framework for managing the capabilities and behaviors of Zebra devices running Android.

Over time, many of the capabilities available only through proprietary mechanisms such as MX have been added by the Android development community. Starting as "Android for Work," these capabilities are now available as "Android Enterprise" APIs or Android Managed Configurations, both of which are based on publicly available specifications. Zebra is adopting both as part of the natural evolution of its device management system.

OEMConfig provides a single interface for managing Zebra Android devices regardless of the underlying APIs required to get the job done. OEMConfig works through Android Enterprise APIs when possible and uses Managed Configurations when no Android Enterprise API is available. OEMConfig and the Zebra schema are available from Google Play and must be used together to configure Zebra Android devices. The Schema defines the functions available for configuration and provides the data necessary to present the corresponding data-driven UI for configuring those functions. This mechanism allows Zebra to make a new Schema available as soon as new features are developed.