Fixed
Details
Details
Assignee
Stephane Desneux
Stephane DesneuxReporter
Stephane Desneux
Stephane DesneuxFix versions
Contract ID
Affects versions
Due date
Sep 28, 2018
Priority
Created September 28, 2018 at 2:35 PM
Updated October 1, 2018 at 8:49 PM
Resolved September 29, 2018 at 7:59 PM
I just pushed https://gerrit.automotivelinux.org/gerrit/16855 to FF.
This introduces a workaround at 4A level: the startup is delayed until the BT device and Bluetooth-Manager are available. And if no BT is detected, the script tries to bail out as early as possible (8 secs max if no BT is detected).
So we need now some help to validate the solution on the boards for FF.
This table is to be updated to fill the test results:
Board
BT Adapter
Assignee
Result
H3+KF
KF
@Stephane Desneux
PASS
H3
Asus USB Dongle
@Stephane Desneux
PASS
H3
None
@Stephane Desneux
PASS
M3+KF
KF
@Jonathan Aillet
PASS
M3
CinolinkCSR BC8510Usb Dongle
@Jonathan Aillet
PASS
M3
None
@Jonathan Aillet
PASS
Minnowboard Turbot
XXXX Usb Dongle
@Matt Ranostay
PASS
Minnowboard Turbot
None
@Matt Ranostay
PASS
Minnowboard MAX
Asus USB Dongle
@Stephane Desneux
PASS
Minnowboard MAX
None
@Stephane Desneux
PASS
How to validate: after bootup, run:
journalctl | grep 4AWAITBT
This will give the result of wait loop (the script 4a_wait_bt.sh introduced in the W/A). When BT is enabled, the last line should be:
{{ 4AWAITBT 4A now starting... }}
Otherwise (no BT controller), it should be:
4AWAITBT TIMEOUT REACHED
To check if 4A BT audio is enabled:
journalctl -u afm-service-agl-service-audio-4a-*@0.service --no-pager -p4 | grep "No bluetooth receiver detected"
There should be no ouput. If you see a warning message with "No bluetooth receiver detected", it means that BT audio is disabled (it should be if we don't have any BT adapter)