Layarva Cloud Player

Power on the screen, keep playing

This launcher opens Cloud Player in Chrome or Chromium in full-screen mode. Once a Screen has been paired, its dedicated browser profile retains that pairing. Add the launcher to autostart so playback opens again whenever someone signs in to a Windows or Linux desktop.

This is not an Edge installer, a pre-login service, or an offline player. The computer needs a graphical desktop, browser, and internet connection. To exit kiosk mode, press Alt+F4.

Clean fullscreen, protected operator controls

The launcher uses the same Cloud Player as the browser, but starts in kiosk fullscreen with no visible playback buttons. Updated scripts identify launcher mode with ?launcher=1 and retain it after pairing/restart. Before pairing you can close the player. After pairing, press Escape/F11 or tap a top corner three times; enter the device PIN if configured. Only launcher mode opens the operator panel after unlock. Close Player Launcher retains pairing; Close Window dismisses only the popup; Resume locks and resumes playback. Release removes pairing after separate confirmation. If Chrome refuses to close the player, press Alt+F4. Ordinary browser mode does not show the second unlock popup, and fullscreen alone does not identify a launcher.

Fullscreen and content fit are different. Fit preserves the entire design and may show black bars if screen and design ratios differ. Choose Fill (crops edges) or Stretch (changes proportions) in Dashboard → Screen → display settings if you need edge-to-edge content. No automatic crop or stretch is applied by the launcher.

Using a second monitor while working? Keep the player in its own visible window. Updated launchers reduce Chrome background timer throttling and renderer backgrounding, without changing your everyday browser profile or disabling security. Close the old player before restarting the updated launcher so its new flags take effect. In the dedicated player profile, add app.layarva.com to Settings → Performance → Always keep these sites active; check Energy Saver and the computer’s Sleep settings. These protections cannot guarantee playback during OS Sleep, browser discard, or severe resource pressure, and may increase power use. Heartbeat continues without input focus and retries promptly when the page resumes; offline status still requires a fresh server response to recover.

Download the ZIP for your device

Each ZIP contains one script that you can inspect in a text editor before running. There is no hidden installer, administrator prompt, or automatic autostart change.

Windows

Windows 10/11 · Google Chrome

Includes launcher=1 · retains the existing pairing profile

Download Windows ZIP

ZIP SHA-256

b7c5901d604b9f507c3bd01bf74ecb550554e50a86421880e27f0e07839c25e2

Linux

Ubuntu / desktop Linux · Chrome or Chromium

Includes launcher=1 · retains the existing pairing profile

Download Linux ZIP

ZIP SHA-256

c45c9741cbfab42b4eaa851a50ffa5186de3a290151576a2deab06e857399ced

Install on Windows

  1. Install Google Chrome from its official source. Download the Windows ZIP above from app.layarva.com.
  2. Open PowerShell in the download folder, run this command, and compare the result with the SHA-256 above:Get-FileHash .\\Layarva-Cloud-Player-Windows.zip -Algorithm SHA256
  3. Extract the ZIP to a permanent user-owned folder, such as Documents\\Layarva. Open the .cmd file with Notepad and compare it with the source below.
  4. Close any previous Layarva launcher window before running the updated script (Alt+F4). Double-click Layarva-Cloud-Player-Windows.cmd, then pair the Screen once in Cloud Player. Keep the dedicated browser profile; do not delete it during an update.
  5. For autostart, press Win+R, enter shell:startup, then create a shortcut to the .cmd file in that permanent folder. Sign out and back in to test it. The launcher runs after a user signs in, not while the computer is still at the sign-in screen.

A browser or Windows may flag an unsigned ZIP or .cmd script as uncommon or potentially risky. Do not disable Defender or antivirus. Continue past a SmartScreen warning only after you have verified the source domain, checksum, and script contents, and when your organisation’s policy permits it. If antivirus detects malware or quarantines the file, stop and contact IT; do not restore it blindly.

Install on Ubuntu or another Linux desktop

  1. Install Google Chrome or Chromium and sign in to a graphical desktop session. Download the Linux ZIP above.
  2. Compare the downloaded checksum:sha256sum Layarva-Cloud-Player-Linux.zip
  3. Extract it to a permanent folder, allow execution, then run:mkdir -p "$HOME/.local/share/layarva-cloud-player" unzip Layarva-Cloud-Player-Linux.zip -d "$HOME/.local/share/layarva-cloud-player" chmod +x "$HOME/.local/share/layarva-cloud-player/Layarva-Cloud-Player-Linux.sh" "$HOME/.local/share/layarva-cloud-player/Layarva-Cloud-Player-Linux.sh"
  4. Pair the Screen once. For autostart, open Startup Applications (Ubuntu) or your desktop’s autostart settings, then add the absolute path to the .sh file as its command. Test it by signing out and back in. Other desktops can use an XDG Autostart entry; the menu name may differ.

Keep Cloud Player running: setup walkthrough

Complete these steps on the computer that runs the player. Menu labels vary by browser, OS version, and language. The launcher does not change browser or power settings automatically.

1. Choose the player window and monitor
  1. Use the Launcher on your main monitor, or a dedicated player window on your second monitor. Keep your work browser in a different window.
  2. Leave the player visible: do not minimize it, switch its window to another tab, or move it to an inactive virtual desktop. You can work in another application without keeping keyboard focus on the player.
  3. For ordinary browser mode, move the separate player window to the intended monitor before entering fullscreen. Check monitor placement again after restart; the launcher does not automatically choose a monitor.
2. Open the Launcher’s own Chrome profile
  1. Download and extract the latest ZIP first. Close the old player with Alt+F4, then close any other windows using the player profile. This briefly stops playback; configure outside viewing hours.
  2. Open PowerShell (Windows) or Terminal (Linux) in the extracted script’s permanent folder and run the matching command below. It opens a normal settings window, not fullscreen, using the same dedicated pairing profile.
  3. Windows: open that folder in File Explorer, type powershell in its address bar, and press Enter. On Linux, use the folder’s Open in Terminal option where available. To verify the browser profile, open chrome://version and check Profile Path contains Layarva/CloudPlayerChrome on Windows or layarva/cloud-player-chrome on Linux.
  4. Do not delete the profile, switch to Guest/Incognito, reset browser data, or clear site storage. These actions can remove pairing. Settings in your everyday Chrome profile do not apply to this Launcher profile.

Windows · PowerShell

.\Layarva-Cloud-Player-Windows.cmd --configure

Linux · Terminal

./Layarva-Cloud-Player-Linux.sh --configure

Windows: %LOCALAPPDATA%\Layarva\CloudPlayerChrome
Linux: ${XDG_CONFIG_HOME:-$HOME/.config}/layarva/cloud-player-chrome

3. Chrome: keep Layarva active
  1. In the configuration window, open Settings → Performance, or enter chrome://settings/performance in its address bar.
  2. Find Always keep these sites active. Select Add → Add sites manually, enter app.layarva.com, and save. Repeat for layarva.com; verify both entries in the list.
  3. Check Energy Saver on this page. For continuous playback, turn it off in the player profile where available, or keep the device plugged in. This does not replace OS Sleep settings.
  4. Close all configuration windows, then run the launcher without --configure. Keep the original profile and Startup shortcut so pairing and autostart are retained.
4. Edge: exclude the web player from Sleeping Tabs

The provided Launcher uses Chrome/Chromium, not Edge. Follow this section only if you run Cloud Player in an Edge window, using that window’s profile.

  1. Open Edge’s three-dot menu → Settings → System and performance → Performance. You can start at edge://settings/system and select Performance.
  2. Under Always keep these sites active, choose Add site. Add https://app.layarva.com and https://layarva.com separately, and verify both entries.
  3. Check Energy saver in the same section, especially its plugged-in option. Keep the player exceptions; disabling Sleeping Tabs globally is not required.
5. Windows: prevent Sleep during playback
  1. Windows 11: Start → Settings → System → Power & battery → Screen, sleep, & hibernate timeouts. Windows 10: Settings → System → Power & sleep.
  2. For a mains-powered display, set the plugged-in Sleep timeout to Never. Set the plugged-in screen-off timeout to Never so the display remains visible. Review hibernation timers if your device exposes them.
  3. Battery settings are separate: use mains power for sustained playback. A laptop lid, scheduled shutdown, screen lock, or organisational policy can still interrupt the display. Do not disable security policies; ask IT if settings are managed.
6. Ubuntu / Linux: prevent automatic suspend
  1. On Ubuntu with GNOME, open Settings → Power. Under Power Saving Options, open Automatic Suspend and turn off the plugged-in option (When Idle on desktops) during playback.
  2. Set Screen Blank to Never if the display must remain visible. Other Linux desktops use their Power Management settings for equivalent suspend and display-off controls.
  3. Keep power connected and the desktop session running. Laptop lid and organisation-managed lock settings are separate; do not bypass security restrictions.
7. Verify the actual multi-monitor setup
  1. Start the updated launcher normally and confirm the existing paired Screen and content appear. Do not add --configure to your autostart command.
  2. Keep playback visible while working in another application for at least 10 minutes. Check moving content or the player clock, not only a still image.
  3. From a separate work-browser window, open Dashboard → Screen. Confirm the linked Screen stays Online and its heartbeat timestamp updates without clicking the player.
  4. If it goes Offline, return to the player and download its log through the operator controls (verify PIN if configured). Record the approximate time, browser version, OS, and whether the window was hidden or the computer slept; share the log privately with support.

These settings reduce interruption; they cannot guarantee playback through OS Sleep, browser discard, a crash, or severe resource pressure. They can increase power consumption. Layarva marks a Screen Online only after authenticated server contact—not merely because its tab remains open.

Copyable launcher source

Do not want to download a ZIP? Copy the Windows code into a .cmd file through Notepad, or the Linux code into a .sh file through a text editor, then follow the autostart steps above. The code below is exactly the source packed in the ZIPs.

Windows batch

Layarva-Cloud-Player-Windows.cmd

@echo off
setlocal EnableExtensions

rem Layarva Cloud Player for a dedicated Windows display.
rem Pair the Screen once. This separate Chrome profile keeps its pairing
rem across normal shutdowns and sign-ins. Close the display with Alt+F4.
rem This is NOT the Queue Kiosk launcher; it never enables silent printing.
rem Reduce background timer/render throttling in this dedicated Chrome process.
rem This cannot prevent Windows Sleep or browser discard under memory pressure.

set "PLAYER_URL=https://app.layarva.com/display?launcher=1"
if not defined LOCALAPPDATA (
  echo LOCALAPPDATA is unavailable. Sign in to a normal Windows user account.
  exit /b 1
)
set "PROFILE_DIR=%LOCALAPPDATA%\Layarva\CloudPlayerChrome"

set "CHROME_EXE="
for %%P in (
  "%ProgramFiles%\Google\Chrome\Application\chrome.exe"
  "%ProgramFiles(x86)%\Google\Chrome\Application\chrome.exe"
  "%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe"
) do if not defined CHROME_EXE if exist "%%~P" set "CHROME_EXE=%%~P"

if not defined CHROME_EXE (
  echo Google Chrome was not found. Install Chrome and run this file again.
  exit /b 1
)

if not exist "%PROFILE_DIR%" mkdir "%PROFILE_DIR%"
if not exist "%PROFILE_DIR%" (
  echo Could not create the Cloud Player profile directory.
  exit /b 1
)

rem Configuration is opt-in and uses the SAME profile, without kiosk mode.
rem Close all old player/profile windows first. No settings are changed for you.
if /I "%~1"=="--configure" (
  echo Opening the Layarva player profile settings...
  start "" "%CHROME_EXE%" --user-data-dir="%PROFILE_DIR%" --no-first-run --no-default-browser-check "chrome://settings/performance"
  exit /b 0
)

echo Opening Layarva Cloud Player in Chrome kiosk mode...
start "" "%CHROME_EXE%" ^
  --kiosk ^
  --start-fullscreen ^
  --disable-background-timer-throttling ^
  --disable-backgrounding-occluded-windows ^
  --disable-renderer-backgrounding ^
  --autoplay-policy=no-user-gesture-required ^
  --user-data-dir="%PROFILE_DIR%" ^
  --no-first-run ^
  --no-default-browser-check ^
  "%PLAYER_URL%"

endlocal

Linux Bash

Layarva-Cloud-Player-Linux.sh

#!/usr/bin/env bash
set -euo pipefail

# Layarva Cloud Player for a dedicated Linux desktop session.
# Pair the Screen once. The separate browser profile retains its pairing.
# Start this after a graphical user signs in, not from a headless boot service.
# Reduce background timer/render throttling in this dedicated browser process.
# This cannot prevent OS Sleep or browser discard under memory pressure.

player_url="https://app.layarva.com/display?launcher=1"
if [[ -z "${DISPLAY:-}" && -z "${WAYLAND_DISPLAY:-}" ]]; then
  printf '%s\n' 'A graphical desktop session is required. Sign in, then run this launcher.' >&2
  exit 1
fi

browser=""
for candidate in google-chrome-stable google-chrome chromium chromium-browser; do
  if command -v "$candidate" >/dev/null 2>&1; then
    browser="$(command -v "$candidate")"
    break
  fi
done
if [[ -z "$browser" ]]; then
  printf '%s\n' 'Chrome or Chromium was not found. Install one and run this file again.' >&2
  exit 1
fi

profile_dir="${XDG_CONFIG_HOME:-${HOME}/.config}/layarva/cloud-player-chrome"
mkdir -p -- "$profile_dir"

# Configuration is opt-in and retains the SAME pairing profile, without kiosk.
# Close all old player/profile windows first. No settings are changed for you.
if [[ "${1:-}" == "--configure" ]]; then
  exec "$browser" --user-data-dir="$profile_dir" --no-first-run --no-default-browser-check "chrome://settings/performance"
fi

exec "$browser" \
  --kiosk \
  --start-fullscreen \
  --disable-background-timer-throttling \
  --disable-backgrounding-occluded-windows \
  --disable-renderer-backgrounding \
  --autoplay-policy=no-user-gesture-required \
  --user-data-dir="$profile_dir" \
  --no-first-run \
  --no-default-browser-check \
  "$player_url"