The firmware of Urovo devices supports custom, OEM-specific management policies (or configurations). OEMConfig is a standard that helps to open up those OEM-specific configurations to the EMM software solution (MobiControl) so that IT admins will be able to use a variety of EMMs to manage and monitor their devices but still able to configure the Urovo-specific settings within.
The OEMConfig application uses what is so called the “managed configurations” on the Google Play Store, and because those managed configurations are visible to the EMM software solutions, that is the reason why the EMMs can show the available Urovo-specific settings to their users (the IT admins) and let them change those configurations.
OEMConfig can also be extended to any software application, when an app follows the OEMConfig standard, the EMMs can see the managed configurations for that app and show the app-specific configurations that can be configured via the EMM. An example is Google’s Chrome browser, it opens up some of its configurations via OEMConfig so that IT admins can use their preferred EMM to change the Chrome settings remotely.
The same goes for UrovoOEMConfig. The UrovoOEMConfig application opens up the Urovo-specific firmware settings to the EMM solutions so that the IT admins can use their preferred EMM to change the Urovo-specific settings.
The Urovo-specific configurations that are exposed via the OEMConfig v1.0 interface include: - Common Android Settings (WiFi, Date & Time, Display, NFC, Language, IME) - Urovo Device Capability Settings - Urovo ScanService Configurations - Urovo Application Configurations (KeyRemap, Scanner, Wireless General, Update, WlanAdvanced) - Update the OS via a Local OTA File