Video Freezes but Audio Continues on Chrome

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

• #1

I mostly experience this issue while using Chrome to view videos embedded in my timeline on Facebook; I think I've also seen it happening on some other sites like nu.nl, but so far have been unable to reproduce this while viewing videos on YouTube mobile website for example, or in other apps (but maybe I just haven't tried enough on other sites or apps).

Usually the video freezes after it has been playing for a couple of seconds, while audio (and captions if enabled) continue. Pausing and restarting the video doesn't help, but video will continue again if I open the recent apps list and then go back to the browser; see https://drive.google.com/file/d/1IFHuMUdqj9xItYy9FSI5lhx4d-AxHYyB/view?usp=sharing for a video that illustrates this. Once the video has resumed using this procedure, it usually plays fine until the end, but the next video may exhibit the same issue all over again.

I've contacted OnePlus about this, but without any decent troubleshooting they advised me to send in my device to get it repaired. Not sure whether that's their standard response if something is not behaving as expected, or maybe this is a common hardware issue with these devices. If it really is a hardware issue, then I'm wondering why I don't experience this issue with other apps for example. Maybe it's related to AVC codec used by Facebook, whereas YouTube for example seems to use VP9 according to 'adb logcat'.

Obviously I would like to be a bit more certain that this is really a hardware issue before sending in my device, so wondering whether anyone else experienced similar issues while playing videos in Chrome, and whether they were able to resolve this.

So far, I've tried the following to no avail: rebooting the device, clearing data for Chrome, disable private DNS (to make sure ad blocking doesn't interfere with Facebook videos).

I did try to get some more information through ADB, not sure whether this is worth anything.

While playing any video in Chrome (on any site, and whether it freezes or not), I see a lot of the following messages in 'adb logcat':

                                MtkOmxVdecDebug: [0xe5ddb700] === BufQWDT=== ETB too slow: 180210us                              

And occasionally the following message:

                                Choreographer: Frame time is 0.061281  now = 127377097084976  timestampNanos = 127377097146257 ms in the future!  Check that graphics HAL is generating vsync timestamps using the correct timebase.                              

Following is an excerpt from the log when the video actually freezes:

                                09-14 09:42:26.872  1195 16327 W MtkOmxVdecDebug: [0xe5d03840] === BufQWDT=== ETB too slow: 214247us 09-14 09:42:27.074  1195 16327 W MtkOmxVdecDebug: [0xe5d03840] === BufQWDT=== ETB too slow: 189233us 09-14 09:42:27.211  1195 16327 W MtkOmxVdecDebug: [0xe5d03840] === BufQWDT=== ETB too slow: 125086us 09-14 09:42:27.321  1195 16328 E MtkV4L2Device: [0xe5d03a9c] [dequeueFrameBuffer] ioctl failed. error = Broken pipe 09-14 09:42:27.325  1195 16328 E MtkV4L2Device: [0xe5d03a9c] [dequeueFrameBuffer] ioctl failed. error = Broken pipe 09-14 09:42:27.555  1195 16287 W MtkOmxVdecDebug: [0xe248b280] === BufQWDT=== FTB too slow: 17538686us 09-14 09:42:27.581  5581 12112 W cr_MediaCodecBridge: Releasing: OMX.MTK.VIDEO.DECODER.AVC 09-14 09:42:27.583  1195  1195 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.583  1195 28762 E OMXNodeInstance: setParameter(0xe248b284:MTK.DECODER.AVC, ??(0x7f00002b)) ERROR: IncorrectStateOperation(0x80001018) 09-14 09:42:27.583  5581 16285 W ACodec  : Failed to set ANW_HWComposer to OMX, ignoring (-2147483648) 09-14 09:42:27.584  1195 16298 W MtkOmxVdecDebug: [0xe79c9840] === BufQWDT=== FTB too slow: 17491481us 09-14 09:42:27.584  1195 13921 E MtkOmxVdecExV4L2: [0xe248b280] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3) 09-14 09:42:27.588  5581 12112 W cr_MediaCodecBridge: Codec released 09-14 09:42:27.597  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.597  1195 16309 W MtkOmxVdecDebug: [0xe24acdc0] === BufQWDT=== FTB too slow: 17470601us 09-14 09:42:27.611  1195 16288 W MtkOmxVdecExV4L2: [0xe248b280] FBD with wrong time order, 701000 => -1 09-14 09:42:27.615  5581 12112 W cr_MediaCodecBridge: Releasing: OMX.MTK.VIDEO.DECODER.AVC 09-14 09:42:27.617  1195 28762 E OMXNodeInstance: setParameter(0xe79c9844:MTK.DECODER.AVC, ??(0x7f00002b)) ERROR: IncorrectStateOperation(0x80001018) 09-14 09:42:27.617  5581 16295 W ACodec  : Failed to set ANW_HWComposer to OMX, ignoring (-2147483648) 09-14 09:42:27.617  1195  1195 E MtkOmxVdecExV4L2: [0xe79c9840] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3) 09-14 09:42:27.620  5581 12112 W cr_MediaCodecBridge: Codec released 09-14 09:42:27.621  5581 12112 W cr_MediaCodecBridge: Releasing: OMX.MTK.VIDEO.DECODER.AVC 09-14 09:42:27.623  1195  1195 E OMXNodeInstance: setParameter(0xe24acdc4:MTK.DECODER.AVC, ??(0x7f00002b)) ERROR: IncorrectStateOperation(0x80001018) 09-14 09:42:27.623  5581 16306 W ACodec  : Failed to set ANW_HWComposer to OMX, ignoring (-2147483648) 09-14 09:42:27.627  1195 13922 E MtkV4L2Device: [0xe248b4dc] [setDevicePollInterrupt] write sueeeed... 09-14 09:42:27.628  1195 28762 E MtkOmxVdecExV4L2: [0xe24acdc0] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3) 09-14 09:42:27.629  1195 16299 W MtkOmxVdecExV4L2: [0xe79c9840] FBD with wrong time order, 917584 => -1 09-14 09:42:27.630  5581 12112 W cr_MediaCodecBridge: Codec released 09-14 09:42:27.637  1195 16310 W MtkOmxVdecExV4L2: [0xe24acdc0] FBD with wrong time order, 767434 => -1 09-14 09:42:27.640  1195 28762 E MtkV4L2Device: [0xe79c9a9c] [setDevicePollInterrupt] write sueeeed... 09-14 09:42:27.656  1195 13922 E MtkV4L2Device: [0xe24ad01c] [setDevicePollInterrupt] write sueeeed... 09-14 09:42:27.672  5581 12112 W cr_MediaCodecBridge: Releasing: OMX.MTK.VIDEO.DECODER.AVC 09-14 09:42:27.673  1195 31709 E OMXNodeInstance: setParameter(0xe5d03844:MTK.DECODER.AVC, ??(0x7f00002b)) ERROR: IncorrectStateOperation(0x80001018) 09-14 09:42:27.673  5581 16325 W ACodec  : Failed to set ANW_HWComposer to OMX, ignoring (-2147483648) 09-14 09:42:27.674  1195 31709 E MtkOmxVdecExV4L2: [0xe5d03840] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3) 09-14 09:42:27.676  5581 12112 W cr_MediaCodecBridge: Codec released 09-14 09:42:27.685  1195 31709 E libc    : Access denied finding property "ro.mtk_crossmount_support" 09-14 09:42:27.685  1195 31709 E libc    : Access denied finding property "ro.mtk_deinterlace_support" 09-14 09:42:27.688  1195 13922 E MtkV4L2Device: [0xe5d03a9c] [setDevicePollInterrupt] write sueeeed... 09-14 09:42:27.704  1195 13922 E OMXNodeInstance: setParameter(0xe79c9284:MTK.DECODER.AVC, OMX.google.android.index.allocateNativeHandle(0x7f20040e): Output:1 en=0) ERROR: BadParameter(0x80001005) 09-14 09:42:27.704  1195 13922 E MtkOmxVdecExV4L2: [0xe79c9280] MtkOmxVdec::GetParameter unsupported nParamIndex 09-14 09:42:27.704  1195 13922 E OMXNodeInstance: getParameter(0xe79c9284:MTK.DECODER.AVC, ??(0x6f600011)) ERROR: UnsupportedIndex(0x8000101a) 09-14 09:42:27.704  5581 16345 E OplusACodec: [GetVideoCodingTypeFromMime:L1093] mime:video/avc 09-14 09:42:27.705  5581 16345 E ACodec  : failed to set min buffer size to 2764800 (is still 2097152) 09-14 09:42:27.705  1195 31709 E MtkOmxVdecExV4L2: [0xe79c9280] MtkOmxVdec::GetConfig Unknown config index: 0x6F100004 09-14 09:42:27.705  1195 31709 E OMXNodeInstance: getConfig(0xe79c9284:MTK.DECODER.AVC, ConfigAndroidVendorExtension(0x6f100004)) ERROR: UnsupportedIndex(0x8000101a) 09-14 09:42:27.706  1195 31709 E MtkV4L2Device: [0xe79c94dc] [getColorDesc] ioctl(3222820423) failed. error = Invalid argument 09-14 09:42:27.715  1161  3586 W ResourceManagerService: Ignoring request to add new resource entry with value <= 0 09-14 09:42:27.719  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.722  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.724  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.725  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.748  1195 16348 E MtkOmxVdecExV4L2: [0xe79c9280] MtkOmxVdec::handleResolutionChange 09-14 09:42:27.753  1195 13921 E MtkOmxVdecExV4L2: [0xe79c9280] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3) 09-14 09:42:27.757  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.763  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.764  1195 13922 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.765  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.769  1226  1280 E VPUD    : [Warning] u4ProcessedNALUSize: 0->35 09-14 09:42:27.787  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.825  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.828  5581  5616 E NdkImageReader: acquireImageLocked: Output buffer format: 0x10f, ImageReader configured format: 0x7f000001 09-14 09:42:27.828  5581  5616 E chromium: [ERROR:image_reader_gl_owner.cc(319)] method fails for some other reasons 09-14 09:42:27.828  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.855  1195 13923 W gralloc4: Buffer descriptor with invalid usage bits 0x2000 09-14 09:42:27.863  5581  5616 E NdkImageReader: acquireImageLocked: Output buffer format: 0x10f, ImageReader configured format: 0x7f000001 09-14 09:42:27.863  5581  5616 E chromium: [ERROR:image_reader_gl_owner.cc(319)] method fails for some other reasons 09-14 09:42:27.864  5581  5616 E NdkImageReader: acquireImageLocked: Output buffer format: 0x10f, ImageReader configured format: 0x7f000001 09-14 09:42:27.865  5581  5616 E chromium: [ERROR:image_reader_gl_owner.cc(319)] method fails for some other reasons 09-14 09:42:27.899  5581  5616 E NdkImageReader: acquireImageLocked: Output buffer format: 0x10f, ImageReader configured format: 0x7f000001 09-14 09:42:27.899  5581  5616 E chromium: [ERROR:image_reader_gl_owner.cc(319)] method fails for some other reasons 09-14 09:42:27.926  5581  5616 E NdkImageReader: acquireImageLocked: Output buffer format: 0x10f, ImageReader configured format: 0x7f000001 09-14 09:42:27.926  5581  5616 E chromium: [ERROR:image_reader_gl_owner.cc(319)] method fails for some other reasons                              

These last two messages ('acquireImageLocked' and 'method fails') then repeat many many times until I switch away from the browser, with only an occasional 'ETB too slow' message in-between.

Anyone any ideas?

Last edited: Sep 14, 2021

• #2

I just tried facebook videos on chrome with dns and it's working normally.

• #3

I thing its something with the chrome. Have you tried other browsers?
Also mine was freezing at 1080 videos with chome.
My old 3t was playing flawlessly

• #4

I thing its something with the chrome. Have you tried other browsers?
Also mine was freezing at 1080 videos with chome.
My old 3t was playing flawlessly

Glad to hear that I'm not the only one experiencing this, did you ever report this to OnePlus? Indeed I think this issue mostly occurs when playing high-resolution videos. Did you switch to a different browser due to this issue, and if so, which browser?

I tried with DuckDuckGo browser which doesn't seem to be affected by this issue, however it looks like DuckDuckGo browser plays the videos in lower resolution so maybe that's the reason why it doesn't exhibit this issue. Not sure whether it's possible to somehow force it to play videos in high resolution. Maybe I'll try some other browsers as well.

Edit: Just tried factory resetting the phone; after going through the initial setup screens, without modifying any other settings or installing any apps, I immediately tried playing Facebook videos in Chrome, and again the issue could be easily reproduced. So even on a clean phone the issue is present.

Edit 2: Just tried some other browsers:

• Both Chrome and Brave browser show the same issue with videos freezing.
• In both Edge and DuckDuckGo browsers, videos are not freezing but video quality is really bad/grainy

Edit 3: I went to a local OnePlus service center today; they flashed the device but unfortunately the problem is still present. They will be contacting OnePlus directly to check with them how this issue can be fixed.

Edit 4:
Just tried disabling video hardware decoding in Chrome (through chrome://flags), which seems to fix the issue of videos freezing, and significantly reduces the number of warnings and errors in 'adb logcat'. However this is not a permanent solution, as disabling hardware decoding results in severely reduced video quality (I guess the browsers that were not affected by this issue were simply not using hardware decoding, as videos in those browsers were showing reduced video quality as well).

Question is whether the hardware decoding issue is caused by defective hardware, or whether this is a general issue with Nord 2 devices, for example caused by the MediaTek chipset or bugs in OnePlus software / Hardware Abstraction Layer.

Edit 5:
I've just been able to reproduce this behavior with other websites like nos.nl, nu.nl and 538.nl. Apparently the issue is triggered by changing the video resolution. For example, on both nu.nl and 538.nl I can more or less consistently reproduce this issue by switching between the 1080p and 720p streams and vice versa. I guess my original issue with Facebook is due to Facebook automatically changing resolution based on connection bandwidth.

Edit 6: The local OnePlus service center replaced mainboard and display, unfortunately this doesn't resolve the issue.

Last edited: Sep 27, 2021

Similar threads

dyerwils1983.blogspot.com

Source: https://forum.xda-developers.com/t/video-freezes-in-chrome-audio-captions-continue.4333457/

Share this post