Description of the bug:
We are observing multiple issues while using Gemini 3.1 Flash Live Preview in a voice-based application.
Environment
- Model: Gemini 3.1 Flash Live Preview
- Audio input/output enabled
- Automatic Activity Detection (VAD) enabled
Configuration:
setup: {
model: `models/${GEMINI_LIVE_MODEL}`,
generationConfig,
systemInstruction: {
parts: [{ text: effectivePromptText }],
},
realtimeInputConfig: {
automaticActivityDetection: {
disabled: false,
silenceDurationMs,
prefixPaddingMs,
},
turnCoverage: 'TURN_INCLUDES_ONLY_ACTIVITY',
},
inputAudioTranscription: {},
outputAudioTranscription: {},
sessionResumption,
tools: [TOPIC_TRANSITION_TOOL, END_CALL_TOOL],
}
silenceDurationMs = 6000;
Issues Observed
1. STT Accuracy Issues
Example:
User speech:
I will identify the odd one out
Transcription:
The transcription drops multiple words and changes the meaning of the utterance.
2. silenceDurationMs Not Being Honored
We configured:
silenceDurationMs = 6000;
However, the model appears to end the user turn after approximately 2000ms of silence, which seems to match the default behavior.
We verified this by:
- Measuring actual silence duration before turn completion
- Checking conversation logs
- Confirming that logs show the configured value of 6000ms
Despite this, the turn closes after roughly 2000ms of silence.
3. VAD Cuts Off Users Mid-Sentence
The VAD occasionally detects end-of-turn while the user is still speaking.
This results in:
- Partial utterances being processed
- Responses generated before the user finishes speaking
- Interrupted conversational flow
4. Inconsistent Tool Calling
Tool invocation appears unreliable.
Even when:
- Tool descriptions are explicit
- Usage instructions are clear
- User intent matches the tool description
The model sometimes invokes the tool and sometimes ignores it for similar requests.
Actual vs expected behavior:
STT
Expected
I will identify the odd one out
Actual
silenceDurationMs
Expected
- User turn should end after approximately 6000ms of silence.
Actual
- User turn ends after approximately 2000ms of silence.
VAD
Expected
- User should be able to complete a sentence without interruption.
- Brief pauses within a sentence should not trigger turn completion.
Actual
- User speech is occasionally cut off mid-sentence.
Tool Calling
Expected
- Consistent tool invocation when user intent clearly matches tool descriptions.
Actual
- Tool calls are inconsistent and appear hit-or-miss.
Any other information you'd like to share?
We have reproduced these behaviors consistently across multiple conversations.
The silence duration issue was specifically validated through timing measurements and conversation logs. The logs indicate that the configured value is received, but the runtime behavior appears to follow the default timeout instead.
Please let us know if these are known limitations/issues of Gemini 3.1 Flash Live Preview or if there are recommended workarounds.
Description of the bug:
We are observing multiple issues while using Gemini 3.1 Flash Live Preview in a voice-based application.
Environment
Configuration:
Issues Observed
1. STT Accuracy Issues
Example:
User speech:
Transcription:
The transcription drops multiple words and changes the meaning of the utterance.
2. silenceDurationMs Not Being Honored
We configured:
However, the model appears to end the user turn after approximately 2000ms of silence, which seems to match the default behavior.
We verified this by:
Despite this, the turn closes after roughly 2000ms of silence.
3. VAD Cuts Off Users Mid-Sentence
The VAD occasionally detects end-of-turn while the user is still speaking.
This results in:
4. Inconsistent Tool Calling
Tool invocation appears unreliable.
Even when:
The model sometimes invokes the tool and sometimes ignores it for similar requests.
Actual vs expected behavior:
STT
Expected
Actual
silenceDurationMs
Expected
Actual
VAD
Expected
Actual
Tool Calling
Expected
Actual
Any other information you'd like to share?
We have reproduced these behaviors consistently across multiple conversations.
The silence duration issue was specifically validated through timing measurements and conversation logs. The logs indicate that the configured value is received, but the runtime behavior appears to follow the default timeout instead.
Please let us know if these are known limitations/issues of Gemini 3.1 Flash Live Preview or if there are recommended workarounds.