PINE64

Hi all,
I'd like to use the PINE64 as a Bluetooth audio sink, but unfortunately it appears that the hardware doesn't support this option. Am I missing something? Is it a limitation of the chip or of the driver?

Here's the uname:

Code:
root@pine64:~# uname -a

Linux pine64 3.10.102-2-pine64-longsleep #66 SMP PREEMPT Sat Jul 16 10:53:13 CEST 2016 aarch64 GNU/Linux

root@pine64:~#

Here's the output of bluetoothctl:

Code:
[bluetooth]# show

Controller 34:C3:D2:BF:85:79

        Name: pine64

        Alias: pine64

        Class: 0x000420

        Powered: yes

        Discoverable: no

        Pairable: yes

        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)

        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)

        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)

        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)

        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)

        Modalias: usb:v1D6Bp0246d052B

        Discovering: no

[bluetooth]#

For comparison, here's what it looks like on my laptop (Arch):

Code:
[bluetooth]# show

Controller 60:57:18:C2:5A:05

        Name: milosz

        Alias: milosz

        Class: 0x1c010c

        Powered: yes

        Discoverable: yes

        Pairable: yes

        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)

        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)

        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)

        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)

        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)

        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)

        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)

        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)

        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)

        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)

        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)

        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)

        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)

        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)

        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)

        Modalias: usb:v1D6Bp0246d052B

        Discovering: no

[bluetooth]#

Cheers!
j.

I don't think it's a limitation of the hardware since at least on Android I tested some BT audio devices like my speakers and a headset and those profiles are not listed there either. The BT module is controlled via one UART and has a PCM interface with full duplex to the audio-codec, so I guess it's a question of getting documentation or drivers from Realtek? The module gets loaded with a firmware during initialization, I guess it also depends on what profiles are in this binary blob...

jszmidt

xalius