English | 中文(简体) | 中文(繁體) | Русский | 日本語 | Українська | 한국어 | Česky | Türkçe | Ελληνικά | Português
_{Attention: readme files are maintained by translators and may become outdated from time to time. For newest info rely on English version.}

Galaxy Buds Client

An unofficial manager for the Buds, Buds+, Buds Live and Buds Pro

Key Features • Download • How it works • Contributing • Credits • License

Key Features

Configure and control any Samsung Galaxy Buds device and integrate them into your desktop.

Aside from standard features known from the official Android app, this project helps you to release the full potential of your earbuds and implements new functionality such as:

• Detailed battery statistics
• Diagnostics and factory self-tests
• Loads of hidden debugging information
• Customizable long-press touch actions
• Firmware flashing, downgrading (Buds+, Buds Pro)
• and much more...

If you're looking for older firmware binaries, have a look here: https://github.com/ThePBone/galaxy-buds-firmware-archive

Download

There are several Linux packages available:

• Flatpak (All Linux distros)
• AUR package (Arch Linux)

Get binaries for Windows in the release section. Please read the release notes before installation:

Flatpak

Universal binary packages for all Linux distributions. This is the recommended way of installing GalaxyBudsClient on Linux.

Available for download on FlatHub: https://flathub.org/apps/me.timschneeberger.GalaxyBudsClient

flatpak install me.timschneeberger.GalaxyBudsClient

Note: Flatpaks are sandboxed. This application can only access ~/.var/app/me.timschneeberger.GalaxyBudsClient/ by default.

AUR package

An AUR package for Arch Linux maintained by @joscdk is also available:

yay -S galaxybudsclient-bin

winget

The Windows package is also available to install with Windows Package Manager (winget)

winget install ThePBone.GalaxyBudsClient

How it works

In order to use Bluetooth wireless technology, a device must be able to interpret specific Bluetooth profiles that enable Bluetooth devices to communicate efficiently with each other.

The Galaxy Buds define two Bluetooth profiles: A2DP (Advanced Audio Distribution Profile) for audio streaming/controlling and SPP (Serial Port Profile) for transmitting binary streams. Manufacturers often use this profile (which relies on the RFCOMM protocol) to exchange configuration data, perform firmware updates, or send other commands to the Bluetooth device.

Even though the A2DP profile is standardized and documented, the format of the binary data exchanged by this RFCOMM protocol is usually proprietary.

To reverse-engineer this data format, I started by analyzing the structure of the binary stream sent by the earbuds. Later on, I also disassembled the official Galaxy Buds apps for Android to gain more insight into these devices' inner workings. You can find some (incomplete) notes I took down below. Check the source code to get more detailed information on the structure of the protocol.

Galaxy Buds (2019) Notes • Galaxy Buds Plus Notes

While taking a closer look at the Galaxy Buds Plus, I also noticed some unusual features, such as a firmware debug mode, an unused pairing mode, and a Bluetooth key dumper. I documented these findings here:

Galaxy Buds Plus: Unusual features

Currently, I'm looking into modifying and reverse-engineering the firmware for the Buds+. At time of writing I have created two tools to fetch and analyze official firmware binaries. Check them out here:

Firmware Downloader • Firmware Extractor

Stream head-tracking data in realtime from your Buds Pro using this script: ThePBone/BudsPro-Headtracking

Contributing

Feature requests, bug reports, and pull requests of any kind are always welcome.

If you want to report bugs or propose your ideas for this project, you are welcome to open a new issue with a suitable template. Visit our wiki for a detailed explanation.

If you are planning to help us translating this app, refer to the instructions on our wiki. No programming knowledge is required, you can test your custom translations without installing any development tools before submitting a pull request. You can find auto-generated progress reports for existing translations here.

If you want to contribute your own code, you can simply submit a plain pull request explaining you changes. For larger and complex contributions it would be nice if you could open an issue (or message me via Telegram @thepbone) before starting to work on it.

Credits

Contributors

• @nift4 - macOS support and bug fixes
• @ArthurWolfhound - Issue templates, wiki and translations
• @AndriesK - Buds Live bug fix
• @TheLastFrame - Buds Pro icons
• @githubcatw - Connection dialog base
• @GaryGadget9 - WinGet package
• @joscdk - AUR package

Translators

• @ArthurWolfhound - Russian and Ukrainian translation
• @PlasticBrain - Korean and Japanese translation
• @cozyplanes - Korean translation
• @erenbektas and @Eta06 - Turkish translation
• @kakkk, @KevinZonda, @ssenkrad, @pseudor and @YexuanXiao - Chinese translation
• @YiJhu - Chinese-Traditional translation
• @efrenbg1 and Andrew Gonza - Spanish translation
• @giovankabisano - Indonesian translation
• @lucasskluser - Portuguese translation
• @alb-p, @mario-donnarumma - Italian translation
• @Buashei - Polish translation
• @KatJillianne - Vietnamese translation
• @joskaja and @Joedmin - Czech translation
• @Benni0109, @TheLastFrame, @ThePBone - German translation
• @nikossyr - Greek translation
• @grigorem - Romanian translation
• @tretre91 - French translation
• @Sigarya - Hebrew translation
• @domroaft - Hungarian translation
• @lampi8426 - Dutch translation

License

This project is licensed under GPLv3. It is not affiliated with Samsung nor supervised by them in any way.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, 
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR 
THE USE OR OTHER DEALINGS IN THE SOFTWARE.