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
I would like to be able to configure the sync cycle duration to run until the sync is complete or a maximum time limit is reached. This is useful because I want the sync cycle to be as short as possible to save battery but I also want it to be as long as it needs to to get a full sync.
For example, I would like to be able to configure the sync cycle to run for at most 5 minutes and expect the following behavior:
If the sync completes in 1 minute the sync cycle ends.
If the sync does not complete in 5 minutes, the sync cycle is interrupted.
This might be how the setting already works in which case it just needs to be documented.
The text was updated successfully, but these errors were encountered:
e00E
changed the title
Make time schedule based sync cylce end early
Allow time schedule based sync cylce end early
Jan 16, 2023
e00E
changed the title
Allow time schedule based sync cylce end early
Allow time schedule based sync cycle end early
Jan 16, 2023
Instead of turning sync on and off purely based on time, it could be better to keep sync on for N minutes after last change - either pulled from other devices or on the device. After N minutes of inactivity, start checking periodically: turn on for X minutes, turn off for Y minutes. On pull or file change, back to being on for N minutes.
That way the app won't turn off while files are being synced, battery is saved, the behavior is more configurable and consistent
I would like to be able to configure the sync cycle duration to run until the sync is complete or a maximum time limit is reached. This is useful because I want the sync cycle to be as short as possible to save battery but I also want it to be as long as it needs to to get a full sync.
For example, I would like to be able to configure the sync cycle to run for at most 5 minutes and expect the following behavior:
This might be how the setting already works in which case it just needs to be documented.
The text was updated successfully, but these errors were encountered: