All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Smith <ga29smith@gmail.com>
To: Bluez List <linux-bluetooth@vger.kernel.org>
Subject: Cached Device UUIDs not Visable on DBus
Date: Fri, 10 Apr 2015 13:34:00 -0400	[thread overview]
Message-ID: <55280988.7090400@gmail.com> (raw)

When searching for devices, I ckeck the service UUIDs to find the 
correct device to connect to. On the first run of the program the device 
is discovered, the service UUID is matched, and everything goes 
smoothly. On every other run after the first the device is found, but no 
service UUIDs are set. I check for a PropertiesChanged signal when this 
occurs, but the signal is only ever sent when the RSSI value changes. 
When the system is rebooted, the program can run again once.
I am using Bluez 5.30 and the high level GIO DBus API. I see that the 
GIO DBus API, specifically GDBusProxy, caches properties, but promises 
that they are updated on PropertiesChanged signals. As the program works 
once I do not think that it is the fault of the GIO DBus API. Is there 
something I am missing with Bluez's operation that would cause this 
error to happen?

-- 
Thank you,
Gabriel Smith


             reply	other threads:[~2015-04-10 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 17:34 Gabriel Smith [this message]
2015-04-13  9:19 ` Cached Device UUIDs not Visable on DBus Luiz Augusto von Dentz

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=55280988.7090400@gmail.com \
    --to=ga29smith@gmail.com \
    --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 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.