Skip to contentSkip to conversation

btsco: Operation not supported

Bluez-devel Sergey Smirnov 3 participants 15 messages Apr 10, 2007 – Apr 11, 2007 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Zaurus 750(ARM), Socket CF BT, kernel 2.6.20.2, btsco 0.5 (show btsco v0.42) Modules sco and snd-bt-sco loaded, alsamixer -c1 show BT Headset.
./btsco -v 00:0F:DE:3E:AE:12
btsco v0.42
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
Using interface hci0
recieved AT*ECBP=?
recieved AT+CLIP=1
recieved AT+CSCS="UTF-8"
recieved AT+CLAN? <-(here start mplayer -ao alsa:device=hw=1.0 music.mp3)
speaker volume: 3 mic volume: 1
i/o needed: connecting sco...
Can't connect SCO audio channel
: Operation not supported

I did the same on my notebook. It's work correct.
Can anybody help me?
Thanks in advance.
--
Sergey

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#1 lore raw

Make sure you have sco support in your kernel, as a module or compiled in. Don't forget to load the module..

FYI: I have my share of trouble with SCO audio links so I have no clue what else you can do :)

Berend

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#2 lore raw

Thank you for answer.
I'm sure that modules loaded:

svs-zaurus:~# lsmod|grep sco
sco                    11396  0
snd_bt_sco             13868  2
snd_hwdep               7620  2 snd_bt_sco
snd_pcm                84613  8 snd_bt_sco,snd_soc_pxa2xx,snd_soc_core,snd_pxa2xx_ac97,snd_ac97_codec,snd_pxa2xx_pcm,snd_pcm_oss
snd_page_alloc          6600  2 snd_bt_sco,snd_pcm
snd                    53876  18 snd_bt_sco,snd_hwdep,snd_soc_corgi,snd_soc_wm8731,snd_soc_core,snd_pxa2xx_ac97,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
bluetooth              52736  10 sco,rfcomm,l2cap,dtl1_cs
svs-zaurus:~#

Also I'm sure that devices was paired.
I check /var/lib/bluetooth/<BT_ADDR>
And also I can cat > /dev/rfcomm[0|1] which is tty of headset

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 10

    L2CAP(d): cid 0x0040 len 6 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2
Quoted 8 lines · Berend Dekens

Make sure you have sco support in your kernel, as a module or compiled in. Don't forget to load the module..

FYI: I have my share of trouble with SCO audio links so I have no clue what else you can do :)

Berend

Quoted 10 lines

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#14 lore raw
In reply to Berend Dekens

One moment. To compile snd-bt-sco modules I need to choose snd-hwdep
But it doesn't appear on ARM arch. I changed sound/arm/Kconfig adding "select SND_HWDEP"

Quoted 8 lines · Berend Dekens

Make sure you have sco support in your kernel, as a module or compiled in. Don't forget to load the module..

FYI: I have my share of trouble with SCO audio links so I have no clue what else you can do :)

Berend

Quoted 10 lines

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#3 lore raw
In reply to Sergey Smirnov
Quoted 6 lines

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Can you provide the part showing the Add SCO connection command? You might have to try different packet types.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#4 lore raw

Sorry for stupid question.
Part of what you want to see?
Problem in function sco_connect of btsco.c:
static int sco_connect(bdaddr_t * src, bdaddr_t * dst, uint16_t * handle,

                       uint16_t * mtu)
{
        struct sockaddr_sco addr;
        struct sco_conninfo conn;
        struct sco_options opts;
        int s;
        unsigned int size;

        if ((s = socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)) < 0) {
                return -1;
        }

        memset(&addr, 0, sizeof(addr));
        addr.sco_family = AF_BLUETOOTH;
        bacpy(&addr.sco_bdaddr, src);
        if (bind(s, (struct sockaddr *)&addr, sizeof(addr)) < 0) {
                close(s);
                return -1;
        }

        memset(&addr, 0, sizeof(addr));
        addr.sco_family = AF_BLUETOOTH;
        bacpy(&addr.sco_bdaddr, dst);
        if (connect(s, (struct sockaddr *)&addr, sizeof(addr)) < 0) {
                close(s);
                return -1;
        }

...
Here hciconfig -a
hci0: Type: PCCARD
BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 0:0
UP RUNNING PSCAN ISCAN
RX bytes:204 acl:0 sco:0 events:15 errors:0
TX bytes:382 acl:0 sco:0 commands:15 errors:0
Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'svs-zaurus-0'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1) LMP Subver: 0x21a
Manufacturer: Nokia Mobile Phones (1)
It's strange for me that SCO MTU is 0:0
I've tried to change it but its didn't help.

Tell me please what information do you need.
Thanks.

Quoted 15 lines · Mayank BATRA
Quoted 6 lines

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Can you provide the part showing the Add SCO connection command? You might have to try different packet types.

Best Regards,

Mayank

Quoted 10 lines

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#5 lore raw
Quoted 2 lines

Sorry for stupid question.
Part of what you want to see?

Actually, I wanted to see Add SCO connection command on hcidump. Not the source code! Just wanted to see what packet types are going in the command.

[...]

Quoted 9 lines
Quoted 9 lines
Quoted 6 lines

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Can you provide the part showing the Add SCO connection command? You might have to try different packet types.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#6 lore raw
svs-zaurus:~# hcidump -V
HCI sniffer - Bluetooth packet analyzer ver 1.32
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:0F:DE:3E:AE:12 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5
Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Create Connection (0x01|0x0005) status 0x00 ncmd 4
Quoted 1 line

HCI Event: Link Key Request (0x17) plen 6

    bdaddr 00:0F:DE:3E:AE:12
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
    bdaddr 00:0F:DE:3E:AE:12 key 5200129BC988A7B6F83756A822D3B174
Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

    Link Key Request Reply (0x01|0x000b) ncmd 4
    status 0x00 bdaddr 00:0F:DE:3E:AE:12
Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

    status 0x00 handle 1 bdaddr 00:0F:DE:3E:AE:12 type ACL encrypt 0x00
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040

< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 1

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0051 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0051 flags 0x00 clen 0
Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 454
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0051 flags 0x00 result 0 clen 4
      Success
      MTU 454
Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 4

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 1 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

    Write Link Policy Settings (0x02|0x000d) ncmd 4
    status 0x00 handle 1
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:0F:DE:3E:AE:12 mode 2 clkoffset 0x0000
Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Remote Name Request (0x01|0x0019) status 0x0c ncmd 4
Error: Command Disallowed

Quoted 1 line

HCI Event: Read Remote Supported Features (0x0b) plen 11

    status 0x00 handle 1
    Features: 0xbc 0x28 0x01 0x00 0x00 0x00 0x00 0x00
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 1

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 454
< ACL data: handle 1 flags 0x02 dlen 24
    L2CAP(d): cid 0x0051 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x1108 (Headset)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 7 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 17 ACL data: handle 1 flags 0x01 dlen 17 ACL data: handle 1 flags 0x01 dlen 17 ACL data: handle 1 flags 0x01 dlen 17 ACL data: handle 1 flags 0x01 dlen 17 ACL data: handle 1 flags 0x01 dlen 4

    L2CAP(d): cid 0x0040 len 102 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x61
          count 94
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10002
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1108 (Headset) uuid-16 0x1203 (Audio) >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x1 > >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1108 (Headset) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "SonyEricsson Headset Service"
              aid 0x0302 (unknown)
                 bool 0x1
          cont 00
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0051 scid 0x0040

< HCI Command: Read Voice Setting (0x03|0x0025) plen 0

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 12

    L2CAP(s): Disconn rsp: dcid 0x0051 scid 0x0040
Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

    Read Voice Setting (0x03|0x0025) ncmd 4
    status 0x00 voice setting 0x0060
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0052 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0052 flags 0x00 clen 4
      MTU 1013
Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 454
< ACL data: handle 1 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0052 flags 0x00 result 0 clen 4
      Success
      MTU 454
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17
HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x01 dlen 1

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 454
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0052 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7

< ACL data: handle 1 flags 0x02 dlen 18
L2CAP(d): cid 0x0052 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 449 max_retrans 0 credits 7

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 2

L2CAP(d): cid 0x0040 len 15 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 449 max_retrans 0 credits 0
< ACL data: handle 1 flags 0x02 dlen 8

    L2CAP(d): cid 0x0052 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0052 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 13

    L2CAP(d): cid 0x0040 len 9 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 7
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(d): cid 0x0052 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 13

    L2CAP(d): cid 0x0040 len 9 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 7
< ACL data: handle 1 flags 0x02 dlen 9
    L2CAP(d): cid 0x0052 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 2

    L2CAP(d): cid 0x0040 len 15 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 10

    L2CAP(d): cid 0x0040 len 6 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0052 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 2

    L2CAP(d): cid 0x0040 len 15 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 10 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0052 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 10

    L2CAP(d): cid 0x0040 len 6 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2
Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 8

    L2CAP(d): cid 0x0040 len 21 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 16 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0052 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 2 lines

ACL data: handle 1 flags 0x02 dlen 17 ACL data: handle 1 flags 0x01 dlen 1

    L2CAP(d): cid 0x0040 len 14 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
< ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(d): cid 0x0052 len 10 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 10

    L2CAP(d): cid 0x0040 len 6 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2

< HCI Command: Sniff Mode (0x02|0x0003) plen 10
handle 1 max 800 min 80 attempt 4 timeout 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Sniff Mode (0x02|0x0003) status 0x23 ncmd 4
Error: LMP Error Transaction Collision
< ACL data: handle 1 flags 0x02 dlen 20

    L2CAP(d): cid 0x0052 len 16 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 12 fcs 0x9a
< ACL data: handle 1 flags 0x02 dlen 20
    L2CAP(d): cid 0x0052 len 16 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 12 fcs 0x9a

< HCI Command: Add SCO Connection (0x01|0x0007) plen 4
handle 1 ptype 0x0020
Packet type: HV1

Quoted 1 line

HCI Event: Mode Change (0x14) plen 6

    status 0x00 handle 1 mode 0x02 interval 2048
    Mode: Sniff
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

ACL data: handle 1 flags 0x02 dlen 10

    L2CAP(d): cid 0x0040 len 6 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2
Quoted 12 lines · Mayank BATRA
Quoted 2 lines

Sorry for stupid question.
Part of what you want to see?

Actually, I wanted to see Add SCO connection command on hcidump. Not the source code! Just wanted to see what packet types are going in the command.

[...]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Quoted 10 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Can you provide the part showing the Add SCO connection command? You might have to try different packet types.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#7 lore raw
In reply to Mayank BATRA

On PDA:
hciconfig hci0 features
hci0: Type: PCCARD
BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 64:8
Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <sniff mode>
On notebook:
hciconfig hci0 features
hci0: Type: USB
BD Address: 00:09:DD:10:02:C2 ACL MTU: 192:8 SCO MTU: 64:8
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>

There is no <SCO link> on PDA! Is it possible to change features?

Quoted 12 lines · Mayank BATRA
Quoted 2 lines

Sorry for stupid question.
Part of what you want to see?

Actually, I wanted to see Add SCO connection command on hcidump. Not the source code! Just wanted to see what packet types are going in the command.

[...]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Here is some part of hcidump while sco connect:

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 1 packets 1

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

Quoted 10 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value

Can you provide the part showing the Add SCO connection command? You might have to try different packet types.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#12 lore raw
In reply to Sergey Smirnov
Quoted 13 lines

Here hciconfig -a
hci0: Type: PCCARD

        BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 0:0
        UP RUNNING PSCAN ISCAN
        RX bytes:204 acl:0 sco:0 events:15 errors:0
        TX bytes:382 acl:0 sco:0 commands:15 errors:0
        Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'svs-zaurus-0'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing, 
Quoted 5 lines

Object Transfer, Audio
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1)
LMP Subver: 0x21a
Manufacturer: Nokia Mobile Phones (1)

It took me a while to understand this confusing situation.

The reason for this behaviour is very simple.
Have a look at the Features of your device: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
Here, byte 0 is 0xbf, byte 1 is 0x00. If you decode these numbers from the bluetooth specs, bit 3 of byte 1 stands for SCO link. In your case it is 0 which means your device does not support SCO links at all. Get yourself a new dongle :(
Now you would ask me why does the packet type shows HV1? This is because HV1 is mandatory if the device supports SCO link. So this is just a mistake done by hciconfig. It should report HV1 packet type only if SCO link bit is 1. In case it is 0 do not mention HV1.

Hope this helps.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#8 lore raw
In reply to Sergey Smirnov
Quoted 23 lines

On PDA:
hciconfig hci0 features
hci0: Type: PCCARD

        BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 64:8
        Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
                <3-slot packets> <5-slot packets> 

<encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode>
On notebook:
hciconfig hci0 features
hci0: Type: USB

        BD Address: 00:09:DD:10:02:C2 ACL MTU: 192:8 SCO MTU: 64:8
        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>

Quoted 1 line

There is no <SCO link> on PDA! Is it possible to change features?

Correct. Your PDA does not support SCO links. See my previous mail. It is simply not possible to change the features of a bluetooth device.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#13 lore raw
In reply to Mayank BATRA

I have the same problem with bluez-utils 3.7
Then I compile version 3.9.
I think that problem in hcid.
I can stop it only by kill -9

I have Socket CF BT card on PDA. I'll try to find information is it support SCO. Thanks

Quoted 33 lines · Mayank BATRA
Quoted 13 lines

Here hciconfig -a
hci0: Type: PCCARD

        BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 0:0
        UP RUNNING PSCAN ISCAN
        RX bytes:204 acl:0 sco:0 events:15 errors:0
        TX bytes:382 acl:0 sco:0 commands:15 errors:0
        Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'svs-zaurus-0'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing, 
Quoted 5 lines

Object Transfer, Audio
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1)
LMP Subver: 0x21a
Manufacturer: Nokia Mobile Phones (1)

It took me a while to understand this confusing situation.

The reason for this behaviour is very simple.
Have a look at the Features of your device: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
Here, byte 0 is 0xbf, byte 1 is 0x00. If you decode these numbers from the bluetooth specs, bit 3 of byte 1 stands for SCO link. In your case it is 0 which means your device does not support SCO links at all. Get yourself a new dongle :(
Now you would ask me why does the packet type shows HV1? This is because HV1 is mandatory if the device supports SCO link. So this is just a mistake done by hciconfig. It should report HV1 packet type only if SCO link bit is 1. In case it is 0 do not mention HV1.

Quoted 7 lines

Hope this helps.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#9 lore raw
In reply to Mayank BATRA

I have Socket CF Rev. F BT card. Bad luck. It doesn't support SCO :(

Quoted 23 lines · Mayank BATRA
Quoted 23 lines

On PDA:
hciconfig hci0 features
hci0: Type: PCCARD

        BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 64:8
        Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
                <3-slot packets> <5-slot packets> 

<encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode>
On notebook:
hciconfig hci0 features
hci0: Type: USB

        BD Address: 00:09:DD:10:02:C2 ACL MTU: 192:8 SCO MTU: 64:8
        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>

Quoted 10 lines
Quoted 1 line

There is no <SCO link> on PDA! Is it possible to change features?

Correct. Your PDA does not support SCO links. See my previous mail. It is simply not possible to change the features of a bluetooth device.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#10 lore raw
In reply to Mayank BATRA

Ok. I have one stupid question.
My BT CF card doesn't support SCO.
Does this means that it dosn't support a2dp?
I tried start on PDA a2play and on notebook a2recv. It's work.
I have plan to buy BT stereo headset to listen music from PDA...

Quoted 23 lines · Mayank BATRA
Quoted 23 lines

On PDA:
hciconfig hci0 features
hci0: Type: PCCARD

        BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 64:8
        Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
                <3-slot packets> <5-slot packets> 

<encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode>
On notebook:
hciconfig hci0 features
hci0: Type: USB

        BD Address: 00:09:DD:10:02:C2 ACL MTU: 192:8 SCO MTU: 64:8
        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>

Quoted 10 lines
Quoted 1 line

There is no <SCO link> on PDA! Is it possible to change features?

Correct. Your PDA does not support SCO links. See my previous mail. It is simply not possible to change the features of a bluetooth device.

Best Regards,

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#11 lore raw
Quoted 3 lines

Ok. I have one stupid question.
My BT CF card doesn't support SCO.
Does this means that it dosn't support a2dp?

No, since a2dp uses ACL link for transmitting stereo data. A2dp has nothing to do with SCO.

Quoted 3 lines

I tried start on PDA a2play and on notebook a2recv. It's work.
I have plan to buy BT stereo headset to listen music from PDA...

Go ahead.

Mayank

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel