* Our device doesn't behave well with the "new" logic that tracks the audio
input with the default SIM
Change-Id: I084305b0ac1bdeb9915d2f75cfdeda4ab7fd0244
messages during build:
device/samsung/klte-common/configs/nfcee_access.xml:9: namespace error : Namespace prefix android for signature on signer is not defined
Change-Id: I7f3a1588b9cf05cb6aff11ccc59d14e75cc6e98e
- missed on this commit: c27f8259a8
- thanks yodevil for pointing this out
Change-Id: Ib9f9832c0ffc4959773053c38e19453be2aded2e
Signed-off-by: Joshua Primero <jprimero155@gmail.com>
* 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
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
* Match the changes made in LineageOS/android_frameworks_base@3d422c3
* Since Pie, AOSP is forcing us to define speeds and power values per CPU cluster.
For single cluster chipsets like MSM8974, define cluster0 with only 4 cores
to retain the existing behaviour.
Change-Id: Ida1edb9cc0335ffdb0ec6857da02b84a6a9d1633
* Some variants have autogenerated fingerprints that are >= 92 chars
on official nightlies, and overriding them in init is failing
* To workaround this, force a build fingerprint that's shorter
Change-Id: If3909ad6f6f00b77559aff16feb6291b42ddbc47
* Google killed it in Pie
* reference: LineageOS/android_frameworks_av@d0a98fa05
Change-Id: I9bfd354c3e3a3d4c193c3865ac7eae84719c02dc
Signed-off-by: Joshua Primero <jprimero155@gmail.com>
media_profiles_V1_0.xml is created from media_profiles.xml by replacing
the dtd schema inside media_profiles.xml with an external reference to
/system/etc/media_profiles_V1_0.dtd.
Change-Id: I0fbb03603a72d0108a96bfa0f0a4ceb12ef3d430
* Per the kernel, bare murata isn't a thing for BCM4354, but that's
what macloader parses the OUIs as being. It's much easier to make
the label match than to further complicate macloader.
Change-Id: I3474e610a0d38873b0274ccb24b24733047929d0
* semcove->semco3rd
* This is actually a "fake" blob, a copy of the un-labeled vesion,
as are all except for wisol. These are needed because wisol is
different and the picker will default to the last stat-ed file.
* Broadcom libbt-vendor was previously coded to look for a semcove,
but that wasn't a value that macloader would write to
/data/.cid.info
* This creates a file that aligns to the new Broadcom libbt-vendor
code.
* Eliminate the src:dst syntax, since these are pinned anyway.
Change-Id: I6f5381ad19174b7aa074eae0ab0db41730b3d7d7
* This is horribly broken after N and if someone really wants to
drag these devices forward they'll need to get a rules exception
anyway.
Change-Id: Iec4e6927e019c9ec91cc16d3eeacb0990ffff6f5
* These need a manual restorecon after create else they do not pick
up the radio_data_file label.
* avc: denied { read } for name="databases" dev="mmcblk0p26" ino=33320
scontext=u:r:rild:s0 tcontext=u:object_r:system_data_file:s0
tclass=lnk_file permissive=0
Change-Id: I3286f47521467f6a1d65befec8a5c6dd7ff00183
* These aren't used anywhere in the source tree and none of the blobs
reference them. We can drop this instead of finding/inventing an
appropriate selinux label to allow the setattr.
Change-Id: I9e238aadade4c051c2815bdf15891443cc649624
* early-init is before the global restorecon of /sys gets run, so
we need to set a context on these before changing attributes
Change-Id: I493a9bb0c1bd2ea83a815e07169b8b689cf76a5d
* Samsung loads the firmware through the front door. Pie init
runs faster than previously, so we need to wait to change
the ownership until some point later, after the firmware has
time to load, else the load gets blocked by a dac_override.
Change-Id: I37be9e22b49735388ce1f5b922132dbfd20e2dc3
fw/b changes in Oreo cause some USB audio devices
which were previously recognized as AUDIO_DEVICE_OUT_USB_DEVICE
or AUDIO_DEVICE_OUT_USB_ACCESSORY now to be recognized as
AUDIO_DEVICE_OUT_USB_HEADSET (0x4000000), causing this error:
AudioPolicyManagerCustom: setDeviceConnectionState() could not find HW module for device 04000000
BUGBASH-2398
Change-Id: If1f6c760e28a2daeb3855c86fc561c7e5e85f0bf
(cherry picked from commit 36fb5d9d181a7e0ae8dd5f2e93a1f5f1a70d1302)
* P made changes to pthread_mutex_init() that are incompatible
with our libsec-ril libraries. In order for rild to even see a
radio as being availble we need the legacy behavior.
* Even though our libsec-ril libraries are from 5.0, which is API
level 21, we do not appear to require any of the other behaviors
from API levels earlier than 27.
Change-Id: I3b3d0160236df09bdae95c5d9f10a61bf91ebc72
* msm8974-common has moved to hwbinder mode for sensors, with the
multihal statically linked into the impl. We don't need this
version of the multihal anymore.
Change-Id: Id9e9103bb03351cef2a7cb0e81800057898fe862
* This singularly handles both text relocation (M) and mutex (P)
linker restrictions
* mediaserver - Needs text relocations
* mm-qcamera-daemon - Needs both text relocations and mutex restrictions
relaxed
Change-Id: I97a79fb57aaadf5cf62894489522b2de6d8c2e36
Framework will now add interface to supplicant (via HIDL) when it
needs to control an interface, so don't specify them in the startup
params.
Bug: 69426063
Test: Device boots up and able to connect to wifi.
Change-Id: I817d28093f8b982e3806c212babd888c0f5eb7c0
Wpa_supplicant's random pool is not necessary on Android. Randomness
is already provided by the entropymixer service which ensures
sufficient entropy is maintained across reboots. Commit b410eb1913
'Initialize /dev/urandom earlier in boot' seeds /dev/urandom with
that entropy before either wpa_supplicant or hostapd are run.
Bug: 34980020
Test: Use wifi and wifi tethering on 8974 targets
Change-Id: Iaa2a8a42e4e3fd941c5be0f8fa691245cdb429e9
The kernel does not support aio with ffs.
Set the property so adb/mtp know to use the compatible
functions, and the same while in recovery.
Bug: 37916658
Test: Use adb / use adb in recovery
Change-Id: Id35a05fcb9952dcf7239bd15a61cc620537419bc
