Jump to content

Recommended Posts

Posted

We have a couple of ChromeBox devices that run an interactive HTML site, connected to touch screens. They are using the Kiosk app found here: https://chromewebstore.google.com/detail/kiosk/afhcomalholahplbjhnmahkoekoijban?hl=en - The devices are managed on Google Workspace.

 

We have replaced the screens, however, the content is not displaying properly, it isn't scaling and only showing the top left corner. The Chromebox itself is fine, when we boot and use CTRL + ALT + S the display is fine. So it looks like it is specific to the app.

 

I can't figure out how this app is configured. I was looking for settings to try and fix this display issue. I can't see setting in the Google Workspace tenant for it. For example the URL it points to. Maybe it's configured locally.

 

Does anyone have any suggestions please? Or maybe does anyone have any alternative ideas?

 

Thanks

Posted

Devices> Chrome> Apps and Extensions. Find the correct OU and look on the Kiosks tab.

 

Click on the app and depending on how it works, you may be able to edit the JSON on the right hand side.

 

 

If it is only displaying the top left corner, could the screens be running in a video wall mode, like on old Top of the Pops? We had some LG screens that somehow got switched to that mode.

  • Thanks 1
Posted
We have a couple of ChromeBox devices that run an interactive HTML site, connected to touch screens.

 

Our lobby display screens are ChromeOS kiosk devices, showing a basic HTML slideshow. We didn't need a separate kiosk app, we just pointed each device at the URL we wanted to show, that seems to work okay.

  • Thanks 1
Posted

Hello,

 

We figured it out. The content was was written for a specific screen resolution and wasn't responsive.

 

I do plan on exploring Chrome OS more for our digital screens. We literally have hundreds of them. No idea why these things are the odd one out using a third party app.

 

Cheers

Posted
The content was was written for a specific screen resolution and wasn't responsive.

 

Ah!

 

No idea why these things are the odd one out using a third party app.

 

Possibly something to do with getting the content to refresh. I've noticed our screens can take a while for changes to take effect (ChromeOS seems to load up the cached version of content, even after a reboot) - not a huge problem in our case, but worth checking if you are rolling something out over a larger estate of devices.

Posted
Ah!

 

 

 

Possibly something to do with getting the content to refresh. I've noticed our screens can take a while for changes to take effect (ChromeOS seems to load up the cached version of content, even after a reboot) - not a huge problem in our case, but worth checking if you are rolling something out over a larger estate of devices.

 

I am looking at standardising our 500 ish estate of screens. Will certainly be doing some testing!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...