linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Daniel T. Cobra" <dcobra@videam.com.br>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Long delay to (re)connect a bluetooth mouse
Date: Fri, 18 Dec 2009 14:04:59 -0800	[thread overview]
Message-ID: <1261173899.4041.96.camel@localhost.localdomain> (raw)
In-Reply-To: <4B2BBF58.4030901@videam.com.br>

Hi Daniel,

> Unbelievable! Here too my posts get zero replies!
> 
> I fell like Bruce Willis in "The Sixth Sense". Maybe I died and just 
> haven't realized it yet! Where is that kid that talks to the dead? Maybe 
> he knows something about bluetooth mouse reconnection delays.
> 
> But, seriously, I guess I'll just have to give up using my bluetooth 
> mouse under Linux. Waiting 5 to 6 seconds for the mouse to reconnect 
> every time it goes to sleep is too much of a nuisance!
> 
> If anybody can read me, good luck with your work developing bluez and 
> happy Holidays to all.

you do know that an open source community doesn't work like this. If
someone would be able to make anything out of your posting or has
experienced the same, they would have spoken. Since you didn't even
include any logs or hcidump details, you didn't even gave any person
without the hardware to respond.

Regards

Marcel



  reply	other threads:[~2009-12-18 22:04 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 [this message]
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
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=1261173899.4041.96.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=dcobra@videam.com.br \
    --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).