Syncthing-Fork v2 uses far too much battery over v1

Support Android
68

Update: Today battery consumption is at 54% (00:00-19:00). Looks like the issue is not fixed for my setup. :anguished_face:

69

I had a similar experience as @George_Hi the other day when I did a change in Syncthing (I removed a stale node that is likely to never come back online again). On that day battery consumption was back to 1.x amounts - but the next day the enormous consumption returned.

70

I got the update to 2.0.11.1 via F-Droid now and it doesn’t seem to help unfortunately.

2 Likes
71

I did another “fresh start” test with the latest release. Battery consumption seemed better at first but went up again, unfortunately. Please find the log files below.

  • com.github.catfriend1.syncthingfork_release_v2.0.11.2_arm64-v8a.apk Pixel 6 Android 16 QPDR1, Stock OS
  • syncthing 2.0.11-1 Arch Linux (Desktop PC)
  • new configs, one newly shared folder

syncthing.log (21.2 KB)

android.log (277 Bytes)

2 Likes
72

I asked a friend of mine to install syncthing-fork on his Pixel 6 with GrapheneOS’s Android 16 via F-Droid. (Reminder: I have the same phone but with stock Android 16.)

He did not configure anything (no connections) but was mostly on WiFi. And as we know:

His battery consumption over 10,5 hours was at 2 %. The problem seems to be specifically Google’s Android on Pixel phones combined with syncthing V2.

1 Like
73

This might have something to do with periodic database maintenance.

You can try setting STDBMAINTENANCEINTERVAL=999999h in Troubleshooting → Environment variables to set the interval to about 111 years (practically never).

74

I pasted this expression in the setting you mention, but it does not help for me, unfortunately. Thanks though!

1 Like
75

Same for me

76

Thank you for this information. Unfortunately it did not help to fix the drain of the battery issue (syncthing-fork 2.0.11.2 on Pixel 8 with Android)

1 Like
77

Today I have got this Android-Protocol:

15:12:091/DisplayManager Choreographer implicitly registered for the refresh rate.

15:12:09E/ashmem Pinning is deprecated since Android Q. Please use trim or other methods.

Maybe this helps to debug the battery issue.

Also I noticed, that something activated the “running in background” option, which I deactivaed to stop the annoying draining of the battery.

78

Hi there, unfortunately, the battery issue is still not fixed. version: v2.0.11.3 (Android 16 on Pixel 8)

79

I created an account just for this reply, so far: I also have huge battery drain (according to the system ~40% usage).

I am a Fairphone user with Fairphone OS and Android 15. My device is rooted.

I already tried reducing the num connections to 1. Using Syncthing with 4 devices, while one of them is my server all othet 3 devices sync to, basically.

Edit: Oh and I installed synthing-fork v2.0.11.3 via F-Droid.

80

As far as I know this version contains the same syncthing 2.0.11 release and therefore is not expected to change battery behavior. We believe that the Syncthing-Fork wrapper has nothing to do with the actual problem since the problem also exists when running syncthing via termux.

81

Today I see battery drain even with “force stop” option enabled. syncthing-fork v2.0.11.2

82

I recently started using pixel 9a and just noticed ~35% battery usage, compared to ~2% on my galaxy s20 5g. They are both using syncthing-fork v2.

As a temporary measure, I’ve disabled unrestricted background battery usage of syncthing-fork. Hopefully it can make a difference.

I also just noticed that the syncthing-fork repo was transferred to a person who only joined github 3 weeks ago and is very suspicious (check out status ¡ Issue #16 ¡ researchxxl/syncthing-android ¡ GitHub).