View Single Post
Old 09-05-2019, 05:27 AM   #19
Frenzie
Wizard
Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.Frenzie ought to be getting tired of karma fortunes by now.
 
Posts: 1,754
Karma: 730681
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
Quote:
Originally Posted by davidfor View Post
As this conversation started from a comment about scheduling a wake-up to do a sync, then if it is obviously possible to schedule a wake-on on the Kobo. How it is done, I have no idea, but, I doubt it is a "wacky non-standard way".
I specified precisely why I didn't think it was possible here, so "obviously" the past tense was referring to the time before the beginning of the conversation.

My H2O has a wacky non-standard implementation of the Linux touch protocol, and the framebuffer is wacky too. This is true of many Kobos to some degree. If the H2O has a method to schedule wake-ups, it's not one specified by the Linux kernel docs. It's therefore non-standard by definition. Whether it's wacky is in the eye of the beholder, but as long as the standard methods aren't practically unusable even a superior non-standard implementation is wacky by default.

Quote:
Originally Posted by baskerville View Post
I can do that, on the Glo HD, by writing a Unix Epoch to /sys/class/rtc/rtc0/wakealarm.
Not on H2O, but it's interesting to know that it's not just 2013-era devices running older firmware on which that works.
Frenzie is offline   Reply With Quote