Quote:
Originally Posted by avhm
I spent a while improving this script for the Kindle PW2 - Better consistency of hitting the schedule, and much improved power management.
I was having issues with Kuhno92's version (high power consumption) and 64bits fork (wouldn't keep schedule) - This version fixes both of those issues.
This should work on almost all supported kindles (it tries to detect which power management process to use) but I've only tested it on PW2, so add an issue if it's failing on your device.
If you try it out, let me know how you get on
Link: https://github.com/avhm/onlinescreensaverPW2 |
Man, so close! I've been struggling with my Kindle Basic (2014) / 7th Gen Kindle, and seemingly like many people, the goal is to get a "live" Home Assistant on the ultra-low-power e-ink display I already have vs. buying something new. Not much a Kindle user, so this is an excellent use for a forgotten device.
Day 1 with an earlier version of the extension: refreshes properly, but never seems to go to Suspend - battery died in a day.
Day 2 with this version and a reboot: refreshed once, but then static all day - ended the day with 94% battery.
Checking the logs, it looks like it failed to get network "up" while it was testing. It seems like Kindle OS's timeout (duration it says in "ready to suspend") is shorter than the time the script gives for network-up checking, so the script ends up "forgetting" to set a new future wake time before the OS kicks it to perma-sleep.
Two thoughts here:
1) Shorten the network-up wait time so that, in case of failure, it doesn't lose the opportunity to schedule its next wake.
2) Stop disabling WiFi at all - the OS should be able to handle that in suspend. Could prevent confusion and mistakes on enabling network in early wakeup.
Actually indeed wondering why we disable WiFi at all. The Kindle has good battery life with WiFi enabled all the time - shouldn't we trust its power management?
I might try playing with these ideas in the meantime.