From: Nils Faerber <nils@kernelconcepts.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] New to the headset club :)
Date: Tue, 07 Oct 2003 16:34:33 +0200 [thread overview]
Message-ID: <1065537273.29878.613.camel@idoru.kc.de> (raw)
Hi!
I made a mistake and bought a Bluetooth headset ;)
New toy... and now I am desperately trying to get a sound from it.
After some struggeling hstest connects but the headset does not play a
single beep.
When hstest connects I get the following:
Voice setting: 0x0040
RFCOMM channel connected
SCO audio channel connected (handle 43, mtu 64)
AT+VGS=4
and the headset beeps a single time.
After that nothing obvious happens anymore.
What does the AT command mean? It seems to come from the headset, right?
Would hstest need to respond at least with OK?
Oh, brave new world ;)
Any hints are welcome!
Oh, BTW: This headset is a C-Tech BT101, seems a quite common low-price
one...
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2003-10-07 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 14:34 Nils Faerber [this message]
2003-10-07 14:55 ` [Bluez-users] New to the headset club :) Marcel Holtmann
2003-10-07 15:04 ` Marcel Holtmann
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=1065537273.29878.613.camel@idoru.kc.de \
--to=nils@kernelconcepts.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