HWC and cit sensor logspam is so intense it bumps up logd's idle CPU
usage up to over 3%. With this change, logs are much cleaner and logd
idle CPU usage is reduced to under 1%, while still allowing error logs
to pass through.
- Do this only in user/debug builds (except eng).
- Add wifi and cnss too while we're at it, they can get noisy at times.
The device ships with PocketMode app, which effectively disables
listening to fingeprints in case the proximity sensor is covered.
Change-Id: If67a0a98c753726ae2eed4d76e073275d7ae74da
gEnableConcurrentSTA=wlan1 will create wlan1 while insmod driver.
[Mashopy: This also fix 'E android.hardware.wifi@1.0-service: Unknown iface name: wlan0' logspam]
Change-Id: Ia7ce00bbc9cb030320bc3bd84f8795c3583ef8b1
CRs-Fixed: 2258995
Signed-off-by: aswin7469 <aswinas@pixysos.com>
-- this feature overrides fps during game play to a
constant value irrespective of actual game frame rate
which is not appropriate.
Change-Id: If072c09dd1f448648eef6199fdebff3853145412
10-19 19:55:47.098 W/HidlServiceManagement(2413): Waited one second for android.hardware.tetheroffload.control@1.1::IOffloadControl/default
10-19 19:55:47.098 I/hwservicemanager(632): Since android.hardware.tetheroffload.control@1.1::IOffloadControl/default is not registered, trying to start it as a lazy HAL (if it's not configured to be a lazy HAL, it may be stuck starting or still starting).
10-19 19:55:47.099 I/HidlServiceManagement(2413): getService: Trying again for android.hardware.tetheroffload.control@1.1::IOffloadControl/default...
10-19 19:55:47.101 W/libc (632): Unable to set property "ctl.interface_start" to "android.hardware.tetheroffload.control@1.1::IOffloadControl/default": PROP_ERROR_HANDLE_CONTROL_MESSAGE (0x20)
10-19 19:55:47.101 I/hwservicemanager(632): Tried to start android.hardware.tetheroffload.control@1.1::IOffloadControl/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
10-19 19:55:47.072 E/init (1): Control message: Could not find 'android.hardware.tetheroffload.control@1.1::IOffloadControl/default' for ctl.interface_start from pid: 632 (/system/system_ext/bin/hwservicemanager)
Change-Id: I970e97248073347604cd019fdd7411c83661c189
Unused effect and led to errors during querying and loading configurations.
E EffectsFactoryConfigLoader: Error querying effect 7d1580bd-297f-4683-9239-e475b6d1d69f on lib offload_bundle.
E EffectsFactoryConfigLoader: EffectLoadXmlEffectConfig 1 errors during loading of configuration: /vendor/etc/audio/sku_cape/audio_effects.xml.
E EffectsFactory: Effect config is partially invalid, skipped 1 elements.
Signed-off-by: chandu078 <chandudyavanapelli03@gmail.com>
Signed-off-by: aswin7469 <aswinas@pixysos.com>
With this change, the schedutil governor
has to wait 500 microseconds to increase
frequencies and 20 milliseconds to decrease
frequency. It improves performance at a
slight cost to power.
Change-Id: Ied25fc112cbb49d70ea496e0beded612478ef897
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Background tasks are not UX-critical.
Free up cores to work on more important
UX tasks.
Change-Id: I01b17f15256a95513b59fd1c7d9d6d71979cebcc
Signed-off-by: aswin7469 <aswinas@pixysos.com>
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
