In this version, we've updated the loading sequence to not dependent on NTP (Click here to learn more about NTP) server to act properly. The reason behind this decision is to remedy situations where on some user's network, the NTP clock is providing false or delayed information, resulting in the application to stall during the loading screen. Since the NexSigns application does not require a valid device time to be present, the development team had decided to remove the device time requirement.

Although the NTP is no longer a requirement during the loading, It is important to note that many features still require NTP to function properly. Here are several examples of features that may not work if NTP is not correctly broadcasted

• Daily maintenance window may not be running at the predefined hours
• Multimedia channel asset with display date/time range may not work as expected
• Time condition channel may not work as expected
• and more...