Camera is not working in GSI image. [385408744]

Infeasible

Bug

NeedsInfo

Status Update

No update yet.

Description

ka...@samsung.corp-partner.google.com

created issue #1

Dec 21, 2024 12:22PM

Dear Google,

We are trying to run CTS on GSI image for Camera. But due to Policy error camera provider is not getting created and due to that camera is not working in GSI image.

11-01 09:14:15.109 E 267 267 init Unable to set propertyservice.camera.supportedCameras from uid:1047 gid:1005 pid:19822: SELinux permission check failed
11-01 09:14:15.106 I 19822 19822 CHI [SS_INFO]: [CHI_META ]: chxsecvendortag.cpp: chi_init_static_metadata: 3407: X
11-01 09:14:15.106 E 19822 19822 CHI [SS_ERR ]: [CHI ]: chxextensionmodule.cpp: EnumerateGeneratedCameras: 3967: [CAMID_DBG] CAM_REAR_ULTRA_WIDE : Fail!! initializing static vendor tag
11-01 09:14:15.106 I 19822 19822 CHI [SS_INFO]: [CHI ]: chxextensionmodule.cpp: EnumerateGeneratedCameras: 3991: [CAMID_DBG] (frameworkId= 0, logicalCamId= 0 publicVisibility=1 ppDeviceInfo[0].(physicalCamId= 2, frameworkId= 0, sensorId= 2)) ,primaryCamId= 2, chiCamId=25 (CAM_ID_MAX )
11-01 09:14:15.106 E 19822 19822 CamX [ERROR][CHI ] camxchi.cpp:3282 ChiStartCSSAONUsecase() Invalid CSS(0x0) / static settings(0xb4000072ebe7c010)
11-01 09:14:15.106 D 19822 19822 CHI [SS_CORE_CFG]chxextensionmodule.cpp:2518 GetNumCameras()ExposedNumOfCamera:1, all:1 legacy 0
11-01 09:14:15.106 I 19822 19822 Samsung_CameraProvider_impl Loaded "QTI Camera HAL" camera module
11-01 09:14:15.119 I 19822 19822 CHI [SS_INFO]: [CHI ]: chxextensionmodule.cpp: GetChiCameraIDByFrmID: 11496: [CAMID_DBG] Current Camera : CAM_REAR_WIDE
11-01 09:14:15.119 I 19822 19822 CHI [SS_INFO]: [CHI ]: chxextensionmodule.cpp: SecRemapCameraId: 13018: frameworkCameraId : 0 and logicalCameraId : -1
11-01 09:14:15.119 W 19822 19822 CHI [SS_WARN]: [CHI ]: chxextensionmodule.cpp: SecRemapCameraId: 13044: [CAMID_DBG] frameworkCameraId 0 mode 0: Can not find logical camera id on Map
11-01 09:14:15.119 E 19822 19822 CamX [ERROR][HAL ] camxhal3.cpp:667 get_camera_info() HAL3Module::GetCameraInfo() failed with result CamxResultEFailed
11-01 09:14:15.119 E 19822 19822 Samsung_CameraProvider_impl Initialize: Camera info query failed!
11-01 09:14:15.119 E 19822 19822 Samsung_CameraProvider_impl Create: Initializing CameraProvider failed: No such device (-19).
11-01 09:14:15.119 E 19822 19822 AIDL_CameraProvider Error! Creating CameraProviderHwl failed
11-01 09:14:15.119 E 19822 19822 AIDL_CameraProvider Initialize: Creating CameraProviderHwlImpl failed.
11-01 09:14:15.119 E 19822 19822 AIDL_CameraProvider Create: Initializing CameraProvider failed: No such device (-19).
11-01 09:14:15.119 I 19822 19822 AIDL_CameraProvider CameraProvider destructor

Have attached full logs for this issue

Thanks

Comments

ch...@google.com <ch...@google.com> Dec 23, 2024 03:49AM

Status: New

sh...@samsung.corp-partner.google.com <sh...@samsung.corp-partner.google.com> #2Dec 23, 2024 04:25AM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Could you please share the full bug report from android 15.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.

vi...@google.com <vi...@google.com> #3Dec 23, 2024 09:53AM

Assigned to vi...@google.com.

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

vi...@google.com <vi...@google.com> #4Dec 29, 2024 08:18AM

We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.

vi...@google.com <vi...@google.com> #5Jan 5, 2025 04:43PM

Status: Won't Fix (Infeasible)

We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.

Issue 385408744