public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] DiscoveryStarted / DiscoveryComplete Signal Not	Sent
Date: Mon, 22 Oct 2007 12:42:35 +0200	[thread overview]
Message-ID: <1193049756.6184.167.camel@violet> (raw)
In-Reply-To: <BAY102-W11B9C20DCF53865C058207F09A0@phx.gbl>

Hi Robert,

> I'm using the D-Bus API for an application and have recently started
> playing around with the periodic discovery process, however it seems
> that the DiscoveryStrarted and DiscoveryComplete signals are not sent
> at the beginning and end of each scan 'period'. Is this usual
> behaviour? I notice in the API documentation there are two functions
> for start and end of a period scan, however these don't seem to run at
> the start and end of every period, only the entire scanning process,
> is that correct?

it is designed to be this way. The periodic inquiry is different from
the normal inquiry in its semantics.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-10-22 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22  9:44 [Bluez-users] DiscoveryStarted / DiscoveryComplete Signal Not Sent Robert Rawlins
2007-10-22 10:42 ` Marcel Holtmann [this message]

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=1193049756.6184.167.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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