Skip to main content

​
Supported Android hardware

The current stable Android Player is 0.40.0 (build 40). Android Player requirements are independent from the plain-browser Cloud Player requirements. Android 8.1/API 27 and older cannot install the APK. Memory close to 1 GB can work, but the Player may recover its renderer more often. Do not purchase a fleet based only on the minimum row; test the exact hardware and content first.

​
Choose the APK for the processor

The published APK signing certificate SHA-256 is:
Use only Layarva download sources. A different certificate means Android will treat the file as a different application and it must not be installed as a Layarva update.

​
Check the box before buying more

From the Android Player welcome screen, select Check this device. The native check reads Android/API level, manufacturer and board, processor ABI, kernel-reported memory, free storage, GPU and texture ceiling, browser engine, and actual WebGL behavior.
Android Player device check showing Android version, processor ABI, memory, storage, and graphics

The Android check measures the device rather than trusting the version and memory printed on a TV-box listing.

Android Player verdict showing supported with limits for a 32-bit processor and software-rendered WebGL

This emulator is intentionally an example of Supported with limits: it is 32-bit and draws WebGL through SwiftShader software rendering.

Yellow is not a failed installation. A 32-bit processor, low texture ceiling, tight memory, or software WebGL means the device needs lighter content or reduced render resolution. A missing OpenGL context or Android below API 28 is a hard failure.

​
Choose where content comes from

Android Player welcome screen showing Cloud, Edge, Offline, and Check this device

Android Player offers Cloud, Edge, and Offline sources from the first-run welcome screen.

Changing the source does not erase the other mode’s identity. Cloud pairing remains stored when switching to Offline, and an imported Offline package remains available when returning to Cloud.

​
Pair in Cloud mode

  1. Select Cloud.
  2. Keep the six-digit code visible.
  3. In Layarva, open Screens → Pair Screen, choose Cloud, and enter the code.
  4. Configure the Screen name, Channel, Location, output, fit, and optional unlock PIN.
  5. Complete pairing and wait for the first Publication.
Android Player Cloud pairing screen with a temporary six-digit code

The Android Player displays the pairing code, expiration countdown, environment, and Platform API destination.

​
Import Offline content

Copy the signed .lvapkg to the root of a flash drive and insert it into the Player. In Offline mode, the Player detects the package, verifies its signature, manifest, files, target, renderer compatibility, and lease before installing anything.
Android Player Offline mode waiting for a flash drive containing a Layarva package

Offline mode waits for a signed Layarva package and discovers it automatically from attached storage.

The current content continues playing while a replacement package is verified.

​
Open diagnostics

Use any supported method:
  1. Press Left, Right, Left, Right on the remote, with no more than 1.5 seconds between presses.
  2. Press the remote’s Info or Settings button.
  3. On a touch device, press and hold the lower-right corner.
If unlock protection is enabled, diagnostics requests the Screen PIN first.

​
Identify the installation

Android Player diagnostics header showing build, API environment, device model, SDK, and ABI

Diagnostics identifies the Player build, API environment, Platform URL, Android device, SDK, and ABI.

Read app.version, api.environment, api.baseUrl, manufacturer, model, SDK, and ABI to support. These fields establish which build, server, and APK architecture are actually running.

​
Display engine and render resolution

Android Player diagnostics showing Automatic, Device browser, Bundled, and render-resolution choices

Automatic engine selection and render resolution can be overridden when a specific box displays incorrectly or struggles with animation.

  • Automatic uses the device browser and can move to the bundled engine when needed. Use this for normal operation.
  • Device browser forces the Android WebView.
  • Bundled forces the engine included in the APK.
  • Native render resolution produces the sharpest image.
  • 720p or 540p reduces shader load on weak GPUs such as Mali-400/450/470.
Changes apply when the next content renderer starts; the content currently on screen is not interrupted.

​
Location, logs, release, and packages

Android Player diagnostics showing location, Save log to USB, Release this screen, and Choose a package

Diagnostics can grant optional location access, export logs, release pairing, and choose a signed Offline package.

  • Allow location is optional. Denial does not stop playback.
  • Save log to USB writes the recent build and playback diagnostics to attached storage.
  • Release this screen removes the Cloud pairing and returns to a pairing code.
  • Choose a package scans attached and device storage for .lvapkg files.

​
Guidance for weak devices

An ARM 32-bit Android 9 box with a Mali-450 and approximately 1 GB RAM can run static content and H.264 video, but animated WebGL content is demanding. Leave engine selection on Automatic and use 720p or 540p render resolution when animation stutters. For new purchases, choose ARM 64-bit, at least 2 GB RAM, 2 GB free storage, and a GPU with a 4096-or-larger texture ceiling.