View Single Post
Old 11-22-2013, 01:49 PM   #68
z000ao8q
Connoisseur
z000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toysz000ao8q shares his or her toys
 
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
hello,
which firmware do you have?
perhaps downgrading to 2.6.35.3-850 and firmware 2.5. would work - thats mine.

Crond: the app was there only crontab-file was missing. but it could be created with crontab -e

rtcwake: mine was compiled back then for the 2.5 binaries. i donīt know if it can work with the newer firmware

how do you know that it does not wake up/ how do you test it?
when you are in terminal, the connection is lost during the progress so you can't recognize.

I would test with one little .sh
- echo timestamp into log-file
- trigger rtcwake
- echo timestamp into log-file

this should work actually.

I have to revise my guide. I found the crond not to work reliable. due to time shifts if the internal clock, the timing was not good.
I am now sending the sleep out of the main update.sh again, right after the processing is done.
So basically a kind of endless-loop. works very stable.


by the way: the batterie lasts for 1 month with 12 wake ups per day.
z000ao8q is offline   Reply With Quote