Topics / Priority (high, medium, low) | Suhasini | Andrey | Stefan K | Piotr | Wassim | Gunnar | |
---|---|---|---|---|---|---|---|
we have a portfolio of audio processors and an automotive audio bus to distribute audio within the car, we want to configure our proprietary audio bus SW stack to use it with AA as we did for Linux | |||||||
we want to determine whether we have a problem of bandwith when using our proprietary network with AA, one approach is to use shared memory transfer | |||||||
configuration of Automotive overlay, there is not much tool to configure the AA system | |||||||
there is no way to control the equalization, i.e. no simple way to control global effects for output streams (by default Android application controls its own tracks) | |||||||
there is no Audio calibration interface | |||||||
there is a need for a generic interface for controlling audio effects on HAL level, global effects are designed for input streams but control over them is limited by interface | |||||||
early audio for RVC (Rear View Camera) or other services | |||||||
configuration management component for TinyALSA | |||||||
Audio Focus doesn't forbid to interrupt Audio, Android 10 provides additional interface for Automotive to solve this problem | |||||||
| |||||||
| |||||||
patches for handsfree management, combination of BT stream with other streams, how to enable the correct audio routing, documentation on the Audio HALis missing, it is difficult to find examples on line | |||||||
I/O for our Bosch HW, the challenge is to adapt the AA framework to our HW, which has for instance 4 audio channels while we need to present them as 2 audio channels to AA | |||||||
Android does not implement all features required by customer.
| |||||||
Android Audio subsystem is developed only for infotainment purposes. Safety-related features need to be implemented in another RTOS
| |||||||
Android way of extending its functionality is developing vendor extensions without modification of the framework.
| |||||||
|