am skip reason: Merged-In I7582ba278abcb30cebe041f775efe45633a58bad with SHA-1 82bb1a5112 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27555815
Change-Id: I6987b6972a4afa8958e54879bfcaaad2362946e4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I7582ba278abcb30cebe041f775efe45633a58bad with SHA-1 82bb1a5112 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27555815
Change-Id: I82ad8f2cbd2af63d183af86c30924e70b0a54f38
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit establishes a soong config variable `sim_count` for
easier converting Android.mk to Android.bp when dealing with multiple
SIMs.
Bug: 343823190
Test: presubmit
Change-Id: I93d355e30771868f1c4664eebbce579e1e37cdcb
Previously, we rely on mount points to copy files out of
efs partitions. Switch over to dump.f2fs to read directly
from block device without mounting. This allows us to copy
files out of efs partition in both 4K and 16K mode.
Test: Boot dev option enabled ext4 device
Bug: 340965747
Change-Id: I9d3f3d5200adc31f13298488b5be068b0fe7c7f4
This reduces the amount of computation needed on critical
boot path for F2FS devices. Boot time is expected to improve
with this patch.
Bug: 341216848
Test: boot device with ext4 and f2fs
Change-Id: I7311a22a7bf9773d3909656d98cc578a43cb9477
am skip reason: Merged-In Ifd5f1b609c0bf5fa98677f9880bfa29496add95d with SHA-1 45b0145f0c is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27270053
Change-Id: I3ff1268af0f6cf0a7a236b8151770d6e7a3670a8
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Products using 16KB kernel may wish to boot into 16KB mode
directly. To do this, these targets would need to use ext4
as their default fs type for /data and /metadata . Add
a build time flag which would install ext4 fstabs.
Test: th
Bug: 339337171
Change-Id: I53de1599bbff583b45ca2bf6d3e3efb83957913e
Common fstab entries(everything but /metadata and /data) are
moved to a separate fstab file.
This allows us to create an ext4 variant of the same fstab later.
Test: device boots
Bug: 339337171
Change-Id: I3129551c98b14473c776f2cf3dee1b81fc0c84b3
V12 is not frozen yet. We should still allow V11 for `next` build.
Test: trigger test build
Bug: 309897479
Bug: 303162192
Change-Id: I14582a51cde66698013b275ec1d668f858ad7cba
Signed-off-by: Leo Chen <yinchiuan@google.com>
Since /persisit was previously mounted during eraly-init stage,
this CL delays the /persist mount to post-fs-data stage.
Actions which depends on the /persist partition are also moved.
Bug: 319335586
Change-Id: I6bcc775f16331905c6896f3a2ec5bbea9e20744f
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e
Revert submission 26822004
Reason for revert: Potential culprit for b/339099720- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:26822004
Change-Id: Ie9598a3b3b56c8ce26f475079798c44314696f44
Revert submission 26822004
Reason for revert: Potential culprit for b/339099720- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:26822004
Change-Id: I744fccbf1aacd817ca1a0c6f4a121393307c8797
Since /persisit was previously mounted during eraly-init stage,
this CL delays the /persist mount to post-fs-data stage.
Actions which depends on the /persist partition are also moved.
Bug: 319335586
Change-Id: I0e70f672b9a5f4b05b95dd30b0a74bb8f91f399a
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: I4c4024b4cad18199226f5644f98254b2230574d6
