bluetoothctl No default controller available

Question

It\'s a bit wired here.

I have a problem is bluetoothctl always said \"No default controller available\". I found there are many people had same problem with me. But th

Answer 1

Its an old thread, but might help someone looking for answers.

I have faced this problem most of the times, and the things I verify are:

1. systemctl status bluetooth == this checks if the bluetooth service daemon is already running or not. Check for output:
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) If not, start it using the command: sudo systemctl start bluetooth

2. using sudo bluetoothctl

one of these two was the culprit usually.