Back

Screen Sharing v2.58 Beta

v2.58

•

Beta

•

Release Candidate

Android 16 Compliance

Montage now supports 16 KB memory page sizes on 64-bit Android devices, targets Android 16 as the receiver's target SDK, and the DisplayNote Android client app itself now also targets Android 16 (API level 36), keeping the whole suite compliant with Google Play's target SDK policy and unblocked from future updates and new installs.

Session ID Visibility Control

Teachers can now toggle the visibility of the session ID on the receiver screen separately for shared-screen and floating-ID contexts, so it no longer obstructs shared content. Session ID over a shared screen is off by default.

Fill Display Option for Full-Screen Sharing

A new "Fill Display" option lets the client temporarily match its resolution to the main display during screen sharing, so shared content fills the screen instead of leaving black bars when aspect ratios differ.

Unified Meeting IDs

Receivers can now use a single 8-character Unified Meeting ID (e.g. BBMG-WBRJ) instead of switching between a 6-digit cloud code and a 10-digit offline code. The code is persistent across reboots, works LAN-first with cloud fallback, and stays globally unique. The existing 6-digit code remains the default for now, switching a receiver to a Unified Meeting ID is a setting available both centrally via Central Management and directly on the receiver.

Backward compatibility: older clients can only read the numeric 6-digit/10-digit code, so they won't recognise the new alphanumeric Unified Meeting ID and can't join a receiver that's been switched to it. Because the 6-digit code stays the default on every receiver, simply updating changes nothing for existing rooms, this only matters once someone deliberately opts a receiver into the Unified Meeting ID setting. To join a receiver running on a Unified Meeting ID, clients need to be on v2.57 or later. When switching a receiver to Unified Meeting ID, the setting flags this to the user so they're aware participants will need the latest client to join.

Native Apple Silicon Support

The DisplayNote macOS app now runs natively on Apple Silicon (ARM64) instead of via Rosetta 2, ahead of Apple's deprecation of Rosetta support in upcoming macOS releases. This improves performance and compatibility on modern Mac hardware.

  • Fixed: no system notification was shown on macOS when attempting to use touchback control while accessibility permissions were denied

  • Fixed: AirPlay service Bluetooth Low Energy announcement was failing on the receiver

  • Fixed: the teacher was not appearing at the top of the participant list

  • Fixed: the session button was not shown as the active button when the teacher was sharing their screen and the session panel was open

  • Fixed: the app could not be reopened after closing while a client was connected, showing a "the app is already running" error

  • Fixed: the app crashed on Android 8 devices shortly after opening

  • Fixed: the Android receiver showed a server error message for an invalid license key

  • Fixed: Windows Defender showed a warning about the installer

  • Fixed: AirPlay audio broke when using grid view

  • Fixed: 'Broadcast to displays' could not be enabled via IR when the device was offline

  • Fixed: description text for the Streaming settings option went out of bounds on the desktop client

  • Fixed: the B2P popup showed incorrect information when the internet connection was removed

  • Fixed: GoogleCast did not work after disconnecting and reconnecting Wi-Fi on AOPEN Chromebox OPS devices

  • Fixed: a crash when restoring a Wi-Fi connection

  • Fixed: a crash during GoogleCast presenting

  • Fixed: an AirPlay client could connect to the receiver without a meeting having been created

  • Fixed: clients on Newline STV devices could not connect to Broadcast-to-Panel (B2P)

  • Fixed: the Floating ID indicator disappeared a few seconds after reconnecting the network

  • Fixed: an occasional crash during session teardown

  • Fixed: an occasional crash during Google Cast service teardown

  • Fixed: the Windows receiver closed if a user cancelled an in-progress update

  • Fixed: Session ID visibility option information on the Android receiver that didn't match the intended design

  • Fixed: the Android receiver could get stuck on launch when TalkBack accessibility was enabled

  • Fixed: a crash (SIGABRT / std::bad_alloc) on Newline STV receivers that could block an OTA update from completing

This version is for review only and should not be included with Production firmware.