Safe mode

From SpinetiX Support Wiki

Jump to: navigation, search
Safe mode is a reduced-functionality state of the HMP which is automatically triggered when the HMP is forced to reboot three times in less than 30 minutes, due to content related problems.

Description

Screen capture while the HMP is in Safe mode

Safe mode is a special operating mode of the player that is meant to prevent rebooting in a loop, when the content cannot be rendered. It is automatically triggered whenever then player reboots three times in less then 30 minutes - when that happens, the retrival and the rendering of the content are disabled - a "Safe Mode" text box along with a small blinking square and a slowly changing background color from white to black (to avoid screen burn-in) is shown on the screen. See below why the player enters into Safe mode.

After one hour, the player automatically reboots back into normal operating mode in order to check whether the content can be displayed; if the content-related problem persists, the player will most-probably end up in Safe mode again. See below what you should do when the player is in Safe mode.

Note Notes:
  • Safe mode should not be confused with Recovery mode, which is a special operating mode as well - in both cases, the user content is not rendered, however the LEDs activity and what is displayed on the screen are different. The major difference is that the player is entering into Safe mode due to content problems, while for Recovery mode, the cause is a corrupted file-system or a hardware hardware fault.
  • If some content is published onto the HMP, the content is displayed, however the "Safe Mode" text box is not removed - a device reboot is required for it to enter into the normal operating mode.

What to do when the player is in Safe mode

This is what you should do when the player is in Safe mode:

  1. Is the player configured to retrieve content from an external server using Scheduled Download or Pull Mode?
    • If so, then disable that to avoid a faulty content being retrieved again.
  2. Has any content been added recently onto the player?
  3. Check whether one or more videos outside the player specs are used.
  4. Check whether your Elementi project is not too charged up and / or try to optimize it.
    • If multiple images are used, but displayed as thumbnails instead, then you should reduce the size of those images before using them.
    • If multiple videos are used in the same time, make sure that they are not all at full HD resolution - normally, only one would be used as full-screen, so the others should be re-encoded at a lower resolution according to the area they occupy on the screen.
    • Some layer effects or playlist transitions need more resources than others - try using none, less, or fade to white / black ones instead.
    • Each layer box decoration increase the complexity level of the content and that should be avoided, especially on video layers.
  5. Are you using data-driven widgets within your content?
    • If so, check whether the data source is not too large to be parsed - for instance a calendar might contain a lot of expired events and thus grow in size, so you need to remove those old events.
  6. Check the player.log for any indications regarding the content at fault - for instance, whether the player reboots after the same amount of time or always after rendering a certain resource (like a video outside the player specs) etc.

If none of the above helped, then generate a standard report from your player and send it to a local partner near you or to SpinetiX Support. Make sure to include a copy of your content as well.

Why the player enters into Safe mode

The player has a software watchdog that observes the internal processes and if something goes wrong, for instance, no frame has been rendered within 60 seconds (or 30s before 3.1.0 firmware release), it will trigger a device reboot.

If there are three reboots in less than 30 minutes, it's clear that something is not right and some measures must be taken (see above). If the player is forced to reboot again, then retrieving content from external servers is also disabled, to avoid a faulty content being retrieved this way.

Examples of content that could trigger Safe mode:

  • JavaScript infinite loops.
  • Content out of the player specifications or requiring too much memory.
  • Data source too large to be parsed - for instance a calendar containing a lot of expired events (in which case, the solution is to remove those old events).
  • Scheduled content that is not protected with spx:start-at-random-time attribute.
  • Synchronized content having items for which the duration cannot be computed.

See also

This page was last modified on 21 September 2018, at 11:32.