Closed
Bug 915130
Opened 12 years ago
Closed 7 years ago
Add audio policy management for PA
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mwu, Unassigned)
References
Details
Attachments
(1 file, 2 obsolete files)
|
12.15 KB,
patch
|
Details | Diff | Splinter Review |
I've been poking at a simple webapi to do audio policy management. This WIP doesn't quite work yet, and will require additional code in gaia.
| Reporter | ||
Comment 1•12 years ago
|
||
Port switching seems to work now. Need to check the port enumeration and add checking of the current port.
Attachment #802964 -
Attachment is obsolete: true
| Reporter | ||
Comment 2•12 years ago
|
||
I've fleshed out the implementation. We'll need an audiopolicy counterpart in gaia.
Attachment #802999 -
Attachment is obsolete: true
| Reporter | ||
Comment 3•12 years ago
|
||
I wonder if we need to expose the concept of different cards. We just assume card 0 here, but that probably won't hold up when we want to start handling bluetooth through here.
Comment 4•12 years ago
|
||
The interface seems reasonable to me. Also this idea is under discussing on w3c, they want to define the input/output device sleection, BTW, I have a question, for mobile device, some input/output device has the pair problem, should we throw exception if UA assign the HW don't support the kind of combination? Especially for the voice call case.
For the Bluetooth/UsbAudio case, I think the pluseaudio is a good start on TV system, it's routing policy is simple and usually don't contain the phone call case.
| Reporter | ||
Comment 5•12 years ago
|
||
Throwing an exception is fine, though I don't know how the audio policy code would recover from it. Maybe we just need to list all valid combos.
Comment 6•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•