* 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

* We don't support NFC by hardware so these permissions are
  technically useless

Change-Id: I35ca7307208cb2d19f81260cd84da0bc0a79c576

* Use fsync_mode=nobarrier to improve random write and fsync performance
* Enable runtime discard to take advantage of asynchronous TRIM
* Remove formattable flag to be sure we always have ext4 by default

Change-Id: Ic7f6fbad178ef6251924e4414c660f4dbe1a8c44

 * Matches rild.legacy.rc from Pie's RIL

Change-Id: Icdb0a3e4859bc0a4011e34fdd483cef2ca3b8a7f

* The marginal memory efficiency improvement we gained with that
  doesn't really outweigh the waste of CPU cycles.

This reverts commit c3fc1e5b.

Change-Id: I89f126b80cdc669c70a2f2e2d8ed2036bdee7894

* We do not use this in the kernel tree

This reverts commit d106e1d5.

Signed-off-by: khusika <khusikadhamar@gmail.com>
Change-Id: I46c935709755b813db013edb45389acce4366143

Change-Id: I64ac891940aadc7662cd15d6119955f6505b297e

* Restart HIDL camera provider to cover some edge cases where camera isn't
  working on FDE devices with boot pin enabled.

Change-Id: Ia757e9d07de26008f426fca582439d68b6d6fecb

* Fixes most denials in charger-only mode

Change-Id: Ia4fad60ab4da7dd6cd84a86a959d377b70c86e10

* Use CAF's more aggressive defaults, as they improve our memory efficiency.
* Keep using LZ4 compression and page-cluster=0 to avoid the potential performance hit.

Change-Id: I39966f000f2dc6dae5bb83be356c4753a6a62cca

We already do it properly in fstab.

Change-Id: I5ff2a626cdc4ef8ff847ad886e304a308a505253

* From LA.UM.7.6.r1-03600-89xx.0

Change-Id: I125d09509bf72c8ec06a401d690e32b0c286f37c

Change-Id: Ia5b4269ebb48753908629e00451d31744f9483bc

Set USB controller configuration like mtp_rx_len, mtp_tx_len
and rndis_transports for msm8953.

Change-Id: Iec7d0341e271a2df2fd6dd43d6f3bc930239d679

Change sysfs owner to system for /sys/kernel/hbtp/display_pwr.
Sysfs is used by power team to notify when display is on/off.

Change-Id: I6adacc30d39e65ad4250f32484ddf87206b85c12

Change-Id: I05aad1a8a56d5feaf25d4cc129503ba6a917517c

Change-Id: Ie485c62270047b5eb8d04bebaf263299da5d9a3b

It doesn't really make much sense on msm8953.

Change-Id: I2751f29a1ca5f6a3de00b534faaa45f1c8e20e7f

Enable sched tune settings for msm8953 targets.

Change-Id: I4ea069f79e4d1ffc7b94c8699abe0c4d80ff554f

Enable sched_boost in early_init for msm8953 targes.
Sched_boost is in order to migrate threads onto perf
cluster and will be disabled at post_boot.

Change-Id: Ica92a3b48a32fc63e33776f0079314d8b7faeaf7

Required on 4.9 now.

Change-Id: I1b4557da497c3c63d64770f94a2ff56e72602f8a

Change-Id: Idc11b64c018bfcd133afa5f5215c4f6dbbe56174

It slows down our boot by roughly 5 seconds.

Change-Id: Icccb51a5cd7d6a9bbe21e2b44be3ad178838148e

post_boot.sh reads from /sys/class/graphics/fb0/modes which is owned by
graphics group.

Change-Id: I0b0a8b1f333a1385f72e9aff1ca11836b6e5800e

The post_boot script writes to scaling_(min/max)_feq and
wake_lock nodes which are owned by system and wakelock groups.

Change-Id: Ief83a152f8433976082aaa129bdb193dd3adb320

* The creation of /data/misc/wifi and /data/misc/dhcp was moved long ago
  to the core init.rc script. Moreover, /data/misc/wifi is deprecated
  since wpa_supplicant now relies on /data/vendor/wifi.

Change-Id: Ic0a33af44ffe163d3dd06cebdc1e192dc9bcb11f

init.qcom.sh accesses files owned by groups radio, system and hence
the groups have been added.

Change-Id: I535eeaf42f38532ec6de46eb57f3cc0e1d959a47

Changes the prefix of mbn_copy_completed to ro.vendor.ril
as there a permission error with current prefix. and due
to this MBN OTA is failed.

Change-Id: I31a0032aba79177680b7b91363d1d9be97dd9c90
CRs-Fixed: 2261501

DAC_OVERRIDE is disabled for all the vendor init scripts
in Android P. This change will grant "group root" the write
permission temporarily for deleting/copying operations.

System user could not access the MBN files in data partition
no longer. Only radio user and root group have read permission
after boot up.

Change-Id: I9f184da2253dc5896b145c0e52fc3b42da15d9f7

1) Using "chmod -h" instead of "chmod"
2) Using "mkdir -m" instread of 2 seperate commands
for creating directory and change permission
3) Using "write" command in RC file instead of "echo ...>"
in bash
4) Create "data/vendor/modem_config" for storing MBNs, which
is read only
5) Remove qcril.db copying in sh file, since this logic is
not used anymore

Change-Id: Ib9a9e0d32ae529dab3dc0c164062d2887dff4439

Solves the following denial.
denied  { write } for  pid=548 comm="init" name="storage" dev="rootfs" ino=15996 scontext=u:r:vendor_init:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0

Change-Id: If246f497bd8384f0fee81469d8d29dcb528d4d4e

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: Id76e6c31a6b9a203f7b2789edf724ac091afe4ab

Treble compliance.

Bug: 70228425
Bug: 70393317
Test: complete wifi test in b/70393317
Test: Test wifi on Taimen and Sailfish
Test: verify sockets exist in /data/vendor/wifi/wpa/sockets

Change-Id: I0bfc3a351419f0a03498e79664949f353369bf1b

Bug: 72394251
Test: Able to start supplicant from framework using
ISupplicant.getService()
Change-Id: I19b8434e7241b9028e7dc86316ec9d5512affcca

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>

Framework will now add interface to supplicant (via HIDL) when it
needs to control an interface, so don't specify them in the startup
params.

Bug: 69426063
Test: Device boots up and able to connect to wifi.
Change-Id: I817d28093f8b982e3806c212babd888c0f5eb7c0

Wpa_supplicant's random pool is not necessary on Android. Randomness
is already provided by the entropymixer service which ensures
sufficient entropy is maintained across reboots. Commit b410eb1913
'Initialize /dev/urandom earlier in boot' seeds /dev/urandom with
that entropy before either wpa_supplicant or hostapd are run.

Bug: 34980020
Test: Use wifi and wifi tethering on Taimen
Change-Id: Ib5caf362bc939911b357db186a274957d3fbf186

 * LA.UM.6.6.r1-06700-89xx.0

Change-Id: Ia81ae03011aff768cf17fe46c5a09132ebb3b1a8

 * The kernel defaults to NOOP, which allows high throughput
 * Switch to BFQ, once we are done booting up, to improve UX

Change-Id: Iff7e24eba73a722c08e5e248ebced389223b0444