Bose · microphone

Bose SoundLink Flex (2nd Gen) microphone sounds bad or is not detected

Bose SoundLink Flex (2nd Gen) microphone sounds bad or is not detected: selected input, app permission, boom position, Bluetooth call profile and hardware should be separated. Scoped to 887612.

Bose's Flex (2nd Gen) guidance on calls is about profiles rather than a microphone menu: Bluetooth speakers in this line support the Hands-Free Profile (HFP) but not the Headset Profile (HSP), and many calling apps, including Skype, WhatsApp and Facebook Messenger, use HSP, so calls made in apps without HFP support will not be heard or controlled through the speaker. If your voice is not picked up, use the phone's regular call function or another app, and check Bluetooth connection and volume first.

Differential

Likely causes of “Bose SoundLink Flex (2nd Gen) microphone sounds bad or is not detected”, and how to tell them apart

  1. 1

    A call app using the Headset Profile

    What separates it The call rings on the phone but you and the caller cannot use the speaker

    How to confirm Try the phone's regular call function or a different calling app

  2. 2

    The speaker is not the active audio route

    What separates it Call audio keeps coming from the phone earpiece instead of the speaker

    How to confirm Select the Bose speaker as the audio output in the call screen

  3. 3

    Weak Bluetooth link

    What separates it Your voice breaks up or drops out completely during calls that started fine

    How to confirm Move within about 33 feet of the phone and remove interference

  4. 4

    A stale pairing

    What separates it Calls worked through the speaker before but now fail to route to it

    How to confirm Clear the speaker's paired-device memory, then pair the phone again from scratch

Before you touch a setting

Record this first — changing settings destroys the evidence

  • Which app you use for calls
  • Whether music plays through the speaker fine
  • How far the phone is from the speaker

Try in this order

0 of 5 completed
  1. Use a supported call path

    Reversible

    Make the call with the phone's standard dialer first. If that works, the speaker is fine and the calling app is the limitation.

  2. Choose the audio route

    Reversible

    During the call select the Bose speaker as the output from the phone's audio menu.

  3. Check the connection

    Reversible

    The Bluetooth light should be solid white when connected. Stay within about 33 feet of the phone with nothing thick between them.

  4. Clear the memory

    Reversible

    Hold the Bluetooth button 15 seconds, forget the speaker on the phone, and pair again.

  5. Reset

    Reversible

    Hold Power for 15 seconds with the cable removed, reboot, and test a normal call.

Model-specific

What is true of this model and not of its siblings

Call audio
Bluetooth speakers of this line support the Hands-Free Profile but not the Headset Profile, and apps like Skype, WhatsApp and Messenger may use the latter, so their call audio can fail to play or be controlled.

Stop boundary

When this stops being a self-service repair

  • !If calls never route to the speaker after a factory reset and a new pairing, request service
  • !If callers cannot hear you on any phone or app after a reset, contact Bose about the hardware

Evidence ledger

Sources behind this answer

01
Bose Support Understanding LED indicator status lights (SoundLink Flex 2nd Gen)

Power, Bluetooth and Shortcut light patterns including failed battery.

02
Bose Support Resetting your product (SoundLink Flex 2nd Gen)

The 15-second Power reset and the Volume + and - factory reset.

03
Bose Support Charging the battery (SoundLink Flex 2nd Gen)

Four-hour charge, 12-hour playback, overnight charging.

04
Bose Support Battery will not fully charge (SoundLink Flex 2nd Gen)

Temperature, charger amp rating and incompatible chargers.

05
Bose Support Power LED indicator flashing white and amber (SoundLink Flex 2nd Gen)

Wait 30 to 60 minutes at room temperature.

06
Bose Support Checking the remaining battery charge (SoundLink Flex 2nd Gen)

Voice prompt and Power button hold.

07
Bose Support Product will not turn on (SoundLink Flex 2nd Gen)

Wet charging, quick press to power off, tone when powered.

08
Bose Support Cannot connect a Bluetooth device (SoundLink Flex 2nd Gen)

Pairing steps and the 15-second memory clear.

09
Bose Support No audio from product (SoundLink Flex 2nd Gen)

Volume, range, Windows LE listing, HFP versus HSP.

010
Bose Support Poor sound quality from product (SoundLink Flex 2nd Gen)

One active driver and two passive radiators, EQ and interference.

011
Bose Support Short battery life (SoundLink Flex 2nd Gen)

Volume, 30-minute auto-off, power off when idle.

012
Bose Support Using the Shortcut Button (SoundLink Flex 2nd Gen)

Linking, phone assistant and Spotify shortcut.

013
Bose Support Software and firmware versions (SoundLink Flex 2nd Gen)

Firmware 8.2.16 to 4.3.24 and the SE release notes.

014
Bose Support Incorrect Voice Prompts (SoundLink Flex 2nd Gen)

The 2026 voice prompt update.

015
Bose Support Difficulty using the Speaker Link Feature

Bose's Speaker Link checklist that lists the Flex 2nd Gen as compatible.

Exact questions

Common questions

Does the speaker support hands-free calls?+

Bose says it supports the Hands-Free Profile.

Which profile do many apps use?+

The Headset Profile, which it does not support.

Which apps have this issue?+

Skype, WhatsApp and Messenger among others.

Will a firmware update change it?+

An update will not add the unsupported Headset Profile, but it fixes bugs.

Is the phone's dialer supported?+

Yes, the standard phone dialer uses the Hands-Free Profile the speaker supports.

Why is call audio on the phone?+

The route was not switched to the speaker.

Can I tell in advance whether an app will work for calls?+

There is no published list of which apps support the Hands-Free Profile, so the fastest test is trying the phone's own dialer first — if that routes to the speaker fine, the speaker itself is confirmed working and the specific app is the limitation, not the hardware.

Wrong device or version?

Match the path before repeating the steps.

Match another device