Zebra OEMConfig managed configuration for Android

Common setups

Common Zebra OEMConfig setups

Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.

{
  "uiConfig": {
    "uiGeneralConfig": {
      "uiElementConfig": {
        "uiElementStatusBar": "2",
        "uiElementPowerOffInPwrKeyMenu": "2"
      }
    },
    "keyboardConfig": {
      "keyboardUseOfHome": "2",
      "keyboardUseOfRecentApps": "2"
    }
  }
}

{
  "uiConfig": {
    "displayConfig": {
      "displayPowerConfig": {
        "displayPowerStayAwake": "15",
        "displayPowerTimeout": "60",
        "displayPowerBrightnessMode": "2",
        "displayPowerBrightness": 60
      }
    }
  }
}

{
  "systemConfig": {
    "clockConfig": {
      "sysClockTimeMode": "true",
      "sysClockAutoNtpServer": "time.example.com",
      "sysClockAutoNtpSyncInterval": "06:00:00",
      "sysClockTimeFormat": "1"
    }
  }
}

Managed configuration

Zebra OEMConfig managed configuration keys

Key names and value types come from the vendor’s documentation. The explanations are written by Nomid.

Deploy with Nomid

Roll Zebra OEMConfig out in three steps

1. Step 1Add Zebra OEMConfig to a policy

   Find it on Google Play from the policy’s apps list and choose how it is installed.

2. Step 2Set its managed configuration

   In the policy, set the app’s managed configuration with the keys and values from this page.

3. Step 3Assign the policy

   Devices in the policy receive Zebra OEMConfig and its configuration on their next sync.

Questions

Zebra OEMConfig on managed Android

Other apps in device configuration

Google Chromecom.android.chrome All apps in the directory