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
Remove the old config_ims_package device config and configure the
new MMTEL and RCS configurations in Telephony instead. Also,
configure the RcsService to be the default RCS service.
Bug: 111305845
Test: make checkbuild
Change-Id: I0d709b8248f1c40f0a5b50ec799396706eeadd65
Fix reboot after 120 seconds on WLAN tethering enable.
Fix "target device is connected but no internet" issue.
Move ipacm-related sections from rootdir/etc/init.qcom.rc to data-ipa-cfg-mgr/ipacm/src/ipacm.rc
Make ipacm.rc look like vendor/qcom/opensource/data-ipa-cfg-mgr/ipacm/src/ipacm.rc but add
writepid /dev/cpuset/system-background/tasks to the service definition.
This let ipacm start after data decryption (it got killed on data decrypt and not respawned,
because was disabled).
This fixes following errors:
04-01 14:35:57.525 591 17586 W libc : Unable to set property "ctl.interface_start" to "android.hardware.tetheroffload.config@1.0::IOffloadConfig/default": error code: 0x20
04-01 14:35:57.526 2665 3190 I ServiceManagement: getService: Trying again for android.hardware.tetheroffload.config@1.0::IOffloadConfig/default...
04-01 14:35:57.526 591 17586 E hwservicemanager: Failed to set property for starting android.hardware.tetheroffload.config@1.0::IOffloadConfig/default
Set wifi.active.interface context to exported_wifi_prop and allow hal_wifi_default to set it.
I don't know why context definition was not embedded to the contexts file, but now it is.
This fixes following errors:
[163263.846522] selinux: avc: denied { set } for property=wifi.active.interface pid=2733 uid=1010 gid=1010 scontext=u:r:hal_wifi_default:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0
Signed-off-by: TheSync <repo-sync@outlook.com>
We are enabling software navigation bar using overlay. Thus, this is
not required. Not to mention, this causes SELinux denials as well.
[ 8.853895] selinux: avc: denied { set } for property=qemu.hw.mainkeys pid=1262 uid=0 gid=0 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0
Signed-off-by: Erfan Abdi <erfangplus@gmail.com>
Change-Id: I36473bb7b5e2c22cbc60b96d0fab0f4446314701
Cannot find entry vendor.qti.hardware.tui_comm@1.0::ITuiComm/default in either framework or device manifest...
Signed-off-by: Palakurthi Sreekanth <palakurthisreekanth995@gmail.com>
Reason for revert: Apparently qcom app randomly has issues
when not used in combination with qcom fm scripts.
Revert to AOSP app for now that is tested for a long time.
- It's loaded as app library, hence not needed to be a boot jar
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Change-Id: I1b1357be08b511f5af7663dee256849e2f2b1b63
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
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
TARGET_KERNEL_ARCH is a no-op unless it is different from TARGET_ARCH.
TARGET_KERNEL_HEADER_ARCH is also a no-op unless
it is different from TARGET_KERNEL_ARCH.
Change-Id: If64fb040c8ec61394e2657f13e51ff7a08519220
This block is completely redundant because..
- WITH_DEXPREOPT := true is the default
- WITH_DEXPREOPT_PIC is never read
- DEX_PREOPT_DEFAULT := nostripping has no effect when the
BOARD_USES_SYSTEM_OTHER_ODEX flag is set to true
Test: make
Change-Id: I618a1e395ca1a14555cd50eef1a4f1aa079b553d
Due to the API change for SearchManager to generalize
handle launching Assistant on both Phones and TVs alike.
25b0f41e84
Signed-off-by: Dybios <dibyajyoti.samal@gmail.com>
* Rules for persist_audio_file have been removed for legacy devices.
* Instead of labeling "/mnt/vendor/persist/audio", which is the default
path for audio calibration, label "/mnt/vendor/persist/factory/audio"
as this is where Moto devices store these calibration files anyway.
Change-Id: Ic27eb7f713e145a795cfec9de3c684fe9e2fc985
