[CCA 5.2.6] Nocturne: app opened with "black preview screen" and blue spinning circle |
||||
Issue descriptionChrome OS Version: 11297.0.0, 72.0.3618.0 (dev) channel Android vers: 9 Devices: Nocturne DVT (A70 Main4) Steps To Reproduce: 1.Open "CCA 5.2.6" app from launcher (Tablet landscape mode) Observe behavior below: Expected result: CCA should open without any issue Actual result: CCA app opened with camera preview black screen with blue spinning circle How frequently does this problem reproduce? (100%) Feedback ID: https://listnr.corp.google.com/product/5015361/report/85809863393
,
Nov 27
Probably due to https://buganizer.corp.google.com/issues/116822885
,
Jan 7
Since https://buganizer.corp.google.com/issues/116822885 has been fixed, this should not be reproducible now. Allen could you verify?
,
Jan 10
Still reproducible on Atlas with build 73.0.3664.0,11547.0.0 (dev) channel (GCA / CCA 5.3.2 canary) Feedback ID: GCA- https://listnr.corp.google.com/report/85898051566 CCA- https://listnr.corp.google.com/report/85898054813 Note: not reproducible on Atlas with build 11316.57.0, 72.0.3626.43 (beta) channel (GCA/CCA 5.3.2 canary) But not reproducible on Nocturne with build 11316.66.0, 72.0.3626.49 (beta) channel (GCA/CCA 5.3.2 canary)
,
Jan 10
I found the following suspicious logs in #1: 2018-11-26 10:24:02.048 3 cros_camera_service[1459]: E/ CAMHAL_PlatformData:Could not find sensor names 2018-11-26 10:24:02.048 3 cros_camera_service[1459]: E/ CAMHAL_Profiles:No sensor Info available, exit parsing 2018-11-26 10:24:02.048 3 cros_camera_service[1459]: E/ CAMHAL_ChromeProfiles:CameraProfiles base init error:-2147483648 2018-11-26 10:24:02.048 3 cros_camera_service[1459]: E/ CAMHAL_PlatformData:Failed to initialize Camera profiles 2018-11-26 10:24:02.050 3 cros_camera_service[1459]: E/ CAMHAL_PlatformData:@getInstance Failed to create CameraProfiles instance 2018-11-26 10:24:02.050 3 cros_camera_service[1459]: E/ CAMHAL_Camera3HALModule:No camera device was found! Daniel, could you triage?
,
Jan 10
This is probably related to https://b.corp.google.com/issues/122281782.
,
Jan 10
I've moved this issue to b/122281782 so that it is visible to partners. I'm closing it here.
,
Jan 10
Typo, it is moved to b/122628053. |
||||
►
Sign in to add a comment |
||||
Comment 1 by allendam@chromium.org
, Nov 26