Summary: | Discharge rate is reported wrong on a two-battery system because "true 0W" is not allowed by heuristics | ||
---|---|---|---|
Product: | upower | Reporter: | Tomislav Ivek <tomislav.ivek> |
Component: | general | Assignee: | Richard Hughes <richard> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | tomislav.ivek |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
allow 0W battery discharge rate to be reported
allow 0W battery discharge rate to be reported allow 0W battery discharge rate to be reported |
Description
Tomislav Ivek
2017-08-17 13:58:46 UTC
I forgot to add system details in the bug report. Hardware: Lenovo ThinkPad 470, two batteries. OS: Fedora 26 upower 0.99.5, builds 0.99.5-1.fc26 and 0.99.5-3.fc28 Created attachment 133583 [details] [review] allow 0W battery discharge rate to be reported This is the correct patch that allows 0W discharge rate to be reported and the one I am currently testing. Please ignore the patch in the original bug report. Created attachment 133620 [details] [review] allow 0W battery discharge rate to be reported It seems additionally we need to allow storage of energy data points which are the same as previous (of course that is the case if there is no discharge). Heuristics: if energy is the same as previous energy, then skip taking the new point. This patch takes the new point if more than 5min passed since taking the last point. In effect, flukes will still be rejected but the reported discharge rate of a battery that suddenly stopped being used will slowly decay to 0W. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/upower/upower/issues/44. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.