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
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>
Prefetching appears to have a slightly negative effect on boot time, and
actually makes boot time much worse when the available dm-bufio cache
shrinks. Since we anticipate the dm-bufio cache will shrink (because of
an increasing number of APEX dm-verity targets), disable prefetching
completely.
Boot time w/o this change: 12.085
Boot time with this change: 11.958
Boot time w/o this change with 128kB dm-bufio cache: 22.82
Boot time with this change with 128kB dm-bufio cache: 12.007
Test: atest google/perf/boottime/boottime-test
Bug: 136247322
Change-Id: I12e342c5692fa89855d9c217f2e94287ff5642a6
We dont need you at all
05-28 19:19:49.428 0 0 I init : Command 'rm /data/vendor/lct_diag/client_*' action=post-fs-data (/vendor/etc/init/hw/init.qcom.rc:371) took 0ms and failed: unlink() failed: No such file or directory
Signed-off-by: Manish4586 <manish.n.manish45@gmail.com>
Change-Id: I1d25b638e9385494f7ce883bab71ddab480559e0
All this does is to disable msm_core and set the
polling_interval to 0, which makes the driver useless.
We can achieve the same result by disabling the driver.
Change-Id: Ic19c505ed74811a3d1b76703255af3aa5cb37bf9
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Signed-off-by: Subhajeet Muhuri <subhajeet.muhuri@gmail.com>
Signed-off-by: OdSazib <odsazib@gmail.com>
Add support to set "ro.netflix.bsp_rev" property at run time
depending on the target. This is needed when 2 or targets are
binary compatible, but have different Netflix proprty for
device whitelisting.
Change-Id: I9484f2886a8b7d986c762fa9031c0e541f15c7e1
Update uventd rules to move new audio drivers to audio group.
Update init rc to move audio sysfs node to audio group.
Change-Id: I8e5230e04090b3555e32c0404401dddacea1cd15
* This is manually ported by me from Lavender tree on Corvus-Devices
* Thanks @StyloGey for reviewing the java code and giving me a better solution
* Original repo: https://github.com/Corvus-Devices/device_xiaomi_lavender.git
To get it working, you need these two commits in your kernel:
> c04d6d6e61
> 8e25ac3318
Signed-off-by: OdSazib <odsazib@gmail.com>
Change-Id: I1bb48ced1f23728daa2e5170647ce08a04347110
* We don't support alarm_boot anyway, also
it's not getting set because of SELinux denial:
[ 7.243347] selinux: avc: denied { set } for property=ro.alarm_boot pid=556 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0\x0a
[ 7.243470] init: Unable to set property 'ro.alarm_boot' to 'false' from uid:0 gid:0 pid:556: SELinux permission check failed
Change-Id: Ia188bac2d2aa466c23dabd9dc50ee1f58e6ab7ee
This patch will remove deprecated code for wpa_supplicant
which is creating symlink with system directory.
Change-Id: I95d1c61ab59addc04c1e7d462529bb9400bbfe92
CRs-Fixed: 2644788
Move the ADSP start KPI marker within the adsp-loader code instead
of adding the same in .rc file.
Change-Id: Ib67f5775dfb9fdca47e62a189de9994b7a6624e8
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
Change-Id: I735e7d8d8d07b9545ef16a6baa35a13aba3cd116
As it turned out, allowing background, system-background, restricted,
foreground and top-app to use all 8 cores results in severe jitter and lag
whenever background tasks are running, whether it be on boot, or during waking up
from sleep.
This commit readds pinning background to cores 0-1, system-background and
restricted to cores 0-3, foreground to cores 0-6 and top-app to cores 0-7.
Change-Id: Idb76879e75e05b437600f0b689c260c674eb7eea
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
During bootup the device first enumerates in ADB only composition
and then falls back to the persist.sys.usb.config.
Prevent this enumeration in ADB only composition during bootup
by setting the sys.usb.configfs from init.qcom.usb.rc
Change-Id: I4d9aa8454202b8118ff76dfda7f44c6413c42020
The restorecon_recursive directive in init is only applied if the
file_contexts file changed between builds, but not necessarily if any
file or folder inside /mnt/vendor/persist/ has changed.
The restorecon code checks whether an xattr named
"security.sehash" contains a string that matches the current
combined hashes of the SELinux context files and skips restoring labels
if there is a match, see
https://android.googlesource.com/platform/external/selinux/+/refs/tags/android-9.0.0_r35/libselinux/src/android/android_platform.c#1546
Force wiping that xattr so that restorecon always runs since it's not
very expensive (there are currently only about 50 files on /persist).
The restorecon is needed to fix issues such as wrong stock labels on
/mnt/vendor/persist/sensors/:
sensors_persist_file -> persist_sensors_file
Change-Id: Ic0cd848836ee550499d9236f56ed6e939e35f01e
- Grant SYS_NICE capabilities to audio HAL processes as sound trigger
HAL threads need to run at real time priority as well as use the
CPU affinity, for far field voice.
CRs-Fixed: 2359951
Change-Id: Ie0da744978609c750e92aec2c6001ace1868ad31
Qseecom needs to start at earlier stage for FBE to work properly.
* Wait for prop moved to device as we have still oreo qseecom devices with different prop name
Change-Id: Ie2408f652df291ad6a1b0dee1e4d559ff35c7c45
Signed-off-by: Ramandeep Trehan <rtrehan@codeaurora.org>
/dev/wigig_sensing is the entry point to an SPI kernel driver which is a
part of a remote sensing solution using 60GHz HW.
Change-Id: I1b538e0c58ae784997407f91a7647c2188ee7d58
0x9020 composition includes DIAG + ADB + DUN + NMEA. Add support
for the same.
Change-Id: I364d4e87b63d7e5dfb394db6e92e650764b7cc96
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
The interface line in hostapd_fst is the same as the
default hostapd service and this can cause the lazy
HAL mechanism to start hostapd_fst instead of the
default hostapd, causing various errors.
This change only fixes the errors with default hostapd
operation. In order to fix FST feature with hostapd_fst,
additional changes are needed such as making it use
the default hostapd service and adding sepolicy rules
to support it.
Change-Id: I133336b1ae18fa823969f240b3e4376989fbf017
/dev_sp_nvm is used by sp_iar_lib to store CMAC values for spu
firmware and application
Change-Id: I2ac5f29b66448a526cdbc6a1ccefd5f80066c170
Signed-off-by: Li Li <liil1@codeaurora.org>
/vendor/firmware_mnt/verinfo/ver_info.txt ownership
is now system,system. Hence need to add system group
for init.class_main.sh
Change-Id: I9c759c22aca7a8c5bc04908748f26916025c7b07
CRs-Fixed: 2534121
Configfs triggers will now be in the core
init.recovery.rc, similar to main system
files.
Test: Usb works in recovery
Bug: 78793464
Change-Id: I26a403425edce1d4947daf2510e28beb026ba5f6
As per treble rules, this is no longer allowed from within
vendor init. At the same time these folders are long deprecated,
so drop them and get rid of the SELinux denials.
Change-Id: I47d25bcf92dcc16b7b112b7b1257cd3e66fee57b
Add iuicc0 and iuicc1 devices that can be opened
by spdaemon to create iuicc0 and iuicc1 channels
respectively and interact with iuicc0 and iuicc1
applications respectively on the Secure Processor.
Change-Id: I2554616073553065416756e23c3e27f2f9c90021
-IMS service is no longer using /data/shared path.
-remove unused /data/shared path access.
CRs-Fixed: 2526160
Change-Id: I072d0b922a48880d45f7c85ac3569b2cec3d7250
add wakelock group and BLOCK_SuSPEND capabilities to vendor.sensors
to acess wake-lock sysfs nodes
Change-Id: I193836d097f15f5bfbe1645909ae70f3f870f972
Allows earlier interaction lock release by polling on display updates to
stop happening (becomes idle) for a programmable amount of time.
Bug: 62110101
Test: Ran UiBench, didn't see regressions
susbset of tests - avg-jank:
testInflatingListViewFling: 0.09
testTrivialListViewFling: 0.15
Change-Id: I83c0fc75a3d7ca5bf76910ebbaeddb69343a7ee2
All this does is to disable msm_core and set the
polling_interval to 0, which makes the driver useless.
We can achieve the same result by disabling the driver.
Change-Id: Ic19c505ed74811a3d1b76703255af3aa5cb37bf9
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Signed-off-by: Subhajeet Muhuri <kenny3fcb@gmail.com>
Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
Add move_wifi_data service from /data/misc/wifi to
/data/vendor/wifi for OTA update.
Change-Id: I134fb663d1f358028eebb80106634d6eb0b87bc0
CRs-Fixed: 2270608
In ueventd support has been added to read firmware path from
vendor.It wil parse /vendor/firmware_mnt/image information
and add in look up path/search path for loading firmware.
Change uid of /venodr/firmware_mnt back to system as kernel
firmware loading is removed. Previouly to support kernel firmware
loading root permissions were required.
Change-Id: I560ed75ee07626094acbc879b615190cf3a9faa3
CarrierSwitch use a new solution from P or later. the new solution
switch carrier by a standalone apk instead of modifing the init.rc
code in old solution.
So, Remove init.rc changes for old carrier switch solution.
Change-Id: I2da9861d71bc73df1b19066d2fad0dd3f4dedb3e
CRs-Fixed: 2377064
VtsTrebleSysProp test cases fail if the
sys.mtp.device_type is unset. Set the property to
value 2 so that the device appears as a phone on the
host PC.
Change-Id: I1123ca808cf027d6d787c58f58133b6ce67af4de
Signed-off-by: PainKiller3 <ninadpatil100@gmail.com>
Grant capabilities and change file permissions to allow the sensors.qcom
daemon to start up as the system user/group, rather than running as
root.
Fixes: 63775281
Test: monitor logcat after reboot, confirm no file open errors. Run
QSensorTest, confirm all sensors provide sane data. Confirm that
IMU calibration can read + write its saved settings. Run sensors CTS.
Change-Id: Ib80ea21900d6af6cd34c82c4a63f50c7e0ac18ff
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
* Restart HIDL camera provider to cover some edge cases where camera isn't
working on FDE devices with boot pin enabled.
Change-Id: Ia757e9d07de26008f426fca582439d68b6d6fecb
Signed-off-by: Albert I <krascgq@outlook.co.id>
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
* For some reason, booting with headphones plugged in results
in a broken speaker output if FDE secure boot is enabled.
* Restarting audio HAL after decryption seems to resolve the issue.
Change-Id: Ie14b89841bf811f0fb09edb0a04fd28aafecde87
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Increasing the tcp_rmem is not sufficient to achieve higher rates
for TCP downlink as all sockets in the system are still bounded
by the core socket rmem_max.
CRs-Fixed: 2351198
Change-Id: I198457745a9e48f0098457e86e7d9523c6249cbd
- all vendor init services should be prefixed
with vendor
- radio.atfwd.start -> vendor.radio.atfwd.start
persist.radio.atfwd.start -> persist.vendor.radio.atfwd.start
This property is now qualified as a platform property and is not
whitelisted. Therefore it must be renamed to continue to be
used as a trigger.
Change-Id: Iebb0eed75f7ac6f71085ac12cf2a3e7414defb09
CRs-Fixed: 2223094
As per sepolicy, add vendor prefix to specific properties.
i.e, persist.vendor.sys.ssr.enable_debug,
persist.vendor.sys.mba_boot_timeout,
persist.vendor.sys.modem_auth_timeout,
persist.vendor.sys.pil_proxy_timeout.
Change-Id: Ibeb87194e2ca9b831fc5e721a87764920c21276d
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
Creating new directory as persist Bluetooth addr
location is changed from /persist/bluetooth to
mnt/vendor/persist/bluetooth.
Change-Id: Idb30dcd9d0af5f9271955e4c7eeff0bd9afe80ad
CRs-Fixed: 2324749
On android P, vendor persist folder is in /mnt/vendor/persist/.
Change time persist foler to /mnt/vendor/persist/time.
Change-Id: I325dfa2ed336d9ae0a2b5850ec3683db205a513c
* 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
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>
* 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
