3895dba9476547f431efc41b38caa0ea526e2866
- Root cause: When an app uses the system default camera app to open the camera on the phone, and another app uses an Intent (MediaStore.ACTION_IMAGE_CAPTURE) (the system default camera app) to open the camera on the virtual display, because they will use the same thread in the camera service, the camera will only reconfigure the stream without creating it again. Therefore, the onCameraOpened callback will not be triggered, causing the issue that the camera on the virtual display is not blocked. - Solution: The camera mechanism is that only one camera can run at a time. If two apps open the camera at the same time, it will first open and close the camera of one of two apps, and then open the camera of another app. So we identify above issue according to this rule: track the app that opens the camera on the phone (main display). When it is detected that this app also appears on the virtual display, it means that the app appears on both sides at the same time, which belongs to the above issue, and the camera of this app is set to a blocked state. Bug: 210795569 Test: Manual Change-Id: Idabee8a38085c8aae1f47f3579cead1adde385ea
…
…
…
…
…
…
…
…
Merge "Update data type and comments on tagSocket/untagSocket APIs" am:
ef89731cd3 am: aa82affbc0 am: 292d5f01ec
…
…
Merge "DO NOT MERGE: Downbranch merge conflict [Output Switcher] Refine seekbar control" into tm-dev
…
…
…
…
Merge "limit TelecomManager#registerPhoneAccount to 10; api doc update" into qt-dev am:
08f8988bc3 am: 8193edd104 am: 74f9b7f432 am: 6b36ce6895 am: e518ef6409 am: 4636aea564 am: d4e7e2336a
…
…
Merge "Remove unused empty filegroups from frameworks/base." am:
5ee9c55130 am: 76e9b955c5 am: 735d0192f6
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%