* This reverts commit e33bb97d67493405b7fbbe31fd7cd60c158ed036 as it causes boot animation lags on Android 13.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I95d5051709803398d4d39fc767f5e8327efc2920
* The values set in commit 294f177 seem to still present quite
a lot of jank in the UI. Increasing them further to these values
have seemed to mitigate most of the jank.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I344448a7f4d8cdd9b0d410e40b110c5402007274
* Fixes:
07-25 15:31:45.325 0 0 I init : starting service 'batterysecret'...
07-25 15:31:45.336 0 0 F init : cannot setexeccon('u:r:batterysecret:s0') for batterysecret: Invalid argument
07-25 15:31:45.345 0 0 I init : Service 'batterysecret' (pid 6483) exited with status 6
07-25 15:31:45.345 0 0 I init : Sending signal 9 to service 'batterysecret' (pid 6483) process group...
Signed-off-by: Kuba Wojciechowski <nullbytepl@gmail.com>
Change-Id: I4c547a0162275a1fb99b1038f8bdd5b1f8632095
System properties set with the "=" operator cannot be overriden. This
device is used elsewhere in the system and some of the properties need
to be overridden. The "?=" operator will use the assigned value if no
other values are assigned elsewhere, allowing for overrides.
Bug: 230638462
Test: adb shell getprop | grep bluetooth
Change-Id: Id6cd7901555edafef141bbc1bbd5e06dc3a54d0c
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
