[clarencelol: It improves scrolling janks in my testing]
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
With the kernel patch to separate placement hinting part of
boost signal on placement into a prefer_high_cap hint knob,
TA will lose the boost placement hint.
This CL adds placement hinting back to TA when INTERACTION
is on.
Bug: 144451857
Test: Boot & run jank test.
Change-Id: I3dcb39804d5bbaff344fbdaf64548335a1fdf1ea
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
Since power_off_alarm is vendor module, so rename it to
vendor.power_off_alarm
Change-Id: Ib4bf6574117cd6b0a381d96de2abf4907a54785d
CRs-Fixed: 2858409
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* As per the init.qcom.rc service defination has vendor prefix
* This Fixes:
I init : Command 'start rmt_storage' action=boot (/vendor/etc/init/hw/init.target.rc:161) took 0ms and failed: service rmt_storage not found
Change-Id: I271adb887b9420d631e67eb4e7f436f0cd931f32
Signed-off-by: pix106 <sbordenave@gmail.com>
On fs/post-fs trigger there are chances of vendor partition mounting,
which may block ipa loading. To prevent the same change the
trigger level.
Signed-off-by: pix106 <sbordenave@gmail.com>
* This gives proper permission to /dev/diag node so that diag driver
can load successfully
* Logs spam with error '-13' which basically translates to access denied/invalid permission.
* Fix this by giving system read and write access.
Change-Id: I87fe322e7c0d91a494d29213e6f657ed8a7032a6
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* Needs Kernel side support
* This activates kernelspace battery saver via powerhal whenever
battery saver is enabled in userspace, thereby lowering power
consumption at kernel-level by disabling boosts and such
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Change-Id: I2623503db27d7518de519bcaa3f5af6ab83879d0
All this does is to disable msm_core and set the
polling_interval to 0, which makes the driver useless.
We can achieve the same result by disabling the driver.
Change-Id: Ic19c505ed74811a3d1b76703255af3aa5cb37bf9
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Signed-off-by: Subhajeet Muhuri <subhajeet.muhuri@gmail.com>
Signed-off-by: OdSazib <odsazib@gmail.com>
* This is manually ported by me from Lavender tree on Corvus-Devices
* Thanks @StyloGey for reviewing the java code and giving me a better solution
* Original repo: https://github.com/Corvus-Devices/device_xiaomi_lavender.git
To get it working, you need these two commits in your kernel:
> c04d6d6e61
> 8e25ac3318
Signed-off-by: OdSazib <odsazib@gmail.com>
Change-Id: I1bb48ced1f23728daa2e5170647ce08a04347110
As it turned out, allowing background, system-background, restricted,
foreground and top-app to use all 8 cores results in severe jitter and lag
whenever background tasks are running, whether it be on boot, or during waking up
from sleep.
This commit readds pinning background to cores 0-1, system-background and
restricted to cores 0-3, foreground to cores 0-6 and top-app to cores 0-7.
Change-Id: Idb76879e75e05b437600f0b689c260c674eb7eea
During bootup the device first enumerates in ADB only composition
and then falls back to the persist.sys.usb.config.
Prevent this enumeration in ADB only composition during bootup
by setting the sys.usb.configfs from init.qcom.usb.rc
Change-Id: I4d9aa8454202b8118ff76dfda7f44c6413c42020
The restorecon_recursive directive in init is only applied if the
file_contexts file changed between builds, but not necessarily if any
file or folder inside /mnt/vendor/persist/ has changed.
The restorecon code checks whether an xattr named
"security.sehash" contains a string that matches the current
combined hashes of the SELinux context files and skips restoring labels
if there is a match, see
https://android.googlesource.com/platform/external/selinux/+/refs/tags/android-9.0.0_r35/libselinux/src/android/android_platform.c#1546
Force wiping that xattr so that restorecon always runs since it's not
very expensive (there are currently only about 50 files on /persist).
The restorecon is needed to fix issues such as wrong stock labels on
/mnt/vendor/persist/sensors/:
sensors_persist_file -> persist_sensors_file
Change-Id: Ic0cd848836ee550499d9236f56ed6e939e35f01e
Qseecom needs to start at earlier stage for FBE to work properly.
* Wait for prop moved to device as we have still oreo qseecom devices with different prop name
Change-Id: Ie2408f652df291ad6a1b0dee1e4d559ff35c7c45
Signed-off-by: Ramandeep Trehan <rtrehan@codeaurora.org>
All this does is to disable msm_core and set the
polling_interval to 0, which makes the driver useless.
We can achieve the same result by disabling the driver.
Change-Id: Ic19c505ed74811a3d1b76703255af3aa5cb37bf9
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Signed-off-by: Subhajeet Muhuri <kenny3fcb@gmail.com>
