Annoying battery notifications #2317
Comments
|
Right-click, Plugins, ConnectionNotifier |
This also disables all connected/disconnected messages, not just battery updates. I would like to see the battery status only once when the device is first connected, but not on subsequent updates (drop by 1%). |
|
To be honest I haven't seen a device that provides battery updates with a 1 % granularity. We can make notifications configurable, of course, but could it be a reasonable tradeoff to only show new values if they are multiples of 10 % or would that still annoy you? |
10% only sounds acceptable to me. |
|
I also find this annoying, especially since my keyboard's battery is "unstable". So I add an option to turn off battery updates: 4eUeP@5a9ac22
How about showing notifications only when the battery level is lower than a value(e.g., 10%)? Proposal: a new option, e.g., |
The Galaxy Buds2 Pro do that unfortunately :/ |
|
Not sure about a minimum battery level. The purpose of the notifications is (or was) to inform about the current level. Most of that should be rather up to a power management tool and in many cases they probably do handle it by now (via UPower). A "running low" logic in blueman seems a bit pointless in light of power management tools and an arbitrary threshold does not sound like a good idea, e.g. mice typically provide distinct levels like 100 %, 80 %, 50 % and 20 % for which a 10 % threshold would just never trigger. The applet plugin for battery level notifications used to be separate and I'd say the main purpose was to show the level on connection. We merged it with |
|
I have devices that can't decide what their battery level is supposed to be, they flicker back and forth between 100% and 90% several times as their battery depletes. So a change to the threshold to 10% would not fix the notification annoyance. Turning off the ConnectionNotifier plugin altogether is fine by me, just mentioning this in case it's useful to help with the solution. |
|
Now I see these notifications. And there are a lot of them. |
|
Well, ok, I don't see us going down that rabbit hole. So, as we do not want to get into power management applet business, I suggest that we show the battery level on connection only and do not process any updates. |
How can I change this setting? Is there a config somewhere? Also the threshold idea seems the way to go. |
There is a link to the fork, so the config is in that fork and is not merged here. You need to build the fork if you want to use it right now.
The conversations above have concluded that the threshold idea is not the way to go. Instead, we will "show the battery level on connection only and do not process any updates". Please read them and give your argument if you disagree. |
From feedback in blueman-project#2317 it became pretty clear that battery data is a mess with devices providing levels like full, medium, low and devices providing fine-grained percent values, flapping values etc. and we do not want to go into power management applet business, so we only show a single battery connection (when the battery interface shows up or - if the interface is already present when the device connects - when the existing interface sends its first property update) and drop the reference to the connection notification to update so that further values do not lead to a notification. (In case people will ask for those notifications we might add them as a separate plugin that's disabled by default.) Due to the great demand, I plan to backport this for 2.4.2, even though it's technically a regression. Closes blueman-project#2317
|
Please try #2362 |
Backport of blueman-project#2362 due to the great demand seen in blueman-project#2317. This is technically a regression, but the current behavior seems unacceptable in many cases, so let's pretend that we never intentionally added those additional notifications. Closes blueman-project#2317
From feedback in #2317 it became pretty clear that battery data is a mess with devices providing levels like full, medium, low and devices providing fine-grained percent values, flapping values etc. and we do not want to go into power management applet business, so we only show a single battery connection (when the battery interface shows up or - if the interface is already present when the device connects - when the existing interface sends its first property update) and drop the reference to the connection notification to update so that further values do not lead to a notification. (In case people will ask for those notifications we might add them as a separate plugin that's disabled by default.) Due to the great demand, I plan to backport this for 2.4.2, even though it's technically a regression. Closes #2317
Backport of blueman-project#2362 due to the great demand seen in blueman-project#2317. This is technically a regression, but the current behavior seems unacceptable in many cases, so let's pretend that we never intentionally added those additional notifications. Closes blueman-project#2317
Backport of blueman-project#2362 due to the great demand seen in blueman-project#2317. This is technically a regression, but the current behavior seems unacceptable in many cases, so let's pretend that we never intentionally added those additional notifications. Closes blueman-project#2317
blueman: 2.4
BlueZ: 5.73
Distribution: Arch Linux
Desktop environment: Sway
Hi,
I'm getting a notification every time my earbuds' batteries drop by 1%. It is getting pretty annoying, how do I disable that?
Regards,
Jules
The text was updated successfully, but these errors were encountered: