linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Brad Midgley <bmidgley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: how to set adapter to master with bluez 4.69?
Date: Wed, 23 Mar 2011 08:20:25 -0400	[thread overview]
Message-ID: <4D89E589.5010909@interlinx.bc.ca> (raw)
In-Reply-To: <4D89DCE6.7050106@interlinx.bc.ca>

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

Experimenting again this morning with both the mouse and the headset
connected both with the B/T adapter as master and the eSCO connection as
slave (since I can't seem to influence that), it was working fairly
stably.  Every now and then all devices would just completely
disconnected and then they would all reconnect.

However this most recent disconnect of all devices resulted in the mouse
reconnecting immediately but the headset went through a dozen or two
reconnection attempts (i.e. as observed by watching the output of
hcitool con with "watch -n 0") before it finally got reconnected.

This is in contrast to where I can have a completely stable (i.e. days
on end without a single hiccup) connection with just the mouse.

This really is frustrating.  ~sigh~

With all of the time I have pissed away on this, if I knew of a B/T
adapter/chipset that would absolutely work stably with multiple devices
(mouse, headset, etc.) I would just run out and buy one, but as it is, I
am on my third B/T adapter here and still nothing works stably -- as
opposed to my laptop where multiple devices seem to cohabitate nicely.

Hrm,  Given that I have multiple B/T adapters here, I don't suppose I'd
have any better luck by using another B/T adapter and just assigning 1
device to each, would I?

Cheers,
b.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-03-23 12:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  2:07 how to set adapter to master with bluez 4.69? Brian J. Murrell
2011-03-06 22:28 ` Brian J. Murrell
2011-03-07  1:08   ` Brad Midgley
2011-03-07 21:13     ` Brian J. Murrell
2011-03-07 22:57       ` Andrei Warkentin
2011-03-08 11:08         ` Brian J. Murrell
2011-03-09 11:22           ` Brian J. Murrell
2011-03-07 23:09       ` Brad Midgley
2011-03-14  3:46         ` Brad Midgley
2011-03-14 11:00           ` Brian J. Murrell
2011-03-14 12:29             ` Brian J. Murrell
2011-03-14 14:07               ` Brian J. Murrell
2011-03-14 15:29                 ` Brad Midgley
2011-03-15  0:23                   ` Brian J. Murrell
2011-03-15 12:26                   ` Brian J. Murrell
2011-03-15 12:43                     ` Brian J. Murrell
2011-03-15 15:25                       ` Brad Midgley
2011-03-17 13:10                         ` Brian J. Murrell
2011-03-17 13:22                           ` Brian J. Murrell
2011-03-17 15:46                             ` Brad Midgley
2011-03-23 11:43                   ` Brian J. Murrell
2011-03-23 12:20                     ` Brian J. Murrell [this message]
2011-03-23 16:24                       ` 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=4D89E589.5010909@interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --cc=bmidgley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).