From: RSmirnov512 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0d052a: shared/battery: improve the display of the charge ...
Date: Wed, 05 Nov 2025 02:52:30 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1019829/000000-18e86b@github.com> (raw)
Branch: refs/heads/1019829
Home: https://github.com/bluez/bluez
Commit: 0d052a4623c6986a0f3f34c7a5af4fc5d0b5c2a4
https://github.com/bluez/bluez/commit/0d052a4623c6986a0f3f34c7a5af4fc5d0b5c2a4
Author: Roman Smirnov <r.smirnov@omp.ru>
Date: 2025-11-05 (Wed, 05 Nov 2025)
Changed paths:
M Makefile.am
M src/battery.c
A src/shared/battery.c
A src/shared/battery.h
Log Message:
-----------
shared/battery: improve the display of the charge level
The battery charge level may fluctuate due to uncalibrated
sensors. Commit smooths out such fluctuations.
The algorithm for determining uncalibrated sensors consists of
finding the number of changes in charge direction (i.e., "spikes").
If the number of spikes is zero, the device is charging or discharging.
If there is one spike, it may mean that the device has started charging
or has been disconnected from charging. If there are two or more spikes,
this is a clear indication of an uncalibrated sensor.
Check that the battery charge is fluctuating. If the battery charge
is fluctuating, use the average charge value, otherwise use the current
value.
Fixes: https://github.com/bluez/bluez/issues/1612
Commit: 18e86b1931bd1d60132567a23eb8885fb1e9ca6b
https://github.com/bluez/bluez/commit/18e86b1931bd1d60132567a23eb8885fb1e9ca6b
Author: Roman Smirnov <r.smirnov@omp.ru>
Date: 2025-11-05 (Wed, 05 Nov 2025)
Changed paths:
M .gitignore
M Makefile.am
M doc/test-coverage.txt
A unit/test-battery.c
Log Message:
-----------
unit: Add basic unit tests for battery charge handling
Compare: https://github.com/bluez/bluez/compare/0d052a4623c6%5E...18e86b1931bd
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-11-05 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1019829/000000-18e86b@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).