4A: Bluetooth support not discovered correctly at boot time

Key details

Description

4A is contacting the Bluetooth-Manager API in the boot phase and for unknown reason, the BT hw controller and bluez are not initialized correctly at that time. As a consequence, no bluetooth controller is detected by 4A BT plugin and BT audio are then disabled without any consequence on the rest of the audio stack.

This only happens at boot time: as soon as things are initialized, a simple restart of 4A service is enough to enable BT audio and stream music through A2DP.

Environment

observed on H3+KF with FF image (the 6.0.0 candidate, after merge of gerrit review #16771)

Attachments

28 Sep 2018, 11:08 AM

Subtasks

100% Done

Work	Priority	Story Points	Assignee	Status
SPEC-1768 Validate Workaroound to SPEC-1763 for FF release	Blocker		Stephane Desneux

Linked work items

relates to

SPEC-1762

bluetooth-service: early API call to 'power' verb fails

Activity

Walt Miner

April 16, 2019 at 6:17 PM

Matt Ranostay

March 25, 2019 at 12:16 AM

Walt Miner

October 1, 2018 at 8:48 PM

Jan-Simon Moeller

October 1, 2018 at 8:43 PM

Walt Miner

October 1, 2018 at 7:56 PM

Resize work item view side panel

Fixed

Details

Assignee

Matt Ranostay

Reporter

Stephane Desneux

Priority

Critical

Created September 27, 2018 at 11:20 PM

Updated September 19, 2019 at 12:06 PM

Resolved March 25, 2019 at 12:16 AM

4A: Bluetooth support not discovered correctly at boot time

Description

Environment

relates to

Walt Miner

Matt Ranostay

Walt Miner

Jan-Simon Moeller

Walt Miner

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority