#!/bin/sh
@@ -83,7 +83,7 @@ fi
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); \
@@ -118,7 +118,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
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.
But why is this happening? Why are my laptop batteries always @@ -153,6 +153,14 @@ to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.
+Update 2015-09-24: I got a tip 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.
+