Yes, definitely. Just wanted to point out the difference between iOS and macOS (Synctrain runs on both) here.
In case I missed it, but a huge thank you to @Tert0 for sitting down and bisecting the offending commit ![]()
This is awesome, thanks all
I am one of the original reporters. Any idea when would this be released in github as a regular release (not super clear which github repository to monitor)
As weāve missed the RC by a few days, the change will probably be part of v2.0.14. But that doesnāt mean that much as the mobile clients are free to ship patched binaries.
You gotta monitor Martchus syncthing tray or researchxxl syncthing android release notes, match the release notes with syncthing/syncthing release note. Only use one of them, it is generally a bad idea having two app changing one database of syncthing.
Found and installed this one yesterday
ā¦Fix the high battery drain if local discovery is in use (thanks @bt90)ā¦
Iāve also created a development build of Syncthing Tray for Android with fix(beacon): skip point-to-point interfaces on Android by bt90 Ā· Pull Request #10504 Ā· syncthing/syncthing Ā· GitHub backported. (This build also has a few other changes, most notable use of Expanded Client Areas and Safe Areas enabled.) You can download it from my build server if you want to help testing.
(I havenāt read all the changes and recommendations for low resources usage that are suggested here, pardon my assumptions)
I understand tuning connection number to 1 and other settings for low resources tuning as default for mobile version is good
(without needing to set it up all the time after setup, but this will make the code diverge ig, if the default in desktop is not for low resources, or its already that?)
- Are the commits from this update only addressed multicast or local discovery as disabled for mobile release, or is it good to make the settings for mobile release shipped in default state for low resources tuning, while desktop is with normal tuning, and high resources tuning left as non-default?
- Does mobile version still connect to desktop with LAN connection over the same WiFi connection even if local discovery is disabled with this update?
(This is useful to conserve limited mobile data, connect 2 devices over LAN with cellular data turned on, disable cellular data, then 2 devices transfer P2P without using internet over LAN connection [fallback method in case unlimited WiFi plan is discontinued],
- maybe making two release version one for with local discovery, the other without is too much more code and compile time added?) (Is my assumption wrong?)
I wanted to know this before I upgrade. Iām open to technical explanations, and sorry for the long questions, I only follow this now, I didnāt follow this since late 2025.
Edit 1:
- Is it a good idea to push this to stable or should I just use the development build of syncthing tray?
Update for syncthing-fork is live on f-droid ![]()
I updated to 2.1.0 and my pixel complained about battery usage. I decided to rollback
Anybody else?
No
Alright, my turn to give my 2 cents.
Context
- Iām on a Pixel 10 Pro XL, GrapheneOS (not stock Android)
- Running Syncthing v2.0.11.1 (installed via Aurora Store)
- Having issues with battery (no meaningful numbers from my phone, but I can tell things are wrong, battery went from 39% to 9% overnight (within 9h), Syncthing is shown as top-1 offender
- Iāve read the whole thread
Current understanding:
- Syncthing-Fork released v2.0.14.2 which supposedly fixes this
-
Fix the high battery drain if local discovery is in use (thanks @bt90)
-
- Disabling Local Discovery seem to heavily improve battery life (multiple reports above seem to confirm that, and the v2.0.14.2 fix explicitely mentions it)
- Doc Global Discovery
- Doc Local Discovery
How to fix
- If your store provides v2.0.14.2 update (or above) => just upgrade Syncthing-Fork
- If your store doesnāt => disable Local Discovery
- If disabling Local Discovery doesnāt work for you (depends on custom setup) => noc documented solution (yet)
In my case, Aurora Store doesnāt provide a version above v2.0.11.1, Iāll uninstall Syncthing-Fork and reinstall it using F-Droid (current release there is v2.1.0.0).
Tip : If you have to uninstall/reinstall, make sure to export your Syncthing settings first.
Donāt hesitate to correct me if I got anything wrong.