* Perf/Thermal blobs from angler - OPM6.171019.030
* Thermal HAL from angler base + hima modified configs.
* Modified thermal sensor numbers for kitakami platform.
* From https://github.com/AICP/device_htc_hima
On high RAM targets, due to more anonymous memory availability,
we can improve headroom by increasing ZRAM swap size,
especially under memory pressure, and during background app compact.
Also ZRAM swap size is logical and is used when needed and
shouldn't cause other side effects.
Change-Id: I11949b8bdf16e9b4b8abb1bd633ffa1a1c0b1ad6
rmt_storage should not be automatically killed by Android during
shutdown since it is needed to actually process the peripheral
shutdown
Change-Id: I58a29fe86955f0abad944727bb4208dad89f495d
* This config needs to be modified for legacy devices. As
there is no easy way to split it, import it into device
tree and bind mount it instead.
* Head at android-10.0.0_r2
(3ac371484399da6efbd0c835aa461d3326263ab1).
Change-Id: I8d5003d7cd3a471c569844aede4b5ea4c68ae36b
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.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as its a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017
Signed-off-by: John Stultz <john.stultz@linaro.org>
The kernel does not support aio with ffs.
Set the property so adb/mtp know to use the compatible
functions.
Bug: 37916658
Test: Use adb
Change-Id: Id35a05fcb9952dcf7239bd15a61cc620537419bc
* Mounting /system partition is handled in kernel now, however
removing the entry from fstab caused issues building the OTA.
The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
As of Q, the directories for the mount points must be created
upfront. Worked well on P, but not anymore.
Change-Id: Id2a7a01c78a82fc310c04377f2e07143178a4f52
* Currently, config.fs doesn't have the ability of adding AIDs
to init so that they can actually be used in init scripts.
* Replace all instances of qcom_diag and rfs_shared with
oem_2950 and oem_2952.
Change-Id: Ibc1a2db8c73ca6ff9d882e42ac734e4ea65ad949
This will let the wifi hal run as "wifi" user and not need root
permissions to access this path for firmware reloads.
(cherry-pick of commit 7a5ffa283181f4437c2107c59af4580a50df31a9)
Bug: 33435250
Test: Compiles.
Change-Id: I84a38cea5e0f729147c3191c3485a3738d7838ef
breaks audio output on certain impedances, like car audio or hi-fi amplifiers
Change-Id: I0e870947442c877499305dca1675db9dbb948f13
Signed-off-by: airlessproject <vlatko.mitreski@gmail.com>
