Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

[Contourné] Connexion Bluetooth avec enceinte Bose

quentind

Bonjour,

Même matos Bose Revolve.
Sur Ubuntu 20.04
Son faible et aussi : les boutons volume de la Bose ne marche pas (ça n'augmente ou ne diminue pas le son).
Et ça vient pas du matos car si je connecte la Bose à mon smartphone, la liaison marche bien.

Pas mal de recherche mais rien de fructueux malheureusement..

Merciiii de l'aide !

quentind

Merciii de l'aide
Je ne savais pas s'il fallait le faire avec le bluetooth connecté avec l'appareil ou non.

Version bluetooth non allumé, non connecté à l'enceinte Bose

Linux quentin-ekimia 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
3b:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
	Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1558:1403]
	Kernel driver in use: r8169
	Kernel modules: r8169
40:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 001 Device 003: ID 8087:0029 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[    3.975019] Bluetooth: Core ver 2.22
[    3.975042] Bluetooth: HCI device and connection manager initialized
[    3.975047] Bluetooth: HCI socket layer initialized
[    3.975050] Bluetooth: L2CAP socket layer initialized
[    3.975053] Bluetooth: SCO socket layer initialized
[    4.006812] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[  188.156148] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[  188.157096] Bluetooth: hci0: Device revision is 1
[  188.157101] Bluetooth: hci0: Secure boot is enabled
[  188.157103] Bluetooth: hci0: OTP lock is enabled
[  188.157105] Bluetooth: hci0: API lock is enabled
[  188.157107] Bluetooth: hci0: Debug lock is disabled
[  188.157110] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  188.160531] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  189.939974] Bluetooth: hci0: Waiting for firmware download to complete
[  189.940122] Bluetooth: hci0: Firmware loaded in 1743320 usecs
[  189.940233] Bluetooth: hci0: Waiting for device to boot
[  189.955256] Bluetooth: hci0: Device booted in 14718 usecs
[  189.955767] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[  189.958129] Bluetooth: hci0: Applying Intel DDC parameters completed
[  192.516638] Bluetooth: RFCOMM TTY layer initialized
[  192.516642] Bluetooth: RFCOMM socket layer initialized
[  192.516645] Bluetooth: RFCOMM ver 1.11
[    0.761869] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[    3.960660] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[    3.960686] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[    3.968114] iwlwifi 0000:40:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[    3.990861] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    4.006812] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[    4.027313] iwlwifi 0000:40:00.0: Allocated 0x00400000 bytes for firmware monitor.
[  188.157110] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  188.160531] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  189.939974] Bluetooth: hci0: Waiting for firmware download to complete
[  189.940122] Bluetooth: hci0: Firmware loaded in 1743320 usecs
bluetooth             548864  30 btrtl,btintel,btbcm,btusb,rfcomm
ecdh_generic           16384  1 bluetooth

ii  bluez                                         5.53-0ubuntu3                         amd64        Bluetooth tools and daemons
ii  bluez-cups                                    5.53-0ubuntu3                         amd64        Bluetooth printer driver for CUPS
ii  bluez-obexd                                   5.53-0ubuntu3                         amd64        bluez obex daemon
ii  gir1.2-gnomebluetooth-1.0:amd64               3.34.3-0ubuntu1                       amd64        Introspection data for GnomeBluetooth
ii  gnome-bluetooth                               3.34.3-0ubuntu1                       amd64        GNOME Bluetooth tools
ii  libbluetooth3:amd64                           5.53-0ubuntu3                         amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth13:amd64                    3.34.3-0ubuntu1                       amd64        GNOME Bluetooth tools - support library
ii  libkf5bluezqt-data                            5.68.0-0ubuntu1                       all          data files for bluez-qt
ii  libkf5bluezqt6:amd64                          5.68.0-0ubuntu1                       amd64        Qt wrapper for bluez
ii  pulseaudio-module-bluetooth                   1:13.99.1-1ubuntu3.8                  amd64        Bluetooth module for PulseAudio sound server
ii  qml-module-org-kde-bluezqt:amd64              5.68.0-0ubuntu1                       amd64        QML wrapper for bluez

1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2020-12-25 19:38:09 CET; 4h 34min ago
       Docs: man:bluetoothd(8)
   Main PID: 900 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9116)
     Memory: 3.3M
     CGroup: /system.slice/bluetooth.service
             └─900 /usr/lib/bluetooth/bluetoothd --plugin=a2dp

déc. 25 19:38:09 quentin-ekimia bluetoothd[900]: Ignoring (cli) battery
déc. 25 19:38:09 quentin-ekimia bluetoothd[900]: Ignoring (cli) sixaxis
déc. 25 19:38:09 quentin-ekimia bluetoothd[900]: Bluetooth management interface 1.14 initialized
déc. 25 20:24:45 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSink/sbc
déc. 25 20:24:45 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc
déc. 25 20:25:15 quentin-ekimia bluetoothd[900]: connect error: Host is down (112)
déc. 25 20:25:30 quentin-ekimia bluetoothd[900]: connect error: Host is down (112)
déc. 25 20:25:45 quentin-ekimia bluetoothd[900]: connect error: Host is down (112)
déc. 25 20:26:08 quentin-ekimia bluetoothd[900]: /org/bluez/hci0/dev_60_AB_D2_34_FD_EC/sep1/fd0: fd(44) ready
déc. 25 20:45:18 quentin-ekimia bluetoothd[900]: Failed to set mode: Blocked through rfkill (0x12)

Version bluetooth allumé, connecté à l'enceinte Bose

Linux quentin-ekimia 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
3b:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
	Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1558:1403]
	Kernel driver in use: r8169
	Kernel modules: r8169
40:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 001 Device 003: ID 8087:0029 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[    3.975019] Bluetooth: Core ver 2.22
[    3.975042] Bluetooth: HCI device and connection manager initialized
[    3.975047] Bluetooth: HCI socket layer initialized
[    3.975050] Bluetooth: L2CAP socket layer initialized
[    3.975053] Bluetooth: SCO socket layer initialized
[    4.006812] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[  188.156148] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[  188.157096] Bluetooth: hci0: Device revision is 1
[  188.157101] Bluetooth: hci0: Secure boot is enabled
[  188.157103] Bluetooth: hci0: OTP lock is enabled
[  188.157105] Bluetooth: hci0: API lock is enabled
[  188.157107] Bluetooth: hci0: Debug lock is disabled
[  188.157110] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  188.160531] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  189.939974] Bluetooth: hci0: Waiting for firmware download to complete
[  189.940122] Bluetooth: hci0: Firmware loaded in 1743320 usecs
[  189.940233] Bluetooth: hci0: Waiting for device to boot
[  189.955256] Bluetooth: hci0: Device booted in 14718 usecs
[  189.955767] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[  189.958129] Bluetooth: hci0: Applying Intel DDC parameters completed
[  192.516638] Bluetooth: RFCOMM TTY layer initialized
[  192.516642] Bluetooth: RFCOMM socket layer initialized
[  192.516645] Bluetooth: RFCOMM ver 1.11
[14024.319421] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[14024.320442] Bluetooth: hci0: Device revision is 1
[14024.320444] Bluetooth: hci0: Secure boot is enabled
[14024.320444] Bluetooth: hci0: OTP lock is enabled
[14024.320445] Bluetooth: hci0: API lock is enabled
[14024.320446] Bluetooth: hci0: Debug lock is disabled
[14024.320448] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[14024.320452] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[14025.969289] Bluetooth: hci0: Waiting for firmware download to complete
[14025.969445] Bluetooth: hci0: Firmware loaded in 1612304 usecs
[14025.969461] Bluetooth: hci0: Waiting for device to boot
[14025.984560] Bluetooth: hci0: Device booted in 14757 usecs
[14025.984563] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[14025.986568] Bluetooth: hci0: Applying Intel DDC parameters completed
[    0.761869] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[    3.960660] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[    3.960686] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[    3.968114] iwlwifi 0000:40:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[    3.990861] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    4.006812] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[    4.027313] iwlwifi 0000:40:00.0: Allocated 0x00400000 bytes for firmware monitor.
[  188.157110] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  188.160531] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  189.939974] Bluetooth: hci0: Waiting for firmware download to complete
[  189.940122] Bluetooth: hci0: Firmware loaded in 1743320 usecs
[14024.320448] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[14024.320452] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[14025.969289] Bluetooth: hci0: Waiting for firmware download to complete
[14025.969445] Bluetooth: hci0: Firmware loaded in 1612304 usecs
bluetooth             548864  34 btrtl,btintel,btbcm,btusb,rfcomm
ecdh_generic           16384  2 bluetooth

ii  bluez                                         5.53-0ubuntu3                         amd64        Bluetooth tools and daemons
ii  bluez-cups                                    5.53-0ubuntu3                         amd64        Bluetooth printer driver for CUPS
ii  bluez-obexd                                   5.53-0ubuntu3                         amd64        bluez obex daemon
ii  gir1.2-gnomebluetooth-1.0:amd64               3.34.3-0ubuntu1                       amd64        Introspection data for GnomeBluetooth
ii  gnome-bluetooth                               3.34.3-0ubuntu1                       amd64        GNOME Bluetooth tools
ii  libbluetooth3:amd64                           5.53-0ubuntu3                         amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth13:amd64                    3.34.3-0ubuntu1                       amd64        GNOME Bluetooth tools - support library
ii  libkf5bluezqt-data                            5.68.0-0ubuntu1                       all          data files for bluez-qt
ii  libkf5bluezqt6:amd64                          5.68.0-0ubuntu1                       amd64        Qt wrapper for bluez
ii  pulseaudio-module-bluetooth                   1:13.99.1-1ubuntu3.8                  amd64        Bluetooth module for PulseAudio sound server
ii  qml-module-org-kde-bluezqt:amd64              5.68.0-0ubuntu1                       amd64        QML wrapper for bluez

1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2020-12-25 19:38:09 CET; 4h 43min ago
       Docs: man:bluetoothd(8)
   Main PID: 900 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9116)
     Memory: 3.2M
     CGroup: /system.slice/bluetooth.service
             └─900 /usr/lib/bluetooth/bluetoothd --plugin=a2dp

déc. 25 20:25:30 quentin-ekimia bluetoothd[900]: connect error: Host is down (112)
déc. 25 20:25:45 quentin-ekimia bluetoothd[900]: connect error: Host is down (112)
déc. 25 20:26:08 quentin-ekimia bluetoothd[900]: /org/bluez/hci0/dev_60_AB_D2_34_FD_EC/sep1/fd0: fd(44) ready
déc. 25 20:45:18 quentin-ekimia bluetoothd[900]: Failed to set mode: Blocked through rfkill (0x12)
déc. 26 00:17:05 quentin-ekimia bluetoothd[900]: Endpoint unregistered: sender=:1.130 path=/MediaEndpoint/A2DPSink/sbc
déc. 26 00:17:05 quentin-ekimia bluetoothd[900]: Endpoint unregistered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc
déc. 26 00:17:06 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSink/sbc
déc. 26 00:17:06 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc
déc. 26 00:17:06 quentin-ekimia bluetoothd[900]: Failed to set mode: Blocked through rfkill (0x12)
déc. 26 00:19:03 quentin-ekimia bluetoothd[900]: /org/bluez/hci0/dev_60_AB_D2_34_FD_EC/sep1/fd1: fd(41) ready

xubu1957

Le 25/12/2020 à 20:47 a écritBonjour,

Il faudrait fournir, en te servant du Retour utilisable de commande :

uname -a; lspci -nnk | grep -iA3 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth

dpkg -l | grep blue

rfkill list all

et avec un terminal dont au préalable la fenêtre est élargie afin de ne pas tronquer l'image :

sudo service bluetooth status

cqfd93 a écritAstuce pour copier / coller sans erreur :

triple clic gauche pour sélectionner et copier une ligne entière

clic molette pour coller dans le terminal

Messages détachés par notre modération de ce fil > Enceinte bluetooth Bose Soundlink Revolve - Son faible malgré sur-amp

_ _ _

Bonjour,

Avec :

déc. 26 00:17:06 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSink/sbc
déc. 26 00:17:06 quentin-ekimia bluetoothd[900]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc

pour des retours similaires , dans > [Résolu] Son faible casque Bose bluetooth

Le 24/11/2020, xubu a écritBonjour,

Je trouve > linuxhint.com/per_application_sound_volume_ubuntu

Mais il faudrait les avis d'aidants connaisseurs.

Donne aussi :

iwconfig

nmcli dev wifi

pour voir les fréquences et les canaux utilisés.

quentind

Je vais tenter de suivre le lien de xubu après.
En attendant :

enp59s0f1  no wireless extensions.

wlp64s0   IEEE 802.11  ESSID:"Livebox-f744"  
          Mode:Managed  Frequency:2.442 GHz  Access Point: 5C:33:8E:08:2C:99   
          Bit Rate=78 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=63/70  Signal level=-47 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:54   Missed beacon:0

lo        no wireless extensions.

IN-USE  BSSID              SSID          MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        52:33:8E:08:2C:99  orange        Infra  7     130 Mbit/s  99      ▂▄▆█  --        
*       5C:33:8E:08:2C:99  Livebox-f744  Infra  7     130 Mbit/s  97      ▂▄▆█  WPA1 WPA2 
        30:7C:B2:CD:8F:EA  Livebox-8fe6  Infra  1     195 Mbit/s  20      ▂___  WPA1 WPA2

xubu1957

Il faut mettre un seul chiffrement WPA2, comme indiqué au § 1 > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier

Et tester un canal 6 au lieu du 7 > lafibre.info/wifi/quel-canal-wi-fi-choisir-pour-optimiser-son-debit

quentind

Ok, ça n'a pas de rapport avec le soucis de bluetooth on est d'accord ? ^^

xubu1957

La carte intel-wi-fi-6-ax200 est une carte combo wifi/Bluetooth.

J'essaye de proposer les réglages les plus utiles.

xubu1957

Vu cette réponse dans > [SOLVED] Bluetooth pairing and connectivity failure on fresh install

Montre :

dmesg | grep iwlwifi

quentind

ça marche, je ne comprenais pas !
après modifs wifi (ce qui n'a pas résolu mon soucis de bouton non fonctionnel) :

quentin@quentin-ekimia:~$ nmcli dev wifi
IN-USE  BSSID              SSID          MODE   CHAN  RATE        SIGNAL  BARS  SECURITY 
*       5C:33:8E:08:2C:99  Livebox-f744  Infra  6     130 Mbit/s  71      ▂▄▆_  WPA2     
quentin@quentin-ekimia:~$ iwconfig
enp59s0f1  no wireless extensions.

wlp64s0   IEEE 802.11  ESSID:"Livebox-f744"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 5C:33:8E:08:2C:99   
          Bit Rate=117 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=61/70  Signal level=-49 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:5   Missed beacon:0

lo        no wireless extensions.

[    3.778426] iwlwifi 0000:40:00.0: enabling device (0000 -> 0002)
[    3.808231] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[    3.808248] iwlwifi 0000:40:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[    3.812126] iwlwifi 0000:40:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[    3.812130] iwlwifi 0000:40:00.0: Found debug destination: EXTERNAL_DRAM
[    3.812132] iwlwifi 0000:40:00.0: Found debug configuration: 0
[    3.812433] iwlwifi 0000:40:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[    3.894249] iwlwifi 0000:40:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    3.906766] iwlwifi 0000:40:00.0: Applying debug destination EXTERNAL_DRAM
[    3.907339] iwlwifi 0000:40:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    4.062975] iwlwifi 0000:40:00.0: base HW address: e0:d4:e8:73:f8:a7
[    4.154831] iwlwifi 0000:40:00.0 wlp64s0: renamed from wlan0
[    5.879581] iwlwifi 0000:40:00.0: Applying debug destination EXTERNAL_DRAM
[    6.028705] iwlwifi 0000:40:00.0: FW already configured (0) - re-configuring
[    6.033533] iwlwifi 0000:40:00.0: BIOS contains WGDS but no WRDS
[ 1496.475357] iwlwifi 0000:40:00.0: Applying debug destination EXTERNAL_DRAM
[ 1496.631586] iwlwifi 0000:40:00.0: FW already configured (0) - re-configuring
[ 1496.636676] iwlwifi 0000:40:00.0: BIOS contains WGDS but no WRDS

xubu1957

Ta Livebox gère t-elle les fréquences 5 GHz ?

quentind

J'ai la Livebox 2.
À priori non.

xubu1957

Tu as une carte wifi ultra performante, mais une Box trop ancienne.

quentind

Mais c'est quoi le lien entre la livebox et le lien entre l'enceinte Bose et mon ordi ?
Comment ça vient perturber le truc je veux dire ? 🙂

xubu1957

J'avais lu des infos de ce genre > macbidouille.com/news/2014/02/07/oui-le-bluetooth-peut-entrer-en-conflit-avec-le-wi-fi

quentind

Okeeeey !
Mais vu que ça marche avec mon téléphone sur le même réseau wifi.. (mais p-e que mon téléphone n'était pas connecté au wifi ceci dit)

xubu1957

Le bouton volume de l'enceinte, tu as essayé d'appuyer pendant une dizaine de secondes ?

quentind

ça ne fait rien.

Pour info mon ordi capte deux fois le bluettoth de la Bose.
Bose Revolve Soundlink
et LE-Bose Revolve Soundlink

quentind

Fin de la mission : on a décidé d'échanger la Bose par la JBL Charge 4 qui marche parfaitement avec tous les téléphones et ordi Ubuntu qu'on avait ici !
Dommage pour la science ! en espérant qu'une mise à jour du firmware de la Bose facilite tout ça.

On peut donc clore cette discussion.

xubu1957

Pour éditer ta discussion et rajouter [Contourné] au début du titre, il faut utiliser le bouton Modifier au bas de ton premier message.

Merci 😉