Syncthing-android: Syncthing not starting with read-only Folders
Using version 0.9.14 that was updated in the Google play store, Syncthing no longer successfully loads on a Samsung Galaxy S5. It displays the "Loading" screen, but then never finishes.
I've tried clearing the cache, but it is still the same. I've also tried to open with out any networks without success.
My phone is the latest Android version Samsung decided to update it to which is 6.0.1.
craycrayuk
All 17 comments
Are you using the option to start directly into web gui? Otherwise, post logs please.
Nutomic
on 21 Sep 2017
I'm having the same problem here, with a Aquaris BQ E4.5 (Android 5.0). Worked like a charm until yesterday's update, now I can't go past the "loading" screen...
joseluis245
on 21 Sep 2017
I'm not loading directly into the web GUI. Looking at the log, there is this error:
20:26:00 FATAL: failed to upgrade folder marker: remove /storage/256D-971C/DCIM/Camera/.stfolder: permission denied
I renamed the .stfolder to .stfolder2 and reopened Syncthing. This time it loaded successfully but had an error about the folder marker missing.
I closed it down again, renamed, stfolder2 and to stfolder and Syncthing successfully started.
The folder it was having difficulty with is on an external SD card.
craycrayuk
on 21 Sep 2017
Ah Syncthing is probably trying to convert .stfolder from a file to a folder (and fails because the folder is not writable). But it shouldn't prevent Syncthing from starting.
Ping @calmh
Nutomic
on 21 Sep 2017
Yeah, that would be my trophy of major fuckups.
AudriusButkevicius
on 21 Sep 2017
We should make it best effort and handle conversions when we actually start using it.
AudriusButkevicius
on 21 Sep 2017
Yeah that Fatalln should have been an Infoln.
Might want to patch that out and make an Android-only release for now or something if this is a common problem.
calmh
on 21 Sep 2017
The same problem would also appear on other platforms, if there is a folder where Syncthing can't write to.
Nutomic
on 21 Sep 2017
Atleast the error is not as hidden as it is on android.
AudriusButkevicius
on 21 Sep 2017
Also more unusual - the bug hasn鈥檛 been reported yet. Clearly we鈥檒l fix it for the next release, I just meant if you wanted a quick fix for Android.
calmh
on 21 Sep 2017
Tbh I don't think this is a very common setup on Android.
Nutomic
on 22 Sep 2017
Is there a workaround available?
Kugeleis
on 23 Sep 2017
You should be able to fix it by deleting the .stfolder file and creating a folder called .stfolder. After that, make Syncthing restart (eg by force killing the app or restarting your phone).
Nutomic
on 23 Sep 2017
That won't work I think, you'd have to manually modify the config and bump the version to skip the migration.
AudriusButkevicius
on 23 Sep 2017
I renamed the .stfolder file to .stfolder2 and reopened Syncthing. This time it loaded successfully but had an error about the folder marker missing.
I closed it down again, renamed, stfolder2 back to stfolder and Syncthing successfully started.
craycrayuk
on 23 Sep 2017
yeah, that might work too I guess.
AudriusButkevicius
on 23 Sep 2017
Chiming in to say this affected me too, and also killed my battery for the past few days while it was broken.
distancesprinter
on 27 Sep 2017
Related issues
gdt
路
6Comments
jebeld17
路
7Comments
acornsirup
路
4Comments
reverse-unina
路
3Comments
martin-sweeny
路
9Comments
Most helpful comment
You should be able to fix it by deleting the
.stfolderfile and creating a folder called.stfolder. After that, make Syncthing restart (eg by force killing the app or restarting your phone).