การปรับปรุง HAL การควบคุมเสียง: หากต้องการกำหนดค่าฟีเจอร์เสียงในรถยนต์ ให้ใช้
API แทนไฟล์ XML
ระบบแจ้งเตือนฉุกเฉิน (EAS) ของวิทยุความละเอียดสูง (HD): ส่งข้อมูล EAS
ไปยังแอปพลิเคชันวิทยุด้วย API ซึ่งใช้ได้กับ HD Radio
(อเมริกาเหนือ) และ DAB EWS (สหภาพยุโรป)
[[["เข้าใจง่าย","easyToUnderstand","thumb-up"],["แก้ปัญหาของฉันได้","solvedMyProblem","thumb-up"],["อื่นๆ","otherUp","thumb-up"]],[["ไม่มีข้อมูลที่ฉันต้องการ","missingTheInformationINeed","thumb-down"],["ซับซ้อนเกินไป/มีหลายขั้นตอนมากเกินไป","tooComplicatedTooManySteps","thumb-down"],["ล้าสมัย","outOfDate","thumb-down"],["ปัญหาเกี่ยวกับการแปล","translationIssue","thumb-down"],["ตัวอย่าง/ปัญหาเกี่ยวกับโค้ด","samplesCodeIssue","thumb-down"],["อื่นๆ","otherDown","thumb-down"]],["อัปเดตล่าสุด 2025-07-29 UTC"],[],[],null,["# Android Automotive 25Q2\n\n| **Important:** The following content is not final and is subject to change.\n\nGoogle is pleased to share this Android **25Q2** release with Android Automotive\npartners. For Android 16, this Android Automotive 25Q2 release is compliant. We\ncontinue to fine tune features, aiming to recommend an upcoming release for\nOEMs.\n\nRelease details\n---------------\n\nThis section summarizes major features and enhancements provided in the AAOS B\nrelease.\n\nThese updates apply to `Android16`, [API level 36](/docs/setup/reference/build-numbers).\n\nThe Android Automotive 25Q2 release is compliant with Android 16.\n\n### New features\n\nThe 25Q2 release provides these new features.\n\n#### AAOS Framework\n\n- Audio and radio:\n\n - **Audio control HAL improvements:** To configure car audio features, use\n APIs instead of XML file.\n\n - **High definition (HD) radio Emergency Alert System (EAS):** Pass EAS\n information to radio applications with an API. This applies to HD Radio\n (North America) and DAB EWS (European Union).\n\n - **AAudio built-in library:** [AAudio](/docs/core/audio/aaudio) AAudio supports OEM-defined\n Audio Attributes tags to customize app behavior. For example, audio\n routing and volume management.\n\n- Power management:\n\n - **Power state notifications to built-in processes:** The availability of power state notifications to OEM built-in processes (beyond Android apps) is extended.\n- Car framework:\n\n - **Dynamic configuration of vehicle properties:** Support the dynamic configuration of minimum and maximum and of supported values in vehicle properties.\n\n#### Connectivity\n\n- Networking:\n\n - **Minimal Telephony:** A subset of the Android Telephony Hardware\n Abstraction Layer (HAL) for automotive OEMs to allow OEMs to use Android\n telephony on data-only devices (including TCUs). This reduces\n fragmentation and provides support for telephony functionality.\n\n - **Connectivity Messaging Upsell API:** Enhanced [SubscriptionManager](https://developer.android.com/reference/android/telephony/SubscriptionManager)\n to provide APIs that can expose a user's mobile data subscription\n status. For example, `active`, `inactive`, `trial`, and expiration date.\n\n - **Projected app support:** Added support to let automotive OEMs\n configure the complete set of `hostapd.conf` parameters not available\n through the Android APIs. Added a disconnect reason to the\n SoftApCallback API so that OEMs can learn why clients disconnected from\n a Local Hotspot (LOHS). These features improve support for projected\n apps and reduce fragmentation.\n\n#### AAOS System UI and Experiences\n\n- **Scalable UI:** This AAOS windowing framework provides OEMs with configurable components that let OEMs meet windowing requirements and facilitate custom experiences.\n\n#### VHAL properties\n\n- Vehicle properties:\n\n - Added new vehicle properties to communicate vehicle characteristics and\n state.\n\n - Updated vehicle property constants from @SystemApi to public APIs to\n consolidate generated documentation at [VehiclePropertyIDs](https://developer.android.com/reference/android/car/VehiclePropertyIds). Any\n previously defined and documented permissions are still required to\n access vehicle property data.\n\n- **Third party-accessible vehicle properties:** This features makes eight\n existing vehicle properties relevant to navigation, voice assistant,\n weather, and driving state available to third party app developers. To learn\n more, see [Integrate with Google apps and services](https://developer.android.com/training/cars/index.md#intents).\n\n### Compliance\n\nAndroid Compliance was executed on the internal reference hardware. The test\nsuites run for this release include CTS, CTS-V, ATS, STS, VTS and CTS on GSI.\n\nExcept for the issues listed below, no known failures require a fix either in\nAndroid 16 code (`android16-release`) or to the Android 16 test branch\n(`android16-tests-dev`).\n| **Note:** Fixes for known compliance issues are provided below and will be made available in the [Android Open Source Project](https://android-review.googlesource.com/q/hashtag:%22aaos-25q2-cts%22+(status:open+OR+status:merged)) when we publish the next release. We aim to recommend an upcoming release.\n\n- Test failing:\n `CtsWindowManagerJetpackTestCases#MultiDisplayActivityEmbeddingPlaceholderTests`\n\n Failure summary: One test fails in portrait display. When testing Activity\n embedding behaviors in Scalable UI builds that are based on windowing\n solutions that involve multiple root tasks each a\n `WINDOWING_MODE_MULTI_WINDOW`, known failures occur due to some activities\n launched in smaller bounds than expected, as in `windowMetrics` of the\n embedding rules. As a result, the placeholder was started and the test\n failed when launching an activity on the secondary display.\n\n The [aosp/3659633](https://android-review.googlesource.com/c/platform/frameworks/base/+/3659633) patch corrects windowing mode inheritance from\n multi-window `rootTask`.\n- Test failing: `CtsAutoFillServiceTestCases`\n\n Failure summary: Two categories of known issues occur in the Scalable UI\n builds based on windowing solutions that involve multiple root tasks each of\n `WINDOWING_MODE_MULTI_WINDOW`:\n - IME covers the Autofill fill dialog that prevents the buttons on the\n fill dialog from being pressed. You can temporarily disable the fill\n dialog with this platform [ag/3664131](https://android-review.googlesource.com/c/platform/frameworks/base/+/3664131) patch.\n\n - When the second field is auto-filled, such as `PASSWORD`, the\n `LoginActivity` is behind `decor_grip`, and loses the input focus.\n Patches can be found in the following links: [ag/3679541](https://android-review.googlesource.com/c/platform/packages/services/Car/+/3679541),\n [ag/3675628](https://android-review.googlesource.com/c/platform/frameworks/base/+/3675628), [ag/3675627](https://android-review.googlesource.com/c/platform/frameworks/base/+/3675627)."]]
