Best Practices for Configuring Restrictions with Android (Legacy) Devices

The following are some considerations for implementing device restrictions for Android devices.

• We do not recommend the Allow WiFi restriction on devices, especially for those without any cellular data available, as this will result in the loss of connectivity on the device.
• For Allow Headphones, enabling headphones while they are still plugged in will not work because headphones need to be initialized by re-plugging in.
• With the Enable Bluetooth Secure Mode you can restrict different Bluetooth profiles and whitelist the devices based on the Bluetooth class, name and UUID of the Bluetooth devices. This setting takes effect after secure mode is enabled and Bluetooth is turned on the next time.
• For Android 4.0 onward, disabling background data with Allow Background Data works only when a mobile data limit is set. When the policy is enabled, the mobile data limit is set to 100GB; the user cannot disable the mobile data limit but can change the actual limit.
• For Allow SD Card Write, this policy is not applicable when the SD card is encrypted. If SD card is encrypted, the files in the SD card cannot be read by other devices or PCs except for the device that encrypted it. Hence SD card encryption takes priority over this policy.
• If Allow Camera has been turned off for the main device user, then the camera will be disabled for all the containers and users created on the device.
• If Allow Microphone has been turned off for the main device user, then the microphone will be disabled for all the containers and users created on the device.
• The Allow Clipboard policy only takes effect over native Android clipboard.
• Allow Incoming MMS and Allow Outgoing MMS applies to the native MMS client application.