[pulseaudio-discuss] Setting Bluetooth headset connection to *both* A2DP _AND_ HSP at the same time?

[Alexander Skwar]

Hello,

On Wed, Sep 14, 2011 at 15:24, Colin Guthrie <gmane at colin.guthr.ie> wrote:

> 'Twas brillig, and Alexander Skwar at 14/09/11 11:25 did gyre and gimble:
>
>

> So really this is not about using A2DP and HSP at the same time, it's
> about graceful hand over from one mode to the other.
>
>
Hm. I think it's also about how to setup the VoIP app to use
an input device, which it doesn't see (in A2DP mode, there's
no "mic on headset" device which could be selected).


>
> > This is with the Phonon backend of KDE 4.6.0 of openSUSE 11.4.
>
> NB The phonon backend itself is irrelevant.
>
>
Is it? I don't know - in Phonon, I cannot select the headset as
an input device, because it's just greyed out (as long as it is
in A2DP mode). I don't know what's the cause of this limitation,
Phonon, PulseAudio, Bluez…


>
> It's really not all that difficult. In fact you could easily wire up a
> small script to your panel just now that flipped the profile for the
> bluetooth device between A2DP and HSP so that when you answer a call,
> you just click the "flip" launcher and the profile will change.


I think that this is too late. In the VoIP app, I need to configure
which device is to be used for getting the input ("where's the
microphone", so to say).

If BT is in A2DP mode, I cannot set it so, that the app uses the
headset as the input device which is to be used.


> And your
> VOIP clients will automatically use the right mic and output device. So
>

Will they? How? I mean, you'll have to specify which mic/output
device to use, don't you?

In A2DP mode, the app doesn't have any input device at all (ie.
it's using the one from the on-motherboard-chip). Now a call comes
in. I fear that I'm not fast enough to

1) Fire the script and
2) Reconfigure the app

Step (2) takes too much time and I don't know if it would even
handle that, if there's already an incoming call.


> it's only one extra click until you get the policy module in place,
> which I don't think is too much hassle.
>
>
I think it's a two step process, where the 2nd step can take
quite some time.

Cheers,

Alexander
-- 
↯    Lifestream (Twitter, Blog, …) ↣ http://alexs77.soup.io/     ↯
↯ Chat (Jabber/Google Talk) ↣ a.skwar at gmail.com , AIM: alexws77  ↯
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20110914/568d22e6/attachment.htm>