It seems the problem relies more on the kernel side and with the amount of events the battery driver sends to the userspace (even when there is no change).
udevadm monitor is already enough to show the amount of kernel events the battery driver sends to the userspace.
It seems the problem relies more on the kernel side and with the amount of events the battery driver sends to the userspace (even when there is no change).
udevadm monitor is already enough to show the amount of kernel events the battery driver sends to the userspace.