Recent updates that happened on the backend of Arreya regarding videos. Our video encoder was just increased in both available Memory and CPU to boost the speed of our encodings.
Fastboot Videos
Additionally, we have added a feature to our encoder to play the videos on ‘fastboot’. The fastboot setting on the backend means that it sets the index of the video to the beginning of the file, by default. This setting allows all or most videos to start playing before the Chrome-box or other device needs to cache the video.
Depending on the size of the video, you might see some delays as the video will still need to load into memory to start playing.
This article is intended for developers interested in remotely debugging their ChromeOS App or Progressive Web Application running in Kiosk mode.
The target ChromeOS device must be in developer mode, and enrolled into an admin console Organization Unit (OU) with forced re-enrollment and verified boot disabled. If it was previously used with forced re-enrollment (FRE) enabled you’ll need to do the steps below.
Forced re-enrollment can be found in the Chrome device settings in your Google Admin console. When this is set to ‘Device is not forced to re-enroll after wiping’, it will disable forced re-enrollment and allow developer mode to be enabled.
Remove ChromeOS device from forced re-enrollment
Move device to OU with FRE and verified access/boot disabled
Reboot with the recovery button depressed, then attempt to enter developer mode with Ctrl + D. You will not be able to enter developer mode, but the device will factory reset itself.
Run through initial setup, the device should not automatically re-enroll, if it does, check your admin console settings and ensure the device is in the correct OU.
Log into the device in consumer mode, do not enterprise enroll the device.
Reset the device again with the recovery button, you should be able to enter developer mode using Ctrl + D shortcut.
Device should be in developer mode now, you can enable debugging features and enterprise enroll the device.
You will need to open a shell on the target Chromebox by either opening a virtual terminal by pressing Ctrl + Alt + F1(back arrow) or you can skip kiosk app on startup with Ctrl + Alt + S, log in, and open a shell by pressing Ctrl + Alt + T and typing ‘shell’
SSH Arguments: ‘-L 9222:localhost:9222’. (-L argument forwards a remote port to a local port. If you used a port other than 9222, replace it here)
Note: If you have used SSH with the same host, you may need to clear the host from your known_hosts file in the ssh client settings, or append ‘-o UserKnownHostsFile=/dev/null’ to the SSH arguments to use an empty known_hosts file.
You’ll be prompted to add the host/key to your known hosts.
Enter the root password you set.
Leave the ssh client window open in the background.
Remote DevTools
Open a new Chrome browser window, and navigate to chrome://inspect
Click Configure… and add ‘localhost:9222’ to the list of targets. Click Done.
Your remote target should now show up under the Remote Target heading. You can select each app, extension, or PWA you wish to inspect.
Each Arreya channel can be deployed as a Progressive Web App (PWA) and has settings to customize the look and feel of your PWA. The PWA can be force installed to managed devices via the Google Admin Console.
After logging in to your Admin console, go to Devices.
In the navigation menu on the left hand side, select Chrome > Apps & extensions > Kiosks
Select the OU (Organization Unit) on the left hand side of the screen that you wish to configure. Only Chrome devices in this OU will have the settings applied.
Click on the KIOSKS tab
Hover your mouse on the Yellow Plus button on the bottom right corner of your screen, next click on the Add by URL option.
Enter the address of your Arreya Channel in the URL field. (e.g. arreyademo.arreya.com), click Save to add the PWA. You will be warned that permissions will automatically be granted to the web app. Click Agree to continue.
After the PWA is added, you will see it in the App listing and the kiosk app will be installed by default. You must select the app to be automatically launchedby selecting it in the drop down box next to Auto-launch app.
Once you have set the app to auto launch, you can change the kiosk app settings by selecting the app in the app listing, and adjusting settings in the window on the right hand side. You need to turn on Allow App to Manage Power. We recommend turning on Enable Health Monitoring and Enable System Log Upload.
This article will cover installing your Arreya Channel PWA on a Chrome OS device where that isn’t force installing the PWA by policy.
On your Chrome OS device, open the Chrome browser.
Navigate to your Arreya channel URL (https://*yourchannel*.arreya.com). You can also send your users a link sent via an email, social media, or other method instead of manual entry.
At the top right of the address bar, click the [Install +] button
The application can now be found in the application launcher accessible from the bottom taskbar. You can also right click the application icon and pin it to your taskbar.
PWA support has been supported in Chrome since version 39. Contact us to learn more about Chrome OS Device PWA.
This article will cover installing your Arreya Channel’s PWA on an iOS device. The process is similar for iPhone and iPad devices.
To add your Arreya Channel as a PWA on an iOS device, on your iOS device, open Safari or other browse.
Navigate to your Arreya channel URL (https://*yourchannel*.arreya.com). You can also send your users a link sent via an email, social media, or other method instead of manual entry.
Safari on iOS will not prompt you to install the application. Click the “Share” button on the bottom toolbar, then select the “Add to Home screen” option.
After adding it to the Home screen, you will be able to open the application using the newly created shortcut.
Web apps are partially supported in iOS starting with version 11.3. You may experience odd behavior in some versions. More about mobile browser support can be found at https://caniuse.com/#feat=web-app-manifest
