After unbalancing, move these IRQs to separate cores
to improve latency.
Change-Id: Ib1c22f9c8d8c00cf74351099e88fbb5ae70e9114
Signed-off-by: aswin7469 <aswinas@pixysos.com>
* Apply c4524313d16d8cc9f000ed92d0806ffd7ee8fd9e to voip call paths as well
this is a dirty fix as in stock voip call and voice call uses diffrent values
well, something is btr than nothing
TO-DO: figure out acdb id's and rewrite this properly hence fix nos cam recording too
Signed-off-by: aswin7469 <aswinas@pixysos.com>
* Goodix tuning for noise cancellation is broken for aosp roms and loads
incorrect input device in calls
* Correct the paths after comparing with stock logs
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Set max to a saner of 200.
Also prior to this change, 80 was default for torch, so set 80 as
default.
Signed-off-by: Jis G Jacob <studiokeys@blissroms.org>
This commit resolves an issue where High Dynamic Range (HDR) content
was not being displayed correctly on peridot after android 15 qpr2
The problem stemmed from Vulkan graphics API support not being
enabled in the device's build configuration. While the device's
hardware (SM8635) natively supports Vulkan, the ROM's build system
was not configured to include or link against the required Vulkan
libraries and Hardware Abstraction Layers (HALs).
By adding to the device's BoardConfig,
the Android build system now correctly compiles and integrates Vulkan
support. This enables the display framework and underlying vendor HALs
to utilize Vulkan, which is essential for the device's HDR pipeline.
An observation post-fix is the change in how SurfaceFlinger processes
HDR content. Initially, when viewing HDR content, SurfaceFlinger reported
, which typically corresponds to HAL_DATASPACE_BT709
or SRGB_LINEAR, meaning the content was treated as standard dynamic range (SDR).
After enabling Vulkan, the same application layer now correctly shows
(HAL_DATASPACE_BT2020_PQ), which is the
appropriate dataspace for HDR10 (Perceptual Quantizer) content.
After this change, HDR content is now rendered perfectly, confirming
its dependency on a fully enabled Vulkan graphics stack.
Signed-off-by: kenway214 <kenway214@outlook.com>
Signed-off-by: AnilShebin <anilshebin@gmail.com>
- This flag turns off GPU/CPU intensive UI effects and
reduces the RAM footprint.
- Using this is a better compromise than the 'low_ram' flag
as this does not disable features in the rom but still
reduces RAM usage and gives better smoothness in the UI.
android-15
- Set only 4 threads to be utilized for dex2oat as dex2oat supports concurrent jobs since [1].
- Moreover, set only 4 threads to be utilized for boot image dex2oat as well.
[1]: 93c605c0d6
Change-Id: I8cf2544efeb4cd0c9befbaa2c208eed68c4204ac
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
* Its eating more RAM and slow down device
* Thanks for CAFEBABE find this
Change-Id: I648564f842033810a376661ecf2c8719e4137e1b
Signed-off-by: Jabiyeff <cebiyevanar@gmail.com>
Signed-off-by: rayrzy <vrayananda@yahoo.com>
