This was long used to enable QC extended features. Right now,
with a pure AOSP BT stack, this is completely unused. Moreover,
it's enabled by default if devices opt-in for the QTI BT stack.
Change-Id: I0ad604d7a7a502df647676b1afc77d770fa50710
to fix error: build/make/core/base_rules.mk:329: error: device/xiaomi/sdm660-common/data-ipa-cfg-mgr/hal: MODULE.TARGET.SHARED_LIBRARIES.liboffloadhal already defined by vendor/qcom/opensource/data-ipa-cfg-mgr/hal.
Signed-off-by: etahamad <220190166@fa-hists.edu.eg>
Add 'wowlan_triggers=magic_pkt' to wpa_supplicant_overlay.conf. With
this, wpa_supplicant will tell the linux kernel that the wifi driver
is wowlan capable, and will wakeup the host when a magic packet is
received. Most importantly, the kernel will no longer disconnect wifi
connections before suspending wifi.
CRs-Fixed: 2615975
Change-Id: I3226943940046ad98e4ab410897d4fdcb457ee5a
* From LA.UM.9.6.2.r1-03300-89xx.0
To eliminate these errors:
--------------------------
CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "libdisplayconfig.qti.so" not found: needed by /vendor/lib/libwfddisplayconfig_proprietary.so in namespace (default)
CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "vendor.display.config@2.0.so" not found: needed by /vendor/lib/libwfddisplayconfig_proprietary.so in namespace (default)
Since Android 10 blobs are being used, org.codeaurora.ims still runs
as phone UID as seen by these denials:
m.android.phone: type=1400 audit(0.0:2914): avc: denied { read } for name="u:object_r:qcom_ims_prop:s0" dev="tmpfs" ino=13660 scontext=u:r:radio:s0 tcontext=u:object_r:qcom_ims_prop:s0 tclass=file permissive=0
m.android.phone: type=1400 audit(0.0:473): avc: denied { call } for scontext=u:r:radio:s0 tcontext=u:r:hal_imsrtp:s0 tclass=binder permissive=0
Change-Id: Ic8c1b7996b9e0e7b63ba2a153441c9e8467a8a31
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
* +Adding some props also
When device is in Enforce mode, this happens:
---------------------------------------------
E init: Do not have permissions to set 'persist.radio.VT_CAM_INTERFACE' to '2' in property file '/vendor/build.prop': SELinux permission check failed
As example, so, moving those props to system/build.prop (from vendor/build.prop) fixes the issue.
Test: adb logcat -b all -d *:E > logcat-err.log and check for any init props related errors
Fix: Enforcing the Device Tree
Allow system permission for RPS sysfs nodes, so that cnss-daemon,
user space daemon can enable RPS(Receive packet steering) feature.
Change-Id: Iccebc347d959fc8ca35f28cb64e7bcf6b05f341a
CRs-Fixed: 2768237
Add rule to set permissions for the mhi_*_pipe_4 pipe that sends and
receives diag traffic to external chipsets. These nodes should have rw
access for the system group so the diag-router appplication can access
it.
Change-Id: Ia83ea035d248482790f70cbce7d42b86238ebd11
This change yields considerable SQLite performance gains. It
should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Signed-off-by: Jesse Chan <jc@lineageos.org>
Signed-off-by: DennySPb <dennyspb@gmail.com>
Change-Id: I50d9b3d9f019772fedc7066675249116d5e441e4
These tell the ROM to use the correct Adreno drivers which fixes graphical artifacts.
Credit to Sultan for the triple buffers prop.
Credit to kdrag0n for noticing vulkan prop was missing.
Change-Id: I3481092f3aea2be2091c8c64ca04c426a244a696
Co-authored-by: Lunarixus <Nathan@lunarixus.party>
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
