Google adds Jetpack Telecom v1.1

Google published new Android developer guidance on May 14 showing how third-party Voice over IP apps can place their calls inside system dialers and device call logs. The documentation describes a “unified call history” flow that lets users see VoIP calls in the native dialer and start a return call from that interface. Google’s developer pages say the feature requires Jetpack Telecom 1.1.0-alpha01 or later and applies to both calling apps and dialer apps. 9to5Google reported on May 14 that Google framed the update as bringing “native-level visibility and convenience” to third-party VoIP apps. The report said Phone by Google is among the dialers that can surface those calls, and showed Google Meet appearing alongside cellular calls in the app’s home tab. ### Which Android apps change with this update? VoIP applications are the main target of the new guidance, according to Android Developers. (developer.android.com) Google says those apps can integrate their calls into the system call log so users can view VoIP history centrally in the system dialer and return calls directly from that dialer. System dialer apps also need changes, Google said. (9to5google.com) The unified call history guide is written for both sides of the interaction: the calling app that adds calls through Telecom APIs and the dialer app that displays those logs and initiates callbacks. ### How does a third-party app get its calls into the native dialer? Google’s documentation says a calling app must register the protected intent `TelecomManager.ACTION_CALL_BACK`. (developer.android.com) Once that intent filter is registered, calls added through `CallsManager.addCall` or related Telecom APIs are automatically logged by the system, according to the guide. The Android Developers guide says each call added through `CallsManager.addCall` receives a unique UUID from `CallControlScope.getCallId`. Google says the VoIP app must store that UUID and map it to call details, because the system dialer later sends a callback intent with `TelecomManager.EXTRA_UUID` when a user taps the call log entry to return the call. (developer.android.com) ### What does Google let developers control? Google says developers can exclude specific calls from logging. The unified call history page says that after callback registration, calls are logged to the system dialer by default, but developers can set `isLogExcluded` to `true` in `CallAttributesCompat` on a per-call basis. 9to5Google said Google described that option as a way to keep some calls out of native dialer history for privacy, ephemeral communication or app-specific reasons. (developer.android.com) That characterization came from the report’s summary of Google’s documentation. ### What is Jetpack Telecom, and how does it fit into Android’s call stack? Android Developers describes the Telecom framework as the layer that manages audio and video calls on Android devices, including SIM-based calls and VoIP calls built with the Core-Telecom Jetpack library. (developer.android.com) Google says the Core-Telecom library is meant to give developers a consistent API for registering a calling app, creating calls and managing call state. (9to5google.com) The Core-Telecom setup guide shows developers adding the `androidx.core:core-telecom` dependency and declaring the `MANAGE_OWN_CALLS` permission. The same guide points developers to lightweight and comprehensive sample apps on GitHub for implementation examples. ### Is this already a stable Jetpack release? Google’s stable AndroidX release page did not list Telecom among stable releases visible through May 12, 2026, while the unified call history page says the feature requires Jetpack Telecom 1.1.0-alpha01 or higher. (developer.android.com) That means Google has published the feature guidance even though the documentation visible in search points to an alpha threshold rather than a stable Telecom listing. (developer.android.com) 9to5Google reported the feature as Jetpack Telecom v1.1.0 and said Google was publishing documentation and sample code ahead of Google I/O. Google I/O is scheduled to begin on May 19, 2026, and the Android Developers pages for unified call history and Core-Telecom are already live. (9to5google.com) (developer.android.com)