*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
* The config has been removed since the centered display cutout
is now programatically detected.
This reverts commit e9cfa5e386.
Change-Id: I731fbf1d440024e0aacc3d8135790654abe0a795
- HW_ACCELERATED has been disabled by default as stated in the HAL
E EffectsFactoryConfigLoader: Error querying effect 7d1580bd-297f-4683-9239-e475b6d1d69f on lib offload_bundle
E EffectsFactoryConfigLoader: 1 errors during loading of configuration: /vendor/etc/audio_effects.xml
Signed-off-by: chandu078 <chandudyavanapelli03@gmail.com>
Change-Id: I58a16b5a488f0f452f9bf856fda35c086a34ef6b
Simon1511: Remove reading mode from livedisplay since setting config_setColorTransformAccelerated enables it in livedisplay
Change-Id: I790fdcb7c2dfd0e7ffbcd32345b2b1120c0c9d94
The way the fingerprint service handles FINGERPRINT_ERROR messages
allows for situations where the user can end up with HBM enabled even though enrolling threw an error.
Fix this by calling `onFingerUp()` when handling FINGERPRINT_ERROR
messages.
Change-Id: I7bb7d9054eb1eac412a05f63b3feb621ca21fe24
*We can now use kernel HBM instead of lighting up the whole screen
*Disable HBM when enrolling finishes and when authenticated to make sure HBM doesn't get stuck in enabled state
*Add a 35ms delay to make sure the screen dims before enabling HBM, preventing flickering
*Depends on d4e9440553
Signed-off-by: Simon1511 <simon2002.schoenmackers@gmail.com>
Change-Id: I330eb33a619e89a6744bca05edfe18fd30215e4a
* It is only used here and otherwise we end up with an autogenerated
rro for every package that includes SettingsLib
Change-Id: I8cfed8864a7d928707eb209acecd923209e4adf7
Simon1511: libsec-ril sets a prop (ril.dds.call.slotid) when in call with Sim1 or Sim2. Patch libsec-ril to make that prop vendor lable-able (vendor.calls.slotid). Then use that prop to check which Sim is currently in a call (0 for Sim1 and 1 for Sim2) and pass the arguments to audio HAL depending on that.
Note for later: Check whether passing [g_]call_state is really needed
Change-Id: I5a0dfd3b100287a2cf1ec3c156292487dc4da3d5
Supports to enable/disable USB data signaling
Bug: 161414036
Test: Pass USB V1.3 HIDL tests
Signed-off-by: Albert Wang <albertccwang@google.com>
Change-Id: Iffe00f8753206fb66cd3ab96cae5aa5ad9c410cd
Simon1511