* [Bluez-users] BT Headset connected but no sound
@ 2008-02-01 1:24 Daniel Stumpner
2008-02-02 9:32 ` Daniel Stumpner
2008-02-03 8:05 ` Guillaume Bedot
0 siblings, 2 replies; 11+ messages in thread
From: Daniel Stumpner @ 2008-02-01 1:24 UTC (permalink / raw)
To: bluez-users
Hi,
can connect to my BT Headset but if I try to play a sound, it does only
beep at the start and at the end of the connection but there is no sound.
mplayer -ao alsa:device=bluetooth test.wav
- beep -
(pressing 'q')
- beep -
I am running Gentoo with linux 2.6.23 (x86)
bluez-libs-3.24
blues-utils-3.24
========================================================================
Some Debug Information:
========================================================================
# lsusb
Bus 002 Device 002: ID 046d:c012 Logitech, Inc. Optical Mouse
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 03f0:011d Hewlett-Packard /* Critical line */
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
------------------------------------------------------------------------
# cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=03f0 ProdID=011d Rev= 0.17
------------------------------------------------------------------------
# hciconfig -a
hci0: Type: USB
BD Address: 00:10:C6:F8:11:7C ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING PSCAN ISCAN
RX bytes:87191 acl:27 sco:1676 events:53 errors:0
TX bytes:809 acl:21 sco:0 commands:30 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.2 (0x2) HCI Rev: 0x11 LMP Ver: 1.2 (0x2) LMP Subver: 0x6963
Manufacturer: Broadcom Corporation (15)
------------------------------------------------------------------------
# hcitool info 00:0D:44:30:4B:11 /* My Logitech headset */
Requesting information ...
BD Address: 00:0D:44:30:4B:11
LMP Version: 1.2 (0x2) LMP Subversion: 0x611
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
<HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
<paging scheme> <power control> <transparent SCO>
<AFH cap. slave> <AFH cap. master>
------------------------------------------------------------------------
# rfcomm
rfcomm0: 00:0D:44:30:4B:11 channel 1 clean
------------------------------------------------------------------------
# l2ping 00:0D:44:30:4B:11
Ping: 00:0D:44:30:4B:11 from 00:10:C6:F8:11:7C (data size 44) ...
44 bytes from 00:0D:44:30:4B:11 id 0 time 34.40ms
44 bytes from 00:0D:44:30:4B:11 id 1 time 52.72ms
2 sent, 2 received, 0% loss
------------------------------------------------------------------------
# cat /etc/asound.conf
pcm.bluetooth {
type bluetooth
device 00:0D:44:30:4B:11
}
------------------------------------------------------------------------
# cat /proc/asound/cards
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with AD1981B at irq 21
1 [Modem ]: ICH-MODEM - Intel ICH6 Modem
Intel ICH6 Modem at irq 19
------------------------------------------------------------------------
# tail -f /var/log/messages /* before executing the above mplayer
command */
Feb 1 00:36:25 snake audio[8329]: Accepted new client connection on
unix socket (fd=9)
Feb 1 00:36:25 snake audio[8329]: Audio API: received
BT_GETCAPABILITIES_REQ
Feb 1 00:36:25 snake audio[8329]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 1 00:36:25 snake audio[8329]: Audio API: received
BT_SETCONFIGURATION_REQ
Feb 1 00:36:25 snake audio[8329]: State changed
/org/bluez/audio/device0: HEADSET_STATE_DISCONNECTED ->
HEADSET_STATE_CONNECT_IN_PROGRESS
Feb 1 00:36:29 snake hcid[8156]: link_key_request
(sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
Feb 1 00:36:29 snake audio[8329]: /org/bluez/audio/device0: Connecting
to 00:0D:44:30:4B:11 channel 1
Feb 1 00:36:30 snake audio[8329]: State changed
/org/bluez/audio/device0: HEADSET_STATE_CONNECT_IN_PROGRESS ->
HEADSET_STATE_CONNECTED
Feb 1 00:36:30 snake audio[8329]: /org/bluez/audio/device0: Connected
to 00:0D:44:30:4B:11
Feb 1 00:36:30 snake audio[8329]: State changed
/org/bluez/audio/device0: HEADSET_STATE_CONNECTED ->
HEADSET_STATE_PLAY_IN_PROGRESS
Feb 1 00:36:30 snake audio[8329]: SCO socket opened for headset
/org/bluez/audio/device0
Feb 1 00:36:30 snake audio[8329]: SCO fd=11
Feb 1 00:36:30 snake audio[8329]: Audio API: sending
BT_SETCONFIGURATION_RSP
Feb 1 00:36:30 snake audio[8329]: State changed
/org/bluez/audio/device0: HEADSET_STATE_PLAY_IN_PROGRESS ->
HEADSET_STATE_PLAYING
Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 0
Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 0
Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 0
Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 0
Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 0
Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
Feb 1 00:36:31 snake audio[8329]: Unix client disconnected (fd=9)
Feb 1 00:36:31 snake audio[8329]: State changed
/org/bluez/audio/device0: HEADSET_STATE_PLAYING ->
HEADSET_STATE_DISCONNECTED
Feb 1 00:36:31 snake hci_scodata_packet: hci0 SCO packet for unknown
connection handle 1
========================================================================
End of debug info
========================================================================
I have no Idea where to start searching the problem...
Somewhere I read that Broadcom Chips aren't fully supported. May I need
firmware perhaps? Would l2ping work in this case? (In my case it DOES
work!?)
Quote:
"If you have a Broadcom Chipset or Hewlett-Packard Integrated Chipset
(such as mine on HP nx8220) then you really want to pass
'force_scofix=1' as argument to kernel: it was the only way to make work
hci_usb properly with my chip. NOTE: bcm203x won't recognize HP
Integrated as a valid chip (03f0:011d instead of 0a5c:2033 - you can
check this with lsusb), then don't even try to make it work."
May I have an error in my alsa-config? There is no card displayed...
Thanks for your time!
Best regards, Daniel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-users] BT Headset connected but no sound
2008-02-01 1:24 [Bluez-users] BT Headset connected but no sound Daniel Stumpner
@ 2008-02-02 9:32 ` Daniel Stumpner
2008-02-02 10:40 ` Guillaume Bedot
2008-02-02 14:29 ` Guillaume Bedot
2008-02-03 8:05 ` Guillaume Bedot
1 sibling, 2 replies; 11+ messages in thread
From: Daniel Stumpner @ 2008-02-02 9:32 UTC (permalink / raw)
To: BlueZ users
Daniel Stumpner wrote:
> Hi,
>
> can connect to my BT Headset but if I try to play a sound, it does only
> beep at the start and at the end of the connection but there is no sound.
>
> mplayer -ao alsa:device=bluetooth test.wav
> - beep -
> (pressing 'q')
> - beep -
>
> I am running Gentoo with linux 2.6.23 (x86)
> bluez-libs-3.24
> blues-utils-3.24
>
>
> ========================================================================
> Some Debug Information:
> ========================================================================
>
> # lsusb
> Bus 002 Device 002: ID 046d:c012 Logitech, Inc. Optical Mouse
> Bus 002 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 002: ID 03f0:011d Hewlett-Packard /* Critical line */
> Bus 003 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
>
> ------------------------------------------------------------------------
>
> # cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1
> T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=03f0 ProdID=011d Rev= 0.17
>
> ------------------------------------------------------------------------
>
> # hciconfig -a
> hci0: Type: USB
> BD Address: 00:10:C6:F8:11:7C ACL MTU: 377:10 SCO MTU: 16:0
> UP RUNNING PSCAN ISCAN
> RX bytes:87191 acl:27 sco:1676 events:53 errors:0
> TX bytes:809 acl:21 sco:0 commands:30 errors:0
> Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0)'
> Class: 0x080100
> Service Classes: Capturing
> Device Class: Computer, Uncategorized
> HCI Ver: 1.2 (0x2) HCI Rev: 0x11 LMP Ver: 1.2 (0x2) LMP Subver: 0x6963
> Manufacturer: Broadcom Corporation (15)
>
> ------------------------------------------------------------------------
>
> # hcitool info 00:0D:44:30:4B:11 /* My Logitech headset */
> Requesting information ...
> BD Address: 00:0D:44:30:4B:11
> LMP Version: 1.2 (0x2) LMP Subversion: 0x611
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
> <encryption> <slot offset> <timing accuracy> <role switch>
> <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
> <paging scheme> <power control> <transparent SCO>
> <AFH cap. slave> <AFH cap. master>
>
> ------------------------------------------------------------------------
>
> # rfcomm
> rfcomm0: 00:0D:44:30:4B:11 channel 1 clean
>
> ------------------------------------------------------------------------
>
> # l2ping 00:0D:44:30:4B:11
> Ping: 00:0D:44:30:4B:11 from 00:10:C6:F8:11:7C (data size 44) ...
> 44 bytes from 00:0D:44:30:4B:11 id 0 time 34.40ms
> 44 bytes from 00:0D:44:30:4B:11 id 1 time 52.72ms
> 2 sent, 2 received, 0% loss
>
> ------------------------------------------------------------------------
>
> # cat /etc/asound.conf
> pcm.bluetooth {
> type bluetooth
> device 00:0D:44:30:4B:11
> }
>
> ------------------------------------------------------------------------
>
> # cat /proc/asound/cards
> 0 [ICH6 ]: ICH4 - Intel ICH6
> Intel ICH6 with AD1981B at irq 21
> 1 [Modem ]: ICH-MODEM - Intel ICH6 Modem
> Intel ICH6 Modem at irq 19
>
> ------------------------------------------------------------------------
>
> # tail -f /var/log/messages /* before executing the above mplayer
> command */
> Feb 1 00:36:25 snake audio[8329]: Accepted new client connection on
> unix socket (fd=9)
> Feb 1 00:36:25 snake audio[8329]: Audio API: received
> BT_GETCAPABILITIES_REQ
> Feb 1 00:36:25 snake audio[8329]: Audio API: sending BT_GETCAPABILITIES_RSP
> Feb 1 00:36:25 snake audio[8329]: Audio API: received
> BT_SETCONFIGURATION_REQ
> Feb 1 00:36:25 snake audio[8329]: State changed
> /org/bluez/audio/device0: HEADSET_STATE_DISCONNECTED ->
> HEADSET_STATE_CONNECT_IN_PROGRESS
> Feb 1 00:36:29 snake hcid[8156]: link_key_request
> (sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
> Feb 1 00:36:29 snake audio[8329]: /org/bluez/audio/device0: Connecting
> to 00:0D:44:30:4B:11 channel 1
> Feb 1 00:36:30 snake audio[8329]: State changed
> /org/bluez/audio/device0: HEADSET_STATE_CONNECT_IN_PROGRESS ->
> HEADSET_STATE_CONNECTED
> Feb 1 00:36:30 snake audio[8329]: /org/bluez/audio/device0: Connected
> to 00:0D:44:30:4B:11
> Feb 1 00:36:30 snake audio[8329]: State changed
> /org/bluez/audio/device0: HEADSET_STATE_CONNECTED ->
> HEADSET_STATE_PLAY_IN_PROGRESS
> Feb 1 00:36:30 snake audio[8329]: SCO socket opened for headset
> /org/bluez/audio/device0
> Feb 1 00:36:30 snake audio[8329]: SCO fd=11
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending
> BT_SETCONFIGURATION_RSP
> Feb 1 00:36:30 snake audio[8329]: State changed
> /org/bluez/audio/device0: HEADSET_STATE_PLAY_IN_PROGRESS ->
> HEADSET_STATE_PLAYING
> Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 0
> Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 0
> Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 0
> Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 0
> Feb 1 00:36:30 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 0
> Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:30 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:30 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Audio API: received BT_STREAMSTART_REQ
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMSTART_RSP
> Feb 1 00:36:31 snake audio[8329]: Audio API: sending BT_STREAMFD_IND
> Feb 1 00:36:31 snake audio[8329]: Unix client disconnected (fd=9)
> Feb 1 00:36:31 snake audio[8329]: State changed
> /org/bluez/audio/device0: HEADSET_STATE_PLAYING ->
> HEADSET_STATE_DISCONNECTED
> Feb 1 00:36:31 snake hci_scodata_packet: hci0 SCO packet for unknown
> connection handle 1
>
>
> ========================================================================
> End of debug info
> ========================================================================
>
>
>
> I have no Idea where to start searching the problem...
> Somewhere I read that Broadcom Chips aren't fully supported. May I need
> firmware perhaps? Would l2ping work in this case? (In my case it DOES
> work!?)
> Quote:
> "If you have a Broadcom Chipset or Hewlett-Packard Integrated Chipset
> (such as mine on HP nx8220) then you really want to pass
> 'force_scofix=1' as argument to kernel: it was the only way to make work
> hci_usb properly with my chip. NOTE: bcm203x won't recognize HP
> Integrated as a valid chip (03f0:011d instead of 0a5c:2033 - you can
> check this with lsusb), then don't even try to make it work."
>
> May I have an error in my alsa-config? There is no card displayed...
>
>
> Thanks for your time!
> Best regards, Daniel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
Hi again,
I got new info:
this is a part of the hcid-log in my messages when I switch on my
headset. Seems that I have no Key-Agent...
#passkey-agent --help /* tells me that I have Version 3.24 */
Do I have to set it up manually?
So I did the following:
#passkey-agent --default 0000 /* test key */
I see:
hcid[14592]: Default passkey agent (:1.41,
/org/bluez/passkey_agent_14605) registered
But the errors don't change...
What do I have to do to get my key-agent working?
Best regards, Daniel
LOG (when switching on headset):
==========================================================================
hcid[10257]: link_key_request (sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
hcid[10257]: /org/bluez: org.bluez.Database.RequestAuthorization()
hcid[10257]: handle_authorize_request
hcid[10257]: no default agent
audio[10261]: Requesting authorization for device 00:0D:44:30:4B:11,
UUID 0000111F-0000-1000-8000-00805F9B34FB
audio[10261]: State changed /org/bluez/audio/device0:
HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
audio[10261]: Access denied: Authorization agent does not exist
audio[10261]: State changed /org/bluez/audio/device0:
HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
hcid[10257]: link_key_notify (sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
==========================================================================
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-users] BT Headset connected but no sound
2008-02-02 9:32 ` Daniel Stumpner
@ 2008-02-02 10:40 ` Guillaume Bedot
2008-02-03 3:45 ` jayjwa
2008-02-02 14:29 ` Guillaume Bedot
1 sibling, 1 reply; 11+ messages in thread
From: Guillaume Bedot @ 2008-02-02 10:40 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
On sam, 2008-02-02 at 10:32 +0100, Daniel Stumpner wrote:
> Daniel Stumpner wrote:
> > Hi,
> >
> > can connect to my BT Headset but if I try to play a sound, it does only
> > beep at the start and at the end of the connection but there is no sound.
> >
> > mplayer -ao alsa:device=bluetooth test.wav
> > - beep -
> > (pressing 'q')
> > - beep -
> >
> > I am running Gentoo with linux 2.6.23 (x86)
> > bluez-libs-3.24
> > blues-utils-3.24
> >
There is a bug in bluez-utils 3.24 that prevents headset/SCO connections
to work.
Try with current bluez cvs or with the attached patch.
> But the errors don't change...
> What do I have to do to get my key-agent working?
>
You can check your configuration in /etc/bluetooth/hcid.conf too.
Regards,
Guillaume B.
[-- Attachment #2: bluez-utils-3.24-fixheadset.patch --]
[-- Type: text/x-patch, Size: 514 bytes --]
--- bluez-utils/audio/pcm_bluetooth.c 2008/01/05 14:51:47 1.91
+++ bluez-utils/audio/pcm_bluetooth.c 2008/01/09 03:03:32 1.92
@@ -786,11 +786,11 @@
DBG("areas->step=%u areas->first=%u offset=%lu size=%lu io->nonblock=%u",
areas->step, areas->first, offset, size, io->nonblock);
+ frame_size = areas->step / 8;
+
if (data->count > 0)
goto proceed;
- frame_size = areas->step / 8;
-
nrecv = recv(data->stream.fd, data->buffer, data->link_mtu,
MSG_WAITALL | (io->nonblock ? MSG_DONTWAIT : 0));
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-users] BT Headset connected but no sound
2008-02-02 10:40 ` Guillaume Bedot
@ 2008-02-03 3:45 ` jayjwa
2008-02-03 4:25 ` Daniel Stumpner
0 siblings, 1 reply; 11+ messages in thread
From: jayjwa @ 2008-02-03 3:45 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1: Type: TEXT/PLAIN, Size: 9896 bytes --]
On Sat, 2 Feb 2008, Guillaume Bedot wrote:
-> > > can connect to my BT Headset but if I try to play a sound, it does only
-> > > beep at the start and at the end of the connection but there is no sound.
Same here.
-> > > mplayer -ao alsa:device=bluetooth test.wav
-> > > - beep -
-> > > (pressing 'q')
-> > > - beep -
-> > >
-> > > I am running Gentoo with linux 2.6.23 (x86)
-> > > bluez-libs-3.24
-> > > blues-utils-3.24
-> > >
-> There is a bug in bluez-utils 3.24 that prevents headset/SCO connections
-> to work.
-> Try with current bluez cvs or with the attached patch.
->
-> > But the errors don't change...
-> > What do I have to do to get my key-agent working?
-> >
-> You can check your configuration in /etc/bluetooth/hcid.conf too.
Patch applied, but it doesn't seem to be making a difference. As several
people have suggested, the passkey-agent does not appear to work correctly.
Started as: passkey-agent --default 0000 00:1A:45:01:F9:42 &
Ex:
Feb 2 20:09:20 vdrl kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2
Feb 2 20:09:21 vdrl kernel: usb 3-2: Product: BELKIN BLUETOOTH USB ADAPTER CL. 1
Feb 2 20:09:21 vdrl kernel: usb 3-2: Manufacturer: Broadcom Corp
Feb 2 20:09:21 vdrl kernel: usb 3-2: configuration #1 chosen from 1 choice
Feb 2 20:09:21 vdrl kernel: Bluetooth: Core ver 2.11
Feb 2 20:09:21 vdrl kernel: NET: Registered protocol family 31
Feb 2 20:09:21 vdrl kernel: Bluetooth: HCI device and connection manager initialized
Feb 2 20:09:21 vdrl kernel: Bluetooth: HCI socket layer initialized
Feb 2 20:09:21 vdrl kernel: Bluetooth: HCI USB driver ver 2.9
Feb 2 20:09:21 vdrl kernel: usbcore: registered new interface driver hci_usb
Feb 2 20:09:22 vdrl sdpd[31664]: Bluetooth SDP daemon
Feb 2 20:09:22 vdrl sdpd[31664]: Starting SDP server
Feb 2 20:09:22 vdrl kernel: Bluetooth: L2CAP ver 2.8
Feb 2 20:09:22 vdrl kernel: Bluetooth: L2CAP socket layer initialized
Feb 2 20:09:23 vdrl hcid[31671]: Bluetooth HCI daemon
Feb 2 20:09:23 vdrl hcid[31671]: HCI dev 0 registered
Feb 2 20:09:23 vdrl hcid[31671]: Created local server at unix:abstract=/var/run/dbus-A2kUxUntXr,guid=1e5c5a75a89eef29f9a7210047a51443
Feb 2 20:09:23 vdrl echo[31673]: Bluetooth echo service ver 3.24
Feb 2 20:09:23 vdrl network[31674]: Bluetooth Network daemon
Feb 2 20:09:23 vdrl serial[31677]: Bluetooth Serial Port daemon
Feb 2 20:09:23 vdrl input[31680]: Bluetooth Input daemon
Feb 2 20:09:23 vdrl input[31680]: Registered input manager path:/org/bluez/input
Feb 2 20:09:23 vdrl audio[31681]: Bluetooth Audio daemon
Feb 2 20:09:23 vdrl audio[31681]: Unix socket created: 5
Feb 2 20:09:23 vdrl hcid[31671]: HCI dev 0 up
Feb 2 20:09:23 vdrl hcid[31671]: Device hci0 has been added
Feb 2 20:09:23 vdrl hcid[31671]: Starting security manager 0
Feb 2 20:09:23 vdrl kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Feb 2 20:09:23 vdrl kernel: Bluetooth: BNEP filters: protocol multicast
Feb 2 20:09:24 vdrl hcid[31671]: Device hci0 has been activated
Feb 2 20:09:24 vdrl transfer[31686]: Bluetooth transfer service ver 3.24
Feb 2 20:09:24 vdrl kernel: Bluetooth: RFCOMM socket layer initialized
Feb 2 20:09:24 vdrl kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 2 20:09:24 vdrl kernel: Bluetooth: RFCOMM ver 1.8
Feb 2 20:09:24 vdrl serial[31677]: Registered manager path:/org/bluez/serial
Feb 2 20:09:24 vdrl audio[31681]: Registered manager path:/org/bluez/audio
Feb 2 20:09:24 vdrl kernel: Bridge firewalling registered
Feb 2 20:09:24 vdrl kernel: pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Feb 2 20:09:24 vdrl network[31674]: Registered manager path:/org/bluez/network
Feb 2 20:09:24 vdrl network[31674]: Registered server path:/org/bluez/network/panu
Feb 2 20:09:24 vdrl network[31674]: Registered server path:/org/bluez/network/gn
Feb 2 20:09:24 vdrl network[31674]: Registered server path:/org/bluez/network/nap
Notice here it claims that a passkey-agent is registered. The pin is simply
'0000', I know this from pairing phone <-> headset. It even logs "Default
passkey agent (:1.7, /org/bluez/passkey_agent_31704) registered".
Feb 2 20:10:29 vdrl hcid[31671]: Default passkey agent (:1.7, /org/bluez/passkey_agent_31704) registered
Feb 2 20:10:48 vdrl hcid[31671]: link_key_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
OK, here we go, connect...pin please...
Feb 2 20:10:48 vdrl hcid[31671]: pin_code_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:10:48 vdrl hcid[31671]: link_key_notify (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:10:50 vdrl hcid[31671]: link_key_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:10:51 vdrl audio[31681]: Access denied: Authorization agent does not exist
Huh? "agent does not exist". That seems exact opposite of what is claimed
above.
Feb 2 20:10:51 vdrl hcid[31671]: link_key_notify (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:11:05 vdrl kernel: Bluetooth: SCO (Voice Link) ver 0.5
Feb 2 20:11:05 vdrl kernel: Bluetooth: SCO socket layer initialized
Feb 2 20:11:45 vdrl smartd[1340]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 119 to 120
Feb 2 20:12:26 vdrl audio[31681]: Audio API: received BT_GETCAPABILITIES_REQ
Feb 2 20:12:26 vdrl audio[31681]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 2 20:12:26 vdrl audio[31681]: Audio API: received BT_SETCONFIGURATION_REQ
After this the results are the same: connect...
Feb 2 20:12:28 vdrl hcid[31671]: link_key_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:12:29 vdrl audio[31681]: connect(): Connection refused (111)
Feb 2 20:12:29 vdrl audio[31681]: config failed
Denied.
Feb 2 20:12:29 vdrl audio[31681]: Audio API: sending BT_SETCONFIGURATION_RSP
Feb 2 20:12:32 vdrl audio[31681]: Error handling command AT+BTRH?: Invalid argument (22)
Feb 2 20:12:32 vdrl audio[31681]: Audio API: received BT_GETCAPABILITIES_REQ
Feb 2 20:12:32 vdrl audio[31681]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 2 20:12:32 vdrl audio[31681]: Audio API: received BT_SETCONFIGURATION_REQ
Feb 2 20:12:33 vdrl audio[31681]: SCO fd=12
Feb 2 20:12:33 vdrl audio[31681]: Audio API: sending BT_SETCONFIGURATION_RSP
Feb 2 20:12:33 vdrl audio[31681]: Audio API: received BT_STREAMSTART_REQ
Feb 2 20:12:33 vdrl audio[31681]: Audio API: sending BT_STREAMSTART_RSP
Feb 2 20:12:33 vdrl audio[31681]: Audio API: sending BT_STREAMFD_IND
Feb 2 20:13:19 vdrl audio[31681]: Audio API: received BT_GETCAPABILITIES_REQ
Feb 2 20:13:19 vdrl audio[31681]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 2 20:13:19 vdrl audio[31681]: Audio API: received BT_SETCONFIGURATION_REQ
Feb 2 20:13:19 vdrl hcid[31671]: link_key_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:13:21 vdrl audio[31681]: connect(): Connection refused (111)
Feb 2 20:13:21 vdrl audio[31681]: config failed
Again.
Feb 2 20:13:21 vdrl audio[31681]: Audio API: sending BT_SETCONFIGURATION_RSP
Feb 2 20:13:24 vdrl audio[31681]: Error handling command AT+BTRH?: Invalid argument (22)
Feb 2 20:13:25 vdrl audio[31681]: Audio API: received BT_GETCAPABILITIES_REQ
Feb 2 20:13:25 vdrl audio[31681]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 2 20:13:25 vdrl audio[31681]: Audio API: received BT_SETCONFIGURATION_REQ
Feb 2 20:13:25 vdrl audio[31681]: SCO fd=12
Feb 2 20:13:25 vdrl audio[31681]: Audio API: sending BT_SETCONFIGURATION_RSP
Feb 2 20:13:25 vdrl audio[31681]: Audio API: received BT_STREAMSTART_REQ
Feb 2 20:13:25 vdrl audio[31681]: Audio API: sending BT_STREAMSTART_RSP
Feb 2 20:13:25 vdrl audio[31681]: Audio API: sending BT_STREAMFD_IND
Feb 2 20:13:58 vdrl audio[31681]: Audio API: received BT_GETCAPABILITIES_REQ
Feb 2 20:13:58 vdrl audio[31681]: Audio API: sending BT_GETCAPABILITIES_RSP
Feb 2 20:13:58 vdrl audio[31681]: Audio API: received BT_SETCONFIGURATION_REQ
Feb 2 20:14:00 vdrl audio[31681]: connect(): Connection refused (111)
Feb 2 20:14:00 vdrl audio[31681]: config failed
And again...
Feb 2 20:14:51 vdrl hcid[31671]: link_key_request (sba=00:0A:3A:7C:5C:74, dba=00:1A:45:01:F9:42)
Feb 2 20:14:53 vdrl audio[31681]: connect(): Connection refused (111)
Feb 2 20:14:53 vdrl audio[31681]: config failed
>>From the command line it looks like the below. I'm guessing this the reason
for the failure. It alternates between what is below, making a tiny channel
clearing noise in headset, and hanging aplay to which Ctrl-C needs to be hit.
aplay -Dbluetooth alert.wav
Playing WAVE 'alert.wav' : Signed 16 bit Little
Endian, Rate 8000 Hz, Mono
ALSA lib pcm_bluetooth.c:458:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION
failed : Input/output error(5)
aplay: set_params:962: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 16
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 125000
PERIOD_SIZE: 1000
PERIOD_BYTES: 2000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 4000
BUFFER_BYTES: 8000
TICK_TIME: [0 0]
(aplay alert.wav does play using normal speakers)
hcitool con
Connections:
< ACL 00:1A:45:01:F9:42 handle 12 state 1 lm MASTER
If press the headset button, it then reads:
hcitool con
Connections:
> ACL 00:1A:45:01:F9:42 handle 11 state 1 lm MASTER AUTH ENCRYPT SECURE
Connecting from the computer to the headset doesn't work as the headset
immediately disconnects the connection before I can type hcitool cc <addr>;
hcitool auth <addr> etc. Prehaps this is standard headset behavior, because on
power-up the headset automatically attempts to pair with the computer, then
meets passkey-agent. The devices are a Belkin (Broadcom) USB adapter and a
Jabra BT135; configs are similar to everyone else's that's posted on this
issue. Has anyone got a Jabra BT135 actually playing sound? Is this doable?
I think passkey-agent is alot of the issue, but possibly my hardware is junk
;)
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-03 3:45 ` jayjwa
@ 2008-02-03 4:25 ` Daniel Stumpner
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Stumpner @ 2008-02-03 4:25 UTC (permalink / raw)
To: BlueZ users
Hello,
I tried with the Patch for 3.24 and with the new version bluez-utils-3.25.
One Error Message is gone in both cases but the problem is still the
same. Is there a difference between the Authorization Agent and the
Passkey-Agent in log Messages?
(The Message "no default passkey agent" is gone.)
Now I get following output:
hcid[7839]: link_key_request (sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
audio[7846]: Requesting authorization for device 00:0D:44:30:4B:11, UUID
00001112-0000-1000-8000-00805F9B34FB
audio[7846]: State changed /org/bluez/audio/device0:
HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
audio[7846]: Access denied: Authorization agent does not exist
audio[7846]: State changed /org/bluez/audio/device0:
HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
hcid[7839]: link_key_notify (sba=00:10:C6:F8:11:7C, dba=00:0D:44:30:4B:11)
Can you tell me what further detailed information you (or I) need to
find the reason for my problem?
Thanks for your time!
Regards, Daniel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-02 9:32 ` Daniel Stumpner
2008-02-02 10:40 ` Guillaume Bedot
@ 2008-02-02 14:29 ` Guillaume Bedot
1 sibling, 0 replies; 11+ messages in thread
From: Guillaume Bedot @ 2008-02-02 14:29 UTC (permalink / raw)
To: BlueZ users
UmUsCgpMZSBzYW1lZGkgMDIgZsOpdnJpZXIgMjAwOCDDoCAxMDozMiArMDEwMCwgRGFuaWVsIFN0
dW1wbmVyIGEgw6ljcml0IDoKPiA+IGJsdWV6LWxpYnMtMy4yNAo+ID4gYmx1ZXMtdXRpbHMtMy4y
NAoKMy4yNSBpcyBvdXQuLi4gaXQgc2hvdWxkIGhlbHAuCgpSZWdhcmRzLAoKR3VpbGxhdW1lIEIu
CgoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQpUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6IE1p
Y3Jvc29mdApEZWZ5IGFsbCBjaGFsbGVuZ2VzLiBNaWNyb3NvZnQoUikgVmlzdWFsIFN0dWRpbyAy
MDA4LgpodHRwOi8vY2xrLmF0ZG10LmNvbS9NUlQvZ28vdnNlMDEyMDAwMDA3MG1ydC9kaXJlY3Qv
MDEvCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkJsdWV6
LXVzZXJzIG1haWxpbmcgbGlzdApCbHVlei11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0
cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYmx1ZXotdXNlcnMK
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-01 1:24 [Bluez-users] BT Headset connected but no sound Daniel Stumpner
2008-02-02 9:32 ` Daniel Stumpner
@ 2008-02-03 8:05 ` Guillaume Bedot
2008-02-05 13:37 ` Daniel Stumpner
1 sibling, 1 reply; 11+ messages in thread
From: Guillaume Bedot @ 2008-02-03 8:05 UTC (permalink / raw)
To: BlueZ users
SGVsbG8gYWdhaW4sCgpMZSB2ZW5kcmVkaSAwMSBmw6l2cmllciAyMDA4IMOgIDAyOjI0ICswMTAw
LCBEYW5pZWwgU3R1bXBuZXIgYSDDqWNyaXQgOgo+IAo+ICMgaGNpY29uZmlnIC1hCj4gaGNpMDog
ICBUeXBlOiBVU0IKPiAgICAgICAgIEJEIEFkZHJlc3M6IDAwOjEwOkM2OkY4OjExOjdDIEFDTCBN
VFU6IDM3NzoxMCBTQ08gTVRVOiAxNjowCj4gICAgICAgICBVUCBSVU5OSU5HIFBTQ0FOIElTQ0FO
Cj4gICAgICAgICBSWCBieXRlczo4NzE5MSBhY2w6Mjcgc2NvOjE2NzYgZXZlbnRzOjUzIGVycm9y
czowCj4gICAgICAgICBUWCBieXRlczo4MDkgYWNsOjIxIHNjbzowIGNvbW1hbmRzOjMwIGVycm9y
czowCj4gICAgICAgICBGZWF0dXJlczogMHhmZiAweGZlIDB4MGQgMHgzOCAweDA4IDB4MDggMHgw
MCAweDAwCj4gICAgICAgICBQYWNrZXQgdHlwZTogRE0xIERNMyBETTUgREgxIERIMyBESDUgSFYx
IEhWMiBIVjMKPiAgICAgICAgIExpbmsgcG9saWN5OiBSU1dJVENIIEhPTEQgU05JRkYgUEFSSwo+
ICAgICAgICAgTGluayBtb2RlOiBTTEFWRSBBQ0NFUFQKPiAgICAgICAgIE5hbWU6ICdCbHVlWiAo
MCknCj4gICAgICAgICBDbGFzczogMHgwODAxMDAKPiAgICAgICAgIFNlcnZpY2UgQ2xhc3Nlczog
Q2FwdHVyaW5nCj4gICAgICAgICBEZXZpY2UgQ2xhc3M6IENvbXB1dGVyLCBVbmNhdGVnb3JpemVk
Cj4gICAgICAgICBIQ0kgVmVyOiAxLjIgKDB4MikgSENJIFJldjogMHgxMSBMTVAgVmVyOiAxLjIg
KDB4MikgTE1QCj4gU3VidmVyOiAweDY5NjMKPiAgICAgICAgIE1hbnVmYWN0dXJlcjogQnJvYWRj
b20gQ29ycG9yYXRpb24gKDE1KQpEaWQgeW91IHRyeSB0byBhZGQgIm9wdGlvbnMgaGNpX3VzYiBm
b3JjZV9zY29maXg9MSIgdG8KeW91ciAvZXRjL21vZHByb2JlLmNvbmYgPwoKUmVnYXJkcywKCkd1
aWxsYXVtZSBCLgoKCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNv
cmVkIGJ5OiBNaWNyb3NvZnQKRGVmeSBhbGwgY2hhbGxlbmdlcy4gTWljcm9zb2Z0KFIpIFZpc3Vh
bCBTdHVkaW8gMjAwOC4KaHR0cDovL2Nsay5hdGRtdC5jb20vTVJUL2dvL3ZzZTAxMjAwMDAwNzBt
cnQvZGlyZWN0LzAxLwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXwpCbHVlei11c2VycyBtYWlsaW5nIGxpc3QKQmx1ZXotdXNlcnNAbGlzdHMuc291cmNlZm9y
Z2UubmV0Cmh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2JsdWV6
LXVzZXJzCg==
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-03 8:05 ` Guillaume Bedot
@ 2008-02-05 13:37 ` Daniel Stumpner
2008-02-05 15:25 ` Brad Midgley
2008-02-06 1:57 ` jayjwa
0 siblings, 2 replies; 11+ messages in thread
From: Daniel Stumpner @ 2008-02-05 13:37 UTC (permalink / raw)
To: BlueZ users
SGksCgpJIGdvdCBpdCB3b3JraW5nIQoKSSBwYXRjaGVkIG15IDIuNi4yMyBrZXJuZWwgd2l0aCB0
aGUgYmx1ZXotcGF0Y2ggYW5kIGF0dGFjaGVkIHRoZQpmb3JjZV9zY29maXg9MSBvcHRpb24gKHRv
IGtlcm5lbCBib290IGxpbmUgYW5kIHRvIG1vZHJvYmUuY29uZiBqdXN0IHRvCm1ha2Ugc3VyZSkK
VGhhdCBkaWRuJ3QgY2hhbmdlIGFueXRoaW5nIGZvciBtZS4KVGhlbiBJIGluc3RhbGxlZCB0aGUg
Ymx1ZXotZ25vbWUgYWdlbnQgYW5kIHN0YXJ0ZWQgdGhlIGFwcGxldC4gVGhhdApoZWxwZWQgbWUg
Z2V0dGluZyByaWQgb2YgdGhlIHdhcm5pbmcgdGhhdCBubyBhdXRob3JpemF0aW9uIGFnZW50IGlz
CmF2YWlsYWJsZS4KU2hvdWxkJ3QgYmUgb25lIGluIGJsdWV6LXV0aWxzL2RhZW1vbi9hdXRoLWFn
ZW50LmMgID8/PwpIb3cgY2FuIEkgZ2V0IHRoaXMgb25lIHdvcmtpbmc/CgoKSSBjYW4gcGxheSBh
bmQgcmVjb3JkIHdpdGggYXBsYXkvYXJlY29yZCBhbmQgcGxheSB3aXRoIG1wbGF5ZXIuCgpJIGFt
IHVzaW5nIHR3aW5rbGUgZm9yIFNJUCwgYnV0IEkgY2FuJ3QgZ2V0IGl0IHdvcmtpbmcgd2l0aCBi
bHVldG9vdGguCklzIHRoZXJlIGEgd2F5IHRoYXQgSSBjYW4gc2VlIHRoZSBoZWFkc2V0IGFzIGEg
YWxzYS1kZXZpY2UgaW4KL3Byb2MvYXNvdW5kL2NhcmRzIGFuZCB0aGF0IGFsbCBhcHBsaWNhdGlv
bnMgY2FuIHVzZSBpdCBsaWtlIGEgc3RhbmRhcmQKYXVkaW8tZGV2aWNlIChhbHNhbWl4ZXIsIGV0
Yy4uLik/CgpCZXN0IHJlZ2FyZHMsIERhbmllbAoKCgpHdWlsbGF1bWUgQmVkb3Qgd3JvdGU6Cj4g
SGVsbG8gYWdhaW4sCj4gCj4gTGUgdmVuZHJlZGkgMDEgZsOpdnJpZXIgMjAwOCDDoCAwMjoyNCAr
MDEwMCwgRGFuaWVsIFN0dW1wbmVyIGEgw6ljcml0IDoKPj4gIyBoY2ljb25maWcgLWEKPj4gaGNp
MDogICBUeXBlOiBVU0IKPj4gICAgICAgICBCRCBBZGRyZXNzOiAwMDoxMDpDNjpGODoxMTo3QyBB
Q0wgTVRVOiAzNzc6MTAgU0NPIE1UVTogMTY6MAo+PiAgICAgICAgIFVQIFJVTk5JTkcgUFNDQU4g
SVNDQU4KPj4gICAgICAgICBSWCBieXRlczo4NzE5MSBhY2w6Mjcgc2NvOjE2NzYgZXZlbnRzOjUz
IGVycm9yczowCj4+ICAgICAgICAgVFggYnl0ZXM6ODA5IGFjbDoyMSBzY286MCBjb21tYW5kczoz
MCBlcnJvcnM6MAo+PiAgICAgICAgIEZlYXR1cmVzOiAweGZmIDB4ZmUgMHgwZCAweDM4IDB4MDgg
MHgwOCAweDAwIDB4MDAKPj4gICAgICAgICBQYWNrZXQgdHlwZTogRE0xIERNMyBETTUgREgxIERI
MyBESDUgSFYxIEhWMiBIVjMKPj4gICAgICAgICBMaW5rIHBvbGljeTogUlNXSVRDSCBIT0xEIFNO
SUZGIFBBUksKPj4gICAgICAgICBMaW5rIG1vZGU6IFNMQVZFIEFDQ0VQVAo+PiAgICAgICAgIE5h
bWU6ICdCbHVlWiAoMCknCj4+ICAgICAgICAgQ2xhc3M6IDB4MDgwMTAwCj4+ICAgICAgICAgU2Vy
dmljZSBDbGFzc2VzOiBDYXB0dXJpbmcKPj4gICAgICAgICBEZXZpY2UgQ2xhc3M6IENvbXB1dGVy
LCBVbmNhdGVnb3JpemVkCj4+ICAgICAgICAgSENJIFZlcjogMS4yICgweDIpIEhDSSBSZXY6IDB4
MTEgTE1QIFZlcjogMS4yICgweDIpIExNUAo+PiBTdWJ2ZXI6IDB4Njk2Mwo+PiAgICAgICAgIE1h
bnVmYWN0dXJlcjogQnJvYWRjb20gQ29ycG9yYXRpb24gKDE1KQo+IERpZCB5b3UgdHJ5IHRvIGFk
ZCAib3B0aW9ucyBoY2lfdXNiIGZvcmNlX3Njb2ZpeD0xIiB0bwo+IHlvdXIgL2V0Yy9tb2Rwcm9i
ZS5jb25mID8KPiAKPiBSZWdhcmRzLAo+IAo+IEd1aWxsYXVtZSBCLgo+IAo+IAo+IC0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0KPiBUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6IE1pY3Jvc29mdAo+
IERlZnkgYWxsIGNoYWxsZW5nZXMuIE1pY3Jvc29mdChSKSBWaXN1YWwgU3R1ZGlvIDIwMDguCj4g
aHR0cDovL2Nsay5hdGRtdC5jb20vTVJUL2dvL3ZzZTAxMjAwMDAwNzBtcnQvZGlyZWN0LzAxLwo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gQmx1ZXot
dXNlcnMgbWFpbGluZyBsaXN0Cj4gQmx1ZXotdXNlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4g
aHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYmx1ZXotdXNlcnMK
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0KVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OiBNaWNy
b3NvZnQKRGVmeSBhbGwgY2hhbGxlbmdlcy4gTWljcm9zb2Z0KFIpIFZpc3VhbCBTdHVkaW8gMjAw
OC4KaHR0cDovL2Nsay5hdGRtdC5jb20vTVJUL2dvL3ZzZTAxMjAwMDAwNzBtcnQvZGlyZWN0LzAx
LwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpCbHVlei11
c2VycyBtYWlsaW5nIGxpc3QKQmx1ZXotdXNlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0Cmh0dHBz
Oi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2JsdWV6LXVzZXJzCg==
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-05 13:37 ` Daniel Stumpner
@ 2008-02-05 15:25 ` Brad Midgley
2008-02-06 1:57 ` jayjwa
1 sibling, 0 replies; 11+ messages in thread
From: Brad Midgley @ 2008-02-05 15:25 UTC (permalink / raw)
To: BlueZ users
Daniel
> I am using twinkle for SIP, but I can't get it working with bluetooth.
> Is there a way that I can see the headset as a alsa-device in
> /proc/asound/cards and that all applications can use it like a standard
> audio-device (alsamixer, etc...)?
sorry...alsa does not allow the plugin to show up in the standard list.
you should be able to choose "ALSA: other device" and type in
"bluetooth" or whatever you named the plugin in /etc/asound.conf or
~/.asounrc
--
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
2008-02-05 13:37 ` Daniel Stumpner
2008-02-05 15:25 ` Brad Midgley
@ 2008-02-06 1:57 ` jayjwa
1 sibling, 0 replies; 11+ messages in thread
From: jayjwa @ 2008-02-06 1:57 UTC (permalink / raw)
To: BlueZ users
On Tue, 5 Feb 2008, Daniel Stumpner wrote:
-> I got it working!
Lucky ;)
I think I have some hardware incompatibility problems, because my
logs are looking OK now, and the system device appears to transmit sound while
the headset acts like it's receiving sound (yet no sound).
-> I patched my 2.6.23 kernel with the bluez-patch and attached the
-> force_scofix=1 option (to kernel boot line and to modrobe.conf just to
-> make sure)
-> That didn't change anything for me.
-> Then I installed the bluez-gnome agent and started the applet. That
-> helped me getting rid of the warning that no authorization agent is
-> available.
-> Should't be one in bluez-utils/daemon/auth-agent.c ???
Yes, there should be a binary auth-agent.
-rwxr-xr-x 1 root bin 8552 2008-02-05 02:13 /usr/bin/auth-agent
-> How can I get this one working?
I've been starting both passkey-agent and auth-agent. I've not seen auth
failures in my logs now. Start them before you try to use remote device.
passkey-agent --default (pin) (addr of remote device) &
auth-agent &
Both should background. That's from trial and error, I've not seen that
documented anyplace. But it seems to work. YMMV.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-users] BT Headset connected but no sound
@ 2008-02-05 11:40 pramod gurav
0 siblings, 0 replies; 11+ messages in thread
From: pramod gurav @ 2008-02-05 11:40 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 16092 bytes --]
hi same thing here
But i was asked to update my kernel(2.6.15)
Now I compiled 2.6.22 But no difference ..headset get connected but
the system hangs with white screen ...
Which kernel are you using...?
Have you applied patch for :SCO flow control from plugs..
i tried it but failing with both the kernel....
Which patch did you apply
Please reply as your done things may help me...
Thanks and Best regards
Pramod
----- Original Message ----
From: Daniel Stumpner <bigstumpi@gmx.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Sent: Saturday, 2 February, 2008 3:02:54 PM
Subject: Re: [Bluez-users] BT Headset connected but no sound
Daniel
Stumpner
wrote:
>
Hi,
>
>
can
connect
to
my
BT
Headset
but
if
I
try
to
play
a
sound,
it
does
only
>
beep
at
the
start
and
at
the
end
of
the
connection
but
there
is
no
sound.
>
>
mplayer
-ao
alsa:device=bluetooth
test.wav
>
-
beep
-
>
(pressing
'q')
>
-
beep
-
>
>
I
am
running
Gentoo
with
linux
2.6.23
(x86)
>
bluez-libs-3.24
>
blues-utils-3.24
>
>
>
========================================================================
>
Some
Debug
Information:
>
========================================================================
>
>
#
lsusb
>
Bus
002
Device
002:
ID
046d:c012
Logitech,
Inc.
Optical
Mouse
>
Bus
002
Device
001:
ID
0000:0000
>
Bus
004
Device
001:
ID
0000:0000
>
Bus
003
Device
002:
ID
03f0:011d
Hewlett-Packard
/*
Critical
line
*/
>
Bus
003
Device
001:
ID
0000:0000
>
Bus
001
Device
001:
ID
0000:0000
>
>
------------------------------------------------------------------------
>
>
#
cat
/proc/bus/usb/devices
|
grep
-e^[TPD]
|
grep
-e
Cls=e0
-B1
-A1
>
T:
Bus=03
Lev=01
Prnt=01
Port=01
Cnt=01
Dev#=
2
Spd=12
MxCh=
0
>
D:
Ver=
1.10
Cls=e0(unk.
)
Sub=01
Prot=01
MxPS=64
#Cfgs=
1
>
P:
Vendor=03f0
ProdID=011d
Rev=
0.17
>
>
------------------------------------------------------------------------
>
>
#
hciconfig
-a
>
hci0:
Type:
USB
>
BD
Address:
00:10:C6:F8:11:7C
ACL
MTU:
377:10
SCO
MTU:
16:0
>
UP
RUNNING
PSCAN
ISCAN
>
RX
bytes:87191
acl:27
sco:1676
events:53
errors:0
>
TX
bytes:809
acl:21
sco:0
commands:30
errors:0
>
Features:
0xff
0xfe
0x0d
0x38
0x08
0x08
0x00
0x00
>
Packet
type:
DM1
DM3
DM5
DH1
DH3
DH5
HV1
HV2
HV3
>
Link
policy:
RSWITCH
HOLD
SNIFF
PARK
>
Link
mode:
SLAVE
ACCEPT
>
Name:
'BlueZ
(0)'
>
Class:
0x080100
>
Service
Classes:
Capturing
>
Device
Class:
Computer,
Uncategorized
>
HCI
Ver:
1.2
(0x2)
HCI
Rev:
0x11
LMP
Ver:
1.2
(0x2)
LMP
Subver:
0x6963
>
Manufacturer:
Broadcom
Corporation
(15)
>
>
------------------------------------------------------------------------
>
>
#
hcitool
info
00:0D:44:30:4B:11
/*
My
Logitech
headset
*/
>
Requesting
information
...
>
BD
Address:
00:0D:44:30:4B:11
>
LMP
Version:
1.2
(0x2)
LMP
Subversion:
0x611
>
Manufacturer:
Cambridge
Silicon
Radio
(10)
>
Features:
0xfc
0xfe
0x0f
0x00
0x08
0x08
0x00
0x00
>
<encryption>
<slot
offset>
<timing
accuracy>
<role
switch>
>
<hold
mode>
<sniff
mode>
<RSSI>
<channel
quality>
<SCO
link>
>
<HV2
packets>
<HV3
packets>
<u-law
log>
<A-law
log>
<CVSD>
>
<paging
scheme>
<power
control>
<transparent
SCO>
>
<AFH
cap.
slave>
<AFH
cap.
master>
>
>
------------------------------------------------------------------------
>
>
#
rfcomm
>
rfcomm0:
00:0D:44:30:4B:11
channel
1
clean
>
>
------------------------------------------------------------------------
>
>
#
l2ping
00:0D:44:30:4B:11
>
Ping:
00:0D:44:30:4B:11
from
00:10:C6:F8:11:7C
(data
size
44)
...
>
44
bytes
from
00:0D:44:30:4B:11
id
0
time
34.40ms
>
44
bytes
from
00:0D:44:30:4B:11
id
1
time
52.72ms
>
2
sent,
2
received,
0%
loss
>
>
------------------------------------------------------------------------
>
>
#
cat
/etc/asound.conf
>
pcm.bluetooth
{
>
type
bluetooth
>
device
00:0D:44:30:4B:11
>
}
>
>
------------------------------------------------------------------------
>
>
#
cat
/proc/asound/cards
>
0
[ICH6
]:
ICH4
-
Intel
ICH6
>
Intel
ICH6
with
AD1981B
at
irq
21
>
1
[Modem
]:
ICH-MODEM
-
Intel
ICH6
Modem
>
Intel
ICH6
Modem
at
irq
19
>
>
------------------------------------------------------------------------
>
>
#
tail
-f
/var/log/messages
/*
before
executing
the
above
mplayer
>
command
*/
>
Feb
1
00:36:25
snake
audio[8329]:
Accepted
new
client
connection
on
>
unix
socket
(fd=9)
>
Feb
1
00:36:25
snake
audio[8329]:
Audio
API:
received
>
BT_GETCAPABILITIES_REQ
>
Feb
1
00:36:25
snake
audio[8329]:
Audio
API:
sending
BT_GETCAPABILITIES_RSP
>
Feb
1
00:36:25
snake
audio[8329]:
Audio
API:
received
>
BT_SETCONFIGURATION_REQ
>
Feb
1
00:36:25
snake
audio[8329]:
State
changed
>
/org/bluez/audio/device0:
HEADSET_STATE_DISCONNECTED
->
>
HEADSET_STATE_CONNECT_IN_PROGRESS
>
Feb
1
00:36:29
snake
hcid[8156]:
link_key_request
>
(sba=00:10:C6:F8:11:7C,
dba=00:0D:44:30:4B:11)
>
Feb
1
00:36:29
snake
audio[8329]:
/org/bluez/audio/device0:
Connecting
>
to
00:0D:44:30:4B:11
channel
1
>
Feb
1
00:36:30
snake
audio[8329]:
State
changed
>
/org/bluez/audio/device0:
HEADSET_STATE_CONNECT_IN_PROGRESS
->
>
HEADSET_STATE_CONNECTED
>
Feb
1
00:36:30
snake
audio[8329]:
/org/bluez/audio/device0:
Connected
>
to
00:0D:44:30:4B:11
>
Feb
1
00:36:30
snake
audio[8329]:
State
changed
>
/org/bluez/audio/device0:
HEADSET_STATE_CONNECTED
->
>
HEADSET_STATE_PLAY_IN_PROGRESS
>
Feb
1
00:36:30
snake
audio[8329]:
SCO
socket
opened
for
headset
>
/org/bluez/audio/device0
>
Feb
1
00:36:30
snake
audio[8329]:
SCO
fd=11
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
>
BT_SETCONFIGURATION_RSP
>
Feb
1
00:36:30
snake
audio[8329]:
State
changed
>
/org/bluez/audio/device0:
HEADSET_STATE_PLAY_IN_PROGRESS
->
>
HEADSET_STATE_PLAYING
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:30
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
0
>
Feb
1
00:36:30
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
0
>
Feb
1
00:36:30
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
0
>
Feb
1
00:36:30
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
0
>
Feb
1
00:36:30
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
0
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:30
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
received
BT_STREAMSTART_REQ
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMSTART_RSP
>
Feb
1
00:36:31
snake
audio[8329]:
Audio
API:
sending
BT_STREAMFD_IND
>
Feb
1
00:36:31
snake
audio[8329]:
Unix
client
disconnected
(fd=9)
>
Feb
1
00:36:31
snake
audio[8329]:
State
changed
>
/org/bluez/audio/device0:
HEADSET_STATE_PLAYING
->
>
HEADSET_STATE_DISCONNECTED
>
Feb
1
00:36:31
snake
hci_scodata_packet:
hci0
SCO
packet
for
unknown
>
connection
handle
1
>
>
>
========================================================================
>
End
of
debug
info
>
========================================================================
>
>
>
>
I
have
no
Idea
where
to
start
searching
the
problem...
>
Somewhere
I
read
that
Broadcom
Chips
aren't
fully
supported.
May
I
need
>
firmware
perhaps?
Would
l2ping
work
in
this
case?
(In
my
case
it
DOES
>
work!?)
>
Quote:
>
"If
you
have
a
Broadcom
Chipset
or
Hewlett-Packard
Integrated
Chipset
>
(such
as
mine
on
HP
nx8220)
then
you
really
want
to
pass
>
'force_scofix=1'
as
argument
to
kernel:
it
was
the
only
way
to
make
work
>
hci_usb
properly
with
my
chip.
NOTE:
bcm203x
won't
recognize
HP
>
Integrated
as
a
valid
chip
(03f0:011d
instead
of
0a5c:2033
-
you
can
>
check
this
with
lsusb),
then
don't
even
try
to
make
it
work."
>
>
May
I
have
an
error
in
my
alsa-config?
There
is
no
card
displayed...
>
>
>
Thanks
for
your
time!
>
Best
regards,
Daniel
>
>
>
-------------------------------------------------------------------------
>
This
SF.net
email
is
sponsored
by:
Microsoft
>
Defy
all
challenges.
Microsoft(R)
Visual
Studio
2008.
>
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
_______________________________________________
>
Bluez-users
mailing
list
>
Bluez-users@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bluez-users
>
Hi
again,
I
got
new
info:
this
is
a
part
of
the
hcid-log
in
my
messages
when
I
switch
on
my
headset.
Seems
that
I
have
no
Key-Agent...
#passkey-agent
--help
/*
tells
me
that
I
have
Version
3.24
*/
Do
I
have
to
set
it
up
manually?
So
I
did
the
following:
#passkey-agent
--default
0000
/*
test
key
*/
I
see:
hcid[14592]:
Default
passkey
agent
(:1.41,
/org/bluez/passkey_agent_14605)
registered
But
the
errors
don't
change...
What
do
I
have
to
do
to
get
my
key-agent
working?
Best
regards,
Daniel
LOG
(when
switching
on
headset):
==========================================================================
hcid[10257]:
link_key_request
(sba=00:10:C6:F8:11:7C,
dba=00:0D:44:30:4B:11)
hcid[10257]:
/org/bluez:
org.bluez.Database.RequestAuthorization()
hcid[10257]:
handle_authorize_request
hcid[10257]:
no
default
agent
audio[10261]:
Requesting
authorization
for
device
00:0D:44:30:4B:11,
UUID
0000111F-0000-1000-8000-00805F9B34FB
audio[10261]:
State
changed
/org/bluez/audio/device0:
HEADSET_STATE_DISCONNECTED
->
HEADSET_STATE_CONNECT_IN_PROGRESS
audio[10261]:
Access
denied:
Authorization
agent
does
not
exist
audio[10261]:
State
changed
/org/bluez/audio/device0:
HEADSET_STATE_CONNECT_IN_PROGRESS
->
HEADSET_STATE_DISCONNECTED
hcid[10257]:
link_key_notify
(sba=00:10:C6:F8:11:7C,
dba=00:0D:44:30:4B:11)
==========================================================================
-------------------------------------------------------------------------
This
SF.net
email
is
sponsored
by:
Microsoft
Defy
all
challenges.
Microsoft(R)
Visual
Studio
2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users
mailing
list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
Forgot the famous last words? Access your message archive online at http://in.messenger.yahoo.com/webmessengerpromo.php
[-- Attachment #1.2: Type: text/html, Size: 19701 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2008-02-06 1:57 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-01 1:24 [Bluez-users] BT Headset connected but no sound Daniel Stumpner
2008-02-02 9:32 ` Daniel Stumpner
2008-02-02 10:40 ` Guillaume Bedot
2008-02-03 3:45 ` jayjwa
2008-02-03 4:25 ` Daniel Stumpner
2008-02-02 14:29 ` Guillaume Bedot
2008-02-03 8:05 ` Guillaume Bedot
2008-02-05 13:37 ` Daniel Stumpner
2008-02-05 15:25 ` Brad Midgley
2008-02-06 1:57 ` jayjwa
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 11:40 pramod gurav
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox