Troubleshooting

A device is failing to pair

This is likely caused by missing a step in the Bluetooth process or not allowing Bluetooth operations, such as scanning, pairing, and connecting, to fully complete before proceeding to the next one. Refer to the Interactive Bluetooth Implementation Flow.

Ensure the following are implemented correctly:

• Once a passenger has found and selected their device in the list of discovered Bluetooth devices during the scanning process, immediately discontinue scanning for Bluetooth devices by calling cancelDiscovery.

• When scanning is discontinued, wait and listen for the ACTION_DISCOVERY_FINISHED broadcast to ensure scanning has finished before continuing to pairing.

Bluetooth is streaming poor audio quality

This may be due to one or more of the following:

• The interactive is scanning for devices while a Bluetooth device is already connected and streaming audio.

  Bluetooth scanning uses resources in both the Bluetooth stack and Bluetooth radio. If scanning is on while audio is streaming through Bluetooth, there will be connection and audio quality issues such as dropouts. Always ensure that scanning is only turned on when a passenger is actively searching for their device to pair with the seatback monitor. Otherwise, turn scanning off.

• Someone is using the MAINT screen to run a rack-wise Bluetooth scan test. This puts all Bluetooth radios in a mode that constantly scans for nearby devices.

• Bluetooth is configured with a small Adaptive Frequency Hopping (AFH) channel map and there is a lot of radio interference in the area on those channels.

The Bluetooth discovered device list is not showing devices

This may be due to Bluetooth being turned off.

Ensure that the interactive has Bluetooth turned on before trying to scan for devices.

Bluetooth is unable to be turned on

This may be due to how Bluetooth is configured on the seatback monitor.

Ensure that Bluetooth is configured on the seatback monitor in its lru.cfg file and allowed for the cabin class. For more information, refer to Check if Bluetooth is enabled.

Bluetooth is turned off after the monitor boots up

When Android first starts up and Bluetooth is enabled, Bluetooth may turn on automatically. However, this is not guaranteed, so when the passenger is trying to use Bluetooth, the interactive should always check the status by listening for the ACTION_CONNECTION_STATE_CHANGED broadcast to determine whether Bluetooth is turned on or off. If Bluetooth is off, the interactive must turn it on.

Additionally, Bluetooth will remain turned on until the inactivity timer runs out and turns it off. This event is reported through the ACTION_CONNECTION_STATE_CHANGED broadcast. For more information, refer to Bluetooth is automatically turning off after a set amount of time

The interactive is not connecting to a Bluetooth device

This may be due to Bluetooth not being enabled on the seatback monitor or the interactive not properly connecting to the device.

Ensure that Bluetooth is enabled on the seatback monitor. For more information, refer to Check if Bluetooth is enabled.

In addition, note that pairing a device is not the same as establishing a connection. Ensure that the device is paired before connecting to it. For more information, refer to What is the difference between a paired device and a connected device?.

Bluetooth audio devices must support A2DP or AVRCP profiles to be automatically connected after pairing. However, automatic connection is not guaranteed and the BluetoothA2dp class does not directly provide APIs for connecting devices, so the interactive should always try to connect to the device using the Android BluetoothA2dp class. For more information, refer to Connect Paired Device.

Bluetooth is automatically turning off after a set amount of time

Due to system requirements, Bluetooth turns off after a set amount of time, if there hasn't been an active connection to a device, scanning is not active, or the self-testing feature is not running.

This behavior cannot be disabled, but the timeout duration can be adjusted by configuring the Bluetooth_Power_Inactive_Timeout field on the seatback montior. The duration is set at five minutes by default but can be extended up to thirty minutes. For more information, contact your Panasonic focal.

Some Bluetooth audio devices are sometimes not pairing

Some models of Apple AirPods and Android headsets have issues with pairing or connecting if they are currently paired with another device.

To resolve this, the passenger will need to unpair the audio device from all other devices or remove all pairing information from their device, which may involve resetting it, before attemping to pair to the seatback monitor again.

The interactive is not receiving any BLUETOOTH_CONTROL events

This is due to Bluetooth not being available on the seatback monitor.

Bluetooth is available if the seatback monitor meets both software and hardware requirements and Bluetooth is configured in the lru.cfg file. When these requirements are met, the interactive will receive the BLUETOOTH_CONTROL transient data event, whose value determines if Bluetooth is allowed. If the interactive does not receive any BLUETOOTH_CONTROL events, assume that Bluetooth is not available.

When Bluetooth is available, the crew can change the value of BLUETOOTH_CONTROL during a flight.

If BLUETOOTH_CONTROL is set to 1, Bluetooth is allowed. If it's set to 0, Bluetooth is disabled.

For software and hardware requirements, refer to Prerequisites.