Inspired Signage XPress v2.2.7.20182

Last Updated: Jul 09

Changes in this release:

  • Improved support for USB HID touch screens, touch screens which report the events under multiple top-level HID collections now work.
  • USB HID devices with application collections in the digitizer page (pen, light pen, touch screen, touch pad and white board) are now recognized as input devices.
  • Improved error checking and reporting in the SD card driver for better diagnostics.
  • Improved SD card initialization procedure for increased card compatibility.
  • The SD card driver now retries failed reads and writes up to two times for improved robustness.


Bug Fixes:

  • Some movement events could be ignored with touchscreens that do not always return both the X and Y coordinates on every event when only one coordinate changed.
  • Crashes may occur when accessing content on password protected HTTP servers.
  • The amx-is-spx-1300 package was missing from the IS-SPX-1300 build, this has no functional influence and will be automatically installed when updating the firmware from 2.2.6 to 2.2.7 on an IS-SPX-1300.
  • IS-SPX players would not boot when connected to a ViewSonic touchscreen TD2340, and possibly other makes and models, due to a driver crash.
  • The system would crash and reboot if the RTC was accessed by a program at the same time as the kernel syncs the RTC to the system time due to incorrect initialization of a mutex, note that this race condition is extremely rare.
  • The system would crash and reboot if the E-EDID information returned by an HDMI sink (e.g., display) has no video mode timing information in the base block.
  • The SD card driver could issue two requests simultaneously to SD card after an SD card error.
  • The SD card driver could do double completion of some requests upon an SD card error or unusual command response timing.
  • The SD card driver did not report CRC errors in command responses.
  • The SD card driver did not set the DMA segment length requirements correctly, although this did not have any effect in practice.
  • The SD card driver did not correctly re-initialize itself after the failure of an SD read or write command and would corrupt data on subsequent write commands, the corruption would appear as a two byte shift of the written data blocks.
  • The read fatigue and limited data retention compensation mechanism introduced in 2.2.6 (in the hwwatchdog daemon) could trigger a bug in certain SD cards that causes a temporary failure of read and write commands and then degenerates into corruption of the SD card's content which make the system gradually fail and boot into recovery mode. On units with affected SD cards this problem can be triggered every 6 months. It can also be triggered about 40 minutes after a firmware is updated from 2.2.5 or earlier to 2.2.6 via the firmware update feature, but not if installed from the recovery console. The condition that triggers the bug in these SD cards is now avoided. This problem has been observed only with some manufacturing batches of SanDisk 2GB SD cards.
  • Crashes may occur when accessing content on password protected HTTP servers and /or IS-SPX players.