From: Szymon Janc <szymon.janc@codecoup.pl>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothctl: list-attributes doesn't list services from example-gatt-server
Date: Wed, 17 Jul 2019 11:26:01 +0200 [thread overview]
Message-ID: <16286916.LhmCvT1dVb@ix> (raw)
In-Reply-To: <c08604d7-5708-ed37-9e55-93e67e06a3da@gmail.com>
Hi Rafał,
On Tuesday, 9 July 2019 14:14:07 CEST Rafał Miłecki wrote:
> On 07.07.2019 12:14, Rafał Miłecki wrote:
> > I decided to test GATT. On elitebook I started:
> > ./test/example-gatt-server
> > and waited to let matebook refresh all info.
> >
> > After that I got:
> >
> > [elitebook]# info 20:16:B9:D8:A9:3B
> > Device 20:16:B9:D8:A9:3B (public)
> >
> > Name: elitebook
> > Alias: elitebook
> > Class: 0x001c010c
> > Icon: computer
> > Paired: yes
> > Trusted: yes
> > Blocked: no
> > Connected: yes
> > LegacyPairing: no
> > UUID: IrMC Sync
> > (00001104-0000-1000-8000-00805f9b34fb) UUID: OBEX Object Push
> > (00001105-0000-1000-8000-00805f9b34fb) UUID: OBEX File Transfer
> > (00001106-0000-1000-8000-00805f9b34fb) UUID: Headset
> > (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Source
> > (0000110a-0000-1000-8000-00805f9b34fb) UUID: Audio Sink
> > (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target
> > (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control
> > (0000110e-0000-1000-8000-00805f9b34fb) UUID: Headset AG
> > (00001112-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server
> > (0000112f-0000-1000-8000-00805f9b34fb) UUID: Message Access Server
> > (00001132-0000-1000-8000-00805f9b34fb) UUID: Message Notification Se..
> > (00001133-0000-1000-8000-00805f9b34fb) UUID: PnP Information
> > (00001200-0000-1000-8000-00805f9b34fb) UUID: Heart Rate
> > (0000180d-0000-1000-8000-00805f9b34fb) UUID: Battery Service
> > (0000180f-0000-1000-8000-00805f9b34fb) UUID: Vendor specific
> > (00005005-0000-1000-8000-0002ee000001) UUID: Vendor specific
> > (12345678-1234-5678-1234-56789abcdef0) Modalias: usb:v1D6Bp0246d0532
> >
> > That seems all correct for now. Test example-gatt-server registers
> > Heart Rate, Battery & Test services. All of them appeared as expected.
> >
> > My problem is that I can't list GATT attributes. I don't any output.
> > Is there anything I'm doing incorrectly?
>
> I decided to test nRF Connect Android app. It showed something
> interesting about my bluetooth devices. It nicely displays & parses
> advertising data.
>
> Logitech M590 advertises:
> 0x01 Flags
> 0x03 Complete List of 16-bit Service Class UUIDs
> 0x09 Complete Local Name
> 0x0A Tx Power Level
> 0x19 Appearance
>
> BlueZ on "elitebook" advertises:
> 0xFF Manufacturer Specific Data
> or to say precisely:
> 0x1BFF750042040180AE78BDBC0B7E307ABDBC0B7E2F01000000000000
>
> Any idea/hint why BlueZ 5.30 on my "elitebook" notebook doesn't
> advertise more data?
Just to be sure, are you using 5.30? If so, update to 5.50..
--
pozdrawiam
Szymon Janc
next prev parent reply other threads:[~2019-07-17 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 10:14 bluetoothctl: list-attributes doesn't list services from example-gatt-server Rafał Miłecki
2019-07-08 13:19 ` Luiz Augusto von Dentz
2019-07-08 13:40 ` Rafał Miłecki
2019-07-09 12:14 ` Rafał Miłecki
2019-07-17 9:26 ` Szymon Janc [this message]
2019-07-17 9:35 ` Rafał Miłecki
2019-07-17 9:38 ` Rafał Miłecki
2019-07-17 9:44 ` Szymon Janc
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=16286916.LhmCvT1dVb@ix \
--to=szymon.janc@codecoup.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zajec5@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