You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please move next_wakeup_secs method to local directory for user/kindles (like fetch-dashboard.sh that cannot use next-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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: