Google moved apex sessions directory from /data/apex/sessions to
/metadata/apex/sessions after commit:
"Move apex sessions directory to /metadata"
36cf4bbac6
Devices with a mounted metadata partition will have the needed
directories set up by system/core/rootdir/init.rc. Xiaomi devices
on sm6125 do not have a metadata partition out of the box, so things
like "Google Play system update" will fail to install the update.
Therefore, create a dummy directory under /data/vendor/metadata_apex
and symlink it to /metadata/apex.
The reason why the old /data/apex/sessions directory is not used
for the symlink is that apexd will call migrateSessionsDirIfNeeded()
to recursively copy things from the old directory to the new one.
Creating the symlink from /data/apex/sessions may result in
unintended behaviors.
Signed-off-by: OdSazib <odsazib@gmail.com>
If two recording apps both select the primary input with
fast flag, second app will fail to start because the hal
doesn't support two inputs with the same use case if input
can't be reused since of the limit of primary input's max
open count.
Add the dedicated profile for “low-latency-record” to make
the first input can be reused if possible.
CRs-Fixed: 2550228
Change-Id: I233bd3eaf614b195df0a41402747f496d3a56b44
* The mediametrics packages are part of the AOSP media stack already.
* libavserviceextensions is not available in Lineage.
Change-Id: Ia05789b6d59ad04e236b20155ac8b9575b0bdab1
Cannot find entry android.hardware.graphics.mapper@3.0::IMapper/default in either framework or device manifest.
Cannot find entry android.hardware.graphics.mapper@4.0::IMapper/default in either framework or device manifest.
b/71936484 has audio accessories failing to connect
when there's a transition to suspend when they're attempting
to enumerate.
Avoid this problem by increasing autosuspend delay
from the default 2s to 7s.
The longest I've seen a device take to enumerate after
vbus is ~3 seconds, this gives a 2x margin.
Test: booted on Walleye, saw no more messages:
[ 472.412555] c0 5675 msm-dwc3 a800000.ssusb: DWC3 in low power mode
between device connection and enumeration.
Bug: 71936484
Change-Id: Ie585f2ce5dec429510cc6c00452dc4d49f1372a0
There is no evidence that Qualcomm devices running a rather recent IMS
stack need to include AOSP RCS packages. RCS already worked before this
change and continues to do so, but the main goal was to get rid of some
of the RCS related log spam, which was accomplished here.
Change-Id: I219546e29d288373877e9bcd194a60ef5e09f224
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
QCOM's driver can support a max of 512 scan results. Ensure that
wpa_supplicant is in sync with that number.
Bug: 74724482
Test: Device boots up and connects to wifi networks.
Change-Id: I62dbd2bd3789c454e9683320d3a58f67019ea7ee
