* 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$PersistentTrustedReceiver
Change-Id: I17c1ab2bfb98375d9b5a6c6de91776244b12cf52
Signed-off-by: dlwlrma123 <alexfinhart@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
- This turbulence effect causes tremendous lags on devices with a midrange/low-end GPU as it requires expensive rendering.
- Hence, disable it by default to alleviate the situation.
Change-Id: I1a446adb36a2a9834b7733b74d8057e38425f8a6
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* Disabled on many devices with reports to lagginess in long term and random reboot in some instances.
Change-Id: I73985159766da08cd35b0288db29cfafc7db62b0
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Since Android 14, when we use the DCI-P3 color space on the adaptive color mode
there are multiple frame drops while using the device. Don't force it for now
until we have a proper fix.
Change-Id: I7ab3604f4b2932f0710374055d086aefad37aaab
The stock ROM enables this because our vibrator supports subtle "tick"
vibration effects. Enable it in our device tree as well to make pulling
down the notification shade/QS panel feel slightly more interactive.
Change-Id: I0c160694bd9616c8693a659da8db9cf4e59ba4c3
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the 8 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Enable Adaptive color mode setting.
Bug: 143513730
Test: Boot test and measure the adaptive color value
Change-Id: I969ec6c3cb1d092a33c0e3a028ff38ad7115dfe2
Accessibility transforms require a specific color mode that is not
always available for the user to select.
Bug: 130376719
Test: atest com.google.android.config.pts
Change-Id: Ia3211d5aa6e117c5361dea44d944064b23260a81
* toco and sweet don't have a notification light and since backlight
control has been moved to hwc this HAL is not needed for these targets.
* Keep the HAL itself in common tree so that devices which need are able
to build the lights HAL which is common for all targets with a
notification light.
Change-Id: Ia4c3c96e49b5ce58f4f55b92a65321fb258f8975
* We do not support different low power modes and handle doze lp1
and lp2 the same in kernel which makes this redundant.
This reverts commit ba52828323.
Change-Id: Ie51dea708f157d1f0ba19f1b00dc8ce3cf892931
* It was previously bumped to 2 because 1 was causing a purple tint
which didn't disappear after fod. This was fixed by properly handling
the minimal brightness level in kernel.
Change-Id: Iec1f73260c061cf5616ee9322514b33d889adfe5
* The following things are left in devices, because they're device specific
- voip compress properties
- HVDCP properties
- audio configs
- power profile
- rounded corner configuration
- partition configuration
- FOD
- camera motor
- NFC
- board-info
- fstab
- ipa and graphics firmware
- shipping and manifest target level
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Co-authored-by: Arian <arian.kulmer@web.de>
Change-Id: I8bef29041f8f239361b999fc8ab1a43cc2ebb86b
