How to enable On-Screen Keyboard in Google Admin Console

Enabling the On Screen Keyboard is necessary for certain widgets inside of Arreya, most notably the SMS widget requires the user of a kiosk to input their phone number. While many ChromeOS devices have On Screen Keyboard enabled as a default, the safer option is to enable it in the Google Admin Console. This ensures that the kiosk functions as expected regardless of updates or changes to the configuration or firmware.

 

  1. Log into your Google Admin account at: https://admin.google.com/
  2. From the options on the left, click and expand the Devices category, then click and expand Settings.
  3. Click Device under the settings sub-category.
    on-screen keyboard for digital displays
  4. From here, choose the Organizational Unit for which you would like to enable the On Screen Keyboard. It is important to note that enabling this in a Organizational Unit will change the setting for any device or Organizational Unit underneath it. If you enable it at the top level Organizational Unit, all devices will have On Screen Keyboard enabled.
  5. In the primary window, scroll down until you find a category of settings titled “Kiosk accessibility”
  6. Underneath “Kiosk accessibility” you will find a setting called “Kiosk on-screen keyboard”. Change the setting to “Enable on-screen keyboard” as shown.
    enable on-screen keyboard for digital signage
  7. In the top right of the screen, click Save to save your settings and have the On-Screen Keyboard enabled for your chrome devices.

How to download device logs in Google Admin Console

An important feature for troubleshooting device issues, is the ability to remotely capture and download device logs for a specific device.

  1. After logging in to your Admin console, go to Devices > Chrome Devices and click a serial number to get into the individual device settings.
  2. On the left side of the screen you’ll see the option to Capture Logs. Click Capture Logs to begin the download.device logs for chrome devices for digital signage
  3. Once the capture is completed it will indicate the logs are ready for download from the Details Page. This is the page you should already be on.
  4. In order to download the logs, under the center info screens, look for the category  System activity and troubleshooting. It should be near the bottom.
  5. In this category you should see System logs, click the date listed underneath it to download the logs in a zip file.
  6. Email the device logs to support@arreya.com and we will analyze them for any issues.

 

Please visit Getting started with Chrome Device Management  for more information regarding Chrome Device Management.

My devices show offline in Google Admin Console

My devices show offline in Google Admin Console

If your device status is Offline in the Google Admin console, typically the device does not have a reliable internet connection, or there is something blocking Google from checking the status of the device on your network.

Verify that there is no interference from a Content Filter or Firewall – The most common cause of an offline device, issues with content not showing, or problems pairing a device come from content filters or firewalls that interrupt communication with Arreya. Please follow our instructions for content filters and firewalls – https://arreya.com/kb/allow-past-firewall/

Known Issues

In early August 2020, Google acknowledged that there was a known issue with the Google Admin console and Chrome OS devices that caused the admin console to show devices as offline, when they were actually online and would respond to requests. This does not affect the devices or the functionality of Arreya. The Arreya dashboard status is still accurate in this case.

We will update this article with more information as it becomes available from Google.

How to force install your Arreya channel PWA by device policy

Each Arreya channel can be deployed as a Progressive Web App (PWA) and has settings to customize the look and feel of your PWA. You can force install to PWA to managed devices via the Google Admin Console.

  1. After logging in to your Admin console, go to Device Management > Chrome management.Force Install your Arreya Channel PWA by Device PolicyForce Install your Arreya Channel
  2. Once you are on the Chrome Management screen, click on Apps & extensions.Force Install your Arreya Channel PWA by Device Policy 
  3. Select the OU (Organization Unit) on the left hand side of the screen that you wish to configure. Only Chrome Users in this OU will have the settings applied.Force Install your Arreya Channel 
  4. Click on the USERS & BROWSERS tabForce Install your Arreya Channel PWA by Device Policy
  5. Hover your mouse on the Yellow Plus button on the bottom right corner of your screen, next click on the Web icon to open up the Add by URL option. Enter the address of your Arreya Channel in the URL field. (e.g. arreyademo.arreya.com) You can select whether the PWA will open in a new tab, or a seperate window. Click Save to add the PWA.Arreya Channel PWA by Device Policy
  6. After the PWA is added, you will see it in the App listing. The app will force install by default, and you have the option to pin it to the users’ taskbars.PWA by Device Policy

 

Please visit Getting started with Chrome Device Management  for more information regarding Chrome Device Management.

Platform Compatibility Notes

platform compatibility with chrome os

Overview

A core goal of Arreya’s development team is to stay informed and constantly test the newest hardware and software that manufacturers have to offer. As a result of our extensive testing we found that Chrome OS devices provide the best experience. These devices offer easy device setup, deployment, and content delivery that works perfectly with Arreya.

Another benefit of Chrome OS devices with Chrome Enterprise Management is the ability to remotely manage the devices through the Google Admin console. To explain further, Chrome Enterprise Management simplifies the troubleshooting and deployment processes. Simply configure networks, reboot devices, fetch logs, take screenshots, and much more.

Arreya tries to remain platform agnostic while taking advantage of new browser features, and retaining backwards compatibility where possible. From user reports and previous testing, we have identified requirements and known issues for other common hardware choices. However this information is subject to change and cannot be guaranteed to work for every situation.

 

Android

  • Minimum version requirement: Android 7.1 (Nougat)
  • Android is an open source operating system and can be compiled with core features missing.
  • Low-end Android media players frequently are shipped with Android builds missing drivers, hardware acceleration issues and missing video codecs.

 

Samsung Smart TV (TIZEN OS)

  • Minimum Samsung OS version: Tizen 3.0. Came in 2017 models, older models may be able to be updated
  • Older versions of Tizen are missing core browser features 

 

General Smart TV/Mobile browser limitations (LG WebOS, etc.)

  • Limited memory and storage space could cause content failure and crashes
  • Concurrent video playback may be limited on any smart TV due to decoding hardware and software
  • Only fonts embedded in the TV will be used, other fonts may fail to display

 

Linux (RaspberryPi, Ubuntu, etc.)

  • Linux/Unix is a family of open source operating systems. Each version and build can be compiled with core features missing and frequently are missing required video decoders and codecs.
  • Additional package installation, configuration, and testing is required in every scenario.

 

Typical browser compatibility issues

Below is a list of browser features commonly missing from older, incompatible browsers. Arreya uses these features and requires them in order to properly run. 

 

 

Contact us to learn more about platform compatibility for digital signage software at 319-294-6671 or info@arreya.com.