Status Update
Comments
ra...@google.com <ra...@google.com> #2
This is a particularly hard device to come by - do you happen to have access to the device? If so could you provide us with the output of: adb shell dumpsys media.camera > info.txt
Thanks!
al...@gmail.com <al...@gmail.com> #3
Stacktrace:
Caused by: java.lang.IllegalArgumentException: Can not get supported output size under supported maximum for the format: 34
at androidx.camera.camera2.internal.SupportedSurfaceCombination.getSupportedOutputSizes(SupportedSurfaceCombination.java:355)
at androidx.camera.camera2.internal.SupportedSurfaceCombination.getSuggestedResolutions(SupportedSurfaceCombination.java:197)
at androidx.camera.camera2.internal.Camera2DeviceSurfaceManager.getSuggestedResolutions(Camera2DeviceSurfaceManager.java:198)
at androidx.camera.core.CameraX.calculateSuggestedResolutions(CameraX.java:943)
at androidx.camera.core.CameraX.bindToLifecycle(CameraX.java:293)
at androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle(ProcessCameraProvider.java:227)
Below are some findings based on our debugging
When Dex is connected
previewConfig.getMaxResolution() is returning "731x411" as maxSize.
Inside Preview.Builder.build() -> Default_MAX_resolution is set to "CameraX.getSurfaceManager().getPreviewSize()" which is 731x411
this is being picked as maxSize.
While rendering maxSize is 731x411 and minSize is 640x480 and below are available outputSizes
0 = {Size@11860} "4032x3024"
1 = {Size@11861} "3984x2988"
2 = {Size@11862} "4032x2268"
3 = {Size@11863} "3024x3024"
4 = {Size@11864} "2976x2976"
5 = {Size@11865} "3840x2160"
6 = {Size@11866} "3264x2448"
7 = {Size@11867} "4032x1960"
8 = {Size@11868} "2880x2160"
9 = {Size@11869} "3264x1836"
10 = {Size@11870} "2160x2160"
11 = {Size@11871} "2560x1440"
12 = {Size@11872} "2224x1080"
13 = {Size@11873} "2048x1152"
14 = {Size@11874} "1920x1080"
15 = {Size@11875} "1440x1080"
16 = {Size@11876} "1088x1088"
17 = {Size@11877} "1280x720"
18 = {Size@11878} "1024x768"
19 = {Size@11879} "1056x704"
20 = {Size@11880} "960x720"
21 = {Size@11881} "960x540"
22 = {Size@11882} "720x720"
23 = {Size@11883} "800x450"
24 = {Size@11884} "720x480"
25 = {Size@11885} "640x480"
26 = {Size@11886} "352x288"
27 = {Size@11887} "320x240"
28 = {Size@11888} "256x144"
29 = {Size@11889} "176x144"
and couldn't find any size in this range.
When Dex not connected
minsize = 640x480
maxsize = 1920x1080
0 = {Size@11836} "4032x3024"
1 = {Size@11837} "3984x2988"
2 = {Size@11838} "4032x2268"
3 = {Size@11839} "3024x3024"
4 = {Size@11840} "2976x2976"
5 = {Size@11841} "3840x2160"
6 = {Size@11842} "3264x2448"
7 = {Size@11843} "4032x1960"
8 = {Size@11844} "2880x2160"
9 = {Size@11845} "3264x1836"
10 = {Size@11846} "2160x2160"
11 = {Size@11847} "2560x1440"
12 = {Size@11848} "2224x1080"
13 = {Size@11849} "2048x1152"
14 = {Size@11850} "1920x1080"
15 = {Size@11851} "1440x1080"
16 = {Size@11852} "1088x1088"
17 = {Size@11853} "1280x720"
18 = {Size@11854} "1024x768"
19 = {Size@11855} "1056x704"
20 = {Size@11856} "960x720"
21 = {Size@11857} "960x540"
22 = {Size@11858} "720x720"
23 = {Size@11859} "800x450"
24 = {Size@11860} "720x480"
25 = {Size@11861} "640x480"
26 = {Size@11862} "352x288"
27 = {Size@11863} "320x240"
28 = {Size@11864} "256x144"
29 = {Size@11865} "176x144"
and we have 12 available sizes in this range
Camera2DeviceSurfaceManager.java:: getPreviewSize()
mCameraSupportedSurfaceCombinationMap.get(cameraId).getSurfaceDefinition().getPreviewSize() = "1920x1080"
cameraId=0
al...@gmail.com <al...@gmail.com> #4
The issue root cause is that CameraX will default filter out sizes smaller than 640x480. For Preview, the max size will be limited to under display size. I checked the HW spec info for the issue related devices. Display size of FUJITSU F-04J/F-05J is 360x640. That will result int that no size exists in the conditions that is larger or equal to 640x480 and smaller or equal to 360x640.
A temporary workaround for this situation is to use Preview.Builder#setTargetResolution() to set a size smaller than 640x480 to bypass the problem.
For device FUJITSU arrowsM04, I checked its HW spec info and its display size I found is 1280x720. It seems that the problem should not exist in the device.
Could you confirm that the problem exist on arrowsM04 device? What will be the returned value when using Display#getRealSize to obtain the display size?
ra...@google.com <ra...@google.com> #5
> A temporary workaround for this situation is to use Preview.Builder#setTargetResolution() to set a size smaller than 640x480 to bypass the problem.
OK. I will try it.
> Could you confirm that the problem exist on arrowsM04 device?
We receive the crash report (Crashlytics) that this crash has occurred on arrowsM04.
We don't have this device so we can't confirm that the problem really exist on arrowsM04.
> What will be the returned value when using Display#getRealSize to obtain the display size?
We can't investigate it for the same reason.
Thank you.
al...@gmail.com <al...@gmail.com> #6
This issue happened on devices that the display size is smaller than 640x480. In original auto-resolution mechanism, supported sizes smaller than 640x480 will be default filter out.
The auto-resolution mechanism encodes the guaranteed configurations tables in CameraDevice#createCaptureSession(SessionConfiguration). It defines that the PREVIEW size is the small one of the device display size and 1080p. The PREVIEW size will be the maximal size limitation for Preview use case. The reason it limits the size to display size and 1080p is the stream output in display size or 1080p has been able to provide good enough preview quality. Therefore, auto-resolution mechanism will limit the selected size to be smaller than the small one of the device display size and 1080p.
With above two conditions, in this issue, all sizes smaller than 640x480 have been filter out, therefore, there is no size smaller than the display size 320x240 can be selected to use. And cause the exception.
Solution:
When the display size is smaller than 640x480, auto-resolution mechanism won't filter out those small sizes smaller than 640x480. This makes those small size be left and can be selected for the Preview use case on small display devices.
The solution has been merged and will be included in next CameraX release.
ra...@google.com <ra...@google.com> #7
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)
al...@gmail.com <al...@gmail.com> #8
Could you help to provide the following information to clarify the issue?
1. Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?
2. Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).
ra...@google.com <ra...@google.com> #9
- Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?
Yes
- 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.
al...@gmail.com <al...@gmail.com> #10
Hello.
- 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)
}
}
}
ra...@google.com <ra...@google.com> #11
al...@gmail.com <al...@gmail.com> #12
I tried to find the device specs and both 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 1.0.0-beta04
release. Before 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-beta04
version. Maybe you can also consider to upgrade to the latest 1.0.0-rc01
version for your application. Thanks.
al...@gmail.com <al...@gmail.com> #13
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
- 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
ra...@google.com <ra...@google.com> #14
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.
al...@gmail.com <al...@gmail.com> #15
Branch: androidx-main
commit 69d15dff7bb857ee33a0f643ff42a0f8bc475ab2
Author: charcoalchen <charcoalchen@google.com>
Date: Fri Jan 08 18:30:03 2021
Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.
Do not filter out sizes smaller than 640x480 when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.
Relnote:"Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480."
Bug: 150506192
Test: SupportedSurfaceCombinationTest
Change-Id: I2a63ce8e2ad42a9cc060c8635ac3603bf440b1ec
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/SupportedSurfaceCombination.java
M camera/camera-camera2/src/test/java/androidx/camera/camera2/internal/SupportedSurfaceCombinationTest.java
ra...@google.com <ra...@google.com> #16
ra...@google.com <ra...@google.com> #17
Also the output from adb shell dumpsys jobscheduler
is not complete. Can you please make sure you dump all the info ?
al...@gmail.com <al...@gmail.com> #18
The `adb shell dumpsys jobscheduler` was incomplete since I didn't know how how to copy the text that was cut-off at the top in my Command Prompt. I've now exported results to a txt file directly which allows me to capture everything, however that means I can't get the rest of the previous `adb shell dumpsys jobscheduler` so I did a new one.
ra...@google.com <ra...@google.com> #19
No, that was always a requirement (since WorkManager 1.0).
This behavior is not tied to WorkManager's implementation though. Its JobSchdeduler
that drives the work. So something could have changed there.
I don't see the logs for an App launch after the app exited doze mode? Do you have additional logs from that session ?
al...@gmail.com <al...@gmail.com> #20
al...@gmail.com <al...@gmail.com> #21
ra...@google.com <ra...@google.com> #22
Thanks. I don't see anything unusual there.
Save this script and try running this using python 3
.
Pass the fully qualified package name as the argument to the script. So something like: python3 jobs.py <your_package_name>
.
I still feel like I am missing huge chunks of dumpsys jobscheduler
. Alternatively, you can also do something like: adb shell dumpsys jobscheduler > out.txt
and send me that.
import os
import sys
def jobs(name):
command = 'adb shell dumpsys jobscheduler | grep -A 24 ".*JOB.*%s"' % (name)
os.system(command)
if __name__ == "__main__":
if len(sys.argv) < 2:
print('Usage is ./job.py package_name')
else:
name = sys.argv[1]
jobs(name.strip())
al...@gmail.com <al...@gmail.com> #23
I'm trying to run the script you sent me but I don't really know how.
ra...@google.com <ra...@google.com> #24
I think you may have forgotten to attach the file.
al...@gmail.com <al...@gmail.com> #25
ra...@google.com <ra...@google.com> #26
Nothing looks out of the ordinary. It looks like you had the Worker
run a couple of times based on:
Timer{<0>com.simonits.adalerts} NOT active, 0 running bg jobs
Saved sessions:
996813165 -> 996902031 (88866), 1 bg jobs.
995442568 -> 995655179 (212611), 1 bg jobs.
995400126 -> 995442559 (42433), 1 bg jobs.
991729518 -> 991739652 (10134), 1 bg jobs.
988324231 -> 988392138 (67907), 1 bg jobs.
987839386 -> 987894917 (55531), 1 bg jobs.
973374788 -> 973542710 (167922), 1 bg jobs.
973335801 -> 973335832 (31), 1 bg jobs.
973334781 -> 973335795 (1014), 1 bg jobs.
973298163 -> 973298778 (615), 1 bg jobs.
973164612 -> 973295300 (130688), 1 bg jobs.
972009891 -> 972228958 (219067), 1 bg jobs.
970880825 -> 971109890 (229065), 1 bg jobs.
969749680 -> 969976527 (226847), 1 bg jobs.
968608690 -> 968847501 (238811), 1 bg jobs.
967034243 -> 967091488 (57245), 1 bg jobs.
965486455 -> 965562052 (75597), 1 bg jobs.
964497879 -> 964555054 (57175), 1 bg jobs.
963084431 -> 963303262 (218831), 1 bg jobs.
961964759 -> 962178948 (214189), 1 bg jobs.
961282552 -> 961468886 (186334), 1 bg jobs.
960842943 -> 960902474 (59531), 1 bg jobs.
959881647 -> 959938712 (57065), 1 bg jobs.
958821517 -> 958977069 (155552), 1 bg jobs.
957169812 -> 957383549 (213737), 1 bg jobs.
So your Worker
was running.
ra...@google.com <ra...@google.com> #27
Your Worker
should respect stoppage requests. Try adding that.
Apart from that, nothing here looks out of the ordinary. I am marking this bug as not-reproducible.
If you have more information, feel free to comment and I can take a look.
al...@gmail.com <al...@gmail.com> #28
I will look into stoppage requests. Thanks.
ra...@google.com <ra...@google.com> #29
I found an edge case, where your Worker
will not correctly be rescheduled if it got interrupted.
That's probably why JobScheduler
is not picking it up. Adding a fix.
al...@gmail.com <al...@gmail.com> #31
ra...@google.com <ra...@google.com> #32
I just wanted to keep you in the loop. This should be addressed by WM 2.3.3.
al...@gmail.com <al...@gmail.com> #33
ap...@google.com <ap...@google.com> #34
Branch: androidx-master-dev
commit 3f01efa9acd4208ad35f2537bf730562982d088b
Author: Rahul Ravikumar <rahulrav@google.com>
Date: Thu Feb 27 15:04:30 2020
Mark WorkSpecs unscheduled when they are interrupted.
* We cancel work in all schedulers when onWorkFinished() is called irrespective of the
state of the WorkSpec.
* When a WorkSpec is interrupted, if it needs rescheduling, the schedule_requested_at bit must be unset,
so it can picked up by Schedulers.
Fixes:
Test: Added unit tests.
Change-Id: I9c5fb3192710ec853b5c80ffd4da5f8936912c1c
M work/workmanager/src/androidTest/java/androidx/work/WorkDatabaseMigrationTest.java
M work/workmanager/src/androidTest/java/androidx/work/impl/WorkerWrapperTest.java
M work/workmanager/src/main/java/androidx/work/impl/WorkDatabase.java
M work/workmanager/src/main/java/androidx/work/impl/WorkDatabaseMigrations.java
M work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
A work/workmanager/src/schemas/androidx.work.impl.WorkDatabase/11.json
Description
Version used: 2.3.2
Devices/Android versions reproduced on: Pixel 3a, Android 10
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).
I have unique periodic work that runs every 15 minutes. On version 2.3.1, the work stops starting when my device enters Doze Mode when I go to sleep. Then in the morning when I pick up my phone and it exits Doze Mode, the work starts again every 15 minutes. In version 2.3.2, the works stops starting when my device enters Doze Mode, but in the morning when my device exits Doze Mode, the work does not start again and never starts thereafter.