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>
* This script doesn't do anything useful, since it tries to set a lot of
ro.* properties, which is not allowed anyway.
Change-Id: I408cc17d0d18e81a9cf0e529e6b78622c3017a7f
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Removed NFC data directory creation to fix
vendor_init access denial issue.
NFC data directoty is already being created
by system core init.rc.
Change-Id: I7ebb88dc7b2df988a8af477baa81fe9253030ffb
To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
* starting rtpd on bootup without waiting for DATA_DAEMON
prop and restarting when property is set
Change-Id: If121089334ef2c0b335320bb561a553163042ba3
Starting imsrcsd on bootup without waiting for DATAD property
which will load libimsrcsbaseimpl and register HAL services
Change-Id: I17c1891583ea99baa31efec0e8ba316e4fbf25f3
hvdcp_opti daemon stores some parameters in
/mnt/vendor/persist/hvdcp_opti directory. Create the directory.
Change-Id: I0cf17467792cc294e6ce1a7f35a356cc0e960e86
Change fstab to mount dsp and firmware to /vendor/dsp and
/vendor/firmware_mnt.
Add classpath for firmware loading /vendor/firmware_mnt/image in
kernel command line.
Change-Id: I2dd2e7ea6334fb979ad8ff8c755648748de93ab4
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>
Changing permission for IOP from 0770 to 0700. This is to restrict the
access for iop database file.
Change-Id: Ic3325595521d4e433d0ce9bada564fc599cf858c
Move persist entry to fstab and mount at /mnt/vendor/persist
Apply required user, group and permissions once persist
folder is created through __mount and parititon is mounted.
Run restorecon on /mnt/vendor/persist.
Change-Id: I20a16f3669bc7abf9844525c6ba0db1521a5a8e2
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
