Linux bluetooth development
 help / color / mirror / Atom feed
From: Fredrik Tolf <fredrik@dolda2000.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Patch] Some btsco modifications
Date: Mon, 14 Mar 2005 16:00:52 +0100	[thread overview]
Message-ID: <1110812452.5056.108.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <1110808286.5056.87.camel@pc7.dolda2000.com>

On Mon, 2005-03-14 at 14:51 +0100, Fredrik Tolf wrote:
> On Mon, 2005-03-14 at 12:52 +0100, Lars Grunewaldt wrote:
> > Is it possible to have the headset buttons work as they did without the
> > patch, like, switching between both behaviours? there are scenarios for
> > both methods, and even the BT specs cover both of them.
> I'm not sure if the signal interface or config file extension is the
> best, really, so I'd appreciate comments on that.

In fact, I took the time and extended the config file format. Now, the
daemon has a "SCO force" variable, that forces connection or
disconnection. If this variable is set to 0, the SCO channel will not be
connected, if it is 1, it will be connected, and if it is -1 (the
default), the connection status will depend on the driver usage.

Some sample config files:

AT\+CKPD=200
system play ~/sounds/click05.wav
AT\+CHLD=2
system play ~/sounds/click06.wav

AT\+CKPD=200
sco-force on
AT\+CHLD=2
sco-force off

AT\+CKPD=200
sco-toggle on off
AT\+CHLD=2
system play ~/sounds/click06.wav

The arguments to sco-force and sco-toggle can be `on', `off' or `none',
which corresponds to the values 1, 0 and -1 of the force variable,
respectively. The default for sco-toggle is to toggle between on and
none.

The new patch is once again available at
<http://www.dolda2000.com/~fredrik/patches/btsco.diff>

Fredrik Tolf




-------------------------------------------------------
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

  reply	other threads:[~2005-03-14 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1110683934.5056.43.camel@pc7.dolda2000.com>
     [not found] ` <4233C663.80109@xmission.com>
2005-03-14  1:11   ` [Bluez-devel] Re: [Patch] Some btsco modifications Fredrik Tolf
2005-03-14 11:52     ` Lars Grunewaldt
2005-03-14 13:51       ` Fredrik Tolf
2005-03-14 15:00         ` Fredrik Tolf [this message]
2005-03-14 12:55     ` Brad Midgley
2005-03-14 14:05       ` Fredrik Tolf
2005-03-14 17:26         ` Brad Midgley
2005-03-14 19:01           ` Florian Echtler
2005-03-14 20:34             ` Brad Midgley
2005-03-15  7:22         ` Brad Midgley
2005-03-15 23:42           ` Fredrik Tolf
2005-03-16  0:17             ` Brad Midgley
2005-03-16  1:56               ` Fredrik Tolf
2005-03-16 12:30                 ` Lars Grunewaldt
2005-03-16 13:01                   ` Fredrik Tolf
2005-03-16 15:18                     ` Brad Midgley
2005-03-16 19:34                     ` Lars Grunewaldt

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=1110812452.5056.108.camel@pc7.dolda2000.com \
    --to=fredrik@dolda2000.com \
    --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