systemd.timer not fireing when time elapses and phone in deep sleep - use timedclient-qt5 instead [duplicate]
asked 2014-09-22 12:36:38 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Hej,
I am facing a rather annoying issue and I don't know wether it is by design, or it is a simple bug.
I set up some timed services with systemd. When issuing the command in terminal: "systemctl start myservice.service", all works fine. Then I start and enable the timer, put down the phone and wait for the timer to elapse.
Here comes the issue: A) If the phone was active (i.e.: screen was on - even only the LPM screen), the timer fires and the service runs. B) If the phone was sleeping (i.e.: screen was off, phone was put down), the timer never fires.
I tried to put "WakeSystem=true" in the timer, but SailfishOS seems to be not understanding it, "systemctl status myservice.timer -l" reveals it.
Edit: Converted to Wiki.
timedclient-qt5 --help
has the answer. ;)
Thanks, LVPVS
show your config files for your timer. I have a setvice that pings google dns every 45 seconds and it wirks fine even in deep sleep.
droll ( 2014-09-22 12:46:17 +0200 )editHej,
One of the timer files is this:
And the corresponding service file:
Thank you!
LVPVS ( 2014-09-22 12:56:40 +0200 )edithow are you checking the run status of your timer?
droll ( 2014-09-22 14:10:01 +0200 )editWith these:
and
LVPVS ( 2014-09-22 14:13:03 +0200 )edithttp://www.freedesktop.org/software/systemd/man/systemd.timer.html
try using Persistent= and AccuracySec= and see if they help.
droll ( 2014-09-22 16:17:24 +0200 )edit