Ok, I’m ‘new’ to Bluetooth, I’ve always preferred physically connected devices vs wireless protocols. In my most recent pc build (Black Friday 2023), I decided to jump onto wireless stuff, so I have a Bluetooth Mouse now.
Everything works, but…bluetooth is slow to start or even doesn’t automatically start.
So…I have KDE running with no mouse. I can either plug in a USB mouse and go turn on bluetooth in the KDE settings or I can open a terminal and ‘bluetoothctl/power on’ (and it may find the mouse) or may require ‘scan on’ (or maybe I’m just not waiting long enough). Typically now it is working.
So…assume I’m idiot and tell me what stupid thing I have done (aside from buying a bluetooth mouse). The problem seems to be with the bluetooth interface vs the mouse itself? Of course, this is somewhat erratic and everything may work fine for a week or two.
This is all that seems pertinent in the journal when it didn’t find it this morning.
kdeconnectd[3722]: 2025-01-13T00:05:00 kdeconnect.core: No local bluetooth adapter found
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb type: USB
Report: btmgmt ID: hci0 state: up address: 74:97:79:EB:C4:10 bt-v: 5.2
I ran into this a bit with a keyboard, speaker and a mouse. Normally I could quickly get it working again but it was just a nightmare at times. I mean I would be in the middle of typing and all the sudden bluetooth just cut off. There were also times I would have to remove the device and re add just to get it to work again. At the end of the day I just decided that some bluetooth devices just don’t seem to play very well with my setup and removed them.
Mine has (so far) never failed other than on startup. It could be a timing/race issue I guess.
I do have this issue with my Android-phone (OnePlus) considering my wireless head-phones.
On my laptop with Gnome they connect almost instantly.
Really odd.
Hmm, that does bring up a question. I may install a non-KDE (probably cosmic) partition and run there a while and see if it seems like KDE is the culprit (would be sad to leave KDE), if no one has any better suggestions in the next day or two.
I have some feeling it’s hardware on the motherboard (ie who wants MediaTek or other scruffy components).
Well I think that if you use a bluetooth device in two places, you always have to reconnect it, because I think the address of the device is stored in it’s memory or something like that. HP has mice that can hold more then one address.
My mouse has three bluetooth settings…that never seems to come into play with issues (well unless they’re internal and hidden). Typically I can move through them successfully (one for Windows, one for Linux distro #1, one for Linux distro #2).
Though yes, this does add to complexity and possible faliures, but as I said, the problem seems to lie with the bluetooth controller, not the device.
Ok, after a few more days of observation (and actually paying attention), it’s still flaky…however, once I wake the adapter up, mouse detection depends on the mouse not setting itself to sleep mode (can’t control that (and probably don’t want to, for battery life), so wiggle the mouse before activating adapter).
As to the initial error, I can only assume somewhat flaky implementation (motherboard).
kf.bluezqt: PendingCall Error: “The name is not activatable”
kdeconnect.core: No local bluetooth adapter found