AllBugsFeaturesChangelogBountiesSearchNew post
Sign in with Fluxer
Bugs

Bluetooth Audio Bug: Earphone Mic / Audio sync failure in Voice Calls

(#4039) Bug Open: Needs triage
by sertylix

Reproduction steps

There is a critical audio routing conflict when joining a Fluxer voice channel using Samsung Galaxy Buds3 (or possibly others earphone) on the latest Android (and maybe iOS) beta builds. When joining a voice channel, the app requests microphone permissions (the Android privacy green dot appears), but no audio is transmitted to other participants. It seems the LiveKit framework fails to properly initialize the bidirectional Bluetooth HFP/SCO profile, causing either total microphone silence. The earbuds work flawlessly on other native VoIP apps like Discord, confirming this is a framework-specific routing issue between LiveKit/Flutter and recent Samsung Bluetooth firmwares.

Steps to Reproduce

  1. Connect Galaxy Buds3 to the Android device.
  2. Open Fluxer (v2026.10.100-beta.6) with "Nearby Devices" permission disabled or enabled.
  3. Join any voice channel.
  4. Observe that you can hear others on the Earphone, and your colleagues cannot hear you despite the app showing ongoing call (the green voice indicator is not triggering)
Note : With the same Earphone when connected to Desktop application , it is working as expected

Expected behaviour

Be able to hear audio in the Galaxy Buds 3 and also be able to send audio with it. The app should seamlessly switch to the Bluetooth HFP/SCO profile, allowing simultaneous high-quality voice input and output through the connected Galaxy Buds3.

Actual behaviour

the microphone in Galaxy Buds 3 is not working (green voice indicator is not there)

Working Workaround / Fix Found

I managed to find a specific sequence that forces Android to reset the audio focus and bypass the framework bug:
  1. Launch Fluxer with the "Nearby devices" permission turned OFF in Android app settings.
  2. While inside the app, go to Android Settings and toggle the "Nearby devices" permission ON, then immediately OFF again.
  3. This action forcefully disconnects the Buds from the current call session (triggering the earbud's hang-up chime).
  4. Reconnect immediately to the Fluxer voice channel.
  5. Fluxer will display a prompt saying "This will terminate your other call". Confirm it.
  6. The audio session successfully resets, and both audio input (mic) and output (sound) now work perfectly together.

Build information

Environment

  • Device: Samsung Galaxy (or specify your phone model)
  • OS: Android 15 / One UI 6.1.1 (or specify your OS version)
  • App Version: v2026.10.100-beta.6
  • Audio Device: Samsung Galaxy Buds3

Platform

Android, iOS

Comments

Sign in with Fluxer to comment and vote.

No comments yet.