Hi andrea
Same problem used to occur with me.
My hciconfig also used to show this sco mtu
SCO MTU: 64:0
whereas others on the list it was something SCO MTU: 64:8.
So i changed my dongle. and it simply worked.
I bought one new BT dongle which clamed it supports HS audio Gtaeway.
It is a product of ENTER multimedia.
this is it.
[root@localhost Pramod]# /usr/local/sbin/hciconfig -a
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
UP RUNNING PSCAN ISCAN
RX bytes:10283222 acl:386 sco:201151 events:719 errors:0
TX bytes:10319322 acl:347 sco:202172 commands:192 errors:0
Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 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: 0x1fe LMP Ver: 1.2 (0x2) LMP Subver: 0x1fe
Manufacturer: Integrated System Solution Corp. (57)
I tried all option from list about sco but they never worked.
You too can try them. But before that try replacing your BT dongle.
It will save your time.
Thanks and Best regards
Pramod
----- Original Message ----
From: Andrea Bondavalli <[email protected]>
To: [email protected]
Sent: Wednesday, 27 February, 2008 8:44:09 PM
Subject: [Bluez-users] BT headset doesn't work: SCO connection timeout
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
span.StileMessaggioDiPostaElettronica17
{font-family:Arial;color:windowtext;}
_filtered {margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
{}
-->
Dear all,
I’ve got a linux kernel 2.4.20 with bluez
libs/utils 3.23 on a ARM linux platform.
I can successfully ping and pair my headset, but I am
not able to connect a SCO channel.
As soon as I try to connect a SCO channel (using the
scotest utility, and also other applications) the call always fails with a timeout
error.
Here are some useful traces:
# hciconfig
hci0: Type: UART
BD Address: 00:80:E1:00:AB:BA ACLMTU: 1021:4 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:10150 acl:204 sco:0events:326 errors:0
TX bytes:4097 acl:168 sco:0commands:81 errors:0
# hciconfig hci0
revision
STLC2500 R4.212102005 12:40:14 ZAV100012 A7
HW Id= V440BAA
# hciconfig hci0
version
hci0: Type: UART
BD Address: 00:80:E1:00:AB:BA ACLMTU: 1021:4 SCO MTU: 64:0
HCI Ver: 2.0 (0x3) HCI Rev: 0x402LMP Ver: 2.0 (0x3) LMP Subver: 0x520
Manufacturer: ST Microelectronics(48)
--------------------------------------------------------------------
Ping
output is OK:
# passkey-agent0000 00:12:1C:BB:01:98 &
# l2ping 00:12:1C:BB:01:98
Passkey request for device 00:12:1C:BB:01:98
Passkey service has been released
Ping : 00:12:1C:BB:01:98 from 00:80:E1:00:AB:BA(data size 44) ...
0 bytes from 00:12:1C:BB:01:98 id 0 time 101.29ms
0 bytes from 00:12:1C:BB:01:98 id 1 time 48.42ms
0 bytes from 00:12:1C:BB:01:98 id 2 time 52.15ms
0 bytes from 00:12:1C:BB:01:98 id 3 time 36.95ms
0 bytes from 00:12:1C:BB:01:98 id 4 time 60.60ms
0 bytes from 00:12:1C:BB:01:98 id 5 time 43.05ms
0 bytes from 00:12:1C:BB:01:98 id 6 time 48.42ms
0 bytes from 00:12:1C:BB:01:98 id 7 time 96.63ms
0 bytes from 00:12:1C:BB:01:98 id 8 time 60.66ms
0 bytes from 00:12:1C:BB:01:98 id 9 time 62.69ms
0 bytes from 00:12:1C:BB:01:98 id 10 time 41.35ms
11 sent, 11 received, 0% loss
--------------------------------------------------------------------
scotest (from bluez-utils-3.23) output
# hcidump -X
HCI sniffer - Bluetooth packet analyzer ver 1.40
device: hci0 snap_len: 1028 filter: 0xffffffff
# passkey-agent
0000 00:12:1C:BB:01:98 &
# scotest -s
00:12:1C:BB:01:98 &
< HCI Command: Create Connection (0x01|0x0005)plen 13
0000: 98 01 bb 1c 12 00 18 cc 02 00 00 0001 .............
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 0504 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 98 01 bb 1c 12 0001 ........
> HCI Event: Link Key Request (0x17) plen 6
0000: 98 01 bb 1c 1200 ......
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
0000: 98 01 bb 1c 1200 ......
> HCI Event: Command Complete (0x0e) plen 10
0000: 01 0c 04 00 98 01 bb 1c 1200 ..........
> HCI Event: PIN Code Request (0x16) plen 6
0000: 98 01 bb 1c 1200 ......
Passkey request for device 00:12:1C:BB:01:98
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
0000: 98 01 bb 1c 12 00 04 30 30 30 30 00 00 00 00 00 .......0000.....
0010: 00 00 00 00 00 0000 .......
Passkey service has been released
> HCI Event: Command Complete (0x0e) plen 10
0000: 01 0d 04 00 98 01 bb 1c 1200 ..........
> HCI Event: Link Key Notification (0x18) plen 23
0000: 98 01 bb 1c 12 00 11 a5 89 24 9a 6a 5b d8 44 07 .........$.j[.D.
0010: 3a e8 13 4e 0f 0600 :..N...
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 01 00 98 01 bb 1c 12 00 0100 ...........
> HCI Event: Command Status (0x0f) plen 4
0000: 00 02 0000 ....
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 01 00 0f 00 ....
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 01 0005 ...
> HCI Event: Command Complete (0x0e) plen 6
0000: 02 0d 08 00 0100 .......
< HCI Command: Add SCO Connection(0x01|0x0007) plen 4
0000: 01 00 a000 ....
> HCI Event: Command Complete (0x0e) plen 4
0000: 02 07 0401 ....
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 98 01 bb 1c 12 00 02 00 00 00 ..........
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1904 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 98 01 bb 1c 12 00 50 61 72 72 6f 74 20 4d 4b .......ParrotMK
0010: 36 30 30 30 76 31 2e 30 31 63 00 00 00 00 00 00 6000v1.01c.......
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 ................
> HCI Event: Command Status (0x0f) plen 4
0000: 00 02 0000 ....
< HCI Command: Read Remote Version Information (0x01|0x001d) plen 2
0000: 0100 ..
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1d04 ....
> HCI Event: Read Remote Ver Info Complete (0x0c) plen 8
0000: 00 01 00 02 43 00 1c01 ....C...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 02 0000 ....
scotest[104]: Can't connect: Connection timed
out (110)
It seems that the only reply to the Add SCO
Connection command is an unexpected Command Complete event and than the
connect() system call fails with a timeout (40sec) error.
As far as I know the only possible replies to the Add
SCO Connection command should be the Command Status event and the Command Complete
event.
Have you ever experienced this problem ? Any hints ?
Thank you a lot in advance,
Andrea Bondavalli
-----Inline Attachment Follows-----
-------------------------------------------------------------------------
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/
-----Inline Attachment Follows-----
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Now you can chat without downloading messenger. Go to http://in.messenger.yahoo.com/webmessengerpromo.php
On jeu, 2008-02-28 at 08:54 +0530, pramod gurav wrote:
> Hi andrea Same problem used to occur with me. My hciconfig also used
> to
> show this sco mtu SCO MTU: 64:0 whereas others on the list it was
> something SCO MTU: 64:8. So i changed my dongle. and it simply
> worked. I bought one new BT dongle which clamed it supports HS audio
> Gtaeway. It is a product of ENTER multimedia. this is it.
> [root@localhost Pramod]# /usr/local/sbin/hciconfig -a hci0: Type:
> USB BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU:
> 48:10 UP RUNNING PSCAN ISCAN RX bytes:10283222
> acl:386 sco:201151 events:719 errors:0 TX bytes:10319322
> acl:347 sco:202172 commands:192 errors:0 Features: 0xbf 0xfe
> 0x8d 0x78 0x08 0x18 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: 0x1fe LMP Ver: 1.2 (0x2) LMP Subver:
> 0x1fe Manufacturer: Integrated System Solution Corp. (57)
It's fine you solved your problem, but...
I currently have a similar dongle "Souyo (r) Bluetooth (tm)", that doesn't
work with either usb2 or integrated usb 1.1 (i use no hub).
# hciconfig -a
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1224 acl:0 sco:0 events:28 errors:0
TX bytes:608 acl:0 sco:0 commands:28 errors:0
Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'littletux-1'
Can't read class of device on hci0: Connection timed out (110)
# lsusb
Bus 003 Device 004: ID 1131:1001 Integrated System Solution Corp.
KY-BT100 Bluetooth Adapter
Tried without force_scofix, in case of (maybe needed only for the other
dongle).
There is an other quirk needed (reset), so I haven't tried btusb module.
I produces various kind of error messages in syslog :
Feb 28 12:22:42 littletux kernel: hub 5-0:1.0: port 2 disabled by hub
(EMI?), re-enabling...
Feb 28 12:22:42 littletux kernel: usb 5-2: USB disconnect, address 2
Feb 28 12:22:42 littletux hcid[9880]: Can't init device hci0: No such
device (19)
Feb 28 12:22:42 littletux hcid[9672]: HCI dev 0 unregistered
Feb 28 12:22:42 littletux hcid[9672]: Unregister path: /org/bluez/hci0
Feb 28 12:22:42 littletux hcid[9672]: Device hci0 has been removed
Feb 28 12:22:42 littletux bluetooth: Starting bluetooth service
Feb 28 12:22:42 littletux kernel: usb 5-2: new full speed USB device
using uhci_hcd and address 3
Feb 28 12:22:42 littletux bluetooth: Starting hidd
Feb 28 12:22:42 littletux kernel: usb 5-2: device not accepting address
3, error -71
Feb 28 12:22:42 littletux kernel: usb 5-2: new full speed USB device
using uhci_hcd and address 4
Feb 28 12:22:43 littletux kernel: usb 5-2: device not accepting address
4, error -71
Feb 28 12:22:43 littletux kernel: usb 5-2: new full speed USB device
using uhci_hcd and address 5
Feb 28 12:22:43 littletux kernel: usb 5-2: device descriptor read/64,
error -71
Feb 28 12:22:43 littletux kernel: usb 5-2: device descriptor read/64,
error -71
Feb 28 12:22:43 littletux kernel: usb 5-2: new full speed USB device
using uhci_hcd and address 6
Feb 28 12:22:43 littletux kernel: usb 5-2: device descriptor read/64,
error -71
Feb 28 12:22:44 littletux kernel: usb 5-2: device descriptor read/64,
error -71
It used to work (before i had the usb2 card, or wi-fi maybe) but is no
more use to me now.
I wouldn't recommend these old dongles. Mailing-list readers should get
a bluetooth 2.0 or more dongle, it's the same price as a 1.2 one.
Best regards,
Guillaume B.
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users