01 / LISTENERS
Find what works with your earbuds.
Check the record for your model, then get the watch app from GitHub.
Check compatibility INDEPENDENT WEARABLE AUDIOWEAR OS × TWS
WearEarsSound, on your wrist.
Check earbud battery and switch listening modes from a Wear OS watch. One place for everyday controls across brands.
01 / PROJECT
Everyday controls within reach.
WearEars brings familiar earbud controls into one watch interface. The model and its driver determine which controls are available.
Find your model- Implemented
Battery awareness
See left, right, case or aggregate battery as reported by the earbuds.
- By model
Acoustic control
Switch between noise cancellation, off and transparency on supported models.
- Public records
Cross-brand compatibility
Find device capabilities, hardware records and protocol candidates by model.
- Implemented
Extensible drivers
Add drivers through a shared interface and reuse the controls on the watch.
02 / SYSTEM DESIGN
One interface. Independent drivers.
Four layers give each step a clear role, from a tap on the watch to a state report from the earbuds.
Read the developer guideInteractionWatch app & tiles
The watch app and tiles expose controls. The connection controller coordinates queries, requested modes and device reports.
View source (opens in a new tab)Unified contractTwsClient
TwsClient defines the interface for connection, battery queries and mode changes. Drivers declare available operations through capability flags.
View source (opens in a new tab)Driver selectionDriverRegistry
The registry selects a candidate driver from device information and keeps brand protocols separate from the interface.
View source (opens in a new tab)CommunicationRFCOMM / GATT
Drivers parse device frames and perform implemented protocol operations. The standard path reads aggregate battery when the system provides it.
View source (opens in a new tab)
03 / EXPLORE
Find your starting point.
02 / DEVELOPERS
From protocol to driver.
Read the contract, matching rules and evidence workflow to contribute a driver.
Developer resources03 / PARTNERS
Validate more devices together.
Explore joint validation and driver adaptation around specific models, firmware and capabilities.
Explore collaboration