Legacy Zebra OEMConfig
Manage Zebra's custom MX features & settings through your EMM/UEM.
Zebra Technologies · com.zebra.oemconfig.common
UpdatedDec 30, 2025
PublishedApr 22, 2021
Packagecom.zebra.oemconfig.common
MD5f51434bae3a98489bd6e2268aad3c25e
SHA1 (signer)D9:13:80:AE:9C:9C:D3:AB:42:9C:36:7B:E4:80:10:85:88:7E:C2:89
Signed byCN=Enterprise Mobile Application, OU=Enterprise Mobile Computing, O=Zebra Technologies, L=Holtsville, ST=New York, C=US
Malware scanTRUSTED
Websitehttps://www.zebra.com
Contact[email protected]
Privacy policyView
What's new
Fix for Schema for 'steps' has type "TYPE_BUNDLE_ARRAY" but the Bundle element type is not Parcelable[]
Description
This original version of Zebra OEMConfig (com.zebra.oemconfig.common) is now marked "Legacy" to indicate its replacement by Zebra OEMConfig (com.zebra.oemconfig.release), in which Zebra delivers numerous organization and navigation enhancements, and which implements an all-new schema designed according to changes mandated by Google.
While both versions can target Zebra devices running Android 11, the new version CANNOT target devices with versions PRIOR to Android 11. Organizations with devices running Android 11 and OLDER can continue to use the Legacy version indefinitely. HOWEVER, targeting devices running Android 13 or later can ONLY be done using "Zebra OEMConfig Powered by MX," the "non-legacy" version of OEMConfig. Companies with mixed device populations running Android versions older AND newer than Android 11 MUST USE BOTH versions of Zebra OEMConfig.
For more information on how to use Zebra’s OEMConfig, please review our Admin Guide
The administrator guide can be found at: http://techdocs.zebra.com/oemconfig
While both versions can target Zebra devices running Android 11, the new version CANNOT target devices with versions PRIOR to Android 11. Organizations with devices running Android 11 and OLDER can continue to use the Legacy version indefinitely. HOWEVER, targeting devices running Android 13 or later can ONLY be done using "Zebra OEMConfig Powered by MX," the "non-legacy" version of OEMConfig. Companies with mixed device populations running Android versions older AND newer than Android 11 MUST USE BOTH versions of Zebra OEMConfig.
For more information on how to use Zebra’s OEMConfig, please review our Admin Guide
The administrator guide can be found at: http://techdocs.zebra.com/oemconfig
Required features
- Faketouch android.hardware.faketouch
Permissions (9)
Legacy Zebra OEMConfig requests the following Android permissions:
- Access Network State android.permission.ACCESS_NETWORK_STATE
- Foreground Service android.permission.FOREGROUND_SERVICE
- Read External Storage android.permission.READ_EXTERNAL_STORAGE
- Receive Boot Completed android.permission.RECEIVE_BOOT_COMPLETED
- Wake Lock android.permission.WAKE_LOCK
- Write External Storage android.permission.WRITE_EXTERNAL_STORAGE
- Com Symbol Mxmf Access Mx Management Framework Service com.symbol.mxmf.ACCESS_MX_MANAGEMENT_FRAMEWORK_SERVICE
- Com Symbol Mxmf Proxyframework Bind Service com.symbol.mxmf.proxyframework.BIND_SERVICE
- Com Symbol Mxmf Proxyframework Bind Service Privapi com.symbol.mxmf.proxyframework.BIND_SERVICE_PRIVAPI
