Hi, On Tue, Oct 11, 2011 at 9:19 AM, Lin, Mengdong <mengdong.lin@xxxxxxxxx> wrote: >> > 4. Is there anyone could explain sco_sink, sco_source? If there are ALSA >> > code related to it, could you tell me the link that explain ? > >> … Apparently some system don't even bother >> exporting this audio path to the software stack because it is only >> active while on call, if this is your case then it means we cannot >> control the audio routing in software and we probably should do >> nothing (e.g. set sco_sink/sco_source to "none" and when HFP/HSP is >> active set card profile to 'Off'), but note that this type of >> configuration has many limitation for instance a system like that >> cannot do navigation or voice commands using SCO. > > Hi Luiz, > > Would you kindly share more information on a system that does not export SCO audio path to the software stack? Is it a typical design for handset? Apparently it is common design in handset world, but probably not so common in smartphones where some other use cases need to be supported such as navigation, voice command and voip calls. > If I have a BT headset that can support both A2DP and HSP profile, and I want to hear music in A2DP and make a phone call in HSP profile on such a system, is it possible? > If it’s possible, how can pulseaudio set BT headset to A2DP profile for music and change to ‘Off’ profile on call? Can PA know when a call begins or ends on such a system, in order to change BT profile? If you mean simultaneously A2DP stream and SCO then probably not, most headset simple cannot do audio mixing so it is either SCO _or_ A2DP, also there are recommendation to always switch the profiles but not to use them simultaneously e.g. suspend A2DP streaming while SCO is connected. As for PA knowing when to switch we probably need to work on that, other systems like MeeGo harmattan have external components to do that, but IMO it would have been much better to have such thing directly in PA as a module. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
