6ff28d8731
1. Only do low battery processing if the battery being queried is the "virtual aggregate battery" (ID -1), this fixes the issue of spurious and duplicated low battery warnings whenever the extended info panel is open (and therefore multiple batteries are being individually queried). 2. Calculate the time remaining separately after adding up all the individual battery values, this works around batteries which are not currently in use returning -1 time_left which caused the aggregate to be incorrect if the values from the driver interface are simply added as-is. An example situation to illustrate item 2: Battery 0 capacity: 20,000mWh Battery 0 draw: 0mW Battery 0 state: Unused Battery 0 time_left: -1 (since it currently has zero draw on it, it has "infinite time left" if looked at in isolation) Battery 1 capacity: 20,000mWh Battery 1 draw: 10,000mW Battery 1 state: Discharging Battery 1 time_left: 2 hours If the time_lefts are added together (even if battery 0 is ignored for that calculation), it'll show 2 hours left despite there being 40,000mWh of total capacity for a 10,000mW draw. We now treat all batteries together as one large one instead, calculating the draw/capacity on the totals which gives an accurate number. This fixes issues 2 and 3 in bug #19167. Change-Id: I1b9a0c3dd47f917da86becfcfebed7b35b3422d4 Reviewed-on: https://review.haiku-os.org/c/haiku/+/8462 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: waddlesplash <waddlesplash@gmail.com> Haiku-Format: Haiku-format Bot <no-reply+haikuformatbot@haiku-os.org> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.