Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Note for dev team to check: If this isn't an error, CameraX should not log.
an...@mutualmobile.com <an...@mutualmobile.com> #3
Hello,
Thanks for filing this issue, this issue can be safely ignored - we have a todo for removing unnecessarily logging. This should be fixed shortly.
If there are other issues, please let us know.
na...@google.com <na...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 404aab04fc5ede6314fa93ff7b62431f9646e0e9
Author: Trevor McGuire <trevormcguire@google.com>
Date: Mon Apr 20 15:49:47 2020
Switch "Failed to set already detached use case online" to debug log
This can occur if the use case is detached before the camera's thread
has a chance to add the use case to the capture session. This should
not affect normal operation, so this error log message can be changed
to a debug log.
Relnote: "Converted error log related to detached use case to a debug log on Camera2CameraImpl."
Test: ./gradlew bOS
Bug: 154422490
Change-Id: I1a565e55af6e63792287221f8cbd9e7747fd6875
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/Camera2CameraImpl.java
https://android-review.googlesource.com/1291317
Branch: androidx-master-dev
commit 404aab04fc5ede6314fa93ff7b62431f9646e0e9
Author: Trevor McGuire <trevormcguire@google.com>
Date: Mon Apr 20 15:49:47 2020
Switch "Failed to set already detached use case online" to debug log
This can occur if the use case is detached before the camera's thread
has a chance to add the use case to the capture session. This should
not affect normal operation, so this error log message can be changed
to a debug log.
Relnote: "Converted error log related to detached use case to a debug log on Camera2CameraImpl."
Test: ./gradlew bOS
Bug: 154422490
Change-Id: I1a565e55af6e63792287221f8cbd9e7747fd6875
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/Camera2CameraImpl.java
Description
Component used: Macrobenchmark module Version used: benchmark-macro-junit4:1.2.0-alpha01 Devices/Android versions reproduced on: Android TV
Running macrobenchmark test on any AndroidTV application which doesn't have
<category android:name="android.intent.category.LAUNCHER" />
but instead has only<category android:name="android.intent.category.LEANBACK_LAUNCHER" />
for the launcher activity, will result in Unable to acquire intent for package becauseMacroBenchmarkScope.startActivityAndWait()
is relying only oncontext.packageManager.getLaunchIntentForPackage()
and not ongetLeanbackLaunchIntentForPackage()
Instead of throwing exception immediately, you could try to grab launch intent by calling
getLeanbackLaunchIntentForPackage()
if the first one fails.