Monitoring battery charge

[MrTick]

I feel my Kindle works less and less on a full charge, but maybe I just read more.
Anyway to verify that I've created a simple script to monitor the battery charge and screensaver events.

#!/bin/bash

VERSION='1.0'
LOGFILE='/mnt/base-us/battery.log'
SOURCES=$'com.lab126.powerd\ncom.lab126.hal'

touch $LOGFILE

echo [`date`] Starting $0 v$VERSION >> $LOGFILE

echo "$SOURCES" | lipc-wait-event -m -l battLevelChanged,goingToScreenSaver,outOfScreenSaver,charging,notCharging | while read event; do
	echo [`date`] $event >> $LOGFILE
	done

It uses lipc-wait-event so should have no visible influence on the battery live.

Example log print:

[Fri Oct 18 11:00:24 EEST 2019] Starting /mnt/us/extensions/battstat/bin/battstat.sh v1.0
[Fri Oct 18 11:01:28 EEST 2019] Event Source: com.lab126.powerd
[Fri Oct 18 11:01:28 EEST 2019] Event Source: com.lab126.hal
[Fri Oct 18 11:01:28 EEST 2019] Waiting for events...
[Fri Oct 18 11:01:28 EEST 2019] com.lab126.powerd charging
[Fri Oct 18 11:03:24 EEST 2019] com.lab126.powerd battLevelChanged 98
[Fri Oct 18 11:08:28 EEST 2019] com.lab126.powerd battLevelChanged 99
[Fri Oct 18 11:14:58 EEST 2019] com.lab126.powerd battLevelChanged 100
[Fri Oct 18 11:21:22 EEST 2019] com.lab126.powerd goingToScreenSaver 3

I'm attaching also KUAL extension to enable the script. It'll run until the restart, creates the log in battery.log file in the root folder.

Changelog:

Spoiler:

• battstat_1.3.zip - add autostart option
• battstat_1.2.zip - add more logged events
• battstat_1.1.zip - move log to /var/local
• battstat.zip - initial version

[hius07]

Thank you for sharing.
Have you found anything interesting in your log that caused battery drain?

[MrTick]

Originally Posted by hius07

Thank you for sharing.
Have you found anything interesting in your log that caused battery drain?

I'm monitoring it for less than an hour, so nothing yet

[knc1]

Put your log file in /var/local/your-choice.

That is persistent "user data" for the Kindle system and untouched by the activities of the USB sub-system.

[MrTick]

Originally Posted by knc1

Put your log file in /var/local/your-choice.

That is persistent "user data" for the Kindle system and untouched by the activities of the USB sub-system.

Thanks for the tip.
The idea was to have easy access to the log files without the need of using usbNetwork.
The improvement is as follows: now the log is stored in /var/local and can be easily obtained via KUAL menu

EDIT: I can't edit the first post, so I'm adding new attachment here.

[knc1]

Originally Posted by MrTick

Thanks for the tip.
The idea was to have easy access to the log files without the need of using usbNetwork.
The improvement is as follows: now the log is stored in /var/local and can be easily obtained via KUAL menu

EDIT: I can't edit the first post, so I'm adding new attachment here.

Sounds good.

It will take a "few" (unknown number) of posts before this system will give you full access.
Just keep on posting, the system will wake up 'soon'.

[hius07]

Will it be useful to add monitoring wirelessEnableChanged event?

More events mentioned I've seen here
https://www.mobileread.com/forums/sh...d.php?t=227859

[MrTick]

Originally Posted by hius07

Will it be useful to add monitoring wirelessEnableChanged event?

It should be easy to modify the script to log any event you want.
Just add the correct event source (separated by /n) to the SOURCES variable and include the event in the lipc-wait event list.

You can also monitor all events in the system, but that might cause exessive flash wear:

lipc-probe -l | lipc-wait-event -m -l "*" | while read event; do
	echo [`date`] $event > /mnt/us/events.log
	done

[MrTick]

So I've done some measurements, it seems that the battery is quite dead (all measurements were done with frontlight set to 3)

Grey zones are times where PW entered 'suspended' state.
Similar green zones for charging.



It lasted a little more than a day on a single charge.
I've replaced the battery situation improved instantly, so it'll take some time before I discharge it fully and attach a new plot

Dirty python script to generate plot from battery.log attached (python2+matplotlib)

[knc1]

Is that your PW1 or PW4? (Your PW1, but future readers may not realize that.)
Also the firmware version in use please.

That is a very pretty little chart.

As you wrote, the old battery is almost a straight line downward, regardless if the device is asleep or awake.
That old battery would probably discharge in less than a day just sitting on a shelf.

[MrTick]

Originally Posted by knc1

Is that your PW1 or PW4? (Your PW1, but future readers may not realize that.)
Also the firmware version in use please.

PW1 running the most recent 5.6.1.1

[Junket]

Nice idea and chart. Thanks for sharing this.

As to being able to edit your older posts, I believe it's > 20 posts and definitely < 53 posts before the forum settings will allow such. As you might gather, I didn't notice exactly when the transition occurred.

[MrTick]

Originally Posted by Junket

As to being able to edit your older posts, I believe it's > 20 posts and definitely < 53 posts before the forum settings will allow such. As you might gather, I didn't notice exactly when the transition occurred.

I think it's exactly 10 posts, as I can already edit my posts for some time
(BTW. Added a little-improved version 1.2 that gather also suspend events)

[NiLuJe]

Just throwing this out there:

While that may be frowned upon in other subforums (as I can't speak for other mods), feel free to PM me if you need an edit on an earlier post .

Or a thread title, because no amount of posting will ever allow you to edit your own thread's title :/.

(Yes, that last one used to drive me mad ^^).

[tiandongxv]

Originally Posted by MrTick

So I've done some measurements, it seems that the battery is quite dead (all measurements were done with frontlight set to 3)



Grey zones are times where PW entered 'suspended' state.

Similar green zones for charging.







It lasted a little more than a day on a single charge.

I've replaced the battery situation improved instantly, so it'll take some time before I discharge it fully and attach a new plot



Dirty python script to generate plot from battery.log attached (python2+matplotlib)

Can this script run on Kindle?