Hi,
Last few week I got an update for my Mi A3. But it show "Couldn't Update". I have tried restart for a few times, still failed. At first I thought is a common issue that happen before for Android 10 Global version. But until now, I google but didn't get similar issue.
Code:
06-09 10:22:14.223 1026 1026 I update_engine: [0609/102214.223549:INFO:delta_performer.cc(384)] Opening /dev/block/bootdevice/by-name/qupfw_a partition without O_DSYNC
06-09 10:22:14.224 1026 1026 I update_engine: [0609/102214.224616:INFO:delta_performer.cc(127)] Caching writes.
06-09 10:22:14.224 1026 1026 I update_engine: [0609/102214.224776:INFO:delta_performer.cc(396)] Applying 3 operations to partition "qupfw"
06-09 10:22:14.253 1026 1026 I update_engine: [0609/102214.253610:INFO:delta_performer.cc(384)] Opening /dev/block/bootdevice/by-name/rpm_a partition without O_DSYNC
06-09 10:22:14.254 1026 1026 I update_engine: [0609/102214.254519:INFO:delta_performer.cc(127)] Caching writes.
06-09 10:22:14.254 1026 1026 I update_engine: [0609/102214.254630:INFO:delta_performer.cc(396)] Applying 4 operations to partition "rpm"
06-09 10:22:14.274 1026 1026 I update_engine: [0609/102214.274571:INFO:delta_performer.cc(384)] Opening /dev/block/bootdevice/by-name/storsec_a partition without O_DSYNC
06-09 10:22:14.275 1026 1026 I update_engine: [0609/102214.275496:INFO:delta_performer.cc(127)] Caching writes.
06-09 10:22:14.275 1026 1026 I update_engine: [0609/102214.275606:INFO:delta_performer.cc(396)] Applying 3 operations to partition "storsec"
06-09 10:22:14.296 1026 1026 I update_engine: [0609/102214.296526:INFO:delta_performer.cc(384)] Opening /dev/block/bootdevice/by-name/system_a partition without O_DSYNC
06-09 10:22:14.297 1026 1026 I update_engine: [0609/102214.297435:INFO:delta_performer.cc(127)] Caching writes.
06-09 10:22:14.297 1026 1026 I update_engine: [0609/102214.297545:INFO:delta_performer.cc(396)] Applying 2663 operations to partition "system"
06-09 10:22:14.325 1026 1026 E update_engine: [0609/102214.325666:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
06-09 10:22:14.325 1026 1026 E update_engine: [0609/102214.325892:ERROR:delta_performer.cc(430)] Unable to open ECC source partition system on slot B, file /dev/block/bootdevice/by-name/system_b: Success (0)
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326004:ERROR:delta_performer.cc(1135)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326089:ERROR:delta_performer.cc(1140)] Expected: sha256|hex = 8FDC83A129E42CCF54930CDF2E0CADA4B9D18D9F28CCA93859745FBFF655620E
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326143:ERROR:delta_performer.cc(1143)] Calculated: sha256|hex = A4862B6548106E22C0A0FEC181ECE24EEF4665B4E9766EE1D815FC88DD2E251F
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326217:ERROR:delta_performer.cc(1154)] Operation source (offset:size) in blocks: 0:2,219:1,224:1,235:226,699:2,2908:49,2958:156,3321:2,3580:1,3584:1,3588:1,3945:1,3948:5,3954:11,3967:10,3978:18,3999:2,4003:3,4007:1,4009:6,4016:12,4034:1
06-09 10:22:14.326 1026 1026 W update_engine: [0609/102214.326291:WARNING:mount_history.cc(66)] Device was remounted R/W 2 times. Last remount happened on 2020-05-15 10:30:32.000 UTC.
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326354:ERROR:delta_performer.cc(1435)] source_fd != nullptr failed.
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326414:ERROR:delta_performer.cc(296)] Failed to perform BROTLI_BSDIFF operation 2373, which is the operation 0 in partition "system"
06-09 10:22:14.326 1026 1026 E update_engine: [0609/102214.326468:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-09 10:22:14.327 1026 1026 I update_engine: [0609/102214.327135:INFO:delta_performer.cc(313)] Discarding 3276 unused downloaded bytes
06-09 10:22:14.327 1026 1026 I update_engine: [0609/102214.327209:INFO:libcurl_http_fetcher.cc(548)] Requesting libcurl to terminate transfer.
06-09 10:22:14.332 1026 1026 I update_engine: [0609/102214.332250:INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-09 10:22:14.332 1026 1026 I update_engine: [0609/102214.332476:INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 206
06-09 10:22:14.332 1026 1026 I update_engine: [0609/102214.332553:INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-09 10:22:14.386 1026 1026 I update_engine: [0609/102214.386506:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
06-09 10:22:14.386 1026 1026 I update_engine: [0609/102214.386774:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-09 10:22:14.386 1026 1026 I update_engine: [0609/102214.386865:INFO:update_attempter_android.cc(454)] Processing Done.
06-09 10:22:14.387 1026 1026 I update_engine: [0609/102214.387793:INFO:update_attempter_android.cc(473)] Resetting update progress.
06-09 10:22:14.387 1026 1026 I update_engine: [0609/102214.387916:INFO:dynamic_partition_control_android.cc(151)] Destroying [] from device mapper
06-09 10:22:14.401 3279 9469 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x111, 0.000).
06-09 10:22:14.402 1026 1026 I update_engine: [0609/102214.402755:INFO:metrics_reporter_android.cc(29)] uploading 1 to histogram for metric ota_update_engine_attempt_number
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.402996:INFO:metrics_reporter_android.cc(29)] uploading 0 to histogram for metric ota_update_engine_attempt_payload_type
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403138:INFO:metrics_reporter_android.cc(29)] uploading 0 to histogram for metric ota_update_engine_attempt_fixed_duration_boottime_in_minutes
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403258:INFO:metrics_reporter_android.cc(29)] uploading 0 to histogram for metric ota_update_engine_attempt_duration_monotonic_in_minutes
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403364:INFO:metrics_reporter_android.cc(29)] uploading 44 to histogram for metric ota_update_engine_attempt_payload_size_mib
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403459:INFO:metrics_reporter_android.cc(29)] uploading 1 to histogram for metric ota_update_engine_attempt_result
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403576:INFO:metrics_reporter_android.cc(29)] uploading 20 to histogram for metric ota_update_engine_attempt_error_code
06-09 10:22:14.403 1026 1026 I update_engine: [0609/102214.403829:INFO:metrics_reporter_android.cc(29)] uploading 29 to histogram for metric ota_update_engine_attempt_fixed_current_bytes_downloaded_mib
From what I notice, these 2 lines show the reason of these issue. From what I remember, I loaded twrp recovery before. Is this cause the OTA failed to update?
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
Device was remounted R/W 2 times. Last remount happened on 2020-05-15 10:30:32.000 UTC.
Anyone has this issue? Or any suggestion to solve this issue.
How do I check what is the version of this update? It does not show in the system update. I have downloaded the OTA.zip.
Current version: Android 10 for EU.
Build number: V11.0.1.0.QFQEUXM
Thanks
You already found the reason why it fails (https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291). Reflash stock boot and system images via fastboot.
_mysiak_ said:
You already found the reason why it fails (https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291). Reflash stock boot and system images via fastboot.
Click to expand...
Click to collapse
After reflash, I will need to start over, right?
Thanks
JackVoo said:
After reflash, I will need to start over, right?
Thanks
Click to expand...
Click to collapse
Start over with what? You will need to root your phone again, but you do not need to perform a factory reset.
_mysiak_ said:
Start over with what? You will need to root your phone again, but you do not need to perform a factory reset.
Click to expand...
Click to collapse
"Start over" mean restore all the app again?
Look at the steps, I will need to flash the system.img. Will I lost all the app data?
Thanks.
JackVoo said:
"Start over" mean restore all the app again?
Look at the steps, I will need to flash the system.img. Will I lost all the app data?
Thanks.
Click to expand...
Click to collapse
Nothing will be lost, app data will stay intact as it's located in /data partition.
Code:
E update_engine: [0615/084826.429756:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
E update_engine: [0615/084826.429929:ERROR:delta_performer.cc(430)] Unable to open ECC source partition vendor on slot B, file /dev/block/bootdevice/by-name/vendor_b: Success (0)
E update_engine: [0615/084826.432353:ERROR:delta_performer.cc(1135)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
E update_engine: [0615/084826.432433:ERROR:delta_performer.cc(1140)] Expected: sha256|hex = 8D0481F97F0F0184F9DFA41A11E27C3A6D36BF9B667327346CA6CB2CB73F52C5
E update_engine: [0615/084826.432483:ERROR:delta_performer.cc(1143)] Calculated: sha256|hex = 06C00C642CAB09B613A1BFC162C508453C8DF1D09A81081FC339812D94291569
E update_engine: [0615/084826.432568:ERROR:delta_performer.cc(1154)] Operation source (offset:size) in blocks: 0:2,71:1,75:2,79:2,82:1,85:1,87:2,92:1,97:1,137:1,291:82,573:2,3169:173,3343:7,3758:173,3949:7,5976:1,6874:1,7355:1,7363:1,7489:1,7498:1,8010:1,8123:1,8144:1,9464:1,9530:1,9535:1,9539:2,9544:2,9549:2,9554:2,9559:2,9565:2,9568:1,9571:2,9574:1,9577:2,9580:1,9590:2,9593:1,9596:2,9599:1,9604:1,9608:2,9613:2,9618:2,9623:2,9628:2,9631:1,9642:1,9644:1,9671:1,9673:1,9678:1
W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] [B]Device was remounted R/W 1 times[/B]. Last remount happened on 2020-05-15 10:30:34.000 UTC.
E update_engine: [0615/084826.432775:ERROR:delta_performer.cc(1435)] source_fd != nullptr failed.
E update_engine: [0615/084826.432968:ERROR:delta_performer.cc(296)] Failed to perform BROTLI_BSDIFF operation 5067, which is the operation 0 in partition "vendor"
E update_engine: [0615/084826.433040:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
I update_engine: [0615/084826.433510:INFO:delta_performer.cc(313)] Discarding 1311 unused downloaded bytes
Hi, I have follow the instruction https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291 to flash the system.img to my system partition. Still have the same issue.
My active slot is B, I only flash to B only, I didn't flash A. Does it has any effect?
I do not have root, so can't check with tune2fs.
Any suggestion?
Thanks
JackVoo said:
Code:
E update_engine: [0615/084826.429756:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
E update_engine: [0615/084826.429929:ERROR:delta_performer.cc(430)] Unable to open ECC source partition vendor on slot B, file /dev/block/bootdevice/by-name/vendor_b: Success (0)
E update_engine: [0615/084826.432353:ERROR:delta_performer.cc(1135)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
E update_engine: [0615/084826.432433:ERROR:delta_performer.cc(1140)] Expected: sha256|hex = 8D0481F97F0F0184F9DFA41A11E27C3A6D36BF9B667327346CA6CB2CB73F52C5
E update_engine: [0615/084826.432483:ERROR:delta_performer.cc(1143)] Calculated: sha256|hex = 06C00C642CAB09B613A1BFC162C508453C8DF1D09A81081FC339812D94291569
E update_engine: [0615/084826.432568:ERROR:delta_performer.cc(1154)] Operation source (offset:size) in blocks: 0:2,71:1,75:2,79:2,82:1,85:1,87:2,92:1,97:1,137:1,291:82,573:2,3169:173,3343:7,3758:173,3949:7,5976:1,6874:1,7355:1,7363:1,7489:1,7498:1,8010:1,8123:1,8144:1,9464:1,9530:1,9535:1,9539:2,9544:2,9549:2,9554:2,9559:2,9565:2,9568:1,9571:2,9574:1,9577:2,9580:1,9590:2,9593:1,9596:2,9599:1,9604:1,9608:2,9613:2,9618:2,9623:2,9628:2,9631:1,9642:1,9644:1,9671:1,9673:1,9678:1
W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] [B]Device was remounted R/W 1 times[/B]. Last remount happened on 2020-05-15 10:30:34.000 UTC.
E update_engine: [0615/084826.432775:ERROR:delta_performer.cc(1435)] source_fd != nullptr failed.
E update_engine: [0615/084826.432968:ERROR:delta_performer.cc(296)] Failed to perform BROTLI_BSDIFF operation 5067, which is the operation 0 in partition "vendor"
E update_engine: [0615/084826.433040:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
I update_engine: [0615/084826.433510:INFO:delta_performer.cc(313)] Discarding 1311 unused downloaded bytes
Hi, I have follow the instruction https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291 to flash the system.img to my system partition. Still have the same issue.
My active slot is B, I only flash to B only, I didn't flash A. Does it has any effect?
I do not have root, so can't check with tune2fs.
Any suggestion?
Thanks
Click to expand...
Click to collapse
You did not follow the instructions as they say to use Fastboot, not TWRP to flash images.
_mysiak_ said:
You did not follow the instructions as they say to use Fastboot, not TWRP to flash images.
Click to expand...
Click to collapse
I didnt't use twrp, I am using
Code:
fastboot flash system_b system.img
to flash the system.img.
My active slot is B. I get it from fastboot getvar all.
Thanks
JackVoo said:
I didnt't use twrp, I am using
Code:
fastboot flash system_b system.img
to flash the system.img.
My active slot is B. I get it from fastboot getvar all.
Thanks
Click to expand...
Click to collapse
Did you flash also boot.img? You mentioned that one R/W mount is from TWRP, which is not possible with stock boot and system images.
_mysiak_ said:
Did you flash also boot.img? You mentioned that one R/W mount is from TWRP, which is not possible with stock boot and system images.
Click to expand...
Click to collapse
Hi, ya. The remount R/W issue is cause by TWRP which I use at 15-May. I am trying to fix this issue. From the forum guide, if using custom ROM, then only need to flash boot.img.
Okay. I will try to flash boot.img and system.img.
Thanks for the reply
_mysiak_ said:
Did you flash also boot.img? You mentioned that one R/W mount is from TWRP, which is not possible with stock boot and system images.
Click to expand...
Click to collapse
Ya. the R/W is due to TWRP at 15-May. Which I want to fix this issue now
Okay. I will try flash the boot.img and system.img.
Thanks for the reply
Flash boot.img and system.img not working for this issue.
I solve it by flashing the new fastboot ROM to slot A. My current active slot is B.
Thanks for the help.
Related
I hope someone here can help me .
First, my Device:
Gigaset QV1030, originally named as Quanta FG6Q
Tegra 4 Chipset, 2gb of Ram, 2560*1600 Screen. Originally shipped with 4.2.2 .
It is quite similar to the Asus Transformer TF701t and the ekrnel source is available.
The Kernel is 3.4.35.
The Past:
I´ve successfully compiled cm10.1 for it, and it's running more or less flawless. So i have a working cwm, and i´m able to work with the sources
The Problem:
I tried to port any higer version than cm 10.1 to this device, but every one, icluding 10.2,11 and 12, show exactly the same Problem:
Surfaceflinger crashes with the following log:
03-03 21:34:42.303 155 155 I SurfaceFlinger: SurfaceFlinger is starting
03-03 21:34:42.307 155 293 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
03-03 21:34:42.325 155 293 D libEGL : loaded /system/lib/egl/libEGL_tegra.so
03-03 21:34:42.325 155 293 I : Attempting to load EGL implementation /system/lib/egl/libEGL_tegra_impl
03-03 21:34:42.461 155 293 I : Loaded EGL implementation /system/lib/egl/libEGL_tegra_impl
03-03 21:34:42.517 155 293 D libEGL : loaded /system/lib/egl/libGLESv1_CM_tegra.so
03-03 21:34:42.536 155 293 D libEGL : loaded /system/lib/egl/libGLESv2_tegra.so
03-03 21:34:42.544 155 293 D NvOsDebugPrintf: NvRmPowerModuleClockControl on MOD[108] INST[0]
03-03 21:34:42.606 155 293 D NVSI : ### VALID CONFIGURATION ###
03-03 21:34:42.619 155 293 D NvOsDebugPrintf: NvRmPowerModuleClockControl off MOD[108] INST[0]
03-03 21:34:42.799 155 293 D hwcomposer: Display 0: found 1 modes
03-03 21:34:42.799 155 293 D hwcomposer: unmatched: 2560 x 1600 @ 59.98 Hz
03-03 21:34:42.799 155 293 D hwcomposer: display type 0: vblank period = 16672794 ns
03-03 21:34:42.799 155 293 D hwcomposer: dc_blank: display 0, [-1 -> 0]
03-03 21:34:42.812 155 293 W hwcomposer: No supported resolution higher than 3, use Max resolution
03-03 21:34:42.812 155 293 D hwcomposer: display type 1: vblank period = 16666214 ns
03-03 21:34:42.812 155 293 D hwcomposer: Setting vblank display to Internal, new vblank period 16672794 ns
03-03 21:34:42.943 155 293 D hwcomposer: Creating nvcap video capture service
03-03 21:34:42.948 155 293 D hwcomposer: display type 2: vblank period = 16666214 ns
03-03 21:34:42.960 155 293 D hwcomposer: Display 0 layer clip is 2560 x 1600
03-03 21:34:42.960 155 293 D hwcomposer: Display 0 device clip is 2560 x 1600
03-03 21:34:42.960 155 293 I SurfaceFlinger: Using composer version 1.1
03-03 21:34:42.960 155 293 D hwcomposer: config[0].x = 2560
03-03 21:34:42.960 155 293 D hwcomposer: config[0].y = 1600
03-03 21:34:42.960 155 293 W SurfaceFlinger: no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
03-03 21:34:43.005 155 293 D NvOsDebugPrintf: Library for API 1 exposes function not wrapped: glPointSizePointerOES
03-03 21:34:43.050 155 293 I : Loading GLESv1_CM implementation /system/lib/egl/libGLESv1_CM_tegra_impl
03-03 21:34:43.050 155 293 I SurfaceFlinger: EGL informations:
03-03 21:34:43.050 155 293 I SurfaceFlinger: vendor : Android
03-03 21:34:43.050 155 293 I SurfaceFlinger: version : 1.4 Android META-EGL
03-03 21:34:43.050 155 293 I SurfaceFlinger: extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_create_context EGL_EXT_create_context_robustness EGL_NV_system_time EGL_ANDROID_image_native_buffer
03-03 21:34:43.050 155 293 I SurfaceFlinger: Client API: OpenGL_ES
03-03 21:34:43.050 155 293 I SurfaceFlinger: EGLSurface: 8-8-8-8, config=0xcaf32c
03-03 21:34:43.050 155 293 I SurfaceFlinger: OpenGL ES informations:
03-03 21:34:43.050 155 293 I SurfaceFlinger: vendor : NVIDIA Corporation
03-03 21:34:43.050 155 293 I SurfaceFlinger: renderer : NVIDIA AP
03-03 21:34:43.050 155 293 I SurfaceFlinger: version : OpenGL ES-CM 1.1
03-03 21:34:43.050 155 293 I SurfaceFlinger: extensions: GL_EXT_bgra GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_format_BGRA8888 GL_EXT_unpack_subimage GL_EXT_debug_marker GL_EXT_debug_label GL_NV_texture_npot_2D_mipmap GL_OES_byte_coordinates GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_extended_matrix_palette GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_fbo_render_mipmap GL_OES_fixed_point GL_03-03 21:34:43.050 155 293 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 4096
03-03 21:34:43.050 155 293 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 4096 x 4096
03-03 21:34:43.059 155 293 D SurfaceFlinger: Screen acquired, type=0 flinger=0xb8a9c478
03-03 21:34:43.059 155 293 D hwcomposer: hwc_blank: display 0: unblank
03-03 21:34:43.059 155 293 D hwcomposer: hwc_blank_display: display 0: [1 -> 0]
03-03 21:34:43.059 155 293 D hwcomposer: Display 0 layer clip is 2560 x 1600
03-03 21:34:43.059 155 293 D hwcomposer: Display 0 device clip is 2560 x 1600
03-03 21:34:43.059 155 293 D hwcomposer: dc_blank: display 0, [0 -> 0]
03-03 21:34:43.183 155 155 E SurfaceFlinger: ro.sf.lcd_density must be defined as a build property
03-03 21:34:51.852 155 545 E SurfaceFlinger: ro.sf.lcd_density must be defined as a build property
03-03 21:34:57.338 155 592 D PermissionCache: checking android.permission.ACCESS_SURFACE_FLINGER for uid=1000 => granted (233 us)
03-03 21:34:57.338 155 293 D SurfaceFlinger: Screen acquired, type=0 flinger=0xb8a9c478
03-03 21:34:57.338 155 293 D SurfaceFlinger: screen was previously acquired
03-03 21:35:10.562 155 293 I : Loading GLESv2 implementation /system/lib/egl/libGLESv2_tegra_impl
03-03 21:35:10.604 155 293 F libc : Fatal signal 11 (SIGSEGV) at 0x0000002f (code=1), thread 293 (SurfaceFlinger)
I included an archive with the contents of data/dropbox, if you want to take a further look.
What I tried:
I swapped out the entire egl folder with the asus one, and even the hwcomposer.tegra.so and the gralloc.hwcomposer.so, but the Problem stays exactly the same.
I tried to fiddle around with the various options in the BoardConfig.mk but i had no luck with that either.
What I guess:
This could be a pain for you to read, so please proceed with caution .
Because the Asus libs are known to be working with cm11 and 12, i guess that the Problem is not located in the *.so files. Also i can not imagine, how an entry in the Device folder could have such an outcome, as far as i know, the most settings there would´t affect such low-level stuff.
But what i know is, that a SIGSEGV means, that there is some sort of memory access violation, which means: Surfaceflinger, or one of it´s threads, try to access or allocate memory, which is not allowed.So i could imagine, that the Problem lies in the incomplete SELinux support in this Kernel, what would explain, why every Version higher than 4.2.2 fails, as SELinux is set to permissive and higher starting with 4.3. But the problem here is, that the Device wont even Boot past the initial Vendor Splashscreen with an SELinux enabled kernel.
My Question:
So i would like to know, am i on the right track with SELinux? Or are these Things not connected with each other?
And, if SELinux, or it´s abstinence, is not causing it, what is?
Thanks for your help in advance :good: .
On different Android-10 custom ROMs with stock vendor I get this error message every second in logcat.
Code:
11-05 11:38:38.927 478 3080 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IService/default": error code: 0x20
11-05 11:38:38.927 478 3080 E hwservicemanager: Failed to set property for starting [email protected]::IService/default
11-05 11:38:39.925 1095 1137 W ServiceManagement: Waited one second for [email protected]::IService/default
11-05 11:38:39.926 1095 1137 I ServiceManagement: getService: Trying again for [email protected]::IService/default...
This happens as soon as the location button (in quick settings) is turned on and doesn't stop when location is turned off.
PID 1095 is xtra-daemon.
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.
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.
I'm trying to update to 11.0.2 with TWRP & Magisk Installed
I ran the TWRP A/B Retention Script at the wrong time (I ran before the OTA applied) and now the update won't run because the sha doesn't match on recovery_b.
TWRP is still installed, and working properly.
How can I restore recovery_b to stock so that I can do the OTA update?
Code:
10-31 21:26:40.629 1354 1354 I update_engine: [1031/212640.629574:INFO:delta_performer.cc(452)] is_ddr5 is , partition name recovery , target path /dev/block/bootdevice/by-name/recovery_a
10-31 21:26:40.629 1354 1354 I update_engine: [1031/212640.629819:INFO:delta_performer.cc(504)] Opening /dev/block/bootdevice/by-name/recovery_a partition without O_DSYNC
10-31 21:26:40.631 1354 1354 I update_engine: [1031/212640.631207:INFO:delta_performer.cc(138)] Caching writes.
10-31 21:26:40.631 1354 1354 I update_engine: [1031/212640.631378:INFO:delta_performer.cc(516)] Applying 160 operations to partition "recovery"
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699043:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699251:ERROR:delta_performer.cc(550)] Unable to open ECC source partition recovery on slot B, file /dev/block/bootdevice/by-name/recovery_b: Invalid argument (22)
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699350:ERROR:delta_performer.cc(1282)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699405:ERROR:delta_performer.cc(1287)] Expected: sha256|hex = 67743BA06C21B6F433753BAB17B6747FA6DEDCC5589B48C62E7B760A08E78804
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699457:ERROR:delta_performer.cc(1290)] Calculated: sha256|hex = 4D367F9C46A3FECAC8F699FC501F141C3BB4D6A9B39DB2D26CC60CEF72ACD485
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699511:ERROR:delta_performer.cc(1301)] Operation source (offset:size) in blocks: 0:1,13293:511
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699608:ERROR:delta_performer.cc(1622)] source_fd != nullptr failed.
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699693:ERROR:delta_performer.cc(307)] Failed to perform BROTLI_BSDIFF operation 1409, which is the operation 0 in partition "recovery"
FYI
Just In Case Anyone is looking for it. I think the OTA update for BE86AA can be found here. I found it in logcat
https://android.googleapis.com/packages/ota-api/package/7d1400a6d94e7ab1ef096761876409963c0b1dae.zip
alchemist.zim said:
I'm trying to update to 11.0.2 with TWRP & Magisk Installed
I ran the TWRP A/B Retention Script at the wrong time (I ran before the OTA applied) and now the update won't run because the sha doesn't match on recovery_b.
TWRP is still installed, and working properly.
How can I restore recovery_b to stock so that I can do the OTA update?
Code:
10-31 21:26:40.629 1354 1354 I update_engine: [1031/212640.629574:INFO:delta_performer.cc(452)] is_ddr5 is , partition name recovery , target path /dev/block/bootdevice/by-name/recovery_a
10-31 21:26:40.629 1354 1354 I update_engine: [1031/212640.629819:INFO:delta_performer.cc(504)] Opening /dev/block/bootdevice/by-name/recovery_a partition without O_DSYNC
10-31 21:26:40.631 1354 1354 I update_engine: [1031/212640.631207:INFO:delta_performer.cc(138)] Caching writes.
10-31 21:26:40.631 1354 1354 I update_engine: [1031/212640.631378:INFO:delta_performer.cc(516)] Applying 160 operations to partition "recovery"
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699043:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699251:ERROR:delta_performer.cc(550)] Unable to open ECC source partition recovery on slot B, file /dev/block/bootdevice/by-name/recovery_b: Invalid argument (22)
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699350:ERROR:delta_performer.cc(1282)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699405:ERROR:delta_performer.cc(1287)] Expected: sha256|hex = 67743BA06C21B6F433753BAB17B6747FA6DEDCC5589B48C62E7B760A08E78804
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699457:ERROR:delta_performer.cc(1290)] Calculated: sha256|hex = 4D367F9C46A3FECAC8F699FC501F141C3BB4D6A9B39DB2D26CC60CEF72ACD485
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699511:ERROR:delta_performer.cc(1301)] Operation source (offset:size) in blocks: 0:1,13293:511
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699608:ERROR:delta_performer.cc(1622)] source_fd != nullptr failed.
10-31 21:26:40.699 1354 1354 E update_engine: [1031/212640.699693:ERROR:delta_performer.cc(307)] Failed to perform BROTLI_BSDIFF operation 1409, which is the operation 0 in partition "recovery"
FYI
Just In Case Anyone is looking for it. I think the OTA update for BE86AA can be found here. I found it in logcat
https://android.googleapis.com/packages/ota-api/package/7d1400a6d94e7ab1ef096761876409963c0b1dae.zip
Click to expand...
Click to collapse
How did you run twrp a/b retention script? im trying to look for it because it is no longer in magisk.
i went to the twrp a/b retention script link you provided but i tried flashing it in magisk and twrp it did not work it just come up with a error and won't flash.