Created attachment 802964 [details] [diff] [review] WIP AudioPolicyManager 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.
Created attachment 802999 [details] [diff] [review] WIP AudioPolicyManager, v2h 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
Created attachment 803059 [details] [diff] [review] WIP AudioPolicyManager, v3 I've fleshed out the implementation. We'll need an audiopolicy counterpart in gaia.
Attachment #802999 - Attachment is obsolete: true
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.
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.
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.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.