* This fixes the following logspam:
E/ QTI PowerHAL: Failed to acquire lock for hint_id: 1040
E/ QTI PowerHAL: Failed to acquire lock for hint_id: 1041
E/ QTI PowerHAL: Failed to acquire lock for hint_id: 10A5
Change-Id: I03746ea83251d8b731afb8d307526d15320c3cf9
Signed-off-by: artemscine <artempemine@gmail.com>
* It's not using for 5.4/5.10/5.15 QCOM kernel family
Change-Id: I4d165a95f597df47f4d2ec07199b5dac0a347b61
Signed-off-by: NikitaSavc <micraftur@gmail.com>
This allows us to use it in QC Split Product Makefiles
Change-Id: Ibd7493eb8c266b524a8f51aad658837798cc3d2d
Signed-off-by: Mesquita <mickaelmendes50@gmail.com>
Signed-off-by: omnitrix21 <okand7946@gmail.com>
Set debug.sf.latch_unsignaled=1 is used to allow surfaceflinger to
latch unsignal buffers that can give more time for buffer to render.
But if the buffer takes longer time to finish, it will block whole
display pipeline result to jank.
Bug: 157964883
Test: scrolling, launch
Change-Id: I56c3e05921de5fc9569bf3f93fde03022a64b6a4
Signed-off-by: kibria5 <mdkibria687@gmail.com>
Need to explicitly set auto_latch_unsignaled property to
disabled state to keep latch-unsignaled as the default
behavior.
Change-Id: I3856caaf0a68e7e720819f25338d1eb9196f56b0
Matches Android 14 D1
commit 6d9f5fc6ee46136163be16ec53cc70b4cba02c83
Author: Evgenii Stepanov <eugenis@google.com>
Date: Fri Jun 16 16:47:21 2023 -0700
Rename sysprop for MTE mode in system_server.
Move the system property that controls MTE mode in system_server out of
arm64.memtag.process namespace. Process sysprops affect the MTE mode of
any process with the given name; using such property in a product means
that any process or test unfortunately named "system_server" would be
affected.
Bug: 280343521
Test: debuggerd `pidof system_server` | head -30 | grep tagged_addr
affected by the new property
not affected by the old property
Signed-off-by: angelomds42 <angelomds42@gmail.com>
Signed-off-by: adi8900 <adrianszymanski242@gmail.com>
Out of all the modes that run the CPU at advertised speeds without
underclocking, mgame has the most conservative thermal limits.
Change-Id: I491f608a7be5c9497c70b3e49501d7abf58a980c
This is a squash of the following commits:
1. Optimise dex flags for a faster boot
* Used multiple threads and speed profile to hasten the first boot
2. Rework dex flags again
When I went through https://source.android.com/devices/tech/dalvik/configure my previous configs felt wrong, this one should be perfect (I hope).
Even though there is a slight trade-off for boot time by using the speed profile, we do make up for it by using 8 threads.
PRODUCT_DEX_PREOPT_DEFAULT_COMPILER_FILTER attempts to compile all prebuilts fully optimised to speed level, thus the phone doesnt need to deal with it.
I also do know that this might be a trade-off on size, but I do see the first boot time is more worthy to trade-off.
The speed level mentioned here runs dex verification and compiles all AOT methods.
3. Switch certain dexopt profiles to verify
Prebuilt apps like Gmail/Google App, will be updated by google play, and there is no need spend time and space optimising what is going to be replaced.
Switch to Google's recommendation of using verify for an OTA package.
Applications still stay on speed.
Instead, replace the install profile with speed-profile making apps perform better.
* Currently mobile network signal and speed was not giving wanted results for daily drive
* Disable QCRIL battery saving mode to have maximum network Performance
Change-Id: I893dc82491996a3ce203f26d9df32919b74c728c
* During the UVC conifguration initialiation qcom USB script tries to create multiple folder and symlinks
* so allow qcom USB script to succesfully create them without any denials.
Change-Id: I601c038a2c83301a9427350d12ad80aced03fe22
* these processes were not allowed to run in background and yet they still persist everytime causing logspam and unnecessary broadcast, we may want to disable "GmsIntentOperationService" but some users on xda reported broken notifications on stuffs like google keep and maybe other google apps that relies on GmsIntentOperationService broadcasts.
07-24 09:29:26.041 2997 5548 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
07-24 09:29:26.042 2879 2879 I Zygote : Process 8201 exited due to signal 9 (Killed)
07-24 09:29:26.043 2997 3023 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiversdm845-common: overlay: Disable intrusive gms components
Change-Id: Icf85dd512072c6898be9d0c9ba88f17702fdaf54
