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>
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
[clarencelol]: I'm not sure why it got removed before, it is not deprecated yet as Google still using it
Reference: https://android.googlesource.com/device/google/redbull/+/refs/tags/android-s-beta-4/fstab.hardware
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
Redmi Note 7 has variants with 3GB as well as for 4GB RAM.
So use 50% for ZRAM size instead of current 3GB for both.
Parameter 'max_comp_streams' is obsolete and should not be set.
Kernel currently uses always num of online CPUs.
Change-Id: Ib0157c7b4ba686a9597fd33d268dace4e0171da7
* Adjust with wayne-common
* Switch to standalone extract utils from pa
* Update FCM level to 3
* Move IR Blaster to device specific repo
Co-authored-by: Erfan Abdi <erfangplus@gmail.com>
Co-authored-by: Michael Bestas <mkbestas@lineageos.org>
Signed-off-by: OdSazib <odsazib@gmail.com>
Allow system permission for RPS sysfs nodes, so that cnss-daemon,
user space daemon can enable RPS(Receive packet steering) feature.
Change-Id: Iccebc347d959fc8ca35f28cb64e7bcf6b05f341a
CRs-Fixed: 2768237
Add rule to set permissions for the mhi_*_pipe_4 pipe that sends and
receives diag traffic to external chipsets. These nodes should have rw
access for the system group so the diag-router appplication can access
it.
Change-Id: Ia83ea035d248482790f70cbce7d42b86238ebd11
Google moved apex sessions directory from /data/apex/sessions to
/metadata/apex/sessions after commit:
"Move apex sessions directory to /metadata"
36cf4bbac6
Devices with a mounted metadata partition will have the needed
directories set up by system/core/rootdir/init.rc. Xiaomi devices
on sm6125 do not have a metadata partition out of the box, so things
like "Google Play system update" will fail to install the update.
Therefore, create a dummy directory under /data/vendor/metadata_apex
and symlink it to /metadata/apex.
The reason why the old /data/apex/sessions directory is not used
for the symlink is that apexd will call migrateSessionsDirIfNeeded()
to recursively copy things from the old directory to the new one.
Creating the symlink from /data/apex/sessions may result in
unintended behaviors.
Signed-off-by: OdSazib <odsazib@gmail.com>
Prefetching appears to have a slightly negative effect on boot time, and
actually makes boot time much worse when the available dm-bufio cache
shrinks. Since we anticipate the dm-bufio cache will shrink (because of
an increasing number of APEX dm-verity targets), disable prefetching
completely.
Boot time w/o this change: 12.085
Boot time with this change: 11.958
Boot time w/o this change with 128kB dm-bufio cache: 22.82
Boot time with this change with 128kB dm-bufio cache: 12.007
Test: atest google/perf/boottime/boottime-test
Bug: 136247322
Change-Id: I12e342c5692fa89855d9c217f2e94287ff5642a6
