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
msm_irqbalancer was not starting for many targets. Call to start
irqbalancer was not getting initiated. Fix this by making a
call to start msm_irqbalancer.
Change-Id: I4fbdef032100c91dba7bdb48a3562c5f9ab38e4d
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
On high RAM targets, due to more anonymous memory availability,
we can improve headroom by increasing ZRAM swap size,
especially under memory pressure, and during background app compact.
Also ZRAM swap size is logical and is used when needed and
shouldn't cause other side effects.
Change-Id: I11949b8bdf16e9b4b8abb1bd633ffa1a1c0b1ad6
-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
CPU BW is set to 200Mhz in QC MTP, since on Pixel, we also adjust CPU BW
in touch PowerHint, we can relax the setting to 100Mhz.
Bug: 69271302
Test: boot
Change-Id: Iead3634d9c6fb0b3edc24ab0a19d62157a6a1793
Unclear if advantages are worth cumulative power draw.
bug 73364974
Test: boot taimen, memlat is powersave
Change-Id: I7b5eb176d0f22281e687b9577f5eedf311fb4a11
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
core_ctl's enable & disable nodes are differnt on different
kernel versions. Fix Disabling of core_ctl for msm8917.
CRs-Fixed: 2366575
Change-Id: Ide7fc5384b34e9e686fe686f9fd70aaaaffcc278
Currently if targets support ESOC there would almost certainly
only be a single instance of an external modem. Hence we can
simplify the esoc_link check accordingly without needing to do
a loop and grep. Choosing the external modem composition simply
depends on whether esoc_name is present.
Change-Id: Ib47e34fd31c3745a0c7b3568968f6f36681c98e7
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>
* 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
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
This has been deprecated for some time and will throw and
error in Android Q
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Change-Id: I9e4caaa6f401a051e5edd341112dcc01c8f040b7
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
* 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
