diff --git a/content/bluetooth.md b/content/bluetooth.md
index 37c101b898..5a7295bcf3 100644
--- a/content/bluetooth.md
+++ b/content/bluetooth.md
@@ -15,189 +15,258 @@ section: network-troubleshooting
tableOfContents: true
---
-## Important Notes About Bluetooth
+## Pairing and Removing Devices
-Bluetooth is a bit odd.
-There are a lot of factors that go into whether Bluetooth devices work together as expected.
+To pair a new device, open the Bluetooth applet located near the top-right corner of the screen, expand the "Other Bluetooth devices" drop-down, and select the device you wish to pair with.
-### Bluetooth version
+
-Bluetooth 5.0 is backwards compatible with older Bluetooth versions, but older bluetooth versioned devices are not always compatible with newer versions or devices.
+Alternatively, open the Settings app, navigate to the Bluetooth page, and select the device there.
-### Signal Interference
+
-Bluetooth uses the same bandwidth as the 2.4Ghz Wi-Fi band, and in most of our machines it is on the same chip as the Wi-Fi module. They usually have two antennae, one for Bluetooth, and one for Wi-Fi, but it is possible for other Wi-Fi or Bluetooth devices signals to cross and to cause connection issues. If users are in an area crowded with other Wi-Fi networks or devices, the interference from these outside sources can impact performance and range.
+Follow any prompts you see to confirm the connection (e.g. by entering a pairing code displayed on your device).
-### Device Specific Differences
+To temprarily disconnect from a device, click the device in the Bluetooth applet.
-Every Bluetooth device is different. They use the same or similar protocols, but the printed circuit boards (PCBs), are specific to each device, and the firmware they are running is often custom designed, and closed-source.
+
-Some of the code and technologies that make Bluetooth work reliably are patented, and only device vendors who have licensed the permission to use that patented technology will be able to experience the full benefits (for more information see the "Audio Input/Output" section below.)
+Alternatively, in the Settings app, click the three dots to the right of the device, and click Disconnect (to temporarily disconnect) or Forget (to unpair the device, requiring a manual re-pairing to use it again later).
-> Some devices, such as Apple or Sony headphones, particularly take advantage of these patents and technologies to ensure they work well with similar devices. Often these devices are not tested against Linux machines. That doesn't mean these devices will not work, only that behavior or performance may vary.
+
-### Kernel Versions
+## Enabling Bluetooth
-As the Linux kernel develops, support for more devices are added. Sometimes Bluetooth devices will work better in a different kernel version.
+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.
-### OS Versions
+
-Similar to the kernel versions. Improvements are often made in newer versions of Ubuntu and Pop!\_OS. Running software updates is always a good idea, followed by a reboot.
+Next, make sure Bluetooth is enabled in the top bar, or in the Bluetooth page of the Settings application.
-
+
-### Configuration Issues
+
-Sometimes Bluetooth devices are working correctly, but something in settings needs to be reset.
+If Bluetooth still isn't working, press `Super`+`T` to launch a Terminal, then check that the Bluetooth service is running with the following command:
-The easiest way to test this is to "forget" the paired Bluetooth device, and pair it again.
+```bash
+sudo systemctl status bluetooth
+```
-A more thorough way of testing this would be to create a [test user](/articles/other-accounts), or boot from a [Live Disk](/articles/live-disk) to see if Bluetooth works in either case.
-If it does, config files may need deleted. If it doesn't (especially in the Live Disk), reinstalling the OS may solve the problem.
-Reinstalling the OS won't affect Bluetooth hardware directly, but resetting and starting with a clean slate can solve a slew of problems and save time hunting for a specific file or bug.
+
-## Setting Expectations
+If it's stopped, enable it to auto-start and immediately start it using the following command:
-Because of all of these factors, if the steps outlined in the Bluetooth troubleshooting article, and the previous troubleshooting steps don't resolve the issue, the issue may not be resolved at all.
-Or, in a future update or change to the system, the devices may start working again. In some cases (many cases) users will not experience any issue with Bluetooth at all.
+```bash
+sudo systemctl enable --now bluetooth
+```
-### Audio Input/Output
+## Using Bluetooth Manager (blueman)
-Bluetooth audio devices, such as headphones and speakers, usually default to the A2DP protocol, which works effectively as an audio output source.
+A third-party program called Bluetooth Manager can sometimes pair and trust Bluetooth devices better than the default Bluetooth settings. Install it with this command:
-Bluetooth devices with microphones built in, can be used if the device supports HFP/HSP. However, without the technology that companies like Sony have patented, the solution is to divide up the audio stream so that some of it is used for audio out and some for audio in.
-This process lowers the sound quality of the stream when in HSP/HFP mode, so audio may be "tinny," compressed (lower-fidelity), or at a lower volume. That is expected behavior.
+```bash
+sudo apt install blueman
+```
-## Bluetooth Troubleshooting
+> After installing the above package, fully shut down the machine and then power it back on, rather than rebooting. This ensures the hardware completely resets.
-Bluetooth issues can be troubleshooted in several ways. The first thing to check is toggling airplane mode which will sometimes get Bluetooth functioning again. Next, make sure Bluetooth is enabled in the top bar, or in the Bluetooth system settings.
+Open Bluetooth Manager by pressing `Super` and searching for "blueman":
-Then, try reinstalling Bluetooth related software with this command, depending on the verison of Pop!\_OS you're using.
+
-*For Pop!\_OS 22.04 or higher:*
+On first launch, you may be asked if Bluetooth should be enabled automatically. Choose `Yes`.
-```bash
-sudo apt reinstall --purge bluez gnome-bluetooth
-```
+
-*For Pop!\_OS 21.10 or 20.04:*
+If the device is already paired, start by removing it to allow for a fresh connection. You can do this by selecting the deivce and clicking the `-` button.
-```bash
-sudo apt install --reinstall bluez gnome-bluetooth indicator-bluetooth pulseaudio-module-bluetooth
-```
+
-After reinstalling the above packages, fully shut down the machine and then power it back on, rather than rebooting. This ensures the hardware completely resets.
+Next, click the Search button, select your device from the list, and click the key icon to pair it again:
-If `tlp` is installed, then there may be settings interfering with Bluetooth functionality. Edit this file and disable Wifi and Bluetooth power saving features:
+
-```bash
-sudo gedit /etc/default/tlp
+Finally, right-click your paired device and select `Connect` to connect to it:
+
+
+
+## Using bluetoothctl
+
+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.
+
+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.
+
+
+
+If you have multiple Bluetooth controllers, you can list them with the `list` command, show information about them with `show `, and select one to use with `select ` command. Use `devices` to see a list of paired devices.
+
+Finally, connect with the device using the `connect ` command. A `Connection successful` message will appear if the connection succeeds.
-There is a program called Bluetooth Manager which is included with XFCE. It can sometimes pair and trust Bluetooth devices better than the default Bluetooth settings. Install it with:
+
+
+## Further Troubleshooting
+
+### Check TLP Settings
+
+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:
```bash
-sudo apt install blueman
+sudo nano /etc/tlp.conf
```
-Then, run Bluetooth Manager. Check for the device being trusted, and also try re-pairing in that program.
+### Bluetooth Version
-### Useful Commands
+Computers with newer Bluetooth versions will generally work with accessories built for older Bluetooth versions, but accessories requiring newer Bluetooth versions may not work on computers with older Bluetooth versions.
-To show if the Bluetooth module (driver) is loaded, and see what system messages have been logged:
+You can check your computer's Bluetooth version by installing and running the `inxi` tool:
-```bash
-lsmod | grep bluetooth
-dmesg | grep Bluetooth
```
+sudo apt install inxi
+inxi -E
+```
+
+The Bluetooth version for each wireless card will be displayed at the end of the `Report` line. For example, if the output says `bt-v: 5.2`, then your computer supports Bluetooth 5.2 (and below).
+
+### Signal Interference
+
+Bluetooth uses the same bandwidth as the 2.4Ghz Wi-Fi band, and in many computers, it uses the same wireless card and antennas as the W-Fi. If you're in an area crowded with other Wi-Fi networks or devices, the interference can impact Bluetooth performance and range.
+
+### Device-Specific Differences
+
+Every Bluetooth device is different. They use the same or similar protocols, but the printed circuit boards (PCBs) are specific to each device, and the firmware they run is often custom-designed and closed-source. Many devices are not tested against Linux systems by their manufacturers.
-To check if the service that handles Bluetooth is running:
+Some devices, such as Apple or Sony headphones, may utilize patentend technologies that aren't available on all computers or operating systems. That doesn't mean these devices won't work, but does mean their behavior or performance may vary.
+
+### Audio Input/Output
+
+Several audio protocols exist for handling audio steaming over Bluetooth:
+
+- **A2DP (Advanced Audio Distribution Profile)**: This protocol allows high-quality stereo audio streaming. However, with some devices, it only supports audio in one direction at a time (e.g. speakers only, no microphone).
+- **HSP (Bluetooth Headset Protocol) and HFP (Hands-Free Protocol):** These protocols allow bidirectional audio streaming (e.g. speakers and microphone at the same time), but are limited to lower-quality, mono audio.
+
+You can try a different device profile by navigating to Settings -> Sound -> Device Profiles and using the drop-down next to your device.
+
+#### Controlling Audio
+
+The default Settings app allows you to select one input or output device for all applications. You may want only certain applications to play through a Bluetooth speaker. PulseAudio Volume Control provides a more advanced GUI interface for routing audio in this manner. To install it, run this command:
```bash
-sudo systemctl status bluetooth
+sudo apt install pavucontrol
```
-To check if Bluetooth or Wireless (Wi-Fi) are software-blocked:
+There will be a drop-down in the Playback tab for each of your applications that's outputting sound, which you can use to select which set of speakers (e.g. built-in or Bluetooth) that application's sound will play through.
+
+### OS & Kernel Versions
+
+As the Linux kernel develops, support for more devices are added. Sometimes, Bluetooth devices will work better in a different kernel version.
+
+Running software updates and rebooting can ensure you're using the most recent available software for Bluetooth support.
+
+#### Linux Firmware Packages
+
+Sometimes, newer Linux firmware packages will contain bux fixes that aren't yet in the standard software repositories. Newer Linux firmware packages can be downloaded from here:
+
+[http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/](http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/)
+
+Then, they can be installed with this command (filling in the version numbers in the filename as appropriate):
```bash
-rfkill list
+sudo dpkg -i linux-firmware_#.###.#_all.deb
```
-To unblock Bluetooth:
+Rebooting is required to load the newly installed firmware.
-```
-sudo rfkill unblock bluetooth
-```
+### Configuration Issues
-To unblock all wireless types:
+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.
+
+### File Transfer
+
+Sometimes, additional programs need to be installed for mobile device file transfer to work. Install the Object Exchange (OBEX) packages with this command:
```bash
-sudo rfkill unblock all
+sudo apt install obexfs obexftp
```
-To manually reload the Bluetooth USB kernel module:
+Then connect (pair) to the device and see if file sending works.
+
+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.
+
+## Other Useful Commands
+
+### Logging
+
+To show kernel logs related to Bluetooth:
```bash
-sudo rmmod btusb
-sudo modprobe btusb
+sudo dmesg | grep -i Bluetooth
```
-To monitor Bluetooth-related messages (try leaving this command running while pairing or using a device to see any error messages or failures):
+To monitor Bluetooth events (try leaving this command running while pairing or using a device to see any error messages or failures):
```bash
sudo btmon
```
-To reset the Bluetooth device profiles and require re-pairing all devices (this can help if your Bluetooth audio device is stuck in an HSP/HFP profile and will not switch to A2DP mode after updates [1](https://github.com/bluez/bluez/issues/157)):
+### Blocks
+
+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.
+
+To check if Bluetooth or Wireless LAN (Wi-Fi) are blocked:
```bash
-sudo rm -r /var/lib/bluetooth/
+rfkill list
```
-*For Pop!\_OS 21.10 or 20.04:*
-
-Older Pop!\_OS versions used a PulseAudio module for Bluetooth audio. It's typically loaded by default, but sometimes a manual load can get Bluetooth headsets working again:
+To unblock Bluetooth:
```bash
-pactl load-module module-bluetooth-discover
+sudo rfkill unblock bluetooth
```
-## Additional Info
+To unblock all wireless types:
-Here are a few additional tidbits about the Bluetooth system that may help with troubleshooting.
+```bash
+sudo rfkill unblock all
+```
-### Controlling audio
+### Kernel Modules
-Once you are connected to a Bluetooth speaker, you may need to change where your current audio is "routed". You can get a more advanced interface to settings on audio with the program called PulseAudio Volume Control. To install, run this command:
+To show what Bluetooth kernel modules (drivers) are loaded:
```bash
-sudo apt install pavucontrol
+lsmod | grep bluetooth
```
-There will be a drop-down in the Playback tab for each of your applications that is outputting sound that you should be able to change to your Bluetooth speaker.
-
-### Linux Firmware
+To manually reload the Bluetooth USB kernel module:
-Occasionally the kernel and/or Linux firmware will have problems. Sometimes, newer Linux firmware packages will have fixed bugs that aren't yet in the repositories. They can be downloaded from here:
+```bash
+sudo rmmod btusb
+sudo modprobe btusb
+```
-[http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/](http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/)
+### Resetting Bluetooth Devices
-Then they can be installed with this command:
+Resetting the Bluetooth device profiles will require re-pairing all devices:
```bash
-sudo dpkg -i linux-firmware_#.###.#_all.deb
+sudo rm -r /var/lib/bluetooth/
```
-> You'll need to replace the numbers/file name with the most current version after downloading it.
-
-### File Transfer
+This can help if your Bluetooth audio device is stuck on an HSP/HFP profile and won't switch to A2DP mode.
-Sometimes, additional programs need to be installed for mobile equipment file transfer. Please install the transfer tool with this command:
+## Get Support for Ongoing Bluetooth Issues
-```bash
-sudo apt install obexfs obexftp
-```
+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.
-Then connect (pair) to the device and see if send files works. To receive files over Bluetooth you will need to enable the option in Personal File Sharing.
+Bluetooth compatibility can depend on a variety of hardware and software factors. While Bluetooth often works flawlessly, certain devices may never be trouble-free with a particular computer or OS, while other devices may start working with software updates at a later date.
diff --git a/static/images/bluetooth/airplane-mode.webp b/static/images/bluetooth/airplane-mode.webp
new file mode 100644
index 0000000000..74b891b281
Binary files /dev/null and b/static/images/bluetooth/airplane-mode.webp differ
diff --git a/static/images/bluetooth/blueman-connect.webp b/static/images/bluetooth/blueman-connect.webp
new file mode 100644
index 0000000000..110b1c9e94
Binary files /dev/null and b/static/images/bluetooth/blueman-connect.webp differ
diff --git a/static/images/bluetooth/blueman-first-launch.webp b/static/images/bluetooth/blueman-first-launch.webp
new file mode 100644
index 0000000000..cedd19a725
Binary files /dev/null and b/static/images/bluetooth/blueman-first-launch.webp differ
diff --git a/static/images/bluetooth/blueman-launcher.webp b/static/images/bluetooth/blueman-launcher.webp
new file mode 100644
index 0000000000..f359765152
Binary files /dev/null and b/static/images/bluetooth/blueman-launcher.webp differ
diff --git a/static/images/bluetooth/blueman-pair.webp b/static/images/bluetooth/blueman-pair.webp
new file mode 100644
index 0000000000..1fc30a34f7
Binary files /dev/null and b/static/images/bluetooth/blueman-pair.webp differ
diff --git a/static/images/bluetooth/blueman-remove.webp b/static/images/bluetooth/blueman-remove.webp
new file mode 100644
index 0000000000..ef56600f11
Binary files /dev/null and b/static/images/bluetooth/blueman-remove.webp differ
diff --git a/static/images/bluetooth/bluetooth-enable-applet.webp b/static/images/bluetooth/bluetooth-enable-applet.webp
new file mode 100644
index 0000000000..7cc8bfab38
Binary files /dev/null and b/static/images/bluetooth/bluetooth-enable-applet.webp differ
diff --git a/static/images/bluetooth/bluetooth-enable-settings.webp b/static/images/bluetooth/bluetooth-enable-settings.webp
new file mode 100644
index 0000000000..7b41b59a30
Binary files /dev/null and b/static/images/bluetooth/bluetooth-enable-settings.webp differ
diff --git a/static/images/bluetooth/bluetooth-systemd-status.webp b/static/images/bluetooth/bluetooth-systemd-status.webp
new file mode 100644
index 0000000000..b8a5dea13e
Binary files /dev/null and b/static/images/bluetooth/bluetooth-systemd-status.webp differ
diff --git a/static/images/bluetooth/bluetoothctl-connection.webp b/static/images/bluetooth/bluetoothctl-connection.webp
new file mode 100644
index 0000000000..3b0d7ee872
Binary files /dev/null and b/static/images/bluetooth/bluetoothctl-connection.webp differ
diff --git a/static/images/bluetooth/bluetoothctl-launch.webp b/static/images/bluetooth/bluetoothctl-launch.webp
new file mode 100644
index 0000000000..a3d68b99cf
Binary files /dev/null and b/static/images/bluetooth/bluetoothctl-launch.webp differ
diff --git a/static/images/bluetooth/devices-available-applet.webp b/static/images/bluetooth/devices-available-applet.webp
new file mode 100644
index 0000000000..d97afc0142
Binary files /dev/null and b/static/images/bluetooth/devices-available-applet.webp differ
diff --git a/static/images/bluetooth/devices-available-settings.webp b/static/images/bluetooth/devices-available-settings.webp
new file mode 100644
index 0000000000..bde32ed241
Binary files /dev/null and b/static/images/bluetooth/devices-available-settings.webp differ
diff --git a/static/images/bluetooth/devices-connected-applet.webp b/static/images/bluetooth/devices-connected-applet.webp
new file mode 100644
index 0000000000..0599340213
Binary files /dev/null and b/static/images/bluetooth/devices-connected-applet.webp differ
diff --git a/static/images/bluetooth/devices-connected-settings.webp b/static/images/bluetooth/devices-connected-settings.webp
new file mode 100644
index 0000000000..6e3412ff09
Binary files /dev/null and b/static/images/bluetooth/devices-connected-settings.webp differ