* Due to the way newer TWRP versions are behaving, our relatively small
persist partition gets overfilled with recovery logs very quickly.
* Let's just remove the recovery cache from persist on every boot to be sure
that we always have enough space for anything that writes to persist.
Signed-off-by: EsromTech <esromgalaxy5@gmail.com>
Add changes to not create fingerprint directories in
init.qcom.rc. It will be done in fingerprint module
init script.
Change-Id: If199cf875bb4201fcda923b0e8162b06d8d93d1a
GPS components make use of DR_SYNC pulse generated by GNSS
hardware, which was received through pps device, hence
require permission for reading this device
Change-Id: I00bd3b8aa88059fb94338b6ba1d107d77c06a5e0
CRs-Fixed: 2299356
* init: Command 'start gralloc-2-0' action=late-fs (/vendor/etc/init/hw/init.qcom.rc:55) took 0ms and failed: service gralloc-2-0 not found
Signed-off-by: Ashwin R C <ashwin2001achu@gmail.com>
Change-Id: Ic444c7c683ab94b9a37e7d100cde19485db651b9
* Adapt the service from configstore-hal-1-0 service
to vendor.configstore-hal for AOSP P
* Resolves surfaceflinger first launch crash
due to configstore not being running earlier enough
Change-Id: I5aae6d8357ce71933e7c6673e9e4d37adb55a6af
As property service is part of init, and if init is busy with built-in
command e.g. fsck, the propety_set() won't go through until the built-in
command is finished.
Move the start of hwservicemanager earlier and wait for its done after
launches bootanim and its dependencies (there is not wait time during
boot but the command is as a safeguard).
Bug: 74437368
Test: boot with simulated long fsck and bootanim shown early
Test: boot see 'start_waiting_for_property("hwservicemanager.ready", "true"): already set'
Change-Id: Iab4b857a51e0e6b8b059d063c1f0d65a0e987622
* Set page-cluster to 0 as the incremental cost of reading 1 page at a
time is negligible for zram
Change-Id: Ia73d08904551dfc8d57268fc4da3f9f34d10e277
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Revert "potter: Adjust mkdir of time data files"
This reverts commit d52dd9094aab10b5d6640ebd1cba56a66ba847db.
Change-Id: I5d2e4a0849223b07bf060ec3c75c32f76710f672
Usb HAL expects data/power role switch to be supported if these are writable.
Despite our hardware can support the functionality, it does not seem to be properly implemented.
Change ownership of /sys/class/dual_role_usb entries to
system/system to allow USB HAL to access them.
Change-Id: Ie6d968180d55647813904970370dbb74012326b0
ag/3332074 broke the Pixel Logger funtionality for wifi.
The Logger needs the write permission for /data/vendor/wifi/cnss_diag.
so, parent directory needs to set the execute permission for other group.
Test: manual test with Pixel Logger
Bug: 70228425
Change-Id: I75819f0b0bf4ed376d5d87f33af2e1693c864db8
Signed-off-by: Ecco Park <eccopark@google.com>
Low level shutdown is triggered after SystemServer is
cleaned up. sys.shutdown.requested is private to SystemServer
and is used to syncrhonize the shutdown process if SystemServer
crashes before hardware reboot is complete.
Native daemons must use low level shutdown indication from
powermanager for their graceful shutdown, if they wish to stop
before init terminates the process.
Change-Id: Ia583f7dce6f1927d9b766fdc132f082b409f4d67
Signed-off-by: kubersharma001 <kubersharma001@gmail.com>
Sensors registry file ownership is retained even after OTA
upgrade and that file is only accessible by daemon belongs to
same ownership permissions.
Change-Id: I3543733232aeab04d14fb9d69f635c1e6c6df1e2
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: I7f54b478de898491e32560d5a37657ac370bf893
Change fstab to mount dsp and firmware to /vendor/dsp and
/vendor/firmware_mnt.
Add classpath for firmware loading /vendor/firmware_mnt/image in
kernel command line.
Change-Id: I04bd18336a1259a1379b3a27b150bb8051283275
We recently created a new GID that can be granted to critical system
processes, so that the system is usable enough for the user to free
up disk space used by abusive apps.
128MB ought to be enough for anybody.
Test: builds, boots
Bug: 62024591
Change-Id: I412ed9b0a885668ebe4c6c677a3bd0cd7f44080b
Signed-off-by: Alberto97 <albertop2197@gmail.com>
