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>
* Pictures shot with Aperture are >80mb per pic, so switch back to Camera2 until we figure out whats wrong
Change-Id: I75c285ae7807659e20cd0f2757da0e4f21ad80b9
* Ensure users are always on the latest recovery image
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
Change-Id: I033ac4442622b737639d678993daf602a89f9bac
* 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
This has barely any effect on audio.
This reverts commit 0528e6d2ed.
This reverts commit fc62df5b70.
Change-Id: I376eee348ad59201f767f301edf9b6ee722d389b
Text below fod was overlapping and going under the fod icon. This fixes it by moving the text lower.
Change-Id: I5655d75467a8b443e63aa0505ef982864daf566b
* 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>
APM would fail to parse the config anyway:
E DevicesFactoryHAL: loadAudioInterface couldn't load audio hw module audio.a2dp (No such file or directory)
W DevicesFactoryHalHidl: The specified device name is not recognized: "a2dp"
E AudioFlinger: loadHwModule() error -22 loading module a2dp
W APM_AudioPolicyManager: could not open HW module a2dp
Change-Id: Iaa1be881cfe8f8474cef0ba46e1b0a62b59e14be
LuK1337