Yes I saw the his app albeit just after I tried this approach.
Looks like he is using the systemd timer approach. Seems like hes escalating privileges with a helper utility.
In contrast I guess using a daemon could have the benefit of letting multiple programs schedule wake-ups in an unified manner.
For example the alarms from the clock and events from the calendar etc. maybe even build a system for permissions, which apps are allowed to wake up the phone in the long run.
For now I changed it to run as a service via systemd and use the system bus in dbus. I added PKGBUILDs to the repo to ease up the installation if someone wants to try.
The service needs to be started/enabled via
But be warned it's very janky.
1. That gnome-clocks version doesn't remove registered wake-ups when you delete or deactivate an alarm
2. waked atm only reschedules the next wake-up if called from outside. (Which that gnome-clocks version does minutely if running and at least one active alarm present when an alarm fires or gets changed otherwise)
3. waked forgets all registered alarm on reboot or if the service gets restarted one way or another
4. don't know if it plays nicely if systemd timers (or other stuff managing rtc wake-ups) are present.
Edit1: updated gnome-clocks-waked
Looks like he is using the systemd timer approach. Seems like hes escalating privileges with a helper utility.
In contrast I guess using a daemon could have the benefit of letting multiple programs schedule wake-ups in an unified manner.
For example the alarms from the clock and events from the calendar etc. maybe even build a system for permissions, which apps are allowed to wake up the phone in the long run.
For now I changed it to run as a service via systemd and use the system bus in dbus. I added PKGBUILDs to the repo to ease up the installation if someone wants to try.
The service needs to be started/enabled via
Code:
systemctl enable waked
# then reboot or
systemctl start waked1. That gnome-clocks version doesn't remove registered wake-ups when you delete or deactivate an alarm
2. waked atm only reschedules the next wake-up if called from outside. (Which that gnome-clocks version does minutely if running and at least one active alarm present when an alarm fires or gets changed otherwise)
3. waked forgets all registered alarm on reboot or if the service gets restarted one way or another
4. don't know if it plays nicely if systemd timers (or other stuff managing rtc wake-ups) are present.
Edit1: updated gnome-clocks-waked
