[Android] Switching video source for video stream is not stable
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 issue during a call with videoStream.switchSource(desiredCamera), using the Nokia 2.4/Android 11 details and the supplied Archive.zip logs. Compare the TextureView getHardwareLayer messages when switching succeeds or leaves the previous frame frozen; done means the camera switches reliably and the returned completion reflects the visible result.
Written by the indexing model from the issue text.
Description
Describe the bug
Switching video source for video stream is not always works.
After calling videoStream.switchSource(desiredCamera) completable feature is completed successfully, but video is not switched and picture is frozen with last frame from the previous camera.
This behaviour is not always reproducible. In most cases it works as expected.
To Reproduce
Steps to reproduce the behavior:
- Start a call
- Execute videoStream.switchSource(desiredCamera)
- Observe camera is not switched
Issues can be reproduced only in call and in about 25% calls to switchSource().
Smartphone (please complete the following information):
- Device: Nokia 2.4
- OS: Android 11
Logs
I have noticed that when I see this log:
2021-09-13 17:49:14.908 8688-8688/com.azure.android.communication.ui D/TextureView: getHardwareLayer, createNewSurface:false
2021-09-13 17:49:14.941 8688-8688/com.azure.android.communication.ui D/TextureView: getHardwareLayer, createNewSurface:false
issue is reproduced, but when I see this, everything works as expected:
2021-09-13 17:50:49.162 8688-8688/com.azure.android.communication.ui D/TextureView: getHardwareLayer, createNewSurface:false
2021-09-13 17:50:49.190 8688-8688/com.azure.android.communication.ui D/TextureView: getHardwareLayer, createNewSurface:true
call id a43ce379-4455-42ad-854a-ad40b91684d7
Archive.zip
- 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 · 2 comments ·
-
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