battery stats ever since. Now my
/var/log/hjemmenett-battery-status.log file contain around 115,000
measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity. My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity. My
+collector shell script is quite simple and look like this:</p>
<pre>
#!/bin/sh
log_battery() {
# Print complete message in one echo call, to avoid race condition
- # when several log processes run in parallell.
+ # when several log processes run in parallel.
msg=$(printf "%s," $(date +%s); \
for f in $files; do \
printf "%s," $(cat $f); \
</pre>
<p>I wrote a small script to create a graph of the charge development
-over time. This graph depicted above show the slow death of mylaptop
+over time. This graph depicted above show the slow death of my laptop
battery.</p>
<p>But why is this happening? Why are my laptop batteries always
to write a tool to calculate the derivative values of the battery
level, but suspect some interesting insights might be learned from
those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop. I've done so now, but expect my existing battery is toast
+and need to be replaced. The proposal is unfortunately Thinkpad
+specific.</p>
</div>
<div class="tags">