All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Ryan Press <ryan@presslab.us>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: LE mouse reconnect problem
Date: Tue, 1 Jul 2014 11:49:48 +0200	[thread overview]
Message-ID: <F2336E43-F4C9-411A-A3A3-1D0BF659C1F7@holtmann.org> (raw)
In-Reply-To: <CABx3TkVt3t_dyRmY6rjrwzw9BoTRaZinHOQEEbyVND+_NjLSVQ@mail.gmail.com>

Hi Ryan,

>>> I have one other question with it.  When it first reconnects the mouse
>>> pointer is really jerky, like it's updating really slow.  Then after a
>>> few seconds it is normal; in fact it is very responsive compared to my
>>> old Bluetooth mouse.  With Windows 8.1 it reconnects lightning fast
>>> when I turn it on, and it is not jerky at first.
>>> 
>> this is a kernel issue with not remembering the previous connection parameters. What you see is that we start connecting with the default values and then the slave (the mouse) will correct us and tell us what connection parameters it needs. We accept them and actually change the LE link to use these parameters. However we end up forgetting them. So every time you connect this procedure keeps repeating itself.
>> 
>> I fixed this as well, but for that you will need a bluetooth-next kernel where I enabled the management API for passive scanning and a modified bluetoothd that will then allow you a smooth experience. If the slave updates the connection parameters we remember them for devices using auto-connection. So once the connection is triggered via passive scanning the values will be remembered.
>> 
>> At the moment, I have one minor issue with the re-connection within bluetoothd and once that is fixed this should be pretty instant.
> 
> 
> Okay, great, glad to hear that you're already on it.  I'm really
> looking forward to the seamless Bluetooth experience on Linux!  When
> everything is ready and in the master branch let me know and I will
> try them out.

the current bluetooth-next tree and bluez.git should now make this work smoothly. The first connection after starting bluetoothd will still use the wrong connection parameters, but all future ones will be snappy.

Regards

Marcel


  reply	other threads:[~2014-07-01  9:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  2:27 LE mouse reconnect problem Ryan Press
2014-06-25  7:08 ` Luiz Augusto von Dentz
     [not found]   ` <CABx3TkVgs6J1UR8Z5Rbyd2e90p74RfggpzsvnxzgWGgN9c2Epg@mail.gmail.com>
2014-06-25 13:23     ` Fwd: " Ryan Press
2014-06-27  8:32       ` Luiz Augusto von Dentz
2014-06-28 15:50         ` Ryan Press
2014-06-28 19:22           ` Luiz Augusto von Dentz
2014-06-28 20:07             ` Ryan Press
2014-06-29  4:51               ` Ryan Press
2014-06-29  5:14                 ` Johan Hedberg
2014-06-29  5:29                   ` Johan Hedberg
2014-06-29  9:43                     ` Marcel Holtmann
2014-06-29 17:02                       ` Ryan Press
2014-06-29 17:52                         ` Marcel Holtmann
2014-06-29 19:01                           ` Ryan Press
2014-07-01  9:49                             ` Marcel Holtmann [this message]
2014-07-03  3:01                               ` Ryan Press
2014-07-03  7:29                                 ` Marcel Holtmann
2014-07-03 15:18                           ` d.eriksson
2014-07-03 15:41                             ` Marcel Holtmann
2014-07-03 16:40                               ` d.eriksson
2014-07-03 16:48                                 ` Marcel Holtmann
2014-07-17  5:40                                 ` Scott James Remnant
2014-06-29 19:03                       ` Scott James Remnant
2014-06-29 19:19                         ` Marcel Holtmann
2014-06-29 19:37                           ` Scott James Remnant
2014-06-29 19:56                             ` Marcel Holtmann
2014-06-29 20:02                               ` Scott James Remnant
2014-07-01 16:01                             ` Marcel Holtmann
2014-07-17  5:42                               ` Scott James Remnant

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=F2336E43-F4C9-411A-A3A3-1D0BF659C1F7@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=ryan@presslab.us \
    /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.