OEM Config

OEMConfig is a set of device configurations offered by OEM (Original Equipment Manufacturers) as an Android app. These configurations are called managed configurations used by EMM providers to remotely restrict and control fully managed or company owned devices. In the past, device manufactures offered their own device management SDKs to EMM vendors but integrating them was cumbersome and not easily deployable due to different versions of SDKs from various OEMs.

How does OEM Config help businesses

OEMConfig interface tries to solve these problems by giving OEMs complete control over their EMM SDK app. OEMs can make updates and publish the app in the Play Store and EMM vendors can deploy it to customers devices. This brings zero-day support for a new mobile device management feature or a bug fix. OEMConfig app can also run in a privileged mode (system app) as it is signed and published by the device manufactures.

How does OEM Config help businesses
How does it work?

How does it work?

When an OEM develops an Android app with Android Enterprise managed configurations, it publishes the app on Google Play Store.

The EMM Administrator approves this OEMConfig app, deploys it and configures the managed configurations through their EMM console.

OEMConfig app in the device receives these configurations settings and enforces them in the device.

Codeproof EMM platform is integrated with the following OEM vendors

  1. Samsung
  2. Kyocera
  3. Zebra
  4. Honeywell
  5. Datalogic
  6. Spectralink
Codeproof EMM platform is integrated with the following OEM vendors

What you can do per OEM

OEMConfig exposes manufacturer-specific Android controls that the standard Android Enterprise API doesn't cover. Codeproof's MDM console reads each OEM's published schema and lets IT configure these advanced controls without custom code:

Samsung Knox (Knox Service Plugin)

  • Hardware key remapping and Bixby controls
  • Dual SIM / eSIM provisioning
  • Knox secure container settings
  • Peripheral and USB controls

Zebra (Mx)

  • Barcode scanner profile and decoder configuration
  • StageNow-equivalent provisioning via OEMConfig
  • Mobility DNA app permissions
  • Custom hardware key behavior

Honeywell (EZConfig / Smart Talk)

  • Scanner and imager configuration
  • Push-to-talk (PTT) controls
  • Power-management and hardware buttons
  • Firmware update channel selection

Kyocera

  • Ruggedization controls (programmable buttons, glove mode)
  • Waterproof / pressure sensor settings
  • Push-to-talk and emergency-button routing

Datalogic

  • Barcode scan engine and decoder controls
  • Wedge / intent-based scan output
  • Keypad and hardware-key mapping

Spectralink

  • Voice / PTT device profile
  • Hardware-key behavior and emergency alarms
  • Wi-Fi roaming and band-steering preferences

Where OEMConfig matters most

  • Warehousing & logistics: configure Zebra and Honeywell scanners, scan engines, and hardware-button behavior across thousands of devices
  • Manufacturing & field service: deploy ruggedized Android with custom power, ergonomic, and PTT settings
  • Retail & POS: pin Samsung XCover or Zebra TC tablets to a single retail app with branded launcher and hardware-button remapping
  • Public safety & first responders: configure Kyocera DuraForce or Sonim emergency buttons and waterproof / glove modes
  • Healthcare: deploy Spectralink and Zebra TC handhelds with PTT and shared-device sign-in / sign-out

Benefits of OEMConfig with Codeproof

  • Zero-day support for new OEM features: when the OEM ships a new OEMConfig version, Codeproof can apply it immediately - no MDM vendor SDK upgrade required
  • Privileged system-app execution: OEMConfig apps run with elevated rights because they're signed by the device manufacturer
  • Standardized model: one Android Enterprise managed-configuration interface across every OEM
  • Bulk deployment via Android Zero-Touch and Samsung Knox Mobile Enrollment
  • Audit-ready: configuration changes are versioned and logged for compliance evidence

OEMConfig FAQs

What is OEMConfig?
OEMConfig is an Android Enterprise standard: device manufacturers publish a managed-configuration schema as an app on Google Play. MDM platforms read the schema and let IT configure OEM-specific controls (scanners, hardware buttons, PTT, etc.) without custom SDK integration.
Which OEMs does Codeproof support via OEMConfig?
Samsung (Knox Service Plugin), Zebra (Mx), Honeywell (EZConfig / Smart Talk), Kyocera, Datalogic, and Spectralink - with new vendors added as they publish OEMConfig apps.
Do I need both standard Android Enterprise policies and OEMConfig?
Yes. Standard Android Enterprise covers OS-level policy (passcode, encryption, app deployment, work profile). OEMConfig adds manufacturer-specific controls that aren't part of the standard API. Codeproof applies both from the same console.
How does OEMConfig compare to the older EMM SDK model?
OEMConfig is far more maintainable: the OEM ships an app via Google Play that any MDM can consume. The legacy EMM SDK model required each MDM vendor to bundle a unique OEM SDK and recompile for every update - much slower and more brittle.

Maximize employee productivity through Codeproof