+- Maui Forums (https://forums.mauilinux.org)
+-- Forum: Maui Support (https://forums.mauilinux.org/forumdisplay.php?fid=74)
+--- Forum: Hardware (https://forums.mauilinux.org/forumdisplay.php?fid=85)
+--- Thread: [Solved] Bluetooth Not Working... (/showthread.php?tid=24589)
[Solved] Bluetooth Not Working... - PinStripe - 24th August 2017
Laptop: HP 14-AL061NR
Headset: JBL EB40 BT
I NEED to get this connected!
Bluetooth reports connected, though the sound is Still playing through the laptop speakers and Not the headset.
What can I do to get my headset fully connected?
Here is a couple things I've tried:
$ lspci -nnk | grep -iA3 net; lsusb; rfkill list; dmesg | egrep -i 'blue|firm'
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [103c:8209]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81)
DeviceName: Intel Dual BandWireless-AC 3165 802.11 ac 1x1 WiFi + BT 4.0 Combo Adapter
Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010]
Kernel driver in use: iwlwifi
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[ 0.554959] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 7.633800] [Firmware Bug]: Invalid critical threshold (0)
[ 7.931134] [drm] GuC firmware load skipped
[ 17.949666] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[ 17.949707] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[ 18.027805] iwlwifi 0000:03:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
[ 18.247489] Bluetooth: Core ver 2.21
[ 18.247506] Bluetooth: HCI device and connection manager initialized
[ 18.248486] Bluetooth: HCI socket layer initialized
[ 18.248489] Bluetooth: L2CAP socket layer initialized
[ 18.248495] Bluetooth: SCO socket layer initialized
[ 18.343709] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 18.382224] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 18.628651] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 21.090334] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.090335] Bluetooth: BNEP filters: protocol multicast
[ 21.090338] Bluetooth: BNEP socket layer initialized
[ 81.475580] Bluetooth: RFCOMM TTY layer initialized
[ 81.475585] Bluetooth: RFCOMM socket layer initialized
[ 81.475589] Bluetooth: RFCOMM ver 1.11
[ 572.254669] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.254674] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.254676] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.264796] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.264812] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.264818] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 577.306561] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 577.306577] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 2514.395698] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2514.395717] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2514.405711] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2514.405729] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2514.405738] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2514.415695] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2519.454255] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 3363.854700] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3363.854709] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3363.854713] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3363.864800] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3363.864809] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3363.864812] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3368.894606] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 3368.894621] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 3384.750711] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3384.750728] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3384.750736] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3384.760705] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3384.760718] Bluetooth: hci0 SCO packet for unknown connection handle 0
$ bluetoothctl
[NEW] Controller AC:2B:6E:C8:95
C maui [default][NEW] Device 00:22:37:34:FC:A5 JBL E40BT
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller AC:2B:6E:C8:95
C Discovering: yes[CHG] Device 00:22:37:34:FC:A5 Connected: yes
[CHG] Device 00:22:37:34:FC:A5 Connected: no
[CHG] Device 00:22:37:34:FC:A5 Connected: yes
scover40BT]# pactl load-module module-bluetooth-di
Invalid command
RE: Bluetooth Not Working... - leszek - 25th August 2017
Could it be that the soundserver just does not switch automatically to that device. Can you change the output device manually to the bluetooth one and see if it works.
This thread might help you:
https://askubuntu.com/questions/589885/automatically-switch-sound-output-device-to-bluetooth-headset-force-to-a2dp-pr
RE: Bluetooth Not Working... - PinStripe - 25th August 2017
(25th August 2017, 9:39)leszek Wrote: Could it be that the soundserver just does not switch automatically to that device. Can you change the output device manually to the bluetooth one and see if it works.
This thread might help you:
https://askubuntu.com/questions/589885/automatically-switch-sound-output-device-to-bluetooth-headset-force-to-a2dp-pr
I did a search and No such file in Maui to add code like that thread suggests:
Code:
/etc/pulse/default.paBut Yes, I tried changing the default output device to the headset and it now works, though the sound quality is not the same as in windows. The sound actually sounds like I'm listening to a TV from the next room over... where windows is super clear.
Is there a way to create a file to make the switch on its own? And if so, where would I put it in Maui?
RE: Bluetooth Not Working... - leszek - 25th August 2017
Like I said the link is what you need to configure pulseaudio.
As for the quality I think it uses the wrong codec that's all.
A2DP is the one with the higher quality. You can configure that with pavucontrol or in systemsettings.
RE: Bluetooth Not Working... - PinStripe - 25th August 2017
(25th August 2017, 17:59)leszek Wrote: Like I said the link is what you need to configure pulseaudio.
As for the quality I think it uses the wrong codec that's all.
A2DP is the one with the higher quality. You can configure that with pavucontrol or in systemsettings.
Why wouldn't you guys set the correct codec for the OS?
I looked in system setting and did not see where to change to A2DP. What are the steps, please?
RE: Bluetooth Not Working... - leszek - 25th August 2017
On my testing machine High-Fidelity-Playback (A2DP) is set as default codec for my Bluetooth device.
The bluetooth sender and receiver negotiate which standards they support and use by default. This is nothing we can set as default for all devices.
You need to go into systemsettings -> multimedia and on the second tab you should choose your bluetooth audio device and there you should have the ability to set the profile.
RE: Bluetooth Not Working... - PinStripe - 25th August 2017
(25th August 2017, 20:21)leszek Wrote: On my testing machine High-Fidelity-Playback (A2DP) is set as default codec for my Bluetooth device.
The bluetooth sender and receiver negotiate which standards they support and use by default. This is nothing we can set as default for all devices.
You need to go into systemsettings -> multimedia and on the second tab you should choose your bluetooth audio device and there you should have the ability to set the profile.
Sorry... but I don't see what you're talking about.
What I see is Audiocd Slave Configuration after clicking on Multimedia from the system settings.
The tabs from left to right are: General - Names - FLAC Encoder - MP3 Encoder - Ogg Vorbis Encoder
Under Names, I see Nothing that pertains to my JBL headset. It is about File name, Track name and
file location.
See attachment
RE: Bluetooth Not Working... - leszek - 25th August 2017
I meant this kcontrol module
Code:
kcmshell5 kcm_phononRE: Bluetooth Not Working... - PinStripe - 25th August 2017
(25th August 2017, 21:03)leszek Wrote: I meant this kcontrol module
(execute in a shell to launch it)Code:kcmshell5 kcm_phonon
oK... i GOT IT...
Thanks!!