How can we disable UVC support in Android Video SDK 2.x?

Video SDK
,
1

Hi

We are developing an Android STB application that uses a USB-connected camera.

After upgrading from Video SDK 1.x to 2.x, we began experiencing new camera-related problems that were not present in 1.x.
We suspect these issues are related to Android UVC support introduced in the 2.x series.

Our camera is already recognized by Android and can be accessed through the Android Camera API.
Therefore, ideally, we want to avoid SDK-level UVC handling.

We have two main problems:

1. A USB permission dialog is now shown whenever the app starts.
This started happening after moving to Video SDK 2.x with UVC support.
We do not want end users to see this dialog.

2. After a video chat ends, the camera may become unusable at the hardware level.
Even if USB permission is granted and the call starts successfully, once the session ends the camera sometimes stops working properly.
This issue did not happen with Video SDK 1.x.

Our questions are:

  • Can UVC support be disabled in Video SDK 2.x on Android?

  • Can we force the SDK to use the regular Android camera framework instead of UVC handling?

  • Is the camera-not-released / camera-stuck-after-call behavior a known issue?

  • Are there any recommended settings, APIs, or cleanup procedures to avoid this problem?

We can provide logs and device details if needed.

Our env
Android 9.0
Video SDK 2.5.0 ← NG
Video SDK 1.14.1 ← OK

Thank you.

2

Hi @Shishikaku I can take this question to our android team and get back to you shortly with their answer.

3

Hi @Shishikaku Apologies for the wait. I contacted our Android team and they replied with the following:

We do not support disabling UVC camera since we assume the cameras that connect to the device will be used. We’ll also release the UVC camera after leaving the session.

They can use callback onUVCCameraStatusChange to check the camera status. However, If there is still issue with the camera status, please provide the SDK log for us to investigate further.

Would you be able to try these steps and share logs with us if you still encounter any issues?