Closed matopeto closed 2 years ago
Hey thanks for the suggestion, that makes sense :-) If you can send a PR that would be great. If not I'll look into this myself later.
For the Kindle DXG you could probably compile the next-wakeup
binary for armv5te
. Not 100% sure, but the CPU seems to be ARM5 compatible so it might work. But indeed if all you need is a hardcoded interval then it's overkill.
Btw should you need a quickfix then you can replace the next-wakeup binary by an executable shell script, something like this:
#!/usr/bin/env sh
echo 3600 # or whatever interval you like
@pascalw nice workaround without changing dash.sh
:) and without compile custom binaries
My use case with my DXG is use it as the photo frame. DXG is without connectivity, so i similarly replace wait_for_wifi :)
So i am closing this issue :) Thanks :)
Please move
next_wakeup_secs
method tolocal
directory for user/kindles (likefetch-dashboard.sh
that cannot usenext-wakeup
binnary (eg. my kindle DXG). So users can implement own logick for next wakeup (e.g. hadcoded interval)Maybe i will post PR for this issue later