A bit more text.

diff --git a/blog/data/2015-09-24-laptop-battery.txt b/blog/data/2015-09-24-laptop-battery.txt
index 638b0350b3448a9abd633067a2acf2c1e7198aec..f2c7be3522f0dc5d63aee0a77b4e84d448754e39 100644 (file)
--- a/blog/data/2015-09-24-laptop-battery.txt
+++ b/blog/data/2015-09-24-laptop-battery.txt
@@ -31,7 +31,7 @@ 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
 /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 look like this:</p>
+colletor shell script is quite simple and look like this:</p>

 
 <pre>
 #!/bin/sh
 
 <pre>
 #!/bin/sh


@@ -112,3 +112,12 @@ Linux too.</p>
 <p>Is there a way with Linux to tell the battery to stop charging at
 80%, unless requested to charge to 100% once in preparation for a
 longer trip?</p>
 <p>Is there a way with Linux to tell the battery to stop charging at
 80%, unless requested to charge to 100% once in preparation for a
 longer trip?</p>

+
+<p>I wonder why the battery capacity was reported to be more than 100%
+at the start.  I also wonder why the "full capacity" increases some
+times, and if it is possible to repeat the process to get the battery
+back to design capacity.  And I wonder if the discharge and charge
+speed change over time, or if this stay the same.  I did not yet try
+to write a tool to calculate the derivative values of the battery
+level, but suspect some interesting insights might be learned from
+those.</p>