Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
* For some magical reason, the naming (and not just associations)
matter as of a few days ago - no clue why.
Change-Id: I6cf12b455dbf460a9be607d796af3536093e8427
Checking stock dubai boot image it has recovery there and not vendor_boot,
so to keep things similar let's do the same here
Change-Id: I86e89ec97a8ce9b4f71705ed526093f37f4331e6
* requires old libprotobuf in system_ext, which doesnt exist anymore
causing this linker missing symbol:
_ZN6google8protobuf8internal14AddDescriptorsEPKNS1_15DescriptorTableE
also: what does qccsyshal do anyway?
Change-Id: Ibb7c8983ae243e67fdd8a8714a79d7b5766aef4f
Nothing changed on common tree, just device... but before
the "Hey, Marc you didn't update common tree" comments start?
this is why.
Change-Id: Ic69284cc69118c52d0c0cc77550055d46db8a526
This applies the following tools/extract-utils changes:
* Allow overriding VENDOR with VENDOR_COMMON
Change-Id: Ib78643a3e6a648e21362b6a1fdc3581d41954700
For now this is implicitly built by lineage specific
libprotobuf-cpp-lite-3.9.1-vendorcompat lib, but in the future this
might not be the case.
Change-Id: I724e933e046cbf631c078321d55550b96ca998da
This reverts commit 55772d45005910e6764c0b457e840f1cc85f1f71.
Reason for revert: Brought to my attention that this is way too broad. Agree.
Change-Id: I3e2fec355960844d2af8af3212780245fc53d66b
(cherry picked from commit 5cd03a02dcc34e31fe40c15ec9c7217b66089234)
Newer netmgrd breaks VoWiFi on Jio and possibly other carriers.
Change-Id: I9fe4798333387bfe5ac18183d3533ee44d267ce5
(cherry picked from commit 189c1e5729f67e3868cc5167a4a75e147c567dc3)
The new folder structure now looks like this:
device/qcom/sepolicy_vndr
├─ legacy-um (meant for sdm845 until sm8350)
├─ sm8450
└─ sm8550
SEPolicy.mk placed in the root automatically redirects devices to the
proper subfolder.
Change-Id: I4ed1a06af779909d64172da294c4a99a3ae9ba0d
* Seems to be an issue where if modemst1/2 (efs) is wiped modem only looks for fsg to rebuild efs in the root_directory.
* Even though this isn't correct it should allow radio to be easily flashed during future firmware upgrades as the stock radio.img is a container which flashes fsg/modem then passes the command to wipe modemst*
Signed-off-by: Andrew Hexen <SyberHexen@gmail.com>
Change-Id: Ic7acabbe16d66740b3aee414be60c24d3a0de43d
* Already set dynamically via init and the property here is blocked by sepolicy anyways, but if one were to boot permissive this would point to a non-exist file crashing media.
Signed-off-by: Andrew Hexen <SyberHexen@gmail.com>
Change-Id: I1951084243b7fa0f697210c353abedbae2ec86a1
* original bringup on 19.1 this did exist but no longer seems to be the case.
Signed-off-by: Andrew Hexen <SyberHexen@gmail.com>
Change-Id: I09998c24652faab76ce0cb58b74e65d3a87295a8
Required after recent kernel update. Based on QCOM commits:
liblight: set "timer" trigger before setting delay for blinking
display: light: set timer trigger before updating delay_on/off values
display: light: clear timer trigger before setting brightness
Change-Id: Iaa4d78fe7411f299ba866de174782c269c068c23
* W libc : Unable to set property "ctl.stop" to "ril-daemon": error code: 0x20
* W libc : Unable to set property "ctl.stop" to "vendor.ril-daemon": error code: 0x20
Change-Id: I80784cb3d6ee3cf539b3a8b5dbcada2e8b850641
This reverts commit e63d405d36b99660806ef278dd4909373b031a7b.
Reason for revert: Need to rework kernel side.
Change-Id: I5edfb82b02a63ab068dfe87878bc2be7edb197b1
Bootloader sets ro.boot.revision, we can use this to show
"Hardware version" in model information in Settings.
Change-Id: Id2d825f60f792e6d05c0b34cfee811a0ac3b5604
