* jasmine thermal leads to:
- 50% reduction in Geekbench scores for multi-core
- Problem with rapid charging for higher ambient temperature
These wayne-configs fix the above issues
- In my testing, i faced some CPU Stalls with the old setup. (caused some spikes in jitter and non-consistent hackbench).
- 1000 was perfect in my testing and did not hit over power usage.
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
hardware/google/pixel/power-libperfmgr from android-11.0.0_r25
SQUASHED:
Revert all HIDL interface and nuke previous changes
Import Pixel libperfmgr AIDL Power HAL
Adapt and rebrand for xiaomi_sdm660
Remove Google-specific display LPM control
Remove Google-specific camera and audio hints
Remove VR hints handling
Remove audio hints handling
Remove dumpstate support
Initialize powerHAL when boot is completed
Add support for tap-to-wake feature control
Add sepolicy rules for power-libperfmgr
Enable power-libperfmgr
Signed-off-by: Subhajeet Muhuri <subhajeet.muhuri@aosip.dev>
init: Control message: Could not find 'android.frameworks.sensorservice@1.0::ISensorManager/default' for ctl.interface_start from pid: 447 (/system/bin/hwservicemanager)
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 ~3.5 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 precious RAM on this
device.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
Signed-off-by: K A R T H I K <karthik.lal558@gmail.com>
Signed-off-by: chrisw444 <wandersonrodriguesf1@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
To eliminate linker error and fix ims_rtp_daemon:
--------------------------------------------------
CANNOT LINK EXECUTABLE "/vendor/bin/ims_rtp_daemon": library "libavservices_minijail.so" not found: needed by main executable
This was long used to enable QC extended features. Right now,
with a pure AOSP BT stack, this is completely unused. Moreover,
it's enabled by default if devices opt-in for the QTI BT stack.
Change-Id: I0ad604d7a7a502df647676b1afc77d770fa50710
to fix error: build/make/core/base_rules.mk:329: error: device/xiaomi/sdm660-common/data-ipa-cfg-mgr/hal: MODULE.TARGET.SHARED_LIBRARIES.liboffloadhal already defined by vendor/qcom/opensource/data-ipa-cfg-mgr/hal.
Signed-off-by: etahamad <220190166@fa-hists.edu.eg>
Add 'wowlan_triggers=magic_pkt' to wpa_supplicant_overlay.conf. With
this, wpa_supplicant will tell the linux kernel that the wifi driver
is wowlan capable, and will wakeup the host when a magic packet is
received. Most importantly, the kernel will no longer disconnect wifi
connections before suspending wifi.
CRs-Fixed: 2615975
Change-Id: I3226943940046ad98e4ab410897d4fdcb457ee5a
* From LA.UM.9.6.2.r1-03300-89xx.0
To eliminate these errors:
--------------------------
CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "libdisplayconfig.qti.so" not found: needed by /vendor/lib/libwfddisplayconfig_proprietary.so in namespace (default)
CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "vendor.display.config@2.0.so" not found: needed by /vendor/lib/libwfddisplayconfig_proprietary.so in namespace (default)
