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>
Add support to set "ro.netflix.bsp_rev" property at run time
depending on the target. This is needed when 2 or targets are
binary compatible, but have different Netflix proprty for
device whitelisting.
Change-Id: I9484f2886a8b7d986c762fa9031c0e541f15c7e1
Update uventd rules to move new audio drivers to audio group.
Update init rc to move audio sysfs node to audio group.
Change-Id: I8e5230e04090b3555e32c0404401dddacea1cd15
* 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
Set USB default composition to 0x9091 having diag,serial_cdev,
rmnet,adb for 8909 with kernel 4.9.
Change-Id: I3066799d801bc9d8451b0d5a0bcd6d4055d1f735
* We don't support alarm_boot anyway, also
it's not getting set because of SELinux denial:
[ 7.243347] selinux: avc: denied { set } for property=ro.alarm_boot pid=556 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0\x0a
[ 7.243470] init: Unable to set property 'ro.alarm_boot' to 'false' from uid:0 gid:0 pid:556: SELinux permission check failed
Change-Id: Ia188bac2d2aa466c23dabd9dc50ee1f58e6ab7ee
* In favor of Low Memory Killer Daemon (lmkd).
* Adaptive LMK was also dropped quite sometime ago
making it useless to keep this script around.
Change-Id: Ie221d6f669d261bb871a77fed712b0df3f5ba248
* No matter how hard QC tried to improve these features, they still suffer
from stability issues, mainly due to the unpredictable nature of vmpressure
they rely on.
Change-Id: Icd14c79298a3c268abffa06ed17a79dececf423a
* When sys.use_fifo_ui is enabled, ActivityManager tracks the UI thread and RenderThread (the two most UI-critical threads) of the top application and makes those threads SCHED_FIFO instead of SCHED_OTHER. This effectively eliminates jitter from UI and RenderThreads; the traces that've gathered with this option enabled show runnable times on the order of microseconds instead of milliseconds.
* However, it should be enabled only when we have EAS i.e a capacity-aware RT scheduler because if RT load balancer is not capacity-aware, then there would be a 30% reduction in application startup performance.
Reference: https://source.android.com/devices/tech/debug/jank_jitter
Signed-off-by: Saurabh Charde <saurabhchardereal@gmail.com>
Signed-off-by: Aston-Martinn <advaithbhat9@gmail.com>
Change-Id: I8b55ad1899be985fc7357abaf06d68d6a130fb75
This patch will remove deprecated code for wpa_supplicant
which is creating symlink with system directory.
Change-Id: I95d1c61ab59addc04c1e7d462529bb9400bbfe92
CRs-Fixed: 2644788
Those values seem off. CAF maybe messed them up as those values look possibly wrong.
Those values are used as powerhint values on pixel 2 and 3.
Signed-off-by: Dusan Uveric <dusan.uveric9@gmail.com>
Change-Id: I1eebb1f57a7e91f26b9900cda65ec151b05ecbd7
* No matter how hard QC tried to improve these features, they still suffer
from stability issues, mainly due to the unpredictable nature of vmpressure
they rely on.
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Change-Id: I8256abb91b7e3160670ec45a22fdceeecc2a928c
Removing the check of 1GB RAM while enabling
low_ram target specific configurations to enable them
for 2GB RAM targets as well.
Updating ZRAM size to 75% of RAM for <2GB devices
Change-Id: I8d5341a4397cd20f2c59e7396801fcbea7fe5b73
Move the ADSP start KPI marker within the adsp-loader code instead
of adding the same in .rc file.
Change-Id: Ib67f5775dfb9fdca47e62a189de9994b7a6624e8
Fix reboot after 120 seconds on WLAN tethering enable.
Fix "target device is connected but no internet" issue.
Move ipacm-related sections from rootdir/etc/init.qcom.rc to data-ipa-cfg-mgr/ipacm/src/ipacm.rc
Make ipacm.rc look like vendor/qcom/opensource/data-ipa-cfg-mgr/ipacm/src/ipacm.rc but add
writepid /dev/cpuset/system-background/tasks to the service definition.
This let ipacm start after data decryption (it got killed on data decrypt and not respawned,
because was disabled).
This fixes following errors:
04-01 14:35:57.525 591 17586 W libc : Unable to set property "ctl.interface_start" to "android.hardware.tetheroffload.config@1.0::IOffloadConfig/default": error code: 0x20
04-01 14:35:57.526 2665 3190 I ServiceManagement: getService: Trying again for android.hardware.tetheroffload.config@1.0::IOffloadConfig/default...
04-01 14:35:57.526 591 17586 E hwservicemanager: Failed to set property for starting android.hardware.tetheroffload.config@1.0::IOffloadConfig/default
Set wifi.active.interface context to exported_wifi_prop and allow hal_wifi_default to set it.
I don't know why context definition was not embedded to the contexts file, but now it is.
This fixes following errors:
[163263.846522] selinux: avc: denied { set } for property=wifi.active.interface pid=2733 uid=1010 gid=1010 scontext=u:r:hal_wifi_default:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0
Change-Id: I735e7d8d8d07b9545ef16a6baa35a13aba3cd116
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
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
