Allow a synced folder to bypass global run condition rules.
A use case would be to allow a folder containing small files permission to use mobile data for more timely updates.
This was already asked several times.
This cannot work as proposed, as the current run conditions start and stop the syncthing binary. So either syncthing is running, or not.
But you can use something like tasker to react to network change and (un)pause the folders that should not run on mobile data.
Any chance the last five years of development might make this feasible? I would expect that app starts or stops could first check if there were folders that had an exception?
Iād prefer it to work this way because the way it currently works, if I must enable it to be on for mobile data globally, across multiple phones thereās a good chance I forget to set a custom condition for each folder not to run. Itās much easier in my flow to opt in the folders I want to override a global preference.
Just to be clear, are you using Syncthing-Fork? The official application is no longer developed.
Thatās correct, using the Syncthing Fork for Android. Hope this is the right place.
I got here by attempting to make a new issue in Github at GitHub Ā· Where software is built and when I selected āRequest a new featureā it redirected me to this forum.
Hi,
Iāve already answered ārun conditionsā related suggestions in multiple places. In short, I am no longer interested in adding more code/complexity to the run condition monitor (the part of the app is called like this). At first it was fun improving that part - now itās a bad stomach feeling for me that those kind of ābackground conditions monitoringā is very likely to break or then end up partly working after major Android version upgrades in the future.
Weāve had this for the wifi conditionā¦ as far as I recall, one example:
Android 8 - location was necessary to get the ssid
Android 10 - the saved ssid list could no longer be read
Looking at how much work the āTasker devā or similar appsā devs put into their background condition monitoring to still work on Androidās modern ādonāt run foreground services forever, donāt waste battery, donāt hold excessive permissions the appās main purpose doesnāt requireā ecosystem like my perception is, I am not interested to do the āsameā or āsimilarā work to put this into the Syncthing-Fork app and test if it works. Costs a lot of timeā¦ sorry.
But thereās one good news: a fix is incoming these days for the remote control by intents the app already has builtin. Some users said, intents hadnāt fired due to a bug. Iāve fixed this 
. So if you need more granular run conditions, you could be able to use Tasker and similar tools again. I also recall Tasker was able to send rest api requests when I last used it years ago. That could also help pausing and unpausing folders or devices more granular instead of using the fork appās builtin options.
4 Likes
Thanks for this explanation @Catfriend1 and sorry to make you repeat. Given what youāre describing, particularly the churn in Androidās performance and security changes, I can relate to not wanting to disrupt whatās working well even if the flow could be streamlined. Carry on!
1 Like