Axios different than these?
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
Can't Connect or Enable Bluetooth on Plasma
- Edited
Changed my mind put this into terminal and watch it as you issue commands
like turn bluetooth off/on, make discoverable
and lets see if its talking on Dbus
sudo dbus-monitor --system path=/org/bluez/hci0
This also kinda out in left field if your using wifi have you tried bluetooth without wifi on?
Well....I have a new problem now.....
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-232.current status: kernel-api
Server-1: PulseAudio v: 15.0 status: active
Bluetooth:
Message: No bluetooth data found.
Axios Okay fixed that
╰─λ inxi -EAZ 0 (0.000s) < 07:42:25
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-232.current status: kernel-api
Server-1: PulseAudio v: 15.0 status: active
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Can't even get to record anything....
╰─λ bluetoothctl 0 (0.023s) < 07:48:19
Agent registered
[bluetooth]# power on
No default controller available
I updated (on unstable) and restarted, bluetooth wasn't even there. I removed the manually installed driver and rebooted, bluetooth was there and it was enabled (at least it appeared so in system settings). I tried to pair my headphones and it sat on the scanning screen for a while. I closed it and tried again, this time it said my device wasn't pairable.
Now if I run inxi -EAZ i'm back to No data found on my bluetooth device.......
Brucehankins I have lost track on your issue now.
and where it stands
Axios no worries, it's still borked. When I restart or fresh boot, I can "see" my Intel ax200 Bluetooth and it's registered.
As soon as I try and connect to anything or run commands with bluetoothctl the device disappears. Bluetoothctl and inxi both say there is no Bluetooth device. If I reboot, it pops back up, but I still can't connect to anything.
Well, I have suggestions.
- Install kernel lts. Does BT work, run the commands related to blutetoothctl, inxi -E and other helpful.
- Start Solus Live. Does BT work, run the commands related to blutetoothctl, inxi -E and other helpful.
- Start another Linux Live distribution. (as above)
pomon 4.3 Plasma Live ISO connected as well as a few other distros run through ventoy. I'm sure it's something I did at this point, but I'm not sure what. Maybe something I did with TLP and Powertop? Either way, the fastest solution to me was just do a fresh install.
- Best Answerset by TraceyC
In case someone comes across this thread or there is someone smarter than me that can provide an answer, it happened again and I've found the cause this time. After I reinstalled my system, everything was fine, bluetooth was connecting, headphones and controllers worked, life was good. I installed TLP to try and help battery performance and ran sudo tlp start and sudo systemctl enable tlp.service. Made no changes to the default TLP configuration file, didn't run recalibrate, anything, just installed and started. Shut down my laptop went about my day, and just turned it on a few moments ago to find that bluetooth would not enable and it said no controllers were found. Removed TLP and rebooted, everything works again.
- Edited
a reinstall makes sense that the BT would be working again. but the TLP thing is strange; seemingly so unrelated.
"I hate the weird ones."
Glad you figured it out
edit/word
- Edited
Brucehankins I ran across that in my travels Had it in the back of my mind
but I cant really remb alot I think they killed the service or something and restarted or something
but after they did that didnt seem to have issue.
Man going from memory sorry not of help I will look back when have time see if I saved it.
Yes there was issues with bluetooth and tlp
But those commands above dont look familiar to what I read.
I thought at the time should I save this. (maybe i did)
- Edited
brent when you introduce a program to control the battery power or conserve it
That might be something we looked at earlier. I think Tom was using something of the kind in order to extend his battery life. I don't run my laptops without an A/C connection, so it wasn't very exciting for me. The proposed answer makes a lot of sense. There needs to be a way to tell it to make an exception of Bluetooth.
- Edited
I would start by looking in tlp.conf anything about bluethtooth related and see about disabling autosuspend for bluetooth
Been reading best answer I can give for starters
of coarse if you disable that prob effect yer battery but if you need bluetooth got do what you gotta do.
Its a lowpower item unless you are paired so its kinda mute then
I just uninstalled TLP. I've got power-profiles-daemon, cpufrequtils, and powertop all working to get me that extra 5 minutes 
. Really though, I need to read up on configuring tlp more before I reinstall it. Unfortunately my speakers are terrible, so to watch anything at an acceptable volume I connect my JBL Go portable via Bluetooth, so it's a bit of a necessity for me right now. Actual speakers are out of the question because I only use it for media when lounging in bed or on the couch.
According to Arch folks, TLP and power-profiles-daemon are incompatible as they both fight to manage power.
Also check if your Bluetooth adapter is on a USB bus: if so, check your USB settings in TLP.
clauded yeah, they are in conflict l, I've removed TLP for power-profiles-daemon. My Bluetooth is built in to my m.2 AX200 card.
WetGeek Don't use ChatGPT as a search engine, because it's not.