On Sat, 2016-08-20 at 21:34 +0300, Tanu Kaskinen wrote:
> On Sat, 2016-08-20 at 11:18 -0700, James Bottomley wrote:
On Sat, 2016-08-20 at 21:03 +0300, Tanu Kaskinen wrote:
> > > Also, pulseaudio doesn't manage when profiles are connected or
> > > disconnected, and starting to do that (and
Hi,
On Sat, Aug 20, 2016, James Bottomley wrote:
> > To clarify, is the problem that bluez has some arbitrary limitation
> > that it's not possible to connect both HFP and HSP? AFAIK bluetooth
> > doesn't allow two simultaneous audio streams, but I guess that's not
> > the problem here?
>
> No,
On Sat, 2016-08-20 at 21:34 +0300, Tanu Kaskinen wrote:
> On Sat, 2016-08-20 at 11:18 -0700, James Bottomley wrote:
> > On Sat, 2016-08-20 at 21:03 +0300, Tanu Kaskinen wrote:
> > > To clarify, is the problem that bluez has some arbitrary
> > > limitation that it's not possible to connect both
On Sat, 2016-08-20 at 11:18 -0700, James Bottomley wrote:
> On Sat, 2016-08-20 at 21:03 +0300, Tanu Kaskinen wrote:
> > To clarify, is the problem that bluez has some arbitrary limitation
> > that it's not possible to connect both HFP and HSP? AFAIK bluetooth
> > doesn't allow two simultaneous
On Sat, 2016-08-20 at 21:03 +0300, Tanu Kaskinen wrote:
> On Sat, 2016-08-20 at 10:28 -0700, James Bottomley wrote:
> > I actually ran into a problem with the approach. It's not really a
> > pulseaudio problem per-se, it's a bluetooth/bluez one: bluez can't
> > talk simultaneously to both HFP
On Fri, 2016-08-19 at 22:33 +0300, Tanu Kaskinen wrote:
> On Thu, 2016-08-18 at 11:14 -0700, James Bottomley wrote:
> > When all headsets supported both HSP and HFP, life was good and we
> > only needed to implement HSP in the native backend. Unfortunately
> > some headsets have started
On Fri, 2016-08-19 at 22:33 +0300, Tanu Kaskinen wrote:
> On Thu, 2016-08-18 at 11:14 -0700, James Bottomley wrote:
> > When all headsets supported both HSP and HFP, life was good and we
> > only needed to implement HSP in the native backend. Unfortunately
> > some headsets have started
On Thu, 2016-08-18 at 11:14 -0700, James Bottomley wrote:
> When all headsets supported both HSP and HFP, life was good and we
> only needed to implement HSP in the native backend. Unfortunately
> some headsets have started supporting HFP only. Unfortuantely, we
> can't simply switch to HFP only
When all headsets supported both HSP and HFP, life was good and we
only needed to implement HSP in the native backend. Unfortunately
some headsets have started supporting HFP only. Unfortuantely, we
can't simply switch to HFP only because that might break older HSP
only headsets meaning we need
