Set up OEM Configurations for Social Mobile devices with Rhino Config app
OEM configuration is a standard consisting of a set of tools used by Google to let mobility management vendors customize OEM-specific settings for devices enrolled in the Android Enterprise program. With the help of Social Mobile’s OEM configuration application, called the Rhino Config, specialized OEM features exclusively present in the app can be configured and deployed in Social Mobile devices.
To make use of these settings, an organization must first integrate with a mobility solution that offers OEM configuration support. Hexnode’s endpoint management solution provides simple tools by which this can be effortlessly achieved. You can configure various settings by adding the Rhino Config app in an App Configurations policy. This is a specialized App Management feature in the Hexnode MDM portal, that offers the admin to set up various configurations and settings present in the app. Once the settings are configured from the console, the apps can be deployed to the respective devices.
Mentioned below are the main steps to be followed while configuring Social Mobile devices with the Rhino Config app:
- Approve and add the Rhino Config application to the Hexnode app inventory.
- Configure OEM-specific features.
- Deploy the app to the respective device(s).
Approve and Add the Rhino Config app to the Hexnode app inventory
To approve and add the Rhino Config app to the Hexnode inventory, go through the following steps:
- In the Hexnode portal, navigate to the Apps tab.
- From the +Add Apps dropdown, select Managed Google Apps.
- Search for Rhino Config, and select the app.
- Now, give the required permissions for the app by clicking on the Approve button.
- This takes you to the Approval Settings page, where there are two approaches to handle the app permission requests:
- Keep approved when app requests new permissions – This option enables the app to automatically get re-approved in a scenario where new permissions are requested.
- Revoke app approval when this app requests new permissions – The app will be removed from the managed Play Store app on the device until it is
re-approved, when new app permissions are requested.
- Go to the Notifications tab to provide your email addresses so that you will be notified when the app requests new permissions. Click Add.
- Now, click Done.
The Rhino Config app will now be added to the Hexnode app inventory. Now, you can deploy the app to the target Social Mobile Rhino devices.
Configure OEM specific settings
To set up OEM configurations on the Android Enterprise enabled Rhino devices,
- Navigate to Policies in Hexnode portal.
- Either choose an existing policy, or click on the New Policy button and create a new policy with a custom policy name.
- Go to Android > App Management > App Configurations.
- Select Configure and click on the +Add new configuration button.
- From the list of applications, choose the Rhino Config app.
- In the app configuration screen displayed, choose and configure the required settings.
The settings that can be configured are given below:
|Enable quicksettings icons||Quick settings icons are the ones displayed when the notification bar is swiped down. This configuration gives the option to freeze the icons so that they cannot be toggled. It also provides an option to hide the panel completely.|
|Enable notification panel settings icon||This option lets the user enable or disable the settings icon displayed in the notification panel. This can prove useful to organizations who want to provide users the option to view notifications, but at the same time restrict access to settings.|
|Enable notification panel||The notification panel is the one that is pulled down to view all notifications, quick settings, settings icon, etc. When this setting is configured as disabled, the system will disable the notification panel, and prevent notification icons from being shown in the status bar.|
|Enable status bar||Status bar is the field displayed on the top of the screen, that includes time, battery, network indicators, notification icons, etc. If this configuration is disabled, the system will disable the status bar entirely, effectively hiding it from view. The notification panel can still be invoked with a swipe down.|
|Enable navbar (whole bottom nav & background bar)||This feature allows the navbar to be configured such that it is completely hidden from view. This configuration is only suitable for a navigation bar with three buttons.|
|Enable home long press (Google assistant)||The home button long-press feature can be configured to enable or disable Google Assistant. This won’t impact its invocation through other means.|
|Enable recents soft key||Allows the user to configure the visibility of the recents key.|
|Enable home soft key||Allows the user to configure the visibility of the home soft key.|
|Enable back soft key||Allows the user to configure the visibility of the back soft key.|
|Enable power button (long press)||Configure the user’s ability to long-press the power button and bring up the power menu.|
|Enable power button (short press)||Configure the user’s ability to short-press the power button, disabling the ability to sleep/wake the screen with a power press.|
|Enable volume buttons||Configure the user’s ability to toggle volume through the volume buttons. This will not prevent access to volume via Settings.|
|Enable camera button (long press/short press)||Controls the ability to long-press/short-press the camera button. This feature is only applicable to devices with camera buttons.|
|Enable multifunction button (long press/short press)||Controls the ability to long-press/short-press the multifunction button. This feature is only applicable to devices with multifunction buttons.|
|Enable PTT button (long press/short press)||Controls the ability to long-press/short-press the Push-to-talk (PTT) button. Basically, a PTT button is one which can be pressed to enable communication. This feature is only applicable to devices with PTT buttons.|
|Enable scanner button (long press/short press)||Controls the ability to long-press/short-press the scanner button. This feature is only applicable to devices with PTT buttons.|
|Enable wake device on scan button press||This feature allows the admin to control the ability to wake the device by pressing the scan button. The feature is enabled by default, and only applicable to devices with scan buttons.|
|Enable access to device recovery||Enables the admin to configure the user’s access to recovery settings on the device. This feature needs to be used with caution, since preventing access can be risky.|
|Screen state||This configuration allows the device screen to be set to always on or always off. It must be noted that keeping the device in always on mode will cause significant battery drainage. The option can also be set to manual.|
|Force brightness level (0 to 100)||The admin can configure the brightness displayed on the device. When configured, this cannot be modified by the user. Automatic brightness should be disabled if this feature is configured. If the value is set outside the 0 – 100 range, the user will gain control over screen brightness.|
|Enable automatic brightness||This configuration will be enabled by default since for Rhino devices, automatic brightness is set by default. If the option remains enabled while the configuration is pushed, it will prevent automatic brightness from being disabled. If manual brightness is to be set, the configuration must be set to false.|
|Device name||Allows the admin to enter the device name in the field provided.|
|Enable screen lock||Allows the admin to disable the screen lock (sets to none in device settings)|
|Enable key guard||Allows the admin to disable the setting up of any kind of passcode on the device. Disabling this feature can affect the working of apps or services that may requires a passcode.|
|Wake up applications||When installed, applications on the device will remain inactive until opened by the user. If a package name is added here, the device will automatically wake the app following installation. You can add multiple app packages by clicking on the Add group button.|
|Apply update from storage||When enabled, this feature allows the admin to send the update package zip normally distributed via OTA to a folder on the system named “systemUpdate” present at /storage/sdcard0/. When file “RhinoUpdate.zip” is detected in the folder, the system update procedure is initiated immediately.|
Associate Policies with Devices/Groups
If the policy has not been saved yet,
- Navigate to Policy Targets.
- Click on +Add Devices.
- Select the devices and click OK.
- Click on Save to apply the policies to devices.
The policy can also be associated with Device Groups, Users, User Groups, or Domain from the left pane of the Policy Targets tab.
If the policy has already been saved,
- From the Policies tab, select the policy to be associated.
- Go to Manage > Associate Targets and select the device.
- Click on Associate to apply the policy to the device.