linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Davies <linux-bluetooth-list@steev.me.uk>
To: linux-bluetooth@vger.kernel.org
Subject: BLE: dbus doesn't show GATT characteristics
Date: Mon, 21 Sep 2015 21:23:42 +0100	[thread overview]
Message-ID: <5600674E.2010602@steev.me.uk> (raw)

I'm having a problem using BLE through dbus where the GATT services
don't appear after a BLE device has been found during a scan. What is
available through dbus is a Device1 node with the correct address and a
Name property of the name which was sent in the advertising beacons -
however that's the only node available in the tree.

When running with the same BLE dongle (ID 0a5c:21e8 Broadcom Corp.
BCM20702A0 Bluetooth 4.0) and same BLE remote device (TI SensorTag 2
CC2650STK) on a different computer I can see all the GATT
characteristics in the dbus tree without any problems.

The computer with the problem is running on kernel 4.2.0 with bluez
5.34. gatttool works without a problem.

Where should I start looking to find out why this is happening? I am a
developer; if someone could point me in the direction to begin looking
I'll do some investigation.

Regards
Steven Davies

             reply	other threads:[~2015-09-21 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 20:23 Steven Davies [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-21 20:20 BLE: dbus doesn't show GATT characteristics Steven Davies
2015-09-21 22:02 ` Mark Rages
2015-09-22  7:53   ` Steven Davies
2015-09-22 10:12     ` Luiz Augusto von Dentz
2015-09-22 13:44       ` Steven Davies
2015-09-23  7:22         ` Luiz Augusto von Dentz
2015-09-26 16:00           ` linux-bluetooth-list

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=5600674E.2010602@steev.me.uk \
    --to=linux-bluetooth-list@steev.me.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).