Console home (mode pill & settings), settings groups, QR code & control code, the dual-process architecture, content recovery, logs and OTA.
Console Home

A dark console window: the header shows the device ID, online status and a QR code (scan with a phone to jump straight to this device's remote page), with feature entries and a collapsible log below. The UI language follows the system (Chinese in zh locales, English otherwise) and can be switched manually in the header. The mode pill [Screen | Remote] switches this device's role:

  • Screen: Windows = open/close all display areas (opening restores content and minimizes the console); phone = enter the fullscreen display page;
  • Remote: enter remote mode (this device acts as a remote; display-family commands are rejected with device is in remote mode; on Windows all display areas are closed first); the remote shell has a "Back to console" button;
  • Back to console: phone = back button (content kept); Windows = move the mouse over any display area to restore the console.
Settings
GroupNotes
Display areasAdd/update/remove/rename areas and pick the default (drag + pixel inputs, stored as 0~1 ratios internally). Double-click an area = open/close its window; "Open all / Close all" buttons available. Layout persists locally, equivalent to cloud screen commands
StartupRestore-on-launch (default on: areas and content reopen after restarts/crashes) + launch on boot (registry / LaunchAgents / autostart / Android BootReceiver). Once bound to a bench, both can also be set remotely from the remote settings page
SoundTTS engine (follow system / system / bundled sherpa — its ~51MB model downloads on first use), speech language/volume/rate; background music volume and ducking (lower to 10%/20%/30% or pause while pages play audio; default -20%, resume after 5s of silence)
Display & languageOrientation (phones/tablets only: system/landscape/portrait; desktop windows resize freely); UI language (system/中文/English)
Control code6 digits, generated on first launch; remotes without sign-in use it to control this screen (same code for LAN direct and cloud channel); refreshable (old code dies instantly) or can be disabled (then only bench members can control)
CacheContent cache master switch (default on; turning it off clears all existing cache and stops read/write) and clear-all
SystemConsole ID (bind/rebind bench — re-registers on save), re-register, restart app (desktop)
Network & Addresses

The console lists all LAN addresses of the device (multiple NICs/IPs wrap as needed); remotes connect directly over LAN using the same-network address (see the API book). The cloud system command {"system":"network"} returns the current link type and IP/mask/gateway/DNS.

Dual-Process Architecture (desktop)
  • console.exe: console window (UI + platform connection + IPC service), custom title bar, single instance;
  • player.exe: one borderless renderer process per display area, spawned by the console on demand, talking over 127.0.0.1 IPC;
  • Without a device ID it shows "Unauthorized" and retries silently.
Content Persistence & Recovery

Each area's content (url/cookie/header/vars) persists locally. After a restart (including crashes), areas with content reopen and restore automatically. Clearing content (clear) or closing a window (close) removes its persisted content. Screen mode keeps a wakelock (phones/TVs don't auto-sleep).

Logs

A logs/ directory next to the exe (falls back to the app-data directory when not writable): player-*.log for key events, dev-*.log for full debugging, rotated daily, kept 7 days. Attach the relevant day's logs when reporting device issues.

OTA Upgrades

After the cloud issues a package name, the device downloads, verifies, replaces the install directory and restarts (Windows only; Android/macOS/iOS currently ignore OTA commands). No manual steps; failures report a failure event.

Android TV Notes

The package declares a TV launcher entry (LEANBACK_LAUNCHER) and doesn't require touchscreens, so TVs can open it directly; a TV remote can operate the console (the drag canvas doesn't fit remotes though — prefer cloud screen commands for layout on TVs). Old TVs may have an outdated system WebView; watch page compatibility.