TV Remote

Releases

• Sep 28, 2026 1.6
  Adds standby wake for Kodi remotes, so the TV can be woken and Kodi brought to the front from a phone without a PC involved. - The on-device app listens on UDP `5600` for Yatse Remote Starter's fixed marker and for a standard Wake-on-LAN magic packet, which is what Kore sends when its Wake-on-LAN port is set to `5600`. Either wakes the TV and launches Kodi. The listener recognises only those two shapes, never passes packet contents to ADB or a shell, and exposes no parameters. Both protocols are unauthenticated by design, so this is for a trusted local network only. - A Wake-on-LAN packet addressed to a different machine on the LAN is ignored, on devices where Android still lets an app read its own hardware addresses. Android 11 and later hide them, and there the listener accepts any well-formed packet as before. - The wake action no longer blocks the listener. Remote apps send their wake packet more than once, and each duplicate used to queue another full wake sequence; now at most one runs at a time. - The HTTP port of the on-device remote is configurable in the app. The default is unchanged at `8080` — move it only if something on the TV already uses that port, Kodi's own HTTP server being the usual reason. - The battery-optimisation prompt opens the system settings screen instead of requesting a Play-restricted permission, and is shown once rather than on every start. Contributed by @NicolasDaLuzDuque in #2, validated on a physical Nvidia Shield, with six adjustments from review and a re-test on the same hardware afterwards.

  More…

  Signed with the same upload key (SHA-256: 4e2335afa65e6a6f0b42a30ef91f32fcad61c95d8ae153696f3293fdf8cbf563).
• Aug 31, 2026 1.5
  Fixes a crash on startup on Android 14 and newer. - `RemoteService` runs as a `connectedDevice` foreground service. Since API 34 that service type also requires one of the device-connectivity permissions, and the manifest declared none — so the service died with `SecurityException` the moment it started. `CHANGE_WIFI_STATE` is now declared, which is the honest one here: the service holds a `WifiLock` for its whole lifetime. Reported in #3. Devices on Android 12 and older were unaffected, and the crash only appeared once v1.4 raised `targetSdk` to 36. No changes to remote functionality. Also carried by this tag, outside the APK: - The setup wizard no longer aborts before it writes `config.json` (#1). `scripts/adb_client.py` called `sys.exit(1)` at import time, and the wizard imports it one step before writing that file, so every fresh install died halfway through and told the user to run the command they were already running. - The project now builds from source without release-signing properties. `signingConfigs` previously read them with `.get()` at configuration time, which made every Gradle task fail for anyone without the keystore — including the F-Droid build server, which builds unsigned and signs itself. Fix contributed by @NicolasDaLuzDuque in #2.

  More…

  Signed with the same upload key (SHA-256: 4e2335afa65e6a6f0b42a30ef91f32fcad61c95d8ae153696f3293fdf8cbf563).
• Aug 1, 2026 1.4