如要支援在 Android Auto 上接聽及控制通話,應用程式必須整合 Telecom Jetpack 程式庫,如「建構通話應用程式」所述。具體來說,應用程式必須支援「遠端介面支援」一文所述的回呼。應用程式也必須隨時使用電信整合功能,而非僅在使用者手機執行 Android Auto 時才使用。
建立使用範本的通話體驗
除了 Android Auto 提供的通話中檢視畫面 (由應用程式的電信整合功能提供) 之外,應用程式還可提供範本體驗,讓使用者在車輛螢幕上存取應用程式內容。舉例來說,您的應用程式可以顯示聯絡人清單,並提供開始通話的動作、即將來電的議程檢視畫面、通話記錄等。通話期間,Android Auto 會自動顯示通話中畫面,取代應用程式的範本畫面。
[null,null,["上次更新時間: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."]]