We used to add framework.jar to proguard via -systemjars option even
for the apks building againsd SDK. This was because the app might have
references to hidden APIs via static libraries, etc.
However, for vendor apks, the use of hidden API is strictly prohibited.
So it is fine to not include framework.jar. Furthermore, including
framework.jar even causes problems in some cases; if a java library
(e.g., android.hidl.base-V1.0-java) is statically linked to both the app
and the framework.jar, -systemjars frameworks.jar forcibly removes
classes in the library from the app to have references to the non-public
classes in framework.jar. This could fail some compliance tests.
Fixing the problem by not raising SDK for apks located in vendor or odm
partitions.
Bug: 128574081
Test: m
Merged-In: If2b658fead5b4bb4d8c023a37eb57a37ad9b741d
Change-Id: If2b658fead5b4bb4d8c023a37eb57a37ad9b741d
(cherry picked from commit eadd1bdb8e)
For OEMs that would like to include these fonts, feel free to include
them in product targets outside of this project.
Bug: 123701811
Test: make
Change-Id: I641477e24155e3e1c0a97f484a500aa155b1a9c4
am: 45fe4f22a4 -s ours
am skip reason: change_id I8228580879c6eb3d44a9111a6ed09b328df4a2c8 with SHA1 d89aacf6d5 is in history
Change-Id: I98ae69983a7223f5289589ab1e29116552969f6f
We have developed a vendor module and set LOCAL_VENDOR_MODULE := true<space> (Added a space character at the end)
The android build system then can't installed it in the right partition until we removed the extra space character.
bug: 129725067
Change-Id: I081ffe7f39a9c850007ba304c815436500be694c
adbd shouldn't be needed on the host in most cases
selinux_policy_system is a device PHONY_PACKAGE that will stop working
soon in PRODUCT_HOST_PACKAGES. I talked to jeffv and he's fine removing
it for now, adding back individual binaries if desired, or creating a
new host PHONY_PACKAGE.
shell_and_utilities_system is a similar device phony module. enh is fine
with it not being installed on the host by default for now, and we can
add them back as needed.
Test: treehugger
Change-Id: I1938f9f4ea5dbea2905baaf301473b617de9c530
Order of those doesn't matter, and the new order simplifies b/119800099.
Test: m and boots
Bug: 119800099
Change-Id: I9667a8d49ae751dfe713e37483548a58dfb25bd4
am: 23a8ddda67 -s ours
am skip reason: change_id I15ef7cb373ff249887f5641ca9c9722bfc3263a2 with SHA1 a13f3750f4 is in history
Change-Id: Iedd21af02587adfdd4b73466d30fe2e51bc36b62
For non-A/B, you must supply the --system-item-list, --other-item-list, and
--system-misc-info-keys parameters approrpriate for merging two partial target
files. Additionally, you must supply the --rebuild-recovery option to correctly
generate the filesystem config and file contexts. With all of these parameters,
the script will generate a merged target files containing the correct recovery
files.
Also fix the --keep-tmp option to be consistent with the other options.
Bug: 122813742
Test: verify that merged target image boots and can perform OTA.
Change-Id: I5a942ac0cd9924fec419a686794a2340304594c8
It is now in the Runtime APEX and considered internal there.
Test: Flash and boot
Test: atest CtsCompilationTestCases CtsBionicTestCases
Bug: 118374951
Bug: 124293228
Change-Id: I33bb9c238d7db46795deb592c9d20fe6591c1654
