kiFOSSk

Releases

• Oct 22, 2026 1.1.4
  ## 1.1.4 — 2026-10 ### Added - **Engine version in Settings.** The settings screen now shows the app version and the detected WebView engine version in a footer, with an explicit note when the engine is classified as legacy (feedback in #2). No more guessing from bug reports whether a device is running an old engine. - **WebView census.** Engine detection (version string, legacy/modern classification, legacy threshold at Chromium 72) now lives in one place (`WebViewCensus`) consulted at startup instead of ad-hoc checks scattered through the activity. ### Changed - **Engine-aware failure routing (Issue #2, completed).** Devices classified as legacy (Chromium below 72, typical Android 7–8 hardware with no WebView updates available) no longer receive the custom waiting page at all. Connection and render errors are delegated to the WebView's own built-in error page, which every engine can display, including engines that cannot render the waiting page itself. Modern engines keep the custom waiting page. Render-failure strikes are not counted on legacy engines, so the circuit breaker can never arm there.

  More…

  - **Waiting page is a terminal witness.** When the circuit breaker opens on a modern engine, the waiting page now switches to a terminal state stating the page could not be loaded, instead of presenting "Loading..." forever after the app has already given up (feedback in #2). - **Responsive waiting page.** The waiting page now carries a viewport meta tag and a flex-centered layout, so its message stays within the visible area on every screen shape. No more pinch-zooming to read it on tall displays (feedback in #2). ### Fixed - **Settings build metadata lookup.** Version display uses `PackageManager` instead of generated `BuildConfig`, avoiding AGP 8.x's disabled automatic `BuildConfig` generation.
• Oct 11, 2026 1.1.3
  ## 1.1.3 — 2026-10 ### Fixed - **Legacy WebView rendering loop (Issue #2, completion).** Pages whose JavaScript can't be parsed by very old WebView engines (roughly Chrome ≤71, common on Android 7–8 with no WebView updates available) previously caused an endless cycle of white screens and reloads. After three consecutive failed renders, a circuit breaker now trips and parks the app on the loading page — permanently, until a single re-attempt after a 10-minute cooldown. The reload loop can no longer repeat endlessly. - **Retry counter stalling.** The host-retry attempt counter now increments when a retry is scheduled rather than after its delay elapses. Rapid successive connection failures can no longer erase the counter's progress, so backoff advances correctly (5s doubling to a 5-minute cap) instead of restarting from the beginning on every failure. - **Stacked fallback loops.** All render-failure witnesses (connection errors, empty-body detection, page watchdog) now record through a single code path, and waiting-page fallbacks are debounced to one per failure event. Duplicate recovery loops can no longer pile up during flapping connectivity. - **Network watcher no longer reloads on stale data.** The network-recovery poller only reloads the URL after confirming connectivity at the end of the poll cycle, instead of blindly firing a doomed reload after the wait budget was exhausted. ### Changed

  More…

  - **Page load watchdog is now observational.** A page that takes longer than 20 seconds no longer gets interrupted with a fallback — slow is not dead. Empty-content detection is the sole basis for intervention, and it now requires two probes 5 seconds apart, and accepts visual elements (canvas, SVG, images, video, iframes) as evidence of a live page in addition to text. - **Auto-refresh suspends on persistent render failure.** While the render-failure count is elevated, the auto-refresh timer stands down rather than feeding the failure loop. - **Engine diagnostics on startup.** kiFOSSk now logs the detected WebView engine version and a legacy/modern classification at launch, making device reports actionable without adb archaeology. ### Restored - **Normal rendering on legacy WebView engines.** The v1.1.x series inadvertently interfered with normal page rendering on older engines through the error-page suppression fallback. v1.1.3 removes that interference — dashboards that the WebView can handle render normally again. ### Removed - Dead code: the legacy inline waiting-page builder and a vestigial retry-count accessor were removed. ### Notes for very old devices On devices whose WebView engine predates the syntax used by a particular page's JavaScript, no kiosk app can force that page to render. What v1.1.3 guarantees: dashboards your device can handle render normally, and pages it can't degrade to a stable loading page instead of an endless white-screen cycle.
• Sep 30, 2026 1.1.2
  ## [1.1.2] - 2026-09 ### Fixed - Critical: Waiting screen never appeared on older WebView versions (API 24-26) when the target URL was unreachable, leaving a permanently blank display (#2) — waiting page now loads from a bundled asset (`file:///android_asset/waiting.html`) instead of inline HTML via `loadDataWithBaseURL(null, ...)`, which old WebViews failed to paint; a 20-second navigation watchdog forces the waiting page if `onPageFinished` never fires, and an empty-content probe detects blank renders and falls back - Fix: `onReceivedError` triggered waiting page for subresource failures — now gated on `request.isForMainFrame` so a single failed image doesn't hijack the kiosk - Hardening: WebView cache disabled during error recovery (`LOAD_NO_CACHE`) to prevent stale content reappearing - Hardening: JS injection guarded — skipped on `about:` origins and null `document.documentElement` (previously threw `TypeError` on error pages) - Fix: screen stayed awake even with "Prevent screen timeout" disabled (#3) — `FLAG_KEEP_SCREEN_ON` now applied conditionally in `onCreate` and `onResume` based on the user preference - Fix: auto-refresh handler stacking — pending callbacks cleared before rescheduling
• Sep 4, 2026 1.1.1
  ## [1.1.1] - 2026-09 ### Fixed - **Critical**: Back-navigation bug allowing escape from kiosk mode — `SettingsActivity` back press now saves settings and returns to `MainActivity` via `OnBackPressedDispatcher` instead of relying on empty back stack (affected all API levels; API 24 stayed stuck in Settings, API 35 exited to launcher) - Migrated from deprecated `onBackPressed()` overrides to `OnBackPressedDispatcher` in both activities — replaces a deprecated API ahead of future Android versions where it's removed entirely ### Removed - **"Boot Autostart" setting** — a ghost from initial development that was past his prime, sorry about this inclusion. The toggle saved a preference nothing ever read; actual boot behavior comes from the home-launcher role. Its one real effect (requesting the battery-optimization exemption) now happens automatically when tapping "Set as Home Launcher". ### Changed

  More…

  - Refactored `SettingsActivity` to route all SharedPreferences reads and writes through `KioskPrefs` methods instead of raw `SharedPreferences` calls - Condensed README — consolidated device-specific troubleshooting into compact table, merged redundant privacy/security sections, streamlined setup guide - Added Obtanium as an installation option in README ### Added - `KioskPrefs.getScreenOn()` / `setScreenOn()` — completes full SharedPreferences encapsulation
• Aug 25, 2026 1.1.0
  ## [1.1.0] - 2026-08 ### Changed - Upgraded AGP from 8.2.1 to 8.7.2 - Upgraded Kotlin from 1.9.21 to 2.0.21 (K2 compiler) - Upgraded compileSdk and targetSdk from 34 to 35 (Android 15) ### Fixed - Long-press gesture broken by Kotlin 2.0 K2 compiler no longer implicitly returning `true` from `onDown()` — now explicitly overridden - Launcher status falsely showing "Active" on fresh installs — replaced `resolveActivity()` with `RoleManager.isRoleHeld(RoleManager.ROLE_HOME)` on Android 10+

  More…

  - Network errors mid-session now show the waiting page instead of Chromium's raw error page (`onReceivedError` hooked into existing `NetworkRetryHelper`) ### Removed - Gesture zone restriction (bottom-right corner) — long-press now works anywhere on screen - `GESTURE_ZONE_SIZE_PX` constant (dead code)
• Aug 16, 2026 1.0.3
  ## v1.0.3 — Gesture Conflict Fix & Auto-Refresh ### Fixed - **Fix**: Disabled WebView native long-press context menu via `setOnLongClickListener { true }` — gesture detection now has exclusive ownership of long-press events (resolves root cause of gesture/WebView conflict originally documented in v1.0.1) - **Hardening**: Injected CSS `webkitUserSelect: none` on page load to prevent text selection highlighting in kiosk mode ### Added - **Feature**: Optional auto-refresh with configurable interval (10s, 30s, 1min, 5min, 15min) - **Settings**: Auto-refresh toggle and interval spinner in SettingsActivity - **Behavior**: Auto-refresh pauses on app background (`onPause`) to preserve battery

  More…

  - **Behavior**: Auto-refresh resumes on page load via `onPageFinished()` --- **Full Changelog**: https://github.com/ShinyDiscoBallsDev/kiFOSSk/blob/main/CHANGELOG.md **Download APK**: See assets below **F-Droid**: Auto-update will arrive within 24-48 hours
• Aug 10, 2026 1.0.2
• Aug 5, 2026 1.0.1