Should read battery_current_now  not battery_current I seem to be on a """"""""""""""""quest"""""""""""""""" to find any app/widget/piece of software that will do one simple task: read the battery current sensor in """"""""""""""""relative real-time"""""""""""""""" - that is  as the CPU scales up and down  GPU kicks in and out  4G modem does its dance  and as all the little things of the system do their work  I can see the immediate response in the current that is MEASURED BY MY PHONE'S SENSOR. It has a sensor. It doesn't need estimation. It just needs an app that'll read /sys/class/power_supply/battery/battery_current_now without delaying 10 seconds for statistics logging or because it thinks it'll only update that fast. I can open a (non-root) shell and """"""""""""""""cat /sys/class/power_supply/battery/battery_current_now""""""""""""""""  and it'll show me a new value each time  as often as I run it  multiple times a second. Why can't an app do that? Even when I select """"""""""""""""1"""""""""""""""" for the refresh interval (which would be adequate  but still slow)  the """"""""""""""""last updated"""""""""""""""" timer ticks away  but the value stays the same. This means the app is reading """"""""""""""""battery_current""""""""""""""""  not """"""""""""""""battery_current_now"""""""""""""""" (I tested that - """"""""""""""""now"""""""""""""""" is real-time). For as well designed as this app is  I'm surprised this was overlooked! :(""
July 01 2014