Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

4A: Bluetooth support not discovered correctly at boot time

Fixed

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

1
100% Done
Loading...

Activity

Show:

Walt Miner 
April 16, 2019 at 6:17 PM

Close for Guppy 7.0.1

Matt Ranostay 
March 25, 2019 at 12:16 AM

Clients can now use the adapter_changes verb to detect changes of adapters.

https://gerrit.automotivelinux.org/gerrit/#/c/20307/

Walt Miner 
October 1, 2018 at 8:48 PM

Thanks. Not sure how I missed it.

Jan-Simon Moeller 
October 1, 2018 at 8:43 PM

Walt Miner 
October 1, 2018 at 7:56 PM

Should the work around be cherry picked to master so we do not see a regression on master while we get the final fix in place?

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority

Created September 27, 2018 at 11:20 PM
Updated September 19, 2019 at 12:06 PM
Resolved March 25, 2019 at 12:16 AM

Flag notifications