🩸 BlueVein

Forget about re-pairing Bluetooth devices

Dual-boot without the headache

🚀 Quick Start - ⚡ How It Works - 🔬 Technical Details - 💬 Support

Pair your device once in any OS.
Switch between Windows and Linux.
Everything works automatically. Forever.

# Install via AUR
yay -S bluevein-bin

# Start the service
sudo systemctl enable --now bluevein

# Check status
sudo systemctl status bluevein

# 1. Clone and build
git clone https://github.com/meowrch/BlueVein.git
cd BlueVein
cargo build --release

# 2. Install
sudo cp target/release/bluevein /usr/bin/
sudo cp ./systemd/bluevein.service /etc/systemd/system/

# 3. Run
sudo systemctl daemon-reload
sudo systemctl enable --now bluevein

# 4. Verify
sudo systemctl status bluevein

1. Go to Releases
2. Download bluevein.exe from the latest release
3. Open PowerShell as Administrator
4. Execute:

# Install and start
.\bluevein.exe install
.\bluevein.exe start

# Verify
Get-Service BlueVeinService

# 1. Build
cargo build --release
cd target\release

# 2. Open PowerShell as Administrator

# 3. Install and start
.\bluevein.exe install
.\bluevein.exe start

# 4. Verify
Get-Service BlueVeinService

# Start/stop/restart
sudo systemctl start bluevein
sudo systemctl stop bluevein
sudo systemctl restart bluevein

# Status and logs
sudo systemctl status bluevein
sudo journalctl -u bluevein -f

# Autostart
sudo systemctl enable bluevein   # enable
sudo systemctl disable bluevein  # disable

# Service management
.\bluevein.exe start      # Start
.\bluevein.exe stop       # Stop
.\bluevein.exe install    # Install
.\bluevein.exe uninstall  # Uninstall

# Or via net
net start BlueVeinService
net stop BlueVeinService

# Check status
Get-Service BlueVeinService

graph TB
    subgraph Windows
        WinBT[Registry Bluetooth]
        WinMonitor[BlueVein Monitor]
    end
    
    subgraph Linux
        LinuxBT[BlueZ Bluetooth]
        LinuxMonitor[BlueVein Monitor]
    end
    
    subgraph EFI["EFI Partition"]
        Config[bluevein.json]
    end
    
    WinBT <-->|Track changes| WinMonitor
    LinuxBT <-->|Track changes| LinuxMonitor
    
    WinMonitor <-->|Read/Write keys| Config
    LinuxMonitor <-->|Read/Write keys| Config
    
    style Config fill:#89b4fa,stroke:#313244,stroke-width:2px,color:#1e1e2e
    style WinMonitor fill:#f38ba8,stroke:#313244,stroke-width:2px,color:#1e1e2e
    style LinuxMonitor fill:#a6e3a1,stroke:#313244,stroke-width:2px,color:#1e1e2e

sequenceDiagram
participant OS as Operating System
participant Monitor as BlueVein Monitor
participant EFI as EFI/bluevein.json

Note over OS,EFI: 1️⃣ System boot
Monitor->>EFI: Reads keys from EFI
Monitor->>OS: Reads local devices
Monitor->>OS: Updates device keys from EFI if they differ
Monitor->>EFI: Adds new devices from OS to EFI

Note over OS,EFI: 2️⃣ New device pairing
OS->>Monitor: Event: new device
Monitor->>EFI: Reads current bluevein.json
Monitor->>EFI: Adds/updates device key

Note over OS,EFI: 3️⃣ Periodic check (every 30 sec)
Monitor->>EFI: Checks for changes from other OS
Monitor->>OS: Applies new keys to existing devices

• On boot: BlueVein checks keys in EFI and updates them for devices present in the system. New devices from the system are added to EFI
• On new pairing: The key is immediately saved to EFI and becomes available to the other OS
• On removal: The device remains in EFI (it may be active on the other OS)
• Periodically: Checks for changes every 30 seconds and applies key updates from EFI

BlueVein fully supports Bluetooth Low Energy devices with all key types:

Dual-mode devices: BlueVein automatically merges Classic and LE keys for devices supporting both modes (e.g., many Bluetooth headphones).

CSRK SignCounter:

• Windows doesn't persist SignCounter in registry — it's kept in driver memory only
• BlueVein stores Counter in bluevein.json and takes MAX value during sync
• This prevents counter rollback and protects against replay attacks

CSRK SignCounter on Windows: Windows Bluetooth stack doesn't persist SignCounter in registry. BlueVein works around this by storing it in bluevein.json, but frequent OS switching may reduce accuracy.

Impact: Minimal. Modern LE devices (keyboards, mice, headphones, gamepads) use LTK for encrypted connections, not CSRK for data signing. Issue may only affect specific IoT devices using unencrypted connections with signing.

Solution: If device doesn't auto-connect after sync — re-pair once. Counter will reset and everything will work.

No. BlueVein only reads and writes pairing keys. It doesn't touch drivers or system files.

Any Bluetooth devices: headphones (AirPods, Sony, Bose), mice (Logitech MX Master), keyboards, gamepads (Xbox, PS5).

Tested on:

• AirPods Pro 2
• Sony WH-1000XM5
• Logitech MX Master 3
• Xbox Series X Controller

Yes. Pairing keys are stored in the EFI partition, which only root/admin can access. BlueVein runs with elevated privileges, but the code is open — you can verify it yourself.

BlueVein works independently of disk encryption. The EFI partition is typically not encrypted and accessible before OS boot.

Yes. BlueVein synchronizes keys between all OSes on one machine, regardless of how many there are.

BlueVein is fully automatic and works in real-time as a background service.

bt-dualboot, besides requiring manual commands after each pairing, has several other drawbacks identified by the community:

• Crashes on real devices. Doesn't support LE keyboards. Crashes on some configurations.
• Doesn't work with multiple Bluetooth adapters. If you have built-in + external adapter — you'll get an error.
• Requires mounting the Windows partition.
• Uses hacky methods to modify Windows system registry
• Abandoned since 2022 — issues remain unanswered

1. Collect logs:

   # Linux
   sudo journalctl -u bluevein -n 100 > bluevein_logs.txt
   
   # Windows
   C:/ProgramData/BlueVein/bluevein.log

2. Create an Issue with detailed description and logs

Open a Feature Request — we always welcome improvements!

Want to improve BlueVein? We'd love your contribution!

1. Fork the repository
2. Create a feature branch (git checkout -b feature/AmazingFeature)
3. Commit your changes (git commit -m 'Add some AmazingFeature')
4. Push to the branch (git push origin feature/AmazingFeature)
5. Open a Pull Request