From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Connection issue with headset
Date: Wed, 02 Feb 2005 17:21:36 +0100 [thread overview]
Message-ID: <ctqulk$ce4$1@sea.gmane.org> (raw)
In-Reply-To: <4200D3B6.1050708@tootai.net>
Hi Daniel,
> Did not help. I made following:
>
> - modprobe snd-bt-sco
are the other things build into the kernel or loaded? (bluetooth,
hci_usb, l2cap, rfcomm, sco)
> - headset is switch off
? what. Maybe you missed me on some point? A switched off headset cannot
play any sound! ;-)
> - btsco 00:0b:2e:06:01:2e
> Device is 1:0
> Failed to connect to SDP server: Host is down
> Assuming channel 2
> - I swith on headset, information above is completed by
> Voice setting: 0x0060
> RFCOMM channel 2 connected
Maybe it's working when switching it on half the way but IMO that's no
good idea.
- load all necessary modules
- start hcid
- check if all is up (hciconfig)
- switch on your headset (normal mode)
- make sure you have the correct address!!
- btsco <hwaddr>
- wait for "RFCOMM channel X connected"
- press the headset button
- you should see some more messages now (have a look at my output below)
btsco <hwaddr>
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected # press headset button
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=01
Sending up speaker change 1 # now you should hear a static noise
recieved AT+CKPD=200 # press button to stop it
disconnected SCO channel
recieved AT+VGS=01 # canceled btsco with ^C
Sending up speaker change 1
When I've pressed the button to start the sound I can see a lot of SCO
data in the output of hcidump. You too?
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.
2. The headset is sending "other" commands when pressing the headset
button. Same effect as 1.
Please have a look at hcidump -x to see if your headset is sending such
a command when pressing the button!
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-02 16:21 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 [this message]
2005-02-02 16:55 ` administrator tootai
2005-02-03 14:13 ` Sebastian Roth
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='ctqulk$ce4$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 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.