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

Fills and Dropped Frames Under Restricted Bandwidth (3 Mbps)

Open
  • Is something wrong?
#2,177 44 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
android, kotlin
Domain
audio-video-rtc, mobile-dev

Research direction

The issue names no source files, tests, or entry points to start from. First compare the reported v2.7.0 and v2.8.0 cases using the requested encoder configuration, bitrate/resolution settings, and logs across the listed devices and bandwidth conditions. Done means narrowing down the cause of the fills, dropped frames, and audio/video interruptions, or establishing a reliable recommended configuration.

Written by the indexing model from the issue text.

Description

Hello,
We recently updated RootEncoder from v2.7.0 to v2.8.0 and have been testing streaming across different Samsung device models.
Note : It is happening when adding filters.
Below are our observations:

  1. Without bandwidth restriction
    Streaming works fine on most devices.
    On Samsung S22, we are observing fills and dropped frames.
    When streaming continuously for more than one hour, the S22 device also gets heated.
    We are observing these issues even when the network connection is stable.
    On Samsung A17, & Samsung M56 we have not observed these issues.
  2. With bandwidth restricted to 3 Mbps
    With the bandwidth restricted to 3 Mbps, we are observing fills and dropped frames.
    We also noticed that audio and video are missed/interrupted at certain points during the stream. When checking the stream in MediaLive, we are seeing audio and video alerts.
    We also tested the same 3 Mbps restricted bandwidth scenario with RootEncoder v2.7.0, and we observed similar behavior, including the audio alerts.
    So, the audio/video issue under the 3 Mbps bandwidth restriction does not appear to be specific to v2.8.0.
  3. Devices tested
    Samsung S22 – Occur fills and dropped frames with and without restriction; device heating during long streaming
    Samsung S24 – Samsung A17 – Without restriction working fine.
    Samsung M56 – Occur fills and dropped frames with 3 Mbps bandwidth restriction
    Questions
    Could you please help us understand:
    Why are we seeing fills and dropped frames on some Samsung models, particularly the S22, even when the network is stable?
    With bandwidth restricted to 3 Mbps, why are we seeing fills/dropped frames and audio/video interruptions?
    Since we also see similar audio alerts with v2.7.0 under the same 3 Mbps restriction, could this be related to the encoder, bitrate, network handling, or device behavior rather than the v2.8.0 upgrade?
    Is there any recommended configuration or approach in RootEncoder to handle these scenarios more reliably?
    Please let us know if you need any additional logs, encoder configuration, bitrate/resolution settings, or other details from our side.
    Thank you.
Dominant language
Kotlin
Stars
3k
Forks
946
Avg merge
5d 1h
Merged PRs (30d)
6

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 pedroSG94/RootEncoder

All issues in pedroSG94/RootEncoder

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.