Review of "Bluetooth Battery Meter" version 37

Details Page Preview

A GNOME extension that displays indicator icons in the system tray, acting as a meter for Bluetooth device battery levels. It also provides detailed battery information via icons and text in the Bluetooth quick settings menu Note: Certain Bluetooth devices do not report battery level until Bluez's experimental features are enabled in system. Check Readme for details. The extension supports multiple device-specific modes to provide detailed battery reporting and device controls, depending on the capabilities exposed by the device: UPower: Devices such as Logitech Lightspeed keyboards and mice that report battery levels through UPower. GATT Battery Service: Devices that expose one or more battery levels via the standard GATT Battery Service (BAS), such as ZMK-based split keyboards. Socket Mode: Provides multiple battery levels and advanced device controls—such as Active Noise Cancellation (ANC) and other supported features using a custom socket-based protocol. Supported devices: - AirPods - Beats earbuds / headphones - Sony earbuds / headphones

Extension Homepage
https://github.com/maniacx/Bluetooth-Battery-Meter

No comments.

Diff Against

Files

Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.

All Versions

Previous Reviews on this Version

maniacx posted a review
Apologize for the huge diff update. This should hopefully be the last GUI update when it come to extension. Future update would be only adding new device like Sony buds, Galaxy buds socket handling and prefs. Note: checkButton and RadioButton although included are not used in this release, but would be used in the next release with Sony update. Thanks
JustPerfection rejected
1. Please remove the timeout before creating a new one since that function can be called multiple times: - line 184 `lib/widgetManagerBluez.js` - line 181 `lib/widgetManagerEnhanced.js` Also, disconnect the `_stateSignalId` in case it was connected before in both of those files (inside `_recordTimeEvent()`). 2. For `script/moreSettings.js`, If you still think that's needed, it can be approved. But IMO that's not a good approach and it's just adding more code to the extension. I think most users know they can open one prefs window at a time.
maniacx posted a review
Thanks JustPerfection. I have resubmitted the extension with the correction. I would like to keep is as script. It just easier to handle it via script as this window in Prefs is different for different devices and also I will have wire a complicated way to launch this window using dbus or schema. The script just makes it easier and the major plus point is opening this window any time regardless of any extension prefs window being opened.