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.
A useful feature of Chrome Device Management is the ability to pre-configure networks on Chrome devices.
After logging in to your Google Admin console, go to the Device Management section.
On the column on the left side of the screen, click Networks. (Your console may say Network instead, under the Device Settings heading)
Click CREATE WI-FI NETWORK.
In Platform access, check the box next to “Chromebooks (by device)”
In Details, create a name for your network. Then add the Network Name (SSID) for your wireless network, check the box for “Automatically connect” and if the SSID is not broadcast (hidden), select the correct Security Type, and lastly the password for the network.
How do I add users to the Admin console in Chrome Management?
After logging in to your Google Admin console, go to the Users section.
Click the [Add User] button in the lower right corner.
Enter the user’s name, desired email address, and if desired make a password in order to set restrictions.
Click [ADD NEW USER].
Record the credentials on the next screen and send them to the new user if desired. Click Done.
How do I give a new user access to Admin console functions in Chrome Management?
In order for a user to have access to Admin console functions, you will need to set admin privileges for the user.
After logging into your Admin console, go to the Admin roles section. The button may be hidden in the More Controls dock at the bottom of the screen.
Select which role you would like your user to have, the typical choice for setting up a user that has access to device management, would be the Services Admin role. An explanation of the different built in roles can be found here: https://support.google.com/a/answer/2405986?hl=en.
Click [Assign Admins].
Type the email address of the User you would like to assign privileges to .
Click [Confirm Assignment]. That user will now have access to the Admin console.
An important feature for troubleshooting device issues, is the ability to remotely reboot a Chrome device or take a screenshot of the screen.
After logging in to your Admin console, go to Devices > Chrome Devices and click a serial number to get into the individual device settings.
On the left side of the screen you’ll see your options for Reboot, Remote Desktop, and Take a Screenshot
This screen also has information regarding system information, and troubleshooting features like Remote Desktop, Capture Logs, and Move.
Pressing [Reboot] will send a command to the Chrome device to reboot. You will either get a success message, or an error if the device is offline or it’s unable to communicate with the device.
Pressing [Remote Desktop] will start a dialog for you to remotely view your screen in real time.
Pressing [Take a Screenshot], next to Screen Capture will take a screenshot of what is currently on the screen. This can be used to determine what is showing on the screen currently.
The Screen Capture and Remote Desktop functions will return an error if a user has interacted with the Chrome device, pressed a touch screen, used a keyboard or mouse, etc. This is a security feature to prevent sensitive information from being accessed on a user’s screen.
An important step in organizing your devices is assigning Asset IDs for each device so you can easily identify a device when you go to reboot or get information from it.
After logging in to your Admin console, go to Devices > Chrome Devices and click a serial number to get into the individual device settings.
Under Custom Fields click on the field you want to edit and it will bring up the edit screen.
Put in your Asset ID that you want to use and put in a Location to help you remember where the device is.
