On Linux Mint 22.3 Cinnamon Framework 13 with jack 3.5mm being plugged to BOSE SoundLink Mini II I correctly get a new *Device*, but there is no physical sound output, what is this issue?
Aug 24, 6:01pm

The issue you're describing—where your Bose SoundLink Mini II is detected as a device in Linux Mint 22.3 (Cinnamon, Framework 13) but produces no sound—is likely related to one of the following common causes:


1. Incorrect Output Device Selection

  • Check: Ensure the Bose SoundLink Mini II is selected as the default output device.
  • How to fix:
    • Open Sound Settings (via the system tray or Menu > Preferences > Sound).
    • Under the Output tab, select the Bose SoundLink Mini II (or its corresponding profile, e.g., "A2DP Sink" for high-quality audio).
    • Test sound output using the built-in tester.

2. Bluetooth Profile Issue

The Bose SoundLink Mini II supports both A2DP (high-quality audio) and HSP/HFP (for calls, lower quality). If the device is connected but no sound plays, it might be using the wrong profile.

  • Check: Run the following command in the terminal to see the active profile:

    bash
    pactl list cards | grep -A 20 "bose"

    Look for Profiles: and Active Profile:.

  • How to fix:

    • Switch to A2DP for music:

      bash
      pactl set-card-profile <card_name> a2dp_sink

      Replace <card_name> with the card identifier (e.g., bluez_card.XX_XX_XX_XX_XX_XX).

    • If the issue persists, restart the Bluetooth service:

      bash
      sudo systemctl restart bluetooth

3. Volume or Mute Settings

  • Check:

    • Ensure the Bose SoundLink Mini II is not muted or at minimum volume.
    • Check the system volume mixer (pavucontrol or alsamixer in the terminal).
    • Some Bluetooth devices have independent volume controls.
  • How to fix:

    • Open PulseAudio Volume Control (pavucontrol):
      bash
      sudo apt install pavucontrol
      pavucontrol
    • Under the Playback tab, ensure the application is sending audio to the correct device.
    • Under the Output Devices tab, check the volume slider for the Bose device.

4. Driver or Kernel Compatibility

  • Check: Linux Mint 22.3 uses PipeWire by default for audio. If you're using PulseAudio, ensure compatibility.

  • How to fix:

    • Restart PipeWire/PulseAudio:
      bash
      systemctl --user restart pipewire pipewire-pulse
    • If using PulseAudio:
      bash
      pulseaudio -k && pulseaudio --start
  • Kernel: Ensure your kernel is up-to-date:

    bash
    sudo apt update && sudo apt upgrade

5. Bluetooth Stack Issues

  • Check: Some users report issues with BlueZ (Bluetooth stack) and specific devices.
  • How to fix:
    • Reset the Bluetooth connection:
      • Remove the device:
        bash
        bluetoothctl remove <device_mac>
      • Re-pair the device:
        bash
        bluetoothctl scan on
        bluetoothctl pair <device_mac>
        bluetoothctl connect <device_mac>
        bluetoothctl trust <device_mac>

6. Hardware or Cable Issues

  • Check:
    • Test the 3.5mm jack with another device (e.g., phone or laptop) to rule out cable/port issues.
    • Try connecting the Bose SoundLink Mini II via Bluetooth to another device to confirm it works.

7. Debugging Steps

  1. Check logs for Bluetooth/audio errors:

    bash
    journalctl -u bluetooth -f

    or

    bash
    dmesg | grep -i audio
  2. Test with aplay: Play a test sound file directly to the device:

    bash
    aplay -D plughw:<card_number> /usr/share/sounds/alsa/Front_Center.wav

    Replace <card_number> with the correct card (find it via aplay -l).

  3. Check alsamixer: Run alsamixer in the terminal and ensure the 3.5mm output is not muted (look for MM; press M to unmute).


8. Known Issues with Bose SoundLink Mini II

  • Some users report that the Bose SoundLink Mini II requires A2DP to work properly on Linux. If the device defaults to HSP/HFP, sound may not play.
  • Workaround: Force A2DP by editing /etc/bluetooth/main.conf:
    ini
    [General]
    AudioSinkPriority = a2dp
    Then restart Bluetooth:
    bash
    sudo systemctl restart bluetooth

Next Steps

  1. Confirm the active profile (A2DP vs. HSP/HFP).
  2. Check volume/mute settings in pavucontrol and on the device.
  3. Test with another app (e.g., vlc or mpv) to rule out application-specific issues.

If the issue persists, let me know the output of:

bash
pactl list sinks | grep -A 10 "bose"

and

bash
aplay -l

I can help diagnose further!

Aug 24, 6:01pm

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more