실제 및 가상 디스플레이를 비롯한 여러 디스플레이에 UXRE 지원을 추가했습니다. 이렇게 하면 실제 디스플레이 또는 가상 디스플레이에 관계없이 디스플레이별로 서로 다른 UXRE를 적용할 수 있습니다. 디스플레이는 UXRE 구성의 자동차 탑승자 영역 내에서 식별할 수 있습니다. 이렇게 하면 운전자가 운전하는 동안 동승자 전용 디스플레이에서 NDO 앱을 계속 사용할 수 있습니다.
이제 Android 소스 트리 외부에서 드라이버 UI 및 클러스터 개발을 사용 설정할 수 있습니다.
이제 운전자 UI가 알림을 생성할 수 있는지 모니터링할 수 있습니다.
연결
블루투스
블루투스 헤드셋 사용자가 연결된 휴대전화와 함께 블루투스 헤드셋을 AAOS에 연결하고 헤드셋을 오디오 출력 장치로 사용할 수 있습니다.
사용자는 오디오 설정 페이지 세트에서 새 오디오 출력 장치 설정을 사용하여 헤드셋을 출력 장치로 지정할 수 있습니다. 블루투스를 통해 한 번에 하나의 미디어 또는 오디오 스트림만 소스 또는 싱크에서 활성화할 수 있습니다.
기본 로그 수준 이제 개발자 옵션에서 또는 새 log.tag.bluetooth 로깅 태그를 사용하여 명령줄에서 블루투스 스택의 기본 로그 수준을 제어할 수 있습니다.
자동차 속성 실적 개선. CPU 부하를 줄이기 위해 Continuous 및 On_Change 속성을 업데이트했습니다.
센서 데이터를 구독할 때 구성 가능한 해상도입니다. CPM 수준에 새 registerCallback API를 추가하고 CarPropertyService 및 VHAL 인터페이스에 로직을 추가했습니다.
VHAL: 액세스 모듈 세분화. 이제 OEM은 전체 속성에 액세스 수준을 지정하는 대신 propertyId-areaId 조합별로 액세스 수준(예: READ-only 및 READ-WRITE)을 지정할 수 있습니다.
규정 준수
Android 규정 준수 테스트는 내부 참조용 하드웨어에서 실행되었습니다. 이 출시에서 실행되는 테스트 모음에는 CTS, STS, VTS, CTSonGSI가 포함됩니다.
다음 문제를 제외하고 Android 15 코드 (android15-release) 또는 Android 15 테스트 브랜치(android15-tests-dev)에서 수정이 필요한 알려진 오류는 발견되지 않았습니다.
CTS-Verifier 선택기 결과
기기가 자동차 세로 모드 UI를 기반으로 하는 경우 이전에 나열된 테스트 외에도 이러한 테스트가 실패할 수 있습니다.
CTS.CtsWindowManagerDeviceWindow
CTS.CtsWindowManagerDeviceMultiDisplay
CTS-Verifier 상태 표시줄 사용 중지
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-06-11(UTC)
[[["이해하기 쉬움","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-06-11(UTC)"],[],[],null,["# Android Automotive 24Q3\n\nThis page summarizes new major features provided in Android Automotive 24Q3.\n\nFeatures\n--------\n\n### Car framework\n\n#### Display and window manager\n\nTo learn more, see\n[Instrument Cluster API](/docs/automotive/displays/cluster_api).\n\n1. **Added UXRE support on multiple displays, including physical and virtual\n displays.** This enables different UXREs to be applied on a per-display basis, whether a physical or a virtual display. Displays can be identified within a car occupant zone in the UXRE config. This allows for passenger-only displays to continue to use NDO apps while driving.\n\n#### Audio and radio\n\nTo learn more, see\n[Radio control implementation](/docs/automotive/radio/radio-control-implementation).\n\n1. **Min and max volume levels.** OEMs can now define minimum and maximum\n volume levels to prevent sounds from being too quiet or too loud when\n activated.\n\n2. **Dynamic audio devices.** Allows audio configurations with dynamic output\n devices, such as Bluetooth and USB headphones, to be selected by the user\n when the devices are connected.\n\n3. **Audio crossover fade configurations.** OEMs can now define crossover fade\n configurations for automotive devices, which can be applied to apps upon\n audio playback.\n\n4. **Improve support HD and DAB radio.** Fully support the HD and DAB radio\n standards so that OEMs can integrate radio features in automotive devices.\n\n#### Performance and system health\n\nTo learn more, see\n[Collect performance data](/docs/automotive/watchdog/wd_performance_health)\nand [Monitor system health](/docs/automotive/watchdog/wd_system_health).\n\n1. **Richer instrumentation for system performance issues.** The CarWatchdog dumpsys proto reports cached metrics in a structured format for easier analysis. CarWatchdog memory profiling is used to better understand the impact of memory pressure on performance.\n\n#### Power management\n\nTo learn more, see [Power management](/docs/automotive/power/power).\n\n1. **Serverless remote access.** Added the ability to enable other ECUs, such\n as the TCU, to trigger AAOS activity and for AAOS to schedule its own\n wake-ups to process a queue of tasks.\n\n2. **Emergency shutdown support.** Improves the car power management service to\n alert system apps that an emergency condition has triggered a shut-down.\n\n3. **Power policy controls.** Allows OEM system apps to change power policy\n according to the situation.\n\n### Multi-display\n\n1. You can enable the communication between the same apps running in different occupant zones using the [Multi-Display Communications API](/docs/automotive/displays/multi-display-comms-api).\n\n### Safety display\n\n1. You can now enable driver UI and cluster development outside the Android\n source tree.\n\n2. You can now monitor the Driver UI can generate alerts and notifications.\n\n### Connectivity\n\n#### Bluetooth\n\n1. **Bluetooth headsets.** Allows users to connect Bluetooth headsets to AAOS,\n alongside connected phones, and to use headsets as an audio output device.\n The user can use the new **Audio Output Device** setting on the **Audio\n Settings** pageset to designate their headset as an output device. Only one\n media or audio stream can be active over Bluetooth at a time, source or\n sink.\n\n2. **Default Log Level.** You can now control the default log level of the\n Bluetooth stack from **Developer Options** or on the command line using the\n new `log.tag.bluetooth` logging tag.\n\n#### Networking\n\nTo learn more, see\n[Maintain hotspots between driving sessions](/docs/automotive/connectivity/persist-access-point).\n\n1. **Data and subscription plan messaging.** A reference UX to present the\n option to renew paid connectivity at the user's point of need.\n\n2. **OEM-paid Wi-Fi.** A reference UX for showing connections to restricted\n Wi-Fi networks.\n\n3. **Wi-Fi hotspot persistence.** Added a toggle to allow users to retain the\n vehicle hotspot for every drive.\n\n#### UWB\n\n1. **Settings update.** Added new options to provide more control of UWB devices.\n\n### System UI and core apps\n\n1. **Config aware System UI.** Broaden the capabilities of AAOS emulators by\n supporting simulated multiple device configurations using a single system\n image.\n\n2. **Compatibility improvements.** Made improvements to third party app facing\n compatibility through the inclusion of core Android functionality, such as\n DocumentsUI and Gallery.\n\n3. **Dock.** Allow users to *pin* favorite apps to the system UI space to more\n quickly launch apps.\n\n4. **Ambient view.** Provide OEMs with a space in which to create\n differentiated experiences when IVI screens are turned on but not in use\n\n5. **Refreshed profile lock challenge.** Added a standardized screen lock\n challenge across Android Automotive.\n\n### Camera\n\nTo learn more, see [Camera](/docs/automotive/camera).\n\n1. **Improved support for EVS concurrent multi-camera clients.** Improved\n multi-camera and multi-client support in `CarEvsService`, allowing clients\n to manage data streams more efficiently.\n\n2. **Camera2 user0 access.** Enable apps running in the headless user to access\n Camera2.\n\n3. **Camera2 privacy allowlist.** OEMs can now designate certain camera apps to\n be allowlisted to access cameras regardless of the state of camera privacy\n toggle.\n\n4. **Camera2 early access.** Privileged clients with `UID AID_AUTOMOTIVE_EVS`\n can now access the camera before an Android boot is completed.\n\n### Sensors and VHAL properties\n\nTo learn more, see\n[Supported system properties](/docs/automotive/vhal/system-properties).\n\n1. **Ultrasonic sensors.** Added new VHAL properties for ultrasonic parking\n sensors.\n\n2. **Driver monitoring.** Added new VHAL properties for driver attention\n monitoring systems.\n\n3. **New VHAL properties.** Added 10 new VHAL properties.\n\n4. **Car property performance improvements.** To reduce CPU load, updated the\n `Continuous` and `On_Change` properties.\n\n5. **Configurable resolution when subscribing to sensor data.** Added a new\n `registerCallback` API at the CPM level and added logic to the\n `CarPropertyService` and VHAL interface.\n\n6. **VHAL: Access module granularity.** OEMs can now specify access levels\n (such as `READ-only` and `READ-WRITE`) per `propertyId-areaId` combinations\n instead of specifying access levels for an entire property.\n\nCompliance\n----------\n\nAndroid compliance tests were executed on internal reference hardware. Test\nsuites run for this release include CTS, STS, VTS, and CTSonGSI.\n\nExcept for the following issues, we discovered no known failures requiring a fix\neither in Android 15 code (`android15-release`) or in the Android 15 test branch\n(`android15-tests-dev`).\n\n- **CTS-Verifier.** Chooser result.\n\nIf your device is based on the Car Portrait UI, these tests might fail, in\naddition to those listed previously.\n\n- **CTS.** `CtsWindowManagerDeviceWindow`\n- **CTS.** `CtsWindowManagerDeviceMultiDisplay`\n- **CTS-Verifier.** Disable the status bar\n\n| **Note:** Fixes for these items, and any other required compliance patches, can be found in the [Android Open Source Project](https://android-review.googlesource.com/q/hashtag:%22aaos-24q3-cts%22+%28status:open%20OR%20status:merged%29). Changes provided here will be provided in the Android 15 24Q4 release."]]
