Camera freeze with Samsung A23 [376173735]

Assigned

Bug

Status Update

No update yet.

Description

ma...@adnovum.ch

created issue #1

Oct 29, 2024 10:44AM

With the last app release, we have updated two deprecated “androix.camera” methods:

https://developer.android.com/reference/kotlin/androidx/camera/core/ImageAnalysis.Builder#setTargetResolution(android.util.Size)

https://developer.android.com/reference/kotlin/androidx/camera/core/Preview.Builder#setTargetAspectRatio(int)

Instead, we started using the following two methods as recommended by Android:

https://developer.android.com/reference/kotlin/androidx/camera/core/ImageAnalysis.Builder#setResolutionSelector(androidx.camera.core.resolutionselector.ResolutionSelector) with a ResolutionStrategy

https://developer.android.com/reference/kotlin/androidx/camera/core/Preview.Builder#setResolutionSelector(androidx.camera.core.resolutionselector.ResolutionSelector) with an AspectRatioStrategy

Unfortunately, after that update the clients having a Samsung A23 device started to call our support as the camera / QR Code scanner in the app stopped working. It’s kind of frozen / greyed out.

After contacting Samsung they provided us the following logs:

-----------------
here you will find the answer from R&D.

Issue related to stride alignment.

08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 256
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 512
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 256
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 512
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 256
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 512
08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 256

Stridealignment and scanlinealignment calculations are incorrect leading to recovery, so this alignment need to be handled from 3rd party app side.

-----------------

CAMERAX VERSION 1.3.2

CAMERA APPLICATION NAME AND VERSION: version 14.1.00.67

ANDROID OS BUILD NUMBER: UP1A.231005.007.A236BXXU6EXF3

DEVICE NAME: Galaxy A23 5G

Comments

we...@google.com <we...@google.com> Oct 29, 2024 11:20AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #2Oct 29, 2024 12:28PM

Reassigned to ma...@adnovum.ch.

Hi,

The problem might be caused by the other Samsung A23 known issue b/308445386. Please refer to the table in b/308445386#comment#39, there might be CameraAccessException: CAMERA_ERROR (3) occurred or the images received from ImageAnalysis might be cropped.

When migrating to use ResolutionSelector, the selected resolution for ImageAnalysis might be changed according to your setting. To clarify whether this issue is the same as b/308445386, could you help to check what resolutions are selected for Preview and ImageAnalysis before/after migrating to use ResolutionSelector and check whether it matches the results in b/308445386#comment#39?

As I remembered, the problem might occur on different resolutions if another ImageCapture is bound together. Therefore, I didn't find a good workaround for this issue.

Looks like your app requires Preview + ImageAnalysis UseCases combination. If it is confirmed that the issue is the same as b/308445386, is it possible to create a device-specific workaround in your side to select the workable/suitable resolutions with ResolutionFilter according to the table in b/308445386#comment#39?

About the following log, it should not be printed by CameraX. By searching some internal info, it might be printed by some qcom related code. If Samsung indicates it is related to the root cause, I would think the issue you reported should be really caused from the device side.

08-12 14:29:43.170 1047 1118 1118 E CHINODEUTIL: [SS_ERR]camxchinodeutil.cpp:1006 GetAlignment()Stride or scanline alignment calculation may be incorrect!, strideAlignment = 512, scanlineAlignment = 256

BTW, for b/308445386, we also tried to reported to Samsung but do not get feedback till now. Hope that using ResolutionFilter to select specific resolution can resolve the problem in your app before Samsung fixes the issue in the device side.

Issue 376173735

Description

Issue summary

Comments

we...@google.com <we...@google.com> Oct 29, 2024 11:20AM

ch...@google.com <ch...@google.com> #2Oct 29, 2024 12:28PM

Add comment

Issue metadata