The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the ~3.5 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save precious RAM on this
device.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
Signed-off-by: K A R T H I K <karthik.lal558@gmail.com>
Signed-off-by: chrisw444 <wandersonrodriguesf1@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
To eliminate linker error and fix ims_rtp_daemon:
--------------------------------------------------
CANNOT LINK EXECUTABLE "/vendor/bin/ims_rtp_daemon": library "libavservices_minijail.so" not found: needed by main executable
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
