Skip to:

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

"Media audio" bluetooth profile in pairing missing

Description

When testing bluetooth and audio on m3ulcb on the latest guppy 7.0.1, when a phone is paired, the device does not expose "Media audio" capabilities, therefore streaming media cannot be tested.

This behavior is observed only on m3ulcb board.

attached manifest file

Link to the image freshly built - https://transfer.sh/y56a3/agl-demo-platform-m3ulcb-20190409101344.rootfs.wic.xz

The link to the image will be valid for two weeks from now on.

Environment

None

Attachments

1

Activity

Edi Feschiyan 
May 20, 2019 at 6:47 AM

I am marking this as fixed since the patches were merged and now bluez-alsa starts correctly.

Edi Feschiyan 
April 12, 2019 at 7:21 AM
(edited)

m3ulcb:~# journalctl -u bluetooth.service -- Logs begin at Thu 2019-04-11 18:40:49 UTC, end at Thu 2019-04-11 18:44:26 UTC. -- Apr 11 18:41:02 m3ulcb systemd[1]: Starting Bluetooth service... Apr 11 18:41:02 m3ulcb bluetoothd[3963]: Bluetooth daemon 5.46 Apr 11 18:41:03 m3ulcb systemd[1]: Started Bluetooth service. Apr 11 18:41:03 m3ulcb bluetoothd[3963]: Starting SDP server Apr 11 18:41:03 m3ulcb bluetoothd[3963]: Bluetooth management interface 1.14 initialized Apr 11 18:41:53 m3ulcb bluetoothd[3963]: Failed to set mode: Blocked through rfkill (0x12) Apr 11 18:44:26 m3ulcb bluetoothd[3963]: a2dp-source profile connect failed for 98:29:A6:C9:6E:3D: Protocol not available
m3ulcb:~# systemctl status bluez-alsa ● bluez-alsa.service - Bluetooth Audio ALSA Backend Loaded: loaded (/lib/systemd/system/bluez-alsa.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-04-11 18:41:03 UTC; 13min ago Main PID: 3982 (code=exited, status=1/FAILURE)Apr 11 18:41:03 m3ulcb systemd[1]: Started Bluetooth Audio ALSA Backend. Apr 11 18:41:03 m3ulcb bluealsa[3982]: /usr/bin/bluealsa: No HCI device available Apr 11 18:41:03 m3ulcb systemd[1]: bluez-alsa.service: Main process exited, code=exited, status=1/FAILURE Apr 11 18:41:03 m3ulcb systemd[1]: bluez-alsa.service: Unit entered failed state. Apr 11 18:41:03 m3ulcb systemd[1]: bluez-alsa.service: Failed with result 'exit-code'.

I suspect this is the culprit. After restarting the service and reconnecting to the device - the "Media Audio" profile for m3ulcb pairing shows up in the Android phone.

Edi Feschiyan 
April 12, 2019 at 7:16 AM

I completely forgot that when I tested, the usb bluetooth adapter was missing and I inserted it later.

I reproduced it 3/3 times this way - boot without bluetooth adapter, then go to Settings->Bluetooth, do a rfkill unblock bluetooth from CLI, pair and connect with the device; after being connected with the phone, click at the paired m3ulcb profile and observe missing Media Audio profile.

 

Edi Feschiyan 
April 11, 2019 at 5:13 PM

I can't reproduce it, I guess not.

Matt Ranostay 
April 11, 2019 at 5:02 PM

Still an issue?

Fixed

Details

Assignee

Reporter

Fix versions

Contract ID

Hardware Platform(s) Affected

Renesas M3

Components

Affects versions

Priority

Created April 9, 2019 at 10:52 AM
Updated September 9, 2024 at 8:28 PM
Resolved May 20, 2019 at 6:47 AM

Flag notifications