The most energy consuming process right now is having the Wi-fi on. This means maintaining the SSH server and constantly doing wi-fi-esque operations in the background.
The Kindle Clock project shows a way to put the device to sleep, putting it into a "deep sleep" state. Problem is of course, we have to know for how much time to sleep for beforehand.
The gist of it:
// Disable Wi-Fi
lipc-set-prop com.lab126.cmd wirelessEnable 0
// Put the device to sleep
let SLEEP_SECS=120
rtcwake -d /dev/rtc1 -m no -s $SLEEP_SECS
echo "mem" > /sys/power/state
// Enable Wi-Fi
lipc-set-prop com.lab126.cmd wirelessEnable 1
Ideas for how to implement this on this project are:
- User defined "Sleep for X minutes/hours"
- Schedules (Automatically sleep during the night)
- Define a "Refresh Rate" for the Kindle to query the server for new images, similar to how the kindle-clock works.
Ideally all three of these implementations could co-exist in the project.
The most energy consuming process right now is having the Wi-fi on. This means maintaining the SSH server and constantly doing wi-fi-esque operations in the background.
The Kindle Clock project shows a way to put the device to sleep, putting it into a "deep sleep" state. Problem is of course, we have to know for how much time to sleep for beforehand.
The gist of it:
Ideas for how to implement this on this project are:
Ideally all three of these implementations could co-exist in the project.