Skip to main content

OEMConfig

Installing the App

The Datalogic OEMConfig can be installed through Google Play, an Enterprise Mobility Management (EMM) solution, or by using Scan2Deploy.

Overview​

The application is compatible with Datalogic devices running Android 8 and above. The Datalogic OEMConfig application is published to your device by your Enterprise Mobility Solution (EMM) provider through the EMM administrator console. Please refer to your EMM's instructions on how to add and deploy OEMConfig to your devices.

Important

OEMConfig can only be configured through an EMM administrator console. The OEMConfig application is a foreground service; it doesn't have a user interface or launcher icon. You can verify that OEMConfig is installed on your device by going to Settings > Apps & notifications > App info.

The following links provide more information about Android Enterprise and OEMConfig.

Applying Managed Configurations​

The managed configuration contains the device settings exposed by OEMConfig. Your EMM administrator console provides an interface to view and make changes to the managed configuration. Once configured, the EMM will publish the customized configuration to the device to be applied by the Datalogic OEMConfig application. Refer to your EMM's instructions on how to edit and send the managed configuration to your devices.

Once the EMM has published the custom configuration, the OEMConfig application will be notified and will automatically begin applying the custom configuration to the device. In most cases, the configuration should be applied in less than one minute.

Updates to the managed configuration and Datalogic OEMConfig app will be uploaded to Managed Google Play. The EMM will sync with the latest version of Datalogic OEMConfig. Therefore, the latest updates and features will always be available for use.

Feedback Channel​

The application feedback channel is a mechanism to provide configuration results to an administrator. Once a managed configuration is deployed, a feedback state will be created for each restriction received. This state will either be INFO (success) or ERROR (failure), and will contain the sent value and other relevant data.

The report will then be available for retrieval by the EMM administrator console. The report may not be immediately available (a request for immediate feedback retrieval is allowed three times per device in a 24-hr period), but will be retrieved within some time frame.

For information regarding feedback channel support within the EMM administrator console, please contact your EMM provider.

Managed Configuration Restrictions​

Each customizable setting in the managed configuration is a restriction type.

The following sections contain:

  • A description of each restriction in the managed configuration
  • Any dependencies on other restrictions
  • Valid value ranges and data types
  • The restriction's default value

A brief description of each restriction should also be presented in the EMM administrator console.

Release Notes​

OEMConfig 2.3.0​

Enhancements​

Corrected Defects​

  • Corrected defects for Launching Activities
  • Minor bug fixes

OEMConfig 2.2.3​

Corrected Defects​

  • Corrected defects for Launching Activities, setting Screen Brightness, and Lock Keyboard Input on A11 devices.

OEMConfig 2.2.2​

Enhancements​

OEMConfig 2.1.3​

Corrected Defects​

  • Corrected defect that can cause OTA updates to fail on the Memor 10.

OEMConfig 2.1.1​

Enhancements​

Corrected Defects​

  • Reboot is no longer required to enable/disable Ethernet.

OEMConfig 2.0.0​

Enhancements​

Corrected Defects​

  • Fixed issue where settings would not apply on Memor 10 Android 8.1
  • Fixed issue where settings would not apply on Memor K

OEMConfig 1.10.0​

Enhancements​

OEMConfig 1.9.0​

Enhancements​

  • Increased keyboard remapping support to cover all keys on the Skorpio X5 and the volume keys.

Corrected Defects​

  • Added descriptions to some configuration items to better indicate which products they are supported on.

OEMConfig 1.8.2​

Enhancements​

  • Improved handling of incorrect values for newer settings

OEMConfig 1.8.1​

Corrected Defects​

  • Fixed incorrect default value for Memor 20 2nd Display Sleep setting

OEMConfig 1.8.0​

Enhancements​

Corrected Defects​

  • Added missing Auto scan trigger
  • Improved screen brightness consistency across devices

OEMConfig 1.7.2​

Corrected Defects​

  • Fixed Language setting not persisting through reboot

OEMConfig 1.7.1 (internal release)​

Enhancements​

  • Changed default behavior when started from Scan2Deploy

OEMConfig 1.7.0​

Enhancements​

OEMConfig 1.6.2​

Corrected Defects​

  • Fixed space character trimming for scanner formatting settings (escape sequence now allowed)

OEMConfig 1.6.1​

Enhancements​

OEMConfig 1.6.0​

Enhancements​

OEMConfig 1.5.1​

Corrected Defects​

  • Fixed service notification icon format

OEMConfig 1.5.0​

Enhancements​

Corrected Defects​

  • Changed default value for keyboard wedge input mode
  • Fixed mismatch in restrictions schema for firmware update

OEMConfig 1.4.0​

Enhancements​

OEMConfig 1.3.0​

Enhancements​

Corrected Defects​

  • Removed value dependencies, allowing any setting to be configured regardless of another setting's state

Other Notes​

  • Removed top level bundle arrays from schema

OEMConfig 1.2.0​

Enhancements​

  • Unconfigured settings have their default value applied

OEMConfig 1.1.0​

Compatibility​

  • Android 8 and above

Enhancements​

Other Notes​

  • Initial release in Play Store