Skip to content

KOSyncthing+ v1.1.3

Choose a tag to compare

View all tags
@d0nizam d0nizam released this 07 Jun 20:21
v1.1.3
c742061
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[v1.1.3] — 2026-06-07

Added

  • Richer Copy diagnostic info — binary ELF check, process RSS/threads/CPU,
    filesystem type & free space, network loopback & Kindle firewall ports
    (22000 TCP, 21027 UDP), folder/device counts.
  • Kindle firewall now opens TCP 22000 (sync) and UDP 21027 (discovery)
    automatically, fixing pairing issues.
  • Autostart respects manual pause — manually stopping Syncthing from the
    menu now pauses Autostart until you start it again. Previously Autostart
    would immediately restart the daemon after a manual stop.
  • LAN-only network support — Autostart and sync timers now use
    NetworkMgr:isConnected() (has IP association) before falling back to
    isOnline() (has internet route). Syncthing can sync on local networks
    without internet access.

Changed

  • Binary download validates ELF & gzip magic and enforces a minimum file size
    before extraction.
  • Binary installation is atomic (.new file replaced only after ELF check).
  • Notifications say "network unavailable / disconnected" instead of
    "Wi‑Fi unavailable / disconnected" to match the new LAN-only behaviour.

Fixed

  • Text file named syncthing (Kobo app‑stream metadata) no longer accepted as
    a valid binary.

  • Curl is tried before wget for more reliable GitHub downloads.

  • Architecture detection now uses a single shared helper
    (st_utils.detectArch).

  • Autostart no longer breaks after network loss. Automatic stops
    (network disconnect, app close) were incorrectly setting the user_paused
    flag, causing Autostart to stay disabled after reconnecting or restarting
    the app. Only an explicit manual stop now sets the flag.

  • Conflict dialog no longer shows "unknown" for older devices. Older
    KOReader builds (pre-2022) write last_percent instead of
    percent_finished; both fields are now recognised when reading progress
    from metadata sidecar files.

  • Conflict dialog now appears when only one side has a percent field.
    Previously the "reading progress conflict" dialog was suppressed when the
    conflict copy lacked percent_finished even though the local copy had it
    (or vice versa). The dialog now opens whenever either side carries progress
    data, showing the known percentage and "unknown" only for the side that
    genuinely has none.

  • getConflictsDetailed now reports has_progress = true when at least
    one side has a percent field     (previously required both sides). This
    affects the auto-merge menu display and any companion plugins that read
    conflict metadata.

Assets 3
Loading