[Android] API 21 to API 25, video frames are not loaded until user perform button click (UI refresh)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android
- Domain
- audio-video-rtc, mobile
Research direction
Start by reproducing the call flow with com.azure.android:azure-communication-calling:1.2.0-beta.2 on API 21–25, then compare initial video-renderer behavior with API 26–31. Done means remote video frames render when the renderer view is first attached, without requiring a button click or UI refresh.
Written by the indexing model from the issue text.
Description
Describe the bug
From API 26 to API 31 on call join if remote participant has video on then Android renders video properly. However, for devices with API 21 to 25, the video frames are not loaded on when video renderer view is loaded first time.
Video: video attached at https://skype.visualstudio.com/SPOOL/_workitems/edit/2542990
To Reproduce
Steps to reproduce the behavior:
- Launch device or emulator with API 21 to 30
- Start call with one remote participant with video on
- Join call from each device individually (end call on first device before joining from second)
- Issue: API 21 to 25 does not load video when video render view is attached to UI (same code is used for all devices)
Desktop (please complete the following information):**
com.azure.android:azure-communication-calling:1.2.0-beta.2
Smartphone (please complete the following information):
- Device: API from 21 to 31
- Dominant language
- No language data
- Stars
- 340
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/Communication
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#600 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#599 · 4 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#598 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/Communication#543 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#447 ·
All issues in Azure/Communication
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
QwenLM/Qwen-MM-Plugins#70 ·
-
area: tools priority: p3 status: needs review type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
use-agent-os/agent-os#3162 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
home-assistant/core#182762 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100