From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Date: Sat, 23 Feb 2008 20:09:59 -0500 [thread overview]
Message-ID: <1203815399.8021.10.camel@pc.ilinx> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3004 bytes --]
I'm running Ubuntu Hardy, so I have a nice bleeding edge installation of
kernel and bluez tools. I am trying to get a Jabra headset to work but
it's just not happening for me. I plug in the dongle and get the little
bluetooth applet showing in my taskbar. My headset also beeps when this
happens.
lsusb reports:
Bus 001 Device 009: ID 0a5c:2121 Broadcom Corp.
lsbusb -v reports:
Bus 001 Device 009: ID 0a5c:2121 Broadcom Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x2121
bcdDevice 1.00
iManufacturer 1 Broadcom Corp
iProduct 2 BCM92045B3 ROM
iSerial 0
bNumConfigurations 1
...
I believe it's all paired up nicely:
$ hcitool con
Connections:
> ACL 00:1A:45:1B:19:89 handle 11 state 1 lm SLAVE AUTH ENCRYPT SECURE
I follow the steps in http://wiki.bluez.org/wiki/HOWTO/AudioDevices but
when I try to play something with:
$ sox /mnt/mp3/bad_mouth.wav -t wav -c 1 - | aplay -D plug:bluetooth
sox wav: Length in output .wav header will be wrong since can't seek to fix it
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono
I hear nothing and the dmesg/console log shows:
Feb 23 20:05:48 pc kernel: [20205.288394] Bluetooth: L2CAP ver 2.9
Feb 23 20:05:48 pc kernel: [20205.288405] Bluetooth: L2CAP socket layer initialized
Feb 23 20:05:48 pc kernel: [20205.297727] Bluetooth: RFCOMM socket layer initialized
Feb 23 20:05:48 pc kernel: [20205.297748] Bluetooth: RFCOMM TTY layer initialized
Feb 23 20:05:48 pc kernel: [20205.297750] Bluetooth: RFCOMM ver 1.8
Feb 23 20:06:37 pc kernel: [20254.100422] Bluetooth: SCO (Voice Link) ver 0.5
Feb 23 20:06:37 pc kernel: [20254.100431] Bluetooth: SCO socket layer initialized
Feb 23 20:06:37 pc kernel: [20254.788127] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.798114] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.798118] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.798121] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.808103] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.808107] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.808110] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Feb 23 20:06:37 pc kernel: [20254.818100] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
[ and on and on and on ]
Anyone got any advise?
Thanx,
b.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 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
next reply other threads:[~2008-02-24 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 1:09 Brian J. Murrell [this message]
2008-02-24 20:25 ` [Bluez-users] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1 Brad Midgley
2008-02-25 1:02 ` Brian J. Murrell
2008-02-25 1:29 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1203815399.8021.10.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.