The old way of creating RFS symlinks was preventing all Qualcomm targets
to build hermetic partitions. All devices should now be able to drop
BUILD_BROKEN_INCORRECT_PARTITION_IMAGES flag for good.
Change-Id: I95076d884ab3c3d46b3875e77b9088f6df895c31
- Required by qcom.trustedui and qcom.eid
Change-Id: I3dfbab252ea539bdacac67a75e5d8a9b7d889ad0
Signed-off-by: Jyotiraditya Panda <jyotiraditya@aospa.co>
[1] - This is present in media hal, the same for kona and lito.
Change-Id: I45024dab5cea5686e46dda65ee1dd7af340cc5b7
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
As 16K alignment is not a mandatory requirement in Android 14,
opt out of it by setting PRODUCT_MAX_PAGE_SIZE_SUPPORTED := 4096
Change-Id: I1555e39dc1c0127b8dd77928d1f09ad37a051395
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Define ro.product.property_source_order to
"odm,vendor,product,system_ext,system".
Build/product properties like
ro.build.[description|display.id|product],
ro.product.[brand|device|manufacturer|model|name] and
ro.build.fingerprint would be picked up from the partitions
in the above defined order.
Change-Id: If5e7a1e627723623d04b88adda6bb60bb1e6dd84
This reverts commit f91588987f.
Reason for revert: Rethinking this, qssi isn't actually
inheriting this and this config would not be used from here.
Change-Id: I242ebc997b3951826e5e1da93e0c198516570011
Despite AOSP design, Qualcomm still relies on vndservicemanager
even for devices shipping API 30 and higher. They build vndservicemanager
for all targets and we should too.
Change-Id: I4d6d8d58b55744aa4fff694af6a2adad3783983d
[1] - Why are they in system if it is copied to the vendor?
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Change-Id: If130c5ac9f7de819abb0f6d3f7317d09bf7a50ab
[1] - Now we have Pixel 6 here, which doesn't use any Qualcommon,
so let's move it to the appropriate place.
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Change-Id: I6027e8a0664a60de6b5d32e7cf98b8843088cf32
This was working fine for us because of the way we inherit
QCOM common, but was not working for other ROMs
that inherit it from device.mk.
Change-Id: If7e640bde5fd7e6c72c55d17470168aba3cb6a9e
* We need the board platform for various makefiles we include
and for kernel version guards, just require it outright in
top level.
Change-Id: I1100b2c731e4d5cc8f522641b6ea60e83ec29908
* Add in a script of our own to set product ID since
QCOM's default is SOC based, e.g. KONA-MTP _SN:XXXXXXXX.
Change-Id: Ieede136b5dd8903dcfe2f41f59d5278df7b02ee6
* Only pick up product makefile if it exists, some
vendorless devices may be opting into all components.
* Move BoardConfigWlan flags here as CAF's tries to
include kernel modules that don't exist and this
is a better solution than touching all of their
BoardConfigs.
Change-Id: I16d49283f754e2c3dd1743ca85f3e625e8496e8f
* Only pick up product makefile if it exists, some
vendorless devices may be opting into all components.
Change-Id: I3b564a20637c8a1ca4b4e54d829201d0d51f2561
Bruno Martins
chrisl7
Jyotiraditya Panda
Cyber Knight
Omkar Chandorkar
Jake Weinstein
BladeRunner-A2C
Roopesh Nataraja
padarshr
Adithya R
Vishalcj17
Kuba Wojciechowski
Alexander Koskovich
SayanAcharya