如需支持在 Android Auto 上接听和控制通话,您的应用必须与 Telecom Jetpack 库集成,如构建通话应用中所述。具体而言,您的应用必须支持远程 Surface 支持中所述的回调。您的应用还必须始终使用其电信集成,而不仅仅是在用户的手机运行 Android Auto 时使用。
构建基于模板的通话体验
除了 Android Auto 提供的通话视图(由应用的通讯集成提供支持)之外,您的应用还可以提供模板化体验,让用户在车载屏幕上访问应用的内容。例如,您的应用可以显示包含发起通话操作的联系人列表、即将进行的通话的日程视图、通话记录等。通话期间,Android Auto 会在通话期间自动显示其通话视图,替换应用的模板屏幕。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],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."]]