Releases: Oppzippy/OpenSCQ30
Releases · Oppzippy/OpenSCQ30
v1.17.0
v1.16.1
v1.16.0
v1.15.0
General
Fixes
- Add missing soundcore mac address ranges for device detection
- Prioritize filtering by GATT service id rather than mac address, since new mac address ranges are showing up. This isn't possible (or implemented yet) on every client, however.
- Various Space A40 issues that prevented it from working at all
CLI
Features
- Add support for all existing sound modes
v1.14.1
v1.14.0
General
Features
- Add support for Space A40 (A3936)
- Add support for Vortex (A3031)
Fixes
- Fix Liberty 2 Pro (A3930) packet parse error
GUI
Fixes
- Quick presets resetting to default values
- Sound mode options unsupported by the device visible in quick presets
Android
Fixes
- Rename General menu to Sound Modes
v1.13.1
v1.13.0
General
Build
- Replace
cargo-make
withjust
GUI
Features
- Add custom equalizer profile importing/exporting
Fixes
- Fix some circumstances where the volume adjustments matching a custom profile would be selected, but the dropdown would not show the profile as selected
- Custom equalizer profile sorting is now case insensitive
- Icon colors now adapt when using dark theme
- Write config file to temp file first before overwriting to work around potential data loss if writing is interrupted
- The config file is no longer overwritten with the exact same content during every application startup
Android
Features
- Add custom equalizer profile importing/exporting
- Show the title of the current screen rather than the device's name in the header bar
- New color scheme generated from logo color
Fixes
- To resolve inconsistent transition animations, use slides everywhere
- Custom equalizer profile duplicate detection issues
Web
Features
- Add custom equalizer profile importing/exporting
- There is now a dropdown menu to select light/dark mode in addition to the default option of following the system preference
Fixes
- Accesibility issues
v1.12.0
CLI
Features
- Add shell completions:
openscq30_cli completions
Android
Features
- Add option to auto connect to paired devices
In order to implement this, the companion device API is now used, which means connected devices will no longer be listed by default. They must first be paired with the app. This was necessary to gain permission to start foreground services from the background, which is necessary for auto connect to work.