Omaphones for Omarchy

JBL  ·  Sony  ·  Samsung  ·  Nothing / CMF  ·  Soundcore  ·  Xiaomi  ·  OPPO  ·  Bose  ·  TOZO  ·  Huawei  ·  Redmi  ·  EarFun  ·  QCY

Battery levels and noise-cancellation control for Bluetooth headphones, in the Omarchy bar.

Install — copy into a terminal and run:

omarchy plugin add https://github.com/ncr/omarchy-headphones --enable

Update an installed copy:

omarchy plugin update io.github.ncr.omaphones --yes && omarchy restart shell

Headphones not on the list? Add yours.

What it does · Supported headphones · In the panel · Settings · Gallery · Add your headphones

Gallery

What it does

• Battery level — per earbud and the case, or the single battery of over-ear headphones.
• The bar icon is the meter — earbuds are drawn as a pair, a headset as headphones, filling up as they charge. Readable from the bar without opening anything.
• Noise control — Off / ANC / Ambient / TalkThru, from the panel or a key. JBL, Sony, Samsung, Nothing / CMF, Soundcore, Xiaomi Buds 5 Pro, Redmi Buds 5 and 3 Pro, OPPO Enco Air3 Pro, EarFun Air Pro 4, Bose QC45 and Bose QC35 today; built to learn your brand. Sony and Soundcore add the ambient level with Focus on Voice or wind noise reduction; Nothing / CMF the ANC strength (Low / Mid / High / Adaptive) and a low-latency switch, and the Bose QC35 grades its ANC Low or High.
• Pause when you take them off, resume when you put them back on — on a headset with a wear sensor (confirmed on the Sony WH-1000XM6). Only the players the sensor paused are resumed. Any headphones pause what is playing when they disconnect.
• Several headphones at once — one icon per connected set, each with its own panel.
• Low-battery notification that names the earbud.
• Scriptable — omarchy-shell omaphones status, omarchy-shell omaphones setMode anc, and so on.

For AirPods use omapods instead: the same idea, built for Apple’s own protocol, and the plugin this one is modelled on.

Supported headphones

CMF Headphone Pro’s connection, reconnect recovery and all panel controls were confirmed on hardware by its owner. See the test record and remaining limits.

Add your own headphones

Use /add-new-bridge in Codex or Claude, or ask your agent to read the shared skill. It first checks whether an existing bridge suffices, then guides capture, tests and owner validation.

Paste the text below into your AI coding agent (Claude Code, Codex, OpenCode…). It adds support for your headphones and opens a pull request here. How the existing protocols were found is written down in PROTOCOL.md.

Add support for my Bluetooth headphones to the Omaphones plugin for Omarchy and
open a pull request against `github.com/ncr/omarchy-headphones` with the result.
0. If it is not installed yet: `omarchy plugin add
   https://github.com/ncr/omarchy-headphones --enable --yes` (`--yes` because you
   have no terminal to confirm in). It lands in
   `~/.config/omarchy/plugins/io.github.ncr.omaphones`.
1. Connect the headphones and check `omarchy-shell omaphones status`. Find out
   what they serve: `bluetoothctl devices` for the address, `bluetoothctl info
   ` for the UUIDs — `df21fe2c-2515-4fdb-8886-f12c4d67927c` is the
   Google Fast Pair Message Stream (battery), `956c7b26-d49a-4ba8-b03f-b17d393cb6e2`
   is Sony MDR v2 and `96cc203e-5068-46ad-b32d-e316f5e069ba` Sony MDR v1 (both
   noise control), `2e73a4ad-332d-41fc-90e2-16bef06523f2` is Samsung SPPNew,
   `aeac4a03-dff5-498f-843a-34487cf133eb` is Nothing NT Link, a UUID
   starting `0cf12d31-fac3-4553-bd80-d6832e7` is Soundcore's vendor channel;
   JBL earbuds are probed over BLE by the plugin itself.
2. If battery and the mode row both already work, no bridge change is needed.
   Still bring my device's own capture, pin and confirmed capabilities from
   step 3, plus its README row and the screenshot from step 4.
3. Follow `.agents/skills/add-new-bridge/SKILL.md` in the repository.
   Read `AGENTS.md` in the plugin directory
   first: it is the map — which files a new model or a new brand touches,
   the bridge contract (`BRIDGE.md`), how a session is pinned
   (`tests/pins/`), and `tools/check`, the one command that runs everything
   a pull request is held to. Run `tools/check` until it passes; CI runs the
   same script on the pull request.

   The canonical examples are JBL TUNE230NC TWS and Sony WH-CH720N,
   prepared and hardware-tested by the maintainer @ncr on his own headphones.
   Read `docs/CANONICAL-TESTS.md`, their `*-canonical.json` pins, captured
   packets and shared fault/battery tests. Match their coverage for the
   capabilities my model actually offers: all mode replies, battery shape,
   malformed/partial data, unsolicited changes, silence vs disconnect,
   recovery and isolation from another device. Use my device's own frames;
   canonical means a coverage example, not permission to reuse their bytes.
   Record a live test with device-reported results and restored settings;
   clearly list anything untested or not applicable. Preserve all existing pins.
   These expanded requirements apply to new models and brands. Existing
   supported models keep their current coverage; do not require historical
   gaps to be filled. Changes to an existing model need tests for the changed
   behaviour and its owner's confirmation, while preserving its existing pins.

   Two rules hold whatever brand this is, because nobody has more than their
   own headphones — the maintainer cannot test mine and I cannot test
   anybody else's — and a pull request that breaks either will be sent back:

   **A new model may not change what an existing one is sent.** Somebody
   else's headphones work today on frames nobody here can retest. A model
   gets its own row (`MODELS` in its bridge) and its own pin file
   (`tests/pins//.json`, the frozen session of its owner's
   headphones); adding mine adds a row and a file, it does not edit another
   owner's. Where something must be decided, let it widen rather than
   narrow: prefer asking one more question to asking one fewer.

   **Ship only what you saw the headphones answer — no guessed bytes.** A
   variant from a vendor table that my headset never answered stays out, in
   the code and in `PROTOCOL.md` both. Keep the probe's output as
   `docs/captures/-.txt` and name it from the pin.

   Mind that any file written inside the plugin directory reloads the plugin
   at once — edit elsewhere and move files in, as the tools in `tools/` do.
4. Take the screenshot: `tools/gallery-shot ` — the `gallery-screenshot`
   skill in `.claude/skills/` has the steps — and add it to the Gallery at the
   bottom of `README.md` with the device name and my handle. The screenshot is
   part of the pull request.
5. Commit, push to a fork, and open the pull request.

Negative results are welcome too — a row saying what does not work saves the next person the afternoon.

In the panel

The icon is the meter:

Keys, while the panel is open (the panel lists them itself, bottom rows):

Click an icon to open its panel; with two sets connected, click the one you mean.

Everything is reachable over IPC — omarchy-shell omaphones :

With more than one set connected, every method that reads or writes a device has a …For twin that names a device by a piece of its name, address or brand: modeFor sony, setModeFor anc jbl, openFor jbl.

The table is the useful subset — Service.qml answers a few more introspection calls (bleAddress, panelRect) for the tools in tools/.

What it deliberately does not do — connect, volume, MAC addresses, equalisers — lives in the stock panels a keypress away (b, v).

Settings

omarchy bar set io.github.ncr.omaphones (add --json for numbers and booleans), or the widget’s entry in ~/.config/omarchy/shell.json.

Credits

• omapods — the idea and the shape.
• Bluetooth-Battery-Meter — the clearest reading of the Fast Pair battery bytes.
• bluetooth-py — the JBL command numbers.
• Gadgetbridge and mos9527/SonyHeadphonesClient — the Sony frame format; the two disagree about the WH-CH720N, and the hardware settled it here.
• @f-iacono — WH-1000XM6 protocol capture and wear-sensor support.
• r-witz/omarchy-nothing-ear — the Nothing protocol as a working Omarchy widget: battery components, the latency switch and the case cache; DaanHessen/earctl — the command table; @Jenesaispas69’s PR #2 — the NT Link UUID and the frame layout from an Ear (a).
• Leaf-lsgtky/OppoPods — the HeyMelody ANC query (0x010C) and the 01 01 window this headset answers; Swastik36/OPPO-Earbuds — the OPOv1 framing and the battery query.

Licence

MIT. See LICENSE.