I have a Giada DN83* device that was previously running version 410, and I just tried to update it to 411.
The app downloaded the update and then closed; after that, the Android desktop was visible.
When I manually restart the app, version 411 now appears.
I’ve noticed twice so far that the 410 crashed and didn’t restart on its own.
Hi there,
Regarding the update closing out to the desktop, that is completely normal. Android has to force close the old app to overwrite the files with the new version, and on many hardware players, it will just drop to the home screen instead of automatically relaunching on its own. Since version 411 is showing up when you manually open it, your update went through successfully.
As for the app crashing and staying closed on the desktop, that usually means a background permission or setting is preventing Xibo from restarting itself. Here are two things you’ll want to check
Go to Displays, then Display Settings and edit your Android profile. Under the Advanced tab, make sure Automatic Restart is checked. This tells the system to automatically pull Xibo back to the foreground if it ever drops out.
On the Giada Device, go into the local Android settings on the box itself and ensure the Xibo app has permission to “Display over other apps”. If this is turned off, the Android OS will actively block Xibo from relaunching itself after a crash.
Hello,
Thank you very much for your reply.
It’s set up and works on the other 40 DS devices as well
Where exactly is this setting located?
Hi, I see this device has “only” 2Gb of RAM. Is this enough for the XIBO CMS?
Or is the system slow because of this?
Kind regards, Peter
The DN83 is a supported device so Xibo is expected to run on it. It’s not a “high powered” device so it’s likely best for lower end requirements. You can see the comparison on the Media Players page of the Xibo website.
Please do ensure you have the correct custom firmware from Giada for that model.
See Xibo for Android v4 R409 Released regarding firmware. It has to be requested from them directly.
Thanks for the reply!
It was the Android R409 announcement that first brought the new media player to my attention; I also contacted Giada and received the firmware. I installed the firmware, and the 410 player ran stably (albeit a bit slowly). Attempting to update to 411 caused the issues described above, and now the screen just shows “Xibo is not responding,” even though the presentation continues to play in the background.
We had a bit of confusion here between us and Giada — initially we thought that the “Display over other apps” permission was not required, so we removed that permission request on install — later we discovered that it was actually required, so we added the permission request back again. However, we only request permissions on configuration, so that wouldn’t have triggered.
You have to locate that manually in Android Settings - under App → Permissions → Xibo.
Sorry to hear that, clearly not expected behaviour. We have an updated Giada API integration to release shortly with v4 R412, which might help solve the issue. That same release has some other playback optimisations around videos which might be relevant if you use a lot of video.