* 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
* In O, the default setting for mobile data always active was
changed from off to on, meaning that when non-WiFi tethering
is being attempted, more than one connection can be active
* Since the first active connection type in this overlay is used,
reorder the values to get WiFi connections first, and then
any type of mobile data connection, instead of vice versa
Change-Id: I41f31ba1a2793e209ff439c9ba28a390fecdeecb
* This is needed for Trust, as we don't have a Vendor image that sets a
valid vendor security patch level.
* Taken from the G900FXXU1CRA2_G900FOXA1CRA2_BTU Factory Image.
Change-Id: I105cc7e464e581683c6784e3aef8f7297b90aea0
* We have included the appropriate android_atomic methods in libril,
so the symbols are loaded into the process space and the libsec-ril*
dependencies for all builds are handled.
Change-Id: I93289af789df7e263488e1db29bdbde0d0964e97
* Recent binder changes caused our approach of shimming libcutils to
re-add the non-inlined android_atomic* methods to start getting
slapped, at least with NDK apps. This looks oddly similar to the
heads-up we received in 7.0, so no clue why it let us do it in 8.*
prior to now.
* See: https://developer.android.com/about/versions/nougat/android-7.0-changes#ndk
* We did this because all of the libsec-ril* blobs and libuiblur
needed it and doing each and every libsec-ril seemed fragile and
fraught with the potential for error, but "fragile and fraught with
the potential for error" is better than "phone breaking". And blur
doesn't seem to ever be coming back.
* We'll leave the "standard" libsec-ril.so here and let the
individual devices handle anything specific if they have variant-
specific blobs
Change-Id: Ib11048e4924f34ade20f44b707f0106e139f2f82
* vcs_device is used to label /dev/vcs*, which are virtual consoles
* Create and use our own label for /dev/vfsspi so our fingerprint
hal can access it, and rename vcs_data_file while we're at it
Change-Id: I01f0e8c4924d3847383319ce59dbbf802f89a36b
This reverts commit aee12a34df.
* No Samsung msm8974 device is going to develop an OSS camera HAL
at this point. Move this common stuff to msm8974-common.
Change-Id: Ib0bb18fe819e2ebbb39c9b278ccf687444f65488
