Breaking changes
If you wish to update your previously installed devices to v4.0, first you have to consider the following:
If you have 2.x version, you have to update to version 2.21.06.x first
If you already have a 3.x version you can update from any subversion of 3.x to 4.0
Aternatively you can update the device from any version manually through the Install application function, or with USB storage!
Version 4.0.33
August 31, 2023
Bug fixes
- Fixed an issue where the Lock feature got the device into a restart loop
Version 4.0.32
August 16, 2023
New Features
- Added a Network watcher that will watch out for invalid network disconnects that could happen on some devices
- Implemented the new V2 Preview API
Improvements
- Added more consistent network type mapping in the Screen info
- Added a restart after the device wakes up from Working hours. This will help the device release memory which was invalidly held by the WebView
- Improvements were made to the cache rotate logic
- The Clear cache feature was improved with a page navigation to avoid problems caused by the current content being loaded in the WebView
- Unsupported Android versions now will be reported in the Screen info
- Added new metrics to the device statistics that will show how many times did the application crash on the device
Bug fixes
- Fixed an issue where videos from bound folders were not cached correctly
- Fixed an issue where a corrupted temporary metric cache file could cause the metric uploading to not work properly
Version 4.0.23
June 27, 2023
Bug fixes
- Fixed an issue where registering the device with a chosen content assigned to it only loaded the content after a content refresh command
Version 4.0.22
June 23, 2023
Improvements
- Crash handling was improved: Now the application will restart the device after 3 Android OS or WebView crashes It will also dump the system logs before device restart to help in identifying issues
- Improved log uploading with System log and System report options
Bug fixes
- Fixed an issue where missing content resources were always rechecked on the server
- Fixed an issue when in some cases the application could not navigate to the assigned content
Version 4.0.20
June 06, 2023
Bug fixes
- Fixed an issue where the application's user-agent suffix got multiplied when the WebView crashed
Version 4.0.19
May 30, 2023
Improvements
- Added check for more crash message types to the application's crash watcher.
- Removed the old and unused firmware update URL on Qbic devices.
Bug fixes
- Fixed an issue where Working Hours was not working on Saturdays.
- Fixed an issue where on certain devices the application could not load the content and was not reacting to the Refresh content command.
Version 4.0.15
May 15, 2023
New Features
- UDP server, and the ability to send custom UDP messages, was added to the application.
Improvements
- Added a 15-minute timeout before restarting the application to the application process watcher to give the user enough time to change settings in the Settings application.
- Improved the device analytics metric collection algorithm to provide more accurate measurements.
Bug fixes
- Fixed an issue where the application was not refreshing the resource validity in the cache.
Version 4.0.13
May 08, 2023
Improvements
- From now on, when the WebView process crashes, the application UI process will restart instead of the device.
Version 4.0.12
May 04, 2023
Bug fixes
- Fixed an issue where the Working hours mode if not set caused a crash
- Fixed an issue where the Advanced configuration default values were not handled properly
- Fixed an issue where the debug mode could not be immediately turned off
- Fixed an issue where forcing a device API could cause a crash
Version 4.0.10
May 03, 2023
New Features
- Added the Advanced configuration feature
- Added Screen mode for the Working hours
Improvements
- Improved system error handling
Version 4.0.6
March 20, 2023
Bug Fixes
Fixed an issue when Rapid preview mode was selected on the device but preview pictures were not created on content page change
Fixed a bug where invalid encoding was used on font resources loaded from the cache