Start loc_launcher as gps user and set uid/gid of loc_launcher
to gps and enable SETUID and SETGID caps for loc_launcher, so
that we can start loc_launcher as gps user instead of root and
still have capabilities for SETUID and SETGID. Also remove not
required permissions groups for loc_launcher.
Change-Id: Ie9f1506874b3c3148f9170c8d5db9afd1e70025c
CRs-Fixed: 2192881
To support ODL to read data from QDSS, create a custom group
and set permission of byte-cntr device. And also set
permission to coresight-tmc-etr/block_size to enable
byte-cntr feature.
Change-Id: Ic80156667dd7511392d5970ddcbd0fdc43ffffca
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
* To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in go/treble-sysprop-compatibility documents.
Test: succeeded building and tested on a sailfish device.
Bug: 36796459
Change-Id: I48e6ee0ae3fe401e39efb273256d991fac676357
Treble compliance.
Bug: 70228425
Bug: 70393317
Test: complete wifi test in b/70393317
Test: Test wifi on Taimen and Sailfish
Test: verify sockets exist in /data/vendor/wifi/wpa/sockets
Change-Id: I0bfc3a351419f0a03498e79664949f353369bf1b
-dpmQmiMgr permissions are updated with radio group
to communicate with QMUXD socket.
CRs-Fixed: 2183993
Change-Id: I37195ffc6602d009ac4cace6c742484e70a768ec
Issue: cameraserver or camera-provider service is not able to
write pid's to cpuset/camera-daemon.
Solution:
1) Increased the cpu to 0-7
2) Moved camera-daemon folder creation from on-boot to on-init.
CRs-fixed:2200628
Change-Id: Ifc80c09ae09b353b3c8a0603f14e5ff4206d6796
File based logging is writing to sdcard, this is not supported.
By default qxdm is required, removing the file based logging.
Change-Id: I7fa1748c0ff3eb594dc7d4c59eb69c0ae9ef7756
This will let the wifi hal run as "wifi" user and not need root
permissions to access this path for firmware reloads.
Bug: 33435250
Test: Compiles.
Change-Id: I84a38cea5e0f729147c3191c3485a3738d7838ef
power_off_alarm is a vendor service. Add vendor prefix to it.
Change-Id: Ib4a988467a54bbe4544960180afeeeb5dd0e85f3
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
While IRQ balancing is generally a good idea, MDSS and KGSL
are critical for UX and shouldn't be migrated between cores.
Change-Id: Ic8ae88f5ea75715f3cd6bfec118380f65ea9e4d1
The package 'org.codeaurora.qti.nrNetworkSettingApp' is a priv-app, and
uses the MODIFY_PHONE_STATE permission. This permission needs to be
whitelisted for the package. Otherwise, a CTS failure will occur.
Change-Id: Iedfce95014b97deb55f24a98233000e552e4d518
CRs-Fixed: 2341511
Adding com.skyhook.blp into whitelist to avoid it being killed by
doze. Also adding INTERACT_ACROSS_USERS permission to be able to
run as single user.
Change-Id: I245965c87e7a5029eb8a308af24484d64a3fcb87
CRs-Fixed: 2294320
* Sadly, out-of-the-box Miracast support was killed in P, so
we need this to keep Wi-Fi display feature working.
Change-Id: Id680d918b64c0e3733251db45992ec477b6fbdfb
