View Single Post
Old 06-27-2012, 02:05 PM   #9
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by baf View Post
Great job nick-tech!

On K5 the easiest way to get battery info is:
Code:
[root@kindle root]# gasgauge-info 
usage:
gasgauge-info [-chklms] [-i <seconds>] <registers...>
-h      help
--help  help

-i s    interval (seconds)

-c      output state of charge in percent
-s      same as -c
-v      output battery voltage value
-l      output battery charge current (load)
-k      output battery temperature
-m      output battery available capacity (mAh)
Nice find. A lot of the /proc interfaces have a shell wrapper like this for them, but the proc output is often easier to parse in a script, while the wrapper is easier for human use.
geekmaster is offline   Reply With Quote