2019 Release Notes
Android Release Summaries
Android 6.70 release summary
MaaS360 for Android core
MaaS360 announces the general availability of Device Admin (DA) to Work Profile (Android Enterprise Profile Owner) migration. In the second phase of series of enhancements, MaaS360 adds support for migration of multiple devices at once (group action), enforcement of Work Profile migration (force migration after 90 days), activation of Samsung Knox License (SKL) as well as track granular migration status in the Action history as a part of migration. Note: Requires MaaS360 for Android agent version 6.70 and later.
MaaS360 now allows administrators to make Android Enterprise the default enrollment mode for the organizations that want to move off the Device Admin deployment mode and adopt Android Enterprise. MaaS360 also displays an alert message in the home page if Android Enterprise is not setup. For new customers, Android Enterprise must be set up in the MaaS360 portal to complete Android Enterprise enrollments on the device. The existing customers can contact MaaS360 Account Representative to enable this feature for their account.
MaaS360 adds support to allow administrators to drive the Android Enterprise enrollments based on the minimum OS version. This feature is helpful for the organizations that are implementing a phased adoption to Android Enterprise, wherein the latest OS versions can be pushed to Android Enterprise and the old versions can stay back on Device Admin deployment. Administrators can use the self enrollment options in the Device Enrollment Settings to configure the OS versions that are allowed to use Android Enterprise. When the end-users initiate the enrollment, the devices that meet the minimum OS requirement enroll into Android Enterprise (Work Profile) and the devices that do not meet the minimum OS requirement fall back to Device Admin deployment.
MaaS360 adds support to block automatic system updates over a scheduled time to allow administrators to evaluate the new update for compatibility and bugs before rolling out to employees. Administrators can suspend system updates for up to 90 days. When a device is within a freeze period, the notifications about pending system updates are not received, the system updates to the OS are not installed, and the users are prevented from manually checking for system updates.
MaaS360 for Android includes various behavior changes as a part of compilation against Android OS version 10.
Location services auto-enabled in Android Enterprise enrollments >>
When a device is enrolled in Android Enterprise (DO and PO), MaaS360 automatically gains access to device location when the app is running in foreground and background. In Device Admin enrollments, users must explicitly grant location permissions to MaaS360. Note: Supported on Android Q and later devices.
Shared Device support for G Suite
The shared device feature is only supported on Android 9 Pie and later devices that are enrolled into Android Enterprise through G Suite account in corporate shared mode. The Sign In and Sign Out options are unavailable on Android devices running OS version below 9 Pie.
Validation of Google user account on the devices as a part of policy evaluation
MaaS360 now validates the status of managed Google account as a part of policy evaluation on the devices that are enrolled in both PO and DO modes . If the managed Google account is removed by the users, MaaS360 automatically creates the Google account for non-G Suite accounts and marks the device Out of Compliance (OOC) for G Suite customers, allowing the users to manually create the corresponding Google account.
Deprecation of devices that only use armeabi architecture >>
MaaS360 announces the deprecation of devices that only use armeabi architecture.
MaaS360 adds a new setting to allow users to directly launch the native dial pad on tapping the phone numbers across Secure Mail and Calendar apps. Previously, users had to manually choose the native dial pad from the app chooser dialog.