Zoom seems to try using camera ID 2 for the back camera instead of
camera ID 0. Block access to aux camera for Zoom to force it to use
camera ID 0 for the back camera.
Change-Id: I99d79259a2a3adefb72a5ffed5fbbb37bd8b756d
The older VNDK 30 blob when linked against the newer default bluetooth
HW module, had a missing symbol:
`_ZN7android9bluetooth5audio25BluetoothAudioSession_2_132invalidOffloadAudioConfigurationE`
Since we build default bluetooth HW module from source, build
libbluetooth_audio_session from source as well.
Fixes: Bluetooth Audio on Android 12
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Change-Id: I13c09ecc37f709c575103d108acf5ca1b5aa2553
Apparently on AOSP builds, these nodes when read by the hals
with O_RDONLY attribute, need an elevated read permission, which
is apparently unneeded on mtk builds/stock rom.
This fixes video playback/OMX
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Change-Id: I7f358d0037de569a4eb038e5ac2a17b7651d307d
MTK has 15 volume steps, we have whatever is set in vc_call_vol_steps.
Mapping our range to theirs allows reaching higher volume levels.
A log curve is used to make gain transitions less abrupt at higher volumes.
Change-Id: I5f0e6467ba9fd0779d7e4abbf9f258b0b42224e4
* Refactor and cleanup code
* Use proper way of getting audioDevice with getPort().type()
* Stop mixing up values between AudioSystem and AudioManager,
as values between AudioManager (java) and AudioSystem (native)
could change and become different from eachother.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I2311ed02b88148b71b374b19aaaf458f82f23824
* My attempt at fixing in call gain control on MediaTek devices.
* It attempts to replicate what the stock MediaTek framework does
when controlling the volume of the earpiece speaker, since MTK's
audio HAL is not able to set the gain of the speaker from the
values sent by AOSP framework.
[LinkBoi00] Rebrand to Mediatek In-Call Service
Change-Id: I43f727f6fb73a0d38457a41a8361653d1d00e220
Signed-off-by: LinkBoi00 <linkdevel@protonmail.com>
- init services fail to setup encoders on boot and camera and
screenrecord fails to open video1 when trying to encode a video.
- While we may wanna consider looking through services that make use of
these devs and correct their groups for AOSP, this gets the job done
for now.
Change-Id: I0278efe201a9cbaa20c650fdc32bed6f9ecfd017
* Since Android 13, gralloc has been spamming the logs with:
E gralloc4: Empty SMPTE 2094-40 data
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Ib4d44443499f1396453bd7070aa1935485b329db
OSS counterpart works well, instead of using prebuilt blobs, use oss
where possible. This has no adverse effect on the audio quality.
Switch to OSS libaudiopreprocessing.
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Change-Id: Ia9163b6363c79dbdab86d7088946a1fc8b200596
Those keys will be embedded into VtsSecurityAvb on host side
instead, to verify the GSI image used on the device.
Bug: 149806769
Test: build and checks those keys are removed from
/recovery/root/first_stage_ramdisk/avb/
Change-Id: I8a002ba6f1421fb460056ccae6572050bdb0ce3c
