Device support tracking

[d7omdev]

Context

Soundcore Control (formerly Liberty Control) supports multiple Soundcore models through a generic device registry (src/devices.rs) instead of being hardcoded to one earbud. This issue tracks device support on an ongoing basis. Comment or open a new issue to request a model that isn't listed below.

Supported devices

Model	Status	Notes
Liberty 4 Pro	Fully supported	Continuous ambient slider, original supported device
R60i NC	Fully supported	Confirmed via testing; mode-only ambient picker (no manual intensity range)
P20i / P25i / R50i	Added, unverified	Bluetooth name guessed as soundcore P20i, needs confirming on real hardware
Life Q30	Added, unverified	Bluetooth name guessed as soundcore Life Q30, needs confirming on real hardware
Space One Pro	Added, unverified	Bluetooth name guessed as soundcore Space One Pro, needs confirming on real hardware

If you own an "unverified" model: try connecting, and if it's not found, run bluetoothctl info <MAC> (or check your Bluetooth settings) and post the exact Name: it reports here.

Needs support (not yet added)

Not on the list above? openscq30-lib (the Bluetooth library this app is built on) already supports many more Soundcore models. See its device table: https://github.com/Oppzippy/OpenSCQ30#supported-devices. Adding one to Soundcore Control just means registering it in src/devices.rs. Comment here with your model and, if known, the exact Bluetooth name it advertises.

Also open

• In-app illustrations only exist for Liberty 4 Pro and R60i NC so far. Other models fall back to a generic vector placeholder. Contributions welcome.

[luca7185]

Hey @d7omdev !

I have quickly tested both my Life Q30 and Space one Pro headsets and here is my feedback (Mind this is just a report, not criticism nor feature request):

Installation...

The presence of rustup and other dependencies should be checked by the installer script to make it a little more noob-friendly. Packaging it as a flatpack or appimage would go a long way to grab testers that do not understand much about compiling (I don't understand either).

After installed:

If the app is running, even in the background (automatic behavior, it seems), it prevents my headsets from connecting to the PC.

• Suggestion: A small welcome page explaining how it connects to the device with a paused service/daemon so the user would not break its mind figuring out why the device suddenly is not connecting)

Of course when connecting a headset, the main window should not show Left/Right/Case, probably only the connected / battery state.

After connecting, I can change modes, equalizer presets, but nothing more (which should be expected, right?) The "control" tab seems to be focused on earbuds and offer nothing.

I'll keep an eye here as the development progress. I like the Idea of having something similar-looking to the mobile app on my pc. let me know If can help in any other testing (I cannot code).

Good Luck!

Edit: I believe that clicking the "quit" option on the taskbar should completely stop the service, so the app does not opo-up againg when it detects a headphone (at least for now).

[d7omdev]

Hey @luca7185, thanks for testing this and writing it up, appreciate it. Also confirms the Life Q30 and Space One Pro actually pair and connect, which I hadn't verified yet.

Going through your points: I'll try putting together an AppImage or an easier install script, compiling from source is a real barrier if you're not a developer. The main window still showing Left/Right/Case for devices that don't have that layout is also a real issue, the UI still assumes the Liberty 4 Pro's battery layout in a few places. The Controls tab being earbud-focused with nothing for the Life Q30 or Space One Pro is expected for now, that tab is built around whatever settings the vendor library reports per model, and those two don't expose much past mode and EQ yet, but I want to double check nothing's being missed on my end. And you're right that quitting from the tray should fully stop the background service, right now it doesn't stop the watcher, so it can respawn when it sees the headset again. I'll fix that.

On the headset-blocked-from-reconnecting bug: this app talks to the device over BlueZ, so I want to rule out whether something else on your system is also trying to manage the Bluetooth connection (a second Bluetooth manager, a different backend, etc). Could you run these and paste the output?

bluetoothctl version
systemctl status bluetooth --no-pager
ps aux | grep -iE 'blueman|blueberry|bluetoothd'
wpctl status

That'll tell me whether it's plain BlueZ, or something like blueman or PipeWire's Bluetooth module is also grabbing the connection.

One thing that would genuinely help: could you send a few screenshots of the official Soundcore app for the Life Q30 and Space One Pro, whatever you've got, the home/battery view, mode switching, EQ. I don't own either device, so real screenshots beat me guessing at layouts.

Also, on the device art: I'm adding proper illustrations per device as I go, so if a device still shows the generic placeholder earbuds icon, that just means I haven't gotten to it yet, not that it's less supported.

Thanks again, this helps a lot.

[luca7185]

Hello again...

Here is the output you requested:

❯ bluetoothctl version
  systemctl status bluetooth --no-pager
  ps aux | grep -iE 'blueman|blueberry|bluetoothd'
  wpctl status
Version 5.87
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Fri 2026-08-14 09:41:51 -03; 1h 3min ago
 Invocation: 32d7779355ff40fb8ae124349e7d90c7
       Docs: man:bluetoothd(8)
   Main PID: 693 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18570)
     Memory: 4.5M (peak: 5.2M)
        CPU: 1.675s
     CGroup: /system.slice/bluetooth.service
             └─693 /usr/lib/bluetooth/bluetoothd

Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Aug 14 09:42:16 CachyOS bluetoothd[693]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Aug 14 09:52:08 CachyOS bluetoothd[693]: profiles/audio/a2dp.c:load_remote_sep() Unable to load LastUsed: rseid 1 not found
Aug 14 09:52:11 CachyOS bluetoothd[693]: /org/bluez/hci0/dev_7C_E9_13_00_7D_66/sep1/fd0: fd(39) ready
root         693  0.0  0.0  12400  7024 ?        SNs  09:41   0:01 /usr/lib/bluetooth/bluetoothd
luca       10604  0.0  0.0   7372  4524 pts/0    S<+  10:45   0:00 grep --color=auto -iE blueman|blueberry|bluetoothd
PipeWire 'pipewire-0' [1.6.8, luca@CachyOS, cookie:4062148230]
 └─ Clients:
        32. WirePlumber                         [1.6.8, luca@CachyOS, pid:1237]
        41. WirePlumber [export]                [1.6.8, luca@CachyOS, pid:1237]
        42. pipewire                            [1.6.8, luca@CachyOS, pid:1259]
       103. kwin_wayland                        [1.6.8, luca@CachyOS, pid:1369]
       110. pipewire                            [1.6.8, luca@CachyOS, pid:1588]
       111. libcanberra                         [1.6.8, luca@CachyOS, pid:1468]
       112.                                     [1.6.8, luca@CachyOS, pid:1468]
       113. libcanberra                         [1.6.8, luca@CachyOS, pid:1480]
       114.                                     [1.6.8, luca@CachyOS, pid:1480]
       119. xdg-desktop-portal                  [1.6.8, luca@CachyOS, pid:1804]
       127. Vivaldi input                       [1.6.8, luca@CachyOS, pid:4492]
       144. wpctl                               [1.6.8, luca@CachyOS, pid:10605]
       149.                                     [1.6.8, luca@CachyOS, pid:1503]
       153. WirePlumber                         [1.6.8, luca@CachyOS, pid:1237]
       177. Shortwave                           [1.6.8, luca@CachyOS, pid:2]

Audio
 ├─ Devices:
 │      45. GA107 High Definition Audio Controller [alsa]
 │      46. C2423H                              [alsa]
 │      47. 500 Series Chipset Family HD Audio  [alsa]
 │     134. Space One Pro                       [bluez5]
 │  
 ├─ Sinks:
 │      56. C2423H Speakers                     [vol: 0.50]
 │      89. 500 Series Chipset Family HD Audio HDMI / DisplayPort 2 Output [vol: 1.00]
 │      90. 500 Series Chipset Family HD Audio HDMI / DisplayPort 1 Output [vol: 1.00 MUTED]
 │      93. 500 Series Chipset Family HD Audio HDMI / DisplayPort 3 Output [vol: 1.00]
 │      94. 500 Series Chipset Family HD Audio Headphones [vol: 1.00]
 │  *  135. Space One Pro                       [vol: 0.30]
 │  
 ├─ Sources:
 │  *   57. C2423h Microphone                   [vol: 1.00]
 │      91. Laptop Microphone (line input)      [vol: 1.00]
 │      92. Laptop Microphone                   [vol: 1.00]
 │  
 ├─ Filters:
 │    - filter-chain-1259-9                                         
 │      43. mic-biglinux-capture                                         [Stream/Input/Audio]
 │      44. mic-biglinux                                                 [Audio/Source]
 │    - loopback-1237-18                                            
 │     151. bluez_capture_internal.7C:E9:13:00:7D:66                     [Stream/Input/Audio/Internal]
 │     152. bluez_input.7C:E9:13:00:7D:66                                [Audio/Source]
 │  
 └─ Streams:
       176. Shortwave                                                   
            167. output_FL       > Space One Pro:playback_FL    [active]
            178. output_FR       > Space One Pro:playback_FR    [active]

Video
 ├─ Devices:
 │      58. Integrated_Webcam_5M_IR             [v4l2]
 │      59. Integrated_Webcam_5M_IR             [v4l2]
 │      60. Integrated_Webcam_5M_IR             [v4l2]
 │      61. Integrated_Webcam_5M_IR             [v4l2]
 │      62. Integrated_Webcam_HD                [v4l2]
 │      63. Integrated_Webcam_HD                [v4l2]
 │      64. OBS Virtual Camera                  [v4l2]
 │  
 ├─ Sinks:
 │  
 ├─ Sources:
 │     104. Integrated_Webcam_5M_IR (V4L2)     
 │     106. Integrated_Webcam_5M_IR (V4L2)     
 │  *  108. Integrated_Webcam_HD (V4L2)        
 │  
 ├─ Filters:
 │  
 └─ Streams:

Settings
 └─ Default Configured Devices:
         0. Audio/Sink    bluez_output.7C_E9_13_00_7D_66.1
         1. Audio/Source  alsa_input.usb-Dell_C2423H_30713A10553-00.analog-stereo

And here are the screenshots from the mobile app:

The soundcore Space One Pro show way more options and a completely different layout than the Life Q30, but they are also two completely different beasts of Headphones.

I don't think you need to replicate the mobile app's layout 1:1, but the layout for headphones will probably need to be standardized.

I do not know if the mobile app contains all the images / layouts for all phones out-of-the-box or if they are downloaded dynamically. It is indeed huge (over 1gb on my phone). May exploring the apk to grab images or other relevant data be an option?

I will keep looking back here for updates and reporting back my experience every now and then. Feel free to ping me when needed.

Happy coding!

[d7omdev]

Hey @luca7185, thanks for running those and for the screenshots.

No blueman or blueberry running, just plain BlueZ and PipeWire's bluez5 module, which is normal on any Linux desktop with Bluetooth audio (it's what's letting Shortwave play through the Space One Pro right now). So this isn't a second Bluetooth stack fighting for the device. It's more likely something in how my app holds its own connection open in the background. That points back at my code, not your setup.

The screenshots help a lot too. The Space One Pro clearly has more going on than the Life Q30 (EQ curve editing, finer ANC controls), so you're right that one shared layout won't work. Over-ear headphones like the Space One Pro probably need their own screen, separate from the earbud layout the app uses now.

On pulling assets from the APK, I'd rather not. Those images and strings belong to Soundcore, not something I want to redistribute. I'll source device icons from elsewhere online instead.

I'll update this thread once the background-connection fix and the headphone layout are done.

[d7omdev]

Hey @luca7185, here's where things stand on everything you raised.

Fixed:

• AppImage is up, no Rust toolchain needed: https://github.com/d7omdev/soundcore-control/releases/latest
• Quit now actually stops the background watcher instead of just closing the window, so it won't quietly relaunch and reopen a Bluetooth connection later.
• The main window shows a single battery percentage for devices without a case (Life Q30, Space One Pro) instead of always showing Left/Right/Case.
• Controls tab now reflects what each device actually has instead of the earbud-only list: Space One Pro gets Wind Noise Suppression, Auto Power Off, LDAC, and single/double press actions; Life Q30 gets Auto Power Off. Sections with nothing to show (including the Ambient tab, for devices with no ANC at all) are hidden instead of rendering empty.
• Life Q30, Space One Pro, and P20i all have real device art now instead of the placeholder icon.

Still open:

• The reconnect issue itself isn't confirmed fixed. Your diagnostic output ruled out a second Bluetooth manager, so my current guess is the watcher not fully quitting was part of it. Worth retesting now that Quit is real.
• No dedicated over-ear headphone layout yet, the Space One Pro's screenshots showed it has meaningfully more going on than the Life Q30. Not started.

Whenever you get a chance, pulling the AppImage and running through the same things (background/reconnect behavior especially, and how the Controls/Ambient tabs look now) would help a lot.

[luca7185]

Hey @d7omdev.

I have tested the AppImage and can confirm that the intended changes and fixes did work as expected. No connection issues with or without the app running.

As for features, of course the more mature OpenSCQ30 is able to expose most if not all of the headphones features (i.e. transparency mode / level - ANR modes / levels and so on...), but I believe you are on the right track. The most basic controls are indeed working.

For now, a small report would be that the connection notification and context menu on the system tray still use the earpods layout for headphones. See bellow:

Keep it up!

[d7omdev]

Thanks for testing, glad the reconnect issue is actually gone now.

Good catch on the tray. Fixed in v0.3.1: the notification and tray tooltip/menu were still hardcoded to L/R/Case, so single-battery devices like yours showed two dashes next to the real number. They now show a plain "Battery X%" like the main window already does.

https://github.com/d7omdev/soundcore-control/releases/tag/v0.3.1

Dedicated over-ear headphone layout (matching the extra ANC/transparency levels and EQ curve editing your screenshots showed) is still on my list, just not started yet.