Linux bluetooth development
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Linux-Bluetooth <linux-bluetooth@vger.kernel.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Hugues <morisset.hugues@gmail.com>
Subject: Re: Bose Quiet Comfort 35 Remaining Battery Reporting
Date: Mon, 13 Feb 2017 06:55:05 +0100	[thread overview]
Message-ID: <20170213055504.kworoylsusadecl7@earth> (raw)
In-Reply-To: <F332B3A2-F715-4526-A161-0B13CFBACEFE@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Hi,

FWIW I was also interested in battery level of my Bose QC35 and
checked this some time ago. That time I only checked the low
energy stuff, since the Android application seems to know the
battery status with only LE being connected.

Marcel Holtman wrote:
>> 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).

Bose QC35 does not expose battery status through standard battery_level
characteristic. There is a proprietary primary service 0xfebe (which
is assigned to Bose) with a couple of custom services. I assume battery
level can be read through them, but the required commands are unknown.

>> How could I read what's in the Apple HFP extensions?
>
> Start with this one. It describes the extra HFP AT commands that iOS uses:
>
> https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf

Thanks for the documentation link! That is actually implemented for
the Bose QC35. Here is a quick hack providing battery status info
in pulseaudio log:

https://github.com/sre/pulseaudio/commit/d66b66d20e9bc73e6d0ca89283cf2b5675304b00

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-02-13  5:55 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
2017-02-10 14:48             ` Marcel Holtmann
2017-02-13  5:55               ` Sebastian Reichel [this message]
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=20170213055504.kworoylsusadecl7@earth \
    --to=sre@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=morisset.hugues@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