We do not have AdrenoTest.apk or SWE_Browser.apk so it does not make
sense to try to install them.
Change-Id: I0615e2e50526f960d5a6c221798ab5ebd1162d7b
5.4 kernel defaults to lzo-rle for zram. lzo-rle added run-length
encoding for lzo, which is beneficial to the use case of zram that
often has long runs of zero bytes. However, according to my testing
results, lzo-rle still has lower decompression throughput and higher
access latency compared to lz4. lzo-rle beats lz4 in compression
ratio, but most Xiaomi SM8350 devices have either 8GB or 12GB of RAM
where memory pressure hardly happens. Therefore, lz4's higher throughput
and lower latency is more preferable.
Now that I added LZ4_FAST_DEC_LOOP to the kernel lz4 module from
upstream lz4 1.9.x release, the decompression speed has increased
by another 10%, which leads further ahead lzo-rle.
Test setup:
- Disable swap on zram if it is enabled
$ swapoff /dev/block/zram0
- If you want to change the comp_algorithm after zram has been
initialized, reset zram first.
$ echo 1 > /sys/block/zram0/reset
- Set the comp_algorithm. For example, for lz4
$ echo lz4 > /sys/block/zram0/comp_algorithm
- Set up zram size
$ echo 4294967296 > /sys/block/zram0/disksize
- Make the swap
$ mkswap /dev/block/zram0
- Pre-fill zram with 1GB of real-word zram data dumped previously under
memory pressure. For example,
$ dd if=/sdcard/zram.test of=/dev/block/zram0 bs=1m count=1000
Random 4k read:
$ fio --readonly --name=randread --direct=1 --rw=randread --ioengine=psync \
--randrepeat=0 --numjobs=4 --iodepth=1 --group_reporting=1 \
--filename=/dev/block/zram0 --bs=4K --size=1000M
lzo-rle: read: IOPS=1547k, BW=6042MiB/s (6336MB/s)(4000MiB/662msec)
lz4: read: IOPS=1646k, BW=6431MiB/s (6743MB/s)(4000MiB/622msec)
lz4 fast dec: read: IOPS=1775k, BW=6932MiB/s (7269MB/s)(4000MiB/577msec)
Sequencial 4k read:
$ fio --readonly --name=zram_seqread --direct=1 --rw=read --ioengine=psync \
--numjobs=4 --iodepth=1 --group_reporting=1 --filename=/dev/block/zram0 \
--bs=4K --size=1000M
lzo-rle: read: IOPS=1816k, BW=7092MiB/s (7437MB/s)(4000MiB/564msec)
lz4: read: IOPS=1907k, BW=7449MiB/s (7811MB/s)(4000MiB/537msec)
lz4 fast dec: read: IOPS=2004k, BW=7828MiB/s (8208MB/s)(4000MiB/511msec)
Compression ratio from /sys/block/zram0/mm_stat
lzo-rle: 1048576000 -> 81969152
lz4: 1048576000 -> 86200320
zstd was also considered. It offers really nice compression ratio,
1048576000 -> 59899904, but the throughput and latency are so much
worse than lz4 and lzo-rle. It is probably more suitable for traditional
desktop/server swap setup with less aggressive swappiness value. It can
also help alleviate high memory pressure situation by compressing the
RAM to smaller size.
Starting with Android R launched devices, debugfs cannot be mounted in
production builds. In order to avoid accidental debugfs dependencies
from creeping in during development with userdebug/eng builds, the
build flag PRODUCT_SET_DEBUGFS_RESTRICTIONS can be set by vendors to
enforce additional debugfs restrictions for userdebug/eng builds. The
same flag will be used to enable sepolicy neveallow statements to
prevent new permissions added for debugfs access.
Test: build, boot
Bug: 184381659
Change-Id: I45e6f20c886d467a215c9466f3a09965ff897d7e
Since Ext4 doesn't implement "-o sync", it commits metadata at every 5 secs.
This may cause /metadata corruption.
Bug: 162883014
Change-Id: Icd38754bad1b1529d01165ea8c703c214d20bb4b
Build process errors out without this.
Traceback (most recent call last):
File "build/make/tools/releasetools/ota_from_target_files", line 2455, in <module>
main(sys.argv[1:])
File "build/make/tools/releasetools/ota_from_target_files", line 2429, in main
output_file=args[1])
File "build/make/tools/releasetools/ota_from_target_files", line 1103, in WriteFullOTAPackage
common.CheckSize(boot_img.data, "boot.img", target_info)
File "/home/aicp-dev/rom/lineage-17.1/build/make/tools/releasetools/common.py", line 1190, in CheckSize
p = info_dict["fstab"][mount_point]
KeyError: '/boot'
- also reformat and fix some fstab intendation
Change-Id: I30a396ea62e6e48420c0dd41533c156e90032929
- writepid command usage to join a cgroup has been deprecated in favor
of a more flexible approach using task_profiles. This way cgroup path
is not hardcoded and cgroup changes can be easily made. Replace
writepid with task_profiles command to migrate between cgroups.
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: Karan Parashar <whyredfire@gmail.com>
Change-Id: I0cdf63daa4eb043488a6d0eceb492af36df8882d
[ 4.526015] init: Command 'start vendor.hwcomposer-2-1' action=post-fs (/vendor/etc/init/hw/init.qcom.rc:85) took 0ms and failed: service vendor.hwcomposer-2-1 not found
- non-existing
- init: Could not start service 'nqnfcinfo' as part of class
'late_start': Cannot find '/system/vendor/bin/nqnfcinfo': No such file
or directory
Change-Id: I2ded3327ba721f629b7f5ea31d6861fed0e7c6c4
* As per the init.qcom.rc service defination has vendor prefix
* This Fixes:
I init : Command 'start rmt_storage' action=boot (/vendor/etc/init/hw/init.target.rc:161) took 0ms and failed: service rmt_storage not found
Signed-off-by: pri0818 <priyanshusinghal0818@gmail.com>
We don't have this file on the device
* init: Command 'rm /data/vendor/perfd/default_values'
action=post-fs-data (/vendor/etc/init/hw/init.qcom.rc:303) took 1ms and
failed: unlink() failed: No such file or directory
Signed-off-by: lupesoltec <dev@lupesoltec.com.br>
Fixes:
init: Command 'rm /data/vendor/radio/shmbus' action=post-fs-data
(/vendor/etc/init/hw/init.qcom.rc:278) took 0ms and failed: unlink()
failed: No such file or directory
Signed-off-by: Arturo <rtsanonynousperson@gmail.com>
* Since /persist is just link to /mnt/vendor/persist
* It fixes:
init: Command 'chown root system /persist' action=post-fs-data (/vendor/etc/init/hw/init.qcom.rc:285) took 0ms and failed: lchown() failed: Read-only file system
init: Command 'chmod 0771 /persist' action=post-fs-data (/vendor/etc/init/hw/init.qcom.rc:286) took 0ms and failed: fchmodat() failed: Read-only file system
Signed-off-by: Dede Dindin Qudsy <xtrymind@gmail.com>
init: Command 'mkdir /acct/uid' action=early-init (/system/etc/init/hw/init.rc:30) took 1ms and failed: mkdir() failed on /acct/uid: Read-only file system
Some banking apps read the file /proc/net/unix to
find out whether things like Magisk are installed/running.
To prevent that, chmod it 440.
This file isn't needed by any other process when boot is finished.
I've tested this and banking apps that did not work before
and recognized Magisk being installed now don't recognize
that and work just fine.
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: firebird11 <hbgassel@gmail.com>
Signed-off-by: Master <mhmdeveloperofficial@gmail.com>
Change-Id: I8f4c3ce55fe206786018ffba5e3301c52158a844
QC-time-servicesDaemon:Open File: /data/vendor/time/ats_3
QC-time-servicesDaemon:Unable to open filefor read
QC-time-servicesDaemon:genoff_post_init:Error in accessing storage
Since we no longer run FM2 app as system app, we need to change
permissions on /dev/radio0 to avoid failure reading the node when
the FM2 app is run as a platform app.
Change-Id: I172444c2cd08e0113ce07bc4dd629b7bd7c715bb
* Some users reported bootanimation lags and freezes
after a while. Looking from logs it fails to exit
once boot is completed. Stopping bootanimation
service, as workaround, is preventing this issue.
Signed-off-by: improbir <ghosh_probir@yahoo.com>
Signed-off-by: kssrao13882 <kssrao13882@gmail.com>
Eliminate drmdiagapp entries in init scripts. This app was deprecated
hence these entries were causing boot time degradation.
Change-Id: Ia8b14ef200a17b37c393f3e62c7be8849d575c71
- Our device doesn't have sscrpcd, so remove it from init.qcom.rc
fixes:
init: Could not start service 'vendor.sensors' as part of class 'early_hal': Cannot find '/vendor/bin/sscrpcd': No such file or directory
Change-Id: I54e93aaa5e76c168d515d626fb7f4f5e88d30f9f
