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
During bootup the device first enumerates in ADB only composition
and then falls back to the persist.sys.usb.config.
Prevent this enumeration in ADB only composition during bootup
by setting the sys.usb.configfs from init.qcom.usb.rc
Change-Id: I4d9aa8454202b8118ff76dfda7f44c6413c42020
The restorecon_recursive directive in init is only applied if the
file_contexts file changed between builds, but not necessarily if any
file or folder inside /mnt/vendor/persist/ has changed.
The restorecon code checks whether an xattr named
"security.sehash" contains a string that matches the current
combined hashes of the SELinux context files and skips restoring labels
if there is a match, see
https://android.googlesource.com/platform/external/selinux/+/refs/tags/android-9.0.0_r35/libselinux/src/android/android_platform.c#1546
Force wiping that xattr so that restorecon always runs since it's not
very expensive (there are currently only about 50 files on /persist).
The restorecon is needed to fix issues such as wrong stock labels on
/mnt/vendor/persist/sensors/:
sensors_persist_file -> persist_sensors_file
Change-Id: Ic0cd848836ee550499d9236f56ed6e939e35f01e
* Our HAL doesn't really support bokeh mode, but enabling this
makes our auxiliary camera available in Snap again.
* Also update copyrights, as this was never an AOSP overlay,
and that copyright was a typo.
Change-Id: I296d42e5e371711b7acb81cb3235ea572a2ded56
Set ADB as the default composition for GVM targets, as DIAG
over USB conflicts with the DIAG over IP used by the PVM.
Change-Id: I09389564db284b16ccb34243eaf34bb17860b30f
Signed-off-by: Anant Goel <anantg@codeaurora.org>
- Grant SYS_NICE capabilities to audio HAL processes as sound trigger
HAL threads need to run at real time priority as well as use the
CPU affinity, for far field voice.
CRs-Fixed: 2359951
Change-Id: Ie0da744978609c750e92aec2c6001ace1868ad31
- SnapdragonVoiceActivation feature for Far Field Voice version
affines its threads to 0-3 CPUs and so prevent them from isolation
for qcs605 target
Change-Id: I09ef5cc97ee245133315edc0821f3a2afc54e99b
ZRAM compression uses the linux slub allocator its internal data
structures. If these internal data structure consume a lot of memory,
ZRAM compression may increase memory usage, rather than decrease it
as expected. Decrease the chance of this occuring by ensuring the
SLAB_STORE_USER debug option is disabled.
Change-Id: I4684feda94b7bebacb6218b7f979c95771b0ee10
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
check populated dm-* nodes and Update read_ahead_kb
values to them. This is needed because on targets
with verity disabled dm-0 to dm-6 are populated,
while on enabled targets dm-3 to dm-6 are populated.
Change-Id: Ia4e262d7487120695db53b562b5764598fd40a87
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.
CRs-Fixed: 2615975
Change-Id: I3226943940046ad98e4ab410897d4fdcb457ee5a
* AOSP defaults to true but 10 QC telephony extension sets it to false.
* Restore AOSP behavior by enabling it with a system property which has
higher priority over global system settings which is used by QCOM w/o
modifying the jar.
Change-Id: I45854b91bb8cfafabfe811777cda9f1e1840febf
Author: dianlujitao <dianlujitao@lineageos.org>
Date: Tue Oct 22 21:11:54 2019 +0800
Change-Id: I1862e9021ccbc8430c9a1dcda21016fdbf2f0bad
Try to fix glitches on AAudio MMAP output on bonito.
The DSP is returning a position/time pair that is too soon.
Bug: 122680738
Test: Should see glitch.count = 0 when you run this test.
Test: adb shell aaudio_loopback -tm -b999 -s20 -x -X
Change-Id: I3cf7698e4038b375a116c4d708eb0686cc72f40e
Merged-In: I3cf7698e4038b375a116c4d708eb0686cc72f40e
