public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Ilya Rubtsov <lusyaru@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: DeviceFound and DeviceDisappeared signals
Date: Sat, 2 May 2009 19:20:55 -0300	[thread overview]
Message-ID: <2d5a2c100905021520i374024a2u565626e4c7f00b87@mail.gmail.com> (raw)
In-Reply-To: <49FB3C18.8030505@gmail.com>

Hi,

On Fri, May 1, 2009 at 3:14 PM, Ilya Rubtsov <lusyaru@gmail.com> wrote:
> I just would add that with hardware scheduler DeviceDisappeared signal works
> fine if there two remote devices in the field, and doesn't work if there is
> only one remote device:
>
> ---
> # Now there only 00:16:B8:53:5F:17 is turned on
> Fri May  1 20:36:48 2009 Signal: DeviceFound 00:16:B8:53:5F:17
> # Now I turn off 00:16:B8:53:5F:17 and wait, but no signal being emitted...
> # So, I turn on 00:02:76:16:F6:8F
> Fri May  1 20:38:52 2009 Signal: DeviceFound 00:02:76:16:F6:8F
> Fri May  1 20:39:01 2009 Signal: DeviceDisappeared 00:16:B8:53:5F:17

You may just have to wait longer to get the DeviceDisappeared signal
the fact the you turned off the device doesn't mean it will instantly
disappear it may happen that bluetoothd is idle waiting for scheduler
to start another discovery round (use Discovering property to check
that.). I will double check if there is some logic problem while
emitting DeviceDisappeared but I remember fixing it myself last time
and have no complaining since then.

-- 
Luiz Augusto von Dentz
Engenheiro de Computação

  reply	other threads:[~2009-05-02 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 14:41 DeviceFound and DeviceDisappeared signals Ilya Rubtsov
2009-05-01 18:14 ` Ilya Rubtsov
2009-05-02 22:20   ` Luiz Augusto von Dentz [this message]
2009-05-02 23:31     ` Ilya Rubtsov

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=2d5a2c100905021520i374024a2u565626e4c7f00b87@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lusyaru@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox