IssueTracker

Thanks for reporting this. We will investigate this and get back to you once we have an update.

The issue has been fixed and merged to Android Open Source Project. The fix should be available in the next tv-compose release (Version: 1.0.0-alpha04).

Closing this ticket. Feel free to re-open in case of any issues.

Thanks 😀

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.tv:tv-material:1.0.0-alpha04

Hello.

This crash still occurs.

• CAMERAX VERSION: 1.0.0-beta4
• ANDROID OS BUILD NUMBER: Android 7.1.1
• DEVICE NAME: FUJITSU F-02H

We receive following crash report from FUJITSU F-02H. So far We have received this crash report only from F-02H.

java.lang.IllegalArgumentException
Can not get supported output size under supported maximum for the format: 34

androidx.camera.camera2.internal.SupportedSurfaceCombination.getSupportedOutputSizes (SupportedSurfaceCombination.java:349)
androidx.camera.camera2.internal.SupportedSurfaceCombination.getSuggestedResolutions (SupportedSurfaceCombination.java:197)
androidx.camera.camera2.internal.Camera2DeviceSurfaceManager.getSuggestedResolutions (Camera2DeviceSurfaceManager.java:198)
androidx.camera.core.CameraX.calculateSuggestedResolutions (CameraX.java:949)
androidx.camera.core.CameraX.bindToLifecycle (CameraX.java:351)
androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle (ProcessCameraProvider.java:230)
(our application's package name).CameraFragment.bindCameraUseCases (CameraFragment.java:174)

1. Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?

Yes

2. Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).

Since we don't have this device, we'll try to collect this information in the next version of our app. The next version will be released later this month.

Hello.

2. Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).

We have collected the output of the device where the crash occurs.

Device1

• Model : arrows Be F-05J
• Android Version : 7.1.1
• Supported output sizes of ImageFormat.PRIVATE

CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

Device2

• Model : Fujitsu arrows M04
• Android Version : 7.1.1
• Supported output sizes of ImageFormat.PRIVATE

CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

Additional Information

CameraX version : 1.0.0-beta04

We collect the supported output sizes by following code.

val errorString = buildString {
      append("The supported output sizes of ImageFormat.PRIVATE: ")

      (requireContext().getSystemService(Context.CAMERA_SERVICE) as CameraManager).apply {

        cameraIdList.forEachIndexed { index, cameraId ->
          val msg = if (VERSION.SDK_INT >= VERSION_CODES.M) {
            val configurationMap =
              getCameraCharacteristics(cameraId).get(CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP)
            val sizes = configurationMap?.getOutputSizes(ImageFormat.PRIVATE)
            "CameraId $index: ${sizes?.joinToString(" ,")}"
          } else {
            "CameraId $index: This device version is under M."
          }
          append(msg)
        }
      }
    }

I tried to find the device specs and both Fujitsu arrows Be F-05J and Fujitsu arrows M04 should have 720x1280 size display. For the camera id 0 device, it is a different case that the display size is larger than 640x480 but the device only supports a 480x480 size. The case also caused the same IllegalArgumentException and was also fixed by aosp/1254406 that was merged in 2020/05/17 and should be included in 1.0.0-beta04 release. Before aosp/1254406 was merged, the only 480x480 size would be filtered out and then caused the IllegalArgumentException. After it was merged, the 640x480 size threshold was removed and then the 480x480 size would be kept and selected to use.

It looks like 1.0.0-beta04 release had been used to collect the supported sizes information. But the issue should have been fixed by 1.0.0-beta04 release. Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?

CameraX's 1.0.0-rc01 version has been released. There should be many fixes included in it compared to the 1.0.0-beta04 version. Maybe you can also consider to upgrade to the latest 1.0.0-rc01 version for your application. Thanks.

Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?

We collect informations only from the device on which IllegalArgumentException happened.

Our latest app uses CameraX version 1.0.0-beta10 and this issue still occurres.

However we don't receive crash report from Fujitsu arrows Be F-05J or Fujitsu arrows M04 so far. (This doesn't mean this issue is fixed on these devices because our app is heavily rely on camera so these device's user wouldn't use our app anymore.)

Instead, we receive crash report from Fujitsu F-03K.

• Model : Fujitsu F-03K
• Android Version : 7.1.2
• Supported output sizes of ImageFormat.PRIVATE

CameraId 0 : 480x480
CameraId 1 : 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

I missed some settings when I simulated the issue by robolectric test so that I was not able to reproduce it. Now, I can reproduce the issue if the device only supports one 480x480 resolution. I'm working on the solution and target to make it included in next release.

The solution has been merged in https://android-review.googlesource.com/1545624. Update the status to be fixed.