If you’re experiencing issues displaying your Arreya content in your desktop web browser, we may ask you to capture one or more Chrome browser logs. Below are a few types of logs, and how to capture them to send to us if our support team requests it.
Chrome Network Log
This log type will help determine if assets or hosts are being blocked from loading. This can be due to a firewall, network configuration or other upstream networking issue.
Click the 3 dots, at the top-right, to open the overflow menu.
Choose ‘More tools’ > ‘Developer tools’ to bring up the console.
Select the ‘Network’ tab and make sure the option ‘Preserve log’ is checked.
You will see a small red circle in the top-left of the console, indicating that it is recording. If the circle is black, click on it to begin recording.
Reproduce the issue. You’ll see data being collected in the console window.
Click the red circle to stop recording after you see the error message.
Right-click in the list of entries loaded and select ‘Save as HAR with Content’ to download the ‘.har’ output file.
Chrome console log
This log type can help troubleshooting assets failing to load, content loading issues, or issues accessing or using the creative studio..
Click the 3 dots, at the top-right, to open the overflow menu.
Choose ‘More tools’ > ‘Developer tools’ to bring up the console.
Select the ‘Console’’ tab and make sure the option ‘Preserve log’ is checked.
Reproduce the issue. You’ll see data being collected in the console window.
Right click on any log statement in the console window, and click Save As… to save the log file to your computer.
Chrome OS Log (local)
This log can capture low level hardware and network issues, critical operating system issues, and kernel crashes outside of Kiosk Mode in Chrome OS.
Log in to your Chrome device.
Open the Chrome browser and navigate chrome://net-internals/.
Click the Chrome OS section on the left hand navigation bar.
Click Store System Logs, and wait for the confirmation message that the log file has been saved.
The compressed log file (.tgz) will be saved in your downloads file.
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.
