O alto-falante Bluetooth se conecta, mas não toca música

1

Eu pareço tentadoramente ter meu alto-falante bluetooth Beoplay P2 funcionando com meu laptop Ubuntu / KDE:

Todos os utilitários bluetooth concordam que o alto-falante está conectado. Por exemplo, a saída de inicialização bluetoothctl s inclui:

    [NEW] Device 04:FE:A1:4B:0F:EA Fenchurch

que é o dispositivo de alto-falante. (Seu nome é Fenchurch .) Quando eu peço mais detalhes, o que eu recebo parece razoável:

[bluetooth]# info 04:FE:A1:4B:0F:EA
Device 04:FE:A1:4B:0F:EA
    Name: Fenchurch
    Alias: Fenchurch
    Class: 0x240414
    Icon: audio-card
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    Modalias: bluetooth:v0103p1005d0100

A configuração Bluetooth do KDE também afirma que o alto-falante está conectado, e o próprio alto-falante tem uma luz indicadora que concorda.

O dispositivo aparece no widget de volume de áudio do Plasma:

Eletambémapareceempavuctl:

Aindamaistentador,quandoeuajusteiovolumeempavuctl,oalto-falanteemsifazumtomdereconhecimento!Masesteéoúnicosomqueeupossotocá-lo.

Osomsaidosalto-falantesinternosdolaptop,exatamentecomoeuesperava.

Oquedevoinvestigar?Qualéopróximopasso?

Maisinformações,outalvezinformaçõesimportantes:

  • Meutelefonepodeseconectaraoalto-falanteereproduzi-losemdificuldades.
  • Naverdade,quandoeutenhoSpotifyabertonomeulaptopemeutelefone,spotifypodedizeraotelefoneparatocarmúsica,quesaidoalto-falanteBluetoothconectado!
  • QuandodesativoaconexãoBluetoothdotelefone,estoucertodequeoalto-falanteestáconectadoaolaptop,eleexibeumindicadorverdeemvezdebranco.Issosignificaqueestánomodo"viva voz". Não tenho certeza de como isso difere de ser um orador regular.

alsamixer diz que há apenas uma placa de som. Parece assim:

ÉpossívelqueeureconheçaoP2digitandoonomecerto,masnãoseicomoencontraronome.

Deacordocomasolicitaçãoabaixo,aquiestáasaídadesystemctlstatusbluetooth:

●bluetooth.service-BluetoothserviceLoaded:loaded(/lib/systemd/system/bluetooth.service;enabled;vendorpreset:enabled)Active:active(running)sinceFri2018-07-2711:09:02EDT;9minagoDocs:man:bluetoothd(8)MainPID:915(bluetoothd)Status:"Running"
       CGroup: /system.slice/bluetooth.service
               └─915 /usr/lib/bluetooth/bluetoothd

    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0017 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x003d for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint unregistered: sender=:1.56 path=/MediaEndpoint/A2DPSource
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint unregistered: sender=:1.56 path=/MediaEndpoint/A2DPSink
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x000a for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0013 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0017 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x003d for device 04:FE:A1:4B:0F:EA

Aqui está a saída de journalctl -n 50 :

    -- Logs begin at Fri 2018-07-27 11:09:01 EDT, end at Fri 2018-07-27 11:17:01 EDT. --
    Jul 27 11:10:10 avocet org.kde.kdeconnect[1527]: kdeconnect.plugin.notification: removeNotification "0|com.spotify.music|2131363975|null|10143"
    Jul 27 11:10:10 avocet org.kde.kdeconnect[1527]: kdeconnect.core: "The remote host closed the connection"
    Jul 27 11:10:10 avocet org.kde.kdeconnect[1527]: kdeconnect.core: "The remote host closed the connection"
    Jul 27 11:12:31 avocet org.kubuntu.DriverManager[1527]: Traceback (most recent call last):
    Jul 27 11:12:31 avocet org.kubuntu.DriverManager[1527]:   File "/usr/lib/x86_64-linux-gnu/libexec/DriverManager_DBus", line 24, in <module>
    Jul 27 11:12:31 avocet org.kubuntu.DriverManager[1527]:     import dbus
    Jul 27 11:12:31 avocet org.kubuntu.DriverManager[1527]: ModuleNotFoundError: No module named 'dbus'
    Jul 27 11:14:00 avocet org.kde.kdeconnect[1527]: kdeconnect.plugin.notification: Destroying NotificationsPlugin
    Jul 27 11:14:00 avocet org.kde.kdeconnect[1527]: kdeconnect.plugin.notification: Destroying NotificationsListener
    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x000a for device 04:FE:A1:4B:0F:EA
    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0013 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0017 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:14:40 avocet bluetoothd[915]: Unable to register GATT service with handle 0x003d for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:21 avocet sudo[3074]: pam_ecryptfs: pam_sm_authenticate: /home/mjd is already mounted
    Jul 27 11:15:21 avocet sudo[3074]:      mjd : TTY=pts/2 ; PWD=/home/mjd ; USER=root ; COMMAND=/usr/bin/pkill pulseaudio
    Jul 27 11:15:21 avocet sudo[3074]: pam_unix(sudo:session): session opened for user root by mjd(uid=0)
    Jul 27 11:15:21 avocet sudo[3074]: pam_unix(sudo:session): session closed for user root
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint unregistered: sender=:1.56 path=/MediaEndpoint/A2DPSource
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint unregistered: sender=:1.56 path=/MediaEndpoint/A2DPSink
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Successfully made thread 3091 of process 3091 (n/a) owned by '1000' high priority at nice level -11.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 1 threads of 1 processes of 1 users.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 1 threads of 1 processes of 1 users.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Successfully made thread 3093 of process 3091 (n/a) owned by '1000' RT at priority 5.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 2 threads of 1 processes of 1 users.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 2 threads of 1 processes of 1 users.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Successfully made thread 3094 of process 3091 (n/a) owned by '1000' RT at priority 5.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 3 threads of 1 processes of 1 users.
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource
    Jul 27 11:15:21 avocet bluetoothd[915]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink
    Jul 27 11:15:21 avocet pulseaudio[3091]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Successfully made thread 3096 of process 3096 (n/a) owned by '1000' high priority at nice level -11.
    Jul 27 11:15:21 avocet rtkit-daemon[1654]: Supervising 4 threads of 2 processes of 1 users.
    Jul 27 11:15:21 avocet pulseaudio[3096]: [pulseaudio] pid.c: Daemon already running.
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x000a for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0013 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x0017 for device 04:FE:A1:4B:0F:EA
    Jul 27 11:15:41 avocet bluetoothd[915]: Unable to register GATT service with handle 0x003d for device 04:FE:A1:4B:0F:EA
    Jul 27 11:16:41 avocet kernel: input: 04:FE:A1:4B:0F:EA as /devices/virtual/input/input22
    Jul 27 11:16:44 avocet rtkit-daemon[1654]: Supervising 3 threads of 1 processes of 1 users.
    Jul 27 11:16:44 avocet rtkit-daemon[1654]: Successfully made thread 3145 of process 3091 (n/a) owned by '1000' RT at priority 5.
    Jul 27 11:16:44 avocet rtkit-daemon[1654]: Supervising 4 threads of 1 processes of 1 users.
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:16:44 avocet kernel: Bluetooth: hci0 SCO packet for unknown connection handle 0
    Jul 27 11:17:01 avocet CRON[3147]: pam_unix(cron:session): session opened for user root by (uid=0)
    Jul 27 11:17:01 avocet CRON[3148]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jul 27 11:17:01 avocet CRON[3147]: pam_unix(cron:session): session closed for user root
    
por Mark Dominus 27.07.2018 / 16:47

2 respostas

1

Aha! Em pavuctl , há um botão para conectar uma fonte de som, como mplayer , a um dispositivo de saída específico:

Aquiestáescrito"Estéreo Analógico de Áudio Incorporado". Mas se eu clicar nele, um menu aparece:

Selecionar"Fenchurch" faz a saída mplayer sair do P2.

Eu posso fazer o mesmo para o Spotify.

Suponho que o próximo passo seria entender como fazer com que o sistema prefira o P2 quando ele estiver disponível. Esta questão parece relevante . Mas por enquanto eu tenho uma solução suficiente para continuar com o meu dia.

    
por 27.07.2018 / 17:28
0

Você tentou ativar o som da placa de som usando alsamixer ? Além disso, você pode compartilhar de systemctl status bluetooth e journalctl -n 50 ?

    
por 27.07.2018 / 16:57