ChromeOS Compatible - Bluetooth Specification v1.1

Version: 1.1
Last Updated: 2024-09-05

Legend

Product Verb	Development Action
"MUST"	Mandatory product requirement
"SHOULD"	Optional recommendation
"MAY"	Nice to have

Objectives

This specification document describes the Bluetooth compliance criteria that ChromeOS Compatible devices meet.

Terminology

Bluetooth device or device

The ChromeOS compatible peripheral being qualified.

ChromeOS device

The host or controlling device, if applicable.

Generic Bluetooth Requirements

The following requirements apply to all Bluetooth devices (accessories and peripherals). Additional sections define scenario-specific requirements.

• The device MUST be qualified and listed on https://launchstudio.bluetooth.com.
• The device SHOULD be qualified against Bluetooth Core 4.0 or higher core specification.
• The device SHOULD use a 7.5ms aligned connection or sniff interval.

Bluetooth Basic Rate and Enhanced Data Rate (aka Classic)

These requirements apply to any device supporting the Bluetooth BR/EDR transport.

• The device MUST support Enhanced Data Rate (EDR).
• The device MUST support the Service Discovery Protocol (SDP) without requiring pairing.

Bluetooth Input Device Requirements

These requirements apply to Bluetooth accessories that provide user input capabilities, such as mice and keyboards.

• The device MUST use Low Energy (LE) transport.
• The device MUST support the HID Over Gatt Profile.

Bluetooth Headset and Speaker Device Requirements

These requirements apply to Bluetooth accessories that provide audio input and output capabilities through the Bluetooth Hands Free Profile (HFP) and Advanced Audio Distribution Profile (A2DP). These requirements are in addition to the Generic Bluetooth Requirements.

• The audio device MUST set the following bits in the Major Service section of the Class of Device (COD) parameter:
  • Audio (bit 21)
  • Rendering (bit 18)

Note: The Class of Device bitfields are defined in the Assigned Numbers Document.

ChromeOS specific muting requirements

For this section, the following abbreviations apply:

HF

The Hands-Free device (Bluetooth peripheral)

AG

The Audio Gateway (ChromeOS device host)

If the bluetooth device (HF) supports Hands-Free Profile profile:

• HF’s Hands-Free Profile must be able to send packets and provide sound bidirectionally (playback/capture) even if AG does not tigger +CIEV,1 to HF during eSCO connection.
• If HF has a microphone mute interface:
  • HF MUST use AT+VGM=0 to represent microphone mute.
    • HF MUST send AT+VGM=0 to request microphone mute in a VC app (like Meet) on AG.
    • HF MUST mute the microphone when AG sends AT+VGM=0 to HF.
  • HF MUST use AT+VGM=X X=[1-15] to represent microphone unmute.
    • HF MUST send AT+VGM=X X=[1-15] to request microphone unmute in a VC app (like Meet) on AG.
    • HF MUST unmute the microphone When AG sends AT+VGM=X X=[1-15].

Revision History

Date	Version	Notes
2024-09-05	1.1	Added ChromeOS specific muting requirements.
2024-02-01	1.0.1	Republication on a new platform.
2023-08-18	1.0	Initial Partner Site Publication.