Bose Quiet Comfort 35 Remaining Battery Reporting

Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

Hello,

I own a Bose QC35 bluetooth headset, sound is working great with
pulseaudio, but the battery reporting does not, I believe it is a
bluetooth issue because the device info doesn't say anything about
battery or power.
Any idea how I can make it report the remaining battery to upower so it
appears in my DE ?

The device info from bluetoothctl
info 04:52:C7:33:23:6E
Device 04:52:C7:33:23:6E
        Name: BQ35 Hugues
        Alias: BQ35 Hugues
        Class: 0x240418
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Vendor specific
(00000000-deca-fade-deca-deafdecacaff)
        UUID: Serial Port
(00001101-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: Advanced Audio Distribu..
(0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control
(0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree
(0000111e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information
(00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v009Ep400Cd0129

Regards,
Hugues

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

If this isn't the right place, where should I seek for more information ?

On 02/06/2017 05:04 PM, Hugues wrote:
> Hello,
> 
> I own a Bose QC35 bluetooth headset, sound is working great with
> pulseaudio, but the battery reporting does not, I believe it is a
> bluetooth issue because the device info doesn't say anything about
> battery or power.
> Any idea how I can make it report the remaining battery to upower so it
> appears in my DE ?
> 
> The device info from bluetoothctl
> info 04:52:C7:33:23:6E
> Device 04:52:C7:33:23:6E
>         Name: BQ35 Hugues
>         Alias: BQ35 Hugues
>         Class: 0x240418
>         Icon: audio-card
>         Paired: yes
>         Trusted: yes
>         Blocked: no
>         Connected: yes
>         LegacyPairing: no
>         UUID: Vendor specific
> (00000000-deca-fade-deca-deafdecacaff)
>         UUID: Serial Port
> (00001101-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: Advanced Audio Distribu..
> (0000110d-0000-1000-8000-00805f9b34fb)
>         UUID: A/V Remote Control
> (0000110e-0000-1000-8000-00805f9b34fb)
>         UUID: Handsfree
> (0000111e-0000-1000-8000-00805f9b34fb)
>         UUID: PnP Information
> (00001200-0000-1000-8000-00805f9b34fb)
>         Modalias: bluetooth:v009Ep400Cd0129
> 
> Regards,
> Hugues
> 

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Luiz Augusto von Dentz]

Hi,

On Tue, Feb 7, 2017 at 3:23 PM, Hugues <morisset.hugues@gmail.com> wrote:
> If this isn't the right place, where should I seek for more information ?
>
> On 02/06/2017 05:04 PM, Hugues wrote:
>> Hello,
>>
>> I own a Bose QC35 bluetooth headset, sound is working great with
>> pulseaudio, but the battery reporting does not, I believe it is a
>> bluetooth issue because the device info doesn't say anything about
>> battery or power.
>> Any idea how I can make it report the remaining battery to upower so it
>> appears in my DE ?
>>
>> The device info from bluetoothctl
>> info 04:52:C7:33:23:6E
>> Device 04:52:C7:33:23:6E
>>         Name: BQ35 Hugues
>>         Alias: BQ35 Hugues
>>         Class: 0x240418
>>         Icon: audio-card
>>         Paired: yes
>>         Trusted: yes
>>         Blocked: no
>>         Connected: yes
>>         LegacyPairing: no
>>         UUID: Vendor specific
>> (00000000-deca-fade-deca-deafdecacaff)
>>         UUID: Serial Port
>> (00001101-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: Advanced Audio Distribu..
>> (0000110d-0000-1000-8000-00805f9b34fb)
>>         UUID: A/V Remote Control
>> (0000110e-0000-1000-8000-00805f9b34fb)
>>         UUID: Handsfree
>> (0000111e-0000-1000-8000-00805f9b34fb)
>>         UUID: PnP Information
>> (00001200-0000-1000-8000-00805f9b34fb)
>>         Modalias: bluetooth:v009Ep400Cd0129

None of these services are specific for fetching battery power, AVRCP
and HFP do have commands for it but they are very rarely implemented
but we could indeed use upower to attach the battery information if
that is implemented.

>> Regards,
>> Hugues
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Luiz Augusto von Dentz

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

On 02/08/2017 10:07 AM, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Tue, Feb 7, 2017 at 3:23 PM, Hugues <morisset.hugues@gmail.com> wrote:
>> If this isn't the right place, where should I seek for more information ?
>>
>> On 02/06/2017 05:04 PM, Hugues wrote:
>>> Hello,
>>>
>>> I own a Bose QC35 bluetooth headset, sound is working great with
>>> pulseaudio, but the battery reporting does not, I believe it is a
>>> bluetooth issue because the device info doesn't say anything about
>>> battery or power.
>>> Any idea how I can make it report the remaining battery to upower so it
>>> appears in my DE ?
>>>
>>> The device info from bluetoothctl
>>> info 04:52:C7:33:23:6E
>>> Device 04:52:C7:33:23:6E
>>>         Name: BQ35 Hugues
>>>         Alias: BQ35 Hugues
>>>         Class: 0x240418
>>>         Icon: audio-card
>>>         Paired: yes
>>>         Trusted: yes
>>>         Blocked: no
>>>         Connected: yes
>>>         LegacyPairing: no
>>>         UUID: Vendor specific
>>> (00000000-deca-fade-deca-deafdecacaff)
>>>         UUID: Serial Port
>>> (00001101-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: Advanced Audio Distribu..
>>> (0000110d-0000-1000-8000-00805f9b34fb)
>>>         UUID: A/V Remote Control
>>> (0000110e-0000-1000-8000-00805f9b34fb)
>>>         UUID: Handsfree
>>> (0000111e-0000-1000-8000-00805f9b34fb)
>>>         UUID: PnP Information
>>> (00001200-0000-1000-8000-00805f9b34fb)
>>>         Modalias: bluetooth:v009Ep400Cd0129
> 
> None of these services are specific for fetching battery power, AVRCP
> and HFP do have commands for it but they are very rarely implemented
> but we could indeed use upower to attach the battery information if
> that is implemented.
> 
>>> Regards,
>>> Hugues
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 
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 ?

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Luiz Augusto von Dentz]

Hi,

On Wed, Feb 8, 2017 at 2:27 PM, Hugues <morisset.hugues@gmail.com> wrote:
> On 02/08/2017 10:07 AM, Luiz Augusto von Dentz wrote:
>> Hi,
>>
>> On Tue, Feb 7, 2017 at 3:23 PM, Hugues <morisset.hugues@gmail.com> wrote:
>>> If this isn't the right place, where should I seek for more information ?
>>>
>>> On 02/06/2017 05:04 PM, Hugues wrote:
>>>> Hello,
>>>>
>>>> I own a Bose QC35 bluetooth headset, sound is working great with
>>>> pulseaudio, but the battery reporting does not, I believe it is a
>>>> bluetooth issue because the device info doesn't say anything about
>>>> battery or power.
>>>> Any idea how I can make it report the remaining battery to upower so it
>>>> appears in my DE ?
>>>>
>>>> The device info from bluetoothctl
>>>> info 04:52:C7:33:23:6E
>>>> Device 04:52:C7:33:23:6E
>>>>         Name: BQ35 Hugues
>>>>         Alias: BQ35 Hugues
>>>>         Class: 0x240418
>>>>         Icon: audio-card
>>>>         Paired: yes
>>>>         Trusted: yes
>>>>         Blocked: no
>>>>         Connected: yes
>>>>         LegacyPairing: no
>>>>         UUID: Vendor specific
>>>> (00000000-deca-fade-deca-deafdecacaff)
>>>>         UUID: Serial Port
>>>> (00001101-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: Advanced Audio Distribu..
>>>> (0000110d-0000-1000-8000-00805f9b34fb)
>>>>         UUID: A/V Remote Control
>>>> (0000110e-0000-1000-8000-00805f9b34fb)
>>>>         UUID: Handsfree
>>>> (0000111e-0000-1000-8000-00805f9b34fb)
>>>>         UUID: PnP Information
>>>> (00001200-0000-1000-8000-00805f9b34fb)
>>>>         Modalias: bluetooth:v009Ep400Cd0129
>>
>> None of these services are specific for fetching battery power, AVRCP
>> and HFP do have commands for it but they are very rarely implemented
>> but we could indeed use upower to attach the battery information if
>> that is implemented.
>>
>>>> Regards,
>>>> Hugues
>>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
>>
> 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.

-- 
Luiz Augusto von Dentz

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Marcel Holtmann]

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

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

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 ?

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Marcel Holtmann]

Hi Hugues,

>>>> 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).
> 
> 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 ?

Start with this one. It describes the extra HFP AT commands that iOS uses:

https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf

Regards

Marcel

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Sebastian Reichel]

[-- 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 --]

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

Hello,
Thanks a lot!
I tried to connect to the headset through dbus to make the AT commands,
but failed.
So what's the services/program where this should be implemented so it
can be exposed on dbus and picked up by the Desktop Environment?

Regards,
Hugues

On 02/13/2017 06:55 AM, Sebastian Reichel wrote:
> 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
> 

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Hugues]

Hello,
Sebastian code works great!
But how can I proceed so the remaining battery is exposed over upower?

	Greping through pulseaudio sources
(git://anongit.freedesktop.org/pulseaudio/pulseaudio) for 'battery'
doesn't return anything, so anything about battery power seems unlikely
to be merged into pulseaudio.

	upower already expose batteries from bluez through dbus
(git://anongit.freedesktop.org/upower:src/linux/up-device-bluez.c)

So is it possible to do the AT commands at the bluez level and expose
the infos through dbus, so upower expose it to the rest of the system?

Thanks,
Hugues

On 02/24/2017 12:01 PM, Hugues wrote:
> Hello,
> Thanks a lot!
> I tried to connect to the headset through dbus to make the AT commands,
> but failed.
> So what's the services/program where this should be implemented so it
> can be exposed on dbus and picked up by the Desktop Environment?
> 
> Regards,
> Hugues
> 
> On 02/13/2017 06:55 AM, Sebastian Reichel wrote:
>> 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
>>
> 

Re: Bose Quiet Comfort 35 Remaining Battery Reporting

[Sebastian Reichel]

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

Hi Hugues,

I agree, that this should be handled in bluez instead of pulseaudio.
I only implemented the proof of concept in pulseaudio, since it was
not easily possible in bluez and easy to do in pulseaudio. I think
some restructuring of bluez/pulseaudio rfcomm handling is required,
but I don't plan to take care of this.

-- Sebastian

On Sun, Feb 11, 2018 at 02:22:46PM +0100, Hugues wrote:
> Hello,
> Sebastian code works great!
> But how can I proceed so the remaining battery is exposed over upower?
> 
> 	Greping through pulseaudio sources
> (git://anongit.freedesktop.org/pulseaudio/pulseaudio) for 'battery'
> doesn't return anything, so anything about battery power seems unlikely
> to be merged into pulseaudio.
> 
> 	upower already expose batteries from bluez through dbus
> (git://anongit.freedesktop.org/upower:src/linux/up-device-bluez.c)
> 
> So is it possible to do the AT commands at the bluez level and expose
> the infos through dbus, so upower expose it to the rest of the system?
> 
> Thanks,
> Hugues
> 
> On 02/24/2017 12:01 PM, Hugues wrote:
> > Hello,
> > Thanks a lot!
> > I tried to connect to the headset through dbus to make the AT commands,
> > but failed.
> > So what's the services/program where this should be implemented so it
> > can be exposed on dbus and picked up by the Desktop Environment?
> > 
> > Regards,
> > Hugues
> > 
> > On 02/13/2017 06:55 AM, Sebastian Reichel wrote:
> >> 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 --]