- Make use of uclamp boost for top-app and foreground
hints based on newer pixels
Co-authored-by: Vivekachooz <vivekachooz@gmail.com>
Change-Id: I70c4262230841b3c7bf84b4165916a22312f829f
Fix for:
W libperfmgr: Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1
Change-Id: I1e394919b75e192def99c444993546634c951781
Reduce readahead from 512KiB to 128KiB to reduce thrashing when we
have a lot of apps running.
Bug: 110908295
Bug: 80426378
Test: manual - device boots
Test: manual - check app launch does not take long
Test: cts-tradefed.sh run cts -m CtsCameraTestCases
Change-Id: I59c1f2f8a6fbb5e0d956ba07a40a2bfac3b61481
No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
Required after recent kernel update. Based on QCOM commits:
liblight: set "timer" trigger before setting delay for blinking
display: light: set timer trigger before updating delay_on/off values
display: light: clear timer trigger before setting brightness
Change-Id: Iaa4d78fe7411f299ba866de174782c269c068c23
* W libc : Unable to set property "ctl.stop" to "ril-daemon": error code: 0x20
* W libc : Unable to set property "ctl.stop" to "vendor.ril-daemon": error code: 0x20
Change-Id: I80784cb3d6ee3cf539b3a8b5dbcada2e8b850641
Bootloader sets ro.boot.revision, we can use this to show
"Hardware version" in model information in Settings.
Change-Id: Id2d825f60f792e6d05c0b34cfee811a0ac3b5604
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
It turns out berlna still needs this to initialize FP sensor
even though in the real world only one is used, so we might
as well leave this in common for berlna and xpeng
Change-Id: I094d12dc7581099c611dc1ffedf63d065af04081
This reverts commit bdbd9a4df4.
Reason: Xiaomi Mi 11 Lite 5G NE (lisa) got A13 stock ROM so we can just
flash their bluetooth firmware partition onto ours and fix the issue
right at the source and drop the fix we have in our device tree.
Change-Id: I21f4918f8d0fc794db29b4aa2235c238c36a800e
This fixes the bluetooth module crashing due to firmware that should support
BT LE as yupik is BT 5.2 but instead it fails.
Change-Id: If744eff8ceb7f665b0304fb4a506efd23926bbe1
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
* The close-sourced binary uses symbols removed on R. It doesn't make
much sense to fix the 45MB binary :), simply use AOSP one instead.
* Move charge-only services to init.mmi.charge_only.rc while at it.
Change-Id: I62cdd36603afb46d5287dfcaac3d16acc9fca178
