<font color="#333333"><font face="tahoma,sans-serif">Hello,<br></font></font><br><div class="gmail_quote">On Wed, Sep 14, 2011 at 15:24, Colin Guthrie <span dir="ltr"><<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">'Twas brillig, and Alexander Skwar at 14/09/11 11:25 did gyre and gimble:<br><br></blockquote><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
So really this is not about using A2DP and HSP at the same time, it's<br>
about graceful hand over from one mode to the other.<br>
<br></blockquote><div><br>Hm. I think it's also about how to setup the VoIP app to use<br>an input device, which it doesn't see (in A2DP mode, there's<br>no "mic on headset" device which could be selected).<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><div class="im">
> This is with the Phonon backend of KDE 4.6.0 of openSUSE 11.4.<br>
<br>
</div>NB The phonon backend itself is irrelevant.<br>
<div class="im"><br></div></blockquote><div><br>Is it? I don't know - in Phonon, I cannot select the headset as<br>an input device, because it's just greyed out (as long as it is<br>in A2DP mode). I don't know what's the cause of this limitation,<br>
Phonon, PulseAudio, Bluez…<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
It's really not all that difficult. In fact you could easily wire up a<br>
small script to your panel just now that flipped the profile for the<br>
bluetooth device between A2DP and HSP so that when you answer a call,<br>
you just click the "flip" launcher and the profile will change. </blockquote><div><br>I think that this is too late. In the VoIP app, I need to configure<br>which device is to be used for getting the input ("where's the<br>
microphone", so to say).<br><br>If BT is in A2DP mode, I cannot set it so, that the app uses the<br>headset as the input device which is to be used.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
And your<br>
VOIP clients will automatically use the right mic and output device. So<br></blockquote><div><br>Will they? How? I mean, you'll have to specify which mic/output<br>device to use, don't you?<br><br>In A2DP mode, the app doesn't have any input device at all (ie.<br>
it's using the one from the on-motherboard-chip). Now a call comes<br>in. I fear that I'm not fast enough to <br><br>1) Fire the script and<br>2) Reconfigure the app<br><br>Step (2) takes too much time and I don't know if it would even<br>
handle that, if there's already an incoming call.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
it's only one extra click until you get the policy module in place,<br>
which I don't think is too much hassle.<br>
<br></blockquote><div><br>I think it's a two step process, where the 2nd step can take <br>quite some time.<br> <br>Cheers,<br></div></div><br>Alexander<br>-- <br>↯ Lifestream (Twitter, Blog, …) ↣ <a href="http://alexs77.soup.io/" target="_blank">http://alexs77.soup.io/</a> ↯<br>
↯ Chat (Jabber/Google Talk) ↣ <a href="mailto:a.skwar@gmail.com" target="_blank">a.skwar@gmail.com</a> , AIM: alexws77 ↯<br><br>