needed for using EdgeTpu.
Due to this code goes to AOSP, please see CL details and test result in
b/289097511#comment24.
Bug: 289097511
Change-Id: Ie0969309346cd85b4bb8ac71860a529710c73345
While implementing the capo nanoapp for audio configuration, we met
some chre socket connected error due to the access group denied.
Add context_hub group for audio hal to connect chre socket.
go/capo-algo
Bug: 141128522
Bug: 149069556
Test: FULL build with audio hal part and local prebuilts nanoapp.
Test: Audio HAL communicates normally with CHRE socket.
Change-Id: Iea84411682f4c3e08f8b37a5b21818b0e9b04983
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
* time_daemon just refuses to work properly on mata.
Sony's TimeKeep, instead, does the job flawlessly,
so just ditch the former in favor of the latter.
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Change-Id: I54f50ed3d49efc2834d478781b15e6ee428a3062
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
Change-Id: I59c23e7974cea1174b0161f31a535fa3afa1e5c9
This time around with ZRAM size set to 75% of total RAM size,
as per Qualcomm Android GO Performance Tuning Guide.
Change-Id: I8f8362ccb5110fba6c5ed50b5d87a0b94a48e01c
writepid command usage to join a cgroup has been deprecated in favor
of a more flexible approach using task_profiles. This way cgroup path
is not hardcoded and cgroup changes can be easily made. Replace
writepid with task_profiles command to migrate between cgroups.
Bug: 191283136
Test: build and boot
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ibb56d2379c42e5ed4b2f15c1b04d5fb163b48678
* Stop handling cust and vendor mounting from kernel, first stage init is gonna do that, together with system (which is now /system)
* Use correct mount flags coming from kernel dts
* Move system, system_ext and vendor mount points to /dev/block/by-name/, we don't have bootdevice symlink to that point in init
* Copy fstab to ramdisk for first stage init
Change-Id: If8d75837f47c70f7ea02183bffaff233b4d6bb26
We are enabling software navigation bar using overlay. Thus, this is
not required. Not to mention, this causes SELinux denials as well.
selinux: avc: denied { set } for property=qemu.hw.mainkeys pid=1262 uid=0 gid=0 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0
Change-Id: I6f641bcde6b55ccc9a0ccad98b00de938d62d00f
Default to false if the property is not set.
Device init scripts will need to be adapted to restart
loc_launcher service when property change is detected.
Change-Id: Icbda789cd2a9a3391f437af2c07fc5127f2f09ab
* The APK is prepared to not run as system user
* Adjust /persist/alarm/data permissions accordingly
Change-Id: Ie24ccb3749d1dda2deb670cdb531e35d153034ed
Add power off alarm service for power off alarm feature to
reboot device when power off alarm is up in some special
mode like power off charging mode.
CRs-Fixed: 2095984
Change-Id: Ib8d82e63e92a85a7f60d5559064a1f19e0de5a22
[ 7.265723] audit: type=1107 audit(129718197.409:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=u:r:init:s0 msg='avc: denied { read } for property=persist.env.fastdorm.enabled pid=0 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0'
Properties which are related to the fastdormancy apk
are removed. Legacy fast dormancy code is obsolete and removed
all its instances.
CRs-Fixed: 2748503
Change-Id: I7a2bd24d78bb49765af59c933eca4503015b6792
If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.
This may cause memory pressure.
Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570
* Possible fix for for qcamerasvr not starting sometimes.
Signed-off-by: Kyle Peterson <kyle.peterson1@gmail.com>
Change-Id: Ia0e69e48f0e005d92e20647c7a8a19b02ad3ac75
- Our device doesn't have sscrpcd, so remove it from init.qcom.rc
fixes:
init: Could not start service 'vendor.sensors' as part of class 'early_hal': Cannot find '/vendor/bin/sscrpcd': No such file or directory
Change-Id: I54e93aaa5e76c168d515d626fb7f4f5e88d30f9f
