This is meant for platinum tests that require device
signing. They will be migrated out of device-tests.zip
Test: presubmit
Bug: 341719739
Change-Id: Ie30c4bedc2edf4f537deb49099d0e23b4eec2626
Certain applications, like tracking the dependency chain of modules,
knowing the "required" dependencies is required.
In this context, "required" here means the `required` field in
Android.bp files.
Bug: 339193439
Test: Inspect module-info.json for the `required` field
Change-Id: I09977bf71a0a0ae46ea9268ce1faa5c90673bb7a
Apprently target-specific variables are only valid for the body of
the target, not its dependency list, so the dependency on the zip file
wasn't being added.
Bug: 340392832
Test: m, rm file_list.txt and the zip file, m again, and ensure we don't get an error that the zip file doesn't exist
Change-Id: Idaca6606ff24055aa98c78ca1206b587cc1df4d2
This reverts commit d17ef4a30b.
Reason for revert: build breakage on sdk_goog3_x86_64-trunk_staging-userdebug
Change-Id: I884df8b07afbbcdc1e07930163108f0baa503014
This reverts commit 1cbd8211e7.
Reason for revert: Droidmonitor triggered revert due to breakage in b/341118115
Change-Id: I0fed4225bd1d4d8888334fdc2a9fac353b748edd
This reverts commit 3f0eba2bdc.
Reason for revert: Causes build flag changes to be ignored sometimes. Better fix is in progress.
Merged-In: Ic85be1da3765656cef8da4ec03d0b1ca7d5d625e
Change-Id: I2c06770b2ff86c69a5de89962ab9bf48bedfe6fe
With our version compatibility check, overriding our cow version no
longer works. Updating this check to only apply if a command line
vabc_cow_version is not specified.
NOTE: the ota may not successfully apply, depending on device if we
override the cow version
Test: th
Change-Id: Ibbed6cf94cc2e91597d0c249dc8ade314b8341a2
Low memory devices place special emphasis on memory constraints and cpu
utilization. We want to expose a set of build configurations that allow
these devices to fine tune resource usage during OTA installation.
Our strategy will be the following.
1. For any tunable needed in first stage init, read the .ro prop during
ota installation, propogate the configuration to SnapshotUpdateStatus
proto, then read the property from /metadata upon first reboot (since
.ro properties are not available here)
2. For tunables which aren't needed until second stage init, read the
.ro prop directly.
This first CL will just add the build configurations to the build
system. Subsequent CL's will forward the configs to protobufs and
snapuserd daemon
Bug: 332255580
Test: th
Change-Id: I31b36b42f8fba997c772fe1a4ba99b17128b3eca
I changed the installs file to be after Android.mk files in
aosp/3080639, in order to minimize the information given to Android.mk
files. But it appears that some exotic vendor builds actually rely
on this information (when they shouldn't).
Bug: 340254841
Test: diff'd out/target/product/<vendor>/installed-files-vendor.txt before/after this cl, and with a revert of aosp/3080639
Change-Id: I00a06fe984397e4dba57352850f5e2484d17f657
Framework already has nano protos, and reusing them won't
introduce extra dependencies for the apps
This is setting up the resources flagging in the framework
Bug: 297373084
Test: Built with related changes
Change-Id: I518bd56f56c42e0adef0002e95f8948e0904fb43
