* As https://source.android.com/docs/security/features/encryption/file-based said emmc_optimized is a inlinecrypt flavor and can only be applied on emmc 5.2 device which has not been released yet
* Apparently Xiaomi 660 is launched with emmc 5.1 5 years ago and never met the 5.2 spec
* Now really enables inlinecrypt hardware by adding it in mnt_flags
* Use AOSP recommended inlinecrypt_optimized
* Use lazytime for reducing meaningless io
* Label metadata partition
(pix106) i use logdump partition for metadata, not cust
Signed-off-by: pix106 <sbordenave@gmail.com>
Kernels >4.7 will create a comp stream for each online CPU
and ignore /sys/block/max_compression_streams. This has been
backported to many 4.4 kernels as well.
Any device running a kernel with the upstream commit can safely remove
the parameter.
Upstream commit: 43209ea2d17aae1540d4e28274e36404f72702f2
Change-Id: Ibb29b54a31f0fb5bd941d7709d15d571dd77ebf5
Signed-off-by: pix106 <sbordenave@gmail.com>
Not supported on Android 13.
Upgrade from previous releases is working.
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Change-Id: I6654673964d4a9ede9f503242a8097fcc1678c3b
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>
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
In ueventd support has been added to read firmware path from
vendor.It wil parse /vendor/firmware_mnt/image information
and add in look up path/search path for loading firmware.
Change uid of /venodr/firmware_mnt back to system as kernel
firmware loading is removed. Previouly to support kernel firmware
loading root permissions were required.
Change-Id: I560ed75ee07626094acbc879b615190cf3a9faa3
Change fstab to mount dsp and firmware to /vendor/dsp and
/vendor/firmware_mnt.
Add classpath for firmware loading /vendor/firmware_mnt/image in
kernel command line.
Change-Id: I2dd2e7ea6334fb979ad8ff8c755648748de93ab4
Move persist entry to fstab and mount at /mnt/vendor/persist
Apply required user, group and permissions once persist
folder is created through __mount and parititon is mounted.
Run restorecon on /mnt/vendor/persist.
Change-Id: I20a16f3669bc7abf9844525c6ba0db1521a5a8e2
* Mounting /system and /vendor partitions is handled in kernel now,
however removing the entries from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
