Android Auto에서 전화를 받고 제어하려면 앱이 통화 앱 빌드에 설명된 대로 Telecom Jetpack 라이브러리와 통합되어야 합니다. 특히 앱은 원격 노출 영역 지원에 설명된 콜백을 지원해야 합니다. 또한 앱은 사용자의 휴대전화에서 Android Auto가 실행 중일 때뿐만 아니라 항상 텔레콤 통합을 사용해야 합니다.
템플릿화된 통화 환경 빌드
Android Auto에서 제공하고 앱의 통신 통합을 기반으로 하는 통화 중 뷰 외에도 앱은 사용자가 자동차 화면에서 앱 콘텐츠에 액세스할 수 있는 템플릿화된 환경을 제공할 수 있습니다. 예를 들어 앱에서 통화 시작 작업이 포함된 연락처 목록, 예정된 통화의 일정 보기, 통화 기록 등을 표시할 수 있습니다. 통화가 진행되는 동안 Android Auto는 통화 기간 동안 통화 중 뷰를 자동으로 표시하여 앱의 템플릿 화면을 대체합니다.
통화를 지원하는 앱은 Google Play의 내부 테스트 및 비공개 테스트 트랙에만 게시할 수 있으므로 공개 테스트 또는 프로덕션 트랙에 지원이 포함된 빌드를 프로모션해서는 안 됩니다. 이러한 트랙의 빌드가 포함된 제출물은 거부되기 때문입니다.
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-07-27(UTC)
[null,null,["최종 업데이트: 2025-07-27(UTC)"],[],[],null,["# Build calling experiences for Android Auto\n\nCalling experiences are in beta \nAt this time, anyone can publish communication apps with calling experiences to internal testing and closed testing tracks on the Play Store. Publishing to open testing and production tracks will be permitted at a later date. \n[Nominate yourself to be an early access partner →](https://forms.gle/VsXEdDEBidxw8q8u8) \n\nApps that support making voice calls can improve their experience on Android\nAuto by integrating with the [Telecom Jetpack library](/develop/connectivity/telecom) and\nproviding a templated user interface built using the [Android for Cars App\nLibrary](/training/cars/apps).\n\nIntegrate with the Jetpack Telecom library\n------------------------------------------\n\nTo support answering and controlling calls on Android Auto, your app must\nintegrate with the Telecom Jetpack library as described in\n[Build a calling app](/develop/connectivity/telecom/voip-app). In particular, your app must support the\ncallbacks described in[Remote surface support](/develop/connectivity/telecom/voip-app/telecom#remote-surface-support). Your app must\nalso use it's telecom integration at all times, not just when a user's phone is\nrunning Android Auto.\n| **Important:** Additional requirements for your app's telecom integration will be provided in this guide soon.\n\nBuild a templated calling experience\n------------------------------------\n\nIn addition to the in-call view that Android Auto provides and which is powered\nby your app's telecom integration, your app can provide a templated experience\nto let users access your app's content on their car screen. For example, your\napp can display a list of contacts with actions to start a call, an agenda view\nof upcoming calls, a call log, and more. While a call is ongoing, Android Auto\nautomatically displays its in-call view for the duration of the call, replacing\nyour app's templated screens.\n\nFollow the guidance in [Use the Android for Cars App Library](/training/cars/apps) and [Add\nsupport for Android Auto to your templated app](/training/cars/apps/auto) to get started\nbuilding your app's templated experience. Then, refer to the guidance on this\npage to understand the specific requirements for calling apps.\n\n### Configure your app's manifest files\n\nTo inform Android Auto of your app's capabilities, your app must do the\nfollowing:\n\n#### Declare category support in your manifest\n\nYour app needs to declare the `androidx.car.app.category.CALLING`\n[car app category](/training/cars/apps#supported-app-categories) in the intent\nfilter of its [`CarAppService`](/reference/androidx/car/app/CarAppService). \n\n \u003capplication\u003e\n ...\n \u003cservice\n ...\n android:name=\".MyCarAppService\"\n android:exported=\"true\"\u003e\n \u003cintent-filter\u003e\n \u003caction android:name=\"androidx.car.app.CarAppService\" /\u003e\n \u003ccategory android:name=\"androidx.car.app.category.CALLING\"/\u003e\n \u003c/intent-filter\u003e\n \u003c/service\u003e\n ...\n \u003capplication\u003e\n\n| **Important:** If your app supports both calling and [messaging](/training/cars/communication/messaging), include both `androidx.car.app.category.CALLING` and `androidx.car.app.category.MESSAGING` `\u003ccategory\u003e` elements in the same intent filter.\n\nDistribute calling apps\n-----------------------\n\nBecause apps that support calling can only be published to Internal Testing and\nClosed Testing tracks on Google Play, you shouldn't promote builds that include\nsupport to Open Testing or Production tracks, as submissions containing builds\non those tracks will be rejected."]]