This reverts commit 64b507b1cf.
Additionally, stop using delays as that can cause audioserver to crash
Change-Id: If77eef84d04039b79ea1390dc81f89e5f01f354f
Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
* This allows us to get rid of TARGET_SPECIFIC_HEADER_PATH
and our custom camera provider for extra camera IDs
Change-Id: If7630fc11b117273cae78f26a3ba337823ac58b4
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
* Ensure users are always on the latest recovery image
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
Change-Id: I033ac4442622b737639d678993daf602a89f9bac
* The keydirectory and metadata_encryption flags for /data make lineage recovery improperly format it
Change-Id: I853b9c94c9bc0d295d393a3e820595ef99593583
*Remove treble flags, those are set by default
*Move fingerprint to device-specific trees
*Other minor fixups
Change-Id: I515e633cb571caabac19d87c5a7d93541fb30206
*Patch RIL again since Samsung changed prop names
*Update configs
*Update sepolicy for new blob updates
*dont allow rild and camera to access every prop, preventing log spam
*Also import Samsung's thermal HAL since health blobs now depend on it. Label it as hal_thermal_samsung_hwservice since hal_thermal_hwservice is a neverallow in health sepolicy
Change-Id: Ic6d699115c2e18f722b623e5a07e3a88e222f1f3
*Drop lineage FOD hal
*Uprev fingerprint hal to 2.3
*Update overlays for UDFPS
*Only light up the screen for 100ms when pressed since onHideFODView is in framework now
*Switch to TARGET_SURFACEFLINGER_UDFPS_LIB
Change-Id: Id7e0d9680a5b308d16e0e91ea6678089874e7d9c
device/samsung/sm7125-common/BoardConfigCommon.mk:201: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated
Change-Id: I863ac65b55105992e9a09267df90723da142d8e8
There's nothing really that different here when compared to the
common HAL except for the specific DT2W handling, which can simply
be supported as a power feature lib.
Change-Id: I59d039c500c672c50727aa715c256c9f55d98fa4
Simon1511