<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style></style></head><body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'><div class=WordSection1>I found the module-echo-cancel's "Echo-Cancel Source Stream" can be created on a monitor source of an new created ALSA sink by mistake, if the real ALSA source is not created yet. <o:p></o:p>Could anyone tell me how to fix this issue?<o:p></o:p><o:p> </o:p>On my MeeGo platform, the ALSA sink/source don’t always exist because the ALSA and Bluetooth HSP headset share one hardware data link. So when BT HSP headset is connected, ALSA card will change into a “hsp” profile , remove the “normal” ALSA sink/source pair and create a “hsp” sink/source pair for BT. And after BT HSP headset is disconnected, ALSA card restores its original profile, remove “hsp” sink/source and create “normal” ALSA sink/source again.<o:p></o:p><o:p> </o:p>My problem is that when BT HSP is disconnected during a phone call, I got the above routing error and a pa deadlock described in another loop: <a href="http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-July/010741.html">http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-July/010741.html</a><o:p></o:p>The module-echo-cancel is loaded again when the VOIP stream is routing back to the new created ALSA sink. But because the ALSA source is not created yet (will be later), PA routes the “Echo-Cancel Source Stream” to the monitor source of the ALSA sink.<o:p></o:p><o:p> </o:p>How to make “Echo-Cancel Source Stream” link to the right ALSA source, which will be created a little later?<o:p></o:p><o:p> </o:p>Here is the log:<o:p></o:p>I  source.c: Created source 8 "alsa_output.platform-pmic_audio.19.intelmadihfheadset.echo-cancel.monitor" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right<o:p></o:p>I  source.c:     device.description = "Monitor of Echo-Cancel Sink alsa_output.platform-pmic_audio.19.intelmadihfheadset.echo-cancel on Intel MAD intelmadihfheadset"<o:p></o:p>I  source.c:     device.class = "monitor"<o:p></o:p>I  source.c:     device.icon_name = "audio-input-microphone"<o:p></o:p>D  classify.c: find_group_for_client (|<null>|0|-1|) => othermedia<o:p></o:p>D  module-suspend-on-idle.c: Sink alsa_output.platform-pmic_audio.19.intelmadihfheadset becomes busy.<o:p></o:p>D  memblockq.c: memblockq requested: maxlength=33554432, tlength=0, base=4, prebuf=0, minreq=1 maxrewind=0<o:p></o:p>D  memblockq.c: memblockq sanitized: maxlength=33554432, tlength=33554432, base=4, prebuf=0, minreq=4 maxrewind=0<o:p></o:p>I  source-output.c: Created output 2 "Echo-Cancel Source Stream" on alsa_output.platform-pmic_audio.19.intelmadihfheadset.monitor with sample spec s16le 2ch 44100Hz and channel map front-left,front-right<o:p></o:p>I  source-output.c:     media.name = "Echo-Cancel Source Stream"<o:p></o:p>I  source-output.c:     media.role = "filter"<o:p></o:p>E  module-echo-cancel.c: new source output <Echo-Cancel Source Stream> on source <alsa_output.platform-pmic_audio.19.intelmadihfheadset.monitor><o:p></o:p><o:p> </o:p>Thanks<o:p></o:p>Amanda<o:p></o:p></div></body></html>