Phones reboot with Syncthing 1.30 under LineageOS 16 on HTC m8

Just FYI: I had similar issues with my Moto X Pure, with a slow (and maybe bad) SD Card formatted for “internal storage”. Even deleting a big directory (tree) caused reboots.

I downgraded, unchecked NAT traversal, then upgraded back to 1.3.0. Syncthing works now, this is very good. Of course NAT does not work, but that is a smaller problem.

2 Likes

@kisenberg @shscs911 @neden What kernel version are you on?

Its a bit convoluted, but works for me. You can enable Airplane mode and open Syncthing. Then select Change Settings from pop-up → Select Run when device is in flight mode → Unselect Run on Wi-Fi → Go back to main screen → Select Settings. Now you can open Syncthing Options and uncheck Enable NAT Traversal. Now change the Run Conditions back to original for normal operation.

1 Like

I’m using a custom kernel called

  • Thunder Kernel
  • zzmoove governer.
  • Linux version 3.4.11.
  • Linaro GCC 7.3-2018.05.
  • SELinux Status : Enforcing

@Catfriend1 @shscs911 Could you run sysctl kernel.panic_on_oops=0, start Syncthing (with “NAT Traversal” enabled) and check dmesg? If there is anything relevant in dmesg please post it.

Now, I have access to one of the phones. Kernel: Linux version 3.4.113-g2d8d797 (buildkite-agent@lineageos-buildkite)(gcc version 4.9.x 20150123(prerelease)(GCC)) #1 SMP PREEMPT Mon Sep 30 17:04:06 UTC 2019

Uncheck NAT in 1.3.0 works also for me.

I’m on LeneageOS 15.1 with kernel 3.4.113-lineageos-gf8d7bda.

@kisenberg @shscs911 @neden If any of you are running a official LineageOS build, could you report it upstream?

Sorry mine’s an unofficial DirtyUnicorn build. I’ll report it to the ROM developer.

With help from @khumarahn, I think we have found the fix. I’m pretty sure this change fix the issue: https://github.com/LineageOS/android_kernel_cyanogen_msm8974/commit/f44b4b19da1541fce8440ffa1e59cdb722cf10b5, so contact your ROM developers and ask them to apply the fix.

See also: https://github.com/syncthing/syncthing-android/issues/1425#issuecomment-543365628

1 Like

Support for my device was dropped half a year ago. :frowning:

In theory you could apply the patch yourself, but I’m not sure it is worth the trouble. What device do you have?

Nexus 4. Don’t think I should bother with the patch.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.