06-08-2013, 06:31 AM | #46 | |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
yes, I found it. thanks.
I will test with the following lines being commented out... Quote:
|
|
06-09-2013, 01:57 PM | #47 |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
what happens after the standby?
when I have WiFi and Telnet working and I am triggering the RTCWAKE command (which seems to work), do I need to reinitialize everything again after the wakeup - or should it work without doing anything? If the answer is "everything should still work" then it might not work in my test yet because I cant reconnect telnet |
Advert | |
|
06-09-2013, 03:04 PM | #48 | |
Enthusiast
Posts: 39
Karma: 454
Join Date: Jul 2012
Location: Brussels
Device: Kobo Touch
|
Quote:
|
|
06-10-2013, 09:04 AM | #49 |
Member
Posts: 12
Karma: 9172
Join Date: Apr 2013
Device: Kobo Touch
|
nice to know
ha, just figured out:
the kobo will not sleep when you have it plugged to usb (usb network, ssh session). So rtcwake IS working, it was my mistake. |
06-10-2013, 09:35 AM | #50 |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
on my Mini the RTCWAKE did work to set it to sleep - only the wakeup did not.
As Sven posted, everything should be there again. on my side, I could not connect to telnet unless I rebooted the Mini. I will try a little more today... |
Advert | |
|
06-10-2013, 11:28 PM | #51 | |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
it seems to work :-)
but only with re-init of Wifi. I am running my test.sh in background with "nohup ./test.sh" Quote:
need to do some more tweaking but looks promising :-) |
|
06-15-2013, 02:20 PM | #52 | |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
Hello,
just a happy update. It seems to work for me - even so I still need to run it for several days to test stability and runtime. Basic idea:
this is how my update.sh looks like (which is executed by cron) Quote:
Last edited by z000ao8q; 06-16-2013 at 01:42 PM. |
|
06-27-2013, 03:34 PM | #53 | |||
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
wakeup with seconds works perfectly - but using a time it is behaving strange.
hwclock is UCT: Thu Jun 27 19:20:31 2013 0.000000 seconds I try:date (system time) is local: Thu Jun 27 21:20:52 CEST 2013 Quote:
Thu Jun 27 21:13:45 CEST 2013 no wakeupwakeup from "mem" at Thu Jun 27 21:14:15 2013 Quote:
wakeup from "mem" at Thu Jun 27 21:14:15 2013 but also no wakeupmy assumption: rtcwake is using the hwclock but when I adjust the system time backwards with hwclock -s -l (instead of -s -u like in rcS): hwclock is UTC: Thu Jun 27 19:29:48 2013 0.000000 seconds Then I executedate is: Thu Jun 27 19:30:16 CEST 2013 Quote:
Thu Jun 27 19:29:03 CEST 2013 and yes - a wakeupwakeup from "mem" at Thu Jun 27 19:29:33 2013 seems to work - but now the issue is, that cron does not work anymore because it is using the system time -which is now 2hrs off any idea? |
|||
06-28-2013, 04:55 AM | #54 |
Pain in the arse
Posts: 758
Karma: 77856
Join Date: Apr 2013
Device: Kobo Aura One, Kindle 4
|
let timestp -= 120 ?
|
06-28-2013, 05:02 AM | #55 |
Pain in the arse
Posts: 758
Karma: 77856
Join Date: Apr 2013
Device: Kobo Aura One, Kindle 4
|
Or
date -u +%s Or man date man hwclock |
06-28-2013, 04:19 PM | #56 | ||
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
I guess you did not try your answer before :-)
+%s obviously always outputs the utc format, no matter what additional parameter Quote:
If i am right, the implementation of rtcwake has an issue. it compares against the local system time Quote:
I changed the timezone now to UTC so I only have one time for all clocks now. now it works - finally |
||
06-29-2013, 10:18 AM | #57 |
Groupie
Posts: 199
Karma: 1071756
Join Date: Sep 2012
Location: Nova Scotia
Device: Kobo Aura, Nexus 5x
|
er, ALL the unix/linux man pages are in numerous places on the Internet
|
07-04-2013, 05:42 AM | #58 |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
a little update:
its running now stable sincs several days with 13 2min wakeups per day. I am relying on the battery-percentage values of the kobo and the consumption of the mode "mem" (suspend-to-ram) seems to be ~3,5% per day. this would give a runtime of around 1 month on a single charge. I want to test the disk-mode next to see if it brings more value... |
07-29-2013, 12:25 PM | #59 |
Member
Posts: 15
Karma: 10
Join Date: Jul 2013
Device: Kobo
|
Hi all,
maybe I missed somthing, but I get the same error: rtcwake: /dev/rtc0 not enabled for wakeup events can I "enable" it!? |
07-30-2013, 05:06 AM | #60 |
Connoisseur
Posts: 51
Karma: 5942
Join Date: May 2013
Device: kobo mini
|
Hello,
you need a tweaked version of the rtcwake command. I still need to post it here. hope that I can do it today or tomorrow... |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Glo How to import reading Life Statistics from Kobo Touch to Kobo Glo? | the_m | Kobo Reader | 5 | 12-13-2012 03:40 PM |
$25 gift card w. purchase of Kobo Touch or Kobo Vox at Frys | sufue | Deals and Resources (No Self-Promotion or Affiliate Links) | 0 | 07-15-2012 10:39 AM |
Touch Kobo Touch defective after 3 months and Kobo Customer Support useless | shaf | Kobo Reader | 5 | 12-04-2011 05:10 PM |
Touch Kobo Touch not ejecting cleanly with Calibre OR Kobo Desktop - Windows 7 | JBlyth | Kobo Reader | 11 | 08-03-2011 05:38 PM |
Kobo Touch not disconnecting properly from Calibre OR Kobo Desktop - Windows 7 | JBlyth | Devices | 1 | 08-03-2011 06:50 AM |