public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Walt Shekrota <penguinacity@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] plantronics 320 working minor problems
Date: Thu, 22 Feb 2007 21:06:12 -0500	[thread overview]
Message-ID: <200702222106.12976.penguinacity@yahoo.com> (raw)

I think I have an answer to having to invoke  btsco twice.
Per the Plantronics instructions my headset is in pairing mode with a long 
press.

However I find that if after I have done this I give it a short press 
Then call btsco it connects perfect on the first call.

So is their document lying about pairing mode or does bluez require another 
signal? Or maybe the headset is trying to connect in some master mode and the 
additional short press says disconnect leaving it waiting?

Is there a document somewhere on the web that describes the interaction of the 
daemons for bluez?

Thanks.
-Walt

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-02-23  2:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23  2:06 Walt Shekrota [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-22  3:25 [Bluez-users] plantronics 320 working minor problems walt shekrota
2007-02-22  0:15 walt shekrota
2007-02-21 22:05 Walt Shekrota

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=200702222106.12976.penguinacity@yahoo.com \
    --to=penguinacity@yahoo.com \
    --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