Bringup Xiaomi Mi 9T (davinci) to 20.0 from 17.1#234
Bringup Xiaomi Mi 9T (davinci) to 20.0 from 17.1#234GarciaLnk wants to merge 2 commits intoDivested-Mobile:masterfrom GarciaLnk:master
Conversation
Previous supported version was 17.1
Superseded by 20.0
| #4GB+ (2GB+) | ||
| sed -i 's/zramsize=.*/zramsize=50%,max_comp_streams=8/' google/redbull/fstab.hardware google/sunfish/fstab.hardware oneplus/msm8998-common/rootdir/etc/fstab.qcom oneplus/sdm845-common/rootdir/etc/fstab.qcom xiaomi/sm6150-common/rootdir/etc/fstab*.qcom &>/dev/null || true; | ||
| sed -i 's/zramsize=.*/zramsize=50%,max_comp_streams=8/' google/redbull/fstab.hardware google/sunfish/fstab.hardware oneplus/msm8998-common/rootdir/etc/fstab.qcom oneplus/sdm845-common/rootdir/etc/fstab.qcom &>/dev/null || true; | ||
| sed -i 's/zramsize=.*/zramsize=50%,max_comp_streams=8,zram_backingdev_size=512M/' xiaomi/sm6150-common/rootdir/etc/fstab.zram &>/dev/null || true; |
There was a problem hiding this comment.
why have both zramsize and zram_backingdev_size?
There was a problem hiding this comment.
I'm just respecting the device tree changes, zram_backingdev_size seems to enable zram writeback with a 512M limit.
Alternatively, the sed regex could be changed to keep additional changes and only modify the values of zramsize and max_comp_streams if that's the intent of the patch.
| fi; | ||
|
|
||
| if enterAndClear "device/xiaomi/davinci"; then | ||
| smallerSystem; |
There was a problem hiding this comment.
The system partition in davinci is 3.5 GiB large, so I don't see why the system image would need further reduction. I have used DivestOS in davinci in the past up to 19.1, without using smallerSystem, and I haven't faced any issues.
|
Thank you for this, I'll merge this after I get the August ASB out for 20.0 after Lineage merges it. |
|
Merged, thanks! A davinci 20.0 build should be up on the server in a few minutes. edit: it is up |
2 participants
Builds but it needs testing, let me know before publishing if you decide to merge this.