Skip to main content

Samsung Tizen Client URL Changes for Signagelive App (October 2025)

Giuseppe (Joe) avatar
Written by Giuseppe (Joe)
Updated this week

TL;DR:

  • On October 20th 2025, any Samsung Tizen players running Signagelive will be automatically updated to a new client version

  • No action is required unless you’re running a beta client or test URL. In such a case, you will need to ensure you’re using one of the URLs listed below to get the latest client updates.

  • For devices running Tizen 3.0 and above, this will include the newly added Screen Takeovers functionality.

  • Tizen 2.4 devices will still be updated to a new client version, but this version does not include Screen Takeovers, as this feature is not supported on this Tizen version.

To coincide with the launch of our Screen Takeovers feature for Samsung Tizen players, we will be updating the client version for all Samsung Tizen-based Signagelive players, regardless of the Tizen OS version they are running. This change is necessary to enable support for our Screen Takeovers feature on newer Tizen generations (3.0 and above) while maintaining compatibility with Tizen 2.4 devices. Read on to learn more about what this means.

What’s Happening?

As our Screen Takeovers features will not be supported on Tizen 2.4 devices, we are splitting the Signagelive for Samsung Tizen client into two separate builds. This means that existing installations will be automatically migrated to a new, appropriate URL.

  • Tizen 2.4 Devices: Will be migrated to a "legacy" client that does not include Screen Takeovers functionality.

  • Tizen 3.0+ Devices: Will be migrated to the "main" client, which supports Screen Takeovers.

Why is this happening?

Separating these installation URLs has become necessary because Screen Takeovers is unsupported on Samsung Tizen 2.4 devices. This change ensures that all Tizen device generations receive the appropriate Signagelive application version.

Key Changes and What This Means for You:

  • Automated Migration: When the update is released, your Tizen player(s) running our current production build (1.33) will automatically update to version 1.34 (as long as they have an internet connection and are connecting to Signagelive). This version includes new logic to automatically update the URL Launcher address for your player and then reboot. After rebooting, your player will be on version 3.03 and will have migrated to its new URL.

  • No Manual Action Required (for primary URLs): For devices configured with our primary production URLs (London and Sydney environments), this migration will happen automatically. This includes both landscape and portrait versions of the main apps.

  • URLs Not Migrated Automatically: Devices configured with other URLs (e.g., beta or other test URLs) will not be automatically migrated. If you are using such URLs, you will need to manually update your installation URL as per the table in the next section. Contact our support team if you’re unsure what this means or have further questions.

  • App URL Reporting: Both the new 1.34 and 3.03 clients will report the currently configured App URL as part of the system report, which will be visible in the System tab in Signagelive.

What are the new URLs?

Please refer to the tables below for the updated URLs based on your Tizen OS generation and Signagelive instance:

eu-west-2-1 (Signagelive London Instance):

ap-southeast-2-1 (Signagelive Sydney Instance):

Please note: The URL migration will work whether your current URL uses http or https, and with or without an ending slash (/). Only the relevant part of the URL will be updated, maintaining your existing protocol.

When is this change taking place?

October 20th 2025

This update ensures your Signagelive Tizen players continue to operate efficiently and, for newer devices, gain access to powerful new features like Screen Takeovers. If you want access our FREE Screen Takeovers feature, please get in touch using the form at the bottom of this page.

If you have any questions or experience any issues after the update, please contact our support team.

Did this answer your question?