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
The original CL was reverted because it references
enable_16k_pages_prop, which is only available on board API level >
202504.
This reland removes enable_16k_pages_prop usage, and worked around it by
reading PRODUCT_16K_DEVELOPER_OPTION at build time.
Test: reformat data as ext4, reboot
Bug: 293313353
Change-Id: Ibd8f57d1ef4fd2b0fd8b4170153d57fe9a9cefc2
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: I90e3bf5ecbdf6c058c56293cfba59c628ccc7aba
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
When a user opts into 16K developer option, we would need to convert the
/data and /metadata partition into ext4. Add necessary fstab entries for
ext4 so that zuma devices can boot on ext4.
This CL does not automatically switch existing devices to ext4, the
newly added fstab entries are intentionally marked as "non-formattable",
so that we don't accidentally format a wiped device as ext4. This CL
merely allows the device to boot if the /data partition is already
formatted as ext4.
Test: adb shell cmd recovery wipe ext4 , make sure device boots
Bug: 293313353
Change-Id: I3a2a2e9d09cdea884f58b509a06c6829938dc369
Add the flag "use_lassen_modem" for bp to do the same checking like
"USES_LASSEN_MODEM" in mk.
Bug: 330654744
Test: 1. lunch aosp_cheetah-trunk_staging-userdebug
2. m RilConfigService
Change-Id: I4ef0fe469e98fa6315896bbe8c422f741e207664
Placing the fips140.ko at the same level as other kernel modules makes
it easier for automation tools to handle all of them.
Bug: 331791671
Change-Id: Id6d978afbd18f98f2a07d418c405699885c05bf0
Signed-off-by: Qian-Hao Huang <qhhuang@google.com>
am skip reason: Merged-In I9f0d29ef69dc88cb8e876e37aac09ed7331c79b7 with SHA-1 f8c54e9912 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27046269
Change-Id: Ifa42ada09fb3d458c02ab9e9f4e3e582b9bc2969
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
