-
Notifications
You must be signed in to change notification settings - Fork 96
Info on battery optimization and settings affecting battery usage
Catfriend1 edited this page Jul 11, 2019
·
11 revisions
First things first:
- Syncthing-Fork requires to be exempted from doze which is asked during the welcome wizard. The app will cease to function if the permission is revoked.
- The app doesn't require the permission to "waste" your battery and the app doesn't use it to set wakelocks. It does run a reliable so called "Android foreground service".
- Technically speaking, it's required to avoid database corruption in case Android can't communicate with the SyncthingNative before putting the app and SyncthingNative in suspend.
Here is how you can reduce battery usage even further by optimizing Syncthing's settings:
- If you've configured your Syncthing instances to connect using static IP addresses, turn off all discovery options: Go to "App/Settings/Syncthing Options" and disable "Local discovery", "Global discovery", "NAT Traversal" and "Relay".
- If you've configured your Syncthing instances to connect devices which are located on the same local network, turn off global discovery and relay options: Go to "App/Settings/Syncthing Options" and disable "Global discovery", "NAT Traversal" and "Relay".
- If you don't need your changes immediately synced between devices and can wait for up to an hour until the changes are synced, go to "App/Settings/Run conditions" and check "Sync every hour for 5 minutes". The app will then stay in the background showing its notification all time but will only do its work in "5-minute-time-windows" every hour. This will save a lot of battery but practically require an always-on device on the other side.
Short summary:
-
Optimize for better battery life
-
Optimize for faster sync with less need of "caretaking" at the cost of battery
Useful reading: