* Bose Quiet Comfort 35 Remaining Battery Reporting
@ 2017-02-06 16:04 Hugues
2017-02-07 13:23 ` Hugues
0 siblings, 1 reply; 12+ messages in thread
From: Hugues @ 2017-02-06 16:04 UTC (permalink / raw)
To: linux-bluetooth
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
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 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 0 siblings, 1 reply; 12+ messages in thread From: Hugues @ 2017-02-07 13:23 UTC (permalink / raw) To: linux-bluetooth 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 > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-07 13:23 ` Hugues @ 2017-02-08 9:07 ` Luiz Augusto von Dentz 2017-02-08 12:27 ` Hugues 0 siblings, 1 reply; 12+ messages in thread From: Luiz Augusto von Dentz @ 2017-02-08 9:07 UTC (permalink / raw) To: Hugues; +Cc: linux-bluetooth 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-08 9:07 ` Luiz Augusto von Dentz @ 2017-02-08 12:27 ` Hugues 2017-02-08 12:40 ` Luiz Augusto von Dentz 0 siblings, 1 reply; 12+ messages in thread From: Hugues @ 2017-02-08 12:27 UTC (permalink / raw) To: Luiz Augusto von Dentz; +Cc: linux-bluetooth 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 ? ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-08 12:27 ` Hugues @ 2017-02-08 12:40 ` Luiz Augusto von Dentz 2017-02-08 13:19 ` Marcel Holtmann 0 siblings, 1 reply; 12+ messages in thread From: Luiz Augusto von Dentz @ 2017-02-08 12:40 UTC (permalink / raw) To: Hugues; +Cc: linux-bluetooth 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-08 12:40 ` Luiz Augusto von Dentz @ 2017-02-08 13:19 ` Marcel Holtmann 2017-02-10 14:13 ` Hugues 0 siblings, 1 reply; 12+ messages in thread From: Marcel Holtmann @ 2017-02-08 13:19 UTC (permalink / raw) To: Luiz Augusto von Dentz; +Cc: Hugues, linux-bluetooth 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-08 13:19 ` Marcel Holtmann @ 2017-02-10 14:13 ` Hugues 2017-02-10 14:48 ` Marcel Holtmann 0 siblings, 1 reply; 12+ messages in thread From: Hugues @ 2017-02-10 14:13 UTC (permalink / raw) To: Marcel Holtmann, Luiz Augusto von Dentz; +Cc: linux-bluetooth 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 ? ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-10 14:13 ` Hugues @ 2017-02-10 14:48 ` Marcel Holtmann 2017-02-13 5:55 ` Sebastian Reichel 0 siblings, 1 reply; 12+ messages in thread From: Marcel Holtmann @ 2017-02-10 14:48 UTC (permalink / raw) To: Hugues; +Cc: Luiz Augusto von Dentz, linux-bluetooth 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-10 14:48 ` Marcel Holtmann @ 2017-02-13 5:55 ` Sebastian Reichel 2017-02-24 11:01 ` Hugues 0 siblings, 1 reply; 12+ messages in thread From: Sebastian Reichel @ 2017-02-13 5:55 UTC (permalink / raw) To: Linux-Bluetooth; +Cc: Luiz Augusto von Dentz, Marcel Holtmann, Hugues [-- 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 --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-13 5:55 ` Sebastian Reichel @ 2017-02-24 11:01 ` Hugues 2018-02-11 13:22 ` Hugues 0 siblings, 1 reply; 12+ messages in thread From: Hugues @ 2017-02-24 11:01 UTC (permalink / raw) To: Sebastian Reichel, Linux-Bluetooth Cc: Luiz Augusto von Dentz, Marcel Holtmann 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 > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2017-02-24 11:01 ` Hugues @ 2018-02-11 13:22 ` Hugues 2018-02-14 12:37 ` Sebastian Reichel 0 siblings, 1 reply; 12+ messages in thread From: Hugues @ 2018-02-11 13:22 UTC (permalink / raw) To: Sebastian Reichel, Linux-Bluetooth Cc: Luiz Augusto von Dentz, Marcel Holtmann 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 >> > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Bose Quiet Comfort 35 Remaining Battery Reporting 2018-02-11 13:22 ` Hugues @ 2018-02-14 12:37 ` Sebastian Reichel 0 siblings, 0 replies; 12+ messages in thread From: Sebastian Reichel @ 2018-02-14 12:37 UTC (permalink / raw) To: Hugues; +Cc: Linux-Bluetooth, Luiz Augusto von Dentz, Marcel Holtmann [-- 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 --] ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2018-02-14 12:37 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2017-02-24 11:01 ` Hugues 2018-02-11 13:22 ` Hugues 2018-02-14 12:37 ` Sebastian Reichel
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.