Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
A dist build fails on a-only devices with retrofit dynamic partitions due to [1].
The check does not take a-only devices into account, even though they are capable of retrofit aswell.
While the PRODUCT_RETROFIT_DYNAMIC_PARTITIONS flag is used to detect and warn about misconfigurations, it does not seem to be needed for any retrofit functionality.
Hence, to avoid changes in releasetools, drop the flag.
[1]: 055b7692fb/tools/releasetools/check_partition_sizes.py (L185)
Change-Id: Ib0dfe4ee3da4c583d924d85a79d5ec37a2f9ba87
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.
Remove the definitions and related internal data structures and
value retrieving code of the following 3 CFG INI items, due to
they're not used to control any driver behavior any more.
-gVccRssiTrigger
-gVccUlMacLossThresh
-gEnableBypass11d
Ref: 3daaeeb4ea
Change-Id: I919bf191f48db4bf0947235ff804aed2b4b1bdb9
CRs-Fixed: 2352224
Signed-off-by: kssrao13882 <kssrao13882@gmail.com>
- This config was renamed as of CLO commit [1] and [2].
[1]: 10989ba376
[2]: 9ef1447db3
Change-Id: Ie6ffbeebb45e5dd97b98592b7dfc195a4fb7045d
Signed-off-by: kssrao13882 <kssrao13882@gmail.com>
Enable the persist.sys.fuse.passthrough.enable flag for the device
configuration to enable the FUSE passthrough feature.
This feature has been enabled on Cuttlefish, Wembley and Redbull devices for
months and no issues have been detected yet.
Bug: 168023149
Test: 'adb shell getprop | grep persist.sys.fuse.passthrough.enable',
ScopedStorageTest
Signed-off-by: Alessio Balsini <balsini@google.com>
Change-Id: I3f39b02af436f7e508bb70efc702565a667a051c
Changed “ro.ril.disable.power.collapse” value to zero.
Seems to be a debate on what value is more effective but after more reading and testing found that a value of “0” shows more improvement.
Have also added “ro.mot.eri.losalert.delay=1000 “ that helps smooth out disconnects and reconnects, saving battery.
Changed “ro.ril.disable.power.collapse” value to zero.
Co-authored by: KARTHIK LAL <karthik.lal558@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: popoA3M <pratyayaborborah@gmail.com>
Signed-off-by: EndCredits <endcredits@crepuscular-aosp.icu>
Could not decompress initial ramdisk image.
Booting to EDL
You can get dmesg from EDL, dump memory and read any HEX Reader, for example - GHex
This reverts commit c264973aa9.
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
* these prop should be accessed by init process from /system partition
I /system/bin/init: type=1107 audit(0.0:3): uid=0 auid=4294967295 ses=4294967295 subj=u:r:init:s0 msg='avc: denied { set } for property=persist.vendor.bt.a2dp_offload_cap pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:bluetooth_prop:s0 tclass=property_service permissive=1'
I /system/bin/init: type=1107 audit(0.0:4): uid=0 auid=4294967295 ses=4294967295 subj=u:r:init:s0 msg='avc: denied { set } for property=ro.hwui.render_ahead pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1'
Since Ext4 doesn't implement "-o sync", it commits metadata at every 5 secs.
This may cause /metadata corruption.
Bug: 162883014
Change-Id: Icd38754bad1b1529d01165ea8c703c214d20bb4b
android.hardware.media.omx@1.0-service: Service not available yet
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: popoA3M <pratyayaborborah@gmail.com>
* avc: denied { set } for scontext=u:r:vendor_init:s0 tcontext=u:object_r:vendor_bluetooth_prop:s0 tclass=property_service
* avc: denied { set } for scontext=u:r:vendor_init:s0 tcontext=u:object_r:vendor_bluetooth_prop:s0 tclass=property_service
Bug: 131149718
Test: Boot up and Turn On/Off Bluetooth
Change-Id: Ifd6bf0a35eafc2513901783b35deed45eed9dac6
