b/71936484 has audio accessories failing to connect
when there's a transition to suspend when they're attempting
to enumerate.
Avoid this problem by increasing autosuspend delay
from the default 2s to 7s.
The longest I've seen a device take to enumerate after
vbus is ~3 seconds, this gives a 2x margin.
Test: booted on Walleye, saw no more messages:
[ 472.412555] c0 5675 msm-dwc3 a800000.ssusb: DWC3 in low power mode
between device connection and enumeration.
Bug: 71936484
Change-Id: Ie585f2ce5dec429510cc6c00452dc4d49f1372a0
There is no evidence that Qualcomm devices running a rather recent IMS
stack need to include AOSP RCS packages. RCS already worked before this
change and continues to do so, but the main goal was to get rid of some
of the RCS related log spam, which was accomplished here.
Change-Id: I219546e29d288373877e9bcd194a60ef5e09f224
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
QCOM's driver can support a max of 512 scan results. Ensure that
wpa_supplicant is in sync with that number.
Bug: 74724482
Test: Device boots up and connects to wifi networks.
Change-Id: I62dbd2bd3789c454e9683320d3a58f67019ea7ee
* It's proprietary and already included in vendor makefiles.
* Remove antradio_app target which is dead
Change-Id: Ic19703a39e3e691a04b226b2cb2a27b02703724d
Remove various variables related to where kernel and ramdisk are loaded
by the bootloader. There are two reasons for this:
1. The B1C1 bootloader ignores all the offset values for kernel, ramdisk
and tags. The default B1C1 memory layout has been designed to accomodate
a larger KASAN kernel.
2. The variables BOARD_KERNEL_TAGS_OFFSET and BOARD_RAMDISK_OFFSET are
ignored by the Android build system (unless they are copied into the
BOARD_MKBOOTIMG_ARGS variable). This is in contrast to the variables
BOARD_KERNEL_BASE, BOARD_KERNEL_PAGESIZE and BOARD_MKBOOTIMG_ARGS which
are referenced by build/make/core/Makefile
Bug: 117832711
Change-Id: I3404a4e084ed063d51077a3a80229854362c768b
The fingerprint HAL is insensitive to increased CPU throughput, but it also
has a tendency to spin while waiting for FP hardware. Limit FPC to the
system-background cpuset in order to avoid increased power consumption
when accidentally touching the fingerprint sensor.
bug 76115243
Test: fingerprint in system-background cpuset
Change-Id: Iaffe6f63bd76b7a1c4acaf0cae980840af515961
Signed-off-by: Manish4586 <manish.n.manish45@gmail.com>
* As seen with December patch some system apps including user apps started to lag (like screen tearing).
* Enabling Vsync and disabling backpressure resolves the issue
Signed-off-by: Manish4586 <manish.n.manish45@gmail.com>
Change-Id: Ieea19e65020643353494336079104f3f53bd1e4c
Prefetching appears to have a slightly negative effect on boot time, and
actually makes boot time much worse when the available dm-bufio cache
shrinks. Since we anticipate the dm-bufio cache will shrink (because of
an increasing number of APEX dm-verity targets), disable prefetching
completely.
Boot time w/o this change: 12.085
Boot time with this change: 11.958
Boot time w/o this change with 128kB dm-bufio cache: 22.82
Boot time with this change with 128kB dm-bufio cache: 12.007
Test: atest google/perf/boottime/boottime-test
Bug: 136247322
Change-Id: I12e342c5692fa89855d9c217f2e94287ff5642a6
