Features

Device support

_{* via BlueZ Battery1 interface · RFCOMM features require an active connection}

Installation

Arch / Omarchy (recommended)

Install system dependencies first:

sudo pacman -S python-gobject python-dbus python-cairo gtk4 libadwaita

Then install from AUR:

yay -S something-x
# or: paru -S something-x

Or via pip:

pip install something-x

Other distros

sudo apt install python3-gi python3-dbus python3-cairo gir1.2-gtk-4.0 gir1.2-adw-1
pip install something-x

sudo dnf install python3-pip python3-gobject python3-dbus python3-cairo gtk4 libadwaita
pip install something-x

nix run github:SoaOaoS/something-x

Run from source

git clone https://github.com/SoaOaoS/something-x
cd something-x
pip install -e .
something-x

Usage

GUI

something-x

1. Splash — animated intro, main window appears after ~2 s
2. Home — lists all paired Bluetooth devices; Nothing / CMF devices get a NOTHING badge
3. Scan — tap SCAN FOR DEVICES to run a 30 s BlueZ discovery
4. Device page — tap a card to open controls:
   • Battery rings (L / R / Case) update in real time
   • ANC and EQ apply immediately over RFCOMM and are saved to your profile
   • Volume slider drives the A2DP sink via pactl
   • Firmware version and serial number appear after RFCOMM connects
5. Close — hides to background; run something-x again to reopen

CLI

Control your earbuds without opening the GUI:

# Battery levels
something-x --battery

# ANC mode
something-x --anc off
something-x --anc on
something-x --anc transparency

# EQ preset
something-x --eq balanced
something-x --eq bass
something-x --eq treble
something-x --eq voice

# Combine
something-x --anc on --eq bass

# Target a specific device by address
something-x --device AA:BB:CC:DD:EE:FF --battery

Development releases

The develop branch publishes pre-release builds to PyPI automatically as something-x-dev:

pip install something-x-dev
something-x-dev

Dev builds use version numbers like 1.3.0.dev42. Not for production use.

Releases & versioning

Pushing to main triggers automatic versioning, a GitHub Release, a PyPI publish, and an AUR update — all from Conventional Commits:

Architecture

nothing_app/
├── application.py   Adw.Application — lifecycle, CSS, CLI arg handling, background mode
├── window.py        AdwNavigationView — home ↔ device routing, RFCOMM auto-connect manager
├── bluetooth.py     BlueZ D-Bus manager — device discovery, connect/disconnect signals
├── protocol.py      Nothing Ear 0x55 RFCOMM protocol (reverse-engineered from APK)
├── profiles.py      Per-device ANC/EQ persistence (~/.config/something-x/profiles.json)
├── splash.py        Animated splash screen (Cairo, typewriter, ripple rings)
├── data/
│   └── style.css    Glass-morphism CSS theme
└── pages/
    ├── home.py      Device list + scan button
    └── device.py    ANC / EQ / volume / settings + Cairo earbud visual

Protocol

Frame format: [SOF=0x55][ctrl:2 LE][cmd:2 LE][len:2 LE][FSN:1][payload][CRC16:2 LE]

All outgoing frames use ctrl=0x0160 with CRC16-ARC. The device silently drops SET commands if any frame in the session was sent without CRC.

Enable raw frame logging:

SOMETHING_X_DEBUG=1 something-x

Contributing

The RFCOMM protocol in nothing_app/protocol.py is reverse-engineered from the official Android APK. If your device uses different command IDs, channels, or ANC values, patches are very welcome — please include the raw RFCOMM dump (SOMETHING_X_DEBUG=1) in your issue or PR.

License

MIT