I’m testing Xibo before implementing it more broadly.
When I revoke authorization from Android monitors, they keep working until the Xibo screen appears, and when I authorize them again, they return to operation on their own after a moment.
With Tizen monitors it’s not like that - they immediately go to the CMS connection configuration screen, which seems rather inelegant, and even if I authorize them, you have to physically go to them and click “Connect to CMS” or perform a restart.
Is there any way for the monitor to, first of all, be able to reconnect to the CMS automatically after authorization is revoked, and in the meantime display something more… let’s call it presentable
Thank you for posting this issue. Please can you open a support ticket on the Xibo help desk so we can discuss and troubleshoot this issue further? You can create an account on the Xibo Signage web portal, then go to the Tickets page in My Account to create a new support request.
When you open the ticket, can you put this for the attention of Daniel and also include:
The model number of your Samsung signage display.
The version of the Xibo for Tizen player you are using.
I look forward to hearing from you in the help desk and resolving this issue with you.
I have an update for all Tizen testers/users about this behaviour. It has been replicated and reported to the developers for a solution to this behaviour.
The issue has been escalated to the developers, who will further investigate the behaviour and them prepare a fix. I don’t have a release date at this time as the issue was only reported a few hours ago. The developers will provide an update when they have completed the next steps of the issue investigation.
I have made a note to share the update with you as soon as I hear from them.
Hi Jakub. I have added an additional note to the issue report that you are looking for an urgent fix for your testing. As soon as I have a fix for you to try I have a note to share that with you.
In short, it’s being resolved now and I will share the fix as soon as it is available for you to test.
I’m having a problem with versions 407 and 408.
The issue is that the screens disconnect from the CMS and can’t re-establish the connection.
Reboots don’t help — some monitors are connected via cable and others via Wi-Fi.
Currently, all of them show the status: Registered: False.
Reinstalling the app helps, but only for a few hours.
I’m using the white-label version, and I’m quite certain that when I was using the original Xibo version, there were no issues with the screens disconnecting from the CMS.
On one of the monitors, I can see 1127 failed connections to XMDS, even though the monitor has a stable internet connection all the time.
Hi Jakub. I believe we are already discussing this issue in a ticket on the help desk.
There are some overlapping issues here that as mentioned in the help desk, should be addressed in the upcoming R409 release, which I will share with you as soon as I have a copy or it is released.
This is very important for me.