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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: upower consuming over 17% cpu Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
