You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if someone manually suspends the system, nothing will ensure that autosuspend has set the next alarm to wake up the system. Thus, activities might be missed.
The existing systemd integration has to be change to call a special-purpose command that handles manual suspends by adding the wake up logic.
The text was updated successfully, but these errors were encountered:
I propose to completely remove the current wakeup handling and instead add a systemd service that runs whenever the system goes to sleep. When this service runs, autosuspend can check which is the next wakeup event and schedule it.
@nioncode I have rebase the old branch to be up to date with the master changes. I will not be able to remove the complete wakeup handling from the main checking loop though, because I do not want to trigger a suspend in case the system has to wake up again in just a few seconds (a configurable delta).
Currently, if someone manually suspends the system, nothing will ensure that autosuspend has set the next alarm to wake up the system. Thus, activities might be missed.
The existing systemd integration has to be change to call a special-purpose command that handles manual suspends by adding the wake up logic.
The text was updated successfully, but these errors were encountered: