From 87ff5235952491d6f73c81b27a5e72b713bd1fc0 Mon Sep 17 00:00:00 2001 From: Xevion Date: Sat, 25 May 2024 20:17:23 -0500 Subject: [PATCH] Minor improvement to dual boot bluetooth post --- src/content/blog/bluetooth-pairing-while-dual-booting.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/content/blog/bluetooth-pairing-while-dual-booting.mdx b/src/content/blog/bluetooth-pairing-while-dual-booting.mdx index 2e56c52..6c01d5c 100644 --- a/src/content/blog/bluetooth-pairing-while-dual-booting.mdx +++ b/src/content/blog/bluetooth-pairing-while-dual-booting.mdx @@ -17,9 +17,11 @@ Recently, I built a new computer; my first in a while. It's prime purpose was to On separate SSDs with high quality components, booting between the two with [rEFInd][refind-boot-manager] has been fantastic. -Unfortunately, my choice to use Bose bluetooth headphones has been a malady on the experience, causing me to attempt to reconnect and re-pair them each time I switch OSes. +Unfortunately, my choice to use bluetooth headphones has been a malady on the experience, causing me to attempt to reconnect and re-pair them each time I switch OSes. -That said, with a couple of commands and a light understanding of MAC addresses, it isn't hard to ensure consistent pairing on both your Linux and Windows installations. +The issue is that the MAC address of my Bluetooth receiver is identical, but the pairing keys aren't shared naturally between my two operating systems. Only one pairing key can exist for a given MAC address inside my headphones. + +That said, with a couple of commands and a brief understanding of MAC addresses, it isn't hard to ensure consistent pairing on both your Linux and Windows installations. The whole process comes down to **copying the pairing key** (a token that verifies a previous pairing exists) from Windows to Linux. The reverse process can be figured out by reading this guide carefully.