Neat Preview Channel Firmware

Last updated on January 21, 2026

If you would like to receive email notifications for new releases, please subscribe here.

This document details what features, improvements, and bug fixes are new in the Neat Preview channel when compared to the Stable update channel.

For release notes covering NeatOS updates available only through the Microsoft Teams Admin Center (TAC), see our dedicated Microsoft TAC release notes page.

1. Introduction

Neat OS 25.4.2

On Thursday, January 15, we rolled out an update for Neat OS (25.4.2) to our Preview Channel.

Check out section 3, What’s new, to see the latest updates for Neat devices, Zoom, and Microsoft Teams.

Head to section 4.1 and 4.2/4.3 for Improvements and Bug fixes, and check out section 5 for Known issues.

2. Important information about the Preview Channel

At Neat, we use two channels for our software updates to give you the best experience.

Stable Channel – This is where our finalized, production-ready updates are released, ensuring everything runs smoothly in your environment.

Preview Channel – Before updates go live, we release them here for a few weeks. This lets you explore new features early and provide feedback.

The best part is that you already have access to both channels! So, whether you prefer rock-solid stability or an early look at what’s coming, you’re covered.

Please note that Preview updates are for evaluation and are not yet fully supported. We do not recommend installing Preview software on Neat devices used in a production environment. Ideally, you should use a Neat device that is in a lab or a lower-risk user environment to try out the Preview software. And please report any feedback or issues you find while testing to us using the steps outlined in section 7. Getting help from Neat. We would love to hear from you!

Using Neat Pulse? Change the update channel in the device settings within Neat Pulse controls or via a room profile.

For Zoom Neat devices: Go to System Settings → System → Software Update → Update Channel on Neat Pad, Neat Board, and Neat Frame.

For Microsoft Teams Neat devices: Navigate to Settings → Device Settings → System → Software Update → Update Channel on Neat Pad and Neat Board.

If there is already a newer version available when you move your Neat device to the Preview channel, your Neat device will automatically download the new version and upgrade between 1:00 a.m. to 5:00 a.m. local time on the next day.

Important: Two-phase update behavior (Android 13 migration)

If you move a device to the Preview channel or schedule an update via Neat Pulse, ZDM, or TAC, the update will complete in two stages:

Stage 1 – Initial update
When triggered manually or by schedule, the device installs an interim transition build of NeatOS 25.4.2 (Android 10).

Stage 2 – Final update to Android 13 (overnight)
The migration to NeatOS 25.4.2 on Android 13 completes automatically during the device’s overnight update window (typically between 1:00–5:00 a.m. local time).

The device must remain powered on and connected to the network overnight for the update to complete. Devices that are powered off overnight will remain on the interim version until the next overnight update window.

Heads up: Google Meet Rooms is now Generally Available on Neat Devices!

Google Workspace customers can now use Google Meet Rooms on Neat devices. Be sure to read the important note below for new devices and follow the Google Meet setup guide before installing.

3. What’s new in Neat OS 25.4.2

	Preview release (October 20, 2025)	Preview release (December 17, 2025)	Preview release (January 10, 2026)	Preview release (January 15, 2026)	Preview release (January 24, 2026)
The Neat firmware builds:	Android 10 – Neat OS 25.4.0: Neat Pad firmware: NFA1.20251003.0226 Neat Bar firmware: NFB1.20251003.0010* Neat Board firmware: NFC1.20251003.0010* Neat Bar Pro firmware: NFD1.20251003.0013 Neat Bar Generation 2 firmware: NFE1.20251003.0013 Neat Frame firmware: NFF1.20251003.0015 Neat Board 50 firmware: NFH1.20251003.0013 Neat Board Pro firmware: NFK1.20251003.0013 Neat Center firmware: NFL1.20251003.0015* Neat Pulse Agent: Pulse Agent 2.0.31 * Only available for A10 only available for A10. A13 pending new Display app supporting AOSP *** Already on A13 Android 13 – Neat OS 25.4.0**: Neat Pad firmware: NFA2.20251003.1308 Neat Bar Pro firmware: NFD2.20251003.0115 Neat Bar Generation 2 firmware: NFE2.20251003.0115 Neat Board 50 firmware: NFH2.20251003.0115 Neat Board Pro firmware: NFK2.20251003.0115 Neat Pulse Agent: Pulse Agent 2.0.31	Android 10 – Neat OS 25.4.0: Neat Pad firmware: NFA1.20251003.0230 Neat Bar firmware: NFB1.20251003.0016* Neat Board firmware: NFC1.20251003.0016* Neat Bar Pro firmware: NFD1.20251003.0017 Neat Bar Generation 2 firmware: NFE1.20251003.0017 Neat Frame firmware: NFF1.20251003.0017 Neat Board 50 firmware: NFH1.20251003.0017 Neat Board Pro firmware: NFK1.20251003.0017 Neat Center firmware: NFL1.20251003.0015* Neat Pulse Agent: Pulse Agent 2.0.31 * Only available for A10 only available for A10. A13 pending new Display app supporting AOSP *** Already on A13 Android 13 – Neat OS 25.4.1**: Neat Pad firmware: NFA2.20251114.0623 Neat Bar Pro firmware: NFD2.20251114.0621 Neat Bar Generation 2 firmware: NFE2.20251114.0621 Neat Board 50 firmware: NFH2.20251114.0621 Neat Board Pro firmware: NFK2.20251114.0621 Neat Pulse Agent: Pulse Agent 2.0.31	Android 10 – Neat OS 25.4.0: Neat Pad firmware: NFA1.20251003.0230 Neat Bar firmware: NFB1.20251003.0016* Neat Board firmware: NFC1.20251003.0016* Neat Bar Pro firmware: NFD1.20251003.0017 Neat Bar Generation 2 firmware: NFE1.20251003.0017 Neat Frame firmware: NFF1.20251003.0017 Neat Board 50 firmware: NFH1.20251003.0017 Neat Board Pro firmware: NFK1.20251003.0017 Neat Center firmware: NFL1.20251003.0015* Neat Pulse Agent: Pulse Agent 2.0.31 * Only available for A10 only available for A10. A13 pending new Display app supporting AOSP *** Already on A13 Android 13 – Neat OS 25.4.1**: Neat Pad firmware: NFA2.20251114.0623 Neat Bar Pro firmware: NFD2.20251114.0621 Neat Bar Generation 2 firmware: NFE2.20251114.0621 Neat Board 50 firmware: NFH2.20251114.0621 Neat Board Pro firmware: NFK2.20251114.0621 Neat Pulse Agent: Pulse Agent 2.0.31	Android 10 – Neat OS 25.4.2: Neat Pad firmware: NFA1.20251114.0719 Neat Bar firmware: NFB1.20251114.0719* Neat Board firmware: NFC1.20251114.0719* Neat Bar Pro firmware: NFD1.20251114.0719 Neat Bar Generation 2 firmware: NFE1.20251114.0719 Neat Frame firmware: NFF1.20251114.0719 Neat Board 50 firmware: NFH1.20251114.0719 Neat Board Pro firmware: NFK1.20251114.0719 Neat Center firmware: NFL1.20251114.0717* Neat Pulse Agent: Pulse Agent 2.2.57 * Only available for A10 only available for A10. A13 pending new Display app supporting AOSP *** Already on A13 Android 13 – Neat OS 25.4.2**: Neat Pad firmware: NFA2.20251114.0723 Neat Bar Pro firmware: NFD2.20251114.0723 Neat Bar Generation 2 firmware: NFE2.20251114.0723 Neat Board 50 firmware: NFH2.20251114.0723 Neat Board Pro firmware: NFK2.20251114.0723 Neat Pulse Agent: Pulse Agent 2.2.57	Android 10 – Neat OS 25.4.2 (NEW): Neat Pad firmware: NFA1.20251114.0727 Neat Bar firmware: NFB1.20251114.0721* Neat Board firmware: NFC1.20251114.0721* Neat Bar Pro firmware: NFD1.20251114.0721 Neat Bar Generation 2 firmware: NFE1.20251114.0721 Neat Frame firmware: NFF1.20251114.0721 Neat Board 50 firmware: NFH1.20251114.0721 Neat Board Pro firmware: NFK1.20251114.0721 Neat Center firmware: NFL1.20251114.0719* Neat Pulse Agent: Pulse Agent 2.2.57 * Only available for A10 only available for A10. A13 pending new Display app supporting AOSP *** Already on A13 Android 13 – Neat OS 25.4.2 (NEW**): Neat Pad firmware: NFA2.20251114.0729 Neat Bar Pro firmware: NFD2.20251114.0727 Neat Bar Generation 2 firmware: NFE2.20251114.0727 Neat Board 50 firmware: NFH2.20251114.0727 Neat Board Pro firmware: NFK2.20251114.0727 Neat Pulse Agent: Pulse Agent 2.2.57
The built-in Zoom Room versions. More information about the latest versions of Zoom can be found here: New Updates for Zoom Rooms Android Controller New updates for Zoom Room Appliances	Zoom Room Controller software version: 6.5.5 (3902) Zoom Room Appliance software version: 6.5.5 (3902)	Zoom Room Controller software version: 6.6.10 (4464) Zoom Room Appliance software version: 6.6.10 (8678)	Zoom Room Controller software version: 6.6.10 (4464) Zoom Room Appliance software version: 6.6.10 (8678)	Zoom Room Controller software version: 6.6.10 (4464) Zoom Room Appliance software version: 6.6.10 (8678)	Zoom Room Controller software version: 6.6.10 (4464) Zoom Room Appliance software version: 6.6.10 (8678)
The built-in Microsoft Teams versions: More information about the latest versions of Microsoft Teams can be found here: Release notes for Microsoft Teams Rooms on Android What’s new in Microsoft Teams devices – Teams Displays and Panels	Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller): – Admin Agent (784): 1.0.0.202505080136.product – Teams Rooms Devices (MTRA 2.7.1): 1449/1.0.96.2025328903 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046 Microsoft Teams Displays: – Admin Agent (784): 1.0.0.202505080136.product – Company Portal (for Displays): 5.0.6423.0 – Display (Display U3A): 1449/1.0.95.2024062804 Microsoft Teams Panels: – Admin Agent (784): 1.0.0.202505080136.product – Panels: 1449/1.0.97.2025364207 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046	Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller): – Admin Agent (803): 1.0.0.202511230136.product – Teams Rooms Devices (MTRA 2.7.2): 1449/1.0.96.2025341701 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046 Microsoft Teams Displays: – Admin Agent (784): 1.0.0.202505080136.product – Company Portal (for Displays): 5.0.6423.0 – Display (Display U3A): 1449/1.0.95.2024062804 Microsoft Teams Panels: – Admin Agent (784): 1.0.0.202505080136.product – Panels: 1449/1.0.97.2025364207 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046	Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller): – Admin Agent (803): 1.0.0.202511230136.product – Teams Rooms Devices (MTRA 2.7.2): 1449/1.0.96.2025341701 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046 Microsoft Teams Displays: – Admin Agent (784): 1.0.0.202505080136.product – Company Portal (for Displays): 5.0.6423.0 – Display (Display U3A): 1449/1.0.95.2025111201 Microsoft Teams Panels: – Admin Agent (784): 1.0.0.202505080136.product – Panels: 1449/1.0.97.2025369004 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046	Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller): – Admin Agent (803): 1.0.0.202511230136.product – Teams Rooms Devices (MTRA 2.7.2): 1449/1.0.96.2025341701 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046 Microsoft Teams Displays: – Admin Agent (784): 1.0.0.202505080136.product – Company Portal (for Displays): 5.0.6423.0 – Display (Display U3A): 1449/1.0.95.2025111201 Microsoft Teams Panels: – Admin Agent (784): 1.0.0.202505080136.product – Panels: 1449/1.0.97.2025369004 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046	Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller): – Admin Agent (803): 1.0.0.202511230136.product – Teams Rooms Devices (MTRA 2.7.2): 1449/1.0.96.2025341701 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046 Microsoft Teams Displays: – Admin Agent (784): 1.0.0.202505080136.product – Company Portal (for Displays): 5.0.6423.0 – Display (Display U3A): 1449/1.0.95.2025111201 Microsoft Teams Panels: – Admin Agent (784): 1.0.0.202505080136.product – Panels: 1449/1.0.97.2025369004 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2509.6046

Keeping your Neat devices supported: The table above shows the compatible Neat firmware builds with Zoom and Microsoft Teams versions. To ensure you can receive technical support, please keep your devices on a supported software combination. If you experience an issue while using an older or unsupported version, Neat’s support team will ask you to update to a supported release before troubleshooting. For more details, check out our Neat Technical Support Policy.

New features in this release:

Introducing multi Neat Center support

Neat Focus: Enhanced control and flexibility

More natural meetings with Dynamic Framing

Neat devices now support Android 13

Google Meet Rooms is now Generally Available on Neat Devices

3.1. Introducing multi Neat Center support: Expanding coverage for larger rooms

We’re excited to announce multi Neat Center support, designed to deliver the same natural, engaging meeting experience you know from Neat Center — now optimized for larger, more complex spaces. With two Neat Centers working in sync alongside your front-of-room device, everyone in the room is captured clearly and consistently, no matter where they sit, stand, or move.

For even larger or more complex environments, you can now test adding a third Neat Center (beta) to further extend video and audio coverage using the same setup approach.

What does this mean for you

Equitable experiences in large rooms – Two Neat Centers extend both camera coverage and audio pickup, ensuring that more people are seen and heard just as clearly as those sitting up front. With three Neat Centers (beta), coverage can scale even further to support very large rooms and extended seating areas.

Dynamic framing that feels natural – Our machine-learning technology ensures each person is framed once, from the best possible angle, for a smooth and cohesive experience without duplication — even when multiple Neat Centers are active.

Smarter speaker tracking – Whether one or more people are speaking, or someone is moving across the room, Neat Centers collaborate with the front-of-room device to keep the active speaker face-on for remote participants.

A “camera crew” in the room – By automatically selecting the optimal view across multiple cameras, the system creates a seamless, production-like experience that makes remote attendees feel closer to the conversation.

Works seamlessly with Neat Focus – Use multi Neat Center support together with Neat Focus to provide an equitable view of participants around the table, while also highlighting presenters or key collaboration zones — including setups where one Neat Center is dedicated to presenter focus and others to participant coverage.

Why this change

As meeting rooms grow in size and complexity, so does the challenge of ensuring equity for everyone — both in the room and online. You told us you love how Neat Center brings clarity and focus, but needed a solution that scaled to larger rooms. Multi Neat Center support answers that call by extending coverage across larger spaces. The ability to test a third Neat Center (beta) gives organizations even more flexibility to explore advanced layouts and future-proof their largest rooms.

How it works

Pair two Neat Centers with your front-of-room device to enable synchronized coverage.

Optionally add a third Neat Center (beta) to test expanded coverage in large or custom deployments.

AI-powered technology dynamically selects the best camera angle to frame each participant once, whether seated, standing, or presenting.

Speaker Framing seamlessly follows the active speaker across devices, keeping remote participants connected.

Neat Focus zones can be applied to tailor views to key areas, spotlighting presenters or collaboration zones

3.2. Neat Focus: Enhanced control and flexibility

Neat Focus has been enhanced and gotten more flexible since 25.3. This evolution of Neat’s intelligent camera control feature is designed for larger and more dynamic meeting spaces — especially those equipped with one or two Neat Centers.

It builds on the original Neat Focus by adding new flexibility, improved camera logic, and smarter framing options, giving meeting organizers greater control over how people and areas in the room are shown to remote participants.

Key improvements in Neat Focus

1. Support for multi Neat Centers

Neat Focus now works with two Neat Centers (or three Neat Centers; beta) in addition to your main front-of-room device. You can pair both Neat Centers through your Neat Pad and assign them to different zones in the room — for example, one focusing on the presenter and the other on participants seated around the table. This makes Neat Focus much more powerful for larger rooms, where more than one camera angle is needed.

Please note that multi (two–three) Neat Center is only supported on Neat Generation 2 products (Neat Bar Pro, Neat Bar 2, Neat Board 50 and Neat Board Pro)

2. New framing modes

You can now choose between three camera display modes for each Neat Center:

Main frame – Mixing – Dynamically switches between showing one or both camera views depending on activity in the zones. This is the most flexible mode for capturing movement and interactions naturally.
Additional frame – Static – Always shows the selected Neat Center’s view, even when no one is in the zone.
Additional frame – Adaptive – Shows the Neat Center’s view only when someone enters the defined area (similar to how Neat Focus worked previously).

Each Neat Center can be configured individually, so you can tailor the setup to your specific room and meeting style.

Configuration

All Neat Focus settings are available locally in the Neat Settings on your Neat Pad.
From there, you can pair multiple Neat Centers, define focus zones, and choose between Static, Adaptive, or Mixing modes.

In short

Neat Focus now supports:

Two (three Neat Centers; beta) Neat Center for larger rooms
New framing modes (Static, Adaptive, Mixing)
Smarter, coordinated camera behavior across all devices
More natural framing that works hand-in-hand with Speaker Framing

Together, these improvements make meetings feel more immersive, giving remote participants a clear, consistent view of everyone in the room.

3.3. More natural meetings with Dynamic Framing

Dynamic Framing is our new AI-powered camera feature that makes sure everyone in the room is clearly seen—no matter where they sit or move.

By using intelligent coordination between your main device and any paired Neat Centers, Dynamic Framing automatically picks the best camera angle for each person, framing them naturally. The transitions between cameras are seamless, creating a smooth, “camera crew” feel that follows the flow of conversation.

The result? A more natural, inclusive meeting experience where remote participants feel like they’re right there in the room.

Please note that Dynamic framing is only supported on Neat Generation 2 products (Neat Bar Pro, Neat Bar 2, Neat Board 50 and Neat Board Pro)

3.4. Neat devices now support Android 13

We’re excited to share that select Neat devices are now ready to test Android 13 as part of this preview release. Android 13 brings stronger security and a modern foundation for future innovations across Neat devices.

This early access gives customers a chance to explore Android 13 and help us ensure everything runs smoothly before full certification.

Which devices can try Android 13

You can try Android 13 on the following Neat devices (as a preview)

Neat Pad
Neat Bar Gen 2
Neat Bar Pro
Neat Board 50
Neat Board Pro

These devices will remain on Android 10 in this release:

Neat Bar (Gen 1)
Neat Board
Neat Frame (Android 13 will come in a future update)

Neat Center is already running Android 13, so when you move your device to this Preview, it will just get updated firmware with some new features. The operating system will remain the same.

What this means for you

Early access to Android 13: Get a first look at Neat’s new Android foundation and help validate the experience.

Improved performance and security: Benefit from Android 13’s enhanced reliability, data protection, and system stability.

Future-ready platform: Prepare your Neat devices for upcoming capabilities built on the Android 13 platform.

Before you begin

If your organization uses Microsoft Intune policies, please ensure they allow Android 13 before transitioning.

Some organizations set minimum or maximum Android version limits, which may block the sign-in until updated.

You’ll also need Microsoft Intune configured for the AOSP Device Management version of Microsoft Teams if testing with Teams Rooms.

Important

Android 13 is currently available as a preview for testing in non-production rooms.
Android 13 is not officially supported by Zoom or Microsoft yet, so please do not open support tickets with them. Escalate support requests via the normal Neat process.
Certification with major platform partners is in progress.
We will only support the combination of an Android 13 Pad connected to a Neat Bar Gen 1 / Neat Board Gen 1 running Android 10. All other variations should be on Android 13 only if they are running NeatOS 25.4.2
The 25.4.0 and 25.4.1 builds are not planned to make it to the Neat Stable channel. A 25.4.2 build that will be a seamless migration path from Android 10 builds to Android 13 will be available without the requirement to perform a factory reset.

Note: if you previously performed this procedure with NeatOS 25.4.0 to try Android 13, you will simply do the regular automatic update to 25.4.2. No additional factory reset will be needed to remain on Android 13.

Note: For details on specific behaviors or limitations when upgrading to Android 13, please refer to the following article: Neat Bar Devices May Stall During Android 10 → 13 Upgrade.

If you want to check you have indeed got the Android 13 build on your Neat device, please review the table below.

The firmware version can be checked on Neat Pad under System Settings > Devices > Selecting a device or by using Neat Pulse.

Neat Product	Android 10 (25.4.2) Jan 24 2026	Android 13 (25.4.2) Jan 24 2026
Neat Pad	NFA1.20251114.0727	NFA2.20251114.0729
Neat Bar (Gen 1)	NFB1.20251114.0721	N/A
Neat Board	NFC1.20251114.0721	N/A
Neat Bar Pro	NFD1.20251114.0721	NFD2.20251114.0727
Neat Bar (Gen 2)	NFE1.20251114.0721	NFE2.20251114.0727
Neat Frame	NFF1.20251114.0721	Coming soon in 26.1.0
Neat Board 50	NFH1.20251114.0721	NFH2.20251114.0727
Neat Board Pro	NFK1.20251114.0721	NFK2.20251114.0727
Neat Center	N/A	NFL1.20251114.0719

3.5 Google Meet Rooms is now Generally Available on Neat Devices

If you are a Google Workspace and Google Meet user, you can now use Google Meet Rooms on Neat devices! Please take a look at the Important note for Google Meet on new devices below, and at our Google Meet documentation for more information, and make sure you understand the steps for a successful installation.

Please note: To use Google Meet Room functionality on Neat devices, you will need a Google Workspace subscription and Google Meet Room licenses.

Important note for Google Meet on new devices

To run Google Meet on Neat Bar Pro or Neat Bar Gen 2, the devices must be running Neat OS 25.4.2 on Android 13. At the moment, Android 13 is only available on the Preview channel and has not yet been rolled out to Stable. For new Google Meet deployments, you will need to set up the devices, upgrade them to Android 13, and then perform a factory reset to prepare them for Google Meet. Follow the steps below to upgrade:

Before 25.4.2 is available in OTA Stable

1. Initial power-up

Power up device → OOB
Update to current Stable 25.3.2 (unless already on 25.3.2)

2. OOB on 25.3.2

Complete OOB
Install Zoom (Sign-in not required) or BYOD only mode

3. Move device to Preview Channel

Go to: System Settings → System → Software update → Update channel
Select Preview

4. Update firmware to 25.4.2 (A10)

Go to: System Settings → System → Software update
Tap Update now
Upgrade to 25.4.2 A10

5. Update to 25.4.2 (A13):

Occurs automatically overnight after upgrading to 25.4.2 A10
Upgrade window: 1:00–5:00 AM, based on device location
To trigger sooner, change the device timezone to fall within the upgrade window
Check systems settings to see the upgrade

6. Factory reset

Perform a factory reset
Device returns to OOB
Then follow the steps outlined in How to Install Google Meet on Neat Devices

Existing devices: Zoom / Microsoft Teams

Ensure the devices are updated to 25.4.2 Preview
Factory reset and follow the rest of step 6 as above

4. Improvements and bug fixes

4.1 Improvements

Issue reference	Description
AUD-389	Improved audio processing for clearer sound. We’ve made small adjustments to how Neat devices detect and balance sound levels. This brings a modest improvement to noise reduction, automatic gain control, and dynamic microphone selection — making overall audio just a bit clearer and more consistent.
CA-1008	Improved Wi-Fi security for Enterprise networks To comply with modern Android 13 security requirements, we have strengthened the validation process for 802.1x Enterprise Wi-Fi networks on our devices. This update introduces stricter security checks to protect your network, but we’ve ensured a smooth transition for our current users. Impact: Current Users: Customers upgrading from Android 10 to Android 13 with existing 802.1x Wi-Fi configurations do not need to do anything. Your settings will continue to work automatically after the update. Required for New Setups: The only change applies when configuring a new Enterprise Wi-Fi connection. In this case, providing a CA certificate and subject alternative name match is now mandatory to ensure the connection is secure.
VID-331	The Chromium Webview component has been upgraded to version M138. This is update brings the embedded browser engine up to date with the latest Chromium release. While the upgrade does not introduce any Neat-specific functional changes, it includes a large number of security, performance, and compatibility improvements from the upstream Chromium project.
VID-324	Improved static photo detection so that confirmed static photos are now re-identified much faster after the device is moved or rotated, reducing the delay before they’re excluded from framing.
VID-338	Default framing boundaries are now automatically set based on the product’s intended room size, ensuring an optimal out-of-box experience without manual adjustment. Frame: 3 m Non-Pro products: 6 m Pro products: 10 m

4.2 Bug fixes

Issue reference	Description
CUS-1594 Included from 25.4.2	We’ve identified and improved an issue where audio could occasionally sound crackled or garbled when using Neat Bar Pro, Neat Pad, and Neat Center in BYOD mode with certain Microsoft Teams Rooms PCs.
CUS-1799 Included from 25.4.2	Fixed an issue where a permanently connected HDMI ingest source could cause audio loss or instability on Neat Bar Pro if left over long periods.
CUS-1713 Included from 25.4.2	Fixed an issue where both self view and far end video could appear greyed out during Microsoft Teams calls on Neat Frame, despite the camera functioning correctly in Zoom and in the Framing Boundary preview.
CUS-1551 Included from 25.4.2	Fixed an issue where Zoom Room Mass Import with Auto Sign In could fail for Neat Pad when used as a controller paired with a Neat Bar, preventing the controller from signing in successfully after device import and room assignment in Zoom Device Management.
INBUGS-3659 Included from 25.4.2	Fixed an issue where HDMI audio out for ALDs (assistive listening devices) does not work correctly on 25.4.0 on Android 13 on Neat Board 50 and Neat Bar Gen 2.
CUS-1652 Included from 25.4.1	Fixed an issue where Neat devices could appear offline in Zoom Device Management despite having network connectivity. The root cause was identified as a certificate renewal process where the ZDM connection client did not reload the updated certificate. This could lead to authentication failures after long uptime periods. The fix ensures the connection service restarts automatically after certificate renewal.
CUS-1709 Included from 25.4.1	Fixed an issue where device remote access tokens are not properly invalidated during the logout process.
CUS-1529 Included from 25.4.1	Fixed an issue where the HDMI output could appear only in the top quarter of the screen.
CUS-1807 Included from 25.4.1	Fixed rare camera crash on Neat Board Pro during Microsoft Teams meetings.
CUS-1777 Included from 25.4.1	Fixed an issue preventing Neat Bar Pro from using full 21:9 resolutions on certain displays
CUS-1428 Included from 25.4.1	Fixed an issue causing stretched or letterboxed video on ultrawide displays
CUS-1541 Included from 25.4.1	Fixed an issue where Neat Bar Pros could occasionally become unresponsive with a blinking white LED during reboot.
CUS-1596 Included from 25.4.1	Fixed an issue that could cause audio loss on Neat Bar Pro during Microsoft Teams calls
CUS-1655 Included from 25.4.1	Fixed an issue where Neat Center could lose its paired camera after network interruptions
CUS-1632 Included from 25.4.1	Fixed issues with SCEP certificate renewal and retry behavior
CUS-1631 Included from 25.4.1	Fixed an issue where Neat Board could freeze or lose HDMI input after a Barco ClickShare device woke from standby
INBUGS-3329 Included from 25.4.1	Fixed an issue where tapping PTZ controls had no effect
INBUGS-3408 Included from 25.4.1	Fixed an issue where HDMI audio out for ALDs (assistive listening devices) does not work correctly on 25.4.0 on Android 13 on Neat Bar Pro.
INBUGS-3409 Included from 25.4.1	Fixed an issue where manually configured static IP settings are not retained after a reboot. The network interface reverts to DHCP on startup. Issue reproducible and under investigation.
CUS-1771 Included from 25.4.0	Fixed an issue where HDMI 2 displayed a different color temperature than HDMI 1 on Neat Bar (Gen 2) and Neat Bar Pro.
CUS-1733 Included from 25.4.0	Fixed an issue preventing Microsoft Teams admin password updates when using French (Canada) with large font sizes
CUS-1724 Included from 25.4.0	Fixed erratic auto-framing behavior on Neat Bar Pro
CUS-1743 Included from 25.4.0	Fixed a crash in BYOD mode when the camera was turned on
CUS-1764 Included from 25.4.0	Fixed an issue where large facial images on walls were not ignored by static-image detection
CUS-1387 Included from 25.4.0	We’ve addressed a low-risk security report on Neat Board 50 and Neat Board Pro.
CUS-1527 Included from 25.4.0	Fixed an issue where Neat Bar (Gen 2) HDMI 2 displayed a different color tone compared to HDMI 1.
INBUGS-3041 Included from 25.4.0	We’ve identified an issue where Framing options may still appear after disabling the FOR camera in Camera Selection. When the FOR (Front-of-Room) camera is disabled before starting a call, its Framing and control options may still be visible in the swipe-left menu or in the in-call controls. This can cause confusion, as only the Neat Center camera should be active and adjustable in this scenario. This behavior does not affect call performance but may mislead users about which camera is in use and which framing modes are available.
INBUGS-3052 Included from 25.4.0	We’ve identified a user interface issue where the Framing Boundary description text may be misaligned or missing on Neat Pad devices. When Camera Selection is set to Automatic, the correct description appears as expected. However, when using Custom mode with All Cameras selected, the description for the Neat Center may not fit the screen margins properly. Additionally, if an individual Neat Center camera (A, B, or C) is selected, the description may not appear at all. This can cause confusion for users who rely on the instructions to adjust Framing Boundary settings.
CUS-1617 Included from 25.4.0	Fixed an issue where, under certain conditions, far-end video did not display during WebEx meetings on Neat Bar (Gen 1) and Neat Bar (Gen 2) devices.
CUS-1653 Included from 25.4.0	Fixed an issue where faulty HDMI camera inputs were not removed correctly and caused black screen.
INBUGS-3121 Included from 25.4.0	Fixed an issue where when you select “All Camera,” the Neat Center’s LED may appear dimmer than usual. This is a known issue that only affects the LED display — it does not impact how the Neat Center works or how the cameras perform. This is only visible when All Cameras are selected directly from the Neat Board settings. If a Neat Board is paired to a Neat Pad (or for the case of Neat Bars/Neat Pads) and the interaction is on Neat Pad only, the issue will not occur.
INBUGS-3097 Introduced in 25.4.0	We’ve fixed an issue where the Field of View slider is incorrectly shown when “All Cameras” is selected in the Framing Boundary settings. Field of View is only relevant when a single Neat Center camera is selected, but currently it can appear even when multiple cameras are in use. This may cause confusion, as adjustments made while “All Cameras” is selected will be saved but not applied until a single camera is chosen.

5. Known issues

Issue reference	Description
CUS-1760 Introduced in 25.4.2	We’ve identified an issue where *Neat Center may appear as Offline* in Neat Pulse after a new installation**, even though the device is successfully paired, added to the room, and fully functional in meetings.
INBUGS-3787 Introduced in 25.4.2	We’ve identified an issue where Neat Bar (Gen 2) and Neat Pad could fail to pair after an Android 10 to Android 13 upgrade performed during out-of-box setup, causing the bar not to appear in the available pairing list despite successful migration and a healthy Neat network connection. An additional factory reset solves this issue.
INBUGS-3171 Introduced in 25.4.0	Board 50 enters sleep mode once the inactivity timer is reached when using BYOD mode on Android 13
INBUGS-3399 Introduced in 25.4.0	For EFT-customers: Accessing Neat settings during a Google Meet call may end the call. An issue may occur when opening the Neat settings menu from the swipe menu during an active Google Meet call. Changing certain settings — such as Dark Mode or Language — while in a call may cause the meeting to end unexpectedly. We recommend avoiding changes to Neat settings during an ongoing Google Meet call until this issue is resolved.
INBUGS-3021 Introduced in 25.3.0	We’ve identified an issue where in some cases, boundary green boxes can appear on the FOR and Neat Center when changing the Camera Selection options.
INBUGS-3042 Introduced in 25.3.0	We’ve identified an issue where the Picture-in-Picture (PIP) view on Neat Board devices may show both Neat Board and Neat Center video streams instead of only the selected Neat Center camera. This can happen when the Neat Board camera toggle is disabled and the Neat Center camera is selected, then later the Neat Board camera toggle is re-enabled.
INBUGS-3100 Introduced in 25.3.0	We’ve identified an issue where the minimum depth/diameter setting for Framing Boundary on Neat Center is not available when camera selection is set to automatic.This option is only visible when using custom camera selection, which can cause confusion if a user sets a minimum depth while in custom mode and then switches back to automatic. In this case, the previous minimum depth setting will still be active but hidden, with no way to adjust it unless the user switches back to custom camera selection.
INBUGS-3101 Introduced in 25.3.0	We’ve identified an issue with the minimum and maximum values for the Framing Boundary width and depth sliders. This does not affect most users but may limit how precisely the framing area can be adjusted in very small spaces.
INBUGS-3119 Introduced in 25.3.0	We’ve identified an issue where verification mode and field of view constraints may appear during a call after modifying Framing Boundary settings. In some cases, the verification mode view and field of view overlays can remain visible once a call starts. This occurs when the camera is reselected after changing Framing Boundary settings and before starting a call. The issue mainly affects setups with a Neat Board and Neat Center; using a Neat Pad as the controller instead can prevent it. Restarting the call or readjusting the Framing Boundary settings may temporarily resolve this behavior.
INBUGS-3006 Introduced in 25.3.0	We’ve identified an inconsistency in how the Camera Selection preview appears when using a Neat Board and Neat Pad together. When a camera is selected using a Neat Pad paired with a Neat Board, the full-screen Preview view appears on the Neat Board, similar to how it works on a Neat Bar/Neat Pad setup — this is the expected behavior. However, if the camera selection is done directly on the Neat Board, a Picture-in-Picture (PIP) window is shown instead. This difference in behavior may cause confusion about what to expect when switching between the Neat Board and Neat Pad for camera selection.
INBUGS-3038 Introduced in 25.3.0	We’ve identified an issue where a camera’s LED will stay on during ongoing calls when that camera is disabled in Camera Selection. This can happen on Neat Board Pro and Neat Center devices. For example, if the Neat Center camera or Board Pro camera is disabled before joining a Microsoft Teams meeting, its LED may still light up even though the video feed is not active. This behavior is due to how the camera streams and how it’s exposed to the app, and does not affect meeting functionality — but it may be confusing for users who expect the LED to turn off when the camera is disabled.
INBUGS-3099 Introduced in 25.3.0	We’ve identified an inconsistency in the Framing Boundary slider labels for the Neat Center camera. When Camera Selection is set to Automatic, the slider uses Diameter with a range of 0–10 m. When Camera Selection is set to Custom, it uses Depth with a range of 0–5 m. While the ranges are technically correct, this inconsistency in naming may confuse users. We plan to align the terminology to use Depth consistently in a future update.
CUS-1579 Introduced in 25.3.0	Since Neat OS 25.2.0 release, Neat Pads running Microsoft Teams could respond very slowly to user actions, such as joining a call or changing a setting, and in some cases show a black screen. The root cause of this issue is under investigation. More information about this technical issue can be found here.
INBUGS-3034	Framing Boundary changes from 25.2.0 to 25.3.0 NeatOS 25.3.0 firmware version includes some user interface changes in the Framing Boundary section, to accommodate the inclusion of the new Beta feature (Camera selection), when paired with a Neat Center. Although the Framing Boundary selectors for Neat Boards and Neat Bars are still including Width and Depth as the Boundary parameters, NeatOS 25.3.0 includes a secondary slider selector allowing the user to modulate the inferior and upper Depth parameters on the Front room device. A difference compared to NeatOS 25.2.0 and older firmware versions is that in NeatOS 25.3.0, the lowest value for the Depth parameter is 1m instead of 0m. This is a known issue included in this firmware version as the changes are to accommodate the new Camera selection implementation. The inferior Depth parameter will be set back to 0m in future firmware updates What if the device is paired to a Neat Center? If the Neat Bar/Neat Board device is paired to a Neat Center and Camera selection is set to ‘Automatic’ – In this situation, Framing Boundary for Neat Center will remain showing Diameter as the only parameter, and the value can be adjusted between 0-10 meters as usual. If the Neat Bar/Neat Board device is paired to a Neat Center and Camera selection is set to ‘Custom’ – In this case, Framing Boundary for Naet Center will show 2 new parameters to adjust: Field of View and Depth. The Field of View can be set from 5-162 degrees, and Depth will show again the 2 slider selectors to adjust the inferior and upper values. As mentioned before, the inferior value for Depth is set to 1m instead of 0m, and will be set back to 0m in future updates.
ZTC-118	When using Neat Board 65 in Companion Zoom Room mode, connecting a peripheral device (e.g. a laptop) to the Neat Board’s local input port causes Zoom to log out of the Companion ZR mode. This occurs because when the local input port is used, the touch-ability of the Neat Board is disabled by design (as in this mode, the Neat Board is being used outside of Zoom as an independent display). However, since Zoom expects the display to be a touch-enabled device at all times, it notices this change and logs out from the Companion ZR mode. This is a known limitation (however expected) as the local input port is not considered part of the Zoom’s work-flow and therefore not supported.
INBUGS-2732	In the current 25.1 Release on Preview, a bug affects Board 50 and Board Pro devices. Prior to 25.1 (in 24.6 and earlier), users could connect a USB-C (C2C) cable from a laptop to a Board (50 or Pro) supporting Display Port and mirror their screen regardless of the cable orientation. However, in 25.1, if the C2C cable is connected with the wrong orientation, media content cannot be shared, although the device can still be used in BYOD mode without screen mirroring.
INBUGS-31	‘Unable to verify certificate’ message is displayed when uploading CA certificate which has a text part before the actual certificate part. To work around this issue, copy only the certificate portion (BEGIN CERTIFICATE / END CERTIFICATE) to a file and save it as .pem/.cert etc.
ZOOM-93	In this release, it is not possible to disable Zoom’s ‘Advanced Noise Suppression’ feature. As a result, any users using the ‘Music mode’ feature will notice that their audio is being suppressed by Zoom’s noise suppression algorithm, making the experience poor. This issue is being investigated by the Zoom engineering team.
CUS-326	In this release, color correction configuration options are available in the accessibility settings on the Neat Board and Neat Bar Pro, but enabling the feature will not have any effect on the screen.
CUS-635	In this release, if a Neat Bar is rebooted while BYOD mode is enabled and in use, the Neat camera and Microphone will no longer function as expected until the USB-C cable is unplugged and replugged from the device.
CUS-760	In this release, it is possible for a Neat device to show an “untrusted server certificate” warning due to a network timing issue. Rebooting the device should resolve the error in these scenarios.
INBUGS-1664	In this release, switching between external audio hardware and the internal speaker while using Audio over USB on a Neat Bar Pro does not always work during a Zoom meeting.
INBUGS-2482	When a Neat Pad is paired with a Neat Board or Neat Board 50, and manual BYOD mode is started on the Board itself (instead of the Neat Pad), then the Board/Board 50 enters the BYOD mode, but the Pad does not. The workaround is to either start BYOD mode on the Pad or if it has already started on the Board, to enter it from the Pad by selecting the manual BYOD mode.
INBUGS-2484	We have identified a compatibility issue affecting users who are utilizing USB Audio with third-party audio devices (such as Shure) in conjunction with the BYOD mode. When both the USB Audio setting and the BYOD Enabled setting are activated in Pulse management platform, USB audio functionality is disrupted. As a result, users with USB Audio connected to third-party devices may experience audio disruptions when both USB Audio and BYOD are enabled. To avoid this issue, please ensure that you do not enable both BYOD and USB Audio in Pulse simultaneously. Disabling the BYOD settings in Pulse will prevent the conflict and maintain USB audio functionality.
INBUGS-2502	Neat Bar Gen 2 can show a shifted layout during OOB phase when connected to some high resolution monitors.
CUS-1181	If an update is requested via Pulse (by changing profile to a newer channel such as Preview from Stable) OR all devices are restarted at the same time when an upgrade is available it can synchronise the OTA polling across the devices for a site.Assuming the devices for the site are all on the same network, the Neat devices will then simultaneously request to download from the Neat OTA servers their upgrade files (around 1GB worth of data per device). When there are many devices doing this on certain networks it can potentially cause network throttling or alert security monitors that block the downloads part way through.If a device has started the upgrade procedure and it is unable to complete within the set upgrade window (1am – 5am local time) it can cause the device to be stuck on a purple upgrade screen and a restart (via Pulse or by removing the power to the device) is needed to restore functionality.
INBUGS-2985 Introduced in 25.2.0	If CEC is enabled on Neat Bar (Neat Bar 2 or Neat Bar Pro) and the CEC-enabled monitor connected to Neat Bar is turned OFF, Neat Bar will go to sleep as a result of the monitor being turned off. However, turning the monitor back on will not wake Neat Bar. If auto-wakeup is disabled, the only way to wake Neat Bar is by touching a connected Neat Pad. If auto wake-up is enabled on Neat Bar, the device will wake up as normal by motion detection.

6. How to check your software and firmware version

Here’s how to find out if your Neat device is running the latest build:

For Zoom Rooms: Select Settings (bottom left) on your Neat Pad, Neat Board, or Neat Frame, then select About. You’ll see the Zoom software version on the right.
For Microsoft Teams: Select More on the main screen, then go to Settings → About to view the Microsoft Teams software version.
For Neat Firmware: On your device, go to System Settings → System → About to find the firmware version and serial number.

You can also check the Zoom Room administrator portal or the Teams Admin Center (TAC) online to see the serial number and firmware version of your Neat devices.

Note for Neat Pad and devices enrolled in Neat Pulse: You can normally check for updates on the device’s Software Update page. But if any of your Neat devices are enrolled in Neat Pulse, that option will be greyed out. In that case, just head over to Neat Pulse to view and manage updates.

7. Need help? We’re here for you!

For quick answers and troubleshooting, check out our Neat Support website, where you’ll find helpful articles, FAQs, and step-by-step guides. We regularly update our content to make finding solutions easier.

If you need further assistance, our support team is ready to help! Simply email us at support@neat.no, and one of our technical support engineers will get back to you.

Privacy Policy: You can review our privacy policy here: Neat Privacy Policy.

Support Policy: Neat provides support for devices running the current or previous software release. For full details, see Neat’s Technical Support Policy.