Mostly just what Jakob said, but I already had the following typed out so here we go:
@tagomago I think I saw those weird runtime/C/unsafe errors in the past with certain combinations of the android NDK and go. Given you are using an F-Droid build, they might have changed any of those variables. However they did not change the NDK between 1.26.6 and 1.26.6.2. For go they use debian bookworm backports and that was updated from go1.21 to go 1.22 in between those two versions (don’t ask me why they stopped building go as part of the syncthing build, they’ll get burned by outdated go versions in debian earlier or later…). Seems very unlikely that the go bump caused this issue, but then again it’s the only change…
@chbly’s crash (post 16) is from the DB we are using, that’s kinda “known”. As in we get reports of those every now and then in our crash reporting system. Might be bad hardware, might be a bug in the DB - but there’s nothing obvious wrong when I looked at that so nothing to I can do. If you could provide a way to repro, I could look into it (when time allows), but I doubt it.
Though actually I think all my ramblings about build environment in F-Droid is irrelevant: This can’t be a build problem, otherwise all F-Droid users would be complaining. So given the old device, I’d say old device hardware/firmware/kernel issue is more likely. You could test by trying out the apk from github.
No prob. Yeah, my log was written by GitHub’s 1.27.10 apk. Well, idk, I’ll just keep trying new versions whenever they come out, see if it gets magically fixed anytime. Thx!!
Hmm, maybe we just really don’t have many users on F-Droid/Github, there’s now a report about crashes on github as well. Unfortunately not with a usable trace, so not certain it’s the same. Also only crashing some of the time doesn’t sound exactly right, but lets see.
Anyone successfully using 1.27.10 on android? (I am currently stuck on an older version because no time, probably need to make time…)
Yeah, I do, on two different devices - Google Pixel 8 running Android 14, and Samsung Galaxy Tab S2 8.0 running Android 7. My binaries are self-compiled though.
Yeah scratch all of that, turns out while the issue had 1.27.10 in the title, the reporter actually experiences these issues for more than a year - so not related.
I finally uninstalled 1.27.10 and installed 1.27.6 through f-droid and it seems to be working fine. One folder which was out of sync added a lot of files to .stversions on the remote side during the initial re-sync which wasn’t a big deal. I haven’t found any sync-conflict files. Scanning is significantly faster again like it was before 1.27.2. No crashes so far, either.
I’ll probably just stay on 1.27.6 until it breaks or I get a new phone. Thanks everyone for taking the time to look into this.
