<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bluetooth on Corvus Blog</title><link>https://nicoleman0.github.io/blog-site/tags/bluetooth/</link><description>Recent content in Bluetooth on Corvus Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nicoleman0.github.io/blog-site/tags/bluetooth/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing Bluetooth Dual Boot on EndeavourOS and Windows</title><link>https://nicoleman0.github.io/blog-site/posts/bluetooth-dualboot/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://nicoleman0.github.io/blog-site/posts/bluetooth-dualboot/</guid><description>&lt;p>If you dual boot Linux and Windows and share Bluetooth devices between them, you&amp;rsquo;ve probably hit this annoying issue: the speakers connect fine on one OS, and then after switching, they refuse to pair on the other.&lt;/p>
&lt;p>When you pair a Bluetooth device, a link key is generated and stored on both the host and the device. The problem is that both Windows and Linux see the same physical Bluetooth adapter — same MAC address — but they don&amp;rsquo;t share their key stores. So when you pair on Linux, it writes a new key to the device. Boot into Windows, and Windows has a stale key that no longer matches. Pair on Windows, and now Linux is the one with the stale key.&lt;/p></description></item></channel></rss>