Android 12 kommt für den Megane

Moin moin,

vorweg es handelt sich um keine offizielle Ankündigung aber es dürfte nach der Aussage so gut wie sicher sein.

In einem Video wird etwas über das neue Open R-Link System des Rafale gesprochen, interessant ist hier, dass erwähnt wird das der Megane und Austral auch ein Update auf Android 12 bekommen sollen, man hierfür aber zum Händler muss.

Das wäre das erste richtig große Update für den Megane auch wenn es bei den Neuerungen bei Android 12 gegenüber Android 10 an Renault liegen wird diese vernünftig zu Implementieren.

Video ist auf französisch, aber mit automatisch übersetzen Untertiteln kann man es doch verstehen.

Klick zur Stelle im Video

Hier einmal der Changelog von Android 10 auf 11:

Major Features and Enhancements

System UI and Core Apps Improvements

• Updated core system applications
• New Settings search. Users can now quickly search for the relevant setting from the Settings Home Screen.

Media. Other features have been added for improved user experience, Customization enhancement for OEMs.Dialer. Option has been added to sort by last name for improved user experience.Messaging. Group Messages are now supported using MMS and RCS.Improved flexibility for notifications. Capability has been added for improved customizability for on-screen position for notifications panel and heads-up notifications, and for improved customizability for heads-up notification animations.Improved customizability for status bar icons. Spacing between icons can be customized, some icons can now be excluded.Automotive UI toolkit. A new set of components and resources have been added to allow for easier, more predictable, and more consistent OEM customization of the system.Baseline rotary support. VHAL events for a physical rotary controller are plumbed through to RotaryController service so that the apps can be made to work with the rotary controller.

User Management

• Updated Multi-User APIs. Moved Android AutomotiveOS multi-user management API surface (e.g. CarUserManagerHelper) into core framework (for example, UserManager) to make OEM integration and upgradability easier.
• User roles and restrictions. Support has been added for easier OEM customization of User roles and restrictions.
• Faster user switching. User switching and multi-user performance has been improved. User pre-creation and removing packages from system user is possible now.
• CarUserHAL. User management (for example, switch Users) integration between external ECUs and Android is now supported.
• Trusted device unlocking.Improvements have been made to unlocking performance of Users and system experience

Bluetooth

• Cover art. Cover art for currently playing and browsed tracks via AVRCP can now be received.
• MMS and RCS. Sending and receiving MMS and RCS messages are now supported in addition to SMS.
• Vendor AT commands. Capability has been added to support sending vendor AT commands over HFP to enable 3P projection.
• Synchronization of favorite contacts. Favorites phone book can now be transferred from phone to car.
• Improve support for multiple browsable media sources. Improved support for signals from phones supporting multiple media players, and changing of those media players.
• AVRCP improvements. Media control capability has been improved.
• Contact downloads.Contact downloads are now batched to get available contacts into the database sooner.

Multiple Displays

• Emulator support. Android Automotive OS emulator now supports multiple physical displays.
• Boot animation for multiple displays.Multi display boot animation is now supported.
• CarActivityView. ActivityView is now aware of the driving restrictions.

Connectivity

• Hotspot client browsing and management. Partners can now view a detailed list of connected AP clients and display or block clients.
• Dynamic Wi-Fi interface management. Support has been added to create and remove Wi-Fi network interfaces dynamically to support Wi-Fi concurrency use cases and reduce fragmentation around current one-off implementations.
• Silent wireless connection to Automotive HUs. Privileged apps can now be silently connected to Wi-Fi.

Audio

• Audio effects per output device. Audio effects to specific output devices in addition to per-stream can be applied now.
• Multi-zone improvements. Multi-zone audio now supports routing based on user and car occupancy. Additionally, audio inputs can be associated with zones for easier device lookups.
• Supporting vehicle sounds. New system usages have been introduced to cover automotive use cases. Also, new APIs have been added to enable the HAL to participate in audio focus for sounds outside of Android.
• Audio focus improvements. Delayed audio focus requests are now supported, and a new user setting for preventing navigation from gaining focus during a call has been added.

Camera

Surround view. Capability has been added to display 360° surround view from multiple camera inputs.

Computer Vision and Machine Learning (CV and ML)

Computepipe on Android Automotive OS. A CVML client implementation in Android now allows connecting with CVML pipelines regardless of which environment they are running in (VM or discrete HW) in a manner that abstracts the underlying deployment architecture.

Sensors

• Ultrasonics. Support for ultrasonic sensor arrays has been added to the platform.
• CarPropertyManager. Improvements have been made to permission granularity for the Vendor property, exposed error callback, and a simplified getProperty API.
• Country detector. Allow Automotive customization to enable OEMs to set a country code other than the default for location detection (specifically for cases in which there is no telephony provision in a car).
• GNSS. Unlimited satellite can now be reported (increased from the maximum of 64 previously supported.

System Reliability and Stability

Watchdog has been added to detect problematic process and restart it.

Boot Performance

IO performance data is collected now as part of CarWatchDog service.

Car Framework

• Optional and experimental features are now supported.
• The capability has been added for activity crash monitoring and restart for crashed activity running in a cluster (FixedActivity mode).
• Car service crash handling has been improved.
• CarOccupantZoneManager API has been added to allow querying the right display/audio for specific usage.
• CarInputManager has been added to enable the capturing of a selected group of input events.
• CAN bus HAL for standardized CAN bus access has been added.

Power Management

Power management service logic now supports new transitions. WAIT_FOR_VHAL_FINISH to WAIT_FOR_VHAL, and SHUTDOWN_PREPARE to sleep immediately.

Bug Fixes

Multiple bug fixes and compliance test fixes have been made.

Known Issues

• xTS run on emulator and not on a compliant device.
• Performance benchmarking has not been performed.

Sowie Android 11 auf Android 12:

System UI and core apps improvements

• Quick Controls feature. Enables OEMs to add selected settings (for example, Bluetooth toggles) to SysUI (for example, the Status bar) to enable users to change key settings safely while driving, without opening the Settings app.
• Rotary support. Improvements and bug fixes.
• UI Customization. Enabled plugin architecture for custom classes. See Car UI Plugins for details.
• Notification visual overhaul. UX overhaul and grouped notifications improvements.

Bluetooth

• Improved Bluetooth reconnection performance. Automatically connect to devices more often and under the right circumstances. To learn more, see Bluetooth connection management.
• Messaging database. Support for using a messaging database through the Message Access Profile (MAP) to provide more flexibility to messaging apps that rely on Bluetooth.

Connectivity

• Per-Application Network Selection (PANS). Enable the creation and enforcement of a dynamic network policy that determines which applications can use OEM_PAID networks.
• Dual STA. Enable the IVI to connect to an OEM restricted Wi-Fi network, concurrently with a primary connection to a Wi-Fi network.

Audio

• Audio ducking signal. Provides HAL with audio focus state and information on what output devices to duck.
• Volume improvements. Enable for finer control of volume, including providing and API to get active volume groups.
• Muting per volume group. Enable per volume group muting and enhance HAL and UI communication about the mute states.
• AIDL migration for the AudioControl HAL. Migrated the AudioControl HAL from HIDL to AIDL to fully use AIDL functionality.
• Power policy handling for Audio. Enabled power handling functionality for the car audio service, including disable and enable focus requests, and mute and unmute volume groups on power policy changes for audio.

Camera

• CarEvsManager. Enables OEMs to implement Android Activity that shows the preview from automotive camera services.

System reliability and stability

• Car watchdog flash memory management. Manages system flash memory by limiting the amount of data written to storage. Enables OEMs to define the write thresholds (for OEM, media, and maps packages) and collect statistics for OEM applications. Disables and terminates non-critical applications and services that exceed defined thresholds.

Security

• Vehicle bound encryption. Android storage encryption can now be configured to store some key encryption parameters on an external ECU. This prevents the harvesting of data by removing the head unit from the car (for example, due to theft or relegated to a junkyard).
• Secure developer options. Android developer options and ADB can be remotely enabled exclusively by an OEM. Reference implementation provides crypto token access mechanisms and remote web service.

Location

• Advanced driver-assistance systems (ADAS) location switch. Access to device location for apps used for ADAS can now be controlled with a separate location switch in the Settings app.

Telemetry

• Edge-based analytics capability. Enables the ability to perform more edge-based metrics processing on Android Automotive devices. Android infotainment and vehicle property metrics can be configured in scripts written in the Lua language and processed on-device to be sent to the backend of OEM choosing.

Compliance

• Compliance fixes. A number of patches ensure compliance with the Android certification test suites. The Android 12L AAOS Release is 100% compliant on CTS, CTS-Verifier, and STS test suites on our internal reference platform with no additional fixes needed in the AOSP software.

Er meint das kleine Hauptdisplay, das hat kein Android Automotive.