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
Set USB default composition to 0x9091 having diag,serial_cdev,
rmnet,adb for 8909 with kernel 4.9.
Change-Id: I3066799d801bc9d8451b0d5a0bcd6d4055d1f735
* 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
* In favor of Low Memory Killer Daemon (lmkd).
* Adaptive LMK was also dropped quite sometime ago
making it useless to keep this script around.
Change-Id: Ie221d6f669d261bb871a77fed712b0df3f5ba248
* No matter how hard QC tried to improve these features, they still suffer
from stability issues, mainly due to the unpredictable nature of vmpressure
they rely on.
Change-Id: Icd14c79298a3c268abffa06ed17a79dececf423a
* When sys.use_fifo_ui is enabled, ActivityManager tracks the UI thread and RenderThread (the two most UI-critical threads) of the top application and makes those threads SCHED_FIFO instead of SCHED_OTHER. This effectively eliminates jitter from UI and RenderThreads; the traces that've gathered with this option enabled show runnable times on the order of microseconds instead of milliseconds.
* However, it should be enabled only when we have EAS i.e a capacity-aware RT scheduler because if RT load balancer is not capacity-aware, then there would be a 30% reduction in application startup performance.
Reference: https://source.android.com/devices/tech/debug/jank_jitter
Signed-off-by: Saurabh Charde <saurabhchardereal@gmail.com>
Signed-off-by: Aston-Martinn <advaithbhat9@gmail.com>
Change-Id: I8b55ad1899be985fc7357abaf06d68d6a130fb75
This patch will remove deprecated code for wpa_supplicant
which is creating symlink with system directory.
Change-Id: I95d1c61ab59addc04c1e7d462529bb9400bbfe92
CRs-Fixed: 2644788
Those values seem off. CAF maybe messed them up as those values look possibly wrong.
Those values are used as powerhint values on pixel 2 and 3.
Signed-off-by: Dusan Uveric <dusan.uveric9@gmail.com>
Change-Id: I1eebb1f57a7e91f26b9900cda65ec151b05ecbd7
* No matter how hard QC tried to improve these features, they still suffer
from stability issues, mainly due to the unpredictable nature of vmpressure
they rely on.
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Change-Id: I8256abb91b7e3160670ec45a22fdceeecc2a928c
Removing the check of 1GB RAM while enabling
low_ram target specific configurations to enable them
for 2GB RAM targets as well.
Updating ZRAM size to 75% of RAM for <2GB devices
Change-Id: I8d5341a4397cd20f2c59e7396801fcbea7fe5b73
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
Set ADB as the default composition for GVM targets, as DIAG
over USB conflicts with the DIAG over IP used by the PVM.
Change-Id: I09389564db284b16ccb34243eaf34bb17860b30f
Signed-off-by: Anant Goel <anantg@codeaurora.org>
- 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
- SnapdragonVoiceActivation feature for Far Field Voice version
affines its threads to 0-3 CPUs and so prevent them from isolation
for qcs605 target
Change-Id: I09ef5cc97ee245133315edc0821f3a2afc54e99b
ZRAM compression uses the linux slub allocator its internal data
structures. If these internal data structure consume a lot of memory,
ZRAM compression may increase memory usage, rather than decrease it
as expected. Decrease the chance of this occuring by ensuring the
SLAB_STORE_USER debug option is disabled.
Change-Id: I4684feda94b7bebacb6218b7f979c95771b0ee10
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
check populated dm-* nodes and Update read_ahead_kb
values to them. This is needed because on targets
with verity disabled dm-0 to dm-6 are populated,
while on enabled targets dm-3 to dm-6 are populated.
Change-Id: Ia4e262d7487120695db53b562b5764598fd40a87
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>
This change makes 90DB (interfaces: diag,dun,rmnet,dpl,qdss,adb)
as default usb composition on bengal.
Change-Id: If83a356219f802e8960c7d341296f3a7b3641e68
CDSP subsytem uses rpmsg to send CPU L3 clock requests via cdspl3
governor. Use cdspl3 as the governor for CDSP L3 devfreq node for
serving CDSP L3 clock requests.
Change-Id: I49ad421811affa82458abd34d0a0851e1f1fc423
Adding cases for sdmshrike to enable clocks
for APPS Power collapse.
Change-Id: I089556c1098d60022bdb3de1ec2024858f0d3b30
Signed-off-by: Nitesh Kataria <nkataria@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
