From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Marcel Holtmann <marcel@holtmann.org>,
"Daniel T. Cobra" <dcobra@videam.com.br>
Subject: Re: Long delay to (re)connect a bluetooth mouse
Date: Wed, 23 Dec 2009 16:48:41 +0100 [thread overview]
Message-ID: <20091223164841.7070e75d@strolchi.home.s3e.de> (raw)
In-Reply-To: <1261177111.4041.99.camel@localhost.localdomain>
On Fri, 18 Dec 2009 14:58:31 -0800
Marcel Holtmann <marcel@holtmann.org> wrote:
> even if I use Bluetooth on a daily basis, I don't use any mouse or
> keyboard devices anymore. So I have no idea on how many people are
> actually using these.
I'm still using it occasionally at home (when not sitting on the sofa
with my notebook ;) and for the last few years they worked fine
(actually since we worked out the reconnect problem of the
Logitech mx1000, which looked similar, but probably was not).
My collection of two bluetooth mice still work fine and reconnect
quickly IIRC, but I will check this evening.
David, "every time I bring the mouse out of sleep mode", does this mean
the mouse went to sleep, you click the button (or move the mouse) and
it takes 5 seconds to reconnect? If so, could you try if it makes a
difference if you switch off the mouse instead? (wait until it falls
asleep, then switch off and on and check if it reconnects faster. Might
not be easy if this is a mouse that wakes up on movement, then you
probably need to lay it upside down until it sleeps).
> wouldn't be of much help until I am back at home and have my device
> library at my disposal (and bought new batteries).
I can recommend eneloop rechargeables for BT HID devices ;)
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
next prev parent reply other threads:[~2009-12-23 15:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 19:43 Long delay to (re)connect a bluetooth mouse dcobra
2009-12-17 15:17 ` Daniel T. Cobra
2009-12-18 17:43 ` Daniel T. Cobra
2009-12-18 22:04 ` Marcel Holtmann
2009-12-18 22:49 ` dcobra
2009-12-18 22:58 ` Marcel Holtmann
2009-12-19 1:21 ` dcobra
2009-12-22 12:02 ` Daniel T. Cobra
2009-12-22 12:09 ` Daniel T. Cobra
[not found] ` <53ea87da0912222033y530c83dci41bb6d9b99ece6c@mail.gmail.com>
2009-12-23 11:01 ` Daniel T. Cobra
2009-12-23 15:19 ` Daniel T. Cobra
[not found] ` <4B32336C.8080806@videam.com.br>
[not found] ` <53ea87da0912230727q617dce1axe5053cd32d03bbf5@mail.gmail.com>
2009-12-23 15:38 ` Daniel T. Cobra
2009-12-23 15:48 ` Stefan Seyfried [this message]
2009-12-23 16:00 ` venu
2009-12-23 17:53 ` Daniel T. Cobra
2009-12-29 15:01 ` Stefan Seyfried
2010-01-04 18:48 ` Daniel T. Cobra
2010-01-05 10:51 ` Stefan Seyfried
2010-02-03 11:44 ` Daniel T. Cobra
2010-02-03 13:58 ` Stefan Seyfried
2010-02-03 14:12 ` Marcel Holtmann
2010-02-03 14:34 ` Daniel T. Cobra
2010-02-03 14:37 ` Marcel Holtmann
2010-02-03 17:13 ` Daniel T. Cobra
2010-02-03 18:04 ` Iain Hibbert
2010-02-04 16:19 ` Daniel T. Cobra
2010-02-04 18:13 ` Iain Hibbert
2010-02-05 11:24 ` Daniel T. Cobra
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=20091223164841.7070e75d@strolchi.home.s3e.de \
--to=stefan.seyfried@googlemail.com \
--cc=dcobra@videam.com.br \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).