This document is a guide for installing and using OEMConfig to configure Datalogic devices.
The Datalogic OEMConfig application is available in Managed Google Play. 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.
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
Apps & notifications >
The following links provide more information about Android Enterprise and OEMConfig.
- Datalogic OEMConfig on the Play Store
- Learn more about Managed Google Play Setup
- Learn more about Android Enterprise
- See list of Android Enterprise Recommended EMMs
- Learn more about 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.
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.
- Added support for SDK v1.30
- Added decoding settings:
- Added Touch Screen Sensitivity
- Added support for file download using HTTP/S or FTP/S:
- Reboot is no longer required to enable/disable Ethernet.
- Added baroque and viper options to Good read audio mode
- Added Good read audio channel
- Added Illumination time
- Added Scan mode
- Added Multi Scan Partial results
- Added Presentation mode
- Added Barcode settings:
- Added Off-mode charge
- Added Memor 20 Dual SIM
- Added Wi-Fi settings:
- Added NTP settings:
- Added USB function:
- Fixed issue where settings would not apply on Memor 10 Android 8.1
- Fixed issue where settings would not apply on Memor K
- Added Launch Activities settings.
- Increased keyboard remapping support to cover all keys on the Skorpio X5 and the volume keys.
- Added descriptions to some configuration items to better indicate which products they are supported on.
- Improved handling of incorrect values for newer settings
- Fixed incorrect default value for Memor 20 2nd Display Sleep setting
- Added Battery Saver settings
- Added Wi-Fi settings
- Added Memor 20 2nd Display settings
- Added Memor 20 Ethernet setting
- Added Disable touch screen setting
- Added missing Auto scan trigger
- Improved screen brightness consistency across devices
- Fixed Language setting not persisting through reboot
OEMConfig 1.7.1 (internal release)
- Changed default behavior when started from Scan2Deploy
- Added Feedback Channel support
- Added USB Debugging setting
- Added Language setting
- Added MSI Linear Quiet Zone setting
- Fixed space character trimming for scanner formatting settings (escape sequence now allowed)
- Updated settings organization
- Added ISBT 128 User ID settings
- Added Network settings
- Added System settings
- Fixed service notification icon format
- Added Key remapping settings
- Changed default value for keyboard wedge input mode
- Fixed mismatch in restrictions schema for firmware update
- Added Charging profile setting
- Added Location mode setting
- Added NFC configuration setting
- Added Power management settings
- Added Key trigger configuration settings
- Improved Good read audio file selection (split into separate custom and default values)
- Added MSI and Code 128 aggressiveness settings
- Added Code 128 linear quiet zone setting
- Added Scanning illumination type setting
- Added Image capture profile setting
- Added Custom image capture profile setting
- Removed value dependencies, allowing any setting to be configured regardless of another setting's state
- Removed top level bundle arrays from schema
- Unconfigured settings have their default value applied
- Android 8 and above
- Added Notification settings
- Added Good Read settings
- Added Formatting settings
- Added Scanner Options & Multi Scan settings
- Added Wedge settings
- Added Symbology settings
- Added Firmware Update settings
- Initial release in Play Store