- Jan 27, 2023
-
-
Change-Id: I8f64a6fa9b4b2e4520e25731f55e89f5087c70da Signed-off-by:
Corinna Vinschen <xda@vinschen.de>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
Change-Id: I90daada0d887008d56e84ce29b3f0b011a298698 Signed-off-by:
Corinna Vinschen <xda@vinschen.de>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev>
-
- Jan 26, 2023
-
-
The FOD layers should be always composed by the device to set the custom zpos bits to the kernel. By default all layers are set to device composition and the proprietary libsdmextension.so moves some to client composition. Unfortunately that also affects the Udfps touched layer. After this commit the layer below the Udfps touched layer is forced to be client composition. For unknown reasons libsdmextension will not change the Udfps touched layer to client composition anymore. tests: - Run 'adb shell dumpsys SurfaceFlinger' and ensure that the Udfps touched layer is composed by the device - Ensure that the Udfps touched layer correctly sets the zpos bits on the kernel while / after using WFD Signed-off-by:
daniml3 <danimoral1001@gmail.com>
Signed-off-by: Arian <arian.kulmer@web.de>
Change-Id: I8aeb98d18557ad4e971eaba74700ceb3058273ab
Signed-off-by: Noah Anleitner <noah.anleitner@halogenos.org> -
* Supports changed z Udfps order * Supports changed Udfps usage bits TheScarastic: Adapt to extension lib and support 12 BiometricPrompt ArianK16a: Adapt layer name to UdfpsControllerOverlay for Android 13 and only compare the prefix. Drop the BufferQueueLayer change because it seems unnecessary. Co-authored-by:TheScarastic <warabhishek@gmail.com>
Change-Id: Id95aa73e06b4223a6b4f05c69fa2fc494f9a97b1
Signed-off-by: Noah Anleitner <noah.anleitner@halogenos.org>
-
- Jan 13, 2023
-
-
While enabling #define LOG_NDEBUG 0, run camera cts test command: run cts -m CtsCameraTestCases -t android.hardware.camera2.cts.MultiViewTest#testSharedSurfaceImageReaderSwitch the libgui will crash due to nullptr, fix this by add nullptr judgement when pointing to the Graphicbuffer handle Bug: 228349805 Signed-off-by:
tangcheng <tangcheng@xiaomi.com>
Change-Id: I69a84bdb5208b16df88f5f09f45c1a93ad2afe01
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
With the previous commit entering idle aggressively, it is important that touch boost works well. Since there are valid cases where we would want touch boost to work when there are no layers detected (e.g., notification panel pull down if it was not accounted for during the initial vote type set), change touch boost to work regardless of layer's status. Change-Id: I0a125cf9027440de205fa4ca611657b70b8a088f Signed-off-by:
Juhyung Park <qkrwngud825@gmail.com>
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
There are now global sanitizers that will be applied to all modules, so we no longer need to decalre local sanitizer options. One of the local sanitizer options caused a ubsan shift-out-of-bounds SIGABRT in several location modules in code that does not appear to have anything problematic with it. Test: Build with SDClang 12 and look out for FATAL errors. Change-Id: I6beb96c8d8547639092ba0d2e8b29387105544bd Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Taken from CLO (QSSI 13). Some Qualcomm devices can still benefit from disabling backpressure propagation by setting: debug.sf.disable_backpressure=1 Change-Id: I2346a1b314666706e1299b295f13b2cef6e00b4d Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Most of the HWC backends don't consume HAL_DATASPACE_ARBITRARY, and will end up with client composition. This change fixes the Surface to clear the prior requested dataspace leftover upon disconnect, and let vulkan swapchain to skip setting dataspace upon PASS_THROUGH. Bug: 239893387 Bug: b/234703161 Test: android.view.cts.DisplayRefreshRateTest#testRefreshRate with angle Test: android.media.cts.EncodeDecodeTest with angle Test: dEQP-EGL.* with angle Test: dEQP-VK.wsi.android.* Change-Id: Iba1d9160569ad6136127cf8055aa75f195fed3d9 Signed-off-by:
Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
... to continue aosp/2157379 to pass dEQP tests with ANGLE using PASS_THROUGH color space as the default. Bug: 237512291 Bug: b/234703161 Test: cts -m CtsDeqpTestCases --module-arg CtsDeqpTestCases:include-filter:dEQP-EGL.* Change-Id: I7753858bf5d740f5083e0e48d97be75b127ad11b Signed-off-by:Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
This CL allows us to specify the pass through color space, and as a consequence, HAL_DATASPACE_ARBITRARY, on swapchain creation. This helps us pass Media encode/decode test cases on ANGLE. Bug: 237512291 Bug: b/234703161 Change-Id: I7aebe80d77fdc454f04489fbc552bad40a922ae3 Merged-In: I7aebe80d77fdc454f04489fbc552bad40a922ae3 Signed-off-by:
Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
When usage bits were 32-bits, and the bit 31 is 1, will meet the below error: E Gralloc4: buffer descriptor contains invalid usage bits 0xffff00000000 E GraphicBufferMapper: validateBufferSize(0xb400007adcd71320) failed: 1 android_native_buffer_t define usage_deprecated as int. For example usage_deprecated is 0x80000000, uint64_t(0x80000000) will cast to 0xffffffff80000000, which leads to validateBufferDescriptorInfo fail. Add ANDROID_NATIVE_UNSIGNED_CAST(usage_deprecated) to fix this. Test: CtsMediaRecorderTestCases android.media.recorder.cts.MediaRecorderTest#testProfileAvcBaselineLevel1 Bug: b/244620240 Signed-off-by:
Jessie Hao <juan.hao@nxp.com>
Change-Id: I131b9dee3b2b768729218d8f7cabe0026ab89007
(cherry picked from commit 5480b212)
Signed-off-by: Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
If the MotionEvent has too many PointerCoords, it will lead to an infinite loop and cannot complete the operator<<. Bug:244248855 Test: printed MotionEvent in log to see the formatting Signed-off-by:
hupeng3 <hp121520@gmail.com>
Change-Id: Id4a01152bc4103976d3f60e69eb375e3d32669a0
Signed-off-by: Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
SELinux makes sure only system services can call installd. Bug: 244657173 Fixes: 244657173 Test: presubmit Test: adb bugreport, check that it has installd section Change-Id: I27a77a12b025cfb27e774c2334e08facdcb4c77e Signed-off-by:
Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
Test: N/A Change-Id: I33c8d35601e56cab1d12db663957795bf15a0a02 Signed-off-by:
Akash Srivastava <akashniki@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
When the parent of a layer changes, shadowRadius should not be directly passed in the computBounds here. When the layer's parent changes, for example, open an app in freeform. If the app exits the current ActivityRecord, it will trigger the recent task request screen capture of the current app, temporarily switch the task of the app to "Screenshot Parent", and then switch back. This operation will cause the shadow of the task to be passed to the children layers through CanDrawShadows, i.e., the shadow of non Container layer is wrongly passed to its children layers. Therefore, there is a problem in shadow drawing. We should judge whether shadowRadius needs to be passed at this time through CanDrawShadows. If not, pass 0.f. Otherwise, the shadow will be painted repeatedly. bug:215476160 in partnerissuetracker Signed-off-by:
xinying1 <xinying1@xiaomi.corp-partner.google.com>
Change-Id: Id4b6c8bcc79aa68f96d0c4c655ea853361ed1e7c
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
You can't use binder after forking, so we can drop the FD. The binder driver doesn't support this (once the FD is open, we would need to open a new context in the child process). So, the userspace API would need to handle resetting all state. However, in general, handling this for multi-threaded processes (because of needing to take all locks by all libraries used by all threads and restoring state, etc...) is too complicated to make work in Android. Bug: 232904068 Bug: 244525876 Test: binderLibTest Change-Id: I38c354af2c69804a40dc2774086a9ab77d158ede (cherry picked from commit df732baf) Signed-off-by:
Simão Gomes Viana <devel@superboring.dev> -
[Optimization] It's no need to start the dispatch cycle going if the outbound queue was not previously empty. If the outbound queue was not previpusly empty, it indicates that the connection's pipe is full.We will try start the next dispatch cycle for this connection in "doDispatchCycleFinishedCommand". This follows "enqueueDispatchEntriesLocked". Change-Id: I7736c2bfdb13c35a51b74c46ada7b0f562fecfd9 Merged-In: I7736c2bfdb13c35a51b74c46ada7b0f562fecfd9 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
This conditionally reverts a commit [1] which causes random camera crashes on tama devices [1] https://github.com/LineageOS/android_frameworks_native/commit/a9550f3fe9097e0934e9b44c5aac6b914fb46aec Change-Id: If3d9c722c63a9da2f9ca10e21de9d7bc6dba7c52 Signed-off-by:
Simão Gomes Viana <devel@superboring.dev> -
Author: Bruno Martins <bgcngm@gmail.com> Date: Wed Oct 14 23:45:14 2020 +0100 Edit: Adapt to new lineage soong config Change-Id: Ic0f314f4053628667a921951f610839f36a5079c Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Change-Id: Iecd2be3eb8775855d82763f069a38bb70fe53d4e CRs-Fixed: 3229968 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Currently, the properties are used as follows: 1. debug.sf.enable_hwc_vds - allows IDs to be generated for VDs 2. vendor.display.vds_allow_hwc - allows WFD to use HWC path With this change, HWC path is enabled for WFD with only the vendor property set. All other virtual displays require both of the properties enabled. Change-Id: Iab2c8d15d2c1cf24be0d371af8892c346634507f CRs-Fixed: 3204941 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
* These changes are part of CAF AOSP merge commits Change-Id: I390f874347d259fca4429c19711be6c85b104090 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Allow HWC based virtual display only for wifi display CRs-Fixed: 2984439 Change-Id: Ifbb094a2a0101171b475bd5a60660a3599dce5ff Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
Bug: 169788930 Change-Id: Ic50f5675d0cd48f84fb9ff14221355741dc52129 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
1. SurfaceFlinger: Fix virtual display related issues. 1) Validate output buffer usage bit appropriately Validate output buffer usage bit only against GRALLOC_USAGE_HW_COMPOSER to differentiate GLES only conposition and HWC/MIXED composition. 2) Exclude video encoder usage for scratch buffer Sink and Scratch buffers in VDS are using same usage flags. This causes video encoder flag to be set for scratch buffers Also. Exclude video encoder flag from scratch buffer usage flags as scratch buffers are used only as write back input and not video encoder input. 2. sf: Allow VDS to use HWC -- Preserve VDS layer pixel format based on GRALLOC flags. -- skip color layer for vds 3. sf: Add secure content support for VDS 4. sf: Enable GPU comp. for non-primary displays Ensure that "Return status" of dequeueBuffer() complies with API requirements. Client relies on this status to call requestBuffer() upon reallocation. 5. sf: Enable UBWC on virtual display scratch buffer Set GRALLOC_USAGE_HW_FB usage flag on virtual display Scratch buffer to enable UBWC. Change-Id: Ia49a175372ca187a295531e18f8e84dc22a19486 CRs-Fixed: 2656027 Signed-off-by:Simão Gomes Viana <devel@superboring.dev>
-
- Jan 10, 2023
-
-
Simão Gomes Viana authored
-
Simão Gomes Viana authored
-
Simão Gomes Viana authored
-
- Jan 07, 2023
-
-
Layer dataspace is initialized as unknown by default, unless overriden by the buffer source. We don't require expensive rendering for color conversion when the dataspace is unknown. Change-Id: I079c520f63a65c77ba3162664656e607eafff991 Signed-off-by:Simão Gomes Viana <devel@superboring.dev>
-
- Jan 01, 2023
-
-
Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
In streaming video case, video decoder needs to change buffer color space dynamically according to video stream real-time parameters. CRs-Fixed: 3155775 Change-Id: I21590ee41708f5cb1ed45cb5a7f5c00f1c129bb0 Signed-off-by:
Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Simao Gomes Viana <simao@halogenos.org>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
CRs-Fixed: 3013293 Change-Id: Idfafcd6aa718054ff749bd5d1c7eb2630be0f109 Signed-off-by:
DennySPb <dennyspb@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Simao Gomes Viana <simao@halogenos.org>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
Change-Id: Icdfd3512a79d9935d3fdb611c96dc8fd91a5e1c5 Signed-off-by:
DennySPB <dennyspb@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Simao Gomes Viana <simao@halogenos.org>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
Unlinking death recipients (from linkToDeath) is a normal part of Binder operation, and doing it when a BpBinder's refcount has reached 0 is not much different. This log message is constantly spamming when swiping as part of a back navigation gesture: 04-05 22:29:41.402 655 3888 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor> 04-05 22:29:41.413 655 3888 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor> 04-05 22:29:41.424 655 3888 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor> 04-05 22:29:41.435 655 681 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor> 04-05 22:29:41.447 655 3888 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor> Logging is relatively expensive on Android and the log spam isn't useful, so suppress this log message by setting it to the verbose log level. Change-Id: I774d0c59ca6f70a4e2ed33b9fac3fb5b86d8ff0a Signed-off-by:
Simao Gomes Viana <simao@halogenos.org>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
* Change I7f4174581e24e361577640b9263514a168ed482d implemented validation of the buffer description info prior to creating the descriptor. Some of our legacy devices need to whitelist additional usage bits to support various functionality. libui: Extend adb95ae to Gralloc3 libui: Extend adb95ae to Gralloc4 This commit squashes: libui: Convert lineage product variables to soong config variables Change-Id: Ib687c966d4eafcc1128611b95ebed00fd0a8bfaf Change-Id: Ie369e78f78e9ac0b18ab3dfea520d4f123005d92 Signed-off-by:Simão Gomes Viana <devel@superboring.dev> -
The candidate of presnet fence is switched dynamically between front/back buffer, based on current design, it will introudce in big side effect especially for app launching, app resume cases, sometimes the timestamp of the candidate fence is not signaled, but the other candidate has fence signaled already. Then previous logic is not well handled to pick up theright presnet fence candidate. Then frame is skiped. This change is to use the legacy logic to pick up fence candidate. It can avoid such abnormal frame skip behavior. Change-Id: I055942d9ae9ac6c96eba403aa4bc1979cf128ce8 CRs-Fixed: 3035044 Signed-off-by:
Chenyang Zhong <zhongcy95@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev> -
libstagefright_omx library need to be extended to vendor which is depenednet on libgui which is a vndk_private lib. Creating vendor version so that libstagefright_omx_ext can link to libgui_vendor. Conflicts: libs/gui/Android.bp CRs-Fixed: 2258968 Change-Id: I777eebffc405c8bb74aab270e9f272c806501458 Signed-off-by:
Volodymyr Zhdanov <wight554@gmail.com>
Signed-off-by: Simão Gomes Viana <devel@superboring.dev>
-
- Oct 01, 2022
-
-
Android Build Coastguard Worker authored
Change-Id: I7327923aa6952c485af578121a177262f3281432
-
- Sep 30, 2022
-
-
Rob Carr authored
-
