In 2024, a Google update to the Bluetooth library in ChromeOS introduced a number of issues affecting Bluetooth-connected devices, including SAM Labs blocks. These issues include, but are not limited to:

• Devices not appearing when using the Pairing ID feature

• SAM Labs blocks failing to fully disconnect and automatically reconnecting

These issues are the result of bugs in Google’s new "Floss" Bluetooth library included within ChromeOS versions 123–133, and are not related to SAM Labs software. The issues are specific to ChromeOS and do not affect Windows, macOS, or Linux.

To resolve these issues, we recommend one of the following actions:

OPTION 1: Update ChromeOS to 134 or later

Google has addressed the known issues in its updated "Floss" Bluetooth stack starting with ChromeOS version 134. Updating your device to version 134 or later should resolve Bluetooth connectivity problems and provide additional performance improvements.

Note: You may need to contact your IT administrator to complete this action.

OPTION 2: Disable the Floss flag

If you are still having issues with your Bluetooth connection or if you are unable to update to the latest version of ChromeOS, you can manually disable the "Floss" Bluetooth stack and revert to the previous, more stable “BlueZ” stack using Chrome’s internal settings.

Steps

1. Open Chrome and enter chrome://flags#bluetooth-use-floss in the address bar.
   
2. Locate the setting labeled "Use Floss instead of BlueZ" and select "Disabled" from the drop-down menu.
   
3. Click "Restart" in the bottom-right corner and allow your device to reboot for changes to take effect.
   

Note: This change must be completed on each device and for each user.

For educators: You may wish to guide your class through the process of adjusting the Chrome Flag together.

Additional Information

The recent Bluetooth connectivity issues on Chromebooks are linked to the transition from the legacy
"BlueZ" stack to the newer "Floss" stack. While BlueZ remains available, Floss is now the default in ChromeOS versions 123 and above. We have worked closely with Google to ensure these connection issues are addressed, and the known issues are confirmed to be fixed as of ChromeOS version 134.

If you continue to experience issues with Bluetooth connectivity, please contact our Customer Success team for support.