You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
| Topics / Priority (high, medium, low) | Category (all TBC) | Suhasini | Andrey | Mobis all TBC | Stefan K | Piotr | Wassim Alexander | Gunnar |
|---|
| 1 | Networked audio devices - need for a better support (of the configuration) of networked audio devices.
- currently Android can view only a single device / sound card.
- an audio network in car might have multiple devices that need to be controlled by the Android OS.
- related need: a silicon vendor has a portfolio of audio processors and an automotive audio bus to distribute audio within the car, and want to configure their proprietary audio bus SW stack to use it with AA as they did for Linux
| Source Management | High | High |
|
| Medium |
|
|
| 2 | Overall configuration management |
|
|
|
|
|
|
|
|
| configuration of automotive overlay, there is not much tool to configure the AA system | Configuration | Medium | Low |
|
| Medium |
|
|
| configuration management component for TinyALSA | Configuration | Medium | Medium |
|
| Medium |
|
|
| configuration challenge (look at slide 12 of tech summit deck) | Configuration | Medium | Low |
|
| High |
|
|
| 3 | Common Audio HAL | Common HAL
| High | Medium |
|
| High |
|
|
| 4 | Audio data transfer - streaming to a co-processor for post processing of audio from the HAL / other Android layers
- related,need: 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 in the audio HAL
| Common HAL
| High | High |
|
| High |
|
|
| 5 | Equalization - 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)
| Common HAL | High | High |
|
| High |
|
|
| 6 | Audio Calibration - there is no Audio calibration interface
| Common HAL | Medium | Medium |
|
| High |
|
|
| 7 | Controlling Audio Effects - there is a need for a generic interface for controlling audio effects at HAL level, global effects are designed for input streams but control over them is limited by the available interface
| Common HAL | High | High |
|
| High |
|
|
| 8 | Latencies | Performance | High | High |
|
| Medium |
|
|
| 9 | Multiple audio channels - the challenge is to adapt the AA framework to HW I/O, e.g. there are 4 audio channels that need to be presented as 2 audio channels to AA
| Common HAL | High | High |
|
| Low |
|
|
| 10 | Early audio - for RVC (Rear View Camera) or other services
| Common HAL | Low | Low |
|
| Medium |
|
|
| 11 | Source Management - Multi‐source multi‐sink
- Stream types – not audio zones
- Still limited to one sink
| Source Management | High | High |
|
| Low |
|
|
| 12 | Audio Focus - doesn't forbid to interrupt Audio, Android 10 provides additional interface for automotive applications to solve this problem
| Source Management | Low | Medium |
|
| Low |
|
|
| 13 | Bluetooth: patches for handsfree management, combination of BT stream with other streams, how to enable the correct audio routing, documentation on the Audio HAL is missing, it is difficult to find examples on line | Multi-Source Management | Low | Medium |
|
| Low |
|
|
| 14 | Android does not implement all features required by customer. (bullet points below will be distributed over the table) - Audio focus can be lost at any time
- Limited number of sources
- Limited number of priorities -2
- No easy way to support external amplifiers
- No priorities of phone call types.
| Multi-Source Management | High | High |
|
| - |
|
|
| 15 | Android Audio subsystem is developed only for infotainment purposes. Safety-related features need to be implemented in another RTOS - Need to share the same hardware between 2 OSes
- Running Android as a virtual machine inside RTOS leads to problems with scheduling of audio processes
| Multi-OS Integration | High | Medium |
|
| Medium |
|
|
| 16 | Android way of extending its functionality is developing vendor extensions without modification of the framework. - But in some cases you need to modify framework. There is a process for this, but slow. And changes needed to one customer / developer is not needed for another. Even if you do this, you have to wait until Tier 1 merges this change to its drop
- You have to retain compatibility for third-party apps
| Extensions | Medium | Medium |
|
| Low |
|
|
| 17 | Google is still very “hand wavy” about solution WR: Highly modified HAL, “virtual sources”, policy/focus management, flexible – data‐driven
| Configration, Tooling (e.g. IDL)
| Low | Low |
|
| Low |
|
|
| 18 | | Deliverables | Low |
|
|
|
|
|
|
