ScreenBeam 750 Firmware
Note: Product is EOL and EOS
Current version
Version 2.15.46.0
- Release date: 2021, Jun 01
- Changes since 2.15.45.0
- Improvements and fixes
- Improve Miracast connection stability
- Fixed issue where the receiver may auto-reboot due to the oversized event log
- Fixed WiFi network name can't support the "_" character
- Fixed issue where some receivers may show blue/black onscreen and is offline in CMS
- Improve system security
Version 2.15.45.0
- Release date: 2020, Nov 06
- Changes since 2.15.44.0
- Improvements and fixes
- Improves Miracast connection stability for Windows 10 build 19H1/19H2/20H1 (#9805)
- Updated behavior for the Display Off state to resume only when waking On Connect or On Scan by a client device (#11310)
- Fixed bug where CMS fails to set NTP time server (#11128)
- Fixed bug where time zone and daylight saving time settings can be reset to default by CMS (#11180)
- Fixed bug where an unexpected black screen may occur after a projector/display is turned off completely (not sleep) and back on (#10865)
- Fixed bug where ScreenBeam cannot be seen from Miracast client devices after a crash event occurred and could not self-recover (#9791)
- Fixed bug where ScreenBeam cannot be seen from Miracast client devices after the P2P Operation Channel is changed (#10891)
- Fixed bug where the receiver may continuously fail to connect to CMS server (#9992)
- Fixed issue where ScreenBeam may connect to the wrong CMS server address if "aeisbcms" hostname and FQDN pointing to different IP (#9873)
- Provides CMS the ability to export receiver MAC address from CMS (#9563)
- Deprecates support for Rx Log upload timer (#9420)
Version 2.15.44.0
- Release date: 2020, Jan 15
- Changes since 2.15.41.0
- New features and enhancements
- Display Sharing Mode - Options for how ScreenBeam should behave
- Single (default) - ScreenBeam supports only 1 connection at a time. The first Miracast device to connect will have full ownership of the display.
- Quick Switch - ScreenBeam supports only 1 connection at a time. However, another Miracast device in the same room could connect and take over the session.
- 4-digit PIN option for Miracast connection
- Display Sharing Mode - Options for how ScreenBeam should behave
- Improvements and fixes
- Mitigates random Miracast disconnect from Windows 10 1903/1909 systems in a certain environment (#8798)
- Fixes occasional black screen with only mouse cursor is shown upon Miracast connection for some Windows 10 systems (#8776)
- Fixes issue where the receiver is not able to re-connect to WiFi AP after renewing the EAP-TLS certificate (#8925)
- Fixes the black screen and quick disconnect from some Android Miracast devices (#9085)
- Improves Miracast pairing success rate (#8310)
- Fixes Wi-fi authentication passphrase cannot support backslash \ and apostrophe ' characters (#7210/#7162)
- Updated self-signed certificate for Local Management Interface website
Version 2.15.41.0
- Release date: 2019, Mar 29
- Changes since 2.15.39.0
- New features and enhancements
- Includes option to disable UPnP broadcast for CMS discovery
- Enables receiver's event logging is on by default
- Includes option to extract event logging from Local Management
- Improvements and fixes
- Improves Miracast stability for certain network environment
- Improves to system network to avoid permanent IP conflict
- Improves Miracast support for some Android devices (i.e. Huawei P9)
Version 2.15.39.0
- Release date: 2018, Nov 05
- Changes since 2.15.35.0
- New features and enhancements
- Allow Force Disconnection - This allows a second 10 Miracast client device to connect by kicking off the existing Miracast session.
- Improvements and fixes
- Improves Miracast initial connection success rate
- Improves Miracast connection stability for a Surface device with Marvell WLAN adapter v15.68.9125.57
- Fixes system stability where the receiver may fail to start up and gets stuck in the "Actiontec" logo
- Fixes issue where occasionally the receiver is not discover-able from any Miracast client device
- Fixes issue where the receiver cannot perform a firmware update over the Local Management
- Changes to the duration setting for "Auto-reboot receiver when idle for" feature