Announcement

Collapse
No announcement yet.

serious bluetooth issues

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    serious bluetooth issues

    Hello

    I'm running Kubuntu 24.04.2 LTS on Dell Inspiron 15 3530 i5
    Everything went fine for about year of use until moment, when I was working on battery without power cord and laptop went to sleep (that's my observation, not 100% sure this is the situation or cause).
    After that moment, I wasn't able to work with my bluetooth mouse or use bluetooth head phones to listen to music, I wasn't able to reconnect to devices visible in bluetooth tab running in system tray.

    This is the output from command line:

    Code:
    uname -a
Linux martin-inspiron153530 6.8.0-63-generic #66-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 13 20:25:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
    ​

    Code:
    sudo lsusb -v | grep -i bluetooth
Bus 001 Device 009: ID 0bda:887b Realtek Semiconductor Corp. Bluetooth Radio
bDeviceProtocol 1 Bluetooth
idProduct 0x887b Bluetooth Radio
iProduct 2 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
bInterfaceProtocol 1 Bluetooth
iInterface 4 Bluetooth Radio
    Code:
    systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-07-10 09:18:02 CEST; 28min ago
Docs: man:bluetoothd(8)
Main PID: 1155 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18713)
Memory: 3.4M (peak: 4.3M)
CPU: 45ms
CGroup: /system.slice/bluetooth.service
└─1155 /usr/libexec/bluetooth/bluetoothd

júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_1
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_0
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream_duplex
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/opus_05
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/opus_05
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/opus_05_duplex
júl 10 09:18:12 martin-inspiron153530 bluetoothd[1155]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/opus_05_duplex
    ​
    Code:
    bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# list
Controller A8:3B:76:DA:90:24 martin-inspiron153530 [default]
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]#
    (headfones put into pairing mode, but don't show up)
    ​
    Code:
    rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
    Code:
    sudo dmesg | grep -i "bluetooth" | tail -n 20
[ 4.355873] Bluetooth: HCI socket layer initialized
[ 4.355875] Bluetooth: L2CAP socket layer initialized
[ 4.355879] Bluetooth: SCO socket layer initialized
[ 4.548156] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[ 4.549071] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 4.549090] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[ 4.550442] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[ 4.551030] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[ 4.878158] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[ 4.963029] Bluetooth: hci0: AOSP extensions version v1.00
[ 4.963033] Bluetooth: hci0: AOSP quality report is supported
[ 9.103794] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.103798] Bluetooth: BNEP filters: protocol multicast
[ 9.103803] Bluetooth: BNEP socket layer initialized
[ 9.105508] Bluetooth: MGMT ver 1.22
[ 9.216138] Bluetooth: hci0: AOSP extensions version v1.00
[ 9.216152] Bluetooth: hci0: AOSP quality report is supported
[ 11.543042] Bluetooth: RFCOMM TTY layer initialized
[ 11.543048] Bluetooth: RFCOMM socket layer initialized
[ 11.543053] Bluetooth: RFCOMM ver 1.11
    Code:
    ​sudo dmesg | grep -i "realtek" | tail -n 20
[ 2.996310] usb 1-10: Manufacturer: Realtek
[ 8.065713] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 8.065722] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 8.065725] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 8.065727] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 8.065729] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 8.065730] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 8.065732] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1b
[ 8.065735] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
    Code:
    ​
​rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
    Code:
    lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 067b:2586 Prolific Technology, Inc. USB 2.0 Hub
Bus 001 Device 003: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 001 Device 004: ID 067b:2586 Prolific Technology, Inc. USB 2.0 Hub
Bus 001 Device 005: ID 27c6:639c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 001 Device 006: ID 1bcf:2283 Sunplus Innovation Technology Inc. Full HD webcam
Bus 001 Device 007: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 008: ID 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
Bus 001 Device 009: ID 0bda:887b Realtek Semiconductor Corp. Bluetooth Radio
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    ​
    I also did more advanced settings:

    Code:
    sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=-1"
sudo update-grub
sudo reboot
    Code:
    echo 'ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0bda", ATTR{idProduct}=="887b", ATTR{power/autosuspend}=="-1"' | sudo tee /etc/udev/rules.d/99-realtek-bt-fix.rules
sudo udevadm control --reload-rules
sudo udevadm trigger
sudo reboot
    ​

    I also did
    Code:
    sudo systemctl restart bluetooth
    and restarted laptop too
    ​
    nothing has helped... any suggestions or experience with this serious issue? Thank you
    Last edited by MartinDT; Jul 10, 2025, 02:25 AM.
    Tags: None
    • Top
    • Bottom
    #2
    just to add, during time, I also updated kernel by incoming updates from initial linux-image-6.8.0-60-generic through linux-image-6.8.0-62-generic
    ​to mentioned actual linux-image-6.8.0-63-generic
    ​
    ​
    • Top
    • Bottom

    Comment

      #3
      Have you tried booting to a previous kernel via your grub menu

      Originally posted by MartinDT View Post
      Code:
      Bus 001 Device 009: ID 0bda:887b Realtek Semiconductor Corp. Bluetooth Radio
      Realtek wifi/bluetooth cards are notorously finicky/picky.

      it might be worth updating to the current HWE kernel, which may have morew solid support for this card.

      A way to test is to boot a live session of the current 24.04 ISO image which has this kernel by default.

      Installing it is not hard, just edit this to use 24.04 instead.

      This does not remove 6.8 kernel, so you would have at least one version of that is keptup to date alongside the 6.11
      Last edited by claydoh; Jul 10, 2025, 03:12 AM.
      ​
      • Top
      • Bottom
      • Likes 1

      Comment

        #4
        Gemini AI:

        You're already on Ubuntu 24.04.2 LTS with Kernel 6.8.0-63-generic, which means you are already using the Hardware Enablement (HWE) kernel!

        Starting with Ubuntu 20.04 LTS (and continuing with 22.04 LTS and your 24.04 LTS), the default kernel provided at installation and through regular updates is the HWE kernel. This kernel line automatically gets updated with newer versions from subsequent Ubuntu releases (e.g., your 24.04 LTS will get kernels from future non-LTS releases like 24.10, 25.04, etc., as part of its HWE stack).

        Your current kernel, 6.8.0-63-generic, is indeed the latest stable HWE kernel for Ubuntu 24.04.2 LTS.

        Therefore, performing an "HWE kernel upgrade" won't install a different or newer kernel than what you currently have through the standard update channels.

        If you're looking for a newer kernel version:
        1. Wait for Future Point Releases: The kernel will be automatically updated to a newer HWE version (e.g., 6.9.x, 6.10.x, etc.) when future point releases of Ubuntu 24.04 LTS (like 24.04.3, 24.04.4, etc.) are released and integrate newer kernels. This is the recommended and safest approach for an LTS system.
        2. Ensure your system is fully updated: Always make sure you have the very latest updates for your current HWE kernel:

          Bash
          sudo apt update
          sudo apt full-upgrade
          sudo reboot


          This will ensure you have the absolute latest 6.8.x kernel available for 24.04.2 LTS.
        3. Manually Install a Mainline Kernel (Advanced & Not Recommended for Stability):

          If you desperately need a kernel newer than what 24.04.2 LTS currently offers and cannot wait for future point releases, you could manually install a mainline kernel from Ubuntu's kernel PPA. However, this is generally not recommended for stability on an LTS system, as mainline kernels are not officially supported by Ubuntu and may lack specific patches or long-term stability guarantees. They can sometimes introduce new issues.

        Given that your kernel 6.8.0-63-generic is very recent, it already includes a lot of the latest hardware support. The Bluetooth issue you're facing might be more nuanced than just needing a newer kernel version within the HWE stack, especially since we confirmed the /mnt/ solution works for SMB video playback.
        ​
        • Top
        • Bottom

        Comment

          #5
          AI doesn't quite grok that Kubuntu has slight differences from Ubuntu Desktop, and is a bit behind (say ~6 months)
          It is always worth double and triple checking these, even though the AI is getting better. The whole Linux ecosphere moves quickly, and these "ai"can easily have outdated and incorrect info.

          Originally posted by MartinDT View Post
          Gemini AI:

          You're already on Ubuntu 24.04.2 LTS with Kernel 6.8.0-63-generic, which means you are already using the Hardware Enablement (HWE) kernel!
          Not true as the current HWE kernel as of February 2025 is 6.11, and in the coming weeks will move to the 6.14. You only have the original 6.8.

          For Kubuntu, Ubuntu Server and probably others, this also is a bit incorrect, as older Kubuntu 24.04 installs, Ubuntu Server, or those using older Kubuntu ISO images do NOT get HWE automatically, unlike the Mothership Ubuntu Desktop. (I still do not know why)
          So, in this case at least checking that the hwe packages are installed is useful, to make sure.

          6.11 provides a better set of Realtek drivers, but it may or may not be relevant for your specific chip, since your Bt I assume was working before? But Realtek are picky and PITAs very often.


          Originally posted by MartinDT View Post
          , I also updated kernel by incoming updates from initial linux-image-6.8.0-60-generic through linux-image-6.8.0-62-generic
          ​to mentioned actual linux-image-6.8.0-63-generic
          ​
          This isn't a new kernel, but a security fix for the current 6.8.0. BUT, have you tried booting to the previous kernel just in case?
          ​
          • Top
          • Bottom

          Comment

          Previous template Next

          Users Viewing This Topic

          Collapse

          There are 0 users viewing this topic.

          Working...
          X