This patch enables zram-writeback job. It will run idle marking
at 60m since the device is boot. After that, it will do first
writeback after 3hour to sweep initiallized cold pages out.
After that, it periodically write out every 24hour.
Bug: 117682284
Bug: 127185055
Test: confirm with manual testing
Signed-off-by: Randall Huang <huangrandall@google.com>
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I6b8f537faf2ffff1a93170aad763f2be4dcaba42
Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.
Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537
* "32-bit overflow" CAF mentioned in the function wrapper inside post-boot
script sounds very bs, since if it's 64-bit it won't be affected anyways
* We do the setup using fstab instead to allow setting up more flags such
as setting up backing device and compression streams; as such kanged from
Pixels
* zRAM size = 50% physical memory size to satisfy what CAF really wants
* Use LZ4 compression even for regular devices
Signed-off-by: Albert I <kras@raphielgang.org>
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Ia6efb3d28e56fb026d9b28fc6633b2eac77dfa47
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'
Change-Id: I30a396ea62e6e48420c0dd41533c156e90032929
init : Command 'mkdir /firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:31) took 0ms and failed: Not a directory on /firmware
init : Command 'mkdir /bt_firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:32) took 0ms and failed: Not a directory on /bt_firmware
init : Command 'mkdir /dsp 0771 media media' action=early-init (/vendor/etc/init/hw/init.target.rc:33) took 0ms and failed: Not a directory on /dsp
Signed-off-by: orgesified <me@orgesified.ml>
Change-Id: I129f6fd9210076fffa1912e3dd6dcec32bd5acf6
* /data/tombstones and /data/vendor/tombstones are both created by
the system's init.rc.
* Creating /tombstones at the root isn't allowed since the root is
a ramdisk and mounted read-only.
Change-Id: I04586994280ae48f36542f56e1cace422943376b
This should be done earlier:
libprocessgroup: Failed to open /dev/cpuset/camera-daemon/tasks: No such file or directory: No such file or directory
libprocessgroup: Failed to apply CameraServiceCapacity task profile: No such file or directory
Change-Id: I9edbdad2e764667a4624b181e0426f14ed9be616
* Remove unused/duplicated parts
* Make changes to do without other scripts
Co-authored-by: Demon000 <demonsingur@gmail.com>
Change-Id: I8e758337488dc19ecb47ec1b583fba33ef05882d
Remove deprecated symlink directories, and remove
services that are not present in our system or vendor.
Change-Id: Ia07d472657f1303bf3ee1b8da36ac43ecc218d17
Common config.fs/$TARGET_FS_CONFIG_GEN AID/fs configuration
file for all chipset inheriting from base.mk.
Since legacy device-specific android_filesystem_config.h and
config.fs do not co-exist, temporarily include config.fs only
if legacy file is absent. Once all legacy, device-specific
files have been deleted, config.fs can be made unconditional.
Change-Id: Ie100d0cd9db808b82d99be7139f0709390c7f3a2
The product abstracts configs that need to be set to support updating of
APEXes.
Bug: 130418467
Test: m
Test: adb shell getprop ro.apex.updatable in Pixel 2 and 3
Test: adb shell /system/apex/com.android.apex.cts.shim.apex exists.
Change-Id: Id5aa944ceba6a6846308f1c18a08af8b3bb38589
This enables casefolding, which is required for removal of sdcardfs.
Test: Wipe data and boot. lsattr /data/media, check for +F
Bug: 138322712
Change-Id: I020aa6bb9c121e7bda83c07bc9fb37dcfa26702c
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save precious RAM on this
device.
Change-Id: Ic2f9edd811879e3f18876a508273a9544d8a23e0
This change yields considerable SQLite performance gains. It
should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Change-Id: I541709fc771d4b501b56b8555e5e8a04486d0293
[dereference23: Take values from curtana-user 11 RKQ1.200826.002 V12.0.4.0.RJWMIXM release-keys]
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: I4153efdbd5ac95a32607d8aba1b6bbbdb02765c0
On builds where A/B support is enabled the system image acts as the
rootfs. In this case we can no longer create the non-hlos image mount
points at run time as we used to. We now create them as part of the
build itself.
Change-Id: I30d98f7c50fca3ce7117b9b8d87150655bb5b440
Add AVB flags to compile recovery image
as a chained partition. This is required
for safe OTA when multislot support is
not present.
Change-Id: I1115eba4038e6fcaa61440846a25861366996ed4
Signed-off-by: Volodymyr Zhdanov <wight554@gmail.com>
* AVB's `--flags 3` argument builds a disabled VBMeta with
disabled hashtree, so no need to set both flags individually.
Change-Id: Ibe9ee322a5af58f13e76d53e18dee49451fe8838
Partitions that use vbmeta_system can be found by looking at
avb flag in fstab from boot ramdisk.
--flags 2 makes the verification function of avb always return a
positive result.
--set_hashtree_disabled_flag builds the vbmeta images with the
HASHTREE_DISABLED bit set and as a result they don't need to manually
disable dm-verity via e.g. 'adb disable-verity'.
The rest of the configuration is taken from
https://source.android.com/devices/tech/ota/dynamic_partitions/implement#avb-configuration-changes
Change-Id: I381feef8f6fefc8449ca50d85d704b67bcc8a77e
