X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/9e0b8ef3ce62050c1f3609c328309fa9fcc76010..eb8ff3442e46d34cea37644170167d445c5cb3b4:/blog/archive/2016/03/03.rss
diff --git a/blog/archive/2016/03/03.rss b/blog/archive/2016/03/03.rss
index 983a1d4016..0b85ed8b0a 100644
--- a/blog/archive/2016/03/03.rss
+++ b/blog/archive/2016/03/03.rss
@@ -6,6 +6,62 @@
http://people.skolelinux.org/pere/blog/
+
+ Full battery stats collector is now available in Debian
+ http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
+ http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
+ Wed, 23 Mar 2016 22:10:00 +0100
+ <p>Since this morning, the battery-stats package in Debian include an
+extended collector that will collect the complete battery history for
+later processing and graphing. The original collector store the
+battery level as percentage of last full level, while the new
+collector also record battery vendor, model, serial number, design
+full level, last full level and current battery level. This make it
+possible to predict the lifetime of the battery as well as visualise
+the energy flow when the battery is charging or discharging.</p>
+
+<p>The new tools are available in <tt>/usr/share/battery-stats/</tt>
+in the version 0.5.1 package in unstable. Get the new battery level graph
+and lifetime prediction by running:
+
+<p><pre>
+/usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
+</pre></p>
+
+<p>Or select the 'Battery Level Graph' from your application menu.</p>
+
+<p>The flow in/out of the battery can be seen by running (no menu
+entry yet):</p>
+
+<p><pre>
+/usr/share/battery-stats/battery-stats-graph-flow
+</pre></p>
+
+<p>I'm not quite happy with the way the data is visualised, at least
+when there are few data points. The graphs look a bit better with a
+few years of data.</p>
+
+<p>A while back one important feature I use in the battery stats
+collector broke in Debian. The scripts in
+<tt>/usr/lib/pm-utils/power.d/</tt> were no longer executed. I
+suspect it happened when Jessie started using systemd, but I do not
+know. The issue is reported as
+<a href="https://bugs.debian.org/818649">bug #818649</a> against
+pm-utils. I managed to work around it by adding an udev rule to call
+the collector script every time the power connector is connected and
+disconnected. With this fix in place it was finally time to make a
+new release of the package, and get it into Debian.</p>
+
+<p>If you are interested in how your laptop battery is doing, please
+check out the
+<a href="https://tracker.debian.org/pkg/battery-stats">battery-stats</a>
+in Debian unstable, or rebuild it on Jessie to get it working on
+Debian stable. :) The upstream source is available from
+<a href="https://github.com/petterreinholdtsen/battery-stats">github</a>.
+As always, patches are very welcome.</p>
+
+
+
UsingQR - "Electronic" paper invoices using JSON and QR codes
http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html
@@ -94,10 +150,10 @@ similar systems. In the Czech republic, the Czech Banking Association
standard #26, with short name SPAYD, uses QR codes with payment
information. More information is available from the Wikipedia page on
<a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short
-Payment Descriptor</a>. And I Germany, there is a system named
+Payment Descriptor</a>. And in Germany, there is a system named
<a href="http://www.bezahlcode.de/">BezahlCode</a>,
(<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification
-v1.8 2013-12-05 available as PDF</a>), which uses QR code with
+v1.8 2013-12-05 available as PDF</a>), which uses QR codes with
URL-like formatting using "bank:" as the URI schema/protocol to
provide the payment information. There is also the
<a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a>