2 Data Maintenance and Version Upgrades

Data Storage and Cleanup

Layouts, columns, numbers, backgrounds and fonts live on the device. Normal upgrades never overwrite them, and nothing depends on the cloud.

Recommendations:

• keep the original files of important backgrounds and fonts on a computer;
• for backup or restoration of terminal data, ask the supplier for help;
• never delete application data on the device yourself, nor replace it with files from unknown sources;
• if unsure before an upgrade, have the supplier take a backup first.

Cleanup rules:

• numbers are auto-cleaned about a day after creation, checked hourly;
• login state lasts 7 days by default and extends with use;
• backgrounds, fonts and layouts persist until manually deleted or replaced;
• only the current background is kept — the old one is cleaned after a switch.

Before Upgrading

• confirm the package comes from the supplier — file names usually carry the version, e.g. lynx-signage_1.0.3_arm64.deb;
• upgrade at off-peak times; the screen blanks briefly while the publishing program restarts;
• keep power stable — never cut power mid-upgrade;
• keep the previous package for supplier troubleshooting;
• read the supplier's release notes to confirm no breaking changes.

Upgrade Steps

Performed by general technical staff; replace the sample address and version with real values. The first line runs on the managing computer to upload the package; log into the device and run the last line to upgrade:

scp lynx-signage_1.0.3_arm64.deb lynx@192.168.1.50:~/
ssh lynx@192.168.1.50
sudo apt install -y ./lynx-signage_1.0.3_arm64.deb

This upgrades the device in place with no reconfiguration. The package updates and restarts the publishing program automatically; the screen may lack a picture for a moment, usually recovering within 1~2 minutes. Do not repeat the upgrade command.

Post-Upgrade Checks

• does the screen return to the publishing display;
• does the browser log in normally;
• are columns, numbers, backgrounds and fonts intact;
• edit one number and confirm it reaches the screen automatically;
• toggle a DPMS mode once and confirm the screen responds.

The browser may cache the old page — press Ctrl+F5 to hard-refresh if needed. Login state usually survives; if prompted, log in with the original credentials.

Package names carry the version; contact the supplier to confirm the current device version.

Failed Upgrades and Rollback

If an upgrade is interrupted or the system misbehaves afterwards:

• keep the device powered; do not retry the upgrade repeatedly;
• do not delete application data on the device;
• record the on-screen message and current symptoms, then contact the supplier;
• keep the old package, but whether rollback is possible is up to the supplier — never downgrade on your own.

Replacing the Main Unit or Storage

Before replacing the terminal's main unit or storage, contact the supplier for data migration and recovery:

• swapping the HDMI monitor, keyboard, mouse, router or network cable has no impact;
• replacing the main unit or storage needs the supplier to restore data and finish device setup;
• never clone the system or swap storage yourself — the device may fail to boot or lose data.