This document outlines the changes made to the telephony-related parts of the Android framework in the 7.0 release to support enterprise use cases. This document is targeted at manufacturers and focuses entirely on framework-related telephony changes. In addition, this document outlines the changes that OEMs will need to make to their preloaded applications that handle telephony-related functions.
Android 7.0 introduces several new features to support enterprise telephony use cases, in particular:
The Android Open Source Project (AOSP) implementations of Dialer, Contacts, and Messaging apps have integrated the cross profile contact search and badging capability.
Examples:
packages/apps/ContactsCommon
f3eb5a207bfe0ff3b4ed2350ae5865ed8bc59798
packages/apps/ContactsCommon
cd0b29ddbf3648e48f048196c62245d545bc6122Device implementers must implement cross-profile, search, lookup and badging for contacts in their Dialer Contacts and SMS/MMS Messaging apps.
Cross profile contact search should be implemented using the Enterprise Contacts
API (ContactsContract.Contacts.ENTERPRISE_CONTENT_FILTER_URI
etc.)
see http://developer.android.com/preview/features/afw.html#contacts
Work profile contact badging can be implemented by checking
ContactsContract.Directory.isEntepriseDirectoryId()
if available or
http://developer.android.com/reference/android/provider/ContactsContract.Contacts.html#isEnterpriseContactId(long)
Manufacturers should not need to modify the framework code to support this functionality, but should be aware of it’s impact on the Telecomm service and other telephony features.
The cross profile contact search and badging feature can be validated by:
CTS tests have been added to ensure the underlying cross profile contact search
API has been implemented in
com/android/cts/managedprofile/ContactsTest.java
.