Issue Report: Syncthing-Fork app terminates on its own

[aloksharmaonline]

Problem Description:

Syncthing-Fork does not maintain automated background persistence. The app only syncs when manually launched.

When the persistent notification is enabled, the app functions correctly in the background. However, once the remote laptop is closed and disconnects, the persistent notification automatically disappears after a while. At this point, the background service terminates completely and fails to auto-start or wake up when the laptop comes back online, requiring another manual launch.

Device Details:

• OS: Android 16

• Device: Motorola

Attempted Troubleshooting (Without Success):

• Set App Battery Usage to Unrestricted and verified Allow Background Usage is enabled.

• Toggled battery settings (Unrestricted > Optimized > Unrestricted) to force reset permissions.

• Enabled Start service automatically on boot in the app settings.

• Locked the app in the Android Recents multitasking view (the system still terminates it after ~1 hour).

• Updated Private DNS from dns.adguard.com to dns.adguard-dns.com to rule out connection blocks.

• Looked for an internal app setting to permanently force the foreground service/notification to stay alive when disconnected, but no such toggle exists in this version.

Any help and guidance to resolve is deeply welcome

[acolomb (André Colomb)]

Have you checked for other installations of the app? I remember having the app on the phone twice at some point, with obviously different app IDs. The symptoms were similar, one instance kept quitting regularly for no apparent reason.

[aloksharmaonline]

Yes I have. New phone, single install for sure.

It was working fine on my earlier phone with, same settings. As soon as I shifted to new phone/Andorid, it is behaving like this:

Earlier Phone model: MiA3, Stock Android, Version Android 11

[Martchus]

I don’t use the Syncthing-Fork app anymore but I suppose it has some way to check logs. So try that and share the logs here or create an issue on GitHub. If it crashes badly enough so there are no logs you’ll have to check for logs or crash dumps on system level. I usually do that as I have documented for Syncthing Tray. Although maybe Syncthing-Fork has some built-in crash collecting - so I’d check that first.