This was copied over from when Soong required us to define it in the
properties file, but this is the default and we also don't care.
Bug: None
Test: None
Change-Id: I35311093c83fddcb7c413535fbb50a126b615036
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
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
The lib is a part of the adbd apex and isn't used from outside of the
apex. Remove the lib from /system/lib[64].
Bug: N/A
Test: watch TH
Change-Id: I2c95fa72befa5a660a4f97d9f26459066b40c1e2
EDI collectors like VintfDeviceInfo and VendorApexDeviceInfo need to
access to VINTF information. Instead of directly accessing related
files, we expose processed VINTF via /system/bin/vintf.
Bug: 336577802
Test: /system/bin/vintf
Change-Id: Id2b2e9b905bcb168638c60c2dc92ca550ed1558f
With trunk stable, we no longer have multiple development branches, and
this flag is no longer in use.
Test: N/A (documentation change)
Bug: 308188056
Change-Id: Icdaddde9d107de9a453106cae35645b7e6cc21e9
One use case for this is to select go prebuilt apexes when building go
devices.
Bug: 338002385
Test: presubmits
Test: verified that this map shows up in `get_build_var
PRODUCT_RELEASE_CONFIG_MAPS` of a go device
Change-Id: I5505c581597bbd5a4e5f8fc6cd69987f67f0adb6
Enable go/perfetto-persistent-tracing for eng builds.
Bug: 325622427
Test: adb shell perfetto --query \
and check the tracing session 'sysui_persistent' started
Change-Id: Ic655eea67c96faf4fbc67bb1da3c359d50a73ccc
The MALLOC_SVELTE variable name is confusing, so add a new variable
name called MALLOC_LOW_MEMORY. Still support MALLOC_SVELTE.
Also, support the change of Malloc_not_svelte to Malloc_low_memory.
Test: Verified scudo config is used by default.
Test: Verfified Android GO config uses the jemalloc low memory config.
Change-Id: I2606205da746d8ab20e29884c7dcb5a77add51e4
The expanded list seems to be no longer required when using prebuilts.
Test: downloaded this CL in v-aml-prebuilt-dev
Test: lunch gsi_partner_arm-ap31-userdebug && m # no ninja analysis
error
Change-Id: I818191f36449032aee98879506c1e564fd0bc1b1
Compression factor, as discussed, should be a configurable build
property. This flag here will control that. From initial analysis, it
looks like 64k is a good default. go/variable-block-vabc-perf
Bug: 313962438
Test: th
Change-Id: I2bddede22655e36446e734ac1917be560b1a3a1b
Also dirty-image-objects-phone is removed as it's really never been
used.
Bug: 335369205
Test: build
Change-Id: Ib3eab3dc4c30aaa99b90310903bcc8a86a0f3480
- Fix the timestamp variable name.
- Convert the intermediate file name extensions to those in the
prebuilt directory.
- Disable check-abi-dump-list for sanitizer and coverage builds.
- Add an exception for libRS, RISC-V.
Test: m check-abi-dump-list
Bug: 333532038
Change-Id: I35b644feed1bef1e6c74731e8f69074bdc5b0352
The SDK finalization process will create APEX ABI dumps from this
target.
Test: make findlsdumps_APEX
Bug: 333532038
Change-Id: Iaec03bd39923678141b12436e5a6b8576e63a999
This reverts commit fa5bfb9d79.
Reason for revert: we were running into OTA failures b/333966507. The reason was that OTA compatibility tools on go/absign weren't updated with our v3 compatibility tools (which turns of v3 full OTA for devices launching prior to Android 15). Once we know that go/absign is updated, we can check in this change again
Change-Id: I789c24b57754d6ede794d7f9451ee0ca469c2fb4
The SDK finalization process will create APEX ABI dumps from this
target.
Test: make findlsdumps_APEX check-abi-dump-list
Bug: 333532038
Change-Id: I68d83616ef58aac2618e405a87b1909167b08d43
