* 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

(config_tether_upstream_automatic=true)

Test: as follows
    - built, flashed, booted
Bug: 32163131
Bug: 62648872
Bug: 63282480
Bug: 110118584
Bug: 110260419

Change-Id: I604cda53d6d37a33de3e3ccc65c0da781d21278b

Test: adb shell dumpsys pinner after boot
Bug: 111132016
Bug: 78585335
Change-Id: I4ed0587ae5348bbe03ad9ac5f1c5b1726dbb8246

Configuring device to be in interactive mode whenever display is on

Change-Id: I2ac5fb39da9a93111283dc23a5fafae0d3cd602f

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

Used by some HALs.

Change-Id: I25eafcd0ef445dac2b2f7b90a8ff451697937f3e

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

Add 'wowlan_triggers=magic_pkt' to wpa_supplicant_overlay.conf. With
this, wpa_supplicant will tell the linux kernel that the wifi driver
is wowlan capable, and will wakeup the host when a magic packet is
received. Most importantly, the kernel will no longer disconnect wifi
connections before suspending wifi.

Change-Id: I3226943940046ad98e4ab410897d4fdcb457ee5a
CRs-Fixed: 2076216

Change-Id: Idc11b64c018bfcd133afa5f5215c4f6dbbe56174

It slows down our boot by roughly 5 seconds.

Change-Id: Icccb51a5cd7d6a9bbe21e2b44be3ad178838148e

Change-Id: I3e3668d77a7b65fd3572248ba98c980537ad1e25

Change-Id: Iad4dfe5bce333b2e94e794097314187caa4c5918

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

New name is config_dozeAfterScreenOffByDefault
Bug: 73178121

Change-Id: Ie3d1ea5a2cc480655592bf6e49b37f5ea07f3f58

Change-Id: Icb2b9810217f4b4d442ab83a16f455bd2ed82071

Change-Id: If846cc590060025202fa336af4420747f6b01238

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

Setting TARGET_2ND_ARCH_VARIANT to armv8-a, instead of armv7-a-neon,
can silence the related warning during build.

Bug: 68012286
Change-Id: I18ae3aa985fd6bff11f043a155f3685d9f6644b8

Change-Id: I8432cec37860864bd78591403f338fd029357b39

Change-Id: Id6d617ead095ef4a0d37e0d8ee1996cd7f0b10bc

LA.UM.7.6.2.r1-03600-89xx.0

Change-Id: I252595bd99b337f9b5cf0353bb0abc7bcce6f203

 * From: OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1809071801:user/release-keys

Change-Id: If0f4628104564020c47087599c5d64ee974d1b05

* With QTI bluetooth it's no longer needed.

Change-Id: Iba4b0b6ba24fe1b85e7175291ed84769615ffadd

 * Otherwise, it resulted in Doze service not being activated
   when enabling one of the features for the first time after
   a clean installation.

Change-Id: I625d9109fb85c970f0e59b1cbcabba7d4375d2f3

Change-Id: I74901339740b82b79f36754c7e52894a98020c3d

Change-Id: Ica5c6f480d1ee84325a113d4149a815d39d8a84c