Franz Glauber | 7 Feb 16:27 2011
Picon

Re: Problems trying to connecf HFP device

I've talked this through with Padovan, but had no success on setting
up a new HFP device.

I can pair it, it recognizes the services Audio and Headset. I am also
able to connect the Headset service using D-Feet. When it does,
Pulseaudio is notified and attempt to configure it for use. The
revelant part seems to be this negotiation:

On bluetoothd:

bluetoothd[9596]: audio/unix.c:server_cb() Accepted new client
connection on unix socket (fd=24)
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[9596]: audio/unix.c:handle_sco_open() open sco -
object=/org/bluez/9596/hci0/dev_88_88_00_B9_CC_DD source=ANY
destination=ANY lock=readwrite
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_OPEN
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_SET_CONFIGURATION
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_SET_CONFIGURATION
(Continue reading)

Franz Glauber | 8 Feb 10:58 2011
Picon

Re: Problems trying to connecf HFP device

I'm cross-posting this from bluez, since I got no reply there and I'm
not sure wether this is a pulseaudio issue or a bluez.

I have a new HFP (mono headset). I can pair it, it recognizes the
services Audio and Headset. I am also able to connect the Headset
service using D-Feet. When it does, Pulseaudio is notified and attempt
to configure it for use. The revelant part seems to be this
negotiation:

On bluetoothd:

bluetoothd[9596]: audio/unix.c:server_cb() Accepted new client
connection on unix socket (fd=24)
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[9596]: audio/unix.c:handle_sco_open() open sco -
object=/org/bluez/9596/hci0/dev_88_88_00_B9_CC_DD source=ANY
destination=ANY lock=readwrite
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
BT_RESPONSE -> BT_OPEN
bluetoothd[9596]: audio/unix.c:client_cb() Audio API: BT_REQUEST <-
BT_SET_CONFIGURATION
bluetoothd[9596]: audio/unix.c:unix_ipc_sendmsg() Audio API:
(Continue reading)

Colin Guthrie | 13 Feb 21:20 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 08/02/11 09:58 did gyre and gimble:
> I'm cross-posting this from bluez, since I got no reply there and I'm
> not sure wether this is a pulseaudio issue or a bluez.

I'm not really much of an expert on BT stuff, but to me it looks like it
is at the bluez end, but what version of PA are you running? Ideally it
would be 0.9.22 or git master....

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Franz Glauber | 13 Feb 22:44 2011
Picon

Re: Problems trying to connecf HFP device



On Sun, Feb 13, 2011 at 6:20 PM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
'Twas brillig, and Franz Glauber at 08/02/11 09:58 did gyre and gimble:
> I'm cross-posting this from bluez, since I got no reply there and I'm
> not sure wether this is a pulseaudio issue or a bluez.

I'm not really much of an expert on BT stuff, but to me it looks like it
is at the bluez end, but what version of PA are you running? Ideally it
would be 0.9.22 or git master....

Yeah, I thought so... I'm using 0.9.22 (latest ebuild on Gentoo). Do you think it's worth trying the git version?

It seems that, given the delay before the error,  PA is waiting for some answer from the device, and that doesn't happen...

--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Colin Guthrie | 14 Feb 14:46 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 13/02/11 21:44 did gyre and gimble:
> Yeah, I thought so... I'm using 0.9.22 (latest ebuild on Gentoo). Do you
> think it's worth trying the git version?

I don't think there are any BT specific changes in git master that are
not also in stable-queue other that would affect this issue. That said,
there have been bluez related changes, so I could be wrong....

> It seems that, given the delay before the error,  PA is waiting for some
> answer from the device, and that doesn't happen...

Yeah that's what it looks like to me.

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Luiz Augusto von Dentz | 16 Feb 07:11 2011
Picon

Re: Problems trying to connecf HFP device

Hi,

On Sun, Feb 13, 2011 at 11:44 PM, Franz Glauber <franzec05 <at> gmail.com> wrote:
>
>
> On Sun, Feb 13, 2011 at 6:20 PM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
>>
>> 'Twas brillig, and Franz Glauber at 08/02/11 09:58 did gyre and gimble:
>> > I'm cross-posting this from bluez, since I got no reply there and I'm
>> > not sure wether this is a pulseaudio issue or a bluez.
>>
>> I'm not really much of an expert on BT stuff, but to me it looks like it
>> is at the bluez end, but what version of PA are you running? Ideally it
>> would be 0.9.22 or git master....
>
> Yeah, I thought so... I'm using 0.9.22 (latest ebuild on Gentoo). Do you
> think it's worth trying the git version?
>
> It seems that, given the delay before the error,  PA is waiting for some
> answer from the device, and that doesn't happen...

It looks like there is a problem trying to open SCO, can you take logs
with hcidump? Ive seems a couple of times some dongles/adapter just
don't connect SCO for some reason.

--

-- 
Luiz Augusto von Dentz
Computer Engineer
Franz Glauber | 16 Feb 11:44 2011
Picon

Re: Problems trying to connecf HFP device

The device is recharging right now, I'll post the dump later today...

On Wed, Feb 16, 2011 at 4:11 AM, Luiz Augusto von Dentz <luiz.dentz <at> gmail.com> wrote:
Hi,

On Sun, Feb 13, 2011 at 11:44 PM, Franz Glauber <franzec05 <at> gmail.com> wrote:
>
>
> On Sun, Feb 13, 2011 at 6:20 PM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
>>
>> 'Twas brillig, and Franz Glauber at 08/02/11 09:58 did gyre and gimble:
>> > I'm cross-posting this from bluez, since I got no reply there and I'm
>> > not sure wether this is a pulseaudio issue or a bluez.
>>
>> I'm not really much of an expert on BT stuff, but to me it looks like it
>> is at the bluez end, but what version of PA are you running? Ideally it
>> would be 0.9.22 or git master....
>
> Yeah, I thought so... I'm using 0.9.22 (latest ebuild on Gentoo). Do you
> think it's worth trying the git version?
>
> It seems that, given the delay before the error,  PA is waiting for some
> answer from the device, and that doesn't happen...

It looks like there is a problem trying to open SCO, can you take logs
with hcidump? Ive seems a couple of times some dongles/adapter just
don't connect SCO for some reason.

--
Luiz Augusto von Dentz
Computer Engineer
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss



--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Franz Glauber | 16 Feb 15:03 2011
Picon

Re: Problems trying to connecf HFP device

The dump is here. The last line was after the delay.

< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
< ACL data: handle 1 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Info rsp: type 2 result 1
      Not supported
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 64
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 64
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 1 flags 0x02 dlen 24
    L2CAP(d): cid 0x0040 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x111e (Handsfree)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 4
    L2CAP(d): cid 0x0040 len 119 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x72
          count 111
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10000
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x111e (Handsfree) uuid-16 0x1203 (Audio) >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x1 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x111e (Handsfree) uint 0x105 > >
              aid 0x0100 (SrvName)
                 str "Hands-Free"
              aid 0x0102 (ProviderName)
                 str "TERAX COMMUNICATION INC."
              aid 0x0311 (SuppFeatures)
                 uint 0x18
          cont 00
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 1013
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
      Success
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 261
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
      MTU 261
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Auth Complete (0x06) plen 3
< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Encrypt Change (0x08) plen 4
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 256 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
      dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
      frame_size 256 max_retrans 0 credits 2
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 2
    L2CAP(d): cid 0x0041 len 15 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 11 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 22
    L2CAP(d): cid 0x0041 len 18 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 14 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 141
    L2CAP(d): cid 0x0041 len 137 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 132 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 32
    L2CAP(d): cid 0x0041 len 28 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 24 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 7
    L2CAP(d): cid 0x0041 len 20 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 16 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< HCI Command: Add SCO Connection (0x01|0x0007) plen 4
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040

> HCI Event: Mode Change (0x14) plen 6

--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Franz Glauber | 28 Feb 12:05 2011
Picon

[pulseaudio-discuss] Problems trying to connecf HFP device

I got a dump with hcitool, the last line was after the delay. I got
latest 4.89 bluez and kernel 2.6.36-r5. Any ideas?

< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
< ACL data: handle 1 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Info rsp: type 2 result 1
      Not supported
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 64
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 64
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 1 flags 0x02 dlen 24
    L2CAP(d): cid 0x0040 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x111e (Handsfree)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 17
> ACL data: handle 1 flags 0x01 dlen 4
    L2CAP(d): cid 0x0040 len 119 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x72
          count 111
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10000
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x111e (Handsfree) uuid-16 0x1203 (Audio) >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x1 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x111e (Handsfree) uint 0x105 > >
              aid 0x0100 (SrvName)
                 str "Hands-Free"
              aid 0x0102 (ProviderName)
                 str "TERAX COMMUNICATION INC."
              aid 0x0311 (SuppFeatures)
                 uint 0x18
          cont 00
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 1013
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
      Success
> ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 261
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
      MTU 261
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Auth Complete (0x06) plen 3
< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Encrypt Change (0x08) plen 4
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 256 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
      dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
      frame_size 256 max_retrans 0 credits 2
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 2
    L2CAP(d): cid 0x0041 len 15 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 11 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 22
    L2CAP(d): cid 0x0041 len 18 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 14 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 141
    L2CAP(d): cid 0x0041 len 137 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 132 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 32
    L2CAP(d): cid 0x0041 len 28 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 24 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 7
    L2CAP(d): cid 0x0041 len 20 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 16 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< HCI Command: Add SCO Connection (0x01|0x0007) plen 4
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040

> HCI Event: Mode Change (0x14) plen 6

--
Franz

http://ciudaddelpico.com

--
Franz

http://ciudaddelpico.com
Daniel Wagner | 28 Feb 13:33 2011

Re: [pulseaudio-discuss] Problems trying to connecf HFP device

Hi Franz,

On Mon, Feb 28, 2011 at 08:05:25AM -0300, Franz Glauber wrote:
> I got a dump with hcitool, the last line was after the delay. I got
> latest 4.89 bluez and kernel 2.6.36-r5. Any ideas?

What is your exact problem? Just the other day, I got HFP (audio
gateway) working on my computer. The main problem was that I had to
tell PulseAudio to loopback the audio stream to the audio
card. Otherwise, PulseAudio would suspend the BT audio streams which
resulted in a SCO disconnect.

HTH,
daniel
Franz Glauber | 28 Feb 23:13 2011
Picon

Problems trying to connecf HFP device

This is an interesting clue someone gave on Bluez list. How to achieve this?


---------- Forwarded message ----------
From: Daniel Wagner <wagi <at> monom.org>
Date: Mon, Feb 28, 2011 at 9:33 AM
Subject: Re: [pulseaudio-discuss] Problems trying to connecf HFP device
To: Franz Glauber <franzec05 <at> gmail.com>
Cc: linux-bluetooth <at> vger.kernel.org


Hi Franz,

On Mon, Feb 28, 2011 at 08:05:25AM -0300, Franz Glauber wrote:
> I got a dump with hcitool, the last line was after the delay. I got
> latest 4.89 bluez and kernel 2.6.36-r5. Any ideas?

What is your exact problem? Just the other day, I got HFP (audio
gateway) working on my computer. The main problem was that I had to
tell PulseAudio to loopback the audio stream to the audio
card. Otherwise, PulseAudio would suspend the BT audio streams which
resulted in a SCO disconnect.

HTH,
daniel



--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Colin Guthrie | 28 Feb 23:35 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 28/02/11 22:13 did gyre and gimble:
> This is an interesting clue someone gave on Bluez list. How to achieve this?

I think what he suggests is loading module-loopback and then using e.g.
pavucontrol to "wire up" the two streams (one recording and one
playback) to the correct devices.

You don't necessarily want to do this (I wouldn't want the audio to be
audible at all times) but it's may work around the problem of disconnects.

If so then the problem of the disconnects needs to be fixed I guess....

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Daniel Wagner | 1 Mar 11:05 2011

Re: Problems trying to connecf HFP device

Hi,

On Mon, Feb 28, 2011 at 10:35:07PM +0000, Colin Guthrie wrote:
> 'Twas brillig, and Franz Glauber at 28/02/11 22:13 did gyre and gimble:
> > This is an interesting clue someone gave on Bluez list. How to achieve this?
> 
> I think what he suggests is loading module-loopback and then using e.g.
> pavucontrol to "wire up" the two streams (one recording and one
> playback) to the correct devices.

Yep, that is my current workaround:

pactl load-module module-loopback source="alsa_input.pci-0000_00_1b.0.analog-stereo" sink="bluez_sink.78_47_1D_44_34_10"
pactl load-module module-loopback source="bluez_source.78_47_1D_44_34_10" sink="alsa_output.pci-0000_00_1b.0.analog-stereo"

> You don't necessarily want to do this (I wouldn't want the audio to be
> audible at all times) but it's may work around the problem of disconnects.

Exactly. I'm not sure yet how to handle all the uses cases such as
mute and switching from the telephone speakers to the local speakers.

> If so then the problem of the disconnects needs to be fixed I guess....

The idle watchdog is suspending the BT streams and the current
implementation calls BT_STOP.

cheers,
daniel
Franz Glauber | 1 Mar 12:16 2011
Picon

Re: Problems trying to connecf HFP device

Hi Daniel!

Thanks for the help, but it doesn't seem to be the issue here. What happens is that whenever I try to open any PA control interface, it freezes while waiting for some reply from the device and then it fails with a Timeout or such. That is exactly what happened while trying to issue those commands:

$ pactl load-module module-loopback source="alsa_input.pci-0000_00_14.2" sink="bluez_sink.88_88_00_B9_CC_DD"
<30-second wait>
Connection fail: Timeout (translated this back to english, not sure if the message is this...

Regards,

--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Colin Guthrie | 1 Mar 12:18 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 01/03/11 11:16 did gyre and gimble:
> Hi Daniel!
> 
> Thanks for the help, but it doesn't seem to be the issue here. What
> happens is that whenever I try to open any PA control interface, it
> freezes while waiting for some reply from the device and then it fails
> with a Timeout or such. That is exactly what happened while trying to
> issue those commands:
> 
> $ pactl load-module module-loopback source="alsa_input.pci-0000_00_14.2"
> sink="bluez_sink.88_88_00_B9_CC_DD"
> <30-second wait>
> Connection fail: Timeout (translated this back to english, not sure if
> the message is this...

Are you doing this via an SSH connection? If so, make sure you unset
$DISPLAY or use ssh -x

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Franz Glauber | 1 Mar 12:20 2011
Picon

Re: Problems trying to connecf HFP device



On Tue, Mar 1, 2011 at 8:18 AM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
'Twas brillig, and Franz Glauber at 01/03/11 11:16 did gyre and gimble:
> Hi Daniel!
>
> Thanks for the help, but it doesn't seem to be the issue here. What
> happens is that whenever I try to open any PA control interface, it
> freezes while waiting for some reply from the device and then it fails
> with a Timeout or such. That is exactly what happened while trying to
> issue those commands:
>
> $ pactl load-module module-loopback source="alsa_input.pci-0000_00_14.2"
> sink="bluez_sink.88_88_00_B9_CC_DD"
> <30-second wait>
> Connection fail: Timeout (translated this back to english, not sure if
> the message is this...

Are you doing this via an SSH connection? If so, make sure you unset
$DISPLAY or use ssh -x

No, it was a normal console (yakuake). Besides, it's the same behavior as when I open 'pavueditor' just after connecting the HFP device (some wait followed by an error).



--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Colin Guthrie | 1 Mar 12:26 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 01/03/11 11:20 did gyre and gimble:
> 
> 
> On Tue, Mar 1, 2011 at 8:18 AM, Colin Guthrie <gmane <at> colin.guthr.ie
> <mailto:gmane <at> colin.guthr.ie>> wrote:
> 
>     'Twas brillig, and Franz Glauber at 01/03/11 11:16 did gyre and gimble:
>     > Hi Daniel!
>     >
>     > Thanks for the help, but it doesn't seem to be the issue here. What
>     > happens is that whenever I try to open any PA control interface, it
>     > freezes while waiting for some reply from the device and then it fails
>     > with a Timeout or such. That is exactly what happened while trying to
>     > issue those commands:
>     >
>     > $ pactl load-module module-loopback
>     source="alsa_input.pci-0000_00_14.2"
>     > sink="bluez_sink.88_88_00_B9_CC_DD"
>     > <30-second wait>
>     > Connection fail: Timeout (translated this back to english, not sure if
>     > the message is this...
> 
>     Are you doing this via an SSH connection? If so, make sure you unset
>     $DISPLAY or use ssh -x
> 
> 
> No, it was a normal console (yakuake). Besides, it's the same behavior
> as when I open 'pavueditor' just after connecting the HFP device (some
> wait followed by an error).

Issues such as "where to connect" would affect all PA clients the same
way (as it's something libpulse does), so it's not in the least
surprising that this affects pavueditor (is this a new tool, or do you
mean pavucontrol?) too.

Can you supply:

whoami (should be the same user as pulseaudio daemon - not e.g. root)

ps aux | grep pulse

PULSE_LOG=99 paplay -vvvv
/usr/share/sounds/freedesktop/stereo/dialog-warning.oga (or some .wav
file - it's not really important)

xprop -root | grep -i PULSE
cat ~/.pulse/client.conf /etc/pulse/client.conf | grep default-server
env | grep -i PULSE

The above should help diagnose any connection issues you might be having.

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Franz Glauber | 1 Mar 16:18 2011
Picon

Re: Problems trying to connecf HFP device



On Tue, Mar 1, 2011 at 8:26 AM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
'Twas brillig, and Franz Glauber at 01/03/11 11:20 did gyre and gimble:
>
>
> On Tue, Mar 1, 2011 at 8:18 AM, Colin Guthrie <gmane <at> colin.guthr.ie
> <mailto:gmane <at> colin.guthr.ie>> wrote:
>
>     'Twas brillig, and Franz Glauber at 01/03/11 11:16 did gyre and gimble:
>     > Hi Daniel!
>     >
>     > Thanks for the help, but it doesn't seem to be the issue here. What
>     > happens is that whenever I try to open any PA control interface, it
>     > freezes while waiting for some reply from the device and then it fails
>     > with a Timeout or such. That is exactly what happened while trying to
>     > issue those commands:
>     >
>     > $ pactl load-module module-loopback
>     source="alsa_input.pci-0000_00_14.2"
>     > sink="bluez_sink.88_88_00_B9_CC_DD"
>     > <30-second wait>
>     > Connection fail: Timeout (translated this back to english, not sure if
>     > the message is this...
>
>     Are you doing this via an SSH connection? If so, make sure you unset
>     $DISPLAY or use ssh -x
>
>
> No, it was a normal console (yakuake). Besides, it's the same behavior
> as when I open 'pavueditor' just after connecting the HFP device (some
> wait followed by an error).

Issues such as "where to connect" would affect all PA clients the same
way (as it's something libpulse does), so it's not in the least
surprising that this affects pavueditor (is this a new tool, or do you
mean pavucontrol?) too.

Can you supply:

whoami (should be the same user as pulseaudio daemon - not e.g. root)

ps aux | grep pulse

Both return my username.

PULSE_LOG=99 paplay -vvvv
/usr/share/sounds/freedesktop/stereo/dialog-warning.oga (or some .wav
file - it's not really important)

With the device connected, only get:

Abrindo um fluxo playback com a especificação de amostragem "float32le 2ch 44100Hz" e mapeamento de canais "front-left,front-right".
Using shared memory pool with 1024 slots of size 64,0 KiB each, total size is 64,0 MiB, maximum usable slot size is 65472
Trying to connect to /home/franz/.pulse/056d645cad154b3e13840dc900000128-runtime/native...

[big pause here, after which the device fails]

SHM possible: yes
Protocol version: remote 16, local 16
Negotiated SHM: yes
Conexão estabelecida.
Fluxo criado com sucesso.
Métricas do buffer: maxlength=4194304, tlength=705600, prebuf=698552, minreq=7056
Usando especificação de amostragem "float32le 2ch 44100Hz", mapa de canais "front-left,front-right".
Conectado ao dispositivo alsa_output.pci-0000_00_14.2.analog-stereo (0, not suspended).
Fluxo iniciado.
Subestimação do fluxo.
Fluxo de reprodução drenado. 221073 usec.       
Drenando conexão para o servidor.



xprop -root | grep -i PULSE
cat ~/.pulse/client.conf /etc/pulse/client.conf | grep default-server
env | grep -i PULSE


~/.pulse/client.conf doesn't exist, and default-server is commented out on main config
xprop and env doesn't return anything.

--
Franz

http://ciudaddelpico.com

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Colin Guthrie | 1 Mar 16:35 2011
Picon

Re: Problems trying to connecf HFP device

[Friendly Request: If possible can you send plain text emails and use
conventional formatting for mailing lists? That makes your mails easier
to read and reply to and saves us upstream people who real loads of such
emails every day some valuable time. Thanks :)]

'Twas brillig, and Franz Glauber at 01/03/11 15:18 did gyre and gimble:
>     Can you supply:
> 
>     whoami (should be the same user as pulseaudio daemon - not e.g. root)
> 
>     ps aux | grep pulse
> 
> 
> Both return my username.

The 2nd one should have returned details of the running PA process...
but that's probably just an oversight on your part :)

> 
>     PULSE_LOG=99 paplay -vvvv
>     /usr/share/sounds/freedesktop/stereo/dialog-warning.oga (or some .wav
>     file - it's not really important)
> 
> 
> With the device connected, only get:
> 
> Abrindo um fluxo playback com a especificação de amostragem "float32le
> 2ch 44100Hz" e mapeamento de canais "front-left,front-right".
> Using shared memory pool with 1024 slots of size 64,0 KiB each, total
> size is 64,0 MiB, maximum usable slot size is 65472
> Trying to connect to
> /home/franz/.pulse/056d645cad154b3e13840dc900000128-runtime/native...
> 
> [big pause here, after which the device fails]
> 
> SHM possible: yes
> Protocol version: remote 16, local 16
> Negotiated SHM: yes
> Conexão estabelecida.
> Fluxo criado com sucesso.
> Métricas do buffer: maxlength=4194304, tlength=705600, prebuf=698552,
> minreq=7056
> Usando especificação de amostragem "float32le 2ch 44100Hz", mapa de
> canais "front-left,front-right".
> Conectado ao dispositivo alsa_output.pci-0000_00_14.2.analog-stereo (0,
> not suspended).
> Fluxo iniciado.
> Subestimação do fluxo.
> Fluxo de reprodução drenado. 221073 usec.       
> Drenando conexão para o servidor.

I should have also asked you to use LC_ALL=C too so the debug was in
English, but never mind, I think I can work it out.

I'm not sure why there would be such a big pause at the connection
stage. Does the big pause only happen when the BT device is connected?
e.g. if it's not connected, the connection is quick?

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss <at> mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Franz Glauber | 1 Mar 17:47 2011
Picon

Re: Problems trying to connecf HFP device

On Tue, Mar 1, 2011 at 12:35 PM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
> [Friendly Request: If possible can you send plain text emails and use
> conventional formatting for mailing lists? That makes your mails easier
> to read and reply to and saves us upstream people who real loads of such
> emails every day some valuable time. Thanks :)]

Sorry, it's a little annoying to switch to it and back on GMail... I
will try to remember this.

> The 2nd one should have returned details of the running PA process...
> but that's probably just an oversight on your part :)

franz     6923  0.0  0.1 233632  5256 ?        Ssl  Feb28   0:01
/usr/bin/pulseaudio --start --log-target=syslog

I didn't thought it was so meaningful

> I should have also asked you to use LC_ALL=C too so the debug was in
> English, but never mind, I think I can work it out.

I also didn't know it would work that way. Next time it will be in english. =)

> I'm not sure why there would be such a big pause at the connection
> stage. Does the big pause only happen when the BT device is connected?
> e.g. if it's not connected, the connection is quick?

Yep, only when the device is connected. Otherwise it's pretty quick.

--

-- 
Franz

http://ciudaddelpico.com
Colin Guthrie | 1 Mar 19:01 2011
Picon

Re: Problems trying to connecf HFP device

'Twas brillig, and Franz Glauber at 01/03/11 16:47 did gyre and gimble:
> On Tue, Mar 1, 2011 at 12:35 PM, Colin Guthrie <gmane <at> colin.guthr.ie> wrote:
>> [Friendly Request: If possible can you send plain text emails and use
>> conventional formatting for mailing lists? That makes your mails easier
>> to read and reply to and saves us upstream people who real loads of such
>> emails every day some valuable time. Thanks :)]
> 
> Sorry, it's a little annoying to switch to it and back on GMail... I
> will try to remember this.

No worries :) I'd have thought you could specify this as an option
per-recipient, but hey ho.

>> The 2nd one should have returned details of the running PA process...
>> but that's probably just an oversight on your part :)
> 
> franz     6923  0.0  0.1 233632  5256 ?        Ssl  Feb28   0:01
> /usr/bin/pulseaudio --start --log-target=syslog
> 
> I didn't thought it was so meaningful

That's OK, I inferred the result from your next test anyway.

>> I should have also asked you to use LC_ALL=C too so the debug was in
>> English, but never mind, I think I can work it out.
> 
> I also didn't know it would work that way. Next time it will be in english. =)

Excellent. One more titbit of knowledge to keep in your debugging arsenal :)

>> I'm not sure why there would be such a big pause at the connection
>> stage. Does the big pause only happen when the BT device is connected?
>> e.g. if it's not connected, the connection is quick?
> 
> Yep, only when the device is connected. Otherwise it's pretty quick.

Very odd. I'm not sure why such a thing would affect the connection phase.

I'll have to defer to cleverer people than I.... any ideas clever people?

Col

--

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]
Tanu Kaskinen | 1 Mar 20:49 2011
Picon
Picon

Re: Problems trying to connecf HFP device

On Tue, 2011-03-01 at 18:01 +0000, Colin Guthrie wrote:
> >> I'm not sure why there would be such a big pause at the connection
> >> stage. Does the big pause only happen when the BT device is connected?
> >> e.g. if it's not connected, the connection is quick?
> > 
> > Yep, only when the device is connected. Otherwise it's pretty quick.
> 
> Very odd. I'm not sure why such a thing would affect the connection phase.
> 
> I'll have to defer to cleverer people than I.... any ideas clever people?

This sounds a lot like a bug that I've heard to exist in
module-bluetooth-device. The module does something in the main thread
that in some situations can block for a long time. The connection
handling should be moved to a separate thread (or perhaps to the IO
thread).

--

-- 
Tanu
Franz Glauber | 1 Mar 21:30 2011
Picon

Re: Problems trying to connecf HFP device

On Tue, Mar 1, 2011 at 4:49 PM, Tanu Kaskinen <tanuk <at> iki.fi> wrote:
> On Tue, 2011-03-01 at 18:01 +0000, Colin Guthrie wrote:
>> >> I'm not sure why there would be such a big pause at the connection
>> >> stage. Does the big pause only happen when the BT device is connected?
>> >> e.g. if it's not connected, the connection is quick?
>> >
>> > Yep, only when the device is connected. Otherwise it's pretty quick.
>>
>> Very odd. I'm not sure why such a thing would affect the connection phase.
>>
>> I'll have to defer to cleverer people than I.... any ideas clever people?
>
> This sounds a lot like a bug that I've heard to exist in
> module-bluetooth-device. The module does something in the main thread
> that in some situations can block for a long time. The connection
> handling should be moved to a separate thread (or perhaps to the IO
> thread).

Now that you mention it, makes sense, as I got it half-working once,
and I don't know how and I couldn't reproduce anymore. Seems to be a
threading issue somehow.

--

-- 
Franz

http://ciudaddelpico.com
Franz Glauber | 2 Mar 12:29 2011
Picon

Re: Problems trying to connecf HFP device

On Tue, Mar 1, 2011 at 5:30 PM, Franz Glauber <franzec05 <at> gmail.com> wrote:
> On Tue, Mar 1, 2011 at 4:49 PM, Tanu Kaskinen <tanuk <at> iki.fi> wrote:
>> On Tue, 2011-03-01 at 18:01 +0000, Colin Guthrie wrote:
>>> >> I'm not sure why there would be such a big pause at the connection
>>> >> stage. Does the big pause only happen when the BT device is connected?
>>> >> e.g. if it's not connected, the connection is quick?
>>> >
>>> > Yep, only when the device is connected. Otherwise it's pretty quick.
>>>
>>> Very odd. I'm not sure why such a thing would affect the connection phase.
>>>
>>> I'll have to defer to cleverer people than I.... any ideas clever people?
>>
>> This sounds a lot like a bug that I've heard to exist in
>> module-bluetooth-device. The module does something in the main thread
>> that in some situations can block for a long time. The connection
>> handling should be moved to a separate thread (or perhaps to the IO
>> thread).
>
> Now that you mention it, makes sense, as I got it half-working once,
> and I don't know how and I couldn't reproduce anymore. Seems to be a
> threading issue somehow.

Taking a glance on the code, it seems that it fails on:

thread_func -> start_stream_fd

and fails around line 804 on

if (service_expect(u, &msg.rsp, sizeof(msg), BT_START_STREAM,
sizeof(msg.start_rsp)) < 0)
        return -1;

I don't know, I keep thinking this looks like a BT issue. If you check
the BT log, it really doesn't reply the message (at least it seems so
to me).
Also, if you look at the last block of log on my first message you'll
notice that the timeout occurs AFTER the error on the IO thread is
issued (due to lack of response from BT)

<snip>
D: module-bluetooth-device.c: Received BT_ERROR <- BT_START_STREAM
E: module-bluetooth-device.c: Received error condition: Input/output
error *translated back to english
D: module-bluetooth-device.c: IO thread failed
D: module-suspend-on-idle.c: Sink bluez_sink.88_88_00_B9_CC_DD becomes
idle, timeout in 5 seconds.
D: module-suspend-on-idle.c: Source bluez_source.88_88_00_B9_CC_DD
becomes idle, timeout in 5 seconds.
</snip>

--

-- 
Franz

http://ciudaddelpico.com

Gmane