IBM Support

Behavior changes with Android 10 or Q

Release Notes


Abstract

MaaS360 for Android includes various behavior changes as a part of compilation against Android Q (OS version 10) devices.

Content

  • NFC-based Android Device Owner enrollments are not supported for Google Pixel devices as Android Beam is deprecated on these devices.
    Path: Device Inventory > Actions drop-down > Enter Programmer mode.
  • When the administrator removes the app from device view > Summary > Apps Installed or the apps marked for Remove apps on stop distribution, MaaS360 displays a notification on the devices to uninstall the app. If users do not take that action, MaaS360 blocks access to end-user App Catalog and other MaaS360 first party apps on Device Admin and Android Enterprise (PO) devices. The apps are silently uninstalled on Device Owner devices.
  • Administrators cannot block the restricted apps on Device Admin devices through App compliance policies. The app compliance policy action Block from use for Configure Restricted applications is not supported on Device Admin devices.
  • IMEI/MEID and Platform Serial Number are not tracked for Device Admin devices. Requires Android Enterprise enrollment. 
  • Randomized Wi-Fi Mac Address is displayed for Device Admin, and Android Enterprise devices enrolled in Profile Owner mode.  Factory MAC address is not tracked for Device Admin and Profile Owner devices.
  • App instant install and instant upgrade are not supported on Device Admin devices. 
  • Authentication and compliance cannot be enforced on Google play apps on Android Enterprise devices.
    Path: App Catalog > Add Google Play App > Policies & Distributions > Security Policies. The Enforce Authentication and Enforce Compliance options are not supported.
  • Buzz action on Device Admin and Profile Owner modes: When the buzz action is issued to a device, the buzz screen with cross icon is not displayed. Users must tap the notification to stop the buzz sound. If notifications are disabled, the buzz sound automatically stops after 3 minutes. 
  • Due to background activity restrictions, the MaaS360 app is not launched automatically when the DA and PO devices become out of compliance. Users must launch the MaaS360 app manually by tapping the Out of Compliance notification.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.74","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
02 July 2019

UID

ibm10957305