Skip to content

Commit 0b2e2cb

Browse files
committed
Update COSMIC screenshots to latest version & optimize PNGs
1 parent 5898a34 commit 0b2e2cb

23 files changed

Lines changed: 45 additions & 77 deletions

content/bluetooth.md

Lines changed: 45 additions & 77 deletions
Original file line numberDiff line numberDiff line change
@@ -35,11 +35,11 @@ Alternatively, in the Settings app, click the three dots to the right of the dev
3535

3636
![Connected Bluetooth devices in the Settings app](/images/bluetooth/devices-connected-settings.png)
3737

38-
## Troubleshooting
38+
## Enabling Bluetooth
3939

4040
If Bluetooth isn't working, first try toggling airplane mode on and back off. This can be done using a keyboard shortcut if your keyboard has one (look for a key with an airplane symbol, commonly `Fn`+`F11` or `Fn`+`F9` on System76 laptops). Otherwise, use the option at the top of the Wi-Fi menu near the top-right corner of your screen.
4141

42-
![Airplane mode toggle in WiFi menu](/images/bluetooth/airplane-mode.png)
42+
![Airplane mode toggle in WiFi menu](/images/bluetooth/airplane-mode.avif)
4343

4444
Next, make sure Bluetooth is enabled in the top bar, or in the Bluetooth page of the Settings application.
4545

@@ -53,15 +53,15 @@ If Bluetooth still isn't working, press `Super`+`T` to launch a Terminal, then c
5353
sudo systemctl status bluetooth
5454
```
5555

56-
![bluetooth status systemd](/images/bluetooth/bluetooth_5.png)
56+
![bluetooth status systemd](/images/bluetooth/bluetooth-systemd-status.png)
5757

5858
If it's stopped, enable it to auto-start and immediately start it using the following command:
5959

6060
```bash
6161
sudo systemctl enable --now bluetooth
6262
```
6363

64-
### Using Bluetooth Manager (blueman)
64+
## Using Bluetooth Manager (blueman)
6565

6666
A third-party program called <u>Bluetooth Manager</u> can sometimes pair and trust Bluetooth devices better than the default Bluetooth settings. Install it with this command:
6767

@@ -91,6 +91,31 @@ Finally, right-click your paired device and select `Connect` to connect to it:
9191

9292
![Pair device](/images/bluetooth/blueman-connect.png)
9393

94+
## Using bluetoothctl
95+
96+
The `bluetoothctl` program offers control, flexibility, and efficiency through precise management of Bluetooth devices via the terminal. For troubleshooting, `bluetoothctl` provides direct feedback and logs, which can help identify connection issues, detect devices, or configure settings in real time. It’s also useful for headless or remote setups where a user interface might not be available.
97+
98+
To get started, ensure Bluetooth is unblocked by running `sudo rfkill unblock bluetooth` in a terminal, then run `bluetoothctl` to enter the Bluetooth control tool.
99+
100+
![bluetoothctl](/images/bluetooth/bluetoothctl-launch.png)
101+
102+
If you have multiple Bluetooth controllers, you can list them with the `list` command, show information about them with `show <MAC address>`, and select one to use with `select <MAC address`.
103+
104+
Power the controller on and scan for available devices to connect to using the following commands:
105+
106+
```
107+
power on
108+
scan on
109+
```
110+
111+
Devices with human-readable names (such as a product name) will show them after the MAC address. To pair with a device, use the `trust <MAC address>` command. Use `devices` to see a list of paired devices.
112+
113+
Finally, connect with the device using the `connect <MAC address>` command. A `Connection successful` message will appear if the connection succeeds.
114+
115+
![bluetootctl trusting & connecting to a device](/images/bluetooth/bluetoothctl-connection.png)
116+
117+
## Further Troubleshooting
118+
94119
### Check TLP Settings
95120

96121
If `tlp` is installed, then there may be settings interfering with Bluetooth functionality. Edit this file and disable any WiFi and Bluetooth power saving features:
@@ -155,66 +180,31 @@ Rebooting is required to load the newly installed firmware.
155180

156181
Beyond forgetting and re-pairing deivces, you can check if any local configuration files are causing problems with a device by creating a [test user](/articles/other-accounts) or booting from a [live disk](/articles/live-disk) to see if Bluetooth works in either case. If it does, config files in your normal user account may need to be deleted.
157182

158-
### Using bluetoothctl
159-
160-
The `bluetoothctl` program offers control, flexibility, and efficiency through precise management of Bluetooth devices via the terminal. For troubleshooting, `bluetoothctl` provides direct feedback and logs, which can help identify connection issues, detect devices, or configure settings in real time. It’s also useful for headless or remote setups where a user interface might not be available.
161-
162-
To get started, ensure Bluetooth is unblocked by running `rfkill` to check and enable it if necessary. Use the command `rfkill unblock bluetooth` to ensure that Bluetooth is not disabled at the system level.
163-
164-
Then, run `bluetoothctl` in a terminal to enter the Bluetooth control tool.
165-
166-
![bluetoothctl](/images/bluetooth/bluetooth_6.png)
167-
168-
If you have multiple Bluetooth controllers, choose the one you wish to connect to the device:
169-
170-
Check list of controllers:
171-
```
172-
list
173-
```
183+
### Controlling Audio
174184

175-
Check controller information:
176-
```
177-
info <controller_address>
178-
```
185+
Once you're connected to a Bluetooth speaker, you may need to change where your current audio is "routed." PulseAudio Volume Control provides a more advanced GUI interface for routing audio. To install it, run this command:
179186

180-
Select the controller you want to use:
181-
```
182-
select <mac address>
187+
```bash
188+
sudo apt install pavucontrol
183189
```
184190

185-
Make sure to power it on
186-
```
187-
power on
188-
```
189-
![bluetoothctl power on](/images/bluetooth/bluetooth_7.png)
191+
There will be a drop-down in the Playback tab for each of your applications that's outputting sound, which you can use to send audio from individual applications to your Bluetooth speaker.
190192

191-
Look for the device you want to connect:
192-
```
193-
scan on
194-
```
195-
Add trusted device
196-
```
197-
trust <mac address>
198-
```
199-
See list of paired devices:
193+
### File Transfer
200194

201-
```
202-
devices
203-
```
195+
Sometimes, additional programs need to be installed for mobile device file transfer to work. Install the Object Exchange (OBEX) packages with this command:
204196

205-
To connect the device:
206-
```
207-
connect <mac address>
197+
```bash
198+
sudo apt install obexfs obexftp
208199
```
209-
![bluetootctl list scan trust connect](/images/bluetooth/bluetooth_8.png)
210200

211-
Successful device connection:
201+
Then connect (pair) to the device and see if file sending works.
212202

213-
![bluetooothctl device connected](/images/bluetooth/bluetooth_9.png)
203+
On GNOME environments (such as Pop!_OS 22.04 and below), you may need to enable the Personal File Sharing option in Settings for file receiving to work.
214204

215-
### Useful Commands
205+
## Other Useful Commands
216206

217-
#### Logging
207+
### Logging
218208

219209
To show kernel logs related to Bluetooth:
220210

@@ -228,7 +218,7 @@ To monitor Bluetooth events (try leaving this command running while pairing or u
228218
sudo btmon
229219
```
230220

231-
#### Blocks
221+
### Blocks
232222

233223
The `rfkill` utility shows whether Bluetooth or Wi-Fi are blocked in software or hardware. Generally, this information corresponds to whether airplane mode is enabled, but it can be useful to check separately in case of bugs in the airplane mode GUI or other components.
234224

@@ -250,7 +240,7 @@ To unblock all wireless types:
250240
sudo rfkill unblock all
251241
```
252242

253-
#### Kernel Module
243+
### Kernel Module
254244

255245
To show what Bluetooth kernel modules (drivers) are loaded:
256246

@@ -265,7 +255,7 @@ sudo rmmod btusb
265255
sudo modprobe btusb
266256
```
267257

268-
#### Resetting Bluetooth Devices
258+
### Resetting Bluetooth Devices
269259

270260
Resetting the Bluetooth device profiles will require re-pairing all devices:
271261

@@ -275,28 +265,6 @@ sudo rm -r /var/lib/bluetooth/
275265

276266
This can help if your Bluetooth audio device is stuck on an HSP/HFP profile and won't switch to A2DP mode.
277267

278-
### Controlling Audio
279-
280-
Once you're connected to a Bluetooth speaker, you may need to change where your current audio is "routed." PulseAudio Volume Control provides a more advanced GUI interface for routing audio. To install it, run this command:
281-
282-
```bash
283-
sudo apt install pavucontrol
284-
```
285-
286-
There will be a drop-down in the Playback tab for each of your applications that's outputting sound, which you can use to send audio from individual applications to your Bluetooth speaker.
287-
288-
### File Transfer
289-
290-
Sometimes, additional programs need to be installed for mobile device file transfer to work. Install the Object Exchange (OBEX) packages with this command:
291-
292-
```bash
293-
sudo apt install obexfs obexftp
294-
```
295-
296-
Then connect (pair) to the device and see if file sending works.
297-
298-
On GNOME environments (such as Pop!_OS 22.04 and below), you may need to enable the Personal File Sharing option in Settings for file receiving to work.
299-
300268
## Get Support for Ongoing Bluetooth Issues
301269

302270
If you own a System76 computer and you're still experiencing Bluetooth problems after troubleshooting with the above steps, [open a support ticket](https://system76.com/contact/support) for additional assistance.
-266 Bytes
Loading
-92 Bytes
Loading
-7 Bytes
Loading
-395 Bytes
Loading
-268 Bytes
Loading
-71 Bytes
Loading
60.3 KB
Loading
-41.8 KB
Binary file not shown.
-119 KB
Binary file not shown.

0 commit comments

Comments
 (0)