2025 – Present · Creator & Systems Developer · Desktop & IoT · Open-source system project
B4S — Desktop Companion for Baseus Headphones
Unofficial desktop companion for Baseus earbuds: Tauri v2, Rust (btleplug), SolidJS
What this system is for
B4S explores what a local desktop companion can look like when a headphone vendor's useful controls are hidden behind a mobile application and a proprietary Bluetooth protocol.
What I owned
Tauri desktop shell, Rust BLE lifecycle, GATT packet investigation, capability-aware UI, and privacy-first local operation.
Overview & Context
B4S explores what a local desktop companion can look like when a headphone vendor's useful controls are hidden behind a mobile application and a proprietary Bluetooth protocol.
Problem & Constraints
Headphone manufacturers often only release mobile apps for EQ and ANC adjustments, leaving desktop users unable to configure their devices without a phone and a vendor account.
System Architecture
Desktop GUI (SolidJS + SCSS) ──► Tauri v2 IPC Bridge
│
▼
Baseus Headphones (BLE) ◄─── GATT Frames ─── [ Rust Core (btleplug) ]- Tauri v2 IPC bridge connecting SolidJS frontend to native Rust backend
- Bluetooth LE GATT client over btleplug
- Two framings: bare AA/BA and a 789C frame with CRC-16
- JSON model catalog driving capability-based UI per profile
Engineering Deliverables
- Built a desktop application on Tauri v2 and Rust with the BLE lifecycle kept in native code.
- Implemented BLE scanning, the GATT connection lifecycle and a handshake via btleplug, with a session that refuses stale state.
- Worked out two Baseus wire framings (bare AA/BA and a 789C frame with CRC-16) and encoded them with documented, tested codecs.
- Built the interface with SolidJS, TypeScript and SCSS, rendering controls from each model profile's capabilities.
- Kept the app local-only: no account, no telemetry.
Engineering Signals & Outcomes
- 124 catalog profiles, 7 can send commands (1 verified)
- Direct Local Bluetooth LE (GATT) Protocol
- Tested on Windows only
Engineering Outcomes
- A local desktop control surface for supported headphone capabilities.
- A narrower boundary between native BLE behavior and the UI layer.
- A privacy-first application model without unnecessary accounts or telemetry.
Engineering threads behind the project
Each thread links to notes focused on one concrete decision or engineering problem.
Reverse engineering as product discovery
The UI can only be honest when the protocol model, device capabilities, failure states, and local privacy boundary are understood first.
Technologies & Tooling
Tauri v2 · Rust · SolidJS · Bluetooth LE · btleplug · TypeScript · SCSS