We have applied Xibo version 4 Revision 410 to our new DSDevices DSDA1 media player and it reports a fault on the Displays page of our hosted Xibo CMS 4.4.1 :
This is then recorded within the Log located in the ADVANCED section the CMS portal:
Does anyone know why this faults is occurring and how to fix the issue. PS the assigned layouts and applied schedules all seem to be working as expected.
It is possible that the error was captured during the installation of your Xibo for Android (XfA) V4 R410. Would you know if the timestamp in the CMS log section for the error is around when you were upgrading your XFA player?
Normally the fault showing in your CMS’s Displays section would clear out in a couple of minutes since you mentioned that the scheduled events for the displays are working fine.
You may also try to clear the player cache in the CMS Task section by running the ‘Drop Player Cache’ task. To do so, click on the row menu of that task. and then click on run.
Next is to clear the player cache in the CMS’s Displays section. To do so, click on the row menu of the player reporting the fault, then click on Edit. Go to the ‘Advanced’ tab and tick on ‘Clear Cache Data’. The player should clear out any error logs in a couple of minutes after clearing its cache. However, if you notice an issue with your scheduled contents not showing on your display, then please try to get a screenshot of the ‘Player status log’ from your XfA player app for us to have a clue on what the player is doing to give us a hint on what could be causing the issue. To do so, you can find the steps here.
thank you for your response, I have tried your suggestions but the situation remains the same. The fault remains constantly against the display and the log entry re-appears every 4 minutes and remains there for 2 minutes.
Your are correct this was only noticed after manually upgrading the player to XfA V4 R410, because this DSDevices DSDA1 media player was supplied with an older XfA on Android 14 and would not upgrade through our hosted CMS 4.4.1. All of our other models of DSDevices media players (a mixture of DSCS9 and DSCS9X units) have upgraded correctly through our hosted CMS 4.4.1.
We are not sure why an entry keeps occurring and then disappearing from the log and then remaining as a fault on the display screen. The log message (listed below) seems to be indicating a missing argument whilst producing the players detail line in the CMS display section.
Xibo\Entity\DisplayEvent::eventEndByReference(): Argument #3 ($refId) must be of type int, null given, called in /sites/deploy/4.4.1_airblocks/lib/Xmds/Soap6.php on line 202
We have had issues with some APP permissions on this new DSDevices DSDA1 player which is running Android 14, permissions needed to be changed to allow Xibo and TeamViewer to auto-start. Although we have resolved these issues, I wonder whether there are any other permission problems causing this issue?
We have know un-installed Xibo R410 and re-installed on this particular DSDevices DSDA1 media player supplied with Android 14, the error is no longer being reported. We can only assume something went wrong during the upgrade to R410, which left an orphan error message in the players log.