AllBugsFeaturesChangelogBountiesSearchNew post
Sign in with Fluxer
Bugs

Voice activity border does not always render when transmitting

(#4526) Bug Open: Confirmed Priority: P1
by Wrycu

Reproduction steps

  1. Set up your voice profile so background noise is not cancelled (the focused version works quite well)
  2. Breath or otherwise make quiet background noise
  3. Have someone else in the call hear the background noise
  4. Note that the green "you are transmitting" border does not always indicate

Expected behaviour

The green "you are transmitting" border is ALWAYS active ANYTIME you are transmitting

Actual behaviour

The green transmitting border appears to show up only above a certain noise threshold

Build information

Canary Desktop 2026.1031.143117, Web 2026.1031.143117, Linux 7.2.9-ogc3.1.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US

Platform

macOS, Windows, Linux

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #4625 Voice activity ring is not sensitive enough for low or short volumes

fltx

Report details

Reproduction steps

  1. Connect to a Voice Call and set your Fluxer or Mic Noise Gate low enough such that keyboard clicks, or mice clicks are being picked up.
  2. Connect on another device (or relay to a friend) to listen to see if they hear a click.
  3. They will hear a click, despite the ring indicator not engaging.

Expected behaviour

The ring should be lit up, even for small duration or low volume if the audio is actually being sent to other clients. There is a mismatch between what is heard and what is visually indicated as heard/broadcast.

Actual behaviour

The ring fails to light up, which can even occur in situations where users have very low mic volume in general. Whole conversations can be heard, despite the voice ring indicator not lighting up at all. This report is an extension of the Feature Request: https://feedback.fluxer.com/p/1069/c/9459 The two problematic code sections appear to be: audio analyser (https://github.com/fluxerapp/fluxer/blob/2d8d130be1839c61e31dae32975dfd522aa46b99/fluxer_app/src/features/voice/engine/VoiceSpeakingDetection.ts#L14-L29), thresholds and timing (https://github.com/fluxerapp/fluxer/blob/2d8d130be1839c61e31dae32975dfd522aa46b99/fluxer_app/src/features/voice/engine/VoiceSpeakingThreshold.ts#L3-L13).

Build information

Canary Desktop 2026.1101.102914, Web 2026.1101.175704, macOS 27.0.1 (arm64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US

Platform

macOS, Windows, Linux, Web

1 comment

Sign in with Fluxer to comment and vote.
Comment by Fullest
FullestReviewer 1 vote
Status changed from Needs triage to Confirmed
CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-GB
Permalink