# Does anyone know why syncthing-fork is no longer available on Github?

**URL:** https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661
**Category:** General
**Created:** [November 13, 2025, 2:36pm UTC](https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661 "2025-11-13T14:36:41Z")
**Posts on this page:** 1
**Showing post:** 256

<div class="post-metadata">

### Author: ![chenxiaolong](https://forum.syncthing.net/user_avatar/forum.syncthing.net/chenxiaolong/32/20542_2.png) [@chenxiaolong](https://forum.syncthing.net/u/chenxiaolong)
#### Post date: [February 13, 2026, 6:02pm UTC](https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661/256 "2026-02-13T18:02:54Z")

</div>

> Can’t really tell if ‘normal’ syncthing-android always uses the Storage Access Framework, but if it _does_, then this version might actually be speedier. Will give it a go hopefully soon regardless!

(Hi! I’m the author of BasicSync)

None of the syncthing Android implementations use the Storage Access Framework for file access. Some apps use the SAF folder picker, but internally are still just using local paths. Unfortunately, SAF is pretty poorly designed for what Syncthing needs. I’ve listed a few technical reasons in the README for BasicSync.

Performance wise, every syncthing Android app should be about the same.

From a user’s point of view, there are two main differences in how BasicSync runs syncthing compared to apps based on the original syncthing-android:

- Syncthing is embedded as a library in the main process, rather than running the `syncthing` command as a child process. For folks on Android 12+ who do not disable child process restrictions in Android’s dev settings, this design makes it so syncthing will never be killed due to high CPU usage, like when it is hashing files.
  - (But for folks with rooted devices, this makes it impossible to run syncthing as root)

- By default, when the app does not permit syncthing to run (eg. low battery level or metered network), syncing is paused without shutting down syncthing entirely. When it’s allowed to run again, it resumes without having to rescan every shared folder. This usually doesn’t matter unless you have huge shared folders.

EDIT: Also, there are significant differences in customizability and UI. BasicSync will never be as flexible as other apps and configuring things is done through syncthing’s web interface.

---

_[View the full topic](https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661)._
