From: Hugues <morisset.hugues@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Bose Quiet Comfort 35 Remaining Battery Reporting
Date: Fri, 10 Feb 2017 15:13:30 +0100 [thread overview]
Message-ID: <589DCA8A.3060905@gmail.com> (raw)
In-Reply-To: <2D4036B9-473E-45B2-A9DE-DEC13EAD2F94@holtmann.org>
On 02/08/2017 02:19 PM, Marcel Holtmann wrote:
> Hi Luiz,
>
>>> Thanks for the reply, I know the bose android application do report the
>>> battery power of the headset, but I don't know if it is done in a
>>> propitiatory manner. How could I check that ?
>>
>> It is probably the 00000000-deca-fade-deca-deafdecacaff service, Ive
>> also seem some bose devices that are dual-mode so they have a GATT
>> service over LE that might expose these details.
>
> or it uses the Apple HFP extensions they defined to get battery status. Also 00000000-deca-fade-deca-deafdecacaff should be the wireless version of Apple’ iAP (iPod Accessory Protocol).
>
> Regards
>
> Marcel
>
>
This headset do have dual mode, I searched around using gatttool ant the
gatt specification but I find nothing about Battery Level
(org.bluetooth.characteristic.battery_level.xml) or Battery Service
(org.bluetooth.service.battery_service.xml). How could I read what's in
the APple HFP extensions ?
next prev parent reply other threads:[~2017-02-10 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 16:04 Bose Quiet Comfort 35 Remaining Battery Reporting Hugues
2017-02-07 13:23 ` Hugues
2017-02-08 9:07 ` Luiz Augusto von Dentz
2017-02-08 12:27 ` Hugues
2017-02-08 12:40 ` Luiz Augusto von Dentz
2017-02-08 13:19 ` Marcel Holtmann
2017-02-10 14:13 ` Hugues [this message]
2017-02-10 14:48 ` Marcel Holtmann
2017-02-13 5:55 ` Sebastian Reichel
2017-02-24 11:01 ` Hugues
2018-02-11 13:22 ` Hugues
2018-02-14 12:37 ` Sebastian Reichel
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=589DCA8A.3060905@gmail.com \
--to=morisset.hugues@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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).