https://github.com/LineageOS/android_system_core/blob/lineage-21.0/init/init.cpp#L1099



This partially reverts commit 4aca9967.

Change-Id: I284f80f364e9057a8373a015f0acaee3ef9e395d
Signed-off-by: Tashfin Shakeer Rhythm <tashfinshakeerrhythm@gmail.com>

For easy transition from SchedTune to UtilClamp, direct access to these
cgroups should be abstracted by using task profiles. Replace writepid
commands with new task_profiles command.

Bug: 155419956
Test: change .rc file and confirm task profile is applied
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ide373c283359cf4b73af4cb0813d8c0306942595

Those commands have moved to init.rc.

Bug: 170507876
Bug: 171740453
Test: build pass
Change-Id: Icfe520e7f7367461607cc8fb5e524d9699e79124

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

* needed for redwood/taoyao/vili

Change-Id: I2a9312ec07bf227965d3655709459079926ade9d

* Needed for redwood/vili/taoyao/zijin

Change-Id: I93f1d7d016a34e70c2772c8bfabb7d4fd0210cc2

Change-Id: I70cc903a03ac9fa3303bb8fa039c9de4806449bf

Change-Id: I688347cfe59f56e4de2e4bf3c3324ca465f7a897

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

Change-Id: I1287d066eca7d1a274b491f80166ed68c5b11459

Change-Id: Ibbaf1fd6ac6e45b71c66b79a95fa2c936cd3e695

 * This lets us flash /vendor regardless of the kernel situation.

Change-Id: Ie1c18354b26006e416d06474f5844ceef3cfbaf3

* Keep previous commits applied

Change-Id: I8b7efe10b25dcd673c770bcf7ae92435065c05ac

Change-Id: Id283d33472e4af8c3397728174908660e3762cd0

Change-Id: Ib837e4a70015dc24d431458a1cce5b86e87816a9

Change-Id: I7cb0a45c865d9dbfd800b1d633f8d5ae613bb1b9

* It is started in the on init phase in /system/etc/init/hw/init.rc

Change-Id: Ie10e1d4c520329a76627a965ca139f9ad0f71875

* Drop foreground and top-app cpus
* Set 0-3 as background cpus
* Drop xiaomi iolimit and custom types for shima

Change-Id: I3733e196a8ed090c15d6867b0722425435f31474

Change-Id: I813e6893475caf8196f7c81f6ae237bd1d4b73d1

Change-Id: I685a215927b445bb2fac9229a1f41de5f88741ef

Change-Id: I6831d37d02012e3ce2d58a9c45818e594a658883

While at it, update lahaina one from odin V12.5.12.0.RKMCNXM

Apply the following commits to all scripts:
commit a7efe9f3
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Tue Sep 28 09:15:41 2021 +0300

    sm8350-common: rootdir: remove cpu 7 from foreground tasks

commit 52fde070
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Fri Sep 24 02:44:34 2021 +0300

    sm8350-common: rootdir: do not touch sleep disabled

commit 30ddf5a8
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Sat Sep 18 02:57:51 2021 +0300

    sm8350-common: rootdir: cleanup

Change-Id: Ibd4e8717b52c35faa4d43ade170dbde58c04ed37

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

Init doesn't handle all dm devices

This reverts commit 17d09b70.

Change-Id: I2b42c286307e8fd41140bca8f893ccdf13ebfc06

Change-Id: I5c65e0df255853eb2b3018a27ceb807c111bc4df

Change-Id: I4353249682aaa0c08b5af462656974bcb6fdf14a

* From odin V12.5.12.0.RKMCNXM

Change-Id: I5509271b0cdb23e40f8fb4186b740c66d79fe069

This depends on caf BoostFramework

Change-Id: I1d3e6750ecb88db83f265cc06b175cbc0cfb9726

This depends on caf BoostFramework

Change-Id: Ie3ea41f7be323472124a395b8fee52aa7333c2fc

Change-Id: Ia37b752c369d8b0dc48aba33898ce7e245f4de2d

Change-Id: I44004a3c1377d91e887f66905df5f8c61b0d5639

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.

https://android.googlesource.com/platform/frameworks/base/+/c78a463e875d91eae2cf256042fd99d130217c38

Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581

Change-Id: I7c0a9ad622a0c42966d84024c22cd03e033fd09b

Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.

Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries


Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537

Change-Id: I0ca98738e4964d23614df797b1faaebe0058a451

The copyright header has been modified by caf while the initial lahaina
tree whose fstab we use.
Specifically from https://source.codeaurora.org/quic/la/platform/vendor/qcom/lahaina/tree/fstab.qcom?h=LA.UM.9.14.r1-18900-LAHAINA.QSSI12.0&id=b403cbb26431c57a8590f94307f12443a55e29e2

Change-Id: I1dd07a729feeded6478e095573070fde532f2f02

Remove start console

Change-Id: I1041fa446499cd82bcbf6d5b86cb25a9a88fa90c
CRs-Fixed: 2977860

Disabling UFS clkgate and ah8 during boot time helps in reducing
IO delays, which helps in reducing the total boot time. This change
will disable UFS clkgate and ah8 during early-init and then enable
it back after boot completion.

Change-Id: I6a10cd57a30fe3bdc4fba72a0d84cdfa3b1fd513

Two fstabs are needed to support different data unit number (dun)
size for ufs and emmc hardwares. This needs different encryption
flag in fstab to address the difference in dun size.

[ArianK16a: don't add the emmc fstab since all our devices are ufs]

Test: Verified bootup, vts_kernel_encryption, fscryptctl.

Change-Id: Iff03422d39c789c544bdd86faef070ae46eb4e0e

Remove the hard-coded path for /dev/block/bootdevice.
Instead use the bootdevice property.

Change-Id: I194587e250f1d24f677c6fd3f34a23f146d4bc7e