Syncthing-fork on Android uses lots of battery

I installed syncthing-fork on my Pixel 8 (Android 15, latest, syncthing-fork 1.29.0/android/64-bit ARM) a few weeks ago, and when it runs I see significant battery drain, like 20%+ of my drain is due to syncthing-fork; I run out in 18-20 hours rather than the 2 days I got before.

I’m syncing 3 folders, a few MB (44MB in the biggest), infrequent changes, and 6 total devices, of which 3 are typically offline. I’m on home Wifi most of the time.

Run conditions: all on (wifi & mobile, AC & battery, respect battery saving, no time-schedule. All folders have “Watch for changes” enabled and nothing else.

What should I check to see what’s causing the drain? Everyone says syncthing-fork is supposed to be pretty good but I can’t use it like this.

One specific question: if “Run according to time schedule” is un-checked, are the settings below it ignored? (Those are “Duration of sync cycle” and “Duration of sync pause interval”.)

I did check the individual folders: none of them has any “Custom sync conditions”.

I guess what I’m looking for is for it to not use battery at all when nothing’s happening, but still sync responsively when changes happen. Just wake up when a file changes locally, or a sync request comes in from another node.

Maybe it’s better to be asked in Issues of Syncthing-fork? As the name implies, it’s not official project.

It’s perfectly fine to ask questions about it on this forum. The name was always… something :slight_smile: Questions were already welcome before, and now that it’s the only android syncthing wrapper even more so.

Edit: Just to avoid a wrong impression: I am not complaining about the -fork name. I don’t think it’s particularly nice or helpful, but it’s naming - it’s really, really hard, I wouldn’t want to know what I’d have chosen :stuck_out_tongue:

2 Likes

I have Syncthing-Fork Wrapper v1.28.1.1 (Syncthing v1.28.1) and have absolutely no untoward processor usage at all (usually 0.0%).

2 Likes

I had the same issue and was instructed to disable global discovery and relays, which helped a lot to reduce the increased battery drain I started seeing with 1.29.0. The two patch versions helped, as well.