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':
Code:
MtkOmxVdecDebug: [0xe5ddb700] === BufQWDT=== ETB too slow: 180210us
And occasionally the following message:
Code:
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:
Code:
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?
I just tried facebook videos on chrome with dns and it's working normally.
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
xirosiman said:
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
Click to expand...
Click to collapse
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.
Related
12-20 06:25:09.129 2362 2362 E MonoPipe: Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional: /system/bin/mediaserver
12-20 06:25:09.129 2361 2361 E dalvikvm: ERROR: couldn't find native method
12-20 06:25:09.129 2361 2361 E dalvikvm: Requested: Landroid/content/res/AssetManager;.addOverlayPathLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/StringI
12-20 06:25:09.129 2361 2361 E dalvikvm: JNI posting fatal error: RegisterNatives failed for 'android/content/res/AssetManager'; aborting...
I have added this missing lines to framework.jar. But still getting errors...
EDIT: This has been resolved. Updating vendor blobs and device trees fixed the issue. Thank you for your time.
Greetings Developers,
I would really appreciate some help. By God's grace, in the development thread, I have put together several Marshmallow Roms, namely PAC Rom and AOKP MM, that have the same problem. The camera works to take pictures, but cannot record video. It "appears" to be recording in the built in camera app, but does not actually save the recording. If I use another app, such as OpenCamera, it stops the recording as soon as I try to start. I am relatively new to development, and any help would be greatly appreciated, as well as fully recognized and credited.
Below is the logcat errors/fails when using the CM camera app, and the OpenCamer app. I just really want to get this fixed for the people who are using the roms. I hate to sell them short because I've made some sort of error.
In my inexperienced opinion, this appears to be an audio problem. I have compared the mediarecorder.cpp and similar files between CM13 and my roms, and they are identical. I was wondering if it might be vendor blobs, so I borrowed them from Beanstalk (where the camera video recorder function works), but that did not work either.
I am pretty sure that it is not the app, because using any video recording app fails to actually record the video.
Code:
Here are the fails from the logcat. I am only focusing on the errors, stops, or fails.
Using the built in Camera app:
07-12 06:43:32.459 244 3766 I MediaCodecSource: encoder (audio) stopped
07-12 06:43:32.459 244 652 I MediaCodecSource: puller (audio) stopping
07-12 06:43:32.461 244 3847 E OMXNodeInstance: setConfig(1d:google.vorbis.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
07-12 06:43:32.461 244 3847 I ACodec : codec does not support config priority (err -2147483648)
07-12 06:43:32.462 244 3847 I MediaCodec: MediaCodec will operate in async mode
07-12 06:43:32.467 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.468 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.469 244 3775 D ALSAStreamOps: setParameters(): keyRouting with device 0x0
07-12 06:43:32.469 244 3775 E ALSAStreamOps: must not change mDevices to 0
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D ALSADevice: standby: handle 0xb216c1c0 h 0x0
07-12 06:43:32.472 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.473 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.500 3612 3612 E MediaRecorder: stop failed: -1007
07-12 06:43:32.502 3612 3612 E CAM_VideoModule: java.lang.RuntimeException: stop failed.
07-12 06:43:33.984 244 3647 W AMessage: failed to post message as target looper for handler 0 is gone.
Using the OpenCamera App for comparison:
07-12 06:50:28.951 244 4439 E ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
07-12 06:50:28.976 244 4436 E SoftAVCEnc: Error in extractGraphicBuffer
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.977 244 4434 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 6
07-12 06:50:28.977 244 4439 D ALSADevice: setHardwareParams: buffer_size 16384, period_size 4096, period_cnt 4
07-12 06:50:28.977 244 4431 E MediaCodecSource: Encoder (video) reported error : 0x80001001
07-12 06:50:29.124 4180 4180 E MediaRecorder: stop failed: -1007
So, the errors or fails that are the same are these:
ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
MediaRecorder: stop failed: -1007
These are both audio errors. It appears that the audio is creating an error, so the video will not save. Unless someone out there knows better (be sure to correct me, I'm still learning). So I will be looking at MediaRecorder and ACDB-LOADER and audio problems.
Once again, any assistance would be greatly appreciated! Thanks!
EDIT: This has been resolved. Updating vendor blobs and device trees fixed the issue. Thank you for your time.
Greetings Developers,
I would really appreciate some help. By God's grace, in the T-Mobile S4 development thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-aokp-mm-t3391994 , I have put together several Marshmallow Roms, namely PAC Rom and AOKP MM, that have the same problem. The camera works to take pictures, but cannot record video. It "appears" to be recording in the built in camera app, but does not actually save the recording. If I use another app, such as OpenCamera, it stops the recording as soon as I try to start. I am relatively new to development, and any help would be greatly appreciated, as well as fully recognized and credited.
Below is the logcat errors/fails when using the CM camera app, and the OpenCamer app. I just really want to get this fixed for the people who are using the roms. I hate to sell them short because I've made some sort of error.
In my inexperienced opinion, this appears to be an audio problem. I have compared the mediarecorder.cpp and similar files between CM13 and my roms, and they are identical. I was wondering if it might be vendor blobs, so I borrowed them from Beanstalk (where the camera video recorder function works), but that did not work either.
I am pretty sure that it is not the app, because using any video recording app fails to actually record the video.
Code:
Here are the fails from the logcat. I am only focusing on the errors, stops, or fails.
Using the built in Camera app:
07-12 06:43:32.459 244 3766 I MediaCodecSource: encoder (audio) stopped
07-12 06:43:32.459 244 652 I MediaCodecSource: puller (audio) stopping
07-12 06:43:32.461 244 3847 E OMXNodeInstance: setConfig(1d:google.vorbis.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
07-12 06:43:32.461 244 3847 I ACodec : codec does not support config priority (err -2147483648)
07-12 06:43:32.462 244 3847 I MediaCodec: MediaCodec will operate in async mode
07-12 06:43:32.467 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.468 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.469 244 3775 D ALSAStreamOps: setParameters(): keyRouting with device 0x0
07-12 06:43:32.469 244 3775 E ALSAStreamOps: must not change mDevices to 0
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D ALSADevice: standby: handle 0xb216c1c0 h 0x0
07-12 06:43:32.472 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.473 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.500 3612 3612 E MediaRecorder: stop failed: -1007
07-12 06:43:32.502 3612 3612 E CAM_VideoModule: java.lang.RuntimeException: stop failed.
07-12 06:43:33.984 244 3647 W AMessage: failed to post message as target looper for handler 0 is gone.
Using the OpenCamera App for comparison:
07-12 06:50:28.951 244 4439 E ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
07-12 06:50:28.976 244 4436 E SoftAVCEnc: Error in extractGraphicBuffer
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.977 244 4434 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 6
07-12 06:50:28.977 244 4439 D ALSADevice: setHardwareParams: buffer_size 16384, period_size 4096, period_cnt 4
07-12 06:50:28.977 244 4431 E MediaCodecSource: Encoder (video) reported error : 0x80001001
07-12 06:50:29.124 4180 4180 E MediaRecorder: stop failed: -1007
So, the errors or fails that are the same are these:
ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
MediaRecorder: stop failed: -1007
These are both audio errors. It appears that the audio is creating an error, so the video will not save. Unless someone out there knows better (be sure to correct me, I'm still learning). So I will be looking at MediaRecorder and ACDB-LOADER and audio problems.
Once again, any assistance would be greatly appreciated! Thanks!
Would you mind giving an explanation how this is done step by step?
lineageOS: cannot use internal SD after factory reset: "Failed to find root"
Hello all,
sorry for posting here, i'm not allowed to post at the peregrine forum section.
I have a Moto G 4G (LTE) peregrine which worked fine with the latest LineageOS 14.1. + twrp-3.1.1-0.
Then i made a factory reset because i wanted to gift it to my mother.
After that, no app could access the INTERNAL SD card for storing eg. pictures or downloads.
When you open the "Files" app, it crashes immediately.
Then logcat shows the output below.
I tried the following to no avail:
- reset with formating data, cache, etc (factory reset)
- reset with formating EVERYTHING, including /system, then reflashing lineage-14.1-20170811-nightly-peregrine-signed.zip and open_gapps-arm-7.1-nano-20170813.zip
- reset with formating EVERYTHING, including /system, then reflashing some other 7.1 ROM found here in the forum (cannot remember which)
- reset with formating EVERYTHING, including /system, then reflashing the original ROM XT1039_Retail_Germany_51_Untouched.zip
the original ROM was rather bad because the keyboard kept crashing and it was totally unusable. still no access to the internal SD card.
- messing with the directory structure:
/sdcard is a softlink to /storage/self/primary
/storage/self/primary is a softlink to /mnt/user/0/primary
/mnt/user/0/primary doesn't exist, it only goes as far as /mnt/user/0
so i tried different scripts from this thread https://forum.xda-developers.com/showthread.php?t=2211109 to create /mnt/user/0/primary at boot, which all didn't work.
it seems LOS 14.1 cannot run init scripts or user init scripts or whatever.
it didn't work.
also, the external SD card slot isn't reliable anymore, so that's out of the question as well.
I'm rather stuck!
can anybody help me?
any help is appreciated!
Thank you very much!
Code:
08-20 22:24:05.859 892 1873 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.documentsui/.LauncherActivity (has extras)} from uid 10028 on display 0
08-20 22:24:05.876 337 495 D audio_hw_primary: start_output_stream: enter: stream(0xb624e980)usecase(1: low-latency-playback) devices(0x2)
08-20 22:24:05.876 337 495 D audio_hw_primary: start_output_stream: enter: usecase(1: low-latency-playback) devices(0x2)
08-20 22:24:05.876 337 495 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
08-20 22:24:05.876 337 495 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
08-20 22:24:05.876 337 495 D hardware_info: hw_info_append_hw_type : device_name = speaker-lite
08-20 22:24:05.876 337 495 I msm8974_platform: platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(14)
08-20 22:24:05.876 337 495 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 14, path = 0
08-20 22:24:05.876 337 495 D ACDB-LOADER: ACDB -> send_adm_topology
08-20 22:24:05.876 337 495 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
08-20 22:24:05.876 337 495 D ACDB-LOADER: ACDB -> send_audtable
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> send_audvoltable
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
08-20 22:24:05.877 337 495 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
08-20 22:24:05.890 337 495 D audio_hw_primary: select_devices: done
08-20 22:24:05.948 892 929 W BroadcastQueue: Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } from com.cyanogenmod.trebuchet (pid=1909, uid=10028) requires com.google.android.launcher.permiss
ion.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.gms/.icing.proxy.ApplicationLauncherReceiver
08-20 22:24:05.963 892 1226 I ActivityManager: Start proc 4441:com.android.documentsui/u0a11 for activity com.android.documentsui/.LauncherActivity
08-20 22:24:05.965 892 929 W BroadcastQueue: Permission Denial: receiving Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$GmsExternalReceiver requires com.androi
d.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS due to sender com.cyanogenmod.trebuchet (uid 10028)
08-20 22:24:06.064 4441 4441 I art : Starting a blocking GC AddRemoveAppImageSpace
08-20 22:24:06.066 4441 4441 W System : ClassLoader referenced unknown path: /system/priv-app/DocumentsUI/lib/arm
08-20 22:24:06.214 892 911 I ActivityManager: Start proc 4472:com.android.externalstorage/u0a12 for content provider com.android.externalstorage/.ExternalStorageProvider
08-20 22:24:06.222 892 1074 I ActivityManager: START u0 {dat=//com.android.documentsui.launchControl flg=0x10280000 cmp=com.android.documentsui/.FilesActivity} from uid 10011 on display 0
08-20 22:24:06.279 4472 4472 I art : Starting a blocking GC AddRemoveAppImageSpace
08-20 22:24:06.280 4472 4472 W System : ClassLoader referenced unknown path: /system/priv-app/ExternalStorageProvider/lib/arm
08-20 22:24:06.331 4472 4472 D ExternalStorage: After updating volumes, found 0 active roots
08-20 22:24:06.358 892 911 I ActivityManager: Start proc 4490:com.android.mtp/u0a10 for content provider com.android.mtp/.MtpDocumentsProvider
08-20 22:24:06.432 4490 4490 I art : Starting a blocking GC AddRemoveAppImageSpace
08-20 22:24:06.514 892 1074 D VoldConnector: SND -> {9 appfuse mount 10010 4490 MtpDocumentsProvider}
08-20 22:24:06.528 892 979 D VoldConnector: RCV <- {200 9 AppFuse command succeeded}
08-20 22:24:06.633 4441 4441 W RestoreRootTask: Failed to find root: content://com.android.externalstorage.documents/root/home
08-20 22:24:06.679 4441 4511 I Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 10/09/15, 6cbbf7d, I3193f6e94a
08-20 22:24:06.685 4441 4511 I OpenGLRenderer: Initialized EGL, version 1.4
08-20 22:24:06.685 4441 4511 D OpenGLRenderer: Swap behavior 1
08-20 22:24:06.690 892 1074 I WindowManager: Failed to capture screenshot of Token{e3bfe3f ActivityRecord{a0dca5e u0 com.android.documentsui/.FilesActivity t14 f}} appWin=Window{7ef870e u0 com.android.documentsui/com.android.documentsui.FilesActivi
ty} drawState=1
08-20 22:24:06.766 892 1873 W InputMethodManagerService: Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
The solution was to format /data with ext4 instead of f2fs:
connect with adb while in TRWP, get the device name for /data, umount it, format with ext4, mount it again
Code:
df -h
umount /data
make_ext4fs /dev/block/mmcblk0p36
mount /data/
Then reboot
Hi all,
I'm experiencing video freezes on my OnePlus Nord 2, so I'm wondering whether this is an issue specific to my device or a generic issue with the Nord 2.
So, anyone with a Nord 2, can you please perform the following test and post the results here?
Open Google Chrome browser on the Nord 2
Navigate to https://www.nu.nl/289242/video/waarom-de-algemene-politieke-beschouwingen-belangrijk-zijn-voor-de-formatie.html (arbitrary video on popular Dutch news site)
Play commercials if necessary, then play actual video stream
While video stream is playing, use the settings icon to change video resolution from 1080p to 720p, or vice versa
Wait a couple of seconds to see whether the video freezes or continues playing
If the video continues playing, repeat steps 4 through 6
Please report whether the video plays correctly, or freezes shortly after changing the resolution. Also, whether the video freezes or not, if you have access to adb, please also report whether 'adb logcat *:W' shows a lot of warnings and errors while playing the video.
For more background information on this issue, please see https://forum.xda-developers.com/t/video-freezes-in-chrome-audio-captions-continue.4333457/.
Thanks for your help!
Same issue here on EEA variant. Got the phone for my daughter and she's not happy with freezing tiktok videos.
Stripped log before video freezes in tiktok:
Code:
09-22 17:16:02.951 1224 31061 W MtkOmxVdecDebug: [0xeb35eb00] === BufQWDT=== FTB too slow: 4460213us
09-22 17:16:02.962 30784 30859 W ttmn : <0x0,AVMDLManagerBridge.cpp,native_setIntValue,688>set key:709 value:0
09-22 17:16:02.962 30784 30859 W ttmn : <0x0,AVMDLog.cpp,set_alog_enable,38>set_alog_enable, 0
09-22 17:16:02.964 30784 30784 E Parcel : Reading a NULL string not supported here.
09-22 17:16:02.981 30784 31084 W ttmn : <0x0,av_decoder.cpp,resetCodec,727>codec need recreate: 0x7afc19ec80
09-22 17:16:03.002 1224 31062 W MtkOmxVdecExV4L2: [0xeb35eb00] FBD with wrong time order, 2666000 => -1
09-22 17:16:03.005 30784 31087 W AudioTrack: Use of stream types is deprecated for operations other than volume control
09-22 17:16:03.005 30784 31087 W AudioTrack: See the documentation of AudioTrack() for what to use instead with android.media.AudioAttributes to qualify your playback use case
09-22 17:16:03.008 30784 31083 W ttmn : <0x0,av_decoder.cpp,resetCodec,727>codec need recreate: 0x7b2f0b3300
09-22 17:16:03.048 31874 32181 E Parcel : Reading a NULL string not supported here.
09-22 17:16:03.049 31874 32181 E Parcel : Reading a NULL string not supported here.
09-22 17:16:03.050 1224 10915 E MtkV4L2Device: [0xeb35ed5c] [setDevicePollInterrupt] write sueeeed...
09-22 17:16:03.052 31874 32181 E Parcel : Reading a NULL string not supported here.
09-22 17:16:03.059 31874 32181 E Parcel : Reading a NULL string not supported here.
09-22 17:16:03.061 1224 10915 E libc : Access denied finding property "ro.mtk_crossmount_support"
09-22 17:16:03.061 1224 10915 E libc : Access denied finding property "ro.mtk_deinterlace_support"
09-22 17:16:03.063 31874 32181 E Parcel : Reading a NULL string not supported here.
09-22 17:16:03.072 30784 31083 W ttmn : <0x0,aj_media_codec.cpp,reconfigureCodec,644>width:0 height:0, nalSize: 0, maxWidth:0, maxHeight:4 surface : 14234, extradataSize: 166
09-22 17:16:03.096 1224 10915 E MtkOmxVdecExV4L2: [0xdd3c6e00] MtkOmxVdec::GetParameter unsupported nParamIndex
09-22 17:16:03.096 1224 10915 E OMXNodeInstance: getParameter(0xdd3c6e04:MTK.DECODER.HEVC, ??(0x6f600011)) ERROR: UnsupportedIndex(0x8000101a)
09-22 17:16:03.096 30784 31385 E OplusACodec: [GetVideoCodingTypeFromMime:L1093] mime:video/hevc
09-22 17:16:03.098 1224 10915 E MtkOmxVdecExV4L2: [0xdd3c6e00] MtkOmxVdec::SetConfig Unknown config index: 0x6F800002
09-22 17:16:03.098 1224 10915 E OMXNodeInstance: setConfig(0xdd3c6e04:MTK.DECODER.HEVC, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)
09-22 17:16:03.098 1224 10915 E MtkOmxVdecExV4L2: [0xdd3c6e00] MtkOmxVdec::GetConfig Unknown config index: 0x6F100004
09-22 17:16:03.098 1224 10915 E OMXNodeInstance: getConfig(0xdd3c6e04:MTK.DECODER.HEVC, ConfigAndroidVendorExtension(0x6f100004)) ERROR: UnsupportedIndex(0x8000101a)
09-22 17:16:03.099 1224 9352 E MtkV4L2Device: [0xdd3c705c] [getColorDesc] ioctl(3222820423) failed. error = Invalid argument
09-22 17:16:03.114 1180 4430 W ResourceManagerService: Ignoring request to add new resource entry with value <= 0
09-22 17:16:03.115 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.117 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.119 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.120 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.133 1224 31388 E MtkOmxVdecExV4L2: [0xdd3c6e00] MtkOmxVdec::handleResolutionChange
09-22 17:16:03.137 1224 10915 E MtkOmxVdecExV4L2: [0xdd3c6e00] Ignore SP AndroidNativeBufferConsumerUsage in mState:(3)
09-22 17:16:03.140 1224 10915 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.146 1224 10915 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.154 1224 10915 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.156 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.161 1224 10915 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.163 550 550 E SELinux : avc: denied { find } for interface=vendor.mediatek.hardware.mmagent::IMMAgent sid=u:r:mediacodec:s0 pid=1224 scontext=u:r:mediacodec:s0 tcontext=u:object_r:mtk_hal_mmagent_hwservice:s0 tclass=hwservice_manager permissive=0
09-22 17:16:03.163 1224 31395 E MDP : [PQ][DpAIPqControl] workerLoop: Failed to get service
09-22 17:16:03.164 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.167 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.168 30784 31086 W ttmn : <0x0,video_outlet_android.cpp,openDevice,327>open render success
09-22 17:16:03.171 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.173 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
09-22 17:16:03.177 1224 9352 W gralloc4: Buffer descriptor with invalid usage bits 0x2000
Can't reproduce with your video it plays fine in latest chrome with resolution changed multiple times.
But have 100% success to get freezing video here with:
In tiktok default feed videos plays fine. Scroll next videos all fine.
Swipe to userprofile and select video it freezes after first frame.
Scroll to next video it plays fine again
Works good, tiktok and the Video not freeze.. im on EEA V10
Update:
Upgraded the phone with sakarya1980's files (update_07_auf_09,09_10 Thanks for your work!) to V10.
Everything is uptodate.
Issue still exists and can be reproduced with tiktok method
https://imgur.com/a/vIDzKgt
Edit:
Fiddled around in Developer options and noticed "Don’t Keep Activities" was enabled (not sure why). Turning this option off and video playback is fine
Everything works fine here too , video link from first post plays just fine in chrome or firefox in my nord 2 .
Same for tiktok , no freezing even after very long sessions or other apps running in background
To all that replied so far, thanks for testing this. Do you have the 8/128GB version, or 12/256GB? And for those mentioning 'EEA' version, I assume this just means you purchased the device in Europe? Or do you see some indication of 'EEA' somewhere on the device itself?
A local OnePlus service center replaced both my mainboard and display last week to see whether the issue was caused by faulty hardware, but unfortunately the problem is still present. The service center flashed the device with A.07, but previously I had the same issue with A.10.
Here's a video showing the behavior: https://drive.google.com/file/d/107cshn5LQK3Yh-CMBQLvqa7Uyk1gyefH/view?usp=sharing
Here it's the 8/128GB version. Think there is some diff in software between IND/EEA, on the phone itself nothing says EEA. But there must be other diffs the phone here never showed v08 v09 ota updates. It was 05 to 07 and then 07 to 10 (wich failed to install thats why used sakarya1980 files).
Is it only in chrome on this webpage or other apps too? Have you tried switching to desktopversion in chrome?
In your capture the sound keeps playing here the whole video stopped (wich was fixed with disabling the devoption)
Nört said:
Here it's the 8/128GB version. Think there is some diff in software between IND/EEA, on the phone itself nothing says EEA. But there must be other diffs the phone here never showed v08 v09 ota updates. It was 05 to 07 and then 07 to 10 (wich failed to install thats why used sakarya1980 files).
Is it only in chrome on this webpage or other apps too? Have you tried switching to desktopversion in chrome?
In your capture the sound keeps playing here the whole video stopped (wich was fixed with disabling the devoption)
Click to expand...
Click to collapse
Same here, 8/128GB version, and I've only seen A.07 and A.10 versions. I've seen this problem in both Chrome and Brave browsers; Edge and DuckDuckGo browsers are not affected but video quality is much worse, I guess because these browsers are not using hardware video decoding.
If I disable hardware acceleration in Chrome (through chrome://flags), then videos are no longer freezing but video quality is much worse. I haven't tried many other apps, but for example YouTube doesn't seem to be affected (good video quality and no freezes when switching resolution).
Hi there
Have the exact same issue on a oneplus Nord 2 5g 12/256GB. Video freezing on Chrome and Brave browser. Firefox has no issues with that.
I am not that technical, but just fiddled around in flags on Brave (and suppose will work on chrome as well).
Setting Android SurfaceControl to disabled is a workaround that fixed this issue for me!
Hope it works for you too.
Daan_H said:
Have the exact same issue on a oneplus Nord 2 5g 12/256GB. Video freezing on Chrome and Brave browser.
Setting Android SurfaceControl to disabled is a workaround that fixed this issue for me!
Hope it works for you too.
Click to expand...
Click to collapse
Many thanks for this tip! Changing this setting in Chrome seems to fix the issue for me as well, I'll do some more testing soon.