* [Bluez-devel] SCO headsetd: "appli closed connection"
@ 2007-03-28 6:36 Marc Haber
2007-03-28 8:10 ` Tim Chick
2007-04-11 10:56 ` [Bluez-devel] SCO headset does work only sporadically, how to debug? Marc Haber
0 siblings, 2 replies; 4+ messages in thread
From: Marc Haber @ 2007-03-28 6:36 UTC (permalink / raw)
To: BlueZ development
I am trying to use a Jabra BT 330 with ALSA. My system is Debian
unstable, running Liux 2.6.20.4 patched with the SCO timing patch.
Last night, I was able to do a single VoIP call using twinkle, and
then things stopped working.
When twinkle starts up, I start hearing very low background hiss in
the headset, so the connection seems to actually work, but when the
application tries sending in actual data, nothing is heard. This is
headsetd's output:
$ headsetd -n
headsetd[30223]: Bluetooth headset daemon version 0.5
headsetd[30223]: Configuration phase ended: target bdaddr is 00:07:A4:BA:48:59, timeout is 6000 ms
headsetd[30223]: Changing state: Idle-->Paging
headsetd[30223]: Changing state: Paging-->Connecting
Headset connected
headsetd[30223]: Changing state: Connecting-->Ready
headsetd[30223]: Changing state: Ready-->Opening
headsetd[30223]: SCO channel opened handle=0x002c mtu=64
headsetd[30223]: Changing state: Opening-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
headsetd[30223]: Changing state: Zombie-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
Received from HS: AT+VGS=10
headsetd[30223]: Changing state: Zombie-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
headsetd[30223]: Changing state: Zombie-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
headsetd[30223]: Changing state: Zombie-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
headsetd[30223]: Changing state: Zombie-->Streaming
headsetd[30223]: Appli closed socket
headsetd[30223]: Changing state: Streaming-->Zombie
headsetd[30223]: Nobody uses SCO channel anymore, closing it.
headsetd[30223]: Changing state: Zombie-->Connected
headsetd[30223]: exiting cleanly
When I try amarok to play back an MP3 file, the same thing happens,
only that the three lines "Streaming-->Zombie", "Zombie-->Streaming",
"Appli closed socket" repeat a lot more often.
What might be going wrong here? Is there any more information that you
need?
I am particularly stymied that it worked once and ceased to do so later.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-devel] SCO headsetd: "appli closed connection"
2007-03-28 6:36 [Bluez-devel] SCO headsetd: "appli closed connection" Marc Haber
@ 2007-03-28 8:10 ` Tim Chick
2007-03-28 10:30 ` Marc Haber
2007-04-11 10:56 ` [Bluez-devel] SCO headset does work only sporadically, how to debug? Marc Haber
1 sibling, 1 reply; 4+ messages in thread
From: Tim Chick @ 2007-03-28 8:10 UTC (permalink / raw)
To: bluez-devel
On Wednesday 28 March 2007 07:36, Marc Haber wrote:
> I am trying to use a Jabra BT 330 with ALSA. My system is Debian
> unstable, running Liux 2.6.20.4 patched with the SCO timing patch.
> Last night, I was able to do a single VoIP call using twinkle, and
> then things stopped working.
>
Try putting the headset into pairing mode again, that fixed it for me. Don't
know why though!
Tim
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-devel] SCO headsetd: "appli closed connection"
2007-03-28 8:10 ` Tim Chick
@ 2007-03-28 10:30 ` Marc Haber
0 siblings, 0 replies; 4+ messages in thread
From: Marc Haber @ 2007-03-28 10:30 UTC (permalink / raw)
To: bluez-devel
On Wed, Mar 28, 2007 at 09:10:05AM +0100, Tim Chick wrote:
> On Wednesday 28 March 2007 07:36, Marc Haber wrote:
> > I am trying to use a Jabra BT 330 with ALSA. My system is Debian
> > unstable, running Liux 2.6.20.4 patched with the SCO timing patch.
> > Last night, I was able to do a single VoIP call using twinkle, and
> > then things stopped working.
>
> Try putting the headset into pairing mode again, that fixed it for me. Don't
> know why though!
This only causes the PIN dialog to pop up when trying to connect, and
after giving the PIN the behavior is as reported in my original message.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bluez-devel] SCO headset does work only sporadically, how to debug?
2007-03-28 6:36 [Bluez-devel] SCO headsetd: "appli closed connection" Marc Haber
2007-03-28 8:10 ` Tim Chick
@ 2007-04-11 10:56 ` Marc Haber
1 sibling, 0 replies; 4+ messages in thread
From: Marc Haber @ 2007-04-11 10:56 UTC (permalink / raw)
To: BlueZ development
On Wed, Mar 28, 2007 at 08:36:25AM +0200, Marc Haber wrote:
> I am trying to use a Jabra BT 330 with ALSA. My system is Debian
> unstable, running Liux 2.6.20.4 patched with the SCO timing patch.
> Last night, I was able to do a single VoIP call using twinkle, and
> then things stopped working.
>
> When twinkle starts up, I start hearing very low background hiss in
> the headset, so the connection seems to actually work, but when the
> application tries sending in actual data, nothing is heard.
Usually, the other side of the call can hear me talking, but I cannot
hear the other side talking. Seldomly, the connection works fine. I
therefore suspect that the headset is correctly paired.
Trying to play a WAV file to the headset ends in "aplay:
set_params:909: Channels count not available:"
$ aplay --device=headset /mnt/usr/usr/share/sounds/KDE_Startup_new.wav
Playing WAVE '/mnt/usr/usr/share/sounds/KDE_Startup_new.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
aplay: set_params:909: Channels count non available
My notebook has Bluetooth built in which shows itself as a USB device:
Bus 003 Device 014: ID 049f:0086 Compaq Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x049f Compaq Computer Corp.
idProduct 0x0086
bcdDevice 8.02
iManufacturer 1 ACTIONTEC
iProduct 2 Bluetooth by hp
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 193
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 138mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 0
iInterface 0
Device Status: 0x0001
Self Powered
The headset is a Jabra BT 330.
$ sudo hciconfig -a
hci0: Type: USB
BD Address: 00:0F:B3:6C:4E:64 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:3063173 acl:53 sco:59943 events:159 errors:0
TX bytes:269476 acl:40 sco:5253 commands:68 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'scyw00225-0'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x322 LMP Ver: 1.1 (0x1) LMP Subver: 0x322
Manufacturer: Cambridge Silicon Radio (10)
$ sudo hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0F:B3:6C:4E:64 ACL MTU: 192:8 SCO MTU: 64:8
Build 802
Chip version: BlueCore02-External
Max key size: 128 bit
SCO mapping: HCI
$ sudo hcitool info 00:07:A4:BA:48:59
Requesting information ...
BD Address: 00:07:A4:BA:48:59
Device Name: Jabra BT330
LMP Version: 1.2 (0x2) LMP Subversion: 0x612
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <park state> <RSSI> <channel quality>
<SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log>
<CVSD> <paging scheme> <transparent SCO>
hcidump -X -V gives copious output. Do you really want to see that?
running kernel 2.6.20.4, bluetooth-alsa version 0.5cvs20070327-1 from
Debian unstable
How do I find out whether my headset can do a2dp?
How can I use aplay with the headset?
Any hints will be appreciated.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-04-11 10:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-28 6:36 [Bluez-devel] SCO headsetd: "appli closed connection" Marc Haber
2007-03-28 8:10 ` Tim Chick
2007-03-28 10:30 ` Marc Haber
2007-04-11 10:56 ` [Bluez-devel] SCO headset does work only sporadically, how to debug? Marc Haber
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox