AEP guideline: Android Telecom Framework

Integrate with the Android Telecom framework using the Core-Telecom Jetpack library to ensure that Voice over IP (VoIP) calls are treated as a core feature by the operating system, on par with traditional SIM-based calls. This integration unifies call management, improves audio handling, and enables compatibility with remote devices like headsets and watches.

Required implementation

To qualify for AEP, your app must adhere to the following requirements:

  • Call registration: All incoming and outgoing VoIP calls must be registered with the Telecom framework using the CallsManager#addCall API.
  • State management: Use the CallControlScope and other library constructs to accurately reflect and manage the call state lifecycle, including dialing, ringing, active, held, and disconnected states.
  • Audio handling: Don't directly use Audio or Bluetooth APIs to manage audio focus and routing; instead, rely on the Telecom framework to handle concurrent call scenarios and audio device changes.
  • Notifications: Use the callStyle API to display call-style notifications that are consistent with the Android system.
  • Foreground service lifecycle: Manage the lifecycle of any necessary Foreground Services for the call in accordance with Android best practices and limitations.
  • Remote surface integration: Synchronizes call state and controls with connected remote surfaces, such as Bluetooth headsets, Wear OS devices, and Android Auto.
  • Multi-call scenarios: Gracefully handles interactions with other calls, such as incoming SIM calls or calls from other VoIP applications, ensuring predictable audio behavior and user experience.

Guideline applicability

This guideline applies to:

  • Apps provide Voice over IP (VoIP) calling capabilities.
  • All form factors on which the app is available.

Exemptions

The following exemptions apply for this guideline:

  • Apps that are technically unable to take AndroidX dependencies due to technical barriers such as:
    • SDK dependency collisions
    • Android Open Source Project (AOSP) constraints
    • Original Equipment Manufacturer (OEM) build system restrictions
  • Temporary exemptions may be granted for apps encountering significant platform or library issues that prevent a stable migration, provided there is a clear timeline for resolution and the issue has been accepted by Google.
  • Apps can use an equivalent alternative framework that provides similar quality, user capabilities, stability and compatibility across the ecosystem. Contact support if you have a suitable framework for consideration.

Feature documentation and resources

The following resources provide implementation guidance and technical details on the Android Telecom Framework. These resources are for your reference only and don't contain additional program requirements.