Cannot connect via bluetooth

Max2Play Home 2016 (en) Forums Max2Play Add-ons Cannot connect via bluetooth

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  MarioM Moderator 1 week ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • 15. Oktober 2020 at 12:38 #49847

    Hello,

    I have a Raspi3 with HifiBerry running on max2play 2.52.
    I activated my license and installed bluetooth support. I was able to connect my cellphone (OnePlus 7 Pro, Android 10) once but I never was able to hear any music. When I disconnect and connect again, the connection is established but immediately dropped. Can you help me?

    Here is the Bluetooth DEBUG output:

    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####
    hci0: Type: Primary Bus: UART
    BD Address: B8:27:EB:87:7F:72 ACL MTU: 1021:8 SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:5352 acl:57 sco:0 events:225 errors:0
    TX bytes:4859 acl:60 sco:0 commands:132 errors:0

    #### DEVICE OnePlus 7 Pro ####
    spawn /usr/bin/bluetoothctl
    Waiting to connect to bluetoothd…
    [0;94m[bluetooth][0m#

    [[0;92mNEW[0m] Controller B8:27:EB:87:7F:72 max2play2 [default]
    [0;94m[bluetooth][0m#

    [[0;92mNEW[0m] Device 98:09:CF:75:FC:31 OnePlus 7 Pro
    [0;94m[bluetooth][0m# info 98:09:CF:75:FC:31
    Device 98:09:CF:75:FC:31
    Name: OnePlus 7 Pro
    Alias: OnePlus 7 Pro
    Class: 0x5a020c
    Icon: phone
    Paired: yes
    Trusted: no
    Blocked: no
    Connected: no
    LegacyPairing: no
    quit
    UUID: Dialup Networking (00001103-0000-1000-8000-00805f9b34fb)
    UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
    UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
    UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
    UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
    UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
    UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific (deab91e4-670f-11e1-9ace-30bc4824019b)
    Modalias: bluetooth:v001Dp1200d1436
    [0;94m[bluetooth][0m# quit
    [0;94m[bluetooth][0m#

    [[0;91mDEL[0m] Controller B8:27:EB:87:7F:72 max2play2 [default]
    [0;94m[bluetooth][0m#

    Waiting to connect to bluetoothd…

    #### BLUEALSA RUNNING ####
    2

    Regards

    Clarenze

    16. Oktober 2020 at 14:41 #49850

    Hi Clarenze,

    Thank you for the debug info. In order to narrow down the problem, please answer the following questions: Have you enabled direct streaming to the sound card or installed streaming to the Squeezebox Server? Do you use a bluetooth dongle or the integrated bluetooth? Do you use our stretch image or buster?

    17. Oktober 2020 at 10:10 #49854

    Hi,

    It is configured to „direct streaming to the soundcard“.
    I intend to use the integrated bluetooth adapter.
    The Debian version is 9.4. It is the image provided by you (I bought a pre-installed max2play package).

    Regards

    Clarenze

    20. Oktober 2020 at 11:50 #49869

    Hi Clarenze,

    Please make sure you have followed the steps for direct Bluetooth streaming on our wiki: https://www.max2play.com/en/wiki/bluetooth-direct-stream/

    If the problem persists, please try to download a new stretch image from our download page and burn it to the SD card. Then try the Bluetooth connection again.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here