From: Sebastian Roth <sebiroth@web.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: mystic AT-Command
Date: Sat, 19 Feb 2005 19:18:49 +0100 [thread overview]
Message-ID: <cv7vnn$b2i$1@sea.gmane.org> (raw)
In-Reply-To: <42161CC7.1090800@dark-reality.de>
Hi Lars,
google shows me that this AT command enables/disables voice recognition.
So I think this behavior of the headset isn't wrong in principle. What
do you think?
> the check in btsco.c for AT+BVRA=1 was only added because I had no
> understanding why my headset sometimes used this, and sometimes the
> expected AT+CKPD=200 - it was because btsco sometimes used the wrong
> channel. Now this should not happen any more as we have (hopefully)
> proper channel auto-detection.
Thanks, this explains the check!
> You can try to remove AT+BVRA=1 from btsco.c:
Have done this already and it works! When initially asking this my idea
was to have this change merged into the cvs.
Thanks for your great help.
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-19 18:18 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 ` [Bluez-devel] " Sebastian Roth
2005-02-18 16:50 ` Lars Grunewaldt
2005-02-19 18:18 ` Sebastian Roth [this message]
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='cv7vnn$b2i$1@sea.gmane.org' \
--to=sebiroth@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox