All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel T. Cobra" <dcobra@videam.com.br>
To: venu <vjosyula@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Long delay to (re)connect a bluetooth mouse
Date: Wed, 23 Dec 2009 09:01:39 -0200	[thread overview]
Message-ID: <4B31F893.6030009@videam.com.br> (raw)
In-Reply-To: <53ea87da0912222033y530c83dci41bb6d9b99ece6c@mail.gmail.com>

Hi Venu:

Thanks for replying.

Indeed, the reconnection is always successful, and, once it reconnects, 
the mouse works well, without any lag or other issues. The whole problem 
is the 4 second delay that happens during reconnection (see the last two 
timestamps in the hicdump), making the overall process take about 5 
seconds, which is a lot to wait every time you need to awake the mouse 
from sleep mode.

Since the delay takes place right after the remote name request, I 
wonder if that may have something to do with it, and if a solution might 
be to not request again the name of a device that was previously 
connected, and is merely coming out of sleep mode. (This is just a 
guess, as I am not familiar with the Bluetooth protocol.) If you can 
suggest how I may provide more information that would help ascertain the 
cause of the delay (other hcidump flags, perhaps?), please let me know.

Regards,

Daniel


  parent reply	other threads:[~2009-12-23 11:01 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 [this message]
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=4B31F893.6030009@videam.com.br \
    --to=dcobra@videam.com.br \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vjosyula@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.