Revision history [back]

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.

Is there any workaround (or fix)? Or am I totally missing something?

Thanks in advance, LVPVS

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.

Is there any workaround (or fix)? Or am I totally missing something?Edit: Converted to Wiki.

Answer: timedclient-qt5 --help has the answer.

Thanks in advance, LVPVS

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.

Answer: timedclient-qt5 --help has the answer.answer. ;)

Thanks in advance, LVPVS

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 in advance, Thanks, LVPVS

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