Re: cannot get a2dp profile enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Mar 31, 2021 at 7:55 AM mailinglisten@xxxxxxxxx
<mailinglisten@xxxxxxxxx> wrote:
>
> Hello,
>
> I hope this is the place to ask for user questions, bluez.org offers no
> other mailing list....

People start using github for this type of problems:

https://github.com/bluez/bluez/issues

> I have a Jabra headphone/headset device and pulseaudio can´t activate
> the a2dp_sink, I want to be sure, A2DP is properly enabled in bluez.
>
> bluetoothctl info MAC-OF-HEADPHONE says:
>
> UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
>
> Thus, the device supports a2dp.
>
> At the bottom I put output from "show CONTROLLER-MAC".
>
> I tried
>
> register-service 0000110d-0000-1000-8000-00805f9b34fb
>
> to no avail, still no a2dp_sink in pulseaudio.
>
> How can I ensure using bluetoothctl that a2dp is really enabled in bluez?
>
> I´m not sure, if I deal with a bluetooth or pulseaudio issue, I want to
> exclude a misconfigured bt device.
>
> I´m using bluez 5.48 and kernel 5.11.3.
>
> Thank you very much in advance!
>
>
>
> This is the output from bluetoothctl show CONTROLLER-MAC:
>
>
> Controller 00:F4:8D:C9:40:5E (public)
>         Name: foobar
>         Alias: onboard
>         Class: 0x007c010c
>         Powered: yes
>         Discoverable: no
>         Pairable: yes
>         UUID: Message Notification Se..
> (00001133-0000-1000-8000-00805f9b34fb)
>         UUID: A/V Remote Control
> (0000110e-0000-1000-8000-00805f9b34fb)
>         UUID: OBEX Object Push
> (00001105-0000-1000-8000-00805f9b34fb)
>         UUID: Message Access Server
> (00001132-0000-1000-8000-00805f9b34fb)
>         UUID: IrMC Sync
> (00001104-0000-1000-8000-00805f9b34fb)
>         UUID: PnP Information
> (00001200-0000-1000-8000-00805f9b34fb)
>         UUID: Vendor specific
> (00005005-0000-1000-8000-0002ee000001)
>         UUID: Headset AG
> (00001112-0000-1000-8000-00805f9b34fb)
>         UUID: A/V Remote Control Target
> (0000110c-0000-1000-8000-00805f9b34fb)
>         UUID: Headset
> (00001108-0000-1000-8000-00805f9b34fb)
>         UUID: Phonebook Access Server
> (0000112f-0000-1000-8000-00805f9b34fb)
>         UUID: Audio Sink
> (0000110b-0000-1000-8000-00805f9b34fb)
>         UUID: Generic Access Profile
> (00001800-0000-1000-8000-00805f9b34fb)
>         UUID: Generic Attribute Profile
> (00001801-0000-1000-8000-00805f9b34fb)
>         UUID: Handsfree Audio Gateway
> (0000111f-0000-1000-8000-00805f9b34fb)
>         UUID: Audio Source
> (0000110a-0000-1000-8000-00805f9b34fb)
>         UUID: OBEX File Transfer
> (00001106-0000-1000-8000-00805f9b34fb)
>         UUID: Handsfree
> (0000111e-0000-1000-8000-00805f9b34fb)
>         Modalias: usb:v1D6Bp0246d0530
>         Discovering: no

It seems you have all the profiles necessary, perhaps there is some
interoperability problem, try checking bluetoothd and btmon logs.

-- 
Luiz Augusto von Dentz




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux