From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: mystic AT-Command
Date: Fri, 18 Feb 2005 16:11:56 +0100 [thread overview]
Message-ID: <cv50e9$tm3$1@sea.gmane.org> (raw)
In-Reply-To: <4215FC4A.20504@dark-reality.de>
Hi Lars,
thanks for your answer!
> Looks like the wrong channel is selected.
Can't imagine why this can be a problem with the RFCOMM channel. But
let's give it a try!
# sdptool search --bdaddr 00:0B:2E:02:03:A2 0x1108
Class 0x1108
Searching for 0x1108 on 00:0B:2E:02:03:A2 ...
Service Name: Headset
Service RecHandle: 0x20000
Service Class ID List:
"Headset" (0x1108)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 6
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
If I do not specify a channel to btsco it uses 6.
I tried to add channels to the commandline. It connects with channel 1
or 2. But if I tried to establish the SCO channel pressing the button
the headset continuosly peeps, no SCO connection!
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-18 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 13:30 [Bluez-devel] mystic AT-Command Sebastian Roth
2005-02-18 14:31 ` Lars Grunewaldt
2005-02-18 15:11 ` Sebastian Roth [this message]
2005-02-18 16:50 ` [Bluez-devel] " Lars Grunewaldt
2005-02-19 18:18 ` Sebastian Roth
2005-02-20 0:56 ` Brad Midgley
2005-02-20 2:17 ` Lars Grunewaldt
2005-02-21 8:20 ` Sebastian Roth
2005-02-21 17:09 ` Brad Midgley
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='cv50e9$tm3$1@sea.gmane.org' \
--to=sebastian.roth@esk.fhg.de \
--cc=bluez-devel@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.