Developer bundles
Debug installers and field diagnostics.
Use these bundles when you need pre-store validation on real hardware, deeper runtime logging, or a reproducible way to investigate memory, stability, connectivity, and command-processing issues across the Trillboards CTV fleet.
Current debug bundles
These artifacts are for internal testing, partner validation, and support-led troubleshooting. They are not the bundles we should treat as store-submission outputs.
Fire TV Debug APK
Debug variant for Fire TV sticks and Fire TV smart displays.
Android debug APK
- Uses the Android debug build flavor with a separate applicationId suffix.
- JavaScript console output is forwarded into Android logcat for field debugging.
Android TV Debug APK
Debug build for Google TV, Chromecast, Shield, and Android TV boxes.
Android debug APK
- Good for reproducing renderer, playback, and connectivity issues outside the Play listing.
- JavaScript console output is forwarded into Android logcat for field debugging.
Tablet Debug APK
Debug build for current Android tablet signage deployments.
Android debug APK
- Useful for kiosk, memory, and stability investigation on full tablet installs.
- JavaScript console output is forwarded into Android logcat for field debugging.
Tablet Lite Debug APK
Debug build for older Android 7.0+ hardware using the Lite agent.
Android debug APK
- Targets legacy signage hardware where startup cost and WebView stability matter most.
- Shares the same debug package-suffix strategy and logcat-friendly console forwarding.
LG webOS Debug IPK
Developer-mode IPK for LG webOS TVs and signage displays.
webOS TV app package
- Installs through the LG webOS TV SDK so developers can inspect runtime state with Chrome DevTools.
- The runtime already exposes socket, heartbeat, Luna-service, and device-capability diagnostics for field triage.
Samsung Tizen Debug WGT
Unsigned/developer-oriented WGT for Samsung TVs and B2B displays.
Tizen web app bundle
- Pairs with SDB debugging and device log capture for install and runtime triage.
- The runtime already emits lifecycle, connectivity, command, and device-info diagnostics.
Hisense VIDAA Debug ZIP
Developer bundle for Hisense VIDAA DevKit and direct test installs.
VIDAA HTML5 app bundle
- Builds in development mode so the web assets stay easier to inspect during field debugging.
- The runtime already logs heartbeat, socket, command, maintenance, and memory diagnostics where the platform exposes them.
Log capture guide
Use the platform-native tooling below when you need logs that explain memory growth, reconnect loops, renderer crashes, or command-processing failures.
Android / Fire TV / Tablets
Install the debug APK, then capture runtime logs with adb. The Android-family debug builds keep JavaScript console logs flowing into logcat, which makes WebView, telemetry, and socket issues much easier to reproduce.
adb logcat | rg -i "Trillboards|WebViewJS|WebViewConsole|Telemetry|Socket|Command"LG webOS
Install the debug IPK on a Developer Mode TV, then attach the web inspector and stream app logs from the CLI. This gives you live access to console output, network behavior, and Luna-service failures on the device.
ares-inspect --device <TV_NAME> com.trillboards.screenares-log --device <TV_NAME> com.trillboards.screenares-setup-device --listSamsung Tizen
Use the debug WGT on a developer-enabled TV. The Tizen runtime already exposes device-info overlays and verbose console logging around lifecycle, sockets, commands, and capabilities.
sdb shell 0 debug com.trillboards.screensdb dlog -v timeHisense VIDAA
Load the bundle through VIDAA DevKit and inspect the browser console/network output from the TV-side tooling. When testing proprietary VIDAA APIs, serve from vidaahub.com so device APIs behave like production hardware expects.
Serve the app through VIDAA DevKitInspect browser console + network output in DevKitUse vidaahub.com when validating proprietary VIDAA APIs