Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4.7f1
2020.2
Issue ID
1271550
Regression
No
[Android] Video freezes while playing when a video is loaded from StreamingAssets folder
Reproduction steps:
1. Download and open the attached project "1271550.zip"
2. Build and run for Android
3. Press the button to play a video
Expected result: Full video plays
Actual result: Video gets stuck after 0-2 seconds
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Reproduces on:
VLNQA00321, Xiaomi MI 9 (MI 9), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Huawei MediaPad SCM-AL09 (Reported by the customer)
Meizu 16T (Reported by the customer)
Does not reproduce on:
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00125, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Samsung Galaxy S10 (SM-G975F), Android 10.0, CPU: Exynos 9820 (ARMv8), GPU: Mali-G76
iPhone 6S (OS version 13.3.1)
-
agnelpb
May 03, 2021 18:20
I was able to fix this issue by re-encoding the video at a lower bit rate, not a higher bit rate. Curious if it is an anomaly or if it is a typo in the resolution note.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
The video hangs because the media extractor read fails. See the device logcat, when you have a message looking like
09-21 18:47:30.674 5135 5183 W NuMediaExtractor: read on track 0 failed with error -2147483646
This is an android message ( was fixed in Android 10), causing Unity to receive EOS for the video.
To go around it you will have to re-encode the video at a higher bit rate.