Hi, I can't get snd-bt-sco (bluetooth-alsa) to work and was told this
was the best place to ask for help:
The problem is, btsco starts up successfully, the device indicates a
connection has been made, but no audio can be read or written, and after
maybe a minute the device indicates the connection has been dropped.
There is no noticeable difference on the host side at this point, i.e.
audio apps directed at the headset still just hang, and btsco is still
there. The mixer produces output from btsco, but has no effect on the
device.
Driver version: bluetooth-alsa CVS checked out 02/12/2004
Kernel: 2.6.9 debian (presence / absence of hci_usb patch seems to make
no difference)
Host bluetooth adapter: Trust BT180 USB
http://www.trust.com/home/default.htm?viewpage=service/sss/preview.htm%3Fartnr%3D13853
Headset: Logitech Mobile Bluetooth Headset
http://www.thinkgeek.com/computing/speakers/headsets/65ff/
Also tested: Nokia 6310i, various channels (this functionality works
under windows)
I'd be grateful for any hints you can give me.
Thanks,
--
Chris Boyle - http://cmb.is-a-geek.org/
GPG: B7D86E0F, MSN: [email protected], ICQ: 24151961,
AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Boyle wrote:
| On Tue, Dec 07, 2004 at 08:37:56AM +0100, Sebastian Roth wrote:
| As mentioned in reply to Brad Midgley, this established a successful
| connection (pressing the volume buttons affected alsamixer), but I
| still couldn't actually get any audio to flow in either direction,
| despite continuous SCO data packets seen with hcidump, although only in
| one direction.
I just wanted to point out that the volume control messages are sent
over the HCI channel, while audio data is send over the SCO channel.
It's likely that if there's a problem with the SCO data transfer, the
volume buttons will still work.
With my headset, I can hear the volume increasing because the noise gets
loader.
You could also try the "loopback" mode; just don't use any audio
software, but activate the loopback i.e. in alsamixer by unmuting and
then press the headset button to connect.
Audio should than be routed back to the headset so you can "hear
yourself". Makes it easier to determine whether there's a bluez/sco
problem or something with your audio setup :)
good luck,
~ Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBtxE6QWC6DTWkDAoRAqVIAKC+2cyao0HoZPqBoK1rbwO6JbIHWwCgtEBN
lLLFf5eU+dU34SiO3lwc17g=
=G1e+
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
>As mentioned in reply to Brad Midgley, this established a successful
>connection (pressing the volume buttons affected alsamixer), but I
>still couldn't actually get any audio to flow in either direction,
>despite continuous SCO data packets seen with hcidump, although only in
>one direction.
>
>
Hi,
i had the same problem in the first.
Possible options:
a) Other soundcards
b) Insufficent rights on /dev/dsp* /dev/audio* /dev/sound* or /dev/snd/*
Cu Thomas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Tue, Dec 07, 2004 at 08:37:56AM +0100, Sebastian Roth wrote:
> Please post the ouput of `hciconfig hci0 revision'
zeus:~# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0B:0D:40:6C:63 ACL MTU: 120:20 SCO MTU: 64:0
Unsupported manufacturer
> The second issue was that all "sound-apps" were blocking (hanging)
> without playing any sound. My headsets (both from Anycom) must be
> activated with the switch to recieve the sound. Just like answer the
> telephone.
As mentioned in reply to Brad Midgley, this established a successful
connection (pressing the volume buttons affected alsamixer), but I
still couldn't actually get any audio to flow in either direction,
despite continuous SCO data packets seen with hcidump, although only in
one direction.
"> SCO data: handle 0x0100 dlen 24"
--
Chris Boyle - http://cmb.is-a-geek.org/
GPG: B7D86E0F, MSN: [email protected], ICQ: 24151961,
AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Tue, Dec 07, 2004 at 08:10:33PM -0700, Brad Midgley wrote:
> Did it start working when you clicked the 'connect' button on the
> headset? Sebastian pointed out that this was something one might miss so
> I highlighted it recently in the docs.
Almost, but not quite. btsco looked more successful, and with hcidump I
could see a lot of SCO data flowing, but still audio apps would hang. I
could however press the volume buttons on the headset and see the mixer
change, so there was definitely a connection.
--
Chris Boyle - http://cmb.is-a-geek.org/
GPG: B7D86E0F, MSN: [email protected], ICQ: 24151961,
AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Tue, Dec 07, 2004 at 08:57:23AM +0100, Marcel Holtmann wrote:
> why don't you try 2.6.9-mh5 or 2.6.10-rc3 ?
I might do that later, this machine is used for quite a lot of different
things...
> > Host bluetooth adapter: Trust BT180 USB
> > http://www.trust.com/home/default.htm?viewpage=service/sss/preview.htm%3Fartnr%3D13853
> > Headset: Logitech Mobile Bluetooth Headset
> > http://www.thinkgeek.com/computing/speakers/headsets/65ff/
> > Also tested: Nokia 6310i, various channels (this functionality works
> > under windows)
>
> what is the output of "hciconfig -a" and "hcitool info ..." for these
> devices. And include "/proc/bus/usb/devices".
zeus:~# hciconfig -a
hci0: Type: USB
BD Address: 00:0B:0D:40:6C:63 ACL MTU: 120:20 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:7475162 acl:256 sco:276593 events:309 errors:0
TX bytes:4578 acl:216 sco:0 commands:48 errors:0
Features: 0xff 0xff 0x05 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: 'zeus'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1) LMP Subver: 0x757
Manufacturer: Silicon Wave (11)
zeus:~# hcitool info 00:0D:44:00:36:41 # headset
Requesting information ...
BD Address: 00:0D:44:00:36:41
Device Name: Logitech HS01
LMP Version: 1.1 (0x1) LMP Subversion: 0x32b
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <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>
<power control> <transparent SCO>
zeus:~# hcitool info 00:02:EE:65:EB:27 # phone
Requesting information ...
BD Address: 00:02:EE:65:EB:27
Device Name: cmb's phone
LMP Version: 1.1 (0x1) LMP Subversion: 0x226
Manufacturer: Nokia Mobile Phones (1)
Features: 0xbf 0x28 0x21 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode> <SCO link>
<HV3 packets> <CVSD>
zeus:~# cat /proc/bus/usb/devices
T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 25/900 us ( 3%), #Int= 1, #Iso= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 uhci_hcd
S: Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
S: SerialNumber=0000:01:07.1
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
[snip FM radio]
T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0c10 ProdID=0000 Rev=15.00
S: Manufacturer=SiW
S: Product=SiW
S: SerialNumber=636C400D0B00
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 uhci_hcd
S: Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
S: SerialNumber=0000:01:07.0
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 4
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 ehci_hcd
S: Product=VIA Technologies, Inc. USB 2.0
S: SerialNumber=0000:01:07.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 ehci_hcd
S: Product=nVidia Corporation nForce2 USB Controller
S: SerialNumber=0000:00:02.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
[snip memory card reader]
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 29/900 us ( 3%), #Int= 3, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 ohci_hcd
S: Product=nVidia Corporation nForce2 USB Controller (#2)
S: SerialNumber=0000:00:02.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
[snip keyboard & mouse]
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.9 ohci_hcd
S: Product=nVidia Corporation nForce2 USB Controller
S: SerialNumber=0000:00:02.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
[snip joystick & webcam]
--
Chris Boyle - http://cmb.is-a-geek.org/
GPG: B7D86E0F, MSN: [email protected], ICQ: 24151961,
AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Chris,
Did it start working when you clicked the 'connect' button on the
headset? Sebastian pointed out that this was something one might miss so
I highlighted it recently in the docs.
Brad
Chris Boyle wrote:
> Hi, I can't get snd-bt-sco (bluetooth-alsa) to work and was told this
> was the best place to ask for help:
>
> The problem is, btsco starts up successfully, the device indicates a
> connection has been made, but no audio can be read or written, and after
> maybe a minute the device indicates the connection has been dropped.
> There is no noticeable difference on the host side at this point, i.e.
> audio apps directed at the headset still just hang, and btsco is still
> there. The mixer produces output from btsco, but has no effect on the
> device.
>
> Driver version: bluetooth-alsa CVS checked out 02/12/2004
> Kernel: 2.6.9 debian (presence / absence of hci_usb patch seems to make
> no difference)
> Host bluetooth adapter: Trust BT180 USB
> http://www.trust.com/home/default.htm?viewpage=service/sss/preview.htm%3Fartnr%3D13853
> Headset: Logitech Mobile Bluetooth Headset
> http://www.thinkgeek.com/computing/speakers/headsets/65ff/
> Also tested: Nokia 6310i, various channels (this functionality works
> under windows)
>
> I'd be grateful for any hints you can give me.
>
> Thanks,
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Marcel,
sorry for this long post here!
> The dongle keeps sending SCO packet, but the kernel already terminated
> the SCO connection.
I figured out that `hciconfig hci0 down' stops the flood. No `up' is
possible afterwards. I have to replug the dongle.
> What does "hcitool con" show when both (ACL + SCO) links were open?
(btsco's last line is RFCOMM channel 1 connected)
# hcitool con
Connections:
< ACL 00:08:1B:00:FF:33 handle 1 state 1 lm MASTER
(pressing the button at my headset starts the SCO stream)
# hcitool con
Connections:
< SCO 00:08:1B:00:FF:33 handle 1025 state 1 lm SLAVE
< ACL 00:08:1B:00:FF:33 handle 1 state 1 lm MASTER
I've tested the anycom dongle with both headsets once again.
Here is a (heavy striped) output of hcidump while testing one of those:
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 33 ff 00 1b 08 00 18 cc 02 00 00 00 01
... (normal connect)
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 01 04 33 ff 00 1b 08 00 00 01
> SCO data: handle 0x0000 dlen 0
... (a lot of those packets)
> SCO data: handle 0x0000 dlen 0
(I guess, here was my first button press)
> SCO data: handle 0x0401 dlen 48
0000: 58 00 60 ff f0 ff a0 ff 7c ff 98 ff d8 00 38 00
0010: 68 00 48 ff d0 ff 6c ff 5c ff a8 ff f0 00 50 00
0020: 70 00 38 ff c8 ff 7c ff 88 ff c0 00 20 00 70 00
... (a lot of those packets)
> SCO data: handle 0x0401 dlen 48
0000: f0 ff f0 ff f8 ff f8 ff f0 ff f0 ff f0 ff f8 ff
0010: f8 ff f8 ff f0 ff f0 ff f8 ff f8 ff f8 ff f0 ff
0020: f0 ff f8 ff f8 ff f8 ff f0 ff f0 ff f8 ff f8 ff
(the second button press)
> ACL data: handle 0x0001 flags 0x01 dlen 4
L2CAP(d): cid 0x0041 len 17 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 12 fcs 0x5c credits 1
0000: 41 54 2b 43 4b 50 44 3d 32 30 30 0d
**
< ACL data: handle 0x0001 flags 0x02 dlen 14
L2CAP(d): cid 0x01c3 len 10 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
0000: 0d 0a 4f 4b 0d 0a
**
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 01 00 01 00
< HCI Command: Disconnect (0x01|0x0006) plen 3
0000: 01 04 13
**
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 06 04
**
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 01 04 13
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 01 00 05
> SCO data: handle 0x0000 dlen 0
> SCO data: handle 0x0000 dlen 0
... flood ;)
** means between the HCI and ACL packets there was some SCO data
with a useful handle (> SCO data: handle 0x0401 dlen 48)
The SCO data between the two button presses seems ok, I think.
Nevertheless I can't hear any sound when trying to play.
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Sebastian,
> > what does "/proc/bus/usb/device" show for the Anycom dongle?
>
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=16 #Cfgs= 1
> P: Vendor=0f4d ProdID=1000 Rev= 4.01
> C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 26mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
> E: Ad=03(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
> I: If#= 1 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> E: Ad=84(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=05(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
at least it has the ISOC endpoints.
> With the anycom dongle I can see SCO data using hcidump but no sound
> is playing. When btsco is stopped it seems to me the connection isn't
> really closed.
> hcidump:
> ...
> > SCO data: handle 0x0000 dlen 0
> > SCO data: handle 0x0000 dlen 0
> ...
>
> syslog:
> ...
> kernel: cket: hci0 SCO packet for unknown connection handle 0
> kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> last message repeated 229 times
> ...
The dongle keeps sending SCO packet, but the kernel already terminated
the SCO connection. However I am not sure if connection handle 0 is a
valid handle. What does "hcitool con" show when both (ACL + SCO) links
were open?
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Marcel,
> what does "/proc/bus/usb/device" show for the Anycom dongle?
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=16 #Cfgs= 1
P: Vendor=0f4d ProdID=1000 Rev= 4.01
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 26mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E: Ad=84(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=05(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
With the anycom dongle I can see SCO data using hcidump but no sound
is playing. When btsco is stopped it seems to me the connection isn't
really closed.
hcidump:
...
> SCO data: handle 0x0000 dlen 0
> SCO data: handle 0x0000 dlen 0
...
syslog:
...
kernel: cket: hci0 SCO packet for unknown connection handle 0
kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
last message repeated 229 times
...
I have to stop hcid shutdown hic0 and unload all the modules to stop it
flooding my syslog!
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Sebastian,
> The first problem was the dongle. I've used an usb-dongle from Anycom
> (Transilica chip).
what does "/proc/bus/usb/device" show for the Anycom dongle?
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Chris,
I'm new to this bluetooth things so please don't mind if my suggestions
are not completely correct.
I've had some problems with my bluetooth headsets too.
The first problem was the dongle. I've used an usb-dongle from Anycom
(Transilica chip). Exchanging the dongle with a D-Link DBT-120
(Cambridge Silicon Radio chip) helped me because this chip routes the
SCO data over HCI.
Please post the ouput of `hciconfig hci0 revision'
The second issue was that all "sound-apps" were blocking (hanging)
without playing any sound. My headsets (both from Anycom) must be
activated with the switch to recieve the sound. Just like answer the
telephone.
Everone, please feel free to correct me if I'm wrong!
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Chris,
> I can't get snd-bt-sco (bluetooth-alsa) to work and was told this
> was the best place to ask for help:
>
> The problem is, btsco starts up successfully, the device indicates a
> connection has been made, but no audio can be read or written, and after
> maybe a minute the device indicates the connection has been dropped.
> There is no noticeable difference on the host side at this point, i.e.
> audio apps directed at the headset still just hang, and btsco is still
> there. The mixer produces output from btsco, but has no effect on the
> device.
>
> Driver version: bluetooth-alsa CVS checked out 02/12/2004
> Kernel: 2.6.9 debian (presence / absence of hci_usb patch seems to make
> no difference)
why don't you try 2.6.9-mh5 or 2.6.10-rc3 ?
> Host bluetooth adapter: Trust BT180 USB
> http://www.trust.com/home/default.htm?viewpage=service/sss/preview.htm%3Fartnr%3D13853
> Headset: Logitech Mobile Bluetooth Headset
> http://www.thinkgeek.com/computing/speakers/headsets/65ff/
> Also tested: Nokia 6310i, various channels (this functionality works
> under windows)
what is the output of "hciconfig -a" and "hcitool info ..." for these
devices. And include "/proc/bus/usb/devices".
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel