You can pause devices or folders. Paused folders don’t watch, scan or hash. Paused devices don’t get connected. If you only pause the remote devices, hashing will in fact continue. Just don’t let it stop the service completely, as advised earlier. My suggestion could help automate this pausing / not connecting to devices instead of having to push the GUI button.
once again, the opposite of what i was trying to achieve.
Apologies for being unclear once again.
I want it to keep hashing and i want it to allow me to edit the configuration when it is not connected.
I do not know how to explain better or what is the cause of the confusion, so let me add some extra information:
I had to leave but I was being kept “babysitting” the thing because if i left i could not edit the configuration unless i went online and i did not want to waste phone bandwidth, but i still wanted to finish setting up the ignores and i wanted to let it finish hashing the 600 GB of data it was hashing.
If i left then it would disconnect from the home wi-fi and it would stop syncing (correct and desired outcome)
BUT ALSO
The phone would not keep hashing the 600GB directory (Undersired. This takes a few hours so i do not see why it could not hash it while i was doing other stuff) and it would not allow me to edit the configuration (undesired, i still needed to finish setting up details about the share and there were things i did not want for it to waste time syncing, plus i needed to acclimatize myself with the android service so i wanted to know how the GUI operated and where were all the commands, something which the FAQ and the WIKI are extremely lacking i found out, as it jumps from complete novice user level to “here is how to operate it via commandline” and completely disregards most of the GUI. While i could set up a commandline app on the phone i honestly did not wish to start learning android commandline stuff just to use syncthing)
I would say that what was suggested above in https://forum.syncthing.net/t/trying-to-understand-what-is-happening/20629/19 by @acolomb about using allowedNetworks should do just that. If you limit Syncthing to use only local networks, then devices will not be able to connect outside of them, meaning that Syncthing won’t use any data (almost, as it still will connect to global discovery, etc.). However, the Android app (wrapper) and Syncthing (service) will both keep running, detecting new changes in folders, and scanning and hashing them.
Basically, the idea is to allow the app to run all the time and use the Web GUI to configure the advanced allowedNetworks option which will limit Syncthing to local networks only.
I think I did understand exactly what you’re trying to achieve, both times when you assumed the opposite. Maybe I didn’t make the suggestion clear enough. Agreed, the docs are very lacking with regards to the GUI and how it works. It’s a large undertaking and any help is very welcome there. It’s rather easy editing the documentation source files, what would be most helpful though is a way to automate taking screenshots for the GUI docs.
Back to the problem at hand. Just try it:
-
When leaving home, disable mobile networking just to be sure it doesn’t eat through data.
-
Enable Syncthing (the app) to run even when not on Wi-Fi.
-
Pause all devices on the Android app. Easiest by accessing the Web GUI from the left slide-out menu.
-
Reactivate your mobile network connection.
-
Syncthing will be scanning and the GUI accessible, but it will not connect to the other (paused) devices.
-
Resume all devices within the GUI once you are back at home and connected to the Wi-Fi.
The mentioned option can help by not requiring you to manually pause and resume the devices. Steps 1 and 4 can be skipped if you do step 3 while still at home.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.