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
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
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>
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>
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
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
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
* 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
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
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
