Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4.1f1
Issue ID
1170214
Regression
No
[Android ] Videoplayer with 1080p freezes when being transcoded with codec H264 and built on Android 9 devices
To reproduce:
1. Open attached project
2. Press on video and make sure that transcode is checked, dimensions set to Original 1920x1080, Codec H264 Bitrate Mode- High, Spatial Quality - High Spacial Quality
2. Build and run to Android 9 devices
Actual result: The video player freezes in the middle of the video
Expected result: Video plays smoothly till the end
Reproduced in: 2017.4.30f1; 2018.3.4f1; 2018.4.5f1; 2019.1.12f1 2019.2.0b10; 2019.3.0a10
Tested devices:
Repro:
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
No repro
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue GT7400 Plus
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00004, Meizu - (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
Note: logcat attached
Note: with other video settings can not reproduce the issue.
Note: if transcoded is unchecked no repro as well
Note: video setting image is attached below
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2020.1.X):
I believe this is an Android bug in the MediaExtractor library, which we depend on in our Unity video player to get the best video playback performance possible on Android. It is not just about the transcoding that we do in the Editor. It appears that this can happen with any high-quality, high-bitrate, 1920x1080, H.264 stream on Android 9.
I'm not sure exactly what triggers it, but it does appear to be fixed in Android 10. For apps that need to support the wide range of Android devices that are out there, reasonable work-arounds appear to be to transcode to a lower resolution (like 1280x720) to a lower bit-rate (like our medium bit-rate option) or to use a different codec (like VP8).