Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[bug]Echo Issue on Specific Android 14 Devices Using LiveKit

Open
#678 17 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #742 by @cloudwebrtc — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter

Research direction

Start by reviewing merged pull request #742, then compare the reported LiveKit call path with direct WebRTC calls using the stated client-sdk-flutter 2.2.6 and flutter-webrtc 0.11.7 versions. Reproduce on the reported Android 14 devices if available; done means LiveKit calls no longer cause the other party to hear echo, including in subsequent direct WebRTC calls.

Written by the indexing model from the issue text.

Description

Hello, thank you for your excellent open-source project!

I encountered an issue while using it: on certain devices, an echo occurs during communication. The problematic devices identified so far are OnePlus 11 and Redmi Note 13, both running Android 14.

The specific issue is as follows:

When the problematic devices communicate with other phones using LiveKit for voice calls, the other party hears an echo from the problematic devices. However, the problematic devices themselves sound normal (this occurs regardless of whether it’s audio-only or video, or whether speaker mode is enabled).
Our app also supports WebRTC direct calls (bypassing LiveKit). We use the WebRTC client library included in the LiveKit SDK. In this scenario, communication is normal on these devices.
An even stranger issue arises: if the problematic devices first use WebRTC direct calling (scenario 2), everything works fine. However, once they use LiveKit for communication, subsequent WebRTC direct calls also produce echoes. Killing the process on the problematic devices restores normal behavior for WebRTC direct calls, but killing the process on the other side does not resolve the issue.

The software versions in use are:
client-sdk-flutter: 2.2.6
flutter-webrtc (the WebRTC client library included with the LiveKit SDK): 0.11.7

I currently have no clue how to resolve this issue. Could you please help investigate? Thank you!

Dominant language
Dart
Stars
421
Forks
260
Avg merge
3d 9h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from livekit/client-sdk-flutter

All issues in livekit/client-sdk-flutter

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.