Prerequisites

The following are required for seatback monitors to support Bluetooth.

Software

Seatback monitors must be running Android 5.1 or higher and using PAC IO. X Series monitors support Bluetooth 4.0. NEXT and Astrova monitors support Bluetooth 5.0. Additionally, seatback monitors must have Bluetooth configured in their lru.cfg file.

Use the standard Android Bluetooth APIs for Bluetooth controls and events on the seatback monitor, with the following exceptions:

Allowing and disallowing Bluetooth — Bluetooth is allowed on the cabin class level through TD 315. If Bluetooth is not allowed, the Bluetooth module will not turn on.
To allow Bluetooth, refer to Allow and Disallow Bluetooth.
Bluetooth Radio Inactivity Monitor — Core software monitors Bluetooth scans and connections. When Bluetooth radio becomes inactive, core software will start a timer. If the timer exceeds the time set by Bluetooth_Power_Inactive_Timeout, Bluetooth radio will be powered off. For more information, refer to Bluetooth is turning off after the monitor boots up.
The interactive can turn the Bluetooth radio back on at any time while Bluetooth is allowed through TD 315. The interactive should never assume that Bluetooth is turned on—before executing any Bluetooth operations, the interactive should always check the state using getState. Additionally, configure the interactive to monitor Android events or listen for the ACTION_CONNECTION_STATE_CHANGED broadcast to determine the current connection status.
Setting the audio output device — Whenever the Bluetooth connection status changes, such as when a device is connected or unpaired, the interactive should use the PAC IO getAudioDevices and setAudioDevices APIs to redirect the audio output accordingly.
For more information, refer to Set Audio Output Device.

For the Android Bluetooth APIs, refer to the Android Bluetooth Guide and Bluetooth Reference.

Supported Bluetooth Profiles

Bluetooth profile support is dependent on the seatback monitor’s Android version. Use the following table to determine whether a seatback monitor supports certain profiles.

Profile	Description	Android 5.1	Android 8.1	Android 9
A2DP Source	Enables streaming audio to a Bluetooth audio device.	Yes	Yes	Yes
AVRCP Target	Enables receiving media commands, such as play and pause, from a Bluetooth audio device to control IFE audio through the interactive. Used with A2DP Source.	Yes, but excludes volume control	Yes	Yes

A2DP Source

Enables streaming audio to a Bluetooth audio device.

Yes

AVRCP Target

Enables receiving media commands, such as play and pause, from a Bluetooth audio device to control IFE audio through the interactive.

Used with A2DP Source.

Yes, but excludes volume control

Yes

Hardware

Seatback monitors must:

Have a Bluetooth module directly wired, whether it’s built-in or using a Bluetooth Remote Jack Module (RJM).
Be running Android with Bluetooth support allowed.
Have a built-in or connected display.

Not all seatback monitors have built-in Bluetooth hardware, but monitors without the built-in hardware can support Bluetooth if a Bluetooth RJM is directly wired to the monitor.

There are two types of Bluetooth RJMs to provide Bluetooth connectivity:

X Series Bluetooth RJM — This is USB-based and is directly wired to the X Series seatback monitor.
Astrova Bluetooth RJM — This is Ethernet-based and is wired to the same seatbox as the Astrova seatback monitor.

NEXT seatback monitors only have built-in Bluetooth hardware and do not have a Bluetooth RJM option.

Astrova has an option to use either the Astrova Bluetooth module in the peripheral bar or the Astrova Bluetooth RJM. X Series monitors have the option to use either the built-in Bluetooth module or the X Series Bluetooth RJM. For either monitor, only one option can be used at a time and must be set in the configuration to enable one option and disable the other.

Build# 20220627.3