Re: [pulseaudio-discuss] Bluetooth Headset Problem with BlueZ-5.38 and Pulseaudio 8.0

2016-08-20 Thread Tanu Kaskinen
On Fri, 2016-08-19 at 13:57 +0700, Hieu Le wrote: > I'm trying to get a SPK-ProHT Bluetooth speaker and headset working on an > embedded Linux board but when I failed to use pacmd set-card-profile to > choose headset_head_unit profile. Checking pulseaudio lof file, it seems > backend-native cannot

Re: [pulseaudio-discuss] Bluetooth Headset Problem with BlueZ-5.38 and Pulseaudio 8.0

2016-08-20 Thread Georg Chini
On 20.08.2016 13:40, Tanu Kaskinen wrote: On Fri, 2016-08-19 at 13:57 +0700, Hieu Le wrote: I'm trying to get a SPK-ProHT Bluetooth speaker and headset working on an embedded Linux board but when I failed to use pacmd set-card-profile to choose headset_head_unit profile. Checking pulseaudio lof

Re: [pulseaudio-discuss] [PATCH v6 17/25] loopback: Track and use average adjust time

2016-08-20 Thread Tanu Kaskinen
On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: > > @@ -79,11 +79,18 @@ struct userdata { >   >  pa_time_event *time_event; >   > +/* Variables used to calculate the average time between > + * subsequent calls of adjust_rates() */ > +pa_usec_t time_stamp; "time_stamp" is

Re: [pulseaudio-discuss] Bluetooth Headset Problem with BlueZ-5.38 and Pulseaudio 8.0

2016-08-20 Thread Tanu Kaskinen
On Sat, 2016-08-20 at 14:14 +0200, Georg Chini wrote: > On 20.08.2016 13:40, Tanu Kaskinen wrote: > > > > On Fri, 2016-08-19 at 13:57 +0700, Hieu Le wrote: > > > > > > I'm trying to get a SPK-ProHT Bluetooth speaker and headset working on an > > > embedded Linux board but when I failed to use

Re: [pulseaudio-discuss] [PATCH v6 17/25] loopback: Track and use average adjust time

2016-08-20 Thread Georg Chini
On 20.08.2016 14:23, Tanu Kaskinen wrote: On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: @@ -79,11 +79,18 @@ struct userdata { pa_time_event *time_event; +/* Variables used to calculate the average time between + * subsequent calls of adjust_rates() */ +pa_usec_t

Re: [pulseaudio-discuss] [PATCH v6 17/25] loopback: Track and use average adjust time

2016-08-20 Thread Tanu Kaskinen
On Sat, 2016-08-20 at 14:55 +0200, Georg Chini wrote: > On 20.08.2016 14:23, Tanu Kaskinen wrote: > > > > On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: > > > > > > > > > > > @@ -79,11 +79,18 @@ struct userdata { > > >    > > >   pa_time_event *time_event; > > >    > > > +/*

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread Tanu Kaskinen
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

Re: [pulseaudio-discuss] [PATCH v6 18/25] loopback: Limit controller step size to 2.01‰

2016-08-20 Thread Georg Chini
On 20.08.2016 17:24, Tanu Kaskinen wrote: On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: The current loopback controller can produce a rate jump of up to 1% at startup. This might be audible, so implement a similar controller that will be used in the initial iterations and has a 2‰

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread James Bottomley
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

Re: [pulseaudio-discuss] [PATCH v6 18/25] loopback: Limit controller step size to 2.01‰

2016-08-20 Thread Tanu Kaskinen
On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: > The current loopback controller can produce a rate jump of up to 1% at > startup. This > might be audible, so implement a similar controller that will be used in the > initial > iterations and has a 2‰ limit to the step size. Once the

Re: [pulseaudio-discuss] [PATCH v6 18/25] loopback: Limit controller step size to 2.01‰

2016-08-20 Thread Tanu Kaskinen
On Sat, 2016-08-20 at 17:39 +0200, Georg Chini wrote: > On 20.08.2016 17:24, Tanu Kaskinen wrote: > > > > On Sun, 2016-06-05 at 21:05 +0200, Georg Chini wrote: > > > > > > The current loopback controller can produce a rate jump of up to 1% at > > > startup. This > > > might be audible, so

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread James Bottomley
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

[pulseaudio-discuss] [PATCH v2 2/3] bluetooth: separate HSP and HFP

2016-08-20 Thread James Bottomley
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

[pulseaudio-discuss] [PATCH v2 3/3] bluetooth: add correct HFP rfcomm negotiation

2016-08-20 Thread James Bottomley
HFP 1.6 requires a stateful negotiation of AT commands. The prior version got away with initialising HFP simply by replying 'OK' to every negotiation attempt. This one actually tries to parse the state and make sure the negotiation occurs correctly Signed-off-by: James Bottomley

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread James Bottomley
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

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread Johan Hedberg
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,

[pulseaudio-discuss] [PATCH v2 1/3] bluetooth: use consistent profile names

2016-08-20 Thread James Bottomley
The PA_BLUETOOTH_PROFILE names should mirror the PA_BLUETOOTH_UUID names using profile_function instead of randomly made up names. Fix this with the transformation: PA_BLUETOOTH_PROFILE_HEADSET_HEAD_UNIT -> PA_BLUETOOTH_PROFILE_HSP_HS PA_BLUETOOTH_PROFILE_HEADSET_AUDIO_GATEWAY ->

Re: [pulseaudio-discuss] [PATCH] bluetooth: separate HSP and HFP

2016-08-20 Thread James Bottomley
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

[pulseaudio-discuss] [PATCH v2 0/3] use bluetooth HFP in pulseaudio when available

2016-08-20 Thread James Bottomley
This is round 2 of the initial bluetooth: separate HSP and HFP patch. It includes the review feedback and a global on/off switch just in case there's a problem headset with dual HFP/HSP but non-working HFP. This one now includes a proper rfcomm negotiation (see patch 3). James Bottomley (3):