Syncthing-Fork v2 uses far too much battery over v1

I too am seeing greatly increased battery usage, and I also have a Pixel (6a) running Android 16.

I was previously running Catfriend1’s Syncthing-fork (GitHub build) v1.29.6.4 and had no noticeable battery usage. I recently upgraded to 2.0.10.1 and it now routinely uses ~10% of the overall battery every 4 hours. When the phone is otherwise idle, it shows as 80-90% of the battery usage! (note, that’s relative to the battery used in each two-hour period)

I am likely going to downgrade using my previous backup but I’m willing to provide logs or try experiments if it will help.

1 Like

Yesterday, I started syncing ~65 GB of data to my computer from my phone, and my phone got really warm, and its battery drained rather fast, and that was fine. It made sense, I think. I can confirm it was Syncthing, the “Device care” section of Settings confirmed that.

But at some point Syncthing started using a lot of RAM, making my phone unusable until either I stopped Syncthing, or it would crash after it got to 3GB

And I can’t tell if the app just ran into a particularly large file I’m not aware of or if there is actually a bug

Same issue here, with all the typical methods to reduce the drain already tried.

I’m on Google Pixel 6 (Pro) running Android 16 as well.

I tested wrapper v1.30.0.4-fdroid with native v2.0.1 and that has the battery drain as well. This means it’s most likely an issue with native.

4 Likes

Aren’t there any logs of what Syncthing is actually doing when consuming so much battery? It’s gonna be impossible to tackle without more data. It also seems related to Pixel phones + Android 16? Or are there other devices affected too?

Galaxy S21 FE (Android 15), no issues. Syncthing 2.0.9 (The Google Play release, though, by nel0x).

2 Likes

We already know that the issue isn’t connected to the wrapper but propably lies within syncthing itself. So what phones and Android versions do you actually use, guys? Maybe there is a connection, since we already have three Pixel phones lined up …

Have battery issues

melusine: Pixel 6 Android 16

@m11kkaa:

@achilleas:

pdc1: Pixel 6a Android 16

@akirapink:

lard0101: Pixel 6 Pro Android 16

No issues

@Catfriend1:

@tomasz86:

@marbens:

@sektor2sync:

er-pa: Galaxy S21 FE

1 Like

Hi everyone,

Sorry in advance for my english level :sweat_smile:

I’m using Syncthing between 3 devices since 3 months :

  • Android (Pixel 8, GrapheneOS, Android 16, Syncthing v2.0.10) → Personal laptop (Ubuntu, Syncthing v1.30.0)
  • Android → Professional laptop (Windows 11, Syncthing v1.30.0)

Settings & usage :

  • Only in Wifi
  • Sync only for my Obsidian folder (several kbytes of data each day).

It works fine but same issue of battery drain since the beginning of my setup.

For example : 52% of battery consumed between 8 am and 12pm today… (80 % to 69 %)

Thanks in advance for your help !

Pixel 8 with stock Android 16 is where I have battery drain.

https://www.reddit.com/r/GooglePixel/comments/1n5knvq/battery_megathread_september_2025/

Just putting it out there, there are many complaints about battery-drainage and battery-protection functionality mot working related to Android 16 or Google Pixel.

But yeah, as said before, more info would be helpful.

If it helps, my phone isn’t a Google Pixel, but a Samsung Galaxy A54

1 Like

Pixel 7a, Android 16.

I use a Fairphone 4 with /e/ os based on Android 14. The only “non standard” I’ve configured is to disable NAT traversal, global search and forwarding since I only need to access local devices.

OK for now there are six Pixel phones and one Samsung phone reporting battery drain. No drain on Samsung (as well), Xiaomi, Fairphone … So maybe not (?) just Pixel specific?

My linked reddit post was covering a Pixel as well though. :frowning:

Thanks, I did not know that. I had also noticed a general degradation regarding battery life on my Pixel but nothing that serious (as seen on your reddit post). All I know is when I stop syncthing-fork or disconnect wifi (which does the same for me), the biggest contributor to battery drain is gone.

Can you please give us instructions on what you need and how to get it? Sadly I am not a developer …

1 Like

Nobody else in this thread has said they tried this, and there are changes made to NAT traversal in v2:

  1. feat(connections, nat): add UDP portmapping/pinhole for QUIC (fixes #7403) by marbens-arch · Pull Request #10171 · syncthing/syncthing · GitHub
  2. fix(beacon, osutil, upnp): fix local discovery send and intf detection on Android by Catfriend1 · Pull Request #10196 · syncthing/syncthing · GitHub
  3. https://github.com/syncthing/syncthing/pull/10204
  4. https://github.com/syncthing/syncthing/pull/10211
  5. chore(config): remove fallback STUN servers that are CNAMEs to stun.counterpath.com by marbens-arch · Pull Request #10219 · syncthing/syncthing · GitHub

I’d be interested in seeing the effect of disabling NAT traversal for people with the problem.

1 Like

Pixel 5, Android 16

1 Like

I will try that and report back but I think this setting was enabled by default on syncthing v1 as well. At least on my phone.

Interesting, so you have no problems on your Pixel phone …

I don’t really notice any difference in battery consumption since I disabled the setting. It’s still far too high. :frowning:

1 Like

Can’t really say what to look for exactly. But if Synching is draining as much energy as some here indicate, then it must do something - I’d say. So the logs may indicate what’s going on. I’m no expert when it comes to the mobile version, but usually with some traces enabled, the logs are quite useful.

It may be worth checking. In an idle state there usually isn’t too much happening, at least not continuesly.

syncthing fork v2.0.10.1 (fdroid) android 15 (not google pixel).

~10 folders. No battery drain

2 Likes

I don’t know when this started but I only noticed it now: My phone is having trouble reading from its SD card when Syncthing is running…

…But it seems to be because of resource starvation, as opposed to a mechanical failure, because when I stop Syncthing, it functions normally again