IssueTracker

Great! Thanks a lot, I'll look for the live updates soon!

・What is the use case combination. ⇒ There are no special use cases. Just start the camera.

Sorry, I mean the CameraX's use cases such as Preview, ImageCapture, ImageAnalysis and VideoCapture (VideoCapture is still under development and is not currently recommended for production).

And one thing want to confirm is

=> the white image problem happen on the "Preview" screen or saved photo by "ImageCapture"? or both?

Ask this is because a photo icon is in the attached file, it looks like a "Preview". And the reproduce step only indicate "Just start the camera."

Thanks

Hi,

Thanks for the update. If you have more findings, let us know.

Here are some questions. Whether this problem occurs in the native camera application? or in other applications have camera function (has to be using camera2 API)? If possible, Camera2Basic is a common sample to test.

Btw, if the problem only occurs on a specific API version or even a build number of Huawei P20 Lite, the workaround I can currently think of is to use CameraControl#setExposureCompensationIndex to adjust the exposure value . But it will need to know what the appropriate value is.

"Then, after opening the application using camaraX, open the native camera application and return to the application using camaraX, the preview will not turn white and will return to the normal display."

This is strange. Does the customer still encounter this problem? Or did the problem disappear after that?

Hi

Could you provide your APK for us to test?

and could customer provide the build number of device?

Hi

Thanks for provide the application link and the build number.
I can reproduce it now on Huawei P20 Lite (ANX2J) Android 9.0 by your application.

The issue should be a device specific issue when meet below conditions

1. Back camera.
2. The surface resolution of Preview is 400x400 or 720x720.
3. The zoom ratio is larger than about 3.37 or linear zoom is larger than about 0.94.

We will have a workaround to resolve this issue on this device.

Besides, may I know how does your app set up the Preview use case? (which result in the resolution 400x400).

i.e

Preview preview = new Preview.Builder()
    // ?
    .build();

Hi

Thank you for your confirmation.

The preview use cases in the app are as follows.

val preview = Preview.Builder().setTargetResolution(Size(400, 400)).build()

Best Regards,

We are trying to remove the problematic resolution 400x400 and 720x720 from the candidate list on this device to avoid this issue.
Then your app will get another resolution of Preview (probably 544x408) on this device.
If you are using PreviewView (or other View with correct scaling), then the UI should still have correct aspect ratio.
I believe your app should already handle that because not every device will get 400x400 for Preview. For example, your app run on Pixel 5 get 640x480 for Preview.
If you have concern about the workaround please let me know. Thank you.

The solution will be included in next release.

Hi,

Take a quick look on it. I updated the app to latest (PeePooNote 1.3.7).
I still get the original issue. Dump the camera configuration by adb shell dumpsys media.camera

Stream[0]: Output
      Consumer name: ImageReader-3456x3456f100m2-23426-1
      State: 4
      Dims: 3456 x 3456, format 0x21, dataspace 0x8c20000
      Max size: 12648450
      Combined usage: 864691129529008131, max HAL buffers: 4
      Frames produced: 0, last timestamp: 0 ns
      Total buffers: 6, currently dequeued: 0
Stream[1]: Output
      Consumer name: SurfaceView - jp.spl.peepoonote/jp.spl.peepoonote.CameraActivity#0
      State: 4
      Dims: 400 x 400, format 0x22, dataspace 0x0
      Max size: 0
      Combined usage: 864691129529010435, max HAL buffers: 7
      Frames produced: 600, last timestamp: 2104751830445000 ns
      Total buffers: 8, currently dequeued: 7

Stream[1] is the preview stream and still uses the problematic resolution Dims: 400 x 400.

From the message

"The version of CAMERAX applied to the app is 1.1.0-alpha07."

Not sure if it is a typo? since the latest version is 1.1.0-alpha08.