Use setMinSchedulerPolicy to enforce minimum thread priority
when accessing the audio HAL to ANDROID_PRIORITY_AUDIO
Test: instrumented
Bug: 261496726
Change-Id: I700b04d3060e9405b1445206882a6131cea0d045
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
* Google broke asn1 structs in 9211b80f1e
by changing types from long to int making the struct used by the blob mismatch new libcrypto
Change-Id: I8b110e9841bd9b50ea482aa98c0963567a69f6fc
* E init : Control message: Could not find 'android.frameworks.sensorservice@1.0::ISensorManager/default' for ctl.interface_start from pid: 516 (/system/bin/hwservicemanager)
Change-Id: I5a4feba0812bcbb187ef8a1c2298f799509e6c92
Updated audio policy by running:
hardware/interfaces/audio/7.0/config/update_audio_policy_config.sh \
device/samsung/sm7125-common/audio/configs/audio_policy_configuration.xml 6.0
with some manual intervention.
Change-Id: Iede32c176742e89577365341732a86f6ecaee514
* Due to config_powerDecoupleInteractiveModeFromDisplay we need to wait for the sensors sub HAL to re-start every time we fail a fingerprint unlock with screen off or on AOD.
* To prevent killing said overlay and having the touchscreen constantly enabled on AOD, we simply toggle the touchscreen on/off with every screen-off-UDFPS unlock
Change-Id: I819b9ef4387a914ccf17d7f4c6023ad08b3d14a0
* onFingerUp() would also be called during unlocking with Pin/Password/etc, always resetting the brightness to the previous value
Change-Id: I5319a8a50a4ad3308e787322c6c2a417b9169b23
This reverts commit 787989e7a4.
Test: build, flash and boot device with flag reverted.
Test: boot GSI with compressed APEX enabled.
Change-Id: I5988614cc055d565b17a5c8d830e35feb0e33e92
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
* Let framework handle the other ones
* On devices without hardware effects DOUBLE_CLICK effect is just
a single click without this
* Let's only keep CLICK and TICK if no hardware effects are supported,
just like AOSP default vibrator impl
Change-Id: Ib8bf299a417d82fe6196e1b071b5a7b2f9c3e5d8
* Use a script to swap check if we are in an A2DP phone call
* Use an app to check if we are in a VoIP or A2DP call and pass parameters accordingly
* Correctly route A2DP phone calls to the actual bluetooth device instead of earpiece and un-swap speaker and earpiece in VoIP calls
Change-Id: I1de8b2ed57b265b65cf619000e78e290c98e3d5c
Co-Authored-By: Ruchit <ruchitmarathe@gmail.com>
Andy Hung