Skip to content

Releases: 6ebeng/torrserver-webos

v1.2.0

Choose a tag to compare

@6ebeng 6ebeng released this 13 Aug 16:41

Full Changelog: v1.1.27...v1.2.0

v1.1.27

Choose a tag to compare

@6ebeng 6ebeng released this 25 Jul 11:03

Fix: the app could hang forever on 'checking status' when installed WITHOUT Homebrew elevation - i.e. via webOS Dev Manager / Developer Mode, or on an unrooted TV. In that case the service runs jailed and is not allowed to execute luna-send; on the old Node 0.12 runtime that surfaces as a synchronous 'Error: spawn EACCES' throw, which killed the whole service process, so every status call went unanswered. Changes: all child processes now spawn through a safeExecFile wrapper that can never throw; getDeviceInfo and the media-player version check read the world-readable /var/run/nyx info files with fs instead of shelling out to luna-send (works jailed, and is faster); and an uncaughtException guard keeps the service alive so a single failing call can no longer leave the UI stuck.

v1.1.26

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 11:07

UI: the Autostart Enabled/Disabled toggle label is now white in both states; the Enabled state uses a slightly darker green so the white text stays readable.

v1.1.25

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 10:37

UI: Start and Stop are now a single toggle button (green Start when stopped, Stop when running). The Autostart control is now a single Enabled/Disabled state toggle (green when enabled) with no duplicate status text; on non-rooted TVs the toggle is hidden and the row shows 'Unavailable (TV not rooted)'.

v1.1.24

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 10:23

UI: Logs now open in a modal overlay (D-pad up/down scrolls, Back/Close dismisses) instead of an inline panel, so the log view is larger and does not push the layout around. The Cache storage control now sits on the Cache storage row (as a Change button), matching the Select version and Autostart rows.

v1.1.23

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 10:14

UI: the Select version, Autostart and Cache storage controls now sit inline in their matching info rows (Server Version, Autostart, Data directory) instead of in the actions bar, so each control is right next to the value it changes. The actions bar keeps the core actions (Start / Stop / Restart / Update / Open Web UI / MediaPlayer / Logs).

v1.1.21

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 09:05

Fix: installing a new .ipk over the app (webOS Dev Manager / Homebrew Channel update) left the control service unreachable - the app stayed on 'checking status' until the TV was rebooted. Cause: the service held a permanent keep-alive activity and ran resident; the installer killed that process abruptly and ls-hubd kept advertising the dead PID (a stale 'ghost' bus registration). Now the service idle-exits shortly after the app closes (so nothing resident is killed at install time) and explicitly de-registers its Luna bus handle on every exit path, so ls-hubd frees the name immediately. Updates no longer require a reboot.

v1.1.20

Choose a tag to compare

@6ebeng 6ebeng released this 04 Jul 08:02

Fix: on older webOS TVs (e.g. webOS 4.x, WebView based on Chromium 53) the app was stuck on 'checking status'. app.js contained ES2017 trailing commas in function calls (added by a Prettier reformat) which the old WebView rejects with a SyntaxError, aborting the whole script so it never polled the service. Removed all such trailing commas and added a .prettierrc (trailingComma: es5) so they cannot be reintroduced. Newer webOS TVs were unaffected.

v1.1.19

Choose a tag to compare

@6ebeng 6ebeng released this 03 Jul 11:30

Fix: the control service crashed on startup on webOS versions shipping older Node (e.g. webOS 4.x, Node 0.12), because getDeviceInfo used a trailing comma in a function call that ES5 rejects. This left the app stuck on 'checking status'. The trailing comma is removed so the service starts and responds correctly.

v1.1.18

Choose a tag to compare

@6ebeng 6ebeng released this 03 Jul 10:24
  • Fix the Status chip briefly flashing the green 'Running' state a second after pressing Start (most visible on a stop then start). The server now reports 'running' only once the HTTP port actually answers, so the Status stays 'Starting...' until the Web UI is genuinely reachable.