What "Certified Hardware" means. Only entries listed below as
Certified or Certified with limits are Certified Hardware
under ScreenTinker agreements. ScreenTinker has tested those models, keeps a unit of each in its
test lab, and support obligations attach to them.
What it does not mean. Entries listed as Community reported, Known issues
or Not supported are not Certified Hardware and carry
no support commitment. They are published because knowing what other people
have run, and what does not work, is useful when you are choosing what to buy.
ScreenTinker is open source and runs on far more hardware than this list. Certification is a
statement about what ScreenTinker has tested and will support, not about what is capable of
running the software.
Certified (5)
Tested by ScreenTinker, works, and supported under ScreenTinker agreements. A unit of each is kept in the ScreenTinker test lab for regression testing.
Web player, running in an roHtmlWidget under the BrightSign autorun package (autorun.zip: autorun.brs plus st-bridge.js)
Maximum resolution
1920x1080
Validated on
2026-08-07
Validated by
ScreenTinker
Tested against
1.9.33
Minimum ScreenTinker version
1.9.33
Manufacturer end of life
Not recorded
The player code is the ordinary web player, unmodified. The BrightSign-specific part is the host around it: autorun.brs owns the widget lifecycle, identity across reboots, recovery from a dead server, and video-mode and multi-output control, with st-bridge.js as the page's half of that contract. This package has to be installed on the player.
BrightSign's HTML widget does not reliably come back from a page reload. That is why the host exists: on deploy the page asks for a restart and autorun.brs tears the widget down and builds a new one, which is a restart the operating system actually performs. Without that host a deploy can darken the panel until someone power-cycles it.
The same hardware can also run the ScreenTinker server itself rather than only the player. That is a separate configuration with its own requirements, listed below.
#BrightSign Series 5, running the ScreenTinker server
Manufacturer
BrightSign
Model numbers
XT245
Category
Media player
Operating system
BrightSign OS 10
ScreenTinker player
The ScreenTinker server itself, as a real Node process, with the player running in the widget beside it
Maximum resolution
1920x1080
Validated on
2026-08-15
Validated by
ScreenTinker
Tested against
1.9.36
Minimum ScreenTinker version
1.9.36
Manufacturer end of life
Not recorded
This is the whole system on one box: no separate server to host, and the panel keeps working if the network does not.
BrightSign OS 10 is required, and is not optional. The server runs on the Node runtime that ships with OS 10. OS 9 can run the player but cannot run the server.
NVMe or SSD storage is REQUIRED. Do not run the server from an SD card. A server writes continuously, to its database, its write-ahead log, its media library and its logs, and that load will wear out an SD card and take the site down with it. This is why the entry names the XT245, which takes a 128 GB NVMe drive, rather than the Series 5 generally.
Server mode is off unless you ask for it. It listens on port 8181.
Install from the autorun-server.zip and server-payload.zip assets published with each release. The payload installs in two stages; a single combined archive is not usable because the boot-time archive reader does not handle one that large.
Newer than the player configuration, which has been running since 2026-08-07. Treat it accordingly.
The panel is 1280x800. It was tested with 1080p content, which the device downscales to fit, so a 1080p playlist plays correctly but is not shown at full resolution.
Requires ScreenTinker 1.9.4 or later. Earlier Android builds could strand a panel on "waiting for content" after a restart, with no recovery short of clearing the app and re-provisioning (issue #162, fixed 2026-07-10).
Tested on Chrome and Firefox. Edge is expected to work but has not been tested.
Point the browser at /player on your server. Nothing is installed.
No minimum browser version has been established.
There is no ScreenTinker version floor either. The browser has been a supported display since the first release, and it is re-tested with the current one.
Community reported (3)
A user reports that this works. ScreenTinker has not tested it and keeps no unit. These are NOT Certified Hardware and carry no support commitment.
ScreenTinker holds no Tizen hardware. This entry rests on user reports and carries no support commitment.
Tizen is not turnkey. There are three install routes and each has a catch.
The released .wgt is unsigned and is for inspection only. Samsung distributor certificates are locked to the DUID of the signer's own panels, so a .wgt we signed would not install on yours.
Native install needs a Samsung certificate tied to each panel's DUID.
The SSSP URL Launcher route works without per-panel signing on your side: the server hosts sssp_config.xml and the panel installs itself, then reinstalls whenever the version bumps.
The simplest route is to point the panel's browser at /player, with no signing at all.
There is no in-app update for this player. A panel keeps its installed build until it is reinstalled.
Requires ScreenTinker 2.0.8 or later. A content security policy added in 2.0.0 black-screened Tizen 5.0 panels and was removed in 2.0.8 (issue #330).
webOS 4.x, 5.x and 6.x, and webOS Signage 22 and later
ScreenTinker player
webOS .ipk shell around the web player
Maximum resolution
Not recorded
Validated on
Not recorded
Validated by
Community
Tested against
Not recorded
Minimum ScreenTinker version
2.0.8
Manufacturer end of life
Not recorded
Community contributed. No LG panel was available to ScreenTinker, so no unit is held in the lab and this carries no support commitment.
Installed from a USB stick or an SI server. No vendor signature is needed.
Built without LG's SCAP library, which LG's licence does not allow us to redistribute. Power control and self-update therefore need a local build with the LG SDK files in place. The dashboard hides those buttons on a panel that reports it cannot do them.
webOS 3.x and older are below the player's baseline and are shown a compatibility message rather than a black screen.
Android TV hardware in general is not certified. Individual models are listed separately when ScreenTinker has tested them.
With group sync enabled the player warms the next clip on a second video decoder shortly before each item boundary. Some chipsets allow only one decoder at higher profiles, and the second request can reclaim the decoder already playing. The picture holds, no error is raised, and the playlist stops advancing.
Reported on Xiaomi Mi TV P1 panels (issue #333) and fixed in 2.0.8. The chipsets that behave this way have never been identified.
Vega OS restricts video playback to 720p, so this cannot drive a 1080p sign at full resolution.
Memory on the device is not sufficient for reliable signage playback.
Do not buy this for ScreenTinker. It is sold alongside the Fire TV sticks that do work and is easy to pick up by mistake.
May be revisited.
Android panels, and why we recommend a player plus a display
No commercial Android signage panel or all-in-one commercial display has been validated to
date. If you have arrived here holding a listing for a white-label Android panel, that is the
gap you are looking at. It is not a judgement about that panel. It means nobody at ScreenTinker
has had one on a bench, so it cannot be certified and no support obligation can attach to it.
The recommended path is a certified player driving a commercial display over HDMI. The player
is the part that runs ScreenTinker, and it is the part that gets certified. The display
itself is not player hardware and does not require certification. Any commercial
display with an HDMI input will work, and you are free to choose it on the things displays are
actually chosen for: panel quality, brightness, operating hours, warranty and size.
That separation is deliberate. It keeps your display choice open, it keeps the part that runs
software cheap and replaceable, and it means a failed player is a swap rather than a
replacement screen.
Getting a device certified
If you need a specific model certified, contact ScreenTinker support and say which model and how
many screens are involved. Validation of non-certified hardware is a paid engagement for
reseller partners, and the result is published here whatever the outcome, including a
Not supported entry if that is what the testing shows.
If you are running something that is not on this list and it works, tell us. Community reports
are welcome and are published as Community reported. That is not certification, and it is
stated as such, but it helps the next person choosing hardware.