From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Connection issue with headset
Date: Thu, 03 Feb 2005 15:13:23 +0100 [thread overview]
Message-ID: <cttbgv$knk$1@sea.gmane.org> (raw)
In-Reply-To: <420105F0.5030407@tootai.net>
Hi Daniel,
>> are the other things build into the kernel or loaded? (bluetooth,
>> hci_usb, l2cap, rfcomm, sco)
>
> all in modules
Have you really loaded all of them?
Your posted output of dmesg:
Bluetooth: L2CAP ver 2.6
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
# where is SCO?
snd-bt-sco revision 1.4 $
snd-bt-sco: snd-bt-scod thread starting
My output:
Bluetooth: L2CAP ver 2.7
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.5
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: SCO (Voice Link) ver 0.4
Bluetooth: SCO socket layer initialized
snd-bt-sco revision 1.4 $
snd-bt-sco: snd-bt-scod thread starting
Btw. what kernel version do you use? Please update the kernel to
2.6.10-mh3 and the libs/utils to 2.15!!
# sdptool search --bdaddr <bdaddr> 0x1108
Class 0x1108
Searching for 0x1108 on <bdaddr> ...
Service Name: Headset
Service RecHandle: 0x10000
Service Class ID List:
"Headset" (0x1108)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
What does this command show to you? Is the Channel the same when
connecting with btsco?
>> If you followed this and it does not work I have two ideas.
>> 1. Is it possible that your headset does not send any AT commands
>> over the connected RFCOMM channel? As far as I know btsco will never
>> try to establish an SCO connection without having recived the cmd
>> from your headset.
>
> From what I check nowhere I saw any AT command. That exactly what I'm
> looking for!
Try hcidump -X (upper case). This is the part of my output:
...
> ACL data: handle 0x0029 flags 0x01 dlen 3
L2CAP(d): cid 0x0041 len 16 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 12 fcs 0x40
0000: 41 54 2b 43 4b 50 44 3d 32 30 30 0d AT+CKPD=200.
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x0087 len 10 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
0000: 0d 0a 4f 4b 0d 0a ..OK..
...
Regards,
hecatomb
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-03 14:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 9:32 [Bluez-users] Connection issue with headset administrator tootai
2005-01-28 15:53 ` [Bluez-users] " Sebastian Roth
2005-01-29 16:39 ` daniel huhardeaux
2005-01-29 16:43 ` administrator tootai
2005-01-29 17:29 ` Stefan Bellon
2005-01-30 3:13 ` Brad Midgley
2005-01-30 19:01 ` administrator tootai
2005-01-31 14:57 ` administrator tootai
2005-01-31 14:58 ` Marcel Holtmann
2005-01-31 15:30 ` administrator tootai
2005-01-31 15:55 ` Marcel Holtmann
2005-01-31 18:20 ` administrator tootai
2005-02-01 16:37 ` Sebastian Roth
2005-02-02 13:20 ` administrator tootai
2005-02-02 16:21 ` Sebastian Roth
2005-02-02 16:55 ` administrator tootai
2005-02-03 14:13 ` Sebastian Roth [this message]
2005-02-03 21:39 ` administrator tootai
2005-02-04 7:38 ` Sebastian Roth
2005-02-04 12:25 ` administrator tootai
2005-02-03 17:06 ` administrator tootai
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='cttbgv$knk$1@sea.gmane.org' \
--to=sebastian.roth@esk.fhg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox